JMS Error when using OJMS/AQ in OC4J 9.0.2 but not in OC4J 9.0.3

Question

Hi,
I tried to use OJMS/AQ as the JMS provider in OC4J 9.0.2 and OC4J 9.0.3. Resource providers in both the containers point to the same Oracle database (9.0.1.3.0) using the same user account.
JMS works fine with OC4J 9.0.3 but not with OC4J 9.0.2.
During the start-up of 9.0.2 container, it successfully connects with Oracle AQ, finds queues in AQ but finally comes back with an error message saying "JMS Error: invalid arguments in call". It does not provide any more information about the error.
Does any one have got any clue why this error message occur during startup? Any assistance is appreciated.
The following is the definition of Resource provider in config/application.xml:
<resource-provider class="oracle.jms.OjmsContext" name="ispojms">
<description> OJMS/AQ </description>
<property name="url" value="jdbc:oracle:thin:@Hduna1.corporatetesth.nsw.edu.au:1527:ISP"></property>
<property name="username" value="ISPDBA"></property>
<property name="password" value="******"></property>
</resource-provider>
The user ISPDBA is given all privileges for AQ in Oracle DB.
The Message Driven Bean's definition in deployment descriptors:
Ejb-jar.xml:
<ejb-jar>
<enterprise-beans>
<message-Long postings are being truncated to ~1 kB at this time.

Answer 1

Hi Balaji,
What most likely is happening is that you have mismatched versions of apapi.jar (client side) and the database, thus the reason for the "invalid arguments in call" error you're seeing.
If you're using 9.0.1.3 of the database it should be patched with patch #2416054. Go to Metalink and do a search for this patch to find it. You can then use the apapi.jar that comes with the patched version of the DB or the apapi.jar that comes with v9.0.3.
By the way, v9.0.3 and 9.0.1.3 + patch is a J2EE 1.3 compatible JMS server.
I'm guessing that you used the apapi.jar that came with v9.0.2 with the v9.0.1.3 database and that you've probably already applied the above patch. If you have then just take the apapi.jar that came with v9.0.3 and use it in your v9.0.2 environment.
In short:
v9.0.3 apapi.jar matches with v9.0.1.3 + patch
v9.0.3 apapi.jar also matches with v9.0.1.4
v9.0.2 apapi.jar matches with v9.0.1.3
Hope this helps...
John
Hi,
I tried to use OJMS/AQ as the JMS provider in OC4J 9.0.2 and OC4J 9.0.3. Resource providers in both the containers point to the same Oracle database (9.0.1.3.0) using the same user account.
JMS works fine with OC4J 9.0.3 but not with OC4J 9.0.2.
During the start-up of 9[i]Long postings are being truncated to ~1 kB at this time.