1 Reply Latest reply: Jan 30, 2013 3:28 AM by René van Wijk RSS

    ORA-25228 error occurs when Foreign JMS Server connecting to the Oracle AQ

    988004
      Hi,

      I configure of a Foreign JMS Server that uses the Oracle JDBC Driver to connect to the AQ Topic. I use OSB messaging proxy service as a JMS client to connect the Foreign JMS Server. After the launch, I get the following error:
      ####<Jan 30, 2013 4:51:49 AM MSK> <Error> <EJB> <EPRUSARW0520> <osb_server1> <RequestEJB7826682746890400115XX35047bed.13c85602eea.X7f53> <<anonymous>> <> <0000Jm8w2Es6qI_5xRh8iW1H1sMk0001sD> <1359507109078> <BEA-010079> <An error occurred while attempting to receive a message from JMS for processing by a message-driven bean: oracle.jms.AQjmsException: JMS-120: Dequeue failed
      Nested exception: java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1
      ORA-06502: PL/SQL: numeric or value error
      ORA-06512: at line 11
      ORA-25228: timeout or end-of-fetch during message dequeue from MDM.ALL_NSI

      The exception is : oracle.jms.AQjmsException: JMS-120: Dequeue failed
           at oracle.jms.AQjmsError.throwEx(AQjmsError.java:315)
           at oracle.jms.AQjmsConsumer.jdbcDequeue(AQjmsConsumer.java:1620)
           at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:1035)
           at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:960)
           at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:938)
           at oracle.jms.AQjmsConsumer.receive(AQjmsConsumer.java:790)
           at weblogic.deployment.jms.WrappedMessageConsumer.receive(WrappedMessageConsumer.java:201)
           at weblogic.ejb.container.internal.JMSMessagePoller$1.run(JMSMessagePoller.java:262)
           at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
           at weblogic.ejb.container.internal.JMSConnectionPoller.doPrivilegedJMSAction(JMSConnectionPoller.java:2752)
           at weblogic.ejb.container.internal.JMSMessagePoller.processOneMessage(JMSMessagePoller.java:257)
           at weblogic.ejb.container.internal.JMSMessagePoller.pollContinuously(JMSMessagePoller.java:351)
           at weblogic.ejb.container.internal.JMSMessagePoller.pollForParent(JMSMessagePoller.java:483)
           at weblogic.ejb.container.internal.JMSMessagePoller.run(JMSMessagePoller.java:499)
           at java.lang.Thread.run(Thread.java:722)
      Caused by: java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1
      ORA-06502: PL/SQL: numeric or value error
      ORA-06512: at line 11
      ORA-25228: timeout or end-of-fetch during message dequeue from MDM.ALL_NSI

           at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:462)
           at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:397)
           at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389)
           at oracle.jdbc.driver.T4Caqdq.processError(T4Caqdq.java:497)
           at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:481)
           at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:205)
           at oracle.jdbc.driver.T4Caqdq.doOAQDQ(T4Caqdq.java:183)
           at oracle.jdbc.driver.T4CConnection.doDequeue(T4CConnection.java:4704)
           at oracle.jdbc.driver.PhysicalConnection.dequeue(PhysicalConnection.java:17863)
           at oracle.jdbc.driver.PhysicalConnection.dequeue(PhysicalConnection.java:17949)
           at oracle.jdbc.OracleConnectionWrapper.dequeue(OracleConnectionWrapper.java:1624)
           at weblogic.jdbc.wrapper.XAConnection_oracle_jdbc_driver_LogicalConnection.dequeue(Unknown Source)
           at weblogic.jdbc.wrapper.JTAConnection_weblogic_jdbc_wrapper_XAConnection_oracle_jdbc_driver_LogicalConnection.dequeue(Unknown Source)
           at oracle.jms.AQjmsConsumer.jdbcConnectionDequeueCheck25242(AQjmsConsumer.java:1713)
           at oracle.jms.AQjmsConsumer.jdbcDequeue(AQjmsConsumer.java:1295)
           ... 13 more
      However, when I put message to AQ topic, the OSB proxy receives and processes it. But SQLException occurs every five seconds and pollute logs.
      Request help to resolve this.

      Thanks in advance.

      Regards
      Alexander.