Tomcat 5.5 Session lookup exception

Hi, could someone please make my newbie day!!
using Tomcat 5.5.14 and the default JDK is JSE 1.5
I wanted to try send email from my EmailServlet,
but since JSE 1.5 does not provide the javax.mail and to be able to write the code needed to send an email you have to to include the Mail.jar provided in my libraries to get " javax.mail , javax.mail.internet and javax.mail.event " etc.
I configured the web.xml, context.xml as followed and placed the the two jar�s " mail.jar and activation.jar " in the Tomcat /common/lib
but here is the problem, when deploying the webapplication, the Mail.jar are copied to the webapplication " web/lib " map, since i included it to get the API of javax.mail.. this would reslut in not following the Tomcat configuration process ( do not place the same jar in the application/web/lib and the server common/lib ).
Iam using James as Smtpserver.
Getting an exception when reaching the lookup for session in my servlet
Context initCtx = new InitialContext();
Context envCtx = (Context) initCtx.lookup("java:comp/env");
--> Session session = (Session) envCtx.lookup("mail/Session");
the Exception does not tell me a jack
ExceptionMessage =( javax.mail.Session )
ExceptionStacktrace = ( [Ljava.lang.StackTraceElement;@1c71508 )
I have a feeling of doing something wrong by having the Mail.jar placed in those meansend dirctories..
Help me out please

Hi
I also have a similar problem?? whom did u seek help from? can you give me his email...
I have tomcat 5.5.15 and jdk 1.5 that runs a jsp page to send emails..but i am getting the
java.lang.NoClassDefFoundError: javax/mail/MessagingException
i have read your mail. But why is this tomcat 5.5 not distributing mail.jar and activation.jar which are required by javaMail!!
and what changes i need to make in server.xml??
Also, i am trying to download the mail.jar from sun..but it's taking me to FATAL EXCEPTION page...
I need to fix this by end of this day..I need HELP SO DESPERATELY...PLZ HLP..me
Also for more detail refer this posting that i posted in jsp forum..
http://forum.java.sun.com/thread.jspa?threadID=708835&tstart=0
Thanks
Sri

Similar Messages

Handling PI 7.1 RFC Lookup Exception in Graphical Mapping

Dear Experts,
I would like to know the better way of handling PI 7.1 - RFC Lookup Exception in Graphical Mapping without using BPM. Say I perform a RFC Lookup from PI 7.1 Graphical Mapping and it fails due to RFC server down. In this case I suppose the RFC exception would be returned as response to the mapping? But, am really not sure how this response (RFC Exception) could be effectively used. Please clarify.
Thanks,
Hussain.
Edited by: HussainShaik on Oct 26, 2009 8:24 AM

Hi Hussain,
I am not sure if I understood you query completely.
IF the RFC look up raised some exception then how this is going to impact your interface will depend your mapping (which you did in ESR)
(the following is adopted from help.sap,com)
If you handled exceptions by selecting Use Exceptions checkbox in the function properties of the standard function, the mapping editor adds an additional parameter in red (the bottommost return parameter) to the standard function in the data-flow editor. If you do not assign a target field to this return parameter, ignore the RFC exceptions (the message mapping is not terminated at runtime). Otherwise the mapping runtime transfers the exception as an XML structure and it can then be evaluated in a user-defined function, for example. If there is no exception, the mapping runtime transfers an empty context.
If you have not selected the Use Exceptions checkbox, the mapping runtime terminates the message mapping if an exception occurs during the RFC lookup.
Is this you are looking here?
Also check this thread and help.sap site
Re: SAP-PI - RFC call to SAP backend system
http://help.sap.com/saphelp_nwpi71/helpdata/en/33/1ec6ced273493a993a80c2301c03da/content.htm
Regards
Suraj

Use of error page resulting in could not deserialize session data exception

          We have recently converted classes that store objects in the HTTP Session to implement
          serializable.
          Our application uses an error page set up in our web.xml for 500 errors.
          It also uses filters.
          When our application throws an exception and allows the server to handle it
          via the error page setup, we end up with the exception we threw, plus a number
          of
          "Could not deserialize session data" exceptions in the stack trace.
          In general, the exceptions can be traced to lines in code that attempt to reference
          one of our "serializable" session objects to get user info for logging purposes.
          Problem is, other applications that do not use error pages to handle exceptions
          do not throw these types of exceptions in the wl-domain.log and they use the same
          classes.
          Does anyone know why this happens when using error pages and what we need to do
          to correct it?
          We are using Weblogic 8.1sp2.
          Thanks!!
          Example of the stack trace messages:
          ####<May 5, 2004 2:52:17 PM EDT> <Error> <HTTP Session> <machinexyz> <cgServer>
          <ExecuteThread: '11' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-100028>
          <Could not deserialize session data.
          java.io.NotSerializableException: weblogic.servlet.internal.FilterConfigImpl
               at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
               at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1330)
               at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1302)
               at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1245)
               at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
               at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
               at weblogic.servlet.internal.AttributeWrapper.convertObjectToBytes(AttributeWrapper.java:136)
               at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:112)
               at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:69)
               at weblogic.servlet.internal.session.SessionData.getAttribute(SessionData.java:431)
               at doh.stuff.OurFilter.doFilter(OurFilter.java:67)
               at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
               at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:305)
               at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:523)
               at weblogic.servlet.internal.WebAppServletContext.handleException(WebAppServletContext.java:3908)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3683)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          >
          ####<May 5, 2004 2:52:17 PM EDT> <Error> <HTTP Session> <machinexyz> <cgServer>
          <ExecuteThread: '11' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-100028>
          <Could not deserialize session data.
          java.io.NotSerializableException: java.util.Vector$1
               at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
               at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1330)
               at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1302)
               at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1245)
               at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
               at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
               at weblogic.servlet.internal.AttributeWrapper.convertObjectToBytes(AttributeWrapper.java:136)
               at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:112)
               at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:69)
               at weblogic.servlet.internal.session.SessionData.getAttribute(SessionData.java:431)
               at doh.stuff.OurHTML.<init>(OurHTML.java:57)
               at doh.stuff.OurFilter.startLog4j(OurFilter.java:513)
               at doh.stuff.OurFilter.doFilter(OurFilter.java:75)
               at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
               at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:305)
               at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:523)
               at weblogic.servlet.internal.WebAppServletContext.handleException(WebAppServletContext.java:3908)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3683)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          >


          We have recently converted classes that store objects in the HTTP Session to implement
          serializable.
          Our application uses an error page set up in our web.xml for 500 errors.
          It also uses filters.
          When our application throws an exception and allows the server to handle it
          via the error page setup, we end up with the exception we threw, plus a number
          of
          "Could not deserialize session data" exceptions in the stack trace.
          In general, the exceptions can be traced to lines in code that attempt to reference
          one of our "serializable" session objects to get user info for logging purposes.
          Problem is, other applications that do not use error pages to handle exceptions
          do not throw these types of exceptions in the wl-domain.log and they use the same
          classes.
          Does anyone know why this happens when using error pages and what we need to do
          to correct it?
          We are using Weblogic 8.1sp2.
          Thanks!!
          Example of the stack trace messages:
          ####<May 5, 2004 2:52:17 PM EDT> <Error> <HTTP Session> <machinexyz> <cgServer>
          <ExecuteThread: '11' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-100028>
          <Could not deserialize session data.
          java.io.NotSerializableException: weblogic.servlet.internal.FilterConfigImpl
               at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
               at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1330)
               at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1302)
               at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1245)
               at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
               at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
               at weblogic.servlet.internal.AttributeWrapper.convertObjectToBytes(AttributeWrapper.java:136)
               at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:112)
               at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:69)
               at weblogic.servlet.internal.session.SessionData.getAttribute(SessionData.java:431)
               at doh.stuff.OurFilter.doFilter(OurFilter.java:67)
               at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
               at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:305)
               at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:523)
               at weblogic.servlet.internal.WebAppServletContext.handleException(WebAppServletContext.java:3908)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3683)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          >
          ####<May 5, 2004 2:52:17 PM EDT> <Error> <HTTP Session> <machinexyz> <cgServer>
          <ExecuteThread: '11' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-100028>
          <Could not deserialize session data.
          java.io.NotSerializableException: java.util.Vector$1
               at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
               at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1330)
               at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1302)
               at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1245)
               at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
               at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
               at weblogic.servlet.internal.AttributeWrapper.convertObjectToBytes(AttributeWrapper.java:136)
               at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:112)
               at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:69)
               at weblogic.servlet.internal.session.SessionData.getAttribute(SessionData.java:431)
               at doh.stuff.OurHTML.<init>(OurHTML.java:57)
               at doh.stuff.OurFilter.startLog4j(OurFilter.java:513)
               at doh.stuff.OurFilter.doFilter(OurFilter.java:75)
               at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
               at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:305)
               at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:523)
               at weblogic.servlet.internal.WebAppServletContext.handleException(WebAppServletContext.java:3908)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3683)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          >

Cluster enviornment i get session failover exception

Hi All,
In cluster enviornment i get session failover exception comes when one of my node is down .
How can i inform all manage server at the time of creation of session object in cluster enviornment.
Thanks in advance,
Sumit Bhasin

.

Session expired exception

Hi,
How/Where to catch session expired exception in web dynpro? The following message is thrown when I click on the ui in portal.
com.sap.tc.webdynpro.clientserver.session.SessionExpiredLongJumpException: Application session has expired: No application session with ID WGM2Pq0FW1NipV5Lp6LduwPdwvcMglH6QrYGsOlwpQ/pcd:portal_content/com.sap.pct/platform_add_ons/com.sap.caf.eu.gp.folders.gp/com.sap.caf.eu.gp.roles.runtime/com.sap.caf.eu.gp.worksets.runtime/com.sap.caf.eu.gp.pages.procinstance2/sap.com/cafeugpuirt/Runtime/base/ exists. Hint: A follow-up request was sent to Web Dynpro, but no corresponding session was found under the existing sessions. Reasons: a) Session has expired; b) Web Dynpro is called with incorrect session parameters; c) Application session has been destroyed due to proceeding exception. Please restart the application.
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doPostprocessing(ClientSession.java:781)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:241)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:228)
     at .....
Thanks.
Regards,
Fui Voon

Hi,
You can try this to retrieve more user friendly error message.
e.getNestedLocalizedMessage()
For more details on handle exception, you can refer following URL.
http://help.sap.com/javadocs/NW04S/current/wd/index-files/index-23.html
Look for :
WDSessionExpiredException(String)
WDSessionExpiredException(String, Throwable)
WDSessionExpiredException(Throwable)
WDSessionExpiredException(String, Object[])
WDSessionExpiredException()
WDSessionIdentificationException(String)
WDSessionIdentificationException(String, Throwable)
WDSessionIdentificationException(Throwable)
WDSessionIdentificationException(String, Object[])
Regards,
Eric

How to let tomcat destroy a session

how to let tomcat destroy a session???

BalusC wrote:
It works perfectly. Your interpretation is just wrong.
In the future please respond to active topics only and don't resurrect old topics.Please tell how my interpretation is wrong.
If you don't people to reply to old threads, please lock them.
And if you want to help, I'm actually waiting for your reply on [Session invalidate() in Tomcat 6|http://forum.java.sun.com/thread.jspa?threadID=5300401&tstart=15].

Tomcat and JavaMail Sessions problem

I'm using Tomcat (with struts). I've configured my web application in server.xml to manage JavaMail Sessions:
          <Resource name="mail/Session" auth="Container" type="javax.mail.Session"/>
          <ResourceParams name="mail/Session">
               <parameter>
                    <name>mail.smtp.host</name>
                    <value>gandalf</value>
               </parameter>
          </ResourceParams>
Also, I've configured my web application deployment descriptor (web.xml) to use this resource:
<resource-ref>
     <description>JavaMail Resource</description>
     <res-ref-name>mail/Session</res-ref-name>
     <res-type>javax.mail.Session</res-type>
     <res-auth>Container</res-auth>
</resource-ref>
Now in the Java code I try to get the JavaMail session in this way:
private Context devuelveContexto() throws javax.naming.NamingException
initContext = new InitialContext();
return (Context) initContext.lookup("java:/comp/env");
public javax.mail.Session devuelveSesionMail()
throws javax.naming.NamingException
Context envContext = devuelveContexto();
javax.mail.Session mailSesion = (javax.mail.Session) envContext.lookup("mail/Session"); <--- this throws an exception
I'm doing all like is explained in Tomcat help web page 'JNDI Resources HOW-TO' but it doesn' work for me.
The exception raised is this:
java.lang.reflect.InvocationTargetException: java.lang.ClassCastException: javax.mail.Session
     at com.aplicacionesweb.evaluaciones.ddbb.CargadorRecursos.devuelveSesionMail(CargadorRecursos.java:76)
     at com.aplicacionesweb.evaluaciones.fases.actions.ConcertacionAction.enviarCorreo(ConcertacionAction.java:562)
     at com.aplicacionesweb.evaluaciones.fases.actions.ConcertacionAction.grabarConcertacion(ConcertacionAction.java:510)
     at java.lang.reflect.Method.invoke(Native Method)
     at org.apache.struts.actions.DispatchAction.perform(DispatchAction.java:236)
     at org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1787)
Please help.

Problem solved. I had 'mail.jar' and 'activation.jar' in 'WEB-INF/lib' directory, causing a classes conflict.

Session bean "Exception in method create()"

Hello,
I have a session bean which is consuming entity bean and session bean is published as webService now when I call create method of entity bean from session bean it says "Exception in method com.syntel.exam_tool.entityBeans.tabExamTable.TabExamLocalHomeImpl0.create()."
But my create method of entity bean is blank I am not getting from where this exceptions is being thrown.
below is the code from session bean wehre I am calling entity bean
javax.naming.Context ctx;
ctx = new InitialContext();
TabExamLocalHome tabExamLocalHome = (TabExamLocalHome) ctx.lookup("java:comp/env/ejb/TabExamBean1");
TabExamLocal tabExam = tabExamLocalHome.create();
Please help me ins this problem.
Thanks

Hi Janeth,
below is the stack trace
com.syntel.exam_tool.entityBeans.tabExamTable.TabExamLocalHomeImpl0_0.create(TabExamLocalHomeImpl0_0.java:343)
com.syntel.exam_tool.sessionBeans.examTool.ExamToolBean.findByPassingScore(ExamToolBean.java:126)
com.syntel.exam_tool.sessionBeans.examTool.ExamToolLocalLocalObjectImpl0_0.findByPassingScore(ExamToolLocalLocalObjectImpl0_0.java:247)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:324)
com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)
com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)
com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
SoapServlet.doPost(SoapServlet.java:51)
javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
java.security.AccessController.doPrivileged(Native Method)
com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
please help me in this as I am not getting where the problem is
Edited by: new to netweaver on Sep 9, 2009 11:15 AM

Session replication exception

          hi all
          I am getting the exception below on the second server in
          the cluster when i am hitting the first machine whenever
          i am trying to login.
          My config.xl is such that the session is replicated;
          Also i am attaching an object of NWSession( implements serializable ) to HttpSession
          object.
          Both servers in the cluster are identical and has the
          same web applications deployed ( so that the class
          com.epeople.NWSession class is available on both
          servers ) ( Note that i can create an instance of
          NWSession on both servers )
          Thanks in advance,
          sri kumar
          java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:
               java.lang.ClassNotFoundException: com.epeople.nwsession.NWSession
          java.lang.ClassNotFoundException: com.epeople.nwsession.NWSession
               <<no stack trace available>>
          --------------- nested within: ------------------
          weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
          [java.rmi.UnmarshalException: error unmarshalling arguments; nested exception
          is:
               java.lang.ClassNotFoundException: com.epeople.nwsession.NWSession]
               at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
               at $Proxy131.create(Unknown Source)
               at weblogic.cluster.replication.ReplicationManager.trySecondary(ReplicationManager.java:797)
               at weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationManager.java:743)
               at weblogic.cluster.replication.ReplicationManager.getPrimary(ReplicationManager.java:716)
               at weblogic.cluster.replication.ReplicationManager.lookup(ReplicationManager.java:374)
               at weblogic.servlet.internal.session.ReplicatedSessionContext.getSessionInternal(ReplicatedSessionContext.java:271)
               at weblogic.servlet.internal.ServletRequestImpl.getValidSession(ServletRequestImpl.java:1888)
               at weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.java:1697)
               at weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(ServletSecurityManager.java:119)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2367)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1959)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)


          I am having the same problem. I am even running both servers in the cluster on
          the same machine (using multi homing ) and still get this error . Any help , please
          . Any BEA expert ??
          "Narinder" <[email protected]> wrote:
          >It looks like, NWSession is not visible to the second server. Try making
          >sure that the config on the second server is exactly like the first server.
          >-Narinder
          >
          >
          >"Sri kumar" <[email protected]> wrote in message
          >news:[email protected]...
          >>
          >> hi all
          >>
          >> I am getting the exception below on the second server in
          >> the cluster when i am hitting the first machine whenever
          >> i am trying to login.
          >>
          >> My config.xl is such that the session is replicated;
          >>
          >> Also i am attaching an object of NWSession( implements serializable
          >) to
          >HttpSession
          >> object.
          >>
          >> Both servers in the cluster are identical and has the
          >> same web applications deployed ( so that the class
          >> com.epeople.NWSession class is available on both
          >> servers ) ( Note that i can create an instance of
          >> NWSession on both servers )
          >>
          >> Thanks in advance,
          >> sri kumar
          >>
          >> java.rmi.UnmarshalException: error unmarshalling arguments; nested
          >exception is:
          >>
          >> java.lang.ClassNotFoundException: com.epeople.nwsession.NWSession
          >> java.lang.ClassNotFoundException: com.epeople.nwsession.NWSession
          >> <<no stack trace available>>
          >> --------------- nested within: ------------------
          >> weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
          >> [java.rmi.UnmarshalException: error unmarshalling arguments; nested
          >exception
          >> is:
          >> java.lang.ClassNotFoundException: com.epeople.nwsession.NWSession]
          >> at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
          >> at $Proxy131.create(Unknown Source)
          >> at
          >weblogic.cluster.replication.ReplicationManager.trySecondary(ReplicationMana
          >ger.java:797)
          >> at
          >weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationM
          >anager.java:743)
          >> at
          >weblogic.cluster.replication.ReplicationManager.getPrimary(ReplicationManage
          >r.java:716)
          >> at
          >weblogic.cluster.replication.ReplicationManager.lookup(ReplicationManager.ja
          >va:374)
          >> at
          >weblogic.servlet.internal.session.ReplicatedSessionContext.getSessionInterna
          >l(ReplicatedSessionContext.java:271)
          >> at
          >weblogic.servlet.internal.ServletRequestImpl.getValidSession(ServletRequestI
          >mpl.java:1888)
          >> at
          >weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.j
          >ava:1697)
          >> at
          >weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Servle
          >tSecurityManager.java:119)
          >> at
          >weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
          >ntext.java:2367)
          >> at
          >weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
          >:1959)
          >> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
          >
          >

Session Loader Exception

Hi,
I am trying to login to a server session in TopLink,I am getting this exception even with the oracle12.zip set in the class path. Has any one encountered the same problem before ? Exception is shown below.
Local Exception Stack:
Exception Description: Several [1] SessionLoaderExceptions were thrown:
Exception [TOPLINK-9003] (OracleAS TopLink - 10g (9.0.4) (Build 031126)): oracle.toplink.exceptions.SessionLoaderException
Exception Description: Unable to process XML tag [driver-class] with value [oracle.jdbc.driver.OracleDriver].
Internal Exception: java.lang.ClassNotFoundException: oracle.jdbc.driver.OracleDriver
     at oracle.toplink.exceptions.SessionLoaderException.finalException(SessionLoaderException.java:89)
     at oracle.toplink.tools.sessionconfiguration.XMLLoader.load(XMLLoader.java:156)
     at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(SessionManager.java:219)
     at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(SessionManager.java:192)
     at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(SessionManager.java:149)
     at com.test.testTop.login(testTop.java:58)
     at com.test.testTop.main(testTop.java:34)
SessionLoaderExceptions:

Try testing to ensure that the driver is on the classpath correctly first. It may be that a class in this jar requires another class missing from your classpath.
In your test first do a,
Class.forName("oracle.jdbc.driver.OracleDriver");
If this works, you may be passing an incorrect class loader to the SessionManager, ensure the class loader you pass can load the Oracle driver.

NWA Session Management Exception

Hi,
how can I access NWA -> Configuration Management -> Infrastructure -> Session Management.
I'm running CE7.1 SP5 and get the following exception:
java.lang.NullPointerException
at com.sap.tc.lm.itsam.ui.session.mngt.sessionmngt.SessionMngtView.refreshDomainsTree (SessionMngtView.java:745) at com.sap.tc.lm.itsam.ui.session.mngt.sessionmngt.SessionMngtView.wdDoInit(SessionMngtView.java:118) at com.sap.tc.lm.itsam.ui.session.mngt.sessionmngt.wdp.InternalSessionMngtView.wdDoInit(InternalSessionMngtView.java:462) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:58) at com.sap.tc.webdynpro.progmodel.controller.Controller.initController (Controller.java:230)... 75 more
Please give feedback if this error can be reproduced.
Best regards,
Kevin

Hi,
have you found a solution for this error.
I have the same error.
regards

Session.invalidate exception

FacesContext ctx = FacesContext.getCurrentInstance();
ExternalContext ectx = ctx.getExternalContext();
HttpServletResponse response = (HttpServletResponse)ectx.getResponse();
HttpServletRequest request = (HttpServletRequest)ectx.getRequest();
HttpSession session = (HttpSession)ectx.getSession(false);
if (session!=null) {
try {
session.invalidate();
catch (Throwable th) {
th.printStackTrace();
if (response!=null) {
response.sendRedirect("/asd/asda/asd.jspx");
//request.getRequestDispatcher("").forward(request, response);
if (ctx!=null) {
ctx.responseComplete();
I get this exception when I call session.invalidate .....not sure why??
## Detail 0 ##
java.lang.NullPointerException
     at oracle.adf.share.http.HttpUtil.getAttribute(HttpUtil.java:98)
     at oracle.adf.share.http.HttpSessionScopeAdapter.get(HttpSessionScopeAdapter.java:240)
     at oracle.jbo.common.ampool.SessionCookieImpl.<init>(SessionCookieImpl.java:164)
     at oracle.jbo.http.HttpSessionCookieImpl.<init>(HttpSessionCookieImpl.java:133)
     at oracle.jbo.http.HttpSessionCookieImpl.<init>(HttpSessionCookieImpl.java:124)
     at oracle.jbo.http.HttpSessionCookieFactory.createSessionCookie(HttpSessionCookieFactory.java:131)
     at oracle.jbo.common.ampool.ApplicationPoolImpl.createSessionCookie(ApplicationPoolImpl.java:452)
     at oracle.adf.model.bc4j.DataControlFactoryImpl.findOrCreateSessionCookie(DataControlFactoryImpl.java:141)
     at oracle.adf.model.bc4j.DataControlFactoryImpl.createSession(DataControlFactoryImpl.java:222)
     at oracle.adf.model.binding.DCDataControlReference.getDataControl(DCDataControlReference.java:76)
     at oracle.adf.model.BindingContext.get(BindingContext.java:457)
     at oracle.adf.model.binding.DCUtil.findSpelObject(DCUtil.java:280)
     at oracle.adf.model.binding.DCUtil.findSpelObject(DCUtil.java:248)
     at oracle.adf.model.binding.DCUtil.findContextObject(DCUtil.java:383)
     at oracle.adf.model.binding.DCIteratorBinding.<init>(DCIteratorBinding.java:127)
     at oracle.jbo.uicli.binding.JUIteratorBinding.<init>(JUIteratorBinding.java:60)
     at oracle.jbo.uicli.binding.JUIteratorDef.createIterBinding(JUIteratorDef.java:87)
     at oracle.jbo.uicli.binding.JUIteratorDef.createIterBinding(JUIteratorDef.java:51)
     at oracle.adf.model.binding.DCIteratorBindingDef.createExecutableBinding(DCIteratorBindingDef.java:277)
     at oracle.adf.model.binding.DCBindingContainerDef.createExecutables(DCBindingContainerDef.java:296)
     at oracle.adf.model.binding.DCBindingContainerDef.createBindingContainer(DCBindingContainerDef.java:425)
     at oracle.adf.model.binding.DCBindingContainerReference.createBindingContainer(DCBindingContainerReference.java:54)
     at oracle.adf.model.binding.DCBindingContainerReference.getBindingContainer(DCBindingContainerReference.java:44)
     at oracle.adf.model.BindingContext.get(BindingContext.java:483)
     at oracle.adf.model.binding.DCBindingContainer.release(DCBindingContainer.java:1913)
     at oracle.adf.model.binding.DCDataControl.release(DCDataControl.java:1551)
     at oracle.adf.model.bc4j.DCJboDataControl.release(DCJboDataControl.java:468)
     at oracle.adf.model.binding.DCDataControl.release(DCDataControl.java:1482)
     at oracle.adf.model.BindingContext.release(BindingContext.java:270)
     at oracle.adf.model.servlet.HttpBindingContext.valueUnbound(HttpBindingContext.java:36)
     at com.evermind.server.http.EvermindHttpSession.destroy(EvermindHttpSession.java:454)
     at com.evermind.server.http.HttpApplication.invalidateSession(HttpApplication.java:871)
     at com.evermind.server.http.EvermindHttpSession.invalidate(EvermindHttpSession.java:396)
     at mycode.SecurityBacking.logoutAction(SecurityBacking.java:387)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.sun.faces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:146)
     at oracle.adf.view.faces.component.UIXComponentBase.__broadcast(UIXComponentBase.java:1087)
     at oracle.adf.view.faces.component.UIXCommand.broadcast(UIXCommand.java:204)
     at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:287)
     at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:401)
     at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:95)
     at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:245)
     at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:110)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:213)
     at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
     at oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl._invokeDoFilter(AdfFacesFilterImpl.java:228)
     at oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl._doFilterImpl(AdfFacesFilterImpl.java:197)
     at oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl.doFilter(AdfFacesFilterImpl.java:123)
     at oracle.adf.view.faces.webapp.AdfFacesFilter.doFilter(AdfFacesFilter.java:103)
     at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)
     at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:162)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
     at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:221)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:122)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:111)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
     at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
     at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)

java.lang.NullPointerException     at oracle.adf.share.http.HttpUtil.getAttribute(HttpUtil.java:98)     at oracle.adf.share.http.HttpSessionScopeAdapter.get(HttpSessionScopeAdapter.java:240)     at oracle.adf.model.BindingRequestHandler.beginRequest(BindingRequestHandler.java:127)     at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:161)     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.3.0) ].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.3.0) ].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.3.0) ].server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.3.0) ].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.3.0) ].server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:221)     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.3.0) ].server.http.HttpRequestHandler.run(HttpRequestHandler.java:122)     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.3.0) ].server.http.HttpRequestHandler.run(HttpRequestHandler.java:111)     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)     at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)     at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)     at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.3.0) ].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)     at java.lang.Thread.run(Thread.java:595)

Lookup exception on conncetionFactory

          Greetings,
          Have TopicSend and TopicReceive applications communicating fine either on PC or
          on UNIX
          when talking to a BEA weblogic JMS server 8.1 installed on PC.
          The two applications are compiled with the two weblogic JMS relating files wljmsclient.jar
          and wlclient.jar that come with workshop 8.1.
          However when I try to use another unix machine as a JMS server (rev 6.1), the
          lookup of topic
          conncetion fails. See below. Any hints? Thanks.
          Exception in thread "main" javax.naming.NamingException: Unhandled exception in
          lookup. Root exception is org.omg.CORBA.portable.UnknownException: vmcid: 0x0
          minor code: 0 completed: Maybe
          at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:376)
          at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:457)
          at org.omg.CosNaming._NamingContextStub.resolve(_NamingContextStub.java:244)
          at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:187)
          at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:174)
          at javax.naming.InitialContext.lookup(InitialContext.java:347)
          at com.qoptics.nba.xngi.TopicSend.initTopicSend(TopicSend.java:110)
          at com.qoptics.nba.xngi.TopicSend.init(TopicSend.java:78)
          at com.qoptics.nba.xngi.Main.main(Main.java:108)
          When executing this line of code:
          tconFactory = (TopicConnectionFactory)
          PortableRemoteObject.narrow(ctx.lookup(JMS_FACTORY), TopicConnectionFactory.class);
          where
          JMS_FACTORY=="weblogic.jndi.WLInitialContextFactory"
          and ctx is built including these two lines:
          env.put(Context.INITIAL_CONTEXT_FACTORY, JNDI_FACTORY);
          env.put(Context.PROVIDER_URL, URL);
          where
          JNDI_FACTORY=="corporatename.MQueueFactory"
          URL== "t3://theServersIPaddress:7001"


Not your bad, the 8.1 weblogic.jar can interoperate
          all the way back to 6.1. If it didn't, we'd have
          a lot of unhappy customers. Something strange is going on,
          but at least for now you have a work-around.
          Yazid Benkhellat wrote:
          > My bad...I was using weblogic.jar version 8.1 and that's how I got that behavior.
          >
          > It works fine now with weblogic.jar version 6.1. Thanks.
          >
          > Tom Barnes <[email protected]> wrote:
          >
          >>
          >>Yazid Benkhellat wrote:
          >>
          >>>Thanks Tom.
          >>>
          >>>I add weblogic.jar to the classpath when compiling and when running
          >>
          >>the two applications.
          >>
          >>>This time both applications just quit (terminate) on lookup without
          >>
          >>an exception!
          >>
          >>That's a new one - your code isn't doing anything
          >>different than any other client has to do. Did you remember
          >>to remove the wl*.jar versions from the classpath? They
          >>aren't designed to work with weblogic.jar and may
          >>conflict in unanticipated ways.
          >>
          >>
          >>>Also, is weblogic.jar license free?
          >>
          >>I knew you were going to ask that one!
          >>
          >>weblogic.jar is license free if used as a client, but a
          >>license is required if used as a server.
          >>
          >>
          >>>Thanks
          >>>
          >>>
          >>>Tom Barnes <[email protected]> wrote:
          >>>
          >>>
          >>>>As documented, the thin clients only work with 8.1 and up. To
          >>>>use a 8.1 client with previous versions you need the
          >>>>whole weblogic.jar for your client instead, or to attempt
          >>>>to create your own thin client based on the
          >>>>weblogic.jar using the methods described
          >>>>in the thin client white-paper (a bit of work there).
          >>>>
          >>>>Yazid Benkhellat wrote:
          >>>>
          >>>>
          >>>>
          >>>>>Greetings,
          >>>>>
          >>>>>Have TopicSend and TopicReceive applications communicating fine either
          >>>>
          >>>>on PC or
          >>>>
          >>>>
          >>>>>on UNIX
          >>>>>when talking to a BEA weblogic JMS server 8.1 installed on PC.
          >>>>>The two applications are compiled with the two weblogic JMS relating
          >>>>
          >>>>files wljmsclient.jar
          >>>>
          >>>>
          >>>>>and wlclient.jar that come with workshop 8.1.
          >>>>>
          >>>>>However when I try to use another unix machine as a JMS server (rev
          >>>>
          >>>>6.1), the
          >>>>
          >>>>
          >>>>>lookup of topic
          >>>>>conncetion fails. See below. Any hints? Thanks.
          >>>>>
          >>>>>
          >>>>>Exception in thread "main" javax.naming.NamingException: Unhandled
          >>>>
          >>>>exception in
          >>>>
          >>>>
          >>>>>lookup. Root exception is org.omg.CORBA.portable.UnknownException:
          >>>>
          >>>>vmcid: 0x0
          >>>>
          >>>>
          >>>>>minor code: 0 completed: Maybe
          >>>>>
          >>>>> at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:376)
          >>>>>
          >>>>> at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:457)
          >>>>>
          >>>>> at org.omg.CosNaming._NamingContextStub.resolve(_NamingContextStub.java:244)
          >>>>>
          >>>>> at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:187)
          >>>>>
          >>>>> at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:174)
          >>>>>
          >>>>> at javax.naming.InitialContext.lookup(InitialContext.java:347)
          >>>>>
          >>>>> at com.qoptics.nba.xngi.TopicSend.initTopicSend(TopicSend.java:110)
          >>>>>
          >>>>> at com.qoptics.nba.xngi.TopicSend.init(TopicSend.java:78)
          >>>>>
          >>>>> at com.qoptics.nba.xngi.Main.main(Main.java:108)
          >>>>>
          >>>>>
          >>>>>
          >>>>>When executing this line of code:
          >>>>>
          >>>>>tconFactory = (TopicConnectionFactory)
          >>>>>
          >>>>> PortableRemoteObject.narrow(ctx.lookup(JMS_FACTORY), TopicConnectionFactory.class);
          >>>>>
          >>>>>where
          >>>>>
          >>>>>JMS_FACTORY=="weblogic.jndi.WLInitialContextFactory"
          >>>>>
          >>>>>
          >>>>>
          >>>>>and ctx is built including these two lines:
          >>>>>
          >>>>>env.put(Context.INITIAL_CONTEXT_FACTORY, JNDI_FACTORY);
          >>>>>
          >>>>>env.put(Context.PROVIDER_URL, URL);
          >>>>>
          >>>>>where
          >>>>>
          >>>>>JNDI_FACTORY=="corporatename.MQueueFactory"
          >>>>>
          >>>>>URL== "t3://theServersIPaddress:7001"
          >>>>>
          >>>>
          >

Tomcat saves the sessions even if I stop application!!!

Hi all,
I have deployed a web application and now whenever I stop it from tomcat/manager and restart it shows the number of whole previous sessions (right now it is 7 ) I reload the context but no chance. Again stop/start application and it does not help too.
Is this a bug? Have you ever encountered it?
-Thanks

Hi,
why don't you post this question on the Apache forum and see what the folks over there have to say ?
Frank

Session Invalidator exceptions

I'm testing out weblogic 4.5 coming from 4.03 and i have discovered some
          strage session behavior. the process controled by the
          weblogic.properties parameter
          weblogic.httpd.session.invalidationIntervalSecs=xxx is throwing the
          following exception:
          Fri Feb 25 10:49:46 PST 2000:<E> <HttpSessionContext> Problem finding
          all keys
          Fri Feb 25 10:49:46 PST 2000:<E> <HttpSessionContext>
          java.rmi.RemoteException:
          Exception unserializing values; nested exception is:
          java.io.EOFException: Expecting code
          java.io.EOFException: Expecting code
          at
          java.io.ObjectInputStream.peekCode(ObjectInputStream.java:1276)
          at
          java.io.ObjectInputStream.readObject(ObjectInputStream.java:282)
          at
          java.io.ObjectInputStream.readObject(ObjectInputStream.java:232)
          at
          java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java:789)
          at
          java.io.ObjectInputStream.readObject(ObjectInputStream.java:353)
          at
          java.io.ObjectInputStream.readObject(ObjectInputStream.java:232)
          at
          java.io.ObjectInputStream.inputObject(ObjectInputStream.java:978)
          at
          java.io.ObjectInputStream.readObject(ObjectInputStream.java:369)
          at
          java.io.ObjectInputStream.readObject(ObjectInputStream.java:232)
          at
          weblogic.servlet.internal.session.ClusteredSession.ejbLoad(ClusteredSession.java:68)
          at
          weblogic.servlet.internal.session.ClusteredSessionPSJDBC.finderEnumToEnum(ClusteredSessionPSJDBC.java:663)
          at
          weblogic.servlet.internal.session.ClusteredSessionPSJDBC.findAllSessions(ClusteredSessionPSJDBC.java:543)
          at
          weblogic.servlet.internal.session.ClusteredSessionHomeImpl.findAllSessions(ClusteredSessionHomeImpl.java:127)
          at
          weblogic.servlet.internal.session.ClusteredSessionHomeImpl_ServiceStub.findAllSessions(ClusteredSessionHomeImpl_ServiceStub.java:143)
          at
          weblogic.servlet.internal.session.ClusteredSessionContextImpl.getIds(ClusteredSessionContextImpl.java:105)
          at
          weblogic.servlet.internal.session.SessionContext$SessionInvalidator.invalidateSessions(SessionContext.java:331)
          at
          weblogic.servlet.internal.session.SessionContext$SessionInvalidator.trigger(SessionContext.java:325)
          at
          weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:201)
          at
          weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:195)
          at
          weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:63)
          at weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:106)
          is this because 4.03 sessions and 4.5 session cannot coexist in the
          database? is there anything that we could be doing to prevent this from
          happening? the exception doesn't seem to be fatal, but it can't be good.
          thanks.
          sam


You should be able to use the internal exception's error code.
i.e.
((SQLException) exception.getInternalException()).getErrorCode() == 17002

Tomcat 5.5 Session lookup exception

Similar Messages

Maybe you are looking for