XA Transaction & JDBC Store
We configured our jms servers using a jdbc backing store. We had an MDB that would
not deploy because the connection factory did not support transaction (we had
only checked the User Transaction box). We enabled XA Transactions and all was
fine.
The manual states that this configuration (a connection factory that supprts XA
Transaction and a jdbc based store) is not supported. Is this still accurate as
of WL7 sp 2, as Weblogic doesn't throw an exception? Should we switch to a filebased
store?
thanks
Sorry about this, I thought we were using an XA JDBC driver and we weren't (We
are using the XA-enabled flag, however). That's why it works.
"weblogic user" <[email protected]> wrote:
>
>We configured our jms servers using a jdbc backing store. We had an
>MDB that would
>not deploy because the connection factory did not support transaction
>(we had
>only checked the User Transaction box). We enabled XA Transactions and
>all was
>fine.
>
>The manual states that this configuration (a connection factory that
>supprts XA
>Transaction and a jdbc based store) is not supported. Is this still accurate
>as
>of WL7 sp 2, as Weblogic doesn't throw an exception? Should we switch
>to a filebased
>store?
>
>thanks
>
Similar Messages
-
JMS JDBC store failed to open after switched to a different database machine
Hi,
I'm running WebLogic 6.1 sp3/Oracle 8.1.6 and I configure the JMS JDBC store for
persistent messaging. I was working fine until I switched to use a different database
machine which has the same software configuration as the old one. It was giving
me "failed to create tables" error at start up time. But I checked the database
and found out the two tables (<prefix>JMSSTORE and <prefix>JMSSTATE) were both
created and I was able to query although they don't contain any data. By the way,
I'm using thin client.
Anyone can help? Thanks a lot!
Here's the exception:
<Jul 23, 2003 4:33:10 PM PDT> <Alert> <JMS> <JMSServer "notifyServer", store failed
to open, java.io.IOException: JMS JDBC store, connection pool = <jmsPool>, prefix
= <qa.JMS_SERVER_>: failed to create tables.
java.io.IOException: JMS JDBC store, connection pool = <jmsPool>, prefix = <qa.JMS_SERVER_>:
failed to create tables
at weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:311)
at weblogic.jms.store.JDBCIOStream.rebuildTables(JDBCIOStream.java:1400)
at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:376)
at weblogic.jms.store.JMSStore.open(JMSStore.java:110)
at weblogic.jms.backend.BEStore.open(BEStore.java:180)
at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:390)
at weblogic.jms.JMSService.createBackEnd(JMSService.java:906)
at weblogic.jms.JMSService.addJMSServer(JMSService.java:1273)
at weblogic.jms.JMSService.addDeployment(JMSService.java:1169)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:360)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:285)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:239)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:199)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy39.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2977)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:372)
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy58.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
at weblogic.management.Admin.finish(Admin.java:644)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
at weblogic.Server.main(Server.java:35)
>
<Jul 23, 2003 4:33:10 PM PDT> <Error> <JMS> <Failed to deploy JMS Server "notifyServer"
due to weblogic.jms.common.ConfigurationException: JMS can not open store.
weblogic.jms.common.ConfigurationException: JMS can not open store
at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:395)
at weblogic.jms.JMSService.createBackEnd(JMSService.java:906)
at weblogic.jms.JMSService.addJMSServer(JMSService.java:1273)
at weblogic.jms.JMSService.addDeployment(JMSService.java:1169)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:360)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:285)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:239)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:199)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy39.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2977)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:372)
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy58.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
at weblogic.management.Admin.finish(Admin.java:644)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
at weblogic.Server.main(Server.java:35)
----------- Linked Exception -----------
java.io.IOException: JMS JDBC store, connection pool = <jmsPool>, prefix = <qa.JMS_SERVER_>:
failed to create tables
at weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:311)
at weblogic.jms.store.JDBCIOStream.rebuildTables(JDBCIOStream.java:1400)
at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:376)
at weblogic.jms.store.JMSStore.open(JMSStore.java:110)
at weblogic.jms.backend.BEStore.open(BEStore.java:180)
at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:390)
at weblogic.jms.JMSService.createBackEnd(JMSService.java:906)
at weblogic.jms.JMSService.addJMSServer(JMSService.java:1273)
at weblogic.jms.JMSService.addDeployment(JMSService.java:1169)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:360)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:285)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:239)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:199)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy39.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2977)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:372)
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy58.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
at weblogic.management.Admin.finish(Admin.java:644)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
at weblogic.Server.main(Server.java:35)
>
Hi Michelle,
I suspect a permission problem where the new tables are created
using the JDBC driver's default schema, but the prefix
specifies another schema "qa". So the tables are getting
created, but aren't found.
Work-around one:
manually extract, edit, and run the ddl that creates
the tables to specify the schema. Prepend
"qa.JMS_SERVER_" to all table names
(This is fairly simple to do.)
http://edocs.bea.com/wls/docs61/jms/appb.html#999286
Work-around two:
Don't include "qa." in the prefix.
(i'm not sure if this will work)
Work-around three:
Change the username of the JDBC pool to "qa".
(i'm not sure if this will work)
Work-around four:
Change the schema for the tables that were created
under the JDBC driver's default schema to "qa".
(I'm not sure how this is done, or even
if it is possible. Database specific.)
Tom
Michelle Lian wrote:
> Hi,
>
> I'm running WebLogic 6.1 sp3/Oracle 8.1.6 and I configure the JMS JDBC store for
> persistent messaging. I was working fine until I switched to use a different database
> machine which has the same software configuration as the old one. It was giving
> me "failed to create tables" error at start up time. But I checked the database
> and found out the two tables (<prefix>JMSSTORE and <prefix>JMSSTATE) were both
> created and I was able to query although they don't contain any data. By the way,
> I'm using thin client.
>
> Anyone can help? Thanks a lot!
>
> Here's the exception:
>
> <Jul 23, 2003 4:33:10 PM PDT> <Alert> <JMS> <JMSServer "notifyServer", store failed
> to open, java.io.IOException: JMS JDBC store, connection pool = <jmsPool>, prefix
> = <qa.JMS_SERVER_>: failed to create tables.
> java.io.IOException: JMS JDBC store, connection pool = <jmsPool>, prefix = <qa.JMS_SERVER_>:
> failed to create tables
> at weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:311)
> at weblogic.jms.store.JDBCIOStream.rebuildTables(JDBCIOStream.java:1400)
> at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:376)
> at weblogic.jms.store.JMSStore.open(JMSStore.java:110)
> at weblogic.jms.backend.BEStore.open(BEStore.java:180)
> at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:390)
> at weblogic.jms.JMSService.createBackEnd(JMSService.java:906)
> at weblogic.jms.JMSService.addJMSServer(JMSService.java:1273)
> at weblogic.jms.JMSService.addDeployment(JMSService.java:1169)
> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:360)
> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:285)
> at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:239)
> at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:199)
> at java.lang.reflect.Method.invoke(Native Method)
> at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
> at $Proxy39.updateDeployments(Unknown Source)
> at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2977)
> at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:372)
> at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
> at java.lang.reflect.Method.invoke(Native Method)
> at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
> at $Proxy58.start(Unknown Source)
> at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
> at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
> at weblogic.management.Admin.finish(Admin.java:644)
> at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
> at weblogic.Server.main(Server.java:35)
>
> <Jul 23, 2003 4:33:10 PM PDT> <Error> <JMS> <Failed to deploy JMS Server "notifyServer"
> due to weblogic.jms.common.ConfigurationException: JMS can not open store.
> weblogic.jms.common.ConfigurationException: JMS can not open store
> at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:395)
> at weblogic.jms.JMSService.createBackEnd(JMSService.java:906)
> at weblogic.jms.JMSService.addJMSServer(JMSService.java:1273)
> at weblogic.jms.JMSService.addDeployment(JMSService.java:1169)
> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:360)
> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:285)
> at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:239)
> at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:199)
> at java.lang.reflect.Method.invoke(Native Method)
> at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
> at $Proxy39.updateDeployments(Unknown Source)
> at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2977)
> at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:372)
> at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
> at java.lang.reflect.Method.invoke(Native Method)
> at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
> at $Proxy58.start(Unknown Source)
> at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
> at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
> at weblogic.management.Admin.finish(Admin.java:644)
> at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
> at weblogic.Server.main(Server.java:35)
> ----------- Linked Exception -----------
> java.io.IOException: JMS JDBC store, connection pool = <jmsPool>, prefix = <qa.JMS_SERVER_>:
> failed to create tables
> at weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:311)
> at weblogic.jms.store.JDBCIOStream.rebuildTables(JDBCIOStream.java:1400)
> at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:376)
> at weblogic.jms.store.JMSStore.open(JMSStore.java:110)
> at weblogic.jms.backend.BEStore.open(BEStore.java:180)
> at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:390)
> at weblogic.jms.JMSService.createBackEnd(JMSService.java:906)
> at weblogic.jms.JMSService.addJMSServer(JMSService.java:1273)
> at weblogic.jms.JMSService.addDeployment(JMSService.java:1169)
> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:360)
> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:285)
> at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:239)
> at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:199)
> at java.lang.reflect.Method.invoke(Native Method)
> at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
> at $Proxy39.updateDeployments(Unknown Source)
> at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2977)
> at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:372)
> at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
> at java.lang.reflect.Method.invoke(Native Method)
> at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
> at $Proxy58.start(Unknown Source)
> at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
> at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
> at weblogic.management.Admin.finish(Admin.java:644)
> at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
> at weblogic.Server.main(Server.java:35)
>
-
Hi, does anybody know if I could configure JMS JDBC Store under OC4J ? It is possible to be done under WebLogic 6.1 (I believe Oracle uses for this purpose Advanced Queue). What about support of other JMS providers, like SonicMQ ? Is it possible to integrate with OC4J ?
Thank you,
Andrejus ChaliapinasHi, does anybody know if I could configure JMS JDBC Store under OC4J ? It is possible to be done under WebLogic 6.1 (I believe Oracle uses for this purpose Advanced Queue). What about support of other JMS providers, like SonicMQ ? Is it possible to integrate with OC4J ?
Thank you,
Andrejus Chaliapinas -
Reg : Unable to connect to JDBC Store
Hi all,
We are unable to connect to a JDBC Store due to which we are experiencing internal error while launching our application. Could anyone please provide a solution why this error is occuring? Please find the error we are facing below
weblogic.store.io.jdbc.JDBCStoreException: [Store:280065]failed to connect to database (server="AdminServer" store="LIQJMSFileStore" table="WLStore"):(Linked Cause, "java.sql.SQLSyntaxErrorException: ORA-00903: invalid table name
at weblogic.store.io.jdbc.ReservedConnection.resetConnection(ReservedConnection.java:341)
at weblogic.store.io.jdbc.ReservedConnection.testConnection(ReservedConnection.java:319)
at weblogic.store.io.jdbc.ReservedConnection.lock(ReservedConnection.java:286)
at weblogic.store.io.jdbc.ReservedConnection.lock(ReservedConnection.java:252)
at weblogic.store.io.jdbc.JDBCStoreIO.initialize(JDBCStoreIO.java:504)
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:351)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:413)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:404)
at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:126)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:66)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:492)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:472)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:101)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: java.sql.SQLSyntaxErrorException: ORA-00903: invalid table name
at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:91)
at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:206)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:413)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1035)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:194)
at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:791)
at oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPreparedStatement.java:866)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1188)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3386)
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3430)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1491)
at weblogic.jdbc.wrapper.PreparedStatement.executeQuery(PreparedStatement.java:135)
at weblogic.store.io.jdbc.ReservedConnection.getRow(ReservedConnection.java:661)
at weblogic.store.io.jdbc.ReservedConnection.resetConnection(ReservedConnection.java:338)
at weblogic.store.io.jdbc.ReservedConnection.testConnection(ReservedConnection.java:319)
at weblogic.store.io.jdbc.ReservedConnection.lock(ReservedConnection.java:286)
at weblogic.store.io.jdbc.ReservedConnection.lock(ReservedConnection.java:252)
at weblogic.store.io.jdbc.JDBCStoreIO.initialize(JDBCStoreIO.java:504)
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:351)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:413)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:404)
at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:126)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:66)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:492)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:472)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:101)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Thanks in advanceThis is not a WebLogic issue. This is an Oracle database issue.
ORA-00903 occurs when you issue a SQL statement with a from clause that contains a reserved keyword for a table name.
SCOTT@gamsot3 > select * -- table does not exist, but the table name is NOT a keyword. Results in ORA-00942.
2 from scot_test;
from scot_test
ERROR at line 2:
ORA-00942: table or view does not exist
SCOTT@gamsot3 > select * -- tables does not exist, but the table name IS a keyword. Results in ORA-00903.
2 from select;
from select
ERROR at line 2:
ORA-00903: invalid table name
SCOTT@gamsot3 > select * -- another example with a keyword. Also results in ORA-00903.
2 from insert;
from insert
ERROR at line 2:
ORA-00903: invalid table name
To solve this, fix the SQL statement that you are issuing from your custom code deployed on the managed server to use the correct table name in the from clause.
Edited by: Scot Krause on Feb 15, 2012 4:29 PM -
Create a persistent JDBC Store using WLST
Hi,
I want to create persistent JDBC store. i am unable to set the value for Datasource using WLST set command. Below are the steps which I followed. Please help me out.
connect('weblogic','welcome1','t3://hostname:port')
edit()
startEdit()
servermb=getMBean("Servers/soa_server1")
ts = create('SampleJMSDataStore','JDBCStore')
ts.addTarget(servermb)
cd('JDBCStores/SampleJMSDataStore')
set('DataSource','SOADataSourceName')
activate()
After I executed above commands, i logged into Admin console to check whether the values are set. But it is not. please let me know how to solve this issue.
Thanks,
GomathiWhich is the output of the script? Do you receive any errors?
-
Distributed transaction (JDBC+JMS), durable MDB, NullPointException in weblogic
I am cross posting to transaction & jms, sorry if this is a mistake...
We have a setup where JMS messages are published to a topic. The posting is transacted
(XA) and is a consequence of a CMP update so JMS and JDBC (Oracle OCI) cooperate
to commit, or not.
Most of the time, transactions issue just a few JMS messages but at least once
a day, we issue hundred of thousands of such messages (max has been about 600000
but typically 300000).
Our setup is four instances of Weblogic 6.1SP3 (two clustered, two not), the topic
is on one of them (all 3 other servers connect to that instance to publish) and
we have a couple MDBs deployed only on the instance that has the JMSServer and
they all listen to the local topic. The transactionnal settings of these MDBs
is CMT and XA (because the beans will write to the DB). Furthermore, these MDB
have been setup to be durable. One of these is just a logger MDB with 20 instances
max.
It worked fine for a couple weeks but we have been running into problems for the
past two days. All of a sudden, the server no longer responds to weblogic.ADMIN
PING. The server log indicates the following error repetitively (MB of logs just
of this)
####<13 nov. 03 23:15:41 CET> <Alert> <JMS> <XXXXXXX> <send1> <ExecuteThread:
'32' for queue: 'default'> <> <> <040060> <JMSServer "OutputServerSend1", unhandled
exception during rollback, java.lang.NullPointerException.>
java.lang.NullPointerException
at weblogic.jms.backend.BEDurableTopicMessageInfo.rollbackReceiveTran(BEDurableTopicMessageInfo.java:352)
at weblogic.jms.backend.BEXATranEntrySubscribe.startRollback(BEXATranEntrySubscribe.java:145)
at weblogic.jms.backend.BEXATranEntry.execute(BEXATranEntry.java:127)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
The logger MDB seems to have started processing the JMS messages. This means that
the transaction that included the JMS message publishing must have commited. Unfortunatly,
there are only 20 log lines before the server restart, so the server must have
hanged although it did commit the messages processed by the logger since the log
messages are apparently not repeated. I have no idea why. I think this is coherant
with the fact that exception above seems to relate to subscribers.
When we restart the server, the topic gets purged and seem to be processed (we
have not found a way to verify that each message has been processed but it's looking
good)
Any ideas ?
Thanks
Philippe
I am cross posting to transaction & jms, sorry if this is a mistake...
We have a setup where JMS messages are published to a topic. The posting is transacted
(XA) and is a consequence of a CMP update so JMS and JDBC (Oracle OCI) cooperate
to commit, or not.
Most of the time, transactions issue just a few JMS messages but at least once
a day, we issue hundred of thousands of such messages (max has been about 600000
but typically 300000).
Our setup is four instances of Weblogic 6.1SP3 (two clustered, two not), the topic
is on one of them (all 3 other servers connect to that instance to publish) and
we have a couple MDBs deployed only on the instance that has the JMSServer and
they all listen to the local topic. The transactionnal settings of these MDBs
is CMT and XA (because the beans will write to the DB). Furthermore, these MDB
have been setup to be durable. One of these is just a logger MDB with 20 instances
max.
It worked fine for a couple weeks but we have been running into problems for the
past two days. All of a sudden, the server no longer responds to weblogic.ADMIN
PING. The server log indicates the following error repetitively (MB of logs just
of this)
####<13 nov. 03 23:15:41 CET> <Alert> <JMS> <XXXXXXX> <send1> <ExecuteThread:
'32' for queue: 'default'> <> <> <040060> <JMSServer "OutputServerSend1", unhandled
exception during rollback, java.lang.NullPointerException.>
java.lang.NullPointerException
at weblogic.jms.backend.BEDurableTopicMessageInfo.rollbackReceiveTran(BEDurableTopicMessageInfo.java:352)
at weblogic.jms.backend.BEXATranEntrySubscribe.startRollback(BEXATranEntrySubscribe.java:145)
at weblogic.jms.backend.BEXATranEntry.execute(BEXATranEntry.java:127)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
The logger MDB seems to have started processing the JMS messages. This means that
the transaction that included the JMS message publishing must have commited. Unfortunatly,
there are only 20 log lines before the server restart, so the server must have
hanged although it did commit the messages processed by the logger since the log
messages are apparently not repeated. I have no idea why. I think this is coherant
with the fact that exception above seems to relate to subscribers.
When we restart the server, the topic gets purged and seem to be processed (we
have not found a way to verify that each message has been processed but it's looking
good)
Any ideas ?
Thanks
Philippe
-
Distributed transactions/jdbc problem WL60
Hi
Our company has aworking application running on WLS5.1sp9.
Im in the process of migrating it to WL6.0sp2.
Our domain has 2 clusters each running 2 servers:
1) servlet engines (handling http requests from clients, running servlets
and jsp's)
2) ejb containers (runnigour entities and session beans, working with Oracle
8i database using connection pool and TxDataSource)
The scenario:
- a client request invokes a servlet on one of the servlet engines.
- the servlet opens a jndi context to one of the ejb containers
- the servlet open a transaction on a UserTransaction stub on that ejb.
- then the servlet calls an entity bean using a home interface looked up
using the same context.
- the entity bean uses DataSource lookup in its own servers jndi to rerieve
a connection.
and then i get the following exception:
java.sql.SQLException: No default driver for database type:
jdbc:weblogic:jts
at
weblogic.jdbcbase.t3.Driver.seeIfWeNeedToInferDriverNameAndUrlFrom(Driver.ja
va:456)
at weblogic.jdbcbase.t3.Driver.getAllPropsFrom(Driver.java:255)
at weblogic.jdbcbase.t3.Driver.connect(Driver.java:75)
at weblogic.jdbcbase.jts.Driver.createRemoteConnection(Driver.java:199)
at weblogic.jdbcbase.jts.Driver.connect(Driver.java:134)
at
weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java
:44)
at com.unisfair.util.DBHelper.getConnection(DBHelper.java:43)
the transaction toString() gives:
transaction=(IdHash=7541556,Name = [EJB
UserBeanImpl.generateSessionSuffix()],Xid=2:b53da78d3c1badbb,Status=Active,n
umRepliesOwedMe=0,numRepliesOwedOthers=1,seconds since begin=0,seconds
left=30,activeThread=Thread[ExecuteThread: '8' for queue: 'default',5,Thread
Group for Queue:
'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=new,assig
ned=none),SCInfo[ejb2]=(state=active),SCInfo[servlet2]=(state=active),SCInfo
[ejb1]=(state=active),properties=({weblogic.transaction.name=[EJB
UserBeanImpl.generateSessionSuffix()], weblogic.jdbc=t3://10.0.0.31:7007}))
However the error happens on the other ejb server 10.0.0.33:7007
It seems that the jts driver tries to get a remote connection on the server
that coordinates the transaction but uses the deprecated t3 driver.
I hope someone can help us since this problem is a good enough reason for us
not moving on to WL6.0 we also looked at WL6.1 Beta and theres nothing new
about it either.
thanks
Dror Last
Senior Software Engineer
Unisfair Inc.
12 Yad Haruzim St. Tel Aviv 67778 Israel
Tel: +972-3-5373738 Ext. 243
Fax: +972-3-5373731
GSM: +972-55-723710
mailto:[email protected]
http://www.unisfair.com/
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by JDBC_TX ():
In the readme file of Oracle JDBC drivers 8.1.6.0.1 (http://technet.oracle.com/software/tech/java/sqlj_jdbc/files/Readme_01.txt)
it mentioned that it supports "distributed transactions".
As I understand, JDBC transaction is connection based and uses Oracle internal transaction manager. In order to do "distributed transactions", I must have at least two connections open at the same time each to its own database instance. How does the two connections coordinate the transactions? I thought in order to support "distributed transactions", one has to build a higher layer to encapsulate the two connections and therefore coordinate the distributed transactions. Any examples will be welcome.<HR></BLOCKQUOTE>
The two branches of the transaction are coordinated using 2-phase commit.
For samples look under
$ORACLE_HOME/jdbc/demo/samples/oci8/jdbc20-samples/
null -
Where do transaction data store?
Hi
1. Do values of char in a cube are stored in sid table of infoobject corresponding to the char?
2.if a infoobject belongs to many different cubes then values in sid table of the infoobject will include all value owned by respective cube? System will join fact table,demension table and sid table for retrieving and displaying data , in this case ,system distinguish value in sid table via sid as different cube use the same sid table.
Are what i said right? Could you give some advice or supplement about this topic ?
where is infomation which can make me master the system inside about this topic(net link)?Hi Guixin,
1. For the charcteristics in the cube SID's are generated in the SID table of the info-object and the values are fetched from the info-object using the SID's.
2. Whenever a cube is loaded with data then new SID's are generated in the SID table. The F fact table of the cube contains the Domension Id as foreign keys. The Dimension table in turn contain the SID's of all the characteristics belonging to that dimension.
<b>Importance of SID table (from SAP help)</b>
In InfoCubes and in aggregates, so-called master data IDs (SIDs), rather than characteristic values, are saved directly. In the SID table, there is a master data ID for every characteristic value. The OLAP processor also works internally only with the SIDs and not with characteristic values.
Dependencies
Generation of SIDs for characteristic M1:
In the following cases SIDs are generated for M1:
Loading of master data for M1
Loading of texts for M1
Loading of master data for a characteristic that has M1 as a navigation attribute
Activation of M1 as navigation attribute for a characteristic
Addition of M1 as navigation attribute for a characteristic if M1 is compounded
Loading of InfoCube data with the option of generating master data
Deactivation of the property exclusive attribute for characteristic M1, if M1 is used in ODS Objects that are released for reporting
In the following cases SIDs for M1 are only generated if M1 is not exclusive attribute):
Activation of data of an ODS object that is released for reporting and contains M1
Release of an ODS object that contains M1 for reporting
Execution of a query on a characteristic as InfoProvider that contains M1 as an attribute
Execution of a query on an InfoSet that contains M1 (via a characteristic or an ODS object)
Example
The content of the SID table for the characteristic Material could be as follows:
MATERIAL SID
0
ABC 1
10000 2
DEF 3
10100 4
XYZ 5
RTZE 6
Bye
Dinesh -
JDBC connection pool failures when used by JMS stores
We are using WebLogic 6.1 sp2. We defined a separate connection pool for use by
a JMS Store.
<JDBCConnectionPool Name="sybaseJMSPool"
Targets="cluster00"
InitialCapacity="2"
MaxCapacity="10"
DriverName="com.sybase.jdbc2.jdbc.SybDriver"
Properties="[email protected]@;[email protected]@;charset=utf8"
URL="jdbc:sybase:Tds:@jms.db.host@/@jms.db.name@"/>
(note that the @xxx@ string are replaced by actual values).
We are using Sybase Jconnect 5.5 to a Sybase ASE 12.5 database.
We deployed this configuration on a number of environments (testing, staging,
..). The actual hardware and network configuration is different for the different
system, but the WebLogic domain stays the same regarding this issue.
On the test system we frequently get the following exceptions:
<Aug 13, 2002 1:56:04 PM CEST> <Alert> <JMS> <www00-test> <node00>
<ExecuteThread: '6' for queue: 'JMS.TimerClientPool'> <> <> <040048>
<JMSServer "JMSServer00", store failure while writing message for topic
OrderChangeTopic, java.io.IOException: JMS JDBC store, connection pool =
<sybaseJMSPool>, prefix = <JMS00>: write failed
java.sql.SQLException: JZ006: Caught IOException:
com.sybase.jdbc2.jdbc.SybConnectionDeadException: JZ0C0: Connection is already
closed.
at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead
(ErrorMessage.java:715)
at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3124)
at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1412)
at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1341)
at com.sybase.jdbc2.jdbc.SybStatement.doCancel(SybStatement.java:564)
at com.sybase.jdbc2.jdbc.SybStatement.updateLoop(SybStatement.java:1672)
at com.sybase.jdbc2.jdbc.SybStatement.executeUpdate
(SybStatement.java:1625)
at com.sybase.jdbc2.jdbc.SybPreparedStatement.executeUpdate
(SybPreparedStatement.java:91)
at com.p6spy.engine.logging.P6LogPreparedStatement.executeUpdate
(P6LogPreparedStatement.java:179)
at weblogic.jdbc.pool.Statement.executeUpdate(Statement.java:293)
at weblogic.jms.store.JDBCIOStream.write(JDBCIOStream.java:1246)
at weblogic.jms.store.StoreRequest.doTheIO(StoreRequest.java:250)
at weblogic.jms.store.JMSStore.execute(JMSStore.java:182)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
.>
java.io.IOException: JMS JDBC store, connection pool = <sybaseJMSPool>, prefix
= <JMS00>: write failed
java.sql.SQLException: JZ006: Caught IOException:
com.sybase.jdbc2.jdbc.SybConnectionDeadException: JZ0C0: Connection is already
closed.
at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead
(ErrorMessage.java:715)
at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3124)
at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1412)
at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1341)
at com.sybase.jdbc2.jdbc.SybStatement.doCancel(SybStatement.java:564)
at com.sybase.jdbc2.jdbc.SybStatement.updateLoop(SybStatement.java:1672)
at com.sybase.jdbc2.jdbc.SybStatement.executeUpdate
(SybStatement.java:1625)
at com.sybase.jdbc2.jdbc.SybPreparedStatement.executeUpdate
(SybPreparedStatement.java:91)
at com.p6spy.engine.logging.P6LogPreparedStatement.executeUpdate
(P6LogPreparedStatement.java:179)
at weblogic.jdbc.pool.Statement.executeUpdate(Statement.java:293)
at weblogic.jms.store.JDBCIOStream.write(JDBCIOStream.java:1246)
at weblogic.jms.store.StoreRequest.doTheIO(StoreRequest.java:250)
at weblogic.jms.store.JMSStore.execute(JMSStore.java:182)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
at weblogic.jms.store.JDBCIOStream.throwIOException
(JDBCIOStream.java:1213)
at weblogic.jms.store.JDBCIOStream.write(JDBCIOStream.java:1256)
at weblogic.jms.store.StoreRequest.doTheIO(StoreRequest.java:250)
at weblogic.jms.store.JMSStore.execute(JMSStore.java:182)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Before that this message appeared:
<Aug 13, 2002 11:31:16 AM CEST> <Error> <ConnectionManager> <www00-test>
<node00> <ExecuteThread: '26' for queue: 'default'> <> <> <000000>
<Closing: 'weblogic.rjvm.t3.T3JVMConnection@795af6' because of: 'Server
received a message over an uninitialized connection: 'JVMMessage from: 'null'
to: '-4555218188801970213S:192.168.13.1:[7001,7001,7002,7002,7001,7002,-
1]:ADIS:node00' cmd: 'CMD_REQUEST', QOS: '101', responseId: '1',
invokableId: '287', flags: 'JVMIDs Not Sent, TX Context Not Sent', abbrev
offset: '34'''>
This problem did not occur on another system which was used during a 2 day stress
testing session.
It seems that the problem occurs after a period in which no user request where
made. The user requests trigger EJB's that start sending JMS messages.
When the problem occurs, the JMS messaging systems seems to lock up as no messages
are received anymore by the different listeners (MDBs).
Undeploying and redeploying the JBDC connection pool solves the problem. This
solution is unacceptable in case of a production system.
A similarly defined connection pool, which is used by the EJBs to make database
connection, does not manifest this problem.
<JDBCConnectionPool Name="sybasePool"
Targets="cluster00"
InitialCapacity="10"
CapacityIncrement="5"
MaxCapacity="50"
PreparedStatementCacheSize="150"
DriverName="com.sybase.jdbc2.jdbc.SybDriver"
Properties="[email protected]@;[email protected]@;JCONNECT_VERSION=6;charset=utf8"
URL="jdbc:sybase:Tds:@db.host@/@db.name@"/>
The JDBC connection pool is used as follows by the JDBC store
<JMSJDBCStore ConnectionPool="sybaseJMSPool" Name="JDBCStore00" PrefixName="JMS00"/>
<JMSServer Name="JMSServer00" Store="JDBCStore00" Targets="node00">
<JMSTopic JNDIName="ADIS.JMSError" JNDINameReplicated="false" Name="ErrorTopic"/>
<JMSTopic JNDIName="ADIS.Status"
Name="StatusTopic" RedeliveryDelayOverride="300000"/>
<JMSTopic JNDIName="ADIS.OrderChange" JNDINameReplicated="false"
Name="OrderChangeTopic" RedeliveryLimit="3"/>
</JMSServer>
Turning on the "Test Reserved Connection" with a appropriate test table does not
help.
Some sources on the internet tell us that JZ0C0 errors in the Jconnect driver
can be related to network problems. Nevertheless the connection pool should be
able to cope with this.
Can you provide any solution for this ? Or give us hints what can cause the problem
Zhenhao Qi wrote:
thanks! Joe.
The SQL statement itself can no longer be simplified, the long excuation time is due to the database size and complicated Select criteria. I can easily reproduce the problem by using this SQL. I tried "BEA's Oracle driver (Type 4): Version 8.1.7,9.0.1,9.2.0". the question can be dissect into 2 pieces:
1) why the jdbc connection (using oracle.jdbc.OracleDriver) won't return anything if the SQL execution time > 5min, that is probably the Oracle's problem
2) why the occupied connection pool won't release even I set "Statementtimeout=600", this is Weblogic's problem.
ZhenhaoHi. Yes, (1) is oracle's problem. (2) may also be. The JDBC spec has very few
allowances for one thread to interrupt a second thread's JDBC call. If we
transmit your timeout request by calling setQueryTimeout() on the oracle
statement, and if you have a weblogic-controlled transaction we call
Statement.cancel() on any ongoing statement, we end up relying on whether
the Oracle driver implements and responds to those calls.
Are you doing weblogic-controlled transactions? Are you/can you
call Statement.setQueryTimeout() on your statements, or are these
generated JDBC queries?
If you can duplicate the problem using the weblogic.jdbc.oracle.OracleDriver
we have some other debug avenues. This would be good even if you really
want to use the thin driver, because we will do the same JDBC calls to
either driver, and the debug would prove (if) we set up a query timeout
and if we call cancel(). If we do, then we can know that it is the Oracle
driver failing in these regards.
Joe -
JDBC Persistence Store: How to
I need to create a JMS JDBC Store in WLS9.1 which will enable me to store XML SOAP messages in SQL Server table. At the moment I intend to persist the messages as is into the JDBC store. I thinking of having the DBA to create a table with single attribute (that will hold more than 5000 bytes). Please advice if there is better startegy storing these WebService messages. I do not want store the messages in the FileStore.
Sample Message
<?xml version="1.0" encoding="UTF-8"?>
<m:SubmitRequest xmlns:m="http://usgs.med.eai.eds.com/provenroll" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><eds:Provider transactionID="399" transactionCode="A" providerID="3753136" partyName="Lyle" firstName="Theodore" middleName="d" xmlns:eds="http://EDS.USGS.MED.EAI.PE.InitEnrolSchemas.PE_InboundEnrolRequest_XML_V1"><reviewType beginDate="20060906" endDate="20060921"><reviewTypeCode/></reviewType><demographic SSN="4553325554" DOB="19760000" gender="M"/><addressPhone handicapAccessible="Yes" fax="8405612315" emailAddress="[email protected]"><address street1="23978 Hospice Way" city="Richmond" stateCode="VA" zipCode="23448" zipCodePlus4="23228"/><phone phone="8059551531" phoneExt="8055551531"/></addressPhone><license licenseNumber="123344" beginDate="20060905" endDate="20070906" stateissue="VA"/><license licenseNumber="2355231" beginDate="20060912" taxonomyCode="745226" beginDate="0"/></eds:Provider><AuditTrialStatus>Prov Enroll Request Submitted to Business Service </AuditTrialStatus><AuditTrialTime>09:57:16.640-07:00</AuditTrialTime><AuditTrialDate>2006-10-26-07:00</AuditTrialDate><AuditTrialCorrelationID providerID="3654436"/></m:SubmitRequest>
Please advice on how I can specify the required table.
Krishna
KrishTom
Let me briefly what I did:
1. Created X_DataSource and connection test was successful.
2. Created JDBCStore and targeted to X_DataSource
3. Prefix Name : [[PM.]dbo.]PMStore or [[[PM.]dbo.]PMStore], as per documentation [[[catalog.]schema.]prefix] no prefix part is provided in this case. PMStore is the table predefined on the database.
I tried all permutation and the error I am getting is failed to open the database table. Please advise.
<Nov 17, 2006 10:26:17 AM EST> <Error> <Store> <BEA-280072> <JDBC store "PM-JDBCStore" failed to open table "[[[PM.]dbo.]PMStoreWLStore".
weblogic.store.io.jdbc.JDBCStoreException: [Store:280065][Store:280068]JDBC store failed to initiali
ze. It did not find its database table and failed trying to create a new empty table using the comma
nds in file "/weblogic/store/io/jdbc/ddl/mssql.ddl". (server="AdminServer" store="PM-JDBCStore" tabl
e="[[[PM.]dbo.]PMStoreWLStore"):(Linked Cause, "java.sql.SQLException: [BEA][SQLSer
ver JDBC Driver][SQLServer]Incorrect syntax near 'dbo'.")
Krish -
JDBC Persistent Store Exceptions Table needs to be renamed
we are facing a situation almost every week in production. The only workaround is to rename the table everytime an boune the Weblogic. Oracle recommended to increase the statement timeout. Not sure if that will work.
Can anyone provide what is the reason behind this. As there is only admin server in this domain with single JMS Server and JDBC Store. So not sure how the ownership is lost. Any help is appreciated .
####<Dec 25, 2010 4:32:01 AM IST> <Error> <Store> <gnnosm21> <OSMServer> <[ACTIVE] ExecuteThread: '65' for queue: 'weblogi
c.kernel.Default (self-tuning)'> <<WLS Kernel>> <1293231721099> <BEA-280075> <JDBC store "oms_jms_store" failed to r
etain ownership of database table "OM_BEAWLStore", either due to database access problems or due to concurrent accessors o
f the table. See the linked exception for more information.
weblogic.store.io.jdbc.JDBCStoreException: [Store:280065]java.sql.SQLException: ORA-01013: user requested cancel of curren
t operation
(server="OSMServer" store="oms_jms_store" table="OM_BEAWLStore"):(Linked Cause, "java.sql.SQLException: ORA-01013: user r
equested cancel of current operation
at weblogic.store.io.jdbc.JDBCStoreIO.readTableLockRecord(JDBCStoreIO.java:2078)
at weblogic.store.io.jdbc.JDBCStoreIO.updateTableOwnership(JDBCStoreIO.java:2105)
at weblogic.store.io.jdbc.ReservedConnection.timerExpired(ReservedConnection.java:436)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:265)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
java.sql.SQLException: ORA-01013: user requested cancel of current operation
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:743)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216)
at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:955)
at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1060)
at oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPreparedStatement.java:839)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1124)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3316)
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3361)
at weblogic.jdbc.wrapper.PreparedStatement.executeQuery(PreparedStatement.java:100)
at weblogic.store.io.jdbc.JDBCStoreIO.internalRead(JDBCStoreIO.java:721)
at weblogic.store.io.jdbc.JDBCStoreIO.readTableLockRecord(JDBCStoreIO.java:2066)
at weblogic.store.io.jdbc.JDBCStoreIO.updateTableOwnership(JDBCStoreIO.java:2105)
at weblogic.store.io.jdbc.ReservedConnection.timerExpired(ReservedConnection.java:436)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:265)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)Hi,
You didnot mention what is that everytime you mean in your question....
Did you check is there any other user also using the same database table "OM_BEAWLStore" from your development environment connecting with the same JMS persistance store? -
Manage Server Start Problem (weblogic.store.io.jdbc.JDBCStoreException)
I have a problem, when i start manage server.
Could you please help me about this problem?
Thanks
Orhan YENER
<Jun 19, 2012 1:45:17 PM EEST> <Warning> <Store> <BEA-280076> <Database table "P13N_MESSAGING_WLStore" for store "p13nJMSPersistenceStore" is currently owned by "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=7010169693931783666:timestamp=1340102710950]". Trying to wait for ownership.>
<Jun 19, 2012 1:45:37 PM EEST> <Error> <Store> <BEA-280077> <JDBC store "p13nJMSPersistenceStore" in this server is not the owner of database table "P13N_MESSAGING_WLStore". Unexpected current owner is "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=7010169693931783666:timestamp=1340102730980]", expected current owner is "[name={server=ManagedServer2!host=172.25.23.238!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=-8739910915764232623:timestamp=1340102716802]".>
<Jun 19, 2012 1:45:37 PM EEST> <Error> <Store> <BEA-280072> <JDBC store "p13nJMSPersistenceStore" failed to open table "P13N_MESSAGING_WLStore".
weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="p13nJMSPersistenceStore" table="P13N_MESSAGING_WLStore")
at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:37 PM EEST> <Error> <Store> <BEA-280061> <The persistent store "p13nJMSPersistenceStore" could not be deployed: weblogic.store.io.jdbc.JDBCStoreException: open failed
weblogic.store.io.jdbc.JDBCStoreException: open failed
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:445)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:135)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:66)
Truncated. see log file for complete stacktrace
Caused By: weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="p13nJMSPersistenceStore" table="P13N_MESSAGING_WLStore")
at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:37 PM EEST> <Warning> <Management> <BEA-141197> <The deployment of p13nJMSPersistenceStore failed.
weblogic.management.DeploymentException:
at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:138)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:66)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
Truncated. see log file for complete stacktrace
Caused By: weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="p13nJMSPersistenceStore" table="P13N_MESSAGING_WLStore")
at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:37 PM EEST> <Warning> <Store> <BEA-280076> <Database table "PF_PROLIFERATION_WLStore" for store "pfProliferationJMSStore" is currently owned by "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=pfProliferationJMSStore!table=PF_PROLIFERATION_WLStore}:random=1226318586891229532:timestamp=1340102728280]". Trying to wait for ownership.>
<Jun 19, 2012 1:45:57 PM EEST> <Error> <Store> <BEA-280077> <JDBC store "pfProliferationJMSStore" in this server is not the owner of database table "PF_PROLIFERATION_WLStore". Unexpected current owner is "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=pfProliferationJMSStore!table=PF_PROLIFERATION_WLStore}:random=1226318586891229532:timestamp=1340102748300]", expected current owner is "[name={server=ManagedServer2!host=172.25.23.238!domain=base_domain!store=pfProliferationJMSStore!table=PF_PROLIFERATION_WLStore}:random=3276936988962983628:timestamp=1340102737578]".>
<Jun 19, 2012 1:45:58 PM EEST> <Error> <Store> <BEA-280072> <JDBC store "pfProliferationJMSStore" failed to open table "PF_PROLIFERATION_WLStore".
weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="pfProliferationJMSStore" table="PF_PROLIFERATION_WLStore")
at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Error> <Store> <BEA-280061> <The persistent store "pfProliferationJMSStore" could not be deployed: weblogic.store.io.jdbc.JDBCStoreException: open failed
weblogic.store.io.jdbc.JDBCStoreException: open failed
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:445)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:135)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:66)
Truncated. see log file for complete stacktrace
Caused By: weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="pfProliferationJMSStore" table="PF_PROLIFERATION_WLStore")
at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Warning> <Management> <BEA-141197> <The deployment of pfProliferationJMSStore failed.
weblogic.management.DeploymentException:
at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:138)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:66)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
Truncated. see log file for complete stacktrace
Caused By: weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="pfProliferationJMSStore" table="PF_PROLIFERATION_WLStore")
at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Error> <JMS> <BEA-040123> <Failed to start JMS Server "p13nJMSServer" due to weblogic.management.DeploymentException: The persistent store "p13nJMSPersistenceStore" does not exist.
weblogic.management.DeploymentException: The persistent store "p13nJMSPersistenceStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:304)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:192)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Warning> <Management> <BEA-141197> <The deployment of p13nJMSServer failed.
weblogic.management.DeploymentException: Internalrror activating the JMS Server p13nJMSServer: weblogic.management.DeploymentException: The persistent store "p13nJMSPersistenceStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:206)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:492)
Truncated. see log file for complete stacktrace
Caused By: weblogic.management.DeploymentException: The persistent store "p13nJMSPersistenceStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:304)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:192)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Error> <JMS> <BEA-040123> <Failed to start JMS Server "pfJMSServer" due to weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist.
weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:304)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:192)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Warning> <Management> <BEA-141197> <The deployment of pfJMSServer failed.
weblogic.management.DeploymentException: Internalrror activating the JMS Server pfJMSServer: weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:206)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:492)
Truncated. see log file for complete stacktrace
Caused By: weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:304)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:192)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'p13n-security-jms'.
weblogic.application.ModuleException: ERROR: Could not activate p13n-security-jms!p13n.security.RDBMSSecurityStoreTopic
at weblogic.jms.backend.BEDestinationRuntimeDelegate.activate(BEDestinationRuntimeDelegate.java:238)
at weblogic.jms.backend.BETopicRuntimeDelegate.activate(BETopicRuntimeDelegate.java:100)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1717)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
Truncated. see log file for complete stacktrace
Caused By: weblogic.messaging.kernel.KernelException: The Messaging Kernel p13nJMSServer has not yet been opened
at weblogic.messaging.kernel.internal.KernelImpl.checkOpened(KernelImpl.java:191)
at weblogic.messaging.kernel.internal.DestinationImpl.activate(DestinationImpl.java:280)
at weblogic.messaging.kernel.internal.TopicImpl.activate(TopicImpl.java:97)
at weblogic.messaging.kernel.internal.DestinationImpl.resume(DestinationImpl.java:264)
at weblogic.jms.backend.BEDestinationImpl.start(BEDestinationImpl.java:627)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'pf-proliferation-jms'.
weblogic.application.ModuleException: ERROR: Could not activate pf-proliferation-jms!pfProliferationQueue
at weblogic.jms.backend.BEDestinationRuntimeDelegate.activate(BEDestinationRuntimeDelegate.java:238)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1717)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
at weblogic.jms.module.JMSModule.activate(JMSModule.java:332)
Truncated. see log file for complete stacktrace
Caused By: weblogic.messaging.kernel.KernelException: The Messaging Kernel pfJMSServer has not yet been opened
at weblogic.messaging.kernel.internal.KernelImpl.checkOpened(KernelImpl.java:191)
at weblogic.messaging.kernel.internal.DestinationImpl.activate(DestinationImpl.java:280)
at weblogic.messaging.kernel.internal.QueueImpl.activate(QueueImpl.java:1696)
at weblogic.messaging.kernel.internal.DestinationImpl.resume(DestinationImpl.java:264)
at weblogic.messaging.kernel.internal.QueueImpl.resume(QueueImpl.java:1872)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Notice> <LoggingService> <BEA-320400> <The log file /weblogic/Oracle/Middleware/user_projects/domains/base_domain/servers/ManagedServer2/logs/ManagedServer2.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Jun 19, 2012 1:45:58 PM EEST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /weblogic/Oracle/Middleware/user_projects/domains/base_domain/servers/ManagedServer2/logs/ManagedServer2.log00054. Log messages will continue to be logged in /weblogic/Oracle/Middleware/user_projects/domains/base_domain/servers/ManagedServer2/logs/ManagedServer2.log.>
<Jun 19, 2012 1:46:04 PM EEST> <Error> <Deployer> <BEA-149605> <Failed to create App/Comp mbeans for AppDeploymentMBean partnerportal. Error - weblogic.management.DeploymentException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear.
weblogic.management.DeploymentException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear
at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:193)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
Truncated. see log file for complete stacktrace
Caused By: java.io.IOException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:114)
at java.util.jar.JarFile.<init>(JarFile.java:133)
at java.util.jar.JarFile.<init>(JarFile.java:97)
at weblogic.utils.jars.JarFileDelegate.<init>(JarFileDelegate.java:32)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:46:04 PM EEST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'partnerportal' due to error weblogic.management.DeploymentException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear.
weblogic.management.DeploymentException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear
at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:193)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
Truncated. see log file for complete stacktrace
Caused By: java.io.IOException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:114)
at java.util.jar.JarFile.<init>(JarFile.java:133)
at java.util.jar.JarFile.<init>(JarFile.java:97)
at weblogic.utils.jars.JarFileDelegate.<init>(JarFileDelegate.java:32)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:46:04 PM EEST> <Error> <Deployer> <BEA-149605> <Failed to create App/Comp mbeans for AppDeploymentMBean partnerstaticweb. Error - weblogic.management.DeploymentException: .
weblogic.management.DeploymentException:
at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:69)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
Truncated. see log file for complete stacktrace
Caused By: java.util.zip.ZipException: Error opening file - /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.staticweb-01.01.00.war Message - error in opening zip file
at weblogic.servlet.utils.WarUtils.existsInWar(WarUtils.java:78)
at weblogic.servlet.utils.WarUtils.isWebServices(WarUtils.java:67)
at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:61)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:46:04 PM EEST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'partnerstaticweb' due to error weblogic.management.DeploymentException: .
weblogic.management.DeploymentException:
at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:69)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
Truncated. see log file for complete stacktrace
Caused By: java.util.zip.ZipException: Error opening file - /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.staticweb-01.01.00.war Message - error in opening zip file
at weblogic.servlet.utils.WarUtils.existsInWar(WarUtils.java:78)
at weblogic.servlet.utils.WarUtils.isWebServices(WarUtils.java:67)
at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:61)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
Truncated. see log file for complete stacktrace
>
>
<Jun 19, 2012 1:46:13 PM EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Jun 19, 2012 1:46:13 PM EEST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Jun 19, 2012 1:46:13 PM EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<Jun 19, 2012 1:46:14 PM EEST> <Notice> <Server> <BEA-002607> <Channel "Default" listening on 172.25.23.238:80 was shutdown.>It's the first couple of bits that are key here
<Jun 19, 2012 1:45:17 PM EEST> <Warning> <Store> <BEA-280076> <Database table "P13N_MESSAGING_WLStore" for store "p13nJMSPersistenceStore" is currently owned by "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=7010169693931783666:timestamp=1340102710950]". Trying to wait for ownership.>
<Jun 19, 2012 1:45:37 PM EEST> <Error> <Store> <BEA-280077> <JDBC store "p13nJMSPersistenceStore" in this server is not the owner of database table "P13N_MESSAGING_WLStore". Unexpected current owner is "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=7010169693931783666:timestamp=1340102730980]", expected current owner is "[name={server=ManagedServer2!host=172.25.23.238!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=-8739910915764232623:timestamp=1340102716802]".>
It looks to me that your stores are incorrectly configured, targetted or or just simply messed up. First thing I would do here is check the configuration and targetting of the JDBC Stores and make sure that each JMS server is using it own store and database tables. You may find that it's a really simple thing like creating two sets of tables on the same database, but making sure that they have different prefixes ... -
Unable to connect to JDBC Persistent Store
- There are two managed server in a cluster on a WLS 9.2 MP2 and the version of database is 9..2.0.8
- Trying to start managed server but getting java.lang.Assertion error.
- Application also does not work.
- Managed server 1 is not starting and throwing the java.lang.Assertion error.
- It connects to a JDBC persistent store.
- Managed server 2 starts perfectly and connects to it's own JDBC persistent store.
- Both managed servers use the same Oracle Database 9.2.0.8.
- There is different JDBC store for both the managed servers.
- Each persistent store has its own separate table in the database
####<Jun 6, 2010 10:40:45 AM PDT> <Error> <Deployer> <emfd2> <WLISMMS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1275846045224> <BEA-149260> <A failure occurred during application startup.
>
Need Help!!
>
Edited by: user12941236 on Jun 10, 2010 7:10 AM
Edited by: user12941236 on Jun 10, 2010 7:11 AMweblogic.application.ModuleException: ERROR: Could not activate EIJMSModule!ApplicationErrorQueue01
at weblogic.jms.backend.BEDestinationRuntimeDelegate.activate(BEDestinationRuntimeDelegate.java:238)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1717)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
at weblogic.jms.module.JMSModule.activate(JMSModule.java:332)
at weblogic.jms.module.ModuleCoordinator.activate(ModuleCoordinator.java:179)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:181)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:358)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:42)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:177)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
weblogic.messaging.kernel.KernelException: The Messaging Kernel EIJMSServer01 has not yet been opened
at weblogic.messaging.kernel.internal.KernelImpl.checkOpened(KernelImpl.java:191)
at weblogic.messaging.kernel.internal.DestinationImpl.activate(DestinationImpl.java:279)
at weblogic.messaging.kernel.internal.QueueImpl.activate(QueueImpl.java:1629)
at weblogic.messaging.kernel.internal.DestinationImpl.resume(DestinationImpl.java:263)
at weblogic.messaging.kernel.internal.QueueImpl.resume(QueueImpl.java:1805)
at weblogic.jms.backend.BEDestinationImpl.start(BEDestinationImpl.java:604)
at weblogic.jms.backend.BEDestinationRuntimeDelegate.activate(BEDestinationRuntimeDelegate.java:235)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1717)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667) -
Hi everyone,
I created one filestore for storing jms queues , now i want to change that filestore to jdbc store. i configured jdbc store . i have a question we should run any script to create tables in the database, or database admin will takecare of that , if databaseadmin will be take care , what requirments we need to tell to the database admin. please let me know , it will help to me alotThe weblogic/jms/ddl directory within the weblogic.jar file contains JMS DDL files for different database.
which are actually text files containing the SQL commands that create the JMS database tables. To use a different database, simply copy and edit any one of these .ddl files. -
Sybase - JDBC Persistent Store
Hi
I'm trying to setup Glassfish JMS to utilise a JDBC store (using Sybase)
I have set the required parameters in config.properties for the imqBroker instance. (including creating the Sybase DDL)
When I invoke imqdbmgr create tbl - all tables and indexes are created - but the process exits with an error. No details are displayed (even when using the -debug option) as to what the reason for failure is.
[11/Sep/2008:12:07:52 BST] Using plugged-in persistent store:
version=410
brokerid=imqBroker
database connection url=jdbc:sybase:Tds:localhost:5000/openmq_store
database user=jms_user
[11/Sep/2008:12:07:52 BST] Creating database table MQVER41SimqBroker ...
[11/Sep/2008:12:07:52 BST] Creating database table MQBKR41SimqBroker ...
[11/Sep/2008:12:07:53 BST] Creating database table MQSES41SimqBroker ...
[11/Sep/2008:12:07:53 BST] Creating database table MQPROP41SimqBroker ...
[11/Sep/2008:12:07:53 BST] Creating database table MQCREC41SimqBroker ...
[11/Sep/2008:12:07:53 BST] Creating database table MQCON41SimqBroker ...
[11/Sep/2008:12:07:53 BST] Creating database table MQCONSTATE41SimqBroker ...
[11/Sep/2008:12:07:53 BST] Creating database table index MQCONSTATE41SimqBrokerIDX1 ...
[11/Sep/2008:12:07:53 BST] Creating database table MQDST41SimqBroker ...
[11/Sep/2008:12:07:53 BST] Creating database table index MQDST41SimqBrokerIDX1 ...
[11/Sep/2008:12:07:53 BST] Creating database table MQMSG41SimqBroker ...
[11/Sep/2008:12:07:53 BST] Creating database table index MQMSG41SimqBrokerIDX1 ...
[11/Sep/2008:12:07:53 BST] Creating database table MQTXN41SimqBroker ...
[11/Sep/2008:12:07:53 BST] Creating database table index MQTXN41SimqBrokerIDX1 ...
[11/Sep/2008:12:07:53 BST] ERROR [B3073]: Failed to create database tables - jdbc:sybase:Tds:localhost:5000/openmq_store
com.sun.messaging.jmq.jmsserver.util.BrokerException: [B3073]: Failed to create
database tables - jdbc:sybase:Tds:localhost:5000/openmq_store
at com.sun.messaging.jmq.jmsserver.persist.jdbc.DBTool.doCreate(DBTool.j
ava:200)
at com.sun.messaging.jmq.jmsserver.persist.jdbc.DBTool.doCommand(DBTool.
java:1700)
at com.sun.messaging.jmq.jmsserver.persist.jdbc.DBTool.main(DBTool.java:
1749)
Any ideas on how I can troubleshoot further?
Thanks
Edited by: chivz on Sep 11, 2008 4:12 AMAre there any errors in Sybase log ? From the error looks like it's failing while creating txn table which I think is using blobs.
Tom
Maybe you are looking for
-
Slow browsing, timeouts and pages failing to load
Hi, Over the last few days we've been having browsing issues on multiple devices where pages are taking forever to load if at all. We're sometimes having to refresh the browser 3 or 4 times to get a page to load correctly. Sites like speedtest, once
-
how do I delete photos in the photo stream? The images remained despite I removed them on the macbook pro.
-
Hi , In ME31k/ME32k Program : SAPMM06E and screen 220 based on the material ,the storage location is automatically populated . I want to make storage location as blank for new(ME31K) and existing contract (ME32k). Please let me regarding the same. T
-
Error loading external library
I have created a library in Oracle using a C library test.so in sun solaris. This library contains string manipulation and memory management functions. When I call a function in this library through PL/SQL I get the error ORA-06520: PL/SQL: Error loa
-
"cannot find the scanner on the bus"
I attached Epson 2450 scanner via firewire but when I open Photoshop I get the message "cannot find the scanner on the bus, Please ensure that it is switched on, ready to scan and that the cables are attached correctly." That message stays on top of