SourceForge.net
2003-08-29 13:35:14 UTC
Bugs item #797284, was opened at 2003-08-29 23:35
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=797284&group_id=54559
Category: transport
Group: v0.7.6-rc1
Status: Open
Resolution: None
Priority: 5
Submitted By: Tim Anderson (tanderson)
Assigned to: Tim Anderson (tanderson)
Summary: http connector: Failed to process request
Initial Comment:
After a period of several hours, the following exception is
being thrown:
Failed to process request:
enableAsynchronousDelivery: session not found
Closer inspection indicates it is because
HttpJmsSessionSender has been failed to send a
message to the client, and has closed the session.
The send has failed because a socket cached by
HttpJmsClientServlet is no longer valid as the original
client session has been closed, and the associated port
is now being used used by a new client sesssion.
To fix this, the cached sockets need to be closed when
the corresponding client session is closed.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=797284&group_id=54559
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=797284&group_id=54559
Category: transport
Group: v0.7.6-rc1
Status: Open
Resolution: None
Priority: 5
Submitted By: Tim Anderson (tanderson)
Assigned to: Tim Anderson (tanderson)
Summary: http connector: Failed to process request
Initial Comment:
After a period of several hours, the following exception is
being thrown:
Failed to process request:
enableAsynchronousDelivery: session not found
Closer inspection indicates it is because
HttpJmsSessionSender has been failed to send a
message to the client, and has closed the session.
The send has failed because a socket cached by
HttpJmsClientServlet is no longer valid as the original
client session has been closed, and the associated port
is now being used used by a new client sesssion.
To fix this, the cached sockets need to be closed when
the corresponding client session is closed.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=797284&group_id=54559