Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 472321, 1 year ago
JMS-225: Invalid JDBC driver - OCI driver must be used for this operation
via Oracle Community by 198189, 1 year ago
via Oracle Community by 680889, 1 year ago
JMS-120: Dequeue failed
via Oracle Community by user121044, 1 year ago
JMS-120: Dequeue failed
via Oracle Community by 584953, 1 year ago
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)