JMS exception: "Invalid method signature", when *.JARs on Siebel CRM side mismatches release of JMS Provider
(Doc ID 1459000.1)
Last updated on FEBRUARY 14, 2019
Applies to:Siebel CRM - Version 7.7.1  and later
Information in this document applies to any platform.
The "Invalid method signature" error error reported by EAI JMS Transport, when accessing a JMS Queue/Topic on a JMS Provider using "outdated" provider's API (*.JAR)
Below are sample traces when one could observe in the JMS API log, when Siebel Application uses "10.1.3.3" version of OC4J/SOA 10g class archives (*:JAR)
to send a JMS message to a Queue of JMS Provider of OC4/SOA Instance version "10.1.3.5":
Java class archives (*.JAR) of accordant JMS provider (OC4J in the example from above) are copied on Siebel CRM server for use by JMS Transport / Receiver
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!