JMS JDBC Store in OC4J ?

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 Chaliapinas

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 Chaliapinas

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)
              >
              

  • JMS Persistance Store "WLStore"

    JMS Persistence Store was using WLStore table, to persist the JMS message, but on production server restart the Weblogic is not able to read that WLStore Table anymore and giving below Error.
    <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Error> <Store> <BEA-280072> <JDBC store "JMSJDBCStore" failed to open table "WLStore".
    All help is appreciated.
    Thanks
    Anand.

    Hi Anand,
    There must be more information about this error in the log like a exception stacktrace. This error may come due to many reasons so complete error info would be required to identify the exact problem.
    As it is a production issue so I would suggest you to raise a SR with support. Cross post your question in weblogic forum to get better response -
    WebLogic Server - General
    Regards,
    Anuj

  • Weblogic Server 9.2 - JMS File Store not working as expected.

    Hi,
    I am facing a problem at the server startup possibly due to huge size of the JMS File Store created.
    My question is that our application receives messages via MDB (container managed),
    Even after successfully processing the message, the message which is logged in the File Store is not deleted.
    How can i make sure that a message which is successfully processed is not logged in the file store?
    (considering container managed transactions do not require acknowledgement-mode set in the descriptor, altough i have it specified)
    Find the the stack trace on the server log below:
    ####<Dec 10, 2008 11:45:30 AM CST> <Error> <JMS> <xlqwls01> <ACSServer1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tu
    ning)'> <<WLS Kernel>> <> <> <1228931130485> <BEA-040123> <Failed to start JMS Server "SDBJMSServer1" due to weblogic.jms.common.JMSException: web
    logic.messaging.kernel.KernelException: Unexpected store exception in messaging kernel recovery.
    weblogic.jms.common.JMSException: weblogic.messaging.kernel.KernelException: Unexpected store exception in messaging kernel recovery
    at weblogic.jms.backend.BackEnd.open(BackEnd.java:963)
    at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:180)
    at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
    at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
    at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:589)
    at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:450)
    at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:430)
    at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:100)
    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: Unexpected store exception in messaging kernel recovery
    at weblogic.messaging.kernel.internal.PersistenceImpl.recover(PersistenceImpl.java:839)
    at weblogic.messaging.kernel.internal.KernelImpl.open(KernelImpl.java:235)
    at weblogic.jms.backend.BackEnd.open(BackEnd.java:961)
    at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:180)
    at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
    at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
    at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:589)
    at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:450)
    at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:430)
    at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:100)
    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.store.PersistentStoreException: [Store:280020]There was an error while reading from the log file
    at weblogic.store.io.file.Heap.read(Heap.java:648)
    at weblogic.store.io.file.FileStoreIO.readInternal(FileStoreIO.java:224)
    at weblogic.store.io.file.FileStoreIO.access$000(FileStoreIO.java:31)
    at weblogic.store.io.file.FileStoreIO$Cursor.nextInternal(FileStoreIO.java:573)
    at weblogic.store.io.file.FileStoreIO$Cursor.next(FileStoreIO.java:547)
    at weblogic.store.internal.PersistentStoreConnectionImpl$CursorImpl.next(PersistentStoreConnectionImpl.java:266)
    at weblogic.messaging.kernel.internal.PersistenceImpl.recoverHeaders(PersistenceImpl.java:1148)
    at weblogic.messaging.kernel.internal.PersistenceImpl.recover(PersistenceImpl.java:814)
    at weblogic.messaging.kernel.internal.KernelImpl.open(KernelImpl.java:235)
    at weblogic.jms.backend.BackEnd.open(BackEnd.java:961)
    at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:180)
    at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
    at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
    at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:589)
    at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:450)
    at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:430)
    at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:100)
    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)
    java.io.IOException: Error reading from file, No such file or directory, errno=2
    at weblogic.store.io.file.direct.DirectIONative.read(Native Method)
    at weblogic.store.io.file.direct.DirectFileChannel.read(DirectFileChannel.java:133)
    at weblogic.store.io.file.StoreFile.read(StoreFile.java:281)
    at weblogic.store.io.file.Heap.read(Heap.java:646)
    at weblogic.store.io.file.FileStoreIO.readInternal(FileStoreIO.java:224)
    at weblogic.store.io.file.FileStoreIO.access$000(FileStoreIO.java:31)
    at weblogic.store.io.file.FileStoreIO$Cursor.nextInternal(FileStoreIO.java:573)
    at weblogic.store.io.file.FileStoreIO$Cursor.next(FileStoreIO.java:547)
    at weblogic.store.internal.PersistentStoreConnectionImpl$CursorImpl.next(PersistentStoreConnectionImpl.java:266)
    at weblogic.messaging.kernel.internal.PersistenceImpl.recoverHeaders(PersistenceImpl.java:1148)
    at weblogic.messaging.kernel.internal.PersistenceImpl.recover(PersistenceImpl.java:814)
    at weblogic.messaging.kernel.internal.KernelImpl.open(KernelImpl.java:235)
    at weblogic.jms.backend.BackEnd.open(BackEnd.java:961)
    at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:180)
    at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
    at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
    at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:589)
    at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:450)
    at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:430)
    at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:100)
    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)
    Edited by: user5823244 on Dec 14, 2008 2:59 AM

    Hi,
    It seems there are two problems going on here:
    (1) Forceful shutdowns should not (must not) normally corrupt the file store. There may be a bug in WL, or it may be the admin is arbitrarily deleting some file store files while leaving others in place (not supported).
    (2) "Even after successfully processing the message, the message which is logged in the File Store is not deleted."
    This is a strong indicator that there's an application error and the message is not actually getting deleted. The file store size is proportional to the number of current messages (successfully processing/acknowledging/committing a received message frees space for new messages), and is not proportional to the number of successfully processed messages.
    I think it's likely that the application isn't actually successfully processing the message but is instead receiving a message somehow and is either:
    (A) throwing an exception from within an XA-or-non-XA-MDB or auto-ack-onMessage() and somehow forcing the message into a state where its not being redelivered for reprocessing
    (B) specifying a transacted session and failing to call session.commit()
    (C) specifying an XA transaction capable receive and failing to call commit
    (D) specifying a "client acknowledge" mode and failing to call acknowledge .
    For evidence, check the console statistics for the destination after "successfully processing" all sent messages: the value of "current" + "pending" should be zero once all processing completes, the value of "received (aka total)" should match the sent message count. If the "current" + "pending" value is non-zero, then this is an indication there are messages that were not successfully processed.
    Tom Barnes
    WebLogic Server Messaging Developer Team

  • JMS & JDBC - 2 phase distributed EJB transaction

    Hi-
    I've got a requirement for some session EJBs and message drive EJBs which have to update an Oracle 9i DB and send out JMS messages (SonicMQ). This all needs to be wrapped in a 2PC distributed transaction. I am currently evaluating whether it's better to use container managed transactions for this, or to roll our own resource coordinator to take explicit control of the transactions. Unfortunately, I haven't found much information / examples for 9iAS (Release 2) to do something like this using container managed transactions (2PC, distributed, JMS & JDBC). Can anyone can point me to some examples, documentation, tips, etc?
    Thanks in advance. Also please note that my email is wrong (and i can't seem to change it), so please don't try to send email there.
    arun

    It doesn't sounds like these 2 operations are running together in a
              transaction. Otherwise, these would be atomic.
              First off, make sure that you get your JDBC connection from a
              TxDataSource, and make sure that your JMS queue send is in an XA
              transaction.
              -- Rob
              Sunita Ajwani wrote:
              > In a Distributed transaction involving a JMS queue and a XA-compliant JDBC resource,
              > messages are persisted to the queue before the persist is invoked on the Database
              > side. The next application picks up the message from the queue but does not find
              > the related data in the database.How do we avoid this?
              > We are using
              > Weblogic Server 6.1 on unix box
              > SunOS gemini 5.8 Generic_108528-07 sun4u sparc SUNW,Ultra-4
              >
              > Appreciate any response
              >
              

  • 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 advance

    This 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

  • Weblogic server 9.2 How to clear up JMS file store messages

    Hi,
    We are facong one issue in our weblogic production environment. The JMS file store size has become 7.2 G and its eatimg up almost all the server space. I have cheked through the jms module queues/ topics to see that if any messages are pending anywhere but nothing signifficant I can find out. Now our requirement is to clear up the file store the freeup the server space.
    Could you please recommend how to do that in the backend.
    Thanks
    Rahul

    Hi Rahul,
    Store files grow to fit all current stored objects, but, as stored objects are deleted, the freed space is re-used for new persistent objects. It's possible your store grew to an unprecedented size because it was temporarily forced to store many objects - in which case you can shrink the file store using the store compression tool described by the other poster.
    On the other hand, in almost all cases, unexpectedly large backlogs are generated due to either (A) an accumulation of a backlog of unprocessed messages, or (B) a bug in an application that processes received messages but never acknowledges them, such as may happen when an application creates a durable subscription on a topic but fails to service the subscription.
    I recommend (again) checking your 'current' and 'pending' message statistics for each and every JMS Server, SAF Agent, and destination that the store hosts. You can also check your store statistics to see which 'connections' are developing a large accumulation of objects.
    Regards,
    Tom
    P.S. You can post JMS related questions to the WebLogic Server JMS newsgroup.

  • 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,
    Gomathi

    Which is the output of the script? Do you receive any errors?

  • How to register MySQL JDBC Driver in OC4J

    Does anyone know how to register the MySQL JDBC driver in OC4J ?

    When your application must connect to heterogeneous databases, use DataDirect JDBC drivers. DataDirect JDBC drivers are not meant to be used with an Oracle database but for connecting to non-Oracle databases, such as Microsoft, SQLServer, Sybase and DB2. If you want to use DataDirect drivers with OC4J, add corresponding entries for each database in the data-sources.xml file.
    Please see the DataDirect documentation for information on installing the DataDirect JDBC drivers.
    The following is an example of a data source entry for SQLServer. For more detailed information, see the DataDirect Connect JDBC User's Guide and Reference.
    <data-source
    class="com.evermind.sql.DriverManagerDataSource"
    name="MerantDS"
    location="jdbc/MerantCoreSSDS"
    xa-location="jdbc/xa/MerantSSXADS"
    ejb-location="jdbc/MerantSSDS"
    connection-driver="com.merant.datadirect.jdbc.sqlserver.SQLServerDriver"
    username="test"
    password="secret"
    url="jdbc:sqlserver//hostname:port;User=test;Password=secret"
    inactivity-timeout="30"
    />
    For a DB2 database, here is a data source configuration sample:
    <data-source
    class="com.evermind.sql.DriverManagerDataSource"
    name="MerantDS"
    location="jdbc/MerantDB2DS"
    xa-location="jdbc/xa/MerantDB2XADS"
    ejb-location="jdbc/MerantDB2DS"
    connection-driver="com.merant.datadirect.jdbc.db2.DB2Driver"
    username="test"
    password="secret"
    url="jdbc:sqlserver//hostname:port;LocationName=jdbc;CollectionId=default;
    inactivity-timeout="30"
    />
    For a Sybase database, here is a data source configuration sample:
    <data-source
    class="com.evermind.sql.DriverManagerDataSource"
    name="MerantDS"
    location="jdbc/MerantCoreSybaseDS"
    xa-location="jdbc/xa/MerantSybaseXADS"
    ejb-location="jdbc/MerantSybaseDS"
    connection-driver="com.merant.datadirect.jdbc.sybase.SybaseDriver"
    username="test"
    password="secret"
    url="jdbc:sqlserver//hostname:port;User=test;Password=secret"
    inactivity-timeout="30"
    />
    please link: http://otn.oracle.com/docs/products/ias/doc_library/903doc_otn/generic.903/a97690/ds3.htm#100612

  • Problem: sending JMS message in other oc4j

    I have two app server instances " OC4J (1) " and " OC4J (2) ". (snandalone 10.1.3.0.0 - Developer Preview 3 (build 041119.0001.2385)). The containers work on Windows2000 in different machines connected by the LAN.
    OC4J (1):
    I have J2ee of the application [app(1)] (ex. Servlet (1) or MDB (1)) in OC4J (1).
    OC4J (2):
    I have J2ee of the application [app(2)] deploy in OC4J (2) [included Servlet (2) or MDB (2)] . The Servlet (2), or MDB (2) - empty stub, for example code Servlet2:
    package mypackage;
    import javax.servlet. *;
    import javax.servlet.http. *;
    import java.io. PrintWriter;
    import java.io. IOException;
    public class Servlet1 extends HttpServlet
    private static final String CONTENT_TYPE = " text/html; charset=windows-1251 ";
    public void init (ServletConfig config) throws ServletException
    super.init (config);
    public void doGet (HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException
    response.setContentType (CONTENT_TYPE);
    PrintWriter out = response.getWriter ();
    out.println (" < html > ");
    out.println (" < head > < title > Servlet1 < /title > < /head > ");
    out.println (" < body > ");
    out.println (" < p > The servlet has received a GET. This is the reply. </p > ");
    out.println (" < /body > < /html > ");
    out.close ();
    I have configuration JMS (2) Queue in jms.xml on OC4J (2):
    < jms-server...... port = "9127"
    < queue name = " Demo Queue " location = "jms/demoQueue" > <description> A dummy queue </description> </queue>
    < queue-connection-factory name = "jms/QueueConnectionFactory" location = "jms/QueueConnectionFactory" / >
    </jms-server>
    It JMS (2) Queue already is present in an OC4J 10.1.3 version.
    My task:
    The J2ee application (1) (ex. Servlet (1)) on OC4J (1) it is necessary to receive connection with JMS (2) (on remote OC4J (2)).
    Variant 1: a code in Servlet (1):
    Hashtable env=new Hashtable (8);
    env.put (Context. PROVIDER_URL, " ormi: // host_OC4J (2)/app(2):23792 ");
    env.put (Context. INITIAL_CONTEXT_FACTORY, " oracle.j2ee.rmi. RMIInitialContextFactory ");
    env.put (Context. SECURITY_PRINCIPAL, "admin");
    env.put (Context. SECURITY_CREDENTIALS, "admin");
    env.put ("dedicated.connection", "true");
    InitialContext ic = new InitialContext (env);
    QueueConnectionFactory connectionFactory = (QueueConnectionFactory)
    ic.lookup ("jms/QueueConnectionFactory");
    QueueConnection connection = connectionFactory.createQueueConnection ();
    connection.start ();
    queueSession =
    connection.createQueueSession (false, Session. AUTO_ACKNOWLEDGE);
    Queue queue = (Queue) ic.lookup ("jms/demoQueue");
    ic.close ();
    while (true)
    // - send in JMS (2)
    Problem:
    The Servlet (1) [in oc4j (1)] established JMS connection with oc4j (2) and begins to pass the messages [in JMS Queue (2)].
    The Oc4j (2) creates some system thread for this JMS connection.
    If the oc4j (1) lose network connection (example- break the cable) then created in oc4j (2) system thread is not destroyed.
    Saw if this situation repeats some times that amount of the system thread in oc4j (2) is grow.
    To me has answered:
    In 10.1.3, the supported connection path is through the Resource Adapter (using OracleASjms.rar). The Resource Adapter offers many benefits, including the removal of stale connection threads. You have configured your application to bypass the Resource Adapter and use a direct path to OC4J JMS. You will need to create a resource mapping from your OC4J JMS admin objects (queues, topics, and connection factories) to new Resource Adapter admin objects. You can find the details of how to do this in the documentation for OC4J 10g (10.1.3) Developer Preview 3 on OTN.
    You can find the link to the documentation for OC4J DP3 here:
    http: // www.oracle.com/technology/tech/java/oc4 j/1013/index.html
    Then I have tried Variant 2:
    I need to receive connection with remote JMS (2) via generic JMS resource adapter (OracleAS Jms).
    In OC4J (2), it is necessary сonfigure the generic JMS resource adapter (OracleAS Jms) to work with Queue "jms/demoQueue".
    According to the documentation Oracle ® Containers for J2EE Services Guide10g Release 2 (10.1.3) and example
    http: // www.oracle.com/technology/tech/java/oc4 j/1013/howtos/how-to-jca-intro/doc/how- to-jca-intro.html anything it is not necessary to do.
    Note that if you use the generic JMS resource adapter in an OC4J 10.1.3 version that is newer than the OC4J 10.0.3 Developer Preview 2, you can skip. In OC4J 10.1.3 it is a step is already made.
    Code in Servlet (1):
    Hashtable env=new Hashtable (8);
    env.put (Context. PROVIDER_URL, " ormi: // host_OC4J (2) /app (2):23792 ");
    env.put (Context. INITIAL_CONTEXT_FACTORY, " oracle.j2ee.rmi. RMIInitialContextFactory ");
    env.put (Context. SECURITY_PRINCIPAL, "admin");
    env.put (Context. SECURITY_CREDENTIALS, "admin");
    env.put ("dedicated.connection", "true");
    InitialContext ic = new InitialContext (env);
    QueueConnectionFactory connectionFactory = (QueueConnectionFactory)
    ic.lookup (" java:comp/resource/oc4jjms/jms/QueueCon nectionFactory ");
    QueueConnection connection = connectionFactory.createQueueConnection ();
    connection.start ();
    queueSession =
    connection.createQueueSession (false, Session. AUTO_ACKNOWLEDGE);
    Queue queue = (Queue) ic.lookup (" java:comp/resource/oc4jjms/jms/demoQueu e ");
    ic.close ();
    while (true)
    // - send in JMS (2)
    This code works.
    But!!!!!!
    The problem - removal of stale connection threads in OC4J (2) instances has not solve. If the oc4j (1) lose network connection (example- break the cable) then created in oc4j (2) system thread is not destroyed.
    How to me to write a code of connection with JMS (2) in Servlet (1), that Resource Adapter (in OC4J (2)) the removal of stale connection threads ???

    I have two app server instances " OC4J (1) " and " OC4J (2) ". (snandalone 10.1.3.0.0 - Developer Preview 3 (build 041119.0001.2385)). The containers work on Windows2000 in different machines connected by the LAN.
    OC4J (1):
    I have J2ee of the application [app(1)] (ex. Servlet (1) or MDB (1)) in OC4J (1).
    OC4J (2):
    I have J2ee of the application [app(2)] deploy in OC4J (2) [included Servlet (2) or MDB (2)] . The Servlet (2), or MDB (2) - empty stub, for example code Servlet2:
    package mypackage;
    import javax.servlet. *;
    import javax.servlet.http. *;
    import java.io. PrintWriter;
    import java.io. IOException;
    public class Servlet1 extends HttpServlet
    private static final String CONTENT_TYPE = " text/html; charset=windows-1251 ";
    public void init (ServletConfig config) throws ServletException
    super.init (config);
    public void doGet (HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException
    response.setContentType (CONTENT_TYPE);
    PrintWriter out = response.getWriter ();
    out.println (" < html > ");
    out.println (" < head > < title > Servlet1 < /title > < /head > ");
    out.println (" < body > ");
    out.println (" < p > The servlet has received a GET. This is the reply. </p > ");
    out.println (" < /body > < /html > ");
    out.close ();
    I have configuration JMS (2) Queue in jms.xml on OC4J (2):
    < jms-server...... port = "9127"
    < queue name = " Demo Queue " location = "jms/demoQueue" > <description> A dummy queue </description> </queue>
    < queue-connection-factory name = "jms/QueueConnectionFactory" location = "jms/QueueConnectionFactory" / >
    </jms-server>
    It JMS (2) Queue already is present in an OC4J 10.1.3 version.
    My task:
    The J2ee application (1) (ex. Servlet (1)) on OC4J (1) it is necessary to receive connection with JMS (2) (on remote OC4J (2)).
    Variant 1: a code in Servlet (1):
    Hashtable env=new Hashtable (8);
    env.put (Context. PROVIDER_URL, " ormi: // host_OC4J (2)/app(2):23792 ");
    env.put (Context. INITIAL_CONTEXT_FACTORY, " oracle.j2ee.rmi. RMIInitialContextFactory ");
    env.put (Context. SECURITY_PRINCIPAL, "admin");
    env.put (Context. SECURITY_CREDENTIALS, "admin");
    env.put ("dedicated.connection", "true");
    InitialContext ic = new InitialContext (env);
    QueueConnectionFactory connectionFactory = (QueueConnectionFactory)
    ic.lookup ("jms/QueueConnectionFactory");
    QueueConnection connection = connectionFactory.createQueueConnection ();
    connection.start ();
    queueSession =
    connection.createQueueSession (false, Session. AUTO_ACKNOWLEDGE);
    Queue queue = (Queue) ic.lookup ("jms/demoQueue");
    ic.close ();
    while (true)
    // - send in JMS (2)
    Problem:
    The Servlet (1) [in oc4j (1)] established JMS connection with oc4j (2) and begins to pass the messages [in JMS Queue (2)].
    The Oc4j (2) creates some system thread for this JMS connection.
    If the oc4j (1) lose network connection (example- break the cable) then created in oc4j (2) system thread is not destroyed.
    Saw if this situation repeats some times that amount of the system thread in oc4j (2) is grow.
    To me has answered:
    In 10.1.3, the supported connection path is through the Resource Adapter (using OracleASjms.rar). The Resource Adapter offers many benefits, including the removal of stale connection threads. You have configured your application to bypass the Resource Adapter and use a direct path to OC4J JMS. You will need to create a resource mapping from your OC4J JMS admin objects (queues, topics, and connection factories) to new Resource Adapter admin objects. You can find the details of how to do this in the documentation for OC4J 10g (10.1.3) Developer Preview 3 on OTN.
    You can find the link to the documentation for OC4J DP3 here:
    http: // www.oracle.com/technology/tech/java/oc4 j/1013/index.html
    Then I have tried Variant 2:
    I need to receive connection with remote JMS (2) via generic JMS resource adapter (OracleAS Jms).
    In OC4J (2), it is necessary сonfigure the generic JMS resource adapter (OracleAS Jms) to work with Queue "jms/demoQueue".
    According to the documentation Oracle ® Containers for J2EE Services Guide10g Release 2 (10.1.3) and example
    http: // www.oracle.com/technology/tech/java/oc4 j/1013/howtos/how-to-jca-intro/doc/how- to-jca-intro.html anything it is not necessary to do.
    Note that if you use the generic JMS resource adapter in an OC4J 10.1.3 version that is newer than the OC4J 10.0.3 Developer Preview 2, you can skip. In OC4J 10.1.3 it is a step is already made.
    Code in Servlet (1):
    Hashtable env=new Hashtable (8);
    env.put (Context. PROVIDER_URL, " ormi: // host_OC4J (2) /app (2):23792 ");
    env.put (Context. INITIAL_CONTEXT_FACTORY, " oracle.j2ee.rmi. RMIInitialContextFactory ");
    env.put (Context. SECURITY_PRINCIPAL, "admin");
    env.put (Context. SECURITY_CREDENTIALS, "admin");
    env.put ("dedicated.connection", "true");
    InitialContext ic = new InitialContext (env);
    QueueConnectionFactory connectionFactory = (QueueConnectionFactory)
    ic.lookup (" java:comp/resource/oc4jjms/jms/QueueCon nectionFactory ");
    QueueConnection connection = connectionFactory.createQueueConnection ();
    connection.start ();
    queueSession =
    connection.createQueueSession (false, Session. AUTO_ACKNOWLEDGE);
    Queue queue = (Queue) ic.lookup (" java:comp/resource/oc4jjms/jms/demoQueu e ");
    ic.close ();
    while (true)
    // - send in JMS (2)
    This code works.
    But!!!!!!
    The problem - removal of stale connection threads in OC4J (2) instances has not solve. If the oc4j (1) lose network connection (example- break the cable) then created in oc4j (2) system thread is not destroyed.
    How to me to write a code of connection with JMS (2) in Servlet (1), that Resource Adapter (in OC4J (2)) the removal of stale connection threads ???

  • 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
              >
              

  • Grouping JMS & JDBC transaction with JTA outside of an app server

    hi,
    Can anyone help me or direct me to some code/configuration that shows how to combine JDBC + JMS into one distributed transaction outside of an app server.
    thanks in advance
    michael

    Hi,
              Well, transaction guru's please correct what I say here, but from what I
              understand of your problem here goes:
              If you begin a user transaction your are going to be starting a distributed
              transaction. That's the point of doing it, and hence that's why you have an
              XA. You have more than once resource participating in a transaction, and
              that is what UserTransaction was created for. You can't do it with a local
              transaction, which is for one resource only. I hope that answers "why
              would I need a XA". Even if both resources are hosted by WebLogic, you have
              explicitly asked for a UserTransaction...WL will optimize it if both are on
              same server, but still.. In addition, if you have a true XA data source and
              connection pool, then I would imagine that WL would list the transaction
              system of the DB too....whcih won't be local.
              As for your other problem, it seems to me that you have a connection pool of
              connections that are not XA-aware. If you set the attribute in the
              datasource and enable emulation, then the datasource becomes XA aware, but
              only sort of. WL handles the XA behaviour of that resource, but with
              limitations (you can't have more than one resource with XA emulation in the
              same Tx). If you are using a connection factory with a different store that
              uses XA-emulation, as well as straight JDBC from yet another pool using XA
              emulation, then you will also get problems. Best is to use a real driver
              that supports XA.
              Regards,
              Jon
              

  • Problem in sending JMS message on remote OC4J

    I have two OC4J standalone (10.1.3.0.0 build 041119.0001.2385)
    The containers work on Windows2000 in different machines connected by the LAN.
    The First container has deployed application from example http://www.oracle.com/technology/tech/java/oc4j/1013/howtos/how-to-jca-intro/doc/how-to-jca-intro.html
    The second container has j2ee application (Servlet) that sending JMS messages in the queue of the first container.
    Code Servlet in second OC4J:
    package mypackage2;
    import javax.servlet. *;
    import javax.servlet.http. *;
    import java.io. PrintWriter;
    import java.io. IOException;
    import javax.jms. *;
    import javax.naming. *;
    import java.util. *;
    public class Servlet1 extends HttpServlet
    private static final String CONTENT_TYPE = "text/html;charset=windows-1251";
    public void init (ServletConfig config) throws ServletException
    super.init (config);
    String QUEUE_NAME = "OracleASjms/MyQueue1";
    String QUEUE_CONNECTION_FACTORY = "OracleASjms/MyQCF";
    public void doGet (HttpServletRequest request, HttpServletResponse response)
    throws ServletException, IOException
    response.setContentType (CONTENT_TYPE);
    PrintWriter out = response.getWriter ();
    out.println (" < html > ");
    out.println (" < head > < title > Servlet1 < /title > < /head > ");
    out.println (" < body > ");
    try
    Hashtable env = new Hashtable ();
    env.put (Context. INITIAL_CONTEXT_FACTORY, "oracle.j2ee.rmi.RMIInitialContextFactory");
    env.put (Context. SECURITY_PRINCIPAL, "admin");
    env.put (Context. SECURITY_CREDENTIALS, "admin");
    env.put (Context. PROVIDER_URL, "ormi://host_OC4J_1:23791/jcamdb");
    env.put ("dedicated.rmicontext", "true");
    InitialContext ic = new InitialContext (env);
    QueueConnectionFactory connectionFactory = (QueueConnectionFactory)ic.lookup (QUEUE_CONNECTION_FACTORY);
    QueueConnection connection = connectionFactory.createQueueConnection ();
    connection.start ();
    QueueSession queueSession =
    connection.createQueueSession (false, Session.AUTO_ACKNOWLEDGE);
    Queue queue = (Queue) ic.lookup (QUEUE_NAME);
    ic.close ();
    System.out.println (" Queue: " + queue);
    QueueSender sender = queueSession.createSender (queue);
    System.out.println (" creating Message: " + queue);
    Message message = queueSession.createMessage ();
    System.out.println (" Message created ");
    message.setJMSType ("theMessage");
    message.setLongProperty ("time", System.currentTimeMillis ());
    message.setStringProperty ("id", "11111");
    message.setStringProperty ("oamount", "55555");
    message.setStringProperty ("message", "77777");
    message.setStringProperty ("RECIPIENT", "MDB");
    System.out.println (" Sending message... ");
    sender.send (message);
    System.out.println (" Message sent ");
    sender.close ();
    queueSession.close ();
    connection.close ();
    catch (Exception e)
    System.out.println (" ** TEST FAILED ** < br > Exception: " + e);
    out.println (e.toString ());
    e.printStackTrace ();
    out.println (" < p > The servlet has received a GET. This is the reply. < /p
    ");out.println (" < /body > < /html > ");
    out.close ();
    Error: This code send message in The First container, and should send in the second OC4J !!!!
    Please answer :
    As configure (what code it is necessary to write) servlet (any J2EE the application in OC4J) to use a path to OC4J JMS (remote OC4J JMS) through the Resource Adapter (using OracleASjms.rar). ???

    I have two OC4J standalone (10.1.3.0.0 build 041119.0001.2385)
    The containers work on Windows2000 in different machines connected by the LAN.
    The First container has deployed application from example http://www.oracle.com/technology/tech/java/oc4j/1013/howtos/how-to-jca-intro/doc/how-to-jca-intro.html
    The second container has j2ee application (Servlet) that sending JMS messages in the queue of the first container.
    Code Servlet in second OC4J:
    package mypackage2;
    import javax.servlet. *;
    import javax.servlet.http. *;
    import java.io. PrintWriter;
    import java.io. IOException;
    import javax.jms. *;
    import javax.naming. *;
    import java.util. *;
    public class Servlet1 extends HttpServlet
    private static final String CONTENT_TYPE = "text/html;charset=windows-1251";
    public void init (ServletConfig config) throws ServletException
    super.init (config);
    String QUEUE_NAME = "OracleASjms/MyQueue1";
    String QUEUE_CONNECTION_FACTORY = "OracleASjms/MyQCF";
    public void doGet (HttpServletRequest request, HttpServletResponse response)
    throws ServletException, IOException
    response.setContentType (CONTENT_TYPE);
    PrintWriter out = response.getWriter ();
    out.println (" < html > ");
    out.println (" < head > < title > Servlet1 < /title > < /head > ");
    out.println (" < body > ");
    try
    Hashtable env = new Hashtable ();
    env.put (Context. INITIAL_CONTEXT_FACTORY, "oracle.j2ee.rmi.RMIInitialContextFactory");
    env.put (Context. SECURITY_PRINCIPAL, "admin");
    env.put (Context. SECURITY_CREDENTIALS, "admin");
    env.put (Context. PROVIDER_URL, "ormi://host_OC4J_1:23791/jcamdb");
    env.put ("dedicated.rmicontext", "true");
    InitialContext ic = new InitialContext (env);
    QueueConnectionFactory connectionFactory = (QueueConnectionFactory)ic.lookup (QUEUE_CONNECTION_FACTORY);
    QueueConnection connection = connectionFactory.createQueueConnection ();
    connection.start ();
    QueueSession queueSession =
    connection.createQueueSession (false, Session.AUTO_ACKNOWLEDGE);
    Queue queue = (Queue) ic.lookup (QUEUE_NAME);
    ic.close ();
    System.out.println (" Queue: " + queue);
    QueueSender sender = queueSession.createSender (queue);
    System.out.println (" creating Message: " + queue);
    Message message = queueSession.createMessage ();
    System.out.println (" Message created ");
    message.setJMSType ("theMessage");
    message.setLongProperty ("time", System.currentTimeMillis ());
    message.setStringProperty ("id", "11111");
    message.setStringProperty ("oamount", "55555");
    message.setStringProperty ("message", "77777");
    message.setStringProperty ("RECIPIENT", "MDB");
    System.out.println (" Sending message... ");
    sender.send (message);
    System.out.println (" Message sent ");
    sender.close ();
    queueSession.close ();
    connection.close ();
    catch (Exception e)
    System.out.println (" ** TEST FAILED ** < br > Exception: " + e);
    out.println (e.toString ());
    e.printStackTrace ();
    out.println (" < p > The servlet has received a GET. This is the reply. < /p
    ");out.println (" < /body > < /html > ");
    out.close ();
    Error: This code send message in The First container, and should send in the second OC4J !!!!
    Please answer :
    As configure (what code it is necessary to write) servlet (any J2EE the application in OC4J) to use a path to OC4J JMS (remote OC4J JMS) through the Resource Adapter (using OracleASjms.rar). ???

  • Oracle JDBC Driver and OC4J 9.0.2.0.0A

    Where is the JDBC Driver located in OC4J 9.0.2.0.0A? In
    1.0.2.2.1 it was located in j2ee\home\lib (as it should be
    IMHO). In OC4J 9.0.2.0.0A there is no file classes12.zip at all
    (only classes12dms.jar?)
    Any hints would be very welcome.
    Regards
    Stefan

    Oracle JDBC driver is in jdbc\lib directory
    jdbc directory is in the sae level as j2ee directory

  • Can't connect using OCI JDBC driver in OC4J 10.1.3.3 standalone

    Hi all,
    I've recently upgraded my JDev from 10.1.3.2 to 10.1.3.3 and now I'm unable to establish any OCI connections with my local Oracle 10.1.0.4 database. Not even through a connection pool. The strangest thing is that when I test an OCI connection running from JDeveloper it works fine and the JDBC jars and the oci client are exactly the same.
    The error is always the same when I execute a test on a connection pool using the OCI driver:
    WARNING J2EE DS-00001 Exception occurred testing connection. Exception: java.sql.SQLException: Closed Connection.
    If I just change the driver to the THIN one, the same test works. If I take the same URL from the OCI test and use it in a test class and run it inside JDeveloper, it works also.
    I've even downloaded the instant client 10.1.0.5 (which happens to be exactly the same version of the JDBC driver that comes with JDev 10.1.3.3) and tried to use it with no success.
    THIN connections are working just fine. The problem happens only when I try to connect via OCI and this problem was not happening in version 10.1.3.2.
    Any help?

    I found the cause of this problem. It turns out that you must be very careful with the environment variable ORACLE_HOME. On Windows, normally, we don't even set this variable because most applications are able to get it from the system's registry.
    Well, it happened that I've edited the script start_oc4j.bat and, for organization reasons, I set the ORACLE_HOME variable with my JDeveloper's home directory (which is the same as my OC4J standalone's). By doing that, I kind of confused the OCI client. Once I removed the "set ORACLE_HOME=C:\JDev" line from the script, everything worked just fine again.
    So, always remember: avoid setting environment variable ORACLE_HOME when using Windows and, if you must set it, be sure to do it right.
    Regards,
    Eduardo.

Maybe you are looking for

  • New Nano 4Gb is not recognised by itunes but is by Windows XP

    I previously had a iPod Mini which recently failed so I have purchased a 4Gb Nano this week However when I connect it to my computer I can see it in explorer but not in iTunes (when I conect my girlfriends 2 Gb Nano to my computer it is recognised by

  • Premiere Pro CC won't let me relocating media on a server?

    Im using premiere pro cc and i am connected to a server at work, i had the media linked before and now when i open it and i go to link the media to the file or locate the files, i can't see the server im connected to for some reason, im fully connect

  • Add attachments to List Item using JavaScript Client object model in SP2010

    Hi All , I have created custom form for submitng data in list using javascript client object model/jquery . Now I want to add option to uplaod multiple attachments to that list item also . Is there option with client object model for uplaoding attach

  • Mac needs to force restart too often

    My mac keeps giving me an image on the screen (http://cjmiscfiles.webs.com/20110124211705.jpg) which says I need to force restart my Mac. I got this message 2 times in a week, and I got it once before. I just got my Mid-2010 Mac when it was first out

  • Callable object and Guided procedures

    Hi all, Where we use callable objects? i want to know about the basic of callable object and guided procedure? sorry if my question is very silly