IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > Oracle E-Business Suite > Troubleshooting and support
Limitations of JMS dequeue mechanism
The behavior of the JMS dequeue operation is found to differ based on the version of the aqapi.jar that is used. The aqapi.jar file from the Oracle database version 11i has stricter validations on the message header during the dequeue operation. Oracle E-Business Suite 12.x has Oracle database of 10g. The aqapi.jar file corresponding to this version seems to have lower restrictions during the dequeue operation. If you notice any dequeue errors with errors from the aqapi driver (JMS-xxx), then it indicates a problem with the driver version that is used. Recheck the version of aqapi.jar file and use aqapi.jar from the Oracle database 10g version.
Here are the limitations of JMS dequeue mechanism:
- Cannot retrieve array of messages
- All message properties and payload properties are not available
- Enqueue time using JMS transport mechanism is in milliseconds rather than timestamp format
Related tasks: