AQ & Message Bean in OC4J 9.0.2

Question

Despite all the confusion, I finally got 9.0.2 to work with AQ in a 8.1.7 database. Some of the standard JMS features are not supported by 9.0.2, but in my case I get what I needed: publish a msg using a standalone java class and receive it from a MDB.
However, there are a few issues remain outstanding.
1. Ever since I put the <resource-provider> in application.xml for AQ, the OC4J process refuse to shutdown by admin.jar -shutdown. I have to ctrl-C out of it and clean up the persistence myself. This is on Windows, not sure if the same on UNIX.
2. Deployment from Jdeveloper 9.0.2 is awefully slow, and many times the process will hang without any results.
3. Every time OC4J starts without a message in the queue, I got the following exception in OC4J console:
java.lang.NullPointerException
void com.copyright.delivery.DeliveryMDB.onMessage(javax.jms.Message)
void com.evermind.server.ejb.MessageDrivenBeanInvocation.run()
void com.evermind.util.ThreadPoolThread.run()
4. When OC4J restarts, the MDB always gets the last message again. (Could this be the issue of not cleanly shutdown?)
Do any of you know these problems and have a solution?
Thank you!

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.