Java.io.notSerializableException:weblogic.jdbc.pool.Connection

Hello,
          In my servelts only sometime I get this exception. I am using WLS7.0 jDK
          1.3.1(the one which comes with WLS7.0). I am using Java Beans which are all
          serializable.(I have declared that the classes implements Serilizable)
          Exception is as follows
          <Jan 27, 2003 4:19:09 AM EST> <Error> <HTTP Session> <triton>
          <AccupacServer> <ExecuteThread: '8' for queue: 'default'> <kernel identity>
          <> <100028> <Could not deserialize session data>
          java.io.NotSerializableException: weblogic.jdbc.pool.Connection
          at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1143)
          at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:361)
          at
          java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1822)
          at
          java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:475)
          at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1209)
          at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:361)
          at
          weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:9
          1)
          at
          weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:6
          6)
          at
          weblogic.servlet.internal.session.SessionData.removeAttribute(SessionData.ja
          va:570)
          at
          weblogic.servlet.internal.session.SessionData.removeAttribute(SessionData.ja
          va:552)
          at
          weblogic.servlet.internal.session.SessionData.remove(SessionData.java:734)
          at
          weblogic.servlet.internal.session.MemorySessionContext.invalidateSession(Mem
          orySessionContext.java:51)
          at
          weblogic.servlet.internal.session.SessionContext$SessionInvalidator$Invalida
          tionAction.run(SessionContext.java:523)
          at
          weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManage
          r.java:744)
          at
          weblogic.servlet.internal.session.SessionContext$SessionInvalidator.cleanupE
          xpiredSessions(SessionContext.java:444)
          at
          weblogic.servlet.internal.session.SessionContext.deleteInvalidSessions(Sessi
          onContext.java:81)
          at
          weblogic.servlet.internal.session.SessionContext$SessionInvalidator.trigger(
          SessionContext.java:392)
          at
          weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:181
          at
          weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManage
          r.java:744)
          at
          weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigg
          er.java:167)
          at
          weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java
          :161)
          at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:38)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
          Any help appreciated.
          Thanks
          Madhu

Similar Messages

Connection Pool using weblogic.jdbc.pool.Driver

I am trying to use connection pooling in my JSP data access classes (which
work fine without connection pooling) on weblogic 4.5.1. I tried using the
weblogic.jdbc.pool.Driver but it exits with the following exception:
java.lang.ClassNotFoundException: weblogic.jdbc.pool.Driver
The path c:\weblogic\classes which contains this driver is specified in the
weblogic.class.path . I can not include it in the java class path because
then weblogic server fails to start at all (with an error message). I would
appreciate any help !
Thanks,
Usamah

Hi. Please don't repost identical posts to different news groups. See a response
in the JDBC group. thanks, joe
Usamah Malik wrote:
I am trying to use connection pooling in my JSP data access classes (which
work fine without connection pooling) on weblogic 4.5.1. I tried using the
weblogic.jdbc.pool.Driver but it exits with the following exception:
java.lang.ClassNotFoundException: weblogic.jdbc.pool.Driver
The path c:\weblogic\classes which contains this driver is specified in the
weblogic.class.path . I can not include it in the java class path because
then weblogic server fails to start at all (with an error message). I would
appreciate any help !
Thanks,
Usamah--
PS: Hey folks, we're hiring Java engineers for our WebLogic
Engineering group in downtown S.F. Send me your resume.
The Weblogic Application Server from BEA
JavaWorld Editor's Choice Award: Best Web Application Server
Java Developer's Journal Editor's Choice Award: Best Web Application Server
Crossroads A-List Award: Rapid Application Development Tools for Java
Intelligent Enterprise RealWare: Best Application Using a Component Architecture
http://weblogic.beasys.com/press/awards/index.htm

Java.lang.StringIndexOutOfBoundsException when trying to create a JDBC pool connection.

Hi, I get a java.lang.StringIndexOutOfBoundsException when making a JDBC
pool connection via the console of WLS 7.0. I use SQL Server 2000 in Win2K
SP2 environment. Exactly the same configuration works perfectly in WinXP
Pro. Can anyone advise me what might cause this problem? Thanks a lot.
Log message
####<May 13, 2002 5:15:52 PM CEST> <Error> <JDBC> <abcdefgh> <vtsserver>
<ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'> <kernel
identity> <> <001060> <Cannot startup connection pool
"ejbTestConnectionPool" java.lang.StringIndexOutOfBoundsException: String
index out of range: -1>
Exception
java.lang.NullPointerException
at
weblogic.management.console.utils.MBeans.getMBeanClassNameFor(MBeans.java:11
53)
at
weblogic.management.console.actions.mbean.EditMBeanAction.getMBeanClass(Edit
MBeanAction.java:210)
at
weblogic.management.console.actions.mbean.EditMBeanAction.getDialogTypeKey(E
ditMBeanAction.java:188)
at
weblogic.management.console.actions.internal.InternalActionContext.setAction
(InternalActionContext.java:158)
at
weblogic.management.console.actions.internal.ActionServlet.doAction(ActionSe
rvlet.java:170)
at
weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServ
let.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Servle
tStubImpl.java:945)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:332)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:242)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(W
ebAppServletContext.java:5363)
at
weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManage
r.java:721)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:3043)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
:2466)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
--------------- nested within: ------------------
weblogic.utils.NestedRuntimeException - with nested exception:
[java.lang.NullPointerException]
at
weblogic.management.console.utils.MBeans.getMBeanClassNameFor(MBeans.java:11
56)
at
weblogic.management.console.actions.mbean.EditMBeanAction.getMBeanClass(Edit
MBeanAction.java:210)
at
weblogic.management.console.actions.mbean.EditMBeanAction.getDialogTypeKey(E
ditMBeanAction.java:188)
at
weblogic.management.console.actions.internal.InternalActionContext.setAction
(InternalActionContext.java:158)
at
weblogic.management.console.actions.internal.ActionServlet.doAction(ActionSe
rvlet.java:170)
at
weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServ
let.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Servle
tStubImpl.java:945)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:332)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:242)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(W
ebAppServletContext.java:5363)
at
weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManage
r.java:721)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:3043)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
:2466)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
--------------- nested within: ------------------
weblogic.management.console.actions.ActionException - with nested exception:
[weblogic.utils.NestedRuntimeException - with nested exception:
[java.lang.NullPointerException]]
at weblogic.management.console.actions.ErrorAction.(ErrorAction.java:38)
at
weblogic.management.console.actions.internal.ActionServlet.doAction(ActionSe
rvlet.java:190)
at
weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServ
let.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Servle
tStubImpl.java:945)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:332)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:242)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(W
ebAppServletContext.java:5363)
at
weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManage
r.java:721)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:3043)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
:2466)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
Current Date
Mon May 13 17:15:52 CEST 2002
Console Release Build
null
Console Build
null
Server Release Build
7.0.0.0
Server Build
WebLogic Server 7.0 Thu Apr 25 17:16:22 PDT 2002 180709
All Server Product Versions
WebLogic Server 7.0 Thu Apr 25 17:16:22 PDT 2002 180709
WebLogic XMLX Module 7.0 Thu Apr 25 17:26:07 PDT 2002 180709
Request Info
Protocol: HTTP/1.1
ServerName: localhost
ServerPort: 7001
Secure: false
ContextPath: /console
ServletPath: /common/error.jsp
QueryString:
MBean=vtsdomain%3AName%3DejbTestConnectionPool%2CType%3DJDBCConnectionPool
PathInfo: null
PathTranslated: null
RequestURI: /console/common/error.jsp
AuthType: null
ContentType: application/x-www-form-urlencoded
CharacterEncoding: null
Locale: en_US
Method: POST
Session:
weblogic.servlet.internal.session.MemorySessionData@1926bd
RequestedSessionId:
8fMghRfnkcOls1wsW0vIRS8PuQKquWoYcnt6ciUG5uznDJiLr1ZA!-37849198!1021299872710
RequestedSessionIdFromCookie: true
RequestedSessionIdFromURL: false
UserPrincipal: vts
RemoteUser: vts
RemoteAddr: 127.0.0.1
RemoteHost: 127.0.0.1
Parameters
MBean = vtsdomain:Name=ejbTestConnectionPool,Type=JDBCConnectionPool
chosen_wl_control_weblogic.management.configuration.JDBCConnectionPoolMBean.
Targets-Server = vtsdomain:Name=vtsserver,Type=Server
weblogic.console.submit_form = dataposted
wl_control_weblogic.management.configuration.JDBCConnectionPoolMBean.Targets
-Server = vtsdomain:Name=vtsserver,Type=Server
Attributes
wlinternalaction =
weblogic.management.console.actions.internal.InternalActionContext@4372d8
java.util.Locale = en_US weblogic.management.console.catalog.Catalog =
weblogic.management.console.catalog.XmlCatalog@3ca759
weblogic.management.console.helpers.BrowserHelper = User-Agent: Mozilla/4.0
(compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.0.3705) IE: true Netscape:
false Supported: true JavscriptHrefs: false TableCellClick: true
DocumentReloadedOnResize: false DropdownStretchable: true CellSpacingBlank:
false EmptyCellBlank: false ImgOnclickSupported: true TableBorderFancy: true
PartialToWideTables: false DisabledControlSupported: true
weblogic.management.console.helpers.DebugHelper =
weblogic.management.console.helpers.DebugHelper@16ed83
weblogic.management.console.helpers.UnitsHelper =
weblogic.management.console.helpers.UnitsHelper@ae2d9
weblogic.management.console.helpers.UrlHelper =
weblogic.management.console.helpers.UrlHelper@28fd41
Headers
Accept = image/gif, image/x-xbitmap, image/jpeg, image/pjpeg,
application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword,
*/* Accept-Encoding = gzip, deflate Accept-Language = en-us Cache-Control =
no-cache Connection = Keep-Alive Content-Length = 304 Content-Type =
application/x-www-form-urlencoded Cookie =
ADMINCONSOLESESSION=8fMghRfnkcOls1wsW0vIRS8PuQKquWoYcnt6ciUG5uznDJiLr1ZA!-37
849198 Host = localhost:7001 Referer =
http://localhost:7001/console/actions/mbean/DoEditMBeanAction?MBean=vtsdomai
n%3AName%3DejbTestConnectionPool%2CType%3DJDBCConnectionPool User-Agent =
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.0.3705)
BrowserInfo
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0;
.NET CLR 1.0.3705)
IE: true
Netscape: false
Supported: true
JavscriptHrefs: false
TableCellClick: true
DocumentReloadedOnResize: false
DropdownStretchable: true
CellSpacingBlank: false
EmptyCellBlank: false
ImgOnclickSupported: true
TableBorderFancy: true
PartialToWideTables: false
DisabledControlSupported: true

Thanks, Joe. It works now!
"Joseph Weinstein" <[email protected]> wrote in message
news:[email protected]...
>
Vladimir wrote:
Here are the definitions of the two pools - both encounter the same
problem:
<JDBCConnectionPool DriverName="weblogic.jdbc.mssqlserver4.Driver"
Name="ejbTestConPool"
Properties="db=ejbTest;user=sa;port=1433;password=test;server=localhost"
TestConnectionsOnRelease="true" TestConnectionsOnReserve="true"
TestTableName="accounts" URL="weblogic:jdbc:mssqlserver4"/>yep, as I thought. A JDBC URL always starts with 'jdbc'. It should be
'jdbc:weblogic:mssqlserver4'. Also, make TestConnectionsOnRelease="false"
(it's a waste of cycles).
Joe
<JDBCConnectionPool DriverName="weblogic.jdbc.mssqlserver4.Driver"
Name="ejbTestConnectionPool" Password="{3DES}sCmdDszi61I="
Properties="user=sa;db=ejbTest;port=1433;password=test;server=localhost"
Targets="vtsserver" TestTableName="accounts"
URL="weblogic:jdbc:mssqlserver4"
XAPassword="{3DES}sCmdDszi61I="/>
>>
Vladimir
"Joseph Weinstein" <[email protected]> wrote in message
news:[email protected]...
show us your pool definitions from the config.xml file. There's
probably a
problem
with the URL or properties.
Joe
Vladimir wrote:
Hi, I get a java.lang.StringIndexOutOfBoundsException when making a
JDBC
pool connection via the console of WLS 7.0. I use SQL Server 2000in
Win2K
SP2 environment. Exactly the same configuration works perfectly in
WinXP
Pro. Can anyone advise me what might cause this problem? Thanks alot.
>>>>
Log message
####<May 13, 2002 5:15:52 PM CEST> <Error> <JDBC> <abcdefgh><vtsserver>
<ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'><kernel
identity> <> <001060> <Cannot startup connection pool
"ejbTestConnectionPool" java.lang.StringIndexOutOfBoundsException:String
index out of range: -1>
Exception
java.lang.NullPointerException
at
weblogic.management.console.utils.MBeans.getMBeanClassNameFor(MBeans.java:11
53)
at
weblogic.management.console.actions.mbean.EditMBeanAction.getMBeanClass(Edit
MBeanAction.java:210)
at
weblogic.management.console.actions.mbean.EditMBeanAction.getDialogTypeKey(E
ditMBeanAction.java:188)
at
weblogic.management.console.actions.internal.InternalActionContext.setAction
(InternalActionContext.java:158)
at
weblogic.management.console.actions.internal.ActionServlet.doAction(ActionSe
rvlet.java:170)
at
weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServ
let.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Servle
tStubImpl.java:945)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:332)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:242)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(W
ebAppServletContext.java:5363)
at
weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManage
r.java:721)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:3043)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
:2466)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
--------------- nested within: ------------------
weblogic.utils.NestedRuntimeException - with nested exception:
[java.lang.NullPointerException]
at
weblogic.management.console.utils.MBeans.getMBeanClassNameFor(MBeans.java:11
56)
at
weblogic.management.console.actions.mbean.EditMBeanAction.getMBeanClass(Edit
MBeanAction.java:210)
at
weblogic.management.console.actions.mbean.EditMBeanAction.getDialogTypeKey(E
ditMBeanAction.java:188)
at
weblogic.management.console.actions.internal.InternalActionContext.setAction
(InternalActionContext.java:158)
at
weblogic.management.console.actions.internal.ActionServlet.doAction(ActionSe
rvlet.java:170)
at
weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServ
let.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Servle
tStubImpl.java:945)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:332)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:242)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(W
ebAppServletContext.java:5363)
at
weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManage
r.java:721)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:3043)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
:2466)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
--------------- nested within: ------------------
weblogic.management.console.actions.ActionException - with nestedexception:
[weblogic.utils.NestedRuntimeException - with nested exception:
[java.lang.NullPointerException]]
atweblogic.management.console.actions.ErrorAction.(ErrorAction.java:38)
at
weblogic.management.console.actions.internal.ActionServlet.doAction(ActionSe
rvlet.java:190)
at
weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServ
let.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Servle
tStubImpl.java:945)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:332)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:242)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(W
ebAppServletContext.java:5363)
at
weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManage
r.java:721)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:3043)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
:2466)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
Current Date
Mon May 13 17:15:52 CEST 2002
Console Release Build
null
Console Build
null
Server Release Build
7.0.0.0
Server Build
WebLogic Server 7.0 Thu Apr 25 17:16:22 PDT 2002 180709
All Server Product Versions
WebLogic Server 7.0 Thu Apr 25 17:16:22 PDT 2002 180709
WebLogic XMLX Module 7.0 Thu Apr 25 17:26:07 PDT 2002 180709
Request Info
Protocol: HTTP/1.1
ServerName: localhost
ServerPort: 7001
Secure: false
ContextPath: /console
ServletPath: /common/error.jsp
QueryString:
MBean=vtsdomain%3AName%3DejbTestConnectionPool%2CType%3DJDBCConnectionPool
PathInfo: null
PathTranslated: null
RequestURI: /console/common/error.jsp
AuthType: null
ContentType: application/x-www-form-urlencoded
CharacterEncoding: null
Locale: en_US
Method: POST
Session:
weblogic.servlet.internal.session.MemorySessionData@1926bd
RequestedSessionId:
8fMghRfnkcOls1wsW0vIRS8PuQKquWoYcnt6ciUG5uznDJiLr1ZA!-37849198!1021299872710
RequestedSessionIdFromCookie: true
RequestedSessionIdFromURL: false
UserPrincipal: vts
RemoteUser: vts
RemoteAddr: 127.0.0.1
RemoteHost: 127.0.0.1
Parameters
MBean = vtsdomain:Name=ejbTestConnectionPool,Type=JDBCConnectionPool
chosen_wl_control_weblogic.management.configuration.JDBCConnectionPoolMBean.
Targets-Server = vtsdomain:Name=vtsserver,Type=Server
weblogic.console.submit_form = dataposted
wl_control_weblogic.management.configuration.JDBCConnectionPoolMBean.Targets
-Server = vtsdomain:Name=vtsserver,Type=Server
Attributes
wlinternalaction =
weblogic.management.console.actions.internal.InternalActionContext@4372d8
java.util.Locale = en_US weblogic.management.console.catalog.Catalog=
weblogic.management.console.catalog.XmlCatalog@3ca759
weblogic.management.console.helpers.BrowserHelper = User-Agent:Mozilla/4.0
(compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.0.3705) IE: trueNetscape:
false Supported: true JavscriptHrefs: false TableCellClick: true
DocumentReloadedOnResize: false DropdownStretchable: trueCellSpacingBlank:
false EmptyCellBlank: false ImgOnclickSupported: true
TableBorderFancy:
true
PartialToWideTables: false DisabledControlSupported: true
weblogic.management.console.helpers.DebugHelper =
weblogic.management.console.helpers.DebugHelper@16ed83
weblogic.management.console.helpers.UnitsHelper =
weblogic.management.console.helpers.UnitsHelper@ae2d9
weblogic.management.console.helpers.UrlHelper =
weblogic.management.console.helpers.UrlHelper@28fd41
Headers
Accept = image/gif, image/x-xbitmap, image/jpeg, image/pjpeg,
application/vnd.ms-excel, application/vnd.ms-powerpoint,application/msword,
*/* Accept-Encoding = gzip, deflate Accept-Language = en-usCache-Control =
no-cache Connection = Keep-Alive Content-Length = 304 Content-Type =
application/x-www-form-urlencoded Cookie =
ADMINCONSOLESESSION=8fMghRfnkcOls1wsW0vIRS8PuQKquWoYcnt6ciUG5uznDJiLr1ZA!-37
849198 Host = localhost:7001 Referer =
http://localhost:7001/console/actions/mbean/DoEditMBeanAction?MBean=vtsdomai
n%3AName%3DejbTestConnectionPool%2CType%3DJDBCConnectionPoolUser-Agent
=
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR
1.0.3705)
BrowserInfo
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; WindowsNT
5.0;
.NET CLR 1.0.3705)
IE: true
Netscape: false
Supported: true
JavscriptHrefs: false
TableCellClick: true
DocumentReloadedOnResize: false
DropdownStretchable: true
CellSpacingBlank: false
EmptyCellBlank: false
ImgOnclickSupported: true
TableBorderFancy: true
PartialToWideTables: false
DisabledControlSupported: true

What jar contains weblogic.jdbc.pool.Driver connection pool class?

Hi all,
I am trying to use the JDeveloper IDE to generate code that I'll deploy on WebLogic
6.1.
I want to add the necessary files to the JDeveloper classpath so that during development
it can use my
weblogic connection pool. I've looked all over and can't seem to find it. It's
not in weblogic.jar. Anyone know
what file contains weblogic.jdbc.pool.Driver?
Thanks in advance,
Norm

Thanks. I don't know how I missed it in the first place.
"Sree Bodapati" <[email protected]> wrote:
weblogic.jar
sree
"Norm Heske" <[email protected]> wrote in message
news:3ba246c2$[email protected]..
Hi all,
I am trying to use the JDeveloper IDE to generate code that I'll deployon
WebLogic
6.1.
I want to add the necessary files to the JDeveloper classpath so thatduring development
it can use my
weblogic connection pool. I've looked all over and can't seem to findit.
It's
not in weblogic.jar. Anyone know
what file contains weblogic.jdbc.pool.Driver?
Thanks in advance,
Norm

Java.lang.ClassCastException: weblogic.jdbc.wrapper.Blob_oracle_sql_BLOB??

Hello. I'm trying to bring back a BLOB object from a PL/SQL procedure. I keep getting a class cast exception when I do it
java.lang.ClassCastException: weblogic.jdbc.wrapper.Blob_oracle_sql_BLOB cannot be cast to oracle.sql.BLOB
I get similar results with oracle.sql.BLOB or java.sql.Blob.
What I've noticed is that when I'm not using a JDBC URL with my AM to do the SQL it does not fail. It's when I change to a JDBC Datasource I get the class cast exception. Any ideas?
Thanks, Graeme.

In the connection pool uncheck the property "Wrap Data Types".
By default, data type objects for Array, Blob, Clob, NClob, Ref, SQLXML, and Struct, plus ParameterMetaData and ResultSetMetaData objects are wrapped with a WebLogic wrapper. This allows for features like debugging and connection usage to be done by the server.
The wrapping can be turned off by setting this value to false. This improves performance, in some cases significantly, and allows for the application to use the native driver objects directly.

Java.lang.ClassNotFoundException: weblogic/jdbc/mssqlserver4/Driver

Hello,
I am moving my database from Sybase to SQL Server. I have a program that ran fine with JConnect driver (Sybase) on both unix and windows. But now when I try to use the weblogic driver to connect to SQL Server the program fails. I am 100% positive that the weblogic drive is in the classpath. Whether the weblogic drive is in the classpath or not I get the same error:
Unexpected error:java.lang.ClassNotFoundException: weblogic/jdbc/mssqlserver4/Driver
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:124)
at com.trilogy.tools.core.DBUtil.loadDriver(DBUtil.java:16)
at com.trilogy.loader.core.LoadInitUtil.<init>(Compiled Code)
at com.trilogy.loader.mass.MassInitUtil.<init>(MassInitUtil.java:15)
at com.trilogy.loader.mass.Loader2CLI.execute(Compiled Code)
at com.trilogy.tools.core.CLIBase.execute(CLIBase.java:45)
at com.trilogy.loader.mass.Loader2CLI.main(Loader2CLI.java:805)
java.lang.NullPointerException
at com.trilogy.loader.mass.Loader2CLI.execute(Compiled Code)
at com.trilogy.tools.core.CLIBase.execute(CLIBase.java:45)
at com.trilogy.loader.mass.Loader2CLI.main(Loader2CLI.java:805)
Pease help me fix this problem. I am not sure why the weblogic driver is not working. Thanks.

The error message says it can't find a class named "weblogic.jdbc.mssqlserver4.Driver". That looks rather odd to me.
Are you sure that you defined the connection information correctly in the configuration file?

Exception in thread "main" java.lang.NoClassDefFoundError: oracle/jdbc/pool

I have the following configuration:
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
on a Suse 10.1 Linux.
The javaversion is Java.Version = 1.4.2_11
The classpath does look like:
Eisele@brezn:~/FH-Weihenstephan/Winter_Semester_200809/Uebungen> echo $CLASSPATH
/derby.jar:/derbytools.jar:/derbynet.jar:/derbyclient.jar:/derbyTesting.jar:/local/derby/tools/java/jakarta-oro-2.0.8.jar:/derbyLocale_de_DE.jar:/derbyLocale_es.jar:/derbyLocale_fr.jar:/derbyLocale_it.jar:/derbyLocale_ja_JP.jar:/derbyLocale_ko_KR.jar:/derbyLocale_pt_BR.jar:/derbyLocale_zh_CN.jar:/derbyLocale_zh_TW.jar:/oracle/oracle/product/10.2.0/db_1/jdbc/lib/classes12.jar:/oracle/oracle/product/10.2.0/db_1/jdbc/lib/classes12.zip:/oracle/oracle/product/10.2.0/db_1/jlib/orai18n.jar:/oracle/oracle/product/10.2.0/db_1/jdbc/lib/ojdbc14.jar:/home/Eisele/Oracle/ojdbc14.jar:/home/Eisele/FH-Weihenstephan/Winter_Semester_200809/Uebungen
Eisele@brezn:~/FH-Weihenstephan/Winter_Semester_200809/Uebungen>
The Program JDBCVersion.java which I copied out of the Oracle-Documentation looks like:
import java.sql.*;
import oracle.jdbc.*;
import oracle.jdbc.pool.OracleDataSource;
class JDBCVersion
public static void main (String args[]) throws SQLException
System.out.println("Java.Version = " + System.getProperty("java.version")) ;
OracleDataSource ods = new OracleDataSource();
ods.setURL("jdbc:oracle:thin:scott/tiger@host:port:service");
Connection conn = ods.getConnection();
// Create Oracle DatabaseMetaData object
DatabaseMetaData meta = conn.getMetaData();
// gets driver info:
System.out.println("JDBC driver version is " + meta.getDriverVersion());
I get the following error
Eisele@brezn:~/FH-Weihenstephan/Winter_Semester_200809/Uebungen> javac JDBCVersion.java
Eisele@brezn:~/FH-Weihenstephan/Winter_Semester_200809/Uebungen> java -cp ~/FH-Weihenstephan/Winter_Semester_200809/Uebungen/ JDBCVersion
Java.Version = 1.4.2_11
Exception in thread "main" java.lang.NoClassDefFoundError: oracle/jdbc/pool/OracleDataSource
at JDBCVersion.main(JDBCVersion.java:10)
Eisele@brezn:~/FH-Weihenstephan/Winter_Semester_200809/Uebungen>
Can anyone help me out here and tell me, what I did wrong ?
Thanks in advance !
Rüdiger

Two thoughts.
The first is that 10.2.0.1 is unpatched. Why? It has been two years since its release and no one has applied 10.2.0.2, 10.2.0.3 or 10.2.0.4.
The second is that your question is not a database question but a Java question is you are more likely to get an answer that will help you if you post in a group where it is on-topic.

Java.io.NotSerializableException: oracle.jdbc.driver.T4CConnection

Hi,
I am using weblogic 9.2 on windows. I have the data source configured(Oracle 9.2)
I am getting the following exception when I try to create temporaryBlob -
BLOB blob = BLOB.createTemporary(conn, false,
                    BLOB.DURATION_SESSION);
Exception messages ------
Exception in thread "main" weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception
     at weblogic.jdbc.rmi.internal.ConnectionImpl_weblogic_jdbc_wrapper_PoolConnection_oracle_jdbc_driver_T4CConnection_920_WLStub.physicalConnectionWithin(Unknown Source)
     at weblogic.jdbc.rmi.SerialConnection_weblogic_jdbc_rmi_internal_ConnectionImpl_weblogic_jdbc_wrapper_PoolConnection_oracle_jdbc_driver_T4CConnection_920_WLStub.physicalConnectionWithin(Unknown Source)
     at oracle.sql.BLOB.createTemporary(BLOB.java:587)
     at com.hp.nuoss.fm.cs.test.SessionBeanClient.testInsertBLOBData(SessionBeanClient.java:109)
     at com.hp.nuoss.fm.cs.test.SessionBeanClient.main(SessionBeanClient.java:154)
Caused by: java.rmi.MarshalException: error marshalling return; nested exception is:
     java.io.NotSerializableException: oracle.jdbc.driver.T4CConnection
     at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:195)
     at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:224)
     ... 5 more
Caused by: java.io.NotSerializableException: oracle.jdbc.driver.T4CConnection
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1075)
     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:291)
     at weblogic.rjvm.MsgAbbrevOutputStream.writeObject(MsgAbbrevOutputStream.java:614)
     at weblogic.utils.io.ChunkedObjectOutputStream.writeObject(ChunkedObjectOutputStream.java:73)
     at weblogic.jdbc.rmi.internal.ConnectionImpl_weblogic_jdbc_wrapper_PoolConnection_oracle_jdbc_driver_T4CConnection_WLSkel.internalInvoke1(Unknown Source)
     at weblogic.jdbc.rmi.internal.ConnectionImpl_weblogic_jdbc_wrapper_PoolConnection_oracle_jdbc_driver_T4CConnection_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:517)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:407)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:403)
     at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:56)
     at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:934)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

Someone else had this same problem and they seem to have solved it:
http://forum.java.sun.com/thread.jspa?threadID=5105589&messageID=9363332
I guess SessionBean1 is not serializable perhaps because it doesn't implement Serializable, and the writeObject method in StandardSession is trying to write it to disk (trying to serialize it).
Try changing SessionBean 1 to
public class SessionBean1 implements Serializable{
}

Java.io.NotSerializableException: weblogic.ejb20.internal.EntityEJBContextImpl

Hi,
We are currently in the process of moving from Weblogic 6.1 SP5 and
Toplink 3.6.3 to Weblogic 8.1 SP2 and Toplink 9.0.4 and during some test
I have seen a "scaring" stack trace. It seems that, for some reason, a
thing that "uses to work" failed with a very strange error. I tried to
reproduce it but without any success. Besides asking if anybody knows
what could have caused this error I would like to know what the "not
serializable" object is. Is it the EntityEJBContext?
<12-09-2004 4:40' GMT> <Error> <app> <000000> <[thread 5
weblogic.kernel.Default]:Exception:
javax.transaction.TransactionRolledbackException at getXML
javax.transaction.TransactionRolledbackException: EJB Exception: :
java.io.NotSerializableException:
weblogic.ejb20.internal.EntityEJBContextImpl
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at
weblogic.rmi.internal.CBVOutputStream.writeObject(CBVOutputStream.java:78)
at weblogic.rmi.internal.ServerRequest.copy(ServerRequest.java:218)
at
weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:158)
at
weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
at
app.data.production.ProductionBean_3toa0w_EOImpl_811_WLStub.EJB2DOM(Unknown
Source)
In case it could share some light in the case I will explain a bit what
does the process intended to do:
The general idea is that, given some data (managed with Toplink's 9.0.4
CMP) we take a XML "snapshot" of them (via a custom OBJ2XML class that
has been working for ages without any problem) and "publish" it via JMS
in order to perform asyncronous actions with it. I'm sure this is a,
more than usual, scenario for a lot of folks.
As it seems looking at the stack at some point during some internal
object serialization it fails and rollbacks all the process. The object
being serialized by our side only contains four attributes: a
java.math.BigDecimal for it's primary key, a java.util.Date for
timestamp locking and two simple java.lang.String's
Although I'm pretty sure the problem should not be with the entity bean
itself but with an internal Weblogic op (is it trying to serialize the
EntityBeanContext as stated after the java.io.NotSerializableException
message?
Any help with this would be greatly appreciated as I have no clue how
this happened and I'm also unable to reproduce it (I'm also sure if I
managed to trigger it testing the application alone it will rise many
more times that could be admited if we move to production).
I would like to point also that currently until we have some more time
to fix it we are using "remote" entity bean, I mean even if we are alway
s calling them within the container they are not deployed with "local"
interfaces yet (although AFAIK Weblogic should avoid RMI calls on them
being co-located with the session beans).
Regards.
Ignacio.
P.S. here is the full stack dump
<12-09-2004 4:40' GMT> <Error> <app> <000000> <[thread 5
weblogic.kernel.Default]:Exception:
javax.transaction.TransactionRolledbackException at getXML
javax.transaction.TransactionRolledbackException: EJB Exception: :
java.io.NotSerializableException:
weblogic.ejb20.internal.EntityEJBContextImpl
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at
weblogic.rmi.internal.CBVOutputStream.writeObject(CBVOutputStream.java:78)
at weblogic.rmi.internal.ServerRequest.copy(ServerRequest.java:218)
at
weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:158)
at
weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
at
app.data.production.ProductionBean_3toa0w_EOImpl_811_WLStub.EJB2DOM(Unknown
Source)
at app.data.general.GeneralBean.EJB2DOM(GeneralBean.java:1180)
at
app.data.module.ModuleBean_1v2h9c_EOImpl.EJB2DOM(ModuleBean_1v2h9c_EOImpl.java:3954)
at app.data.general.GeneralBean.EJB2DOM(GeneralBean.java:1180)
at app.data.general.GeneralBean.getXML(GeneralBean.java:1024)
at app.data.general.GeneralBean.getXML(GeneralBean.java:1002)
at
app.data.module.ModuleBean_nw294k_EOImpl.getXML(ModuleBean_nw294k_EOImpl.java:3138)
at app.biz.common.Publisher.performPublication(Publisher.java:1644)
at app.biz.common.Publisher.launchPublisher(Publisher.java:1580)
at app.biz.module.ModuleDAO.update(ModuleDAO.java)
at
app.biz.module.ModuleDAO_jcgreo_EOImpl.update(ModuleDAO_jcgreo_EOImpl.java:100)
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:324)
at app.core.util.Proxy.execute(Proxy.java:583)
at app.core.servlet.BaseServlet.execute(BaseServlet.java:440)
at
app.user.servlet.common.BaseServlet.accessSessionBean(BaseServlet.java:279)
at
app.user.servlet.common.BaseServlet.buildResponse(BaseServlet.java:132)
at app.core.servlet.BaseServlet.doGet(BaseServlet.java:116)
at app.core.servlet.BaseServlet.doPost(BaseServlet.java:154)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6310)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3622)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>

Ignacio,
6.1 used pass-by-reference by default, so parameters to beans were
passed by reference.
It's very likely that you are getting this error because in 8.1 this default
was turned off. This causes serialization of parameters by default and
that's why your code that worked started failing - you just did not know
that you were passing non-serializable objects around.
To fix this you could either turn on the pass-by-reference explicitly and/or
find out where your code is passing non-serializable objects. This is a useful
exercise anyways.
Hope this helps.
Regards,
Slava Imeshev
"Ignacio G. Dupont" <[email protected]> wrote in message news:41b8c93f@mail...
Hi,
We are currently in the process of moving from Weblogic 6.1 SP5 and
Toplink 3.6.3 to Weblogic 8.1 SP2 and Toplink 9.0.4 and during some test
I have seen a "scaring" stack trace. It seems that, for some reason, a
thing that "uses to work" failed with a very strange error. I tried to
reproduce it but without any success. Besides asking if anybody knows
what could have caused this error I would like to know what the "not
serializable" object is. Is it the EntityEJBContext?
<12-09-2004 4:40' GMT> <Error> <app> <000000> <[thread 5
weblogic.kernel.Default]:Exception:
javax.transaction.TransactionRolledbackException at getXML
javax.transaction.TransactionRolledbackException: EJB Exception: :
java.io.NotSerializableException:
weblogic.ejb20.internal.EntityEJBContextImpl
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at
weblogic.rmi.internal.CBVOutputStream.writeObject(CBVOutputStream.java:78)
at weblogic.rmi.internal.ServerRequest.copy(ServerRequest.java:218)
at
weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:158)
at
weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
at
app.data.production.ProductionBean_3toa0w_EOImpl_811_WLStub.EJB2DOM(Unknown
Source)
In case it could share some light in the case I will explain a bit what
does the process intended to do:
The general idea is that, given some data (managed with Toplink's 9.0.4
CMP) we take a XML "snapshot" of them (via a custom OBJ2XML class that
has been working for ages without any problem) and "publish" it via JMS
in order to perform asyncronous actions with it. I'm sure this is a,
more than usual, scenario for a lot of folks.
As it seems looking at the stack at some point during some internal
object serialization it fails and rollbacks all the process. The object
being serialized by our side only contains four attributes: a
java.math.BigDecimal for it's primary key, a java.util.Date for
timestamp locking and two simple java.lang.String's
Although I'm pretty sure the problem should not be with the entity bean
itself but with an internal Weblogic op (is it trying to serialize the
EntityBeanContext as stated after the java.io.NotSerializableException
message?
Any help with this would be greatly appreciated as I have no clue how
this happened and I'm also unable to reproduce it (I'm also sure if I
managed to trigger it testing the application alone it will rise many
more times that could be admited if we move to production).
I would like to point also that currently until we have some more time
to fix it we are using "remote" entity bean, I mean even if we are alway
s calling them within the container they are not deployed with "local"
interfaces yet (although AFAIK Weblogic should avoid RMI calls on them
being co-located with the session beans).
Regards.
Ignacio.
P.S. here is the full stack dump
<12-09-2004 4:40' GMT> <Error> <app> <000000> <[thread 5
weblogic.kernel.Default]:Exception:
javax.transaction.TransactionRolledbackException at getXML
javax.transaction.TransactionRolledbackException: EJB Exception: :
java.io.NotSerializableException:
weblogic.ejb20.internal.EntityEJBContextImpl
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at
weblogic.rmi.internal.CBVOutputStream.writeObject(CBVOutputStream.java:78)
at weblogic.rmi.internal.ServerRequest.copy(ServerRequest.java:218)
at
weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:158)
at
weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
at
app.data.production.ProductionBean_3toa0w_EOImpl_811_WLStub.EJB2DOM(Unknown
Source)
at app.data.general.GeneralBean.EJB2DOM(GeneralBean.java:1180)
at
app.data.module.ModuleBean_1v2h9c_EOImpl.EJB2DOM(ModuleBean_1v2h9c_EOImpl.java:3954)
at app.data.general.GeneralBean.EJB2DOM(GeneralBean.java:1180)
at app.data.general.GeneralBean.getXML(GeneralBean.java:1024)
at app.data.general.GeneralBean.getXML(GeneralBean.java:1002)
at
app.data.module.ModuleBean_nw294k_EOImpl.getXML(ModuleBean_nw294k_EOImpl.java:3138)
at app.biz.common.Publisher.performPublication(Publisher.java:1644)
at app.biz.common.Publisher.launchPublisher(Publisher.java:1580)
at app.biz.module.ModuleDAO.update(ModuleDAO.java)
at
app.biz.module.ModuleDAO_jcgreo_EOImpl.update(ModuleDAO_jcgreo_EOImpl.java:100)
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:324)
at app.core.util.Proxy.execute(Proxy.java:583)
at app.core.servlet.BaseServlet.execute(BaseServlet.java:440)
at
app.user.servlet.common.BaseServlet.accessSessionBean(BaseServlet.java:279)
at
app.user.servlet.common.BaseServlet.buildResponse(BaseServlet.java:132)
at app.core.servlet.BaseServlet.doGet(BaseServlet.java:116)
at app.core.servlet.BaseServlet.doPost(BaseServlet.java:154)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6310)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3622)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>

XA resource [weblogic.jdbc.jts.Connection] has not responded in the last 120 second(s).

I frequently encounter this problem: The application calls long-lasting stored
procedure on Sybase which located in another country. Sometimes, WL 6.1 get stuck
just and log the message "XA resource [weblogic.jdbc.jts.Connection] has not responded
in the last 120 second(s)."
Questions:
Does increasing thread count help? Default is 15. Is 30 or larger OK?
Can anybody share their experience on this matter?
Detailed log messages in weblogic.log are follows:
####<Apr 21, 2003 5:03:48 PM GMT+08:00> <Warning> <JTA> <hkxp0032> <myserver>
<Thread-0> <> <> <110030> <XA resource [weblogic.jdbc.jts.Connection] has not
responded in the last 120 second(s).>
####<Apr 21, 2003 5:33:51 PM GMT+08:00> <Info> <JTA> <hkxp0032> <myserver> <Thread-0>
<> <> <110207> <Previously unavailable XA resource [weblogic.jdbc.jts.Connection]
is now available.>
####<Apr 21, 2003 5:33:56 PM GMT+08:00> <Warning> <JTA> <hkxp0032> <myserver>
<Thread-0> <> <> <110030> <XA resource [weblogic.jdbc.jts.Connection] has not
responded in the last 120 second(s).>

Andrew Ng wrote:
I frequently encounter this problem: The application calls long-lasting stored
procedure on Sybase which located in another country. Sometimes, WL 6.1 get stuck
just and log the message "XA resource [weblogic.jdbc.jts.Connection] has not responded
in the last 120 second(s)."
Questions:
Does increasing thread count help? Default is 15. Is 30 or larger OK?Increasing thread count isn't going to help. The local server is just waiting for the
remote system to respond.
>
Can anybody share their experience on this matter?
Detailed log messages in weblogic.log are follows:
####<Apr 21, 2003 5:03:48 PM GMT+08:00> <Warning> <JTA> <hkxp0032> <myserver>
<Thread-0> <> <> <110030> <XA resource [weblogic.jdbc.jts.Connection] has not
responded in the last 120 second(s).>
####<Apr 21, 2003 5:33:51 PM GMT+08:00> <Info> <JTA> <hkxp0032> <myserver> <Thread-0>
<> <> <110207> <Previously unavailable XA resource [weblogic.jdbc.jts.Connection]
is now available.>
####<Apr 21, 2003 5:33:56 PM GMT+08:00> <Warning> <JTA> <hkxp0032> <myserver>
<Thread-0> <> <> <110030> <XA resource [weblogic.jdbc.jts.Connection] has not
responded in the last 120 second(s).>

ClassNotFoundException: weblogic/jdbc/pool/Driver

          Hi,
          I was able to run the sql example in the jsp\tagext directory.
          The ConnectionTag tag contains basically code like:
          Class.forName("weblogic.jdbc.pool.Driver").newInstance();
          which works fine.
          Next, I moved the code into a utility package, which I
          compiled into the public_html\WEB-INF\classes directory. This
          code is called from within a servlet.
          Strangely enough, when I run the servlet, I get the
          ClassNotFoundException: weblogic/jdbc/pool/Driver error.
          It is as if the servlet does not have access to the
          weblogic.jdbc.pool.Driver class while the tag library does.
          What am I doing wrong?
          Thanks,
          Vladimir


You must include the path to jdbc driver in the script wich you start the
          server.
          WEBLOGIC_CLASSPATH
          vladimir <[email protected]> escribió en el mensaje de noticias
          39bcdf0c$[email protected]..
          >
          > Hi,
          >
          > I was able to run the sql example in the jsp\tagext directory.
          > The ConnectionTag tag contains basically code like:
          >
          > Class.forName("weblogic.jdbc.pool.Driver").newInstance();
          >
          > which works fine.
          >
          > Next, I moved the code into a utility package, which I
          > compiled into the public_html\WEB-INF\classes directory. This
          > code is called from within a servlet.
          >
          > Strangely enough, when I run the servlet, I get the
          > ClassNotFoundException: weblogic/jdbc/pool/Driver error.
          > It is as if the servlet does not have access to the
          > weblogic.jdbc.pool.Driver class while the tag library does.
          >
          > What am I doing wrong?
          >
          > Thanks,
          > Vladimir
          >

Repost: ClassNotFoundException: weblogic/jdbc/pool/Driver

          Hi,
          I was able to run the sql example in the jsp\tagext directory. The ConnectionTag tag contains basically code like:
          Class.forName("weblogic.jdbc.pool.Driver").newInstance();
          which works fine.
          Next, I moved the code into a utility package, which I compiled into the public_html\WEB-INF\classes directory. This code is called from within a servlet.
          Strangely enough, when I run the servlet, I get the ClassNotFoundException: weblogic/jdbc/pool/Driver error. It is as if the servlet does not have access to the weblogic.jdbc.pool.Driver class while the tag library does.
          What am I doing wrong?
          Thanks, Vladimir


          Hi,
          I was able to run the sql example in the jsp\tagext directory. The ConnectionTag tag contains basically code like:
          Class.forName("weblogic.jdbc.pool.Driver").newInstance();
          which works fine.
          Next, I moved the code into a utility package, which I compiled into the public_html\WEB-INF\classes directory. This code is called from within a servlet.
          Strangely enough, when I run the servlet, I get the ClassNotFoundException: weblogic/jdbc/pool/Driver error. It is as if the servlet does not have access to the weblogic.jdbc.pool.Driver class while the tag library does.
          What am I doing wrong?
          Thanks, Vladimir

What are the correct parameter names for a JDBC pool connection?

Looking in the admin console I notice the differences in the properties name (type casting) of PointBasePool and __TimerPool pool connections properties and the create wizard properties.
PointBasePool and __TimerPool uses this name parameters: User,Password, and DatabaseName.
Create wizard uses these: databaseName, user, password.
So, then, what is the standard names for a connection in SOA8? What is the standard for JDBC?
For example, Tomcat 4 uses username, password, url, driverClassName as parameters names.
Please help,
This is getting more and more confising,
Thanks,
Lorenzo Jimenez

The properties that you specify when creating the connection pool are unique to the vendor.
Any or the properties that you specify user,password, url...etc we expect to have setters (setUser, setPassword, setUrl)
let me know if need more info

Re: Internal error: XAResource 'weblogic.jdbc.jts.Connection'

Has anyone found a resolution to this problem? I just opened a case with BEA but am hoping that someone has learned what this problem is and how to solve it..Any ideas?Thanks!Steve

Weblogic 8.1 Connection Pool and jta

Hi ! I am getting the below exception while migrating my application from weblogic
6.1sp2 to weblogic 8.1. When I migrate to weblogic 7.0 sp2 there are no problems.
The problem occurs specifically when I save an record using a container managed
transaction thru a stateless session bean. The save itself works, but when I
refresh my JSP, I get the following exception. Keep in mind that the same application
works fine in 7.0.
Thanks,
Eddie
java.sql.SQLException: Cannot obtain connection: driverURL = jdbc:weblogic:pool:Sybdev07Pool,
props = {enableTwoPhaseCommit=true, jdbcTxDataSource=true, connectionPoolID=Sybdev07Pool,
dataSourceName=sdaapadrDB}. Nested Exception: java.lang.RuntimeException: Failed
to setAutoCommit to true for pool connection. at weblogic.jdbc.wrapper.PoolConnection.init(PoolConnection.java:38)
at weblogic.jdbc.pool.Driver.allocateConnection(Driver.java:248) at weblogic.jdbc.pool.Driver.connect(Driver.java:158)
at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:444) at weblogic.jdbc.jts.Driver.connect(Driver.java:138)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:298)
at

Hi Eddie,
"Eddie Baue" <[email protected]> wrote in message
news:[email protected]...
In addition to the exception below, which is displayed on the browser,the
weblogic server log has the following error:
####<Aug 1, 2003 11:50:24 AM EDT> <Warning> <JDBC> <6X19DYSZH1ZV><wla_adruat>
<Finalizer> <<anonymous>> <> <BEA-001074> <A JDBC pool connection leak wasdetected.
A connection leak occurs when a connection obtained from the pool was notclosed
explicitly by calling close() and then was disposed by the garbagecollector and
returned to the connection pool. The following stack trace at create showswhere
the leaked connection was created. [Null exception passed, creating stack
trace> for offending caller
atweblogic.utils.StackTraceUtils.throwable2StackTrace(StackTraceUtils.java:28)
at weblogic.jdbc.wrapper.PoolConnection.finalize(PoolConnection.java:69)
at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)
at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:83)
at java.lang.ref.Finalizer.access$100(Finalizer.java:14)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:160)The only case it's possible is when the weblogic.jdbc.wrapper.PoolConnection
failed during instantiation process and GC kicked in before the
Throwable holding stack trace at create was initialized.
I believe this is the result of the exception below and you can not see
this under normal circumstances.
Regards,
Slava Imeshev
>
Any info would be greatly appreciated.
Thanks,
Eddie
"Eddie Baue" <[email protected]> wrote:
Hi ! I am getting the below exception while migrating my application
from weblogic
6.1sp2 to weblogic 8.1. When I migrate to weblogic 7.0 sp2 there are
no problems.
The problem occurs specifically when I save an record using a container
managed
transaction thru a stateless session bean. The save itself works, but
when I
refresh my JSP, I get the following exception. Keep in mind that the
same application
works fine in 7.0.
Thanks,
Eddie
java.sql.SQLException: Cannot obtain connection: driverURL =
jdbc:weblogic:pool:Sybdev07Pool,
props = {enableTwoPhaseCommit=true, jdbcTxDataSource=true,connectionPoolID=Sybdev07Pool,> >dataSourceName=sdaapadrDB. Nested Exception: java.lang.RuntimeException:
Failed
to setAutoCommit to true for pool connection. at
weblogic.jdbc.wrapper.PoolConnection.init(PoolConnection.java:38)
at weblogic.jdbc.pool.Driver.allocateConnection(Driver.java:248) atweblogic.jdbc.pool.Driver.connect(Driver.java:158)
at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:444) atweblogic.jdbc.jts.Driver.connect(Driver.java:138)
atweblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java
:298)
at

Java.io.notSerializableException:weblogic.jdbc.pool.Connection

Similar Messages

Maybe you are looking for