Bug 263792 - ORACLE 11.1.0.7 OCI: Oracle specific test - JMSDirectConnectTest failed
Summary: ORACLE 11.1.0.7 OCI: Oracle specific test - JMSDirectConnectTest failed
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---   Edit
Assignee: Nobody - feel free to take it CLA
QA Contact:
URL:
Whiteboard: oracle
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-05 10:41 EST by Edwin Tang CLA
Modified: 2022-06-09 10:34 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Edwin Tang CLA 2009-02-05 10:41:28 EST 
This is not a regression. It is the first time for the test to be run with Oracle OCI driver.

Oracle specific test - JMSDirectConnectTest failed with Oracle 11.1.0.7 OCI driver. It passed with thin driver.

Stack Trace:
============
Exception Description: Fatal error occurred. Internal Exception: java.lang.NoSuchMethodError: setWriteLobLater

Local Exception Stack:
Exception [EclipseLink-0] (Eclipse Persistence Services - 1.1.0.20090203-SNAPSHOT): org.eclipse.persistence.testing.framework.TestErrorException
Exception Description: Fatal error occurred.
Internal Exception: java.lang.NoSuchMethodError: setWriteLobLater
at org.eclipse.persistence.testing.framework.TestCase.execute(TestCase.java:164)
at org.eclipse.persistence.testing.framework.TestCase.runBare(TestCase.java:263)
at org.eclipse.persistence.testing.framework.TestExecutor.execute(TestExecutor.java:247)
at org.eclipse.persistence.testing.framework.TestSuite.execute(TestSuite.java:75)
at org.eclipse.persistence.testing.framework.TestCollection.run(TestCollection.java:313)
at org.eclipse.persistence.testing.framework.TestExecutor.execute(TestExecutor.java:247)
at org.eclipse.persistence.testing.framework.TestModel.execute(TestModel.java:208)
at org.eclipse.persistence.testing.framework.TestCollection.run(TestCollection.java:313)
at org.eclipse.persistence.testing.framework.TestExecutor.execute(TestExecutor.java:247)
at org.eclipse.persistence.testing.framework.TestModel.execute(TestModel.java:208)
at org.eclipse.persistence.testing.framework.TestCollection.run(TestCollection.java:313)
Caused by: java.lang.NoSuchMethodError: setWriteLobLater
at oracle.jms.AQjmsSession.ociinit(Native Method)
at oracle.jms.AQjmsSession.getOCIHandles(AQjmsSession.java:6147)
at oracle.jms.AQjmsSession.(AQjmsSession.java:395)
at oracle.jms.AQjmsConnection.createTopicSession(AQjmsConnection.java:739)
at org.eclipse.persistence.testing.tests.eis.aq.JMSDirectConnectTest.connectTopic(JMSDirectConnectTest.java:40)
at org.eclipse.persistence.testing.tests.eis.aq.JMSDirectConnectTest.test(JMSDirectConnectTest.java:29)
at org.eclipse.persistence.testing.framework.TestCase.executeTest(TestCase.java:543)
at org.eclipse.persistence.testing.framework.TestCase.execute(TestCase.java:154)
Comment 1 Tom Ware CLA 2009-02-11 13:19:16 EST 
Targetting for 1.1x which will make this bug a candidate for the first patch after 1.1.
Comment 2 Peter Krogh CLA 2009-11-30 11:38:09 EST 
Changing the priority of the bugs that have been recently triaged to future.  Targetting them to P2 will differentiate them from the P3s that have been triaged into future earlier.
Comment 3 Eclipse Webmaster CLA 2022-06-09 10:34:49 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink