10 Replies Latest reply on May 6, 2003 9:42 PM by sashahunt

    jdbc2 Persistance with Oracle gives Error

    sashahunt Newbie

      Hello,

      I am upgrading from 3.0.0-tomcat-4.0.3 to 3.0.7-jakarta-tomcat-4.1.24. I previously downloaded the oracle-jms-service.xml which worked OK with 3.0.0-tomcat-4.0.3. I noticed that when I did a failover test, some messages were not redelivered, so that is why I'm upgrading (bug fix?).
      Anyway, I downloaded what I think is the correct branch/version of oracle-jms-service.xml
      (
      Revision 1.1.2.5 / (as text) / (view) - annotate - [select for diffs] , Sat Mar 1 09:13:45 2003 UTC (8 weeks, 2 days ago) by ejort
      Branch: Branch_3_0
      CVS Tags: Rel_3_0_0_9, JBoss_3_0_8_RC1, JBoss_3_0_7_RC3, JBoss_3_0_7_RC2, JBoss_3_0_7
      Changes since 1.1.2.4: +4 -2 lines
      Diff to previous 1.1.2.4 to branch point 1.1 )

      with the following error:

      2003-04-28 08:40:46,027 INFO [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Starting
      2003-04-28 08:40:46,037 INFO [org.jboss.ejb.plugins.jms.DLQHandler] Creating
      2003-04-28 08:40:46,047 ERROR [org.jboss.ejb.plugins.jms.DLQHandler] Initialization failed
      javax.jms.JMSException: Error creating the dlq connection: XAConnectionFactory not bound
      at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:137)
      at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:136)
      at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:608)
      at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:824)
      at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:165)
      at org.jboss.ejb.MessageDrivenContainer.start(MessageDrivenContainer.java:200)
      at org.jboss.ejb.Container.invoke(Container.java:782)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:1003)
      at $Proxy4.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:413)
      at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
      at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
      at $Proxy25.start(Unknown Source)
      at org.jboss.ejb.EjbModule.startService(EjbModule.java:404)
      at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:165)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:1003)
      at $Proxy4.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:413)
      at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
      at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
      at $Proxy11.start(Unknown Source)
      at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:395)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:814)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:627)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:591)
      at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
      at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
      at $Proxy3.deploy(Unknown Source)
      at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:435)
      at org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDeploymentScanner.java:656)
      at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:507)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:266)
      at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:165)
      at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:1003)
      at $Proxy0.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:413)
      at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
      at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
      at $Proxy2.start(Unknown Source)
      at org.jboss.deployment.SARDeployer.start(SARDeployer.java:232)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:814)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:627)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:591)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:575)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
      at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:324)
      at org.jboss.system.server.ServerImpl.start(ServerImpl.java:221)
      at org.jboss.Main.boot(Main.java:148)
      at org.jboss.Main$1.run(Main.java:381)
      at java.lang.Thread.run(Thread.java:536)
      2003-04-28 08:40:46,528 INFO [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Started
      2003-04-28 08:40:46,528 INFO [org.jboss.ejb.EjbModule] Started
      2003-04-28 08:40:46,528 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/C:/jboss-3.0.7_jakarta-tomcat-4.1.24/server/all/deploy/TOMSAdapter.jar
      2003-04-28 08:40:46,538 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.7_jakarta-tomcat-4.1.24/server/all/deploy/ZCOREAdapter.jar
      2003-04-28 08:40:46,548 WARN [org.jboss.ejb.plugins.jms.JMSContainerInvoker] JMS provider failure detected:

      All I need is a Jboss-tomcat version with Oracle 9.2 persistence that has the bug fix to redeliver messages after JMS Provider (JBossMQ) failure. It would be great if one of the versions I already have can be made to work.

      Thanks!

        • 1. Re: jdbc2 Persistance with Oracle gives Error
          sashahunt Newbie

          ... I meant to say the "oracle-jbossmq-service.xml"...

          • 2. Re: jdbc2 Persistance with Oracle gives Error
            Adrian Brock Master

            Hi, why is the XAConnectionFactory not bound?

            You will need to look backwards through the log,
            for the initial failure.

            Regards,
            Adrian

            • 3. Re: jdbc2 Persistance with Oracle gives Error
              sashahunt Newbie

              Hi,
              Thanks,

              That was the initial error... I think it may be a
              requirement. I will try that.

              In the meantime, There is another error that I am
              getting due to the line:


              <depends optional-attribute-name="TransactionManagerService">jboss.tm:service=TransactionManagerService


              in the jdbc2.PersistenceManager MBean. It says that there is no writable attribute "TransactionManagerService". I tried changing the service name from TransactionManagerService to TransactionManager (which is the one that seems to be being built), but still, unless i take out the "option-attribute-name" tag, this gives me an error.

              Any ideas? Am I using the wrong version?

              Thanks.

              • 4. Re: jdbc2 Persistance with Oracle gives Error
                sashahunt Newbie

                Still no luck getting rid of the first error, even with depends defined.

                Any ideas?

                • 5. Re: jdbc2 Persistance with Oracle gives Error
                  Adrian Brock Master

                  I think you have confused the versions.
                  The 3.0.7 does not include a transaction manager
                  service attribute. This applies to 3.2

                  http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/jbossmq/src/etc/server/examples/deploy/oracle-jbossmq-service.xml?annotate=1.1.2.5
                  Regards,
                  Adrian

                  • 6. Re: jdbc2 Persistance with Oracle gives Error
                    sashahunt Newbie

                    Thanks again.

                    I downloaded this one. I still got the error. So, I took it out and put in the original out-of-box one. I think I may be on to the issue, because I got the following error:

                    2003-04-30 15:53:48,742 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] MBeanException: Exception in MBean operation 'checkIncompleteDeployments()'
                    Cause: Incomplete Deployment listing:
                    Packages waiting for a deployer:

                    Incompletely deployed packages:

                    MBeans waiting for classes:

                    MBeans waiting for other MBeans:
                    [ObjectName: jboss.jca:service=LocalTxCM,name=OracleDS
                    state: CONFIGURED
                    I Depend On: jboss.jca:service=LocalTxDS,name=OracleDS
                    jboss.jca:service=LocalTxPool,name=OracleDS
                    jboss.jca:service=CachedConnectionManager
                    jboss.security:name=JaasSecurityManager
                    jboss.jca:service=RARDeployer

                    Depends On Me: ]

                    Is the oracle-service.xml I am using not good with this version?? I don't see offhand what is wrong with it, though. Here is a copy:

                    ------------------------------------------------------

                    <?xml version="1.0" encoding="UTF-8"?>

                    <!-- ===================================================================== -->
                    <!-- -->
                    <!-- JBoss Server Configuration -->
                    <!-- -->
                    <!-- ===================================================================== -->



                    <!-- ==================================================================== -->
                    <!-- ConnectionManager setup for Oracle dbs -->
                    <!-- Build jmx-api (build/build.sh all) and view for config documentation -->
                    <!-- Thanks to Steven Coy -->
                    <!-- ==================================================================== -->




                    <!-- Include a login module configuration named OracleDbRealm.
                    Update your login-conf.xml, here is an example for a
                    ConfiguredIdentityLoginModule:

                    <application-policy name = "OracleDbRealm">

                    <login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule" flag = "required">
                    <module-option name = "principal">pubsub</module-option>
                    <module-option name = "userName">pubsub</module-option>
                    <module-option name = "password">pubsub</module-option>
                    <module-option name = "managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=OracleDS</module-option>
                    </login-module>

                    </application-policy>

                    NOTE: the application-policy name attribute must match SecurityDomainJndiName, and the
                    module-option name = "managedConnectionFactoryName"
                    must match the object name of the ConnectionManager you are configuring here.
                    -->

                    <!--uncomment out this line if you are using the OracleDbRealm above BETH -->
                    OracleDbRealm


                    <depends optional-attribute-name="ManagedConnectionFactoryName">
                    <!--embedded mbean-->


                    OracleDS



                    <config-property name="ConnectionURL" type="java.lang.String">jdbc:oracle:thin:@cat-3.catconsulting.com:1521:student</config-property>
                    <config-property name="DriverClass" type="java.lang.String">oracle.jdbc.driver.OracleDriver</config-property>
                    <!-- set these only if you want only default logins, not through JAAS -->
                    <config-property name="UserName" type="java.lang.String">pubsub</config-property>
                    <config-property name="Password" type="java.lang.String">pubsub</config-property>




                    <!--Below here are advanced properties -->
                    <!--hack-->
                    <depends optional-attribute-name="OldRarDeployment">jboss.jca:service=RARDeployment,name=JBoss LocalTransaction JDBC Wrapper



                    <depends optional-attribute-name="ManagedConnectionPool">
                    <!--embedded mbean-->


                    0
                    50
                    5000
                    15
                    <!--criteria indicates if Subject (from security domain) or app supplied
                    parameters (such as from getConnection(user, pw)) are used to distinguish
                    connections in the pool. Choices are
                    ByContainerAndApplication (use both),
                    ByContainer (use Subject),
                    ByApplication (use app supplied params only),
                    ByNothing (all connections are equivalent, usually if adapter supports
                    reauthentication)-->
                    ByApplication



                    <depends optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedConnectionManager

                    <depends optional-attribute-name="JaasSecurityManagerService">jboss.security:name=JaasSecurityManager

                    java:/TransactionManager

                    <!--make the rar deploy! hack till better deployment-->
                    jboss.jca:service=RARDeployer





                    ------------------------------------------------------------------

                    Does this look OK?
                    If not, does anyone know where I can get a working oracle-service.xml for version
                    3.0.7_jakarta-tomcat-4.1.24?

                    • 7. Re: jdbc2 Persistance with Oracle gives Error
                      Adrian Brock Master

                      You have an old oracle-service.xml

                      The security manager is called
                      jboss.security:service=JaasSecurityManager

                      Regards,
                      Adrian

                      • 8. Re: jdbc2 Persistance with Oracle gives Error
                        sashahunt Newbie

                        Where can I get a new one? I don't have the download location....

                        • 9. Re: jdbc2 Persistance with Oracle gives Error
                          Adrian Brock Master

                          You can find one in the jboss release

                          docs/examples/jca

                          Regards,
                          Adrian

                          • 10. Re: jdbc2 Persistance with Oracle gives Error
                            sashahunt Newbie

                            Thanks!

                            Now it is working. I need to test now to make sure the redeliver after JMS Provider failure is working.

                            Thanks again.