• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

java.sql.SQLException: ORA-00028: your session has been killed

 
Annasaheb Sunthe
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,
I am getting "java.sql.SQLException: ORA-00028: your session has been killed" error while executing a stored procedure using Oracle Thin driver Oracle. The application is running on App server WebLogic 9.2.
According to oracle documentation the reason for this error is that a privilaged user has killed the session. But I don't think that has happened. Is it issue with WebLogic connection pool? or issue with oracle driver or oracle 10g db.
Any help will be appreciated.
 
Paul Sturrock
Bartender
Posts: 10336
Eclipse IDE Hibernate Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This can only happen when an admin user kills your session. They may be explicitly doing this, or implicitly doing this by setting limits in your profile. Speak to your Oracle admin.
 
Annasaheb Sunthe
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for quick reply Paul,

"or implicitly doing this by setting limits in your profile" is it session time out limit?

Actual setup is like this:
Application is deployed on TWO weblogic domains (with one managed server in each domain), both pointing to same database. Connection pool on both weblogic domains configured with same user credentials. I run cron job on first weblogic server, which inturn calls stored procedure through java code. After completing cron job, we are firing browser requests on both weblogic servers. Request on first weblogic serves correctly, while request on second server fails with java.sql.SQLException: ORA-00028 error.

appreciate your help.
 
Paul Sturrock
Bartender
Posts: 10336
Eclipse IDE Hibernate Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

"or implicitly doing this by setting limits in your profile" is it session time out limit?

Could be. Your DBA could set up almost any trigger they like to do this in the profile your account uses. Speak to them.

 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic