SoftTree Technologies SoftTree Technologies
Technical Support Forums
RegisterSearchFAQMemberlistUsergroupsLog in
Web Console has login issues after a few hours
Goto page 1, 2  Next
 
Reply to topic    SoftTree Technologies Forum Index » 24x7 Scheduler, Event Server, Automation Suite View previous topic
View next topic
Web Console has login issues after a few hours
Author Message
Loril



Joined: 21 Feb 2007
Posts: 82

Post Web Console has login issues after a few hours Reply with quote
Hi,

I've installed the latest web console on our web server where we use it to connect to several scheduler instances. Everything works fine for several hours and then all of a sudden, the login would fail with the error "Server reply is invalid". We don't have security setup on any of the schedulers so it's not a set up issue. I've turned trace on and here's the output. Towards the very end, I have at least two instances where I've attempted to log in and received the error. Thanks.

DPB Release DPB_SESSION_SERVICE(07055CE8) refCount(2)
DPB43 SessionId (07055C28): Create Object : className(jdpb_24x7), instanceId(000
00000). ... (00000000)
SMI06 Connection(07051E88): Process request Message: (02065C10) serviceId(0), se
quenceNumber(0). SUCCEEDED (00000000)
SMI01 Connection(07051E88): Create Message: (020601C8), initial size 0 bytes
SMI03 Connection(07051E88): Send Reply Message: (020601C8) sequenceNumber(229746
) Asynchronous. ... (00000000)
WSD08 Send: result = 0
SMI03 Connection(07051E88): Send Reply Message: (020601C8) sequenceNumber(229746
) Asynchronous. SUCCEEDED (00000000)
DPB43 SessionId (07055C28): Create Object : className(jdpb_24x7), instanceId(000
38171). SUCCEEDED (00000000)
WSD07 ReadHeader: Proto = 24576, Len = 169
SMI01 Connection(07051E88): Create Message: (020601C8), initial size 169 bytes
DPB55 Memory Session : (07055CE8) count(996), total(356352), alloc(213523),
free(133161)
DPB56 Memory Proc Common : count(1667), total(233472), alloc(114810), free(1122
35)
DPB Release DPB_SESSION_SERVICE(07055CE8) refCount(1)
DPB AddRef DPB_SESSION_SERVICE(07055CE8) refCount(2)
DPB40 SessionId (07055C28): Handle Request: INVOKE(6), streamVer(0). SUCCEEDED (
00000000)
SMI02 Connection(07051E88): ERROR OCCURRED: Object instance does not exist (8004
206B)
SMI01 Connection(07051E88): Create Message: (02065C10), initial size 0 bytes
SMI03 Connection(07051E88): Send Reply Message: (02065C10) sequenceNumber(229747
) Asynchronous. ... (00000000)
WSD08 Send: result = 0
SMI03 Connection(07051E88): Send Reply Message: (02065C10) sequenceNumber(229747
) Asynchronous. SUCCEEDED (00000000)
DPB Release DPB_SESSION_SERVICE(07055CE8) refCount(1)
SMI06 Connection(07051E88): Process request Message: (020601C8) serviceId(0), se
quenceNumber(0). SUCCEEDED (00000000)
WSD07 ReadHeader: Proto = 24576, Len = 112
SMI01 Connection(07051E88): Create Message: (020601C8), initial size 112 bytes
DPB AddRef DPB_SESSION_SERVICE(07055CE8) refCount(2)
DPB40 SessionId (07055C28): Handle Request: GET_PROPERTY(8), streamVer(0). SUCCE
EDED (00000000)
SMI02 Connection(07051E88): ERROR OCCURRED: Object instance does not exist (8004
206B)
SMI01 Connection(07051E88): Create Message: (02065C10), initial size 0 bytes
SMI03 Connection(07051E88): Send Reply Message: (02065C10) sequenceNumber(229748
) Asynchronous. ... (00000000)
WSD08 Send: result = 0
SMI03 Connection(07051E88): Send Reply Message: (02065C10) sequenceNumber(229748
) Asynchronous. SUCCEEDED (00000000)
DPB Release DPB_SESSION_SERVICE(07055CE8) refCount(1)
SMI06 Connection(07051E88): Process request Message: (020601C8) serviceId(0), se
quenceNumber(0). SUCCEEDED (00000000)
WSD07 ReadHeader: Proto = 24576, Len = 112
SMI01 Connection(07051E88): Create Message: (020601C8), initial size 112 bytes
DPB AddRef DPB_SESSION_SERVICE(07055CE8) refCount(2)
DPB40 SessionId (07055C28): Handle Request: INVOKE(6), streamVer(0). SUCCEEDED (
00000000)
SMI02 Connection(07051E88): ERROR OCCURRED: Object instance does not exist (8004
206B)
SMI01 Connection(07051E88): Create Message: (02065C10), initial size 0 bytes
SMI03 Connection(07051E88): Send Reply Message: (02065C10) sequenceNumber(229753
) Asynchronous. ... (00000000)
WSD08 Send: result = 0
SMI03 Connection(07051E88): Send Reply Message: (02065C10) sequenceNumber(229753
) Asynchronous. SUCCEEDED (00000000)
DPB Release DPB_SESSION_SERVICE(07055CE8) refCount(1)
SMI06 Connection(07051E88): Process request Message: (020601C8) serviceId(0), se
quenceNumber(0). SUCCEEDED (00000000)
WSD07 ReadHeader: Proto = 24576, Len = 87
SMI01 Connection(07051E88): Create Message: (020601C8), initial size 87 bytes
DPB AddRef DPB_SESSION_SERVICE(07055CE8) refCount(2)
DPB40 SessionId (07055C28): Handle Request: DELETE_INSTANCE(4), streamVer(0). SU
CCEEDED (00000000)
SMI02 Connection(07051E88): ERROR OCCURRED: Object instance does not exist (8004
206B)
SMI01 Connection(07051E88): Create Message: (02065C10), initial size 0 bytes
SMI03 Connection(07051E88): Send Reply Message: (02065C10) sequenceNumber(229754
) Asynchronous. ... (00000000)
WSD08 Send: result = 0
SMI03 Connection(07051E88): Send Reply Message: (02065C10) sequenceNumber(229754
) Asynchronous. SUCCEEDED (00000000)
DPB Release DPB_SESSION_SERVICE(07055CE8) refCount(1)
SMI06 Connection(07051E88): Process request Message: (020601C8) serviceId(0), se
quenceNumber(0). SUCCEEDED (00000000)
WSD07 ReadHeader: Proto = 24576, Len = 83
SMI01 Connection(07051E88): Create Message: (020601C8), initial size 83 bytes
DPB AddRef DPB_SESSION_SERVICE(07055CE8) refCount(2)
DPB40 SessionId (07055C28): Handle Request: DISCONNECT(2), streamVer(0). SUCCEED
ED (00000000)
DPB AddRef DPB_SESSION_SERVICE(07055CE8) refCount(3)
DPB Release DPB_SESSION_SERVICE(07055CE8) refCount(2)
DPB21 Connection(07055CE8): ClientDisconnect: userId(micm\Administrator), connec
tString(), sessionId(07055C28). ... (00000000)
SMI06 Connection(07051E88): Process request Message: (020601C8) serviceId(0), se
quenceNumber(0). SUCCEEDED (00042137)
DPB21 Connection(07055CE8): ClientDisconnect: userId(micm\Administrator), connec
tString(), sessionId(07055C28). SUCCEEDED (00000000)
SMI01 Connection(07051E88): Create Message: (02065C10), initial size 0 bytes
SMI03 Connection(07051E88): Send Reply Message: (02065C10) sequenceNumber(229756
) Asynchronous. ... (00000000)
WSD08 Send: result = 0
SMI03 Connection(07051E88): Send Reply Message: (02065C10) sequenceNumber(229756
) Asynchronous. SUCCEEDED (00000000)
WSD07 ReadHeader: Proto = 24576, Len = 0
SMI08 Connection(07051E88): Disconnect: ... (00000000)
SMI01 Connection(07051E88): Create Message: (02065C10), initial size 0 bytes
WSD09 SendDisconnect: result = 0
WSD04 Release: RefCount for connection object = 2
SMI08 Connection(07051E88): Disconnect: SUCCEEDED (00000000)
DPB Release DPB_SESSION_SERVICE(07055CE8) refCount(1)
SMI Release SMI_CONNECTION(07051E88) refCount(2)
DPB56 Memory Proc Common : count(1657), total(233472), alloc(114492), free(1125
53)
SMI02 Connection(07051E88): ERROR OCCURRED: Distributed Communications Error: (
8004200D)
DPB Release DPB_SESSION_SERVICE(07055CE8) refCount(0)
SMI02 Connection(07051E88): ERROR OCCURRED: Distributed Communications Error: (
8004200D)
DPB Release DPB_Connection(07055E68) refCount(0)
WSD04 Release: RefCount for connection object = 1
SMI Release SMI_CONNECTION(07051E88) refCount(1)
WSD02 ~DPB_WINSOCK_CONNECTION: Error! socket hasn't been closed
SMI Release SMI_TRACE(07052038) refCount(4)
SMI Release SMI_CONNECTION(07051E88) refCount(0)
SMI Release SMI_TRACE(07052038) refCount(3)
SMI Release SMI_LISTENER(07052080) refCount(1)
SMI Release SMI_TRACE(07052038) refCount(2)
SMI AddRef SMI_LISTENER(07052080) refCount(2)
SMI AddRef SMI_TRACE(07052038) refCount(3)
WSD04 AddRef: RefCount for connection object = 1
SMI AddRef SMI_TRACE(07052038) refCount(4)
SMI AddRef SMI_TRACE(07052038) refCount(5)
SMI AddRef SMI_LISTENER(07052080) refCount(3)
SMI Release SMI_LISTENER(07052080) refCount(2)
SMI AddRef SMI_CONNECTION(07051E88) refCount(3)
SMI Release SMI_CONNECTION(07051E88) refCount(2)
SMI12 Listener (07052080): Open Connection: (07051E88). numConnections(3), SUCC
EEDED (00000000)
WSD04 AddRef: RefCount for connection object = 2
WSD07 ReadHeader: Proto = 24576, Len = 155
SMI01 Connection(07051E88): Create Message: (020601C8), initial size 155 bytes
DPB AddRef DPB_SESSION_SERVICE(07055C28) refCount(2)
DPB40 SessionId (00000000): Handle Request: CREATE_SESSION(1), streamVer(0). SUC
CEEDED (00000000)
DPB20 Connection(07051E88): ClientConnect : IUSR_MICAPWEB(MICAPWEB) userId(mic
m\Administrator), connectString(), sessionId(FFFFFFFF). ... (00000000)
SMI AddRef SMI_LISTENER(07052080) refCount(3)
SMI16 Listener (07052080): Create Session: (07055CE8). SUCCEEDED (00000000)
DPB41 : Use Session : sessionId(117791976). SUCCEEDED (000
00000)
SMI Release SMI_LISTENER(07052080) refCount(2)
SMI AddRef SMI_CONNECTION(07051E88) refCount(3)
DPB AddRef DPB_Connection(070563C8) refCount(1)
DPB AddRef DPB_SESSION_SERVICE(07055C28) refCount(3)
SMI01 Connection(07051E88): Create Message: (0FF00AF8), initial size 0 bytes
DPB20 Connection(07051E88): ClientConnect : IUSR_MICAPWEB(MICAPWEB) userId(mic
m\Administrator), connectString(), sessionId(07055CE8). SUCCEEDED (00000000)
SMI03 Connection(07051E88): Send Reply Message: (0FF00AF8) sequenceNumber(230708
) Asynchronous. ... (00000000)
DPB Release DPB_SESSION_SERVICE(07055C28) refCount(2)
WSD08 Send: result = 0
SMI06 Connection(07051E88): Process request Message: (020601C8) serviceId(0), se
quenceNumber(0). SUCCEEDED (00000000)
SMI03 Connection(07051E88): Send Reply Message: (0FF00AF8) sequenceNumber(230708
) Asynchronous. SUCCEEDED (00000000)
WSD07 ReadHeader: Proto = 24576, Len = 97
SMI01 Connection(07051E88): Create Message: (020601C8), initial size 97 bytes
DPB55 Memory Session : (07055C28) count(985), total(356352), alloc(213150),
free(133537)
DPB56 Memory Proc Common : count(1396), total(233472), alloc(85964), free(14108
9)
DPB Release DPB_SESSION_SERVICE(07055C28) refCount(1)
DPB AddRef DPB_SESSION_SERVICE(07055C28) refCount(2)
DPB40 SessionId (07055CE8): Handle Request: CREATE_INSTANCE(3), streamVer(0). SU
CCEEDED (00000000)
DPB AddRef DPB_SESSION_SERVICE(07055C28) refCount(3)
DPB43 SessionId (07055CE8): Create Object : className(jdpb_24x7), instanceId(000
00000). ... (00000000)
DPB Release DPB_SESSION_SERVICE(07055C28) refCount(2)
SMI01 Connection(07051E88): Create Message: (0FF00A78), initial size 0 bytes
SMI06 Connection(07051E88): Process request Message: (020601C8) serviceId(0), se
quenceNumber(0). SUCCEEDED (00000000)
SMI03 Connection(07051E88): Send Reply Message: (0FF00A78) sequenceNumber(230711
) Asynchronous. ... (00000000)
WSD08 Send: result = 0
SMI03 Connection(07051E88): Send Reply Message: (0FF00A78) sequenceNumber(230711
) Asynchronous. SUCCEEDED (00000000)
WSD07 ReadHeader: Proto = 24576, Len = 169
DPB43 SessionId (07055CE8): Create Object : className(jdpb_24x7), instanceId(000
38536). SUCCEEDED (00000000)
SMI01 Connection(07051E88): Create Message: (0FF00A78), initial size 169 bytes
DPB55 Memory Session : (07055C28) count(996), total(356352), alloc(213523),
free(133161)
DPB56 Memory Proc Common : count(1404), total(233472), alloc(90379), free(13667
2)
DPB Release DPB_SESSION_SERVICE(07055C28) refCount(1)
DPB AddRef DPB_SESSION_SERVICE(07055C28) refCount(2)
DPB40 SessionId (07055CE8): Handle Request: INVOKE(6), streamVer(0). SUCCEEDED (
00000000)
SMI02 Connection(07051E88): ERROR OCCURRED: Object instance does not exist (8004
206B)
SMI01 Connection(07051E88): Create Message: (020601C8), initial size 0 bytes
SMI03 Connection(07051E88): Send Reply Message: (020601C8) sequenceNumber(230716
) Asynchronous. ... (00000000)
WSD08 Send: result = 0
SMI03 Connection(07051E88): Send Reply Message: (020601C8) sequenceNumber(230716
) Asynchronous. SUCCEEDED (00000000)
DPB Release DPB_SESSION_SERVICE(07055C28) refCount(1)
SMI06 Connection(07051E88): Process request Message: (0FF00A78) serviceId(0), se
quenceNumber(0). SUCCEEDED (00000000)
WSD07 ReadHeader: Proto = 24576, Len = 112
SMI01 Connection(07051E88): Create Message: (0FF00A78), initial size 112 bytes
DPB AddRef DPB_SESSION_SERVICE(07055C28) refCount(2)
DPB40 SessionId (07055CE8): Handle Request: GET_PROPERTY(8), streamVer(0). SUCCE
EDED (00000000)
SMI02 Connection(07051E88): ERROR OCCURRED: Object instance does not exist (8004
206B)
SMI01 Connection(07051E88): Create Message: (020601C8), initial size 0 bytes
SMI03 Connection(07051E88): Send Reply Message: (020601C8) sequenceNumber(230717
) Asynchronous. ... (00000000)
WSD08 Send: result = 0
SMI03 Connection(07051E88): Send Reply Message: (020601C8) sequenceNumber(230717
) Asynchronous. SUCCEEDED (00000000)
DPB Release DPB_SESSION_SERVICE(07055C28) refCount(1)
SMI06 Connection(07051E88): Process request Message: (0FF00A78) serviceId(0), se
quenceNumber(0). SUCCEEDED (00000000)
WSD07 ReadHeader: Proto = 24576, Len = 112
SMI01 Connection(07051E88): Create Message: (0FF00A78), initial size 112 bytes
DPB AddRef DPB_SESSION_SERVICE(07055C28) refCount(2)
DPB40 SessionId (07055CE8): Handle Request: INVOKE(6), streamVer(0). SUCCEEDED (
00000000)
SMI02 Connection(07051E88): ERROR OCCURRED: Object instance does not exist (8004
206B)
SMI01 Connection(07051E88): Create Message: (020601C8), initial size 0 bytes
SMI03 Connection(07051E88): Send Reply Message: (020601C8) sequenceNumber(230718
) Asynchronous. ... (00000000)
WSD08 Send: result = 0
SMI03 Connection(07051E88): Send Reply Message: (020601C8) sequenceNumber(230718
) Asynchronous. SUCCEEDED (00000000)
DPB Release DPB_SESSION_SERVICE(07055C28) refCount(1)
SMI06 Connection(07051E88): Process request Message: (0FF00A78) serviceId(0), se
quenceNumber(0). SUCCEEDED (00000000)
WSD07 ReadHeader: Proto = 24576, Len = 87
SMI01 Connection(07051E88): Create Message: (0FF00A78), initial size 87 bytes
DPB AddRef DPB_SESSION_SERVICE(07055C28) refCount(2)
DPB40 SessionId (07055CE8): Handle Request: DELETE_INSTANCE(4), streamVer(0). SU
CCEEDED (00000000)
SMI02 Connection(07051E88): ERROR OCCURRED: Object instance does not exist (8004
206B)
SMI01 Connection(07051E88): Create Message: (020601C8), initial size 0 bytes
SMI03 Connection(07051E88): Send Reply Message: (020601C8) sequenceNumber(230719
) Asynchronous. ... (00000000)
WSD08 Send: result = 0
SMI03 Connection(07051E88): Send Reply Message: (020601C8) sequenceNumber(230719
) Asynchronous. SUCCEEDED (00000000)
DPB Release DPB_SESSION_SERVICE(07055C28) refCount(1)
SMI06 Connection(07051E88): Process request Message: (0FF00A78) serviceId(0), se
quenceNumber(0). SUCCEEDED (00000000)
WSD07 ReadHeader: Proto = 24576, Len = 83
SMI01 Connection(07051E88): Create Message: (0FF00A78), initial size 83 bytes
DPB AddRef DPB_SESSION_SERVICE(07055C28) refCount(2)
DPB40 SessionId (07055CE8): Handle Request: DISCONNECT(2), streamVer(0). SUCCEED
ED (00000000)
DPB AddRef DPB_SESSION_SERVICE(07055C28) refCount(3)
DPB Release DPB_SESSION_SERVICE(07055C28) refCount(2)
DPB21 Connection(07055C28): ClientDisconnect: userId(micm\Administrator), connec
tString(), sessionId(07055CE8). ... (00000000)
SMI06 Connection(07051E88): Process request Message: (0FF00A78) serviceId(0), se
quenceNumber(0). SUCCEEDED (00042137)
DPB21 Connection(07055C28): ClientDisconnect: userId(micm\Administrator), connec
tString(), sessionId(07055CE8). SUCCEEDED (00000000)
SMI01 Connection(07051E88): Create Message: (020601C8), initial size 0 bytes
SMI03 Connection(07051E88): Send Reply Message: (020601C8) sequenceNumber(230725
) Asynchronous. ... (00000000)
WSD08 Send: result = 0
WSD07 ReadHeader: Proto = 24576, Len = 0
SMI03 Connection(07051E88): Send Reply Message: (020601C8) sequenceNumber(230725
) Asynchronous. SUCCEEDED (00000000)
SMI01 Connection(07051E88): Create Message: (0FF00AF8), initial size 0 bytes
SMI08 Connection(07051E88): Disconnect: ... (00000000)
WSD09 SendDisconnect: result = 0
WSD04 Release: RefCount for connection object = 2
SMI08 Connection(07051E88): Disconnect: SUCCEEDED (00000000)
SMI02 Connection(07051E88): ERROR OCCURRED: Distributed Communications Error: (
8004200D)
DPB Release DPB_SESSION_SERVICE(07055C28) refCount(1)
SMI02 Connection(07051E88): ERROR OCCURRED: Distributed Communications Error: (
8004200D)
SMI Release SMI_CONNECTION(07051E88) refCount(2)
WSD04 Release: RefCount for connection object = 1
DPB56 Memory Proc Common : count(1393), total(233472), alloc(85935), free(14111
8)
WSD02 ~DPB_WINSOCK_CONNECTION: Error! socket hasn't been closed
DPB Release DPB_SESSION_SERVICE(07055C28) refCount(0)
SMI Release SMI_CONNECTION(07051E88) refCount(1)
DPB Release DPB_Connection(070563C8) refCount(0)
SMI Release SMI_TRACE(07052038) refCount(4)
SMI Release SMI_CONNECTION(07051E88) refCount(0)
SMI Release SMI_TRACE(07052038) refCount(3)
SMI Release SMI_LISTENER(07052080) refCount(1)
SMI Release SMI_TRACE(07052038) refCount(2)
Thu Oct 08, 2009 12:50 pm View user's profile Send private message
SysOp
Site Admin


Joined: 26 Nov 2006
Posts: 7952

Post Reply with quote
This message indicates that either your web session has expired or the server connection has aborted because of some network issue. I suspect the first. The session duration is controlled in web server settings. I think the default is like 90 minutes or so.
Thu Oct 08, 2009 2:05 pm View user's profile Send private message
Loril



Joined: 21 Feb 2007
Posts: 82

Post Reply with quote
Are you talking about the connection timeout setting? We currently have it set to 120 seconds with Enable HTTP Keep-Alives option checked. Here's a screenshot of another setting that may pertain to this. Does it look right?

Thu Oct 08, 2009 8:11 pm View user's profile Send private message
SysOp
Site Admin


Joined: 26 Nov 2006
Posts: 7952

Post Reply with quote
You may need to adjust the "Session timeout" property for the application, not for ASP.NET

Please see this article for more info
http://natttech.blogspot.com/2008/12/lets-talk-about-iis-settting-timeout.html
Thu Oct 08, 2009 9:20 pm View user's profile Send private message
Loril



Joined: 21 Feb 2007
Posts: 82

Post Reply with quote
The application session timeout is set to the default of 20 minutes. Should it be more or less? What should I set it to? Thanks.
Mon Oct 12, 2009 1:26 pm View user's profile Send private message
Loril



Joined: 21 Feb 2007
Posts: 82

Post Reply with quote
Any updates? Thanks.
Fri Oct 16, 2009 7:40 pm View user's profile Send private message
SysOp
Site Admin


Joined: 26 Nov 2006
Posts: 7952

Post Reply with quote
Quote:
Everything works fine for several hours and then all of a sudden


Quote:
application session timeout is set to the default of 20 minutes



I guess you have answered your own question. Did I get it wrong?[/quote]
Sat Oct 17, 2009 11:23 am View user's profile Send private message
Loril



Joined: 21 Feb 2007
Posts: 82

Post Reply with quote
The problem still exists. Perhaps I should explain more in detail.

I use the web console for several minutes, leaves the web page alone for a couple of hours, then comes back and logs off from web console. After 5 minutes, I tried to log in again and I receive the "server invalid reply" message.

What setting should I change so that I don't receive the error? Thanks.
Tue Oct 20, 2009 12:14 pm View user's profile Send private message
SysOp
Site Admin


Joined: 26 Nov 2006
Posts: 7952

Post Reply with quote
This could be an old response from the expired session. Does this error appear only once and you can dismiss it and login after that, or it actually prevents you from logging in?

When happens when you login using a different browser tab? A different browser window? Same error?
Tue Oct 20, 2009 4:33 pm View user's profile Send private message
Loril



Joined: 21 Feb 2007
Posts: 82

Post Reply with quote
I thought that's what's happening also so I closed the browser and opened up another session. The error still occurred. I even tried to open web console with a different browser (Firefox as opposed to IE) but the error still occurred. I find that if I either wait another hour or restart 24x7 scheduler service, then I would be able to log in to web console. Hope that helps.
Wed Oct 21, 2009 4:35 pm View user's profile Send private message
SysOp
Site Admin


Joined: 26 Nov 2006
Posts: 7952

Post Reply with quote
This is totally weird.


Please try changing your browser settings and in the Settings for browsing / temporary files, set it to Always Refresh. Please see the following image for details




Thu Oct 22, 2009 5:00 pm View user's profile Send private message
Loril



Joined: 21 Feb 2007
Posts: 82

Post Reply with quote
That is the default of my IE settings so no change is needed. Any other ideas? Thanks.
Fri Oct 23, 2009 2:17 pm View user's profile Send private message
Loril



Joined: 21 Feb 2007
Posts: 82

Post Reply with quote
Actually, I take back the part about waiting another hour and the issue disappears. I haven't logged on to the web console for almost a week now and just tried it. I still received the server reply is invalid error. Here's the trace log:

DPB Release DPB_SESSION_SERVICE(07055C28) refCount(1)
SMI06 Connection(07051E88): Process request Message: (0FF00A08) serviceId(0), se
quenceNumber(0). SUCCEEDED (00000000)
WSD07 ReadHeader: Proto = 24576, Len = 112
SMI01 Connection(07051E88): Create Message: (0FF00A08), initial size 112 bytes
DPB AddRef DPB_SESSION_SERVICE(07055C28) refCount(2)
DPB40 SessionId (07055CE8): Handle Request: INVOKE(6), streamVer(0). SUCCEEDED (
00000000)
SMI02 Connection(07051E88): ERROR OCCURRED: Object instance does not exist (8004
206B)
SMI01 Connection(07051E88): Create Message: (02065C10), initial size 0 bytes
SMI03 Connection(07051E88): Send Reply Message: (02065C10) sequenceNumber(549618
4) Asynchronous. ... (00000000)
WSD08 Send: result = 0
SMI03 Connection(07051E88): Send Reply Message: (02065C10) sequenceNumber(549618
4) Asynchronous. SUCCEEDED (00000000)
DPB Release DPB_SESSION_SERVICE(07055C28) refCount(1)
SMI06 Connection(07051E88): Process request Message: (0FF00A08) serviceId(0), se
quenceNumber(0). SUCCEEDED (00000000)
WSD07 ReadHeader: Proto = 24576, Len = 87
SMI01 Connection(07051E88): Create Message: (0FF00A08), initial size 87 bytes
DPB AddRef DPB_SESSION_SERVICE(07055C28) refCount(2)
DPB40 SessionId (07055CE8): Handle Request: DELETE_INSTANCE(4), streamVer(0). SU
CCEEDED (00000000)
SMI02 Connection(07051E88): ERROR OCCURRED: Object instance does not exist (8004
206B)
SMI01 Connection(07051E88): Create Message: (02065C10), initial size 0 bytes
SMI03 Connection(07051E88): Send Reply Message: (02065C10) sequenceNumber(549618
5) Asynchronous. ... (00000000)
WSD08 Send: result = 0
SMI03 Connection(07051E88): Send Reply Message: (02065C10) sequenceNumber(549618
5) Asynchronous. SUCCEEDED (00000000)
DPB Release DPB_SESSION_SERVICE(07055C28) refCount(1)
SMI06 Connection(07051E88): Process request Message: (0FF00A08) serviceId(0), se
quenceNumber(0). SUCCEEDED (00000000)
WSD07 ReadHeader: Proto = 24576, Len = 83
SMI01 Connection(07051E88): Create Message: (0FF00A08), initial size 83 bytes
DPB AddRef DPB_SESSION_SERVICE(07055C28) refCount(2)
DPB40 SessionId (07055CE8): Handle Request: DISCONNECT(2), streamVer(0). SUCCEED
ED (00000000)
DPB AddRef DPB_SESSION_SERVICE(07055C28) refCount(3)
DPB Release DPB_SESSION_SERVICE(07055C28) refCount(2)
DPB21 Connection(07055C28): ClientDisconnect: userId(micm\Administrator), connec
tString(), sessionId(07055CE8). ... (00000000)
SMI06 Connection(07051E88): Process request Message: (0FF00A08) serviceId(0), se
quenceNumber(0). SUCCEEDED (00042137)
DPB21 Connection(07055C28): ClientDisconnect: userId(micm\Administrator), connec
tString(), sessionId(07055CE8). SUCCEEDED (00000000)
SMI01 Connection(07051E88): Create Message: (02065C10), initial size 0 bytes
SMI03 Connection(07051E88): Send Reply Message: (02065C10) sequenceNumber(549618
7) Asynchronous. ... (00000000)
WSD08 Send: result = 0
WSD07 ReadHeader: Proto = 24576, Len = 0
SMI03 Connection(07051E88): Send Reply Message: (02065C10) sequenceNumber(549618
7) Asynchronous. SUCCEEDED (00000000)
SMI01 Connection(07051E88): Create Message: (020601C8), initial size 0 bytes
SMI08 Connection(07051E88): Disconnect: ... (00000000)
WSD09 SendDisconnect: result = 0
WSD04 Release: RefCount for connection object = 2
SMI08 Connection(07051E88): Disconnect: SUCCEEDED (00000000)
SMI02 Connection(07051E88): ERROR OCCURRED: Distributed Communications Error: (
8004200D)
DPB Release DPB_SESSION_SERVICE(07055C28) refCount(1)
SMI02 Connection(07051E88): ERROR OCCURRED: Distributed Communications Error: (
8004200D)
SMI Release SMI_CONNECTION(07051E88) refCount(2)
WSD04 Release: RefCount for connection object = 1
DPB56 Memory Proc Common : count(1414), total(233472), alloc(86810), free(14023
4)
WSD02 ~DPB_WINSOCK_CONNECTION: Error! socket hasn't been closed
DPB Release DPB_SESSION_SERVICE(07055C28) refCount(0)
SMI Release SMI_CONNECTION(07051E88) refCount(1)
DPB Release DPB_Connection(070563C8) refCount(0)
SMI Release SMI_TRACE(07052038) refCount(4)
SMI Release SMI_CONNECTION(07051E88) refCount(0)
SMI Release SMI_TRACE(07052038) refCount(3)
SMI Release SMI_LISTENER(07052080) refCount(1)
SMI Release SMI_TRACE(07052038) refCount(2)
Fri Oct 23, 2009 2:21 pm View user's profile Send private message
SysOp
Site Admin


Joined: 26 Nov 2006
Posts: 7952

Post Reply with quote
This is something with the server config. The error message "Error! socket hasn't been closed " indicates that some objects are hanging in the web server memory. When the session expires the web server is supposed to destroy all the objects for that session.

I will look into this.
Fri Oct 23, 2009 3:05 pm View user's profile Send private message
Loril



Joined: 21 Feb 2007
Posts: 82

Post Reply with quote
Any update on this? Thanks.
Fri Oct 30, 2009 3:01 pm View user's profile Send private message
Display posts from previous:    
Reply to topic    SoftTree Technologies Forum Index » 24x7 Scheduler, Event Server, Automation Suite All times are GMT - 4 Hours
Goto page 1, 2  Next
Page 1 of 2

 
Jump to: 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


 

 

Powered by phpBB © 2001, 2005 phpBB Group
Design by Freestyle XL / Flowers Online.