This week's book giveaway is in the Performance forum.
We're giving away four copies of The Java Performance Companion and have Charlie Hunt, Monica Beckwith, Poonam Parhar, & Bengt Rutisson on-line!
See this thread for details.
Win a copy of The Java Performance Companion this week in the Performance forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

timeout problem

 
Jun Hong
Ranch Hand
Posts: 181
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi guys,
I have a java client accessing stateless session bean. If the processing time on session bean side is longer than 2 hours, my client cannot get the reponse from application server. The Exception is related to session table. It is not CORBA request timeout(in sas.client.props) I know it. From logging, I know session bean finished processing in 2 hours and the when the client got the response from application server Exception happened. Does anyone have any idea what happened? By the way, it is not related to token timeout (security).
 
Jun Hong
Ranch Hand
Posts: 181
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Here is the Exception:
29> [2002-06-12 20:37:35.844], [ServerID: -1], [VaultImpl.get_security_context]:
JSAS0170E: Null session handle in session table. Check to see if a server process has terminated just prior to re
ceiving these errors. If a process has terminated, restart the process and retry the operation. Verify that the client
userid/password is valid. If the login fails, the session will be deleted on the client side and the credentials will
be marked invalid. If a retry occurs, you will likely see this error. Restart the client program after verifying the l
ogin info. If the errors persist, contact support for assistance.
30> [2002-06-12 20:37:35.872], [ServerID: -1], [SecureInvocationInterceptorImpl.receive_response_message]:
JSAS0150E: Unable to find session in session table. Retry the operation. If the error repeats itself, restart th
e client program. Check the client properties to ensure the login information is correct. If after restarting the clie
nt and server programs, you still are unable to eliminate the error, contact support for assistance.
32> [2002-06-12 20:37:35.888], [ServerID: -1], [VaultImpl.get_security_context]:
JSAS0170E: Null session handle in session table. Check to see if a server process has terminated just prior to re
ceiving these errors. If a process has terminated, restart the process and retry the operation. Verify that the client
userid/password is valid. If the login fails, the session will be deleted on the client side and the credentials will
be marked invalid. If a retry occurs, you will likely see this error. Restart the client program after verifying the l
ogin info. If the errors persist, contact support for assistance.
Exception thrown in getDQEResultsInBinary: java.rmi.RemoteException: CORBA INTERNAL 0 No; nested exception is:
org.omg.CORBA.INTERNAL: Unexpected Java Exception: org.omg.CORBA.INTERNAL: Unexpected Java Exception: org.omg.CO
RBA.NO_PERMISSION: Failed mutual authentication handshake. Session does not exist in the session table. minor code: 0
completed: No minor code: 0 completed: No minor code: 0 completed: No
49> [2002-06-13 00:29:08.835], [ServerID: -1], [VaultImpl.get_security_context]:
JSAS0170E: Null session handle in session table. Check to see if a server process has terminated just prior to re
ceiving these errors. If a process has terminated, restart the process and retry the operation. Verify that the client
userid/password is valid. If the login fails, the session will be deleted on the client side and the credentials will
be marked invalid. If a retry occurs, you will likely see this error. Restart the client program after verifying the l
ogin info. If the errors persist, contact support for assistance.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic