JDev 11g on WebLogic+TopLink+Web Services (getSharedSession() Disconnects)

Question

I am facing an issue while using {color:#0000ff}TopLink{color} through a {color:#0000ff}web service{color} request.
I apologize for a lengthy posting but thought I should give as much information as possible.
<strong><u>Migration from TP4 to JDev 11g Production
</u></strong>I am in a process of {color:#0000ff}migration{color} of an application from {color:#0000ff}JDeveloper 11g TP4 to JDeveloper 11g Production{color}.
I am facing an issue using {color:#0000ff}TopLink{color} with {color:#0000ff}Web Services{color} on {color:#0000ff}Oracle WebLogic 10g Release 3.
{color}
<strong><u>Existing Application</u></strong>
This application uses {color:#0000ff}TopLink{color} and also has{color:#0000ff} JAX-WS{color} based web services.
The web services client calls the service endpoint that internally uses {color:#0000ff}TopLink{color} to make database calls.
We currently use {color:#0000ff}Tomcat{color} for deployment and the application works fine.
<strong><u>Issue while moving to Oracle WebLogic 10g R3
</u></strong>While porting this application to WebLogic we faced an issue wherein a call to the {color:#0000ff}web service{color} results in {color:#0000ff}disconnection{color} of existing {color:#0000ff}TopLink{color} {color:#000080}server session{color} and creation of new ones.
Some surfing on the net indicated that this could be due to the different class loaders that are used to access the TopLink server session.
You must login to the ServerSession before acquiring ClientSessions
<strong><u>LOG</u></strong>
Here is a log from our application
TopLink server sessions when accessed in several JSP pages.
getDelegateSession: session = 6666709
getDelegateSession: sessionName = my_session (this is the name of the server session)
getDelegateSession: sessionClassLoader =weblogic.utils.classloaders.ChangeAwareClassLoader@feaad1 finder: weblogic.utils.classloaders.CodeGenClassFinder@15712d annotation: &lt;JDevApp&gt;@&lt;Appname&gt;
getDelegateSession: threadClassLoader =weblogic.utils.classloaders.ChangeAwareClassLoader@feaad1 finder: weblogic.utils.classloaders.CodeGenClassFinder@15712d annotation: &lt;JDevApp&gt;@&lt;Appname&gt;
<p>
TopLink server session when accessed through a web service.
getDelegateSession: session = 1013641
getDelegateSession: sessionName = my_session
getDelegateSession: sessionClassLoader =weblogic.wsee.util.JAXWSClassLoaderFactory$1@180a6b3 finder: weblogic.utils.classloaders.CodeGenClassFinder@1e2a021 annotation:
getDelegateSession: threadClassLoader =weblogic.wsee.util.JAXWSClassLoaderFactory$1@180a6b3 finder: weblogic.utils.classloaders.CodeGenClassFinder@1e2a021 annotation:
<strong><u>Note that the class loader is different.</u></strong>
Also the following log is displayed just before it could log the above information.
<strong><u>DETAILED LOG
</u></strong>009-03-04 16:55:12,883 DEBUG ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)' http://oracle.toplink.logging.DefaultSessionLog - &lt;TopLink Finest: 2009.03.04 16:55:12.883--ServerSession(6666709)--Thread(Thread[)--sequencing disconnected&gt;<br />
2009-03-04 16:55:12,883 DEBUG ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)' http://oracle.toplink.logging.DefaultSessionLog - &lt;TopLink Config: 2009.03.04 16:55:12.883--ServerSession(6666709)--Connection(23588442)--Thread(Thread[)--disconnect&gt;<br />
2009-03-04 16:55:12,883 DEBUG ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)' http://oracle.toplink.logging.DefaultSessionLog - &lt;TopLink Finer: 2009.03.04 16:55:12.883--ServerSession(6666709)--Thread(Thread[)--initialize identitymaps&gt;<br />
2009-03-04 16:55:12,992 INFO ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)' http://oracle.toplink.logging.DefaultSessionLog - &lt;TopLink Info: 2009.03.04 16:55:12.992--ServerSession(6666709)--Thread(Thread[)--my_session logout successful&gt;<br />
Thanks for reading this lengthy posting.
- Abhay
</p>
Edited by: user608979 on Mar 4, 2009 5:10 AM

Answer 1

James,
My issue is resolved. Thanks for your tip.
I am using {color:#0000ff}SessionManager.getSession(...{color}
Solution:*
I changed the class loader while getting a session.
I had to extend the {color:#0000ff}SessionFactory{color} and override {color:#0000ff}both{color} the {color:#0000ff}getSharedSession(){color} methods while replacing {color:#ff0000}getClass().getClassLoader(){color} with {color:#0000ff}&lt;MyLocatorSingletonBean&gt;.getInstance().getClass().getClassLoader().{color}
Regrding Server Sessions*
While posting the question I had started thinking in the same direction of having sever sessions as singleton/Spring bean but sine this will change a lot of things in my current framework so decided I just use the above solution for now.
Really appreciated!
- Abhay