Home/ Questions/Q 3487670
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-18T11:10:38+00:00

facing some strange behavior in OSB, i have configured WLS with MQ in client

  • 0

facing some strange behavior in OSB, i have configured WLS with MQ in client mode, i am doing some minor test to check the connection, i have created a proxy service to read the message from Q1 and a Business Service(BS) to route it to Q2. The issue is the proxy is able to read the message but the BS is throwing this:

JMSPool BEA-169807 There was an error while making the initial connection to the JMS resource named ALSB_JMS_SessionPool_491704821 from within an EJB or a servlet. The server will attempt the connection again later. The error was javax.jms.JMSException: [JMSPool:169803]JNDI lookup of the JMS connection factory AKBConnFact failed: javax.naming.NoInitialContextException: Cannot instantiate class: com.sun.jndi.fscontext.RefFSContextFactory [Root exception is java.lang.ClassNotFoundException: com.sun.jndi.fscontext.RefFSContextFactory

Note: The classpath or the domain/lib folder contains the RefFSContextFactory class

Any ideas gang..? TIA

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The answer is this is a bug in OSB which needs to be reported.
    As a workaround you need to individually set the jars in the weblogic classpath in your domain/server/bin folder. just go through the link below for more details:

    http://forums.oracle.com/forums/thread.jspa?threadID=2135523&start=0&tstart=0

    • 0