Oracle.jms.AQjmsException: JMS-225: Invalid JDBC driver

I am deploying an MDB to an SOA Suite iAS 10g OC4J container version 10.1.3.1 and I am receiving this error when trying to start the bean, even though the connection pool has been setup and tested to connect using OCI.
Error in MessageDrivenBean 'MessageDrivenEJBBean': oracle.jms.AQjmsException: JMS-225: Invalid JDBC driver - OCI driver must be used for
this operation
oracle.jms.AQjmsException: JMS-225: Invalid JDBC driver - OCI driver must be used for this operation
at oracle.jms.AQjmsError.throwEx(AQjmsError.java:285)
at oracle.jms.AQjmsConsumer.dequeue(AQjmsConsumer.java:1186)
at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:922)
at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:835)
at oracle.jms.AQjmsConsumer.receive(AQjmsConsumer.java:776)
at oracle.j2ee.ra.jms.generic.CommonConsumerWrapper.receive(CommonConsumerWrapper.java:203)
at com.evermind.server.ejb.MessageDrivenConsumer.receiveMessage(MessageDrivenConsumer.java:424)
at com.evermind.server.ejb.MessageDrivenConsumer.processMessages(MessageDrivenConsumer.java:213)
at com.evermind.server.ejb.MessageDrivenConsumer.run(MessageDrivenConsumer.java:169)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
Anyone have any ideas?
Thanks

Hello,
You need to use the OCI driver as the error indicates.
The thin driver does not have support for the ANYDATA type in 10.2 only the OCI driver does. in 11.1 onwards the thin driver supports the ANYDATA type. So an option may be to use the jar files from an 11g install.
Thanks
Peter

Similar Messages

Oracle 9.2.0.1.0 JDBC driver for Java 1.5 & Java 1.6

Hi,
Is there any JDBC driver that I can download for running Java application of version 1.5 or 1.6 on Oracle 9.2.0.1.0 ?
As I see in the official link of Oracle: http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html
The JDBC drivers for this database are only for Java 1.4 and older.
Can any one please help?
Thanks
Edited by: user11088169 on 05:21 09/06/2009

The subject is about Oracle 9.2.0.1 JDBC drivers. "Oracle 9.2.0.1.0 JDBC driver for Java 1.5 & Java 1.6"
Oracle database 9.2.0 drivers may only be used with JDK 1.4 or earlier.
But, Oracle database 9.2.0 may be used with Oracle database 11 drivers with JDK 5.0, 6.0.

Upgrade Oracle iAS 9.0.4.1 JDBC Driver to 9.2.0.8

Hi,
I'm using Oracle Application Server 10g R1 (9.0.4.1) for a JDBC application that connects to an Oracle 9.2.0.7 Database.
Due to some NLS problems with JDBC connections which are out of the scope of this posting, I need to upgrade the JDBC Driver of iAS 9.0.4.1 to the latest JDBC Driver, closest to my database full version. Since there is no 9.2.0.7 JDBC Driver set, I downloaded the 9.2.0.8 JDBC Driver files for Java JRE 1.4 which is the jdk/jre of the iAS 9.0.4.1.
This set though, contains files ojdbc14.jar, ojdbc14_g.jar and ocrs12.jar and NOT the JDBC Driver files that are found in the ORACLE_HOME\jdbc\lib path of the iAS 9.0.4.1., and of course, replacing the existing with the new ones, does not work (does not update the JDBC Driver on the server).
How can this upgrade be archived?
Is anyone aware of the documented JDBC upgrade procedure for Oracle iAS 9.0.4.1, to driver version 9.2.0.8?
Why there is no classes12.zip or classes12.jar distribution in the JDBC driver 9.2.0.8 set?
Thank you

JspServlet: unable to dispatch to requested page: Exception:java.lang.UnsupportedClassVersionError: wfrecruit/WFRequisition (Unsupported major.minor version 49.0)
Application is compiled with a JDK version and run with another version of JDK.
Compile and run application with same version of JDK.

Oracle.jms.AQjmsException when inserting large MessageMap message via JMS

Is there a limit on the number of items/size of message that can be placed on the AQ using the MessageMap message format?
Ive attempted to place 100 elements, each a small string of approximately 20 characters, into the AQ but I get the following error.
---> nested oracle.jms.AQjmsException: JMS-204: An error occurred in the AQ JNI layer
If I reduce the number of elements to about 70 the message is successfully queued.

As long as the byte array obtained by serializing the JMSMapMessage
java object instance fits in a BLOB (max size 4 Gig) you should be able to
enqueue your message (providing the OS and/or the JVM can handle it).
Smaller map messages are stored inline in the table itself. Larger messages
are stored in a BLOB. It is likely that you do not have permissions to
write to the BLOB field of the OJMS MapMessage ADT.
To figure out the exact SQL exception turn tracing on by putting the following
lines of code in your OJMS client and recompiling.
AQjmsOracleDebug.setDebug(true);
AQjmsOracleDebug.setTraceLevel(5);
This will give you the exact SQL exception that is thrown.
-Vivek

Oracle jdbc driver problems in netbeans 5.5

need help again....i'm experience a problem. the problems are :
i connect from netbeans 5.5 to oracle database express client 10g using jdbc driver ojdbc14.jar. the connection succeded (all the tables appears and i even can view the data). but when i trying to bind data to a drop down list component (with right click to the dropdown list component and then bind data), the dataprovider of that table appear in red color and there's no field appears in that. i'm so confused? i already add the ojdbc14.jar driver to the following path :
1. i create a new class library in netbeans with consist of that driver,
then added to my project (right click in my project then add library).
2. then i added the ojdbc14.jar driver to my tomcats lib at "C:\Program
Files\netbeans-5.5\enterprise3\apache-tomcat-5.5.17\common\lib".
Is there any additional settings in using oracle jdbc driver? Does anyone knows? thanks a lot for the answers...
Message was edited by:
darma_sadha

Hi!
I'm using NetBeans 6.5 and I'm having some troubles to connect.
The steps I've made:
- Create the connection pool in Glassfish, nothing special, just standard parameters (Based on javax.sql.DataSource and including URL, Username and Password).
- Create the JDBC resource associated with that connection pool,let's say jdbc/test.
Now in NetBeans I register the driver:
- New driver -> Find the ojdbc14.jar and from the options that I can choose it shows: oracle.jdbc.OracleDriver and oracle.jdbc.driver.OracleDriver.
If i choose without +.driver+ I got the thin drivers (the ones i want) and if i chosse the one with the other one I got the OCI drivers. So I choose the first option oracle.jdbc.OracleDriver
- Then I go to my project and click New -> Entity Classes from Database and from Datasource I select jdbc/test and it shows the following error message:
Unable to find the driver oracle.jdbc.driver.OracleDriver. Please register this driver in the Databases.
I can fix it if while registering the ojdbc14.jar I select the second option (*oracle.jdbc.driver.OracleDriver*) but with this option I need to specity the connection to use OCI instead of the desired thin driver.
I hope you'll understand and help me somehow
Edited by: KILE on Oct 10, 2008 2:26 AM

Doubts: Oracle 9i Client -J2SDK1.4 - JDBC Driver

Hi eXperts,
I have installed Oracle 9i(9.2.0.1) client in my machine. Along with the Oracle 9i client, there are two JREs (versions 1.3.1 and 1.1.8) also installed. After installing the oracle 9i client, the SYSTEM�s environment variable �PATH� is updated with the �bin� directory of both JRE (C:\Program Files\Oracle\jre\1.3.1\bin;
C:\Program Files\Oracle\jre\1.1.8\bin;) and �bin� director of Oracle home (C:\oracle\ora92\bin;)
Already I have installed J2SDK 1.4.1_02. I have set the USER�s environment variable �PATH� to �C:\j2sdk1.4.1_02\bin;�
My problem is:
1.     Before installing oracle 9i client, I was working with J2SDK v1.4.1. After installing, I could not able to invoke the J2SDK 1.4.1; instead I�m invoking JRE 1.3.1. I want work with latest version of J2SDK (that is J2SDK1.4.1, the one I installed) at the same time without disturbing the Oracle 9i clients JREs. Because, I want use the Oracle client for JDBC connection to the database.
2.     I have installed J2SDK1.4.1, I want connect with oracle 9i database from JAVA using JDBC driver. That means JDBC driver supporting J2SDK1.4. (With ojdbc14.jar, not with classes12.jar,). But, currently I�m using �classes12.jar� to connect with database, because my program invokes JRE1.3, not J2SDK1.4.
3.     And one more doubt is that why Oracle 9i client comes with two JREs. JRE 1.3.1 is having backward compatibility; it should support JRE 1.1.8 features too. Why two JREs?
Hope that any of you can solve my doubts.
Thank & Regards,
Vijay

Hi Viravan,
Yes of course, JRE 1.1.8 doesn�t have the forward compatibility with JRE 1.3. I would like to hear the words from you to clear and assure myself with the doubt that what is the purpose of inclusion of JRE1.1.8 along with the oracle 9i client?. I�m assuming that this is because of to use JRE 1.1.8 compatible JDBC drivers. Is it right?
Because,
For JDK1.1 � classes111.zip
For JDK1.2 and JDK1.3 � classes12.zip and
For JDK1.4 � ojdbc14.jar
If that is the case why they haven�t included the JRE1.4 along with Oracle 9i client, because they were provided the ojdbc14.jar.
If any OTHER REASON is there, please let me know. I�m suspecting that there may be some other reasons for the inclusion of JRE1.1.8. Looking forward your reply�
Thanks for your support.
Vijay

DatabaseMetaData.getTypeInfo ()=NULL when use JDBC Driver 9.2.0.5

Why DatabaseMetaData.getTypeInfo () is NULL when use JDBC Driver 9.2.0.5 to connect Oracle 9.0.1.1.1 database?
In the following links
http://www.oracle.com/technology/tech/java/sqlj_jdbc/htdocs/jdbc_faq.htm#02_02
the segment "Which JDBC drivers support which versions of Oracle Database?" tells us that JDBC Driver 9.2.0.5 can support Oracle 9.0.1.1.1 database.
thanks!

ERROR --- java.sql.SQLException: ORA-01722: 无效数字

JDBC driver install for SQLSERVER 2000

I am porting my application from Oracle DB to SQLServer2000.
Which JDBC driver and where can I get the drivers and procedures to
install the driver?
Any advice for the porting procedures will be appreciated.
Thanks in advance for any comments.
Judy

This comes up over and over and over and over; use the "search Forums" feature...

Buying a new JDBC driver

Hi There,
I am a student and currently working on a ASP ->MS ACCESS application. I have converted that application to JSP->MS ACCESS.
Now I am planning to migrate to JSP->Oracle and want to buy a JDBC driver for the same. Can anybody guide me to buying a good/cheap driver?
I have gone through the following list but I want somebody experienced to advice me on this topic.
http://industry.java.sun.com/products/jdbc/drivers
Any help will be useful.
Thanks
Mahesh.

Thanks for the reply!!
Another query about developing applications:
For the JSP->MS ACCESS application that I developed, I used JDBC:ODBC bridge that comes with SDK and Apache Tomcat as the JSP container.
Compared to the implementation in ASP, the JSP version was very very slow (crashed after 30 min of extensive interaction with the database) and after a long thought I attributed this problem to the JDBC:ODBC bridge. This led me to my decision of buying / using a new JDBC driver.
Do you think I am in the right direction? Also is Oracle JDBC driver used commercially?
Regards.

[BEA][SQLServer JDBC Driver]Error

hi
i am veeresh.s, in 1 of our user this below error has came,i am a fresher, i don't know how to resolve it, please any body help me in resolving this error
user gets the following error message when the user try to create a connection pool to connect user weblogic server to oracle server.
Error:
[BEA][SQLServer JDBC Driver]Error establishing socket to host and port: dt2888-swaminat:1433. Reason: Connection refused: connect
The Network Adapter could not establish the connection
user is unable to telnet to that machine. user suspect that it to be some driver issue.
So what may be the problem,
please look into the problem and Kindly help me in resolving this issue.

This appears to be a duplicate thread. I posted a reply in the other forum
Re: [BEA][SQLServer JDBC Driver]Error
Justin

Oracle.jms.AQjmsException: invalid arguments in call

Hi
Has anyone seen this error before?
Environment Configuration:
APP SERVER 9.0.4 (OUT 0F BOX CONFIG)
JDK 1.4
RED HAT ENTERPRISE SERVER 3.0
COMPAC DL380
ON VM SOFTWARE
DB 9.2.0.4
HP-UX 11i
SUPERDOME
Error logs:
[18-06-04 10:27:20] [AJPRequestHandler-ApplicationServerThread-137] - [bcc.sde.common.jms.pool.QueueConnectionPool]
[getQueueConnection] :Using pooled queue connection for factory:
java:comp/resource/SDEJMS/QueueConnectionFactories/SDEQUEUETAB
[18-06-04 10:27:20] [AJPRequestHandler-ApplicationServerThread-137] - [bcc.sde.common.jms.pool.QueueSessionPool]
[createQueueSession] :Failed to create queue session: oracle.jms.AQjmsException: invalid arguments in call
[18-06-04 10:27:20] [AJPRequestHandler-ApplicationServerThread-137] - [bcc.sde.common.jms.BytesMessageWriter]
[writeBytesMessage] :Failed to write message onto queue: java:comp/resource/SDEJMS/Queues/SDEDEV_LOGQUEUE using queue
factory: java:comp/resource/SDEJMS/QueueConnectionFactories/SDEQUEUETAB - bcc.sde.common.jms.pool.JMSPoolException:
QueueSessionPool.createQueueSession() failed to create queue session - oracle.jms.AQjmsException: invalid arguments in call
[18-06-04 10:27:20] [AJPRequestHandler-ApplicationServerThread-137] - [bcc.sde.sil.common.log.silInteractionLogger] [log]
:silInteractionLogger.log() Exception writing ServiceExecutionRecord to JMS queue: bcc.sde.common.exception.SDEException:
Failed to write message onto queue: java:comp/resource/SDEJMS/Queues/SDEDEV_LOGQUEUE using queue factory:
java:comp/resource/SDEJMS/QueueConnectionFactories/SDEQUEUETAB - bcc.sde.common.jms.pool.JMSPoolException:
QueueSessionPool.createQueueSession() failed to create queue session - oracle.jms.AQjmsException: invalid arguments in
call: QueueSessionPool.createQueueSession() failed to create queue session - oracle.jms.AQjmsException: invalid arguments
in call;
---> nested: bcc.sde.common.jms.pool.JMSPoolException: QueueSessionPool.createQueueSession() failed to create queue
session - oracle.jms.AQjmsException: invalid arguments in call
[18-06-04 10:27:20] [AJPRequestHandler-ApplicationServerThread-137] - [bcc.sde.sil.bids.api.sql.BidsSQLInterface]
[logInteractionRecord] :Failed to log interaction record: bcc.sde.common.exception.SDEException: silInteractionLogger.log()
Exception writing ServiceExecutionRecord to JMS queue: bcc.sde.common.exception.SDEException: Failed to write message onto
queue: java:comp/resource/SDEJMS/Queues/SDEDEV_LOGQUEUE using queue factory:
java:comp/resource/SDEJMS/QueueConnectionFactories/SDEQUEUETAB - bcc.sde.common.jms.pool.JMSPoolException:
QueueSessionPool.createQueueSession() failed to create queue session - oracle.jms.AQjmsException: invalid arguments in
call: QueueSessionPool.createQueueSession() failed to create queue session - oracle.jms.AQjmsException: invalid arguments
in call;
---> nested: bcc.sde.common.jms.pool.JMSPoolException: QueueSessionPool.createQueueSession() failed to create queue
session - oracle.jms.AQjmsException: invalid arguments in call
Database error with same error message:
ORA-17433 - invalid arguments in call
http://www.doc.gold.ac.uk/oracle/doc/java.817/a83724/ermesap3.htm
Code causing problem:
queueConnection = queueConnectionPool.getQueueConnection(queueConnectionFactoryName, runningExternal);
queueSession = queueConnection.createQueueSession(TRANSACTIONAL, AUTO_ACK_MODE);

I am facing the same problem. Have you figured out what the cause was? Thanks,

Oracle.jms.AQjmsException: Error creating the db_connection( OSB PS2.)

hi All,
I am beginner in OSB 11g. Please excuse me if I am asking any dumb question.
I am trying to post messages to Oracle AQ by configuring JMS Destination in OSB Alert destination
I have configured AQ JMS in weblogic 10.3.3 ( OSB PS2) following the blog (http://jianmingli.com/wp/?p=2950)
When i invoked my proxy OSB proxy service i am getting following exception. Can you please help if i am missing any kind of setup while configuring the JMS Module.
Caused By: oracle.jms.AQjmsException: Error creating the db_connection
     at oracle.jms.AQjmsDBConnMgr.getConnection(AQjmsDBConnMgr.java:625)
     at oracle.jms.AQjmsDBConnMgr.<init>(AQjmsDBConnMgr.java:399)
     at oracle.jms.AQjmsXAConnection.<init>(AQjmsXAConnection.java:112)
     at oracle.jms.AQjmsXAQueueConnectionFactory.createAllXAConnection(AQjmsXAQueueConnectionFactory.java:320)
     at oracle.jms.AQjmsXAQueueConnectionFactory.createXAQueueConnection(AQjmsXAQueueConnectionFactory.java:198)
     at weblogic.deployment.jms.JMSConnectionHelper.openConnection(JMSConnectionHelper.java:282)
     at weblogic.deployment.jms.JMSConnectionHelper.<init>(JMSConnectionHelper.java:144)
     at weblogic.deployment.jms.JMSSessionPool.getConnectionHelper(JMSSessionPool.java:517)
     at weblogic.deployment.jms.PooledConnectionFactory.createConnectionInternal(PooledConnectionFactory.java:355)
     at weblogic.deployment.jms.PooledConnectionFactory.createQueueConnection(PooledConnectionFactory.java:188)
     at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.getSession(JmsOutboundMessageContext.java:399)
     at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.newMessage(JmsOutboundMessageContext.java:621)
     at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.setRequestMetaData(JmsOutboundMessageContext.java:229)
     at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.access$100(JmsOutboundMessageContext.java:72)
     at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext$SendAction.run(JmsOutboundMessageContext.java:788)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at weblogic.security.Security.runAs(Security.java:61)
     at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.send(JmsOutboundMessageContext.java:551)
     at com.bea.wli.sb.transports.jms.JmsTransportProvider.sendMessageAsync(JmsTransportProvider.java:680)
     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:597)
     at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
     at $Proxy111.sendMessageAsync(Unknown Source)
     at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageWithoutService(TransportManagerImpl.java:489)
     at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:417)
     at com.bea.wli.sb.init.FrameworkStarter$TransportServiceImpl.sendMessageAsync(FrameworkStarter.java:391)
     at com.bea.alsb.alert.action.jms.JmsActionProvider.executeAction(JmsActionProvider.java:345)
     at com.bea.alsb.alert.AlertDestinationHandlerImpl.sendAlertToDestination(AlertDestinationHandlerImpl.java:105)
     at com.bea.alsb.alert.pipeline.PipelineAlertManager.processAlert(PipelineAlertManager.java:59)
     at stages.logging.runtime.AlertRuntimeStep.processMessage(AlertRuntimeStep.java:125)
     at com.bea.wli.sb.pipeline.debug.DebuggerRuntimeStep.processMessage(DebuggerRuntimeStep.java:74)
     at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
     at com.bea.wli.sb.stages.impl.SequenceRuntimeStep.processMessage(SequenceRuntimeStep.java:33)
     at stages.routing.runtime.RouteRuntimeStep.processMessage(RouteRuntimeStep.java:102)
     at com.bea.wli.sb.pipeline.debug.DebuggerRuntimeStep.processMessage(DebuggerRuntimeStep.java:74)
     at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
     at com.bea.wli.sb.pipeline.RouteNode.doRequest(RouteNode.java:106)
     at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:67)
     at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:922)
     at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:214)
     at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:99)
     at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:593)
     at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:591)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
     at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:590)
     at com.bea.wli.sb.test.service.ServiceMessageSender.send0(ServiceMessageSender.java:329)
     at com.bea.wli.sb.test.service.ServiceMessageSender.access$000(ServiceMessageSender.java:76)
     at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:134)
     at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:132)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
     at com.bea.wli.sb.test.service.ServiceMessageSender.send(ServiceMessageSender.java:137)
     at com.bea.wli.sb.test.service.ServiceProcessor.invoke(ServiceProcessor.java:454)
     at com.bea.wli.sb.test.TestServiceImpl.invoke(TestServiceImpl.java:172)
     at com.bea.wli.sb.test.client.ejb.TestServiceEJBBean.invoke(TestServiceEJBBean.java:167)
     at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl.invoke(TestService_sqr59p_EOImpl.java:353)
     at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
     at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
     at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: java.lang.ClassCastException: weblogic.jdbc.rmi.SerialConnection_weblogic_jdbc_rmi_internal_ConnectionImpl_weblogic_jdbc_wrapper_JTAConnection_weblogic_jdbc_wrapper_XAConnection_oracle_jdbc_driver_LogicalConnection_1033_WLStub cannot be cast to oracle.jdbc.internal.OracleConnection
     at oracle.jms.AQjmsGeneralDBConnection.getProviderKey(AQjmsGeneralDBConnection.java:96)
     at oracle.jms.AQjmsGeneralDBConnection.<init>(AQjmsGeneralDBConnection.java:65)
     at oracle.jms.AQjmsDBConnMgr.getConnection(AQjmsDBConnMgr.java:566)
     at oracle.jms.AQjmsDBConnMgr.<init>(AQjmsDBConnMgr.java:399)
     at oracle.jms.AQjmsXAConnection.<init>(AQjmsXAConnection.java:112)
     at oracle.jms.AQjmsXAQueueConnectionFactory.createAllXAConnection(AQjmsXAQueueConnectionFactory.java:320)
     at oracle.jms.AQjmsXAQueueConnectionFactory.createXAQueueConnection(AQjmsXAQueueConnectionFactory.java:198)
     at weblogic.deployment.jms.JMSConnectionHelper.openConnection(JMSConnectionHelper.java:282)
     at weblogic.deployment.jms.JMSConnectionHelper.<init>(JMSConnectionHelper.java:144)
     at weblogic.deployment.jms.JMSSessionPool.getConnectionHelper(JMSSessionPool.java:517)
     at weblogic.deployment.jms.PooledConnectionFactory.createConnectionInternal(PooledConnectionFactory.java:355)
     at weblogic.deployment.jms.PooledConnectionFactory.createQueueConnection(PooledConnectionFactory.java:188)

hi All,
Here is the actual exception while posting message into AQ ( AQ JMS) from OSB.
Caused By: java.lang.ClassCastException: weblogic.jdbc.rmi.SerialConnection_weblogic_jdbc_rmi_internal_ConnectionImpl_weblogic_jdbc_wrapper_JTAConnection_weblogic_jdbc_wrapper_XAConnection_oracle_jdbc_driver_LogicalConnection_1033_WLStub cannot be cast to oracle.jdbc.internal.OracleConnection
at oracle.jms.AQjmsGeneralDBConnection.getProviderKey(AQjmsGeneralDBConnection.java:96)
at oracle.jms.AQjmsGeneralDBConnection.<init>(AQjmsGeneralDBConnection.java:65)
Not sure what is missing in my AQ JMS configuration. Please help.
Regards,
Nagi

Oracle 8.1.7.4 + JDBC Driver 10.2.0.3.0=invalid or unknown NLS parameter...

I'm having an issue trying to update the jdbc driver from 10.1.0.2.0 to 10.2.0.3.0 to access an Oracle 8.1.7.4 instance. Using this code I'm getting the following exception, any ideas how to fix it?
Thanks,
Johann
Connection c = null;
try {
     Driver dr = new oracle.jdbc.OracleDriver();
     DriverManager.registerDriver(dr);
     Properties props = new Properties();
     props.put("user", "congiromsr");
     props.put("password", "the password");
     String url = "jdbc:oracle:thin:@cholguaco:1533:lobo";
     c = dr.connect(url, props);
     System.out.println("The driver is "
               + c.getMetaData().getDriverVersion());
     System.out.println("The DBMS is "
               + c.getMetaData().getDatabaseProductVersion());
} catch (Exception e) {
     e.printStackTrace();
} finally {
     try {
          c.close();
     } catch (Exception ignore) {
java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1
ORA-12705: invalid or unknown NLS parameter value specified
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:283)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:278)
     at oracle.jdbc.driver.T4CTTIoauthenticate.receiveOauth(T4CTTIoauthenticate.java:791)
     at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:362)
     at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:439)
     at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:165)
     at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)
     at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:801)
     at TestClass.main(TestClass.java:14)

JDBC drivers set NLS parameters based on your locale settings. There are three based parameters: language, territory and character set. Maybe in your case JDBC driver 10.2.0.3.0 sets one of them with value that is not supported in Oracle Database 8.1.7.4. Character set is the first candidate for this. JDBC drivers use only Unicode character sets - there are a few new of them in Oracle Database 10g. 8 and 9 versions of JDBC drivers use UTF8 which is Unicode version 3.0 but in 10g is added Al32UTF8 which is Unicode version 4.0.

Invalid Column Name Error : JDBC Driver 9.2.* accessing Oracle 7.3.*

We are migrating a web app from JDK 1.2 environment to a JDK 1.5 server enviroment. Previously the web app used the classes12.zip package, now we are using ojdbc14.jar for the new server environment.
Now this particular app uses Oracle7 Server Release 7.3.3.6.0. to retrieve data. I would run a query and get the result set explicitly using the column name.
sql_query = " SELECT DISTINCT(INSIDE_SALES_TEAM_NAME) AS D_INSIDE_SALES_TEAM_NAME FROM AGED_INVENTORY" ;
rset.getString("D_INSIDE_SALES_TEAM_NAME");
However, after migration to ojdc14.jar (using Oracle JDBC driver 9.2.0.8.0) I can't retrieve the resultset in the above-mentioned fashion. I will always get
java.sql.SQLException: Invalid column name
If I use the following, then I do not get any error in retrieving data from the resultset.
rset.getString(1);
Any cause for this scenario?
Thanks,
TA

Yes of course. I just the posted code snippet. This code used to work in old web server environment. Now we have to modify the resultset line to make it work when using ojdc14.jar.

Microsoft SQL Server JDBC driver and WLS JMS problem?

          Greetings,
          I'm using the Microsoft SQL Server JDBC driver with WLS with JMS
          persisted to SQL Server, during WLS startup the JMS attempts to
          read the JMSStore and JMSState tables in the db, if they are
          already present (say, from a previous run) the driver kicks out:
          java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet can
          not re-read row data for column 1.
          If the tables are not present, then WLS creates them and
          everything proceeds fine. Now, its not a good thing to attempt
          to reread row data for a ResultSet, especially for portability. Why is WLS JMS
          doing this? is there some config I can use to adjust JMS startup behavior for
          persisted JMS stores?
          Jay Houghton
          Centiv
          [email protected]
          long exception trace follows:
          <Oct 1, 2002 8:29:11 AM EDT> <Info> <JMS> <User connection factory "BroadcastTopicFactory"
          is started.>
          <Oct 1, 2002 8:29:18 AM EDT> <Info> <JMS> <JMSServer "EnergizerJMSServer", Opening
          JDBC store tables "JMSStore
          " and "JMSState" using connection pool "JMSConnectionPool".>
          <Oct 1, 2002 8:29:20 AM EDT> <Alert> <JMS> <JMSServer "EnergizerJMSServer", store
          failed to open, java.io.IOEx
          ception: JMS JDBC store, connection pool = <JMSConnectionPool>, prefix = <null>:
          recover
          java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet can
          not re-read row data for colum
          n 1.
          at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
          at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
          at weblogic.jdbc.pool.ResultSet.getLong(ResultSet.java:304)
          at weblogic.jms.store.JDBCIOStream.doRecover(JDBCIOStream.java:618)
          at weblogic.jms.store.JDBCIOStream.recover(JDBCIOStream.java:728)
          at weblogic.jms.store.JMSStore.recover(JMSStore.java:112)
          at weblogic.jms.backend.BEStore.open(BEStore.java:179)
          at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:330)
          at weblogic.jms.JMSService.createBackEnd(JMSService.java:923)
          at weblogic.jms.JMSService.addJMSServer(JMSService.java:1277)
          at weblogic.jms.JMSService.addDeployment(JMSService.java:1174)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
          at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:23
          3)
          at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
          at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
          at $Proxy40.updateDeployments(Unknown Source)
          at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub
          .java:2734)
          at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:362
          at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:154)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
          at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
          at $Proxy57.start(Unknown Source)
          at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean
          _CachingStub.java:480)
          at weblogic.management.Admin.startApplicationManager(Admin.java:1151)
          at weblogic.management.Admin.finish(Admin.java:571)
          at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:508)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
          at weblogic.Server.main(Server.java:35)


          Tom,
          thanks for the info, I'll bring this to support.
          I did try the weblogic jDriver for SQL Server and it works fine, so i think it
          must be the way JMS is interacting with the MS driver.
          here are my components:
          WLS 6.1sp1
          Microsoft® SQL Server™ 2000 Driver for JDBC™ is a (Type 4 JDBC) which provides
          partial JDBC 2 support (no blobs, clobs, etc)
          MS SQL Server 2000 (sp2?)
          thanks!
          Jay Houghton
          [email protected]
          Tom Barnes <[email protected]> wrote:
          >Hi Jay,
          >
          >This is not a known issue at BEA as far as I know, perhaps it is the
          >result
          >of a new driver/database combination. Try using a different driver,
          >or a different
          >version of the current driver. Meanwhile, use a file store (just as
          >reliable but faster) and log a case with customer support, including
          >information on your version, service-pack, and what driver you are using.
          >
          >Tom, BEA
          >
          >Jay Houghton wrote:
          >
          >> Greetings,
          >>
          >> I'm using the Microsoft SQL Server JDBC driver with WLS with JMS
          >> persisted to SQL Server, during WLS startup the JMS attempts to
          >> read the JMSStore and JMSState tables in the db, if they are
          >> already present (say, from a previous run) the driver kicks out:
          >>
          >> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet
          >can
          >> not re-read row data for column 1.
          >>
          >> If the tables are not present, then WLS creates them and
          >> everything proceeds fine. Now, its not a good thing to attempt
          >> to reread row data for a ResultSet, especially for portability. Why
          >is WLS JMS
          >> doing this? is there some config I can use to adjust JMS startup behavior
          >for
          >> persisted JMS stores?
          >>
          >> Jay Houghton
          >> Centiv
          >> [email protected]
          >>
          >> long exception trace follows:
          >>
          >> <Oct 1, 2002 8:29:11 AM EDT> <Info> <JMS> <User connection factory
          >"BroadcastTopicFactory"
          >> is started.>
          >> <Oct 1, 2002 8:29:18 AM EDT> <Info> <JMS> <JMSServer "EnergizerJMSServer",
          >Opening
          >> JDBC store tables "JMSStore
          >> " and "JMSState" using connection pool "JMSConnectionPool".>
          >> <Oct 1, 2002 8:29:20 AM EDT> <Alert> <JMS> <JMSServer "EnergizerJMSServer",
          >store
          >> failed to open, java.io.IOEx
          >> ception: JMS JDBC store, connection pool = <JMSConnectionPool>, prefix
          >= <null>:
          >> recover
          >> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet
          >can
          >> not re-read row data for colum
          >> n 1.
          >> at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
          >> at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
          >> at weblogic.jdbc.pool.ResultSet.getLong(ResultSet.java:304)
          >> at weblogic.jms.store.JDBCIOStream.doRecover(JDBCIOStream.java:618)
          >> at weblogic.jms.store.JDBCIOStream.recover(JDBCIOStream.java:728)
          >> at weblogic.jms.store.JMSStore.recover(JMSStore.java:112)
          >> at weblogic.jms.backend.BEStore.open(BEStore.java:179)
          >> at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:330)
          >> at weblogic.jms.JMSService.createBackEnd(JMSService.java:923)
          >> at weblogic.jms.JMSService.addJMSServer(JMSService.java:1277)
          >> at weblogic.jms.JMSService.addDeployment(JMSService.java:1174)
          >> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
          >> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
          >> at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:23
          >> 3)
          >> at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
          >> at java.lang.reflect.Method.invoke(Native Method)
          >> at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
          >> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
          >> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
          >> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          >> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          >> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
          >> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
          >> at $Proxy40.updateDeployments(Unknown Source)
          >> at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub
          >> java:2734)
          >> at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:362
          >> )
          >> at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:154)
          >> at java.lang.reflect.Method.invoke(Native Method)
          >> at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
          >> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
          >> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
          >> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          >> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          >> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
          >> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
          >> at $Proxy57.start(Unknown Source)
          >> at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean
          >> _CachingStub.java:480)
          >> at weblogic.management.Admin.startApplicationManager(Admin.java:1151)
          >> at weblogic.management.Admin.finish(Admin.java:571)
          >> at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:508)
          >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
          >> at weblogic.Server.main(Server.java:35)
          >

Oracle.jms.AQjmsException: JMS-225: Invalid JDBC driver

Similar Messages

Maybe you are looking for