Tuesday, May 24, 2011

ORABPEL-12141 - ERRJMS_CONN_FAC_NOT_FOUND


Error Description:

ORABPEL-12141
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor weblogic.jms.ConnectionFactory neither through JNDI nor instantiate it as a Java class [Caused by: invalid type code: 31]
Please examine the log file to determine the problem.
Caused by: javax.naming.CommunicationException [Root exception is java.rmi.UnmarshalException: failed to unmarshal class weblogic.security.acl.internal.AuthenticatedUser; nested exception is:
        java.io.StreamCorruptedException: invalid type code: 31]
Caused by: java.rmi.UnmarshalException: failed to unmarshal class weblogic.security.acl.internal.AuthenticatedUser; nested exception is:
        java.io.StreamCorruptedException: invalid type code: 31
        at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:223)
Caused by: java.io.StreamCorruptedException: invalid type code: 31
        at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1355)


Cause:  This exception may be thrown if the JRE/JDK is v1.6.The weblogic.jar is based on JDK1.5.


Solution: Add -Dsun.lang.ClassLoader.allowArraySyntax=true in opmn.xml under the container in which connectivity to the weblogic server is made.

2 comments:

  1. I am not able to find opmn.xml file. can you please give location where it can be? i am using oracle soa 11.1.1.5 and weblogic is of version 10.3.5

    ReplyDelete
  2. Hi Pinakpani,

    opmn.xml file can be found when Oracle Application Server has been used. SOA Suite 11g uses weblogic as the Application Server. So you need to add this parameter in setSOADomainEnv.sh/setSOADomainEnv.cmd file depending on the OS you are using. On weblogic application server, this file can be found @$Middleware_HOME/user_projects/domains//bin.

    HTH,
    -Shantanu

    ReplyDelete