OSB: JMS Foreign Server

Hi!
I have problem with configure BusinesService for HornetQ JMS Server.
Connection cannot instantiate:
<Error> <WliSbTransports> <BEA-381502> <Exception in JmsInboundMessageContext.close : javax.jms.JMSException: [JMSPool:169803]JNDI lookup of the JMS connection factory jms.WLReceiverCF failed: javax.naming.NoInitialContextException: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory [Root exception is java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory]
javax.jms.JMSException: [JMSPool:169803]JNDI lookup of the JMS connection factory jms.WLReceiverCF failed: javax.naming.NoInitialContextException: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory [Root exception is java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory]
     at weblogic.deployment.jms.JMSExceptions.getJMSException(JMSExceptions.java:29)
     at weblogic.deployment.jms.JMSConnectionHelper.lookupConnectionFactory(JMSConnectionHelper.java:485)
     at weblogic.deployment.jms.JMSConnectionHelper.openConnection(JMSConnectionHelper.java:268)
     at weblogic.deployment.jms.JMSConnectionHelper.<init>(JMSConnectionHelper.java:144)
     at weblogic.deployment.jms.JMSSessionPool.getConnectionHelper(JMSSessionPool.java:517)
     at weblogic.deployment.jms.PooledConnectionFactory.createConnectionInternal(PooledConnectionFactory.java:355)
     at weblogic.deployment.jms.PooledConnectionFactory.createQueueConnection(PooledConnectionFactory.java:188)ProxyService for this foreign server work fine.
Help please!
Best Regards,
lam
Edited by: laaam on Nov 25, 2010 1:02 PM
Edited by: laaam on Nov 25, 2010 7:52 PM

Hi Lam,
I have a successful configuration to JBoss JMS . My foreign server configuration is like this:
<foreign-server name=”ForeignServer”>
<default-targeting-enabled>true</default-targeting-enabled>
<foreign-destination name=”A”>
<local-jndi-name>A</local-jndi-name>
<remote-jndi-name>queue/A</remote-jndi-name>
</foreign-destination>
<foreign-connection-factory name=”FConf”>
<local-jndi-name>FConf</local-jndi-name>
<remote-jndi-name>ConnectionFactory</remote-jndi-name>
<username>esbuser</username>
<password-encrypted>{3DES}90sIZwo6Llr9r73p+VXkvQ==</password-encrypted>
</foreign-connection-factory>
<initial-context-factory>org.jnp.interfaces.NamingContextFactory</initial-context-factory>
<connection-url>jnp://localhost:1099</connection-url>
</foreign-server>
The difference I can see is the extra jndi property java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces. Can you try removing that ?
Another try if the above doesn't work is to specify the full jms business service URI if your JBoss destination is not a secured one (if no user name/password is required to access it).
jms://<WLSHostname>:<wls port>/jms.WLReceiverCF/jms.queue.RegisterDocumentResponse

Similar Messages

  • Issue with osb + weblogic foreign server AQ configuration

    Hi ,
    I am trying out a scenario wherein, OSB publishes a message onto an Oracle AQ JMS Topic.
    I have created the Foreign Server and have used the Local JNDIs of the connection factory and the destination within my OSB business service. But then, my business service fails to publish the message onto the AQ giving below exception in the server logs:
    "<BEA-169807>There was an error while making the initial connection to the JMS resource named ALSB_JMS_SessionPool_-541341947 from within an EJB or a servlet. The server will attempt the connection again later. The error was oracle.jms.AQjmsException: Error creating the db_connection"
    Below are the configurations that I have used for configuring the foreign server
    Connection Factory - LocalCF | Local JNDI - LocalCF | Remote JNDI - XATopicConnectionFactory
    Destination - ETASNIN | Local JNDI - ETASNIN | Remote JNDI - Topics/ETASNIN
    The Business Service URL: jms://xxxxhost:7011/LocalCF/ETASNIN
    **P.S:** I have tried out the same scenario of interfacing OSB with AQ JMS on a Windows box it works fine... But the above is the case on a UNIX box. Also, I am using PS3 of OSB with 10.3.4 of weblogic server.
    Any Suggestions on this would really help and is much appreciated...
    Thanks,
    Manoj Nair

    Hi Manoj,
    how it was solved?

  • Monitor JMS Foreign Server

    Hi,
              I have configured the IBM MQ server as a foreign server in one of the JMS Module of WLS9.1. I am able to identify it using JMX (MBeans).(I thought this was a good approach if u have any other approach for it? reply me).
              Now i want to monitor the Foreign Server i.e. capture the Foreign Server status whether the server is active or not and accordingly deploy/undeploy the Foreign Server.
              Can anyone go through this and reply me with the solution? PLzzzzzzzzzz its very urgent

    A "foreign server" is stateless configuration code that simply maps an application's JNDI lookup request into another vendor's JNDI context. It provides no monitoring.
              If you want to determine the status of the server that a foreign server references, you need to either (A) monitor the foreign server directly or (B) monitor the status of an application or service that depends on the foreign server.
              Tom

  • Weblogic: problem with JMS foreign server and Transaction

    Hello everyone,
    I am working with an enterprise application with Web Application Server Logic 10.3. L 'application uses the following components:
    1) MDB 2.0
    2) FOREIGN JMS SERVER -> WebSpereMQ
    3) EJB SESSION
    L 'MDB calls the session bean which uses in its ejb-jar.xml using a Wrapper for JMS QueueConnectionFactory with res-ref:
    <resource- ref>
    <res-ref-name> jms / iss / QCFIXP </ res-ref-name>
    <res-auth> Container </ res-auth>
    <res-sharing -scope> Shareable </ res-sharing-scope>
    <resource- ref>
    The MDB is CMT
    <transaction-type> Container </ transaction-type>
    while the session bean is BMT
    <transaction-type> Bean </ transaction-type>
    to call the QCFIXP in its transaction.
    The QCFIXP ii an XA resource
    When there is a rollback operation in SessionBean also in 'MDB
    There 'an operation setRollbackOnly:
    getMessageDrivenContext (). setRollbackOnly ();
    After this operation on the MDB I do a JNDI look up the QueueConnectionFactory but sending the message on a queue I get the following exception:
    javax.jms.JMSException: [JMSPool: 169809] An error occurred while registering the JMS connection with JTA:
    But if not using the "wrapper jms" in the session bean I did not take any exception and the application don' t have any error.
    My doubt is :
    Why if I use the JMS wrapper I get an error javax.jms.JMSException: [JMSPool: 169809] An error occurred while registering the JMS connection with JTA?
    Thanks in advance.
    Michele
    Edited by: user3501731 on 11-mag-2011 3.16

    Hi Tom,
    Thanks very much for your responses and careful analysis you've done.
    Following the source code of the MDB where error occurs.
    Marked In bold the line where the exception is thrown.
         public void onMessage(Message msg) {
    //          Utility.logger(AP.DEBUG, "Partito MDB 2");
              processa(msg);
              protected void processa(Message msg) {
              Utility.logger(
                   AP.DEBUG,
                   "IXPReceiverMDB7.processa(Message msg) partito");
              try {
                   long start = System.currentTimeMillis();
    /*               Utility.logger(
                        AP.DEBUG,
                        "IXPReceiverMDB.processa(Message msg) effettuo lookup");*/
                   ejb = myEjbLocalHome.create();
                   // individuo l'identificativo del messaggio in ricezione
                   String msgid = msg.getJMSMessageID();
                   Utility.logger(
                        AP.DEBUG,
                        "IXPReceiverMDB7.processa(Message msg) elaboro messaggio:"
                             + msgid);
                   String charset = msg.getStringProperty("JMS_IBM_Character_Set");
                   Utility.logger(
                        AP.DEBUG,
                        "IXPReceiverMDB7.processa Charset:" + charset );
                   // invoco il processo di ricezione
                   boolean commitRequested = ejb.processa(ctlReq, encoding, msg);
                   // il valore di ritorno del processo di ricezione identifica o meno
                   // la necessita' di effettuare il rollback dell'intero processo
                   if (!commitRequested) {
                        getMessageDrivenContext().setRollbackOnly();
                   if (ctlReq) {
                        Utility.logger(
                             AP.INFO,
                             "IXPReceiverMDB7.processa(Message msg) spedisco il messaggio pilota del 'cleaning' con JMSCorrelationID = '"
                                  + msgid
                                  + "'");
                        msg.setJMSCorrelationID(msgid);
                        // Viene creata la QueueConnection
                        QueueConnectionFactory factory =
                             JmsFactoryDispenser.getSingleton().getFactory();
                        QueueConnection connection = factory.createQueueConnection();
                        // Viene ottenuta la 'session'
                        QueueSession session =
                             connection.createQueueSession(
                                  false,
                                  Session.AUTO_ACKNOWLEDGE);
                        // spedisco il messaggio sulla coda abbinata al processo di 'cleaning'
                        // della coda di controllo
                        IXPMessageManager msgManager = new IXPMessageManager(session);
                        msgManager.spedisci(msg, AP.PILOTQUEUE, "J", AP.STD_MESSAGE);                    session.close();
                        connection.close();
                   long end = System.currentTimeMillis();
                   Long durata = new Long (end - start);
                   Utility.logger(
                        AP.INFO,
                        "IXPReceiverMDB7 Tempo totale elaborazione messaggio: " +
                        msgid + " " +
                        durata.toString() + " mill" );
                   Utility.logger(
                        AP.DEBUG,
                        "IXPReceiverMDB7.processa(Message msg) terminato");
              } catch (Throwable e) {
                   getMessageDrivenContext().setRollbackOnly();
                   try {
                        Utility.myExceptionHandler(
                             "E",
                             "1",
                             "4028",
                             "IXPReceiverMDB.onMessage()",
                             e);
                   } catch (Throwable ex) {
                        ex.printStackTrace();
    Thanks in advance.
    Edited by: serpichetto on 16-mag-2011 1.24

  • MDB cannot connect to JMS destination using Foreign Server

    Hi everyone,
    I have configured foreign jms server in weblogic but when MDB tries to connect to specific queue, it gets the following exception:
    I would really appreciate if anyone could help me.
    <Sep 28, 2012 5:23:34 PM CEST> <Warning> <EJB> <BEA-010096> <The Message-Driven EJB: SmsReceiver is unable to connect to the JMS destination or bind to JCA resource adapter: xcg2/smsInQueue. Connection failed after 2 attempts. The MDB will attempt to reconnect/rebind every 10 seconds. This log message will repeat every 600 seconds until the condition clears.>
    <Sep 28, 2012 5:23:34 PM CEST> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: SmsReceiver is unable to connect to the JMS destination: xcg2/smsInQueue. The Error was:
    [EJB:011010]The JMS destination with the JNDI name: jmsxcg.out could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.xml or corresponding annotation is correct, and the JMS destination has been deployed.
    javax.naming.InvalidNameException: jmsxcg.out: [LDAP: error code 34 - Invalid DN]; remaining name 'jmsxcg.out' NestedException Message is :jmsxcg.out: [LDAP: error code 34 - Invalid DN]>
    MDB annotation looks like this:
    @MessageDriven(name="SmsReceiver", mappedName="xcg2/smsInQueue",
    activationConfig = {
    @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue")
    @TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED)
    public class SmsReceiverBean implements MessageListener
    weblogic-ejb-jar.xml excerpt:
         <weblogic-enterprise-bean>
              <ejb-name>SmsReceiver</ejb-name>
              <message-driven-descriptor>
                   <pool>
                        <max-beans-in-free-pool>10</max-beans-in-free-pool>
                        <initial-beans-in-free-pool>5</initial-beans-in-free-pool>
                   </pool>
                   <connection-factory-jndi-name>echoQueueConnectionFactory</connection-factory-jndi-name>
              </message-driven-descriptor>
              <transaction-descriptor>
                   <trans-timeout-seconds>600</trans-timeout-seconds>
              </transaction-descriptor>
    <dispatch-policy>MdbSmsWorkManager</dispatch-policy>
         </weblogic-enterprise-bean>
    and the configuration of foreign-server:
    <?xml version="1.0" encoding="UTF-8"?>
    <weblogic-jms xmlns="http://www.bea.com/ns/weblogic/weblogic-jms">
    <foreign-server name="serverr">
    <sub-deployment-name>Subdeployment</sub-deployment-name>
    <foreign-destination name="sms queue>
    <local-jndi-name>xcg2/smsInQueue</local-jndi-name>
    <remote-jndi-name>jmsxcg.out</remote-jndi-name>
    </foreign-destination>
    <foreign-connection-factory name="Connection Factory">
    <local-jndi-name>echoQueueConnectionFactory</local-jndi-name>
    <remote-jndi-name>QueueConnectionFactory</remote-jndi-name>
    </foreign-connection-factory>
    <initial-context-factory>com.tibco.tibjms.naming.TibjmsInitialContextFactory</initial-context-factory>
    <connection-url>tibjmsnaming://xx.xx.xx.xx:7222</connection-url>
    </foreign-server>
    </weblogic-jms>
    PS. I'm able to connect to the weblogic jndi, get connectionFactory echoQueueConnectionFactory, then lookup queue and grab messages so that's i suspect there is something wrong with configuration

    Hmm - I'm not sure what's going on. Two thoughts --
    Thought 1 - According to my (admittedly minimal) research, Tibco is complaining about a syntax error in the lookup name. Perhaps the problem has something to do with your use of a "." in the queue name "jmsxcg.out": WL or Tibco JNDI might be interpreting the "." as a subcontext or some-such. Perhaps try renaming the queue to "jmsxcg_out" throughout (in Tibco and in your Foreign JMS reference).
    Thought 2 - It probably won't make a difference, but you might want try specifying the source destination via the "destinationJndiName" config property instead of via "mappedName".
    @MessageDriven(
      name = "MyMDB",
      activationConfig = {
        @ActivationConfigProperty(propertyName  = "destinationType",
                                  propertyValue = "javax.jms.Queue"),
        @ActivationConfigProperty(propertyName  = "destinationJndiName",
                                  propertyValue = "MyQueue") // Ext. JNDI Name
    )HTH,
    Tom

  • JMS Foregin server configuration with two Weblogic 8.1 AS

    Hi,
    I have two Weblogic8.1 AS. Box 1 is configured with JMS connection factory and Topic. MDB is deployed on Box 2, which is configured to listen to Box1 JMS Topic. I am running session bean which is publishing JMS message to the Topic on Box1. Also, I have configured JMS foreign Server on Box2 pointing to Box1 connection factory and Topic.
    MDB throws error "Destination not found", while deploying. I read somewhere in the net, that We need Weblogic with Clustering licence for configuring Foreign JMS Server.
    Pls. help me.
    Regards
    Anand Bobade

    hi... can you please send me the java code for messaging part ...... i want to know how you are sending
    message from server and it is listened at different server?
    I am also in same condition....I have configured JMS foreign server on box 1 .....on box2 my MDB is listening....
    My problem is how do i send a message to a foreign queue which is inside JMS Foreign Server..... I am not able to give any JNDI name to this server... so please send me the code from which you are sending the Message.
    Thanks in advance

  • WebLogic 10.3.3 - 2-Way SSL setup between WLS JMS Foregin Server & IBM MQ 6

    Hi,
    I am trying to configure 2-Way SSL between WebLogic 10.3.3 using JMS Foreign Server and IBM MQ 6. I could not find any documentation on this.
    Can someone provide with steps for setting up 2-Way between WebLogic and IBM MQ?
    Also I want to use SSLPEERNAME attribute in MQ Connection Factory and generate bindings so that I can connect to correct queuemanager on MQ side. Please let me know the configuration steps and check's that have to be done on WLS and IBM MQ side on this.
    Thanks in advance
    - BoyelT

    Check this:
    http://www.ibm.com/developerworks/websphere/library/techarticles/0510_fehners/0510_fehners.html

  • JMS Module, Foreign Server: Destination unreachable

    Hi,
    In our OSB setup we have 2 weblogic domains (on RHEL5), one for hosting the OSB services and one that is used solely for the purpose of JMS messsaging.
    Therefore we have configured a Foreign Server in our JMS Module on the OSB Domain with following config:
    * JNDI Initial Context Factory: weblogic.jndi.WLInitialContextFactory
    * JNDI Connection URL: t3://fsb-jms1-dev:7901,fsb-jms2-dev:7901
    After deploying an EJB that makes use of this module we see following error in our log files every time when starting a Managed Server:
    ####<Jun 8, 2011 11:36:48 AM CEST> <Warning> <EJB> <esddev148> <osbms1> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <11d1def534ea1be0:-27013fcb:1306e9a12ac:-8000-0000000000000016> <13075
    25808959> <BEA-010061> <The Message-Driven EJB: MessageLogWriter is unable to connect to the JMS destination: fsb.jms.MessageLoggingQueue. The Error was:
    javax.naming.CommunicationException [Root exception is java.rmi.ConnectException: Could not establish a connection with 3499163233583403748S:fsb-jms1-dev:[7901,-1,-1,-1,-1,-1,-1]:fsb-jms1-dev:7901,fsb-jms2-dev:7901:jmsdevdomain:jmsms1, java
    .rmi.ConnectException: Destination unreachable; nested exception is:
    java.io.IOException: Empty server reply; No available router to destination; nested exception is:
    java.rmi.ConnectException: Destination unreachable; nested exception is:
    java.io.IOException: Empty server reply; No available router to destination]
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:64)
    at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:470)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:426)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
    at javax.naming.InitialContext.lookup(InitialContext.java:392)
    at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:221)
    at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
    at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
    at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
    at javax.naming.InitialContext.lookup(InitialContext.java:392)
    at weblogic.jms.common.CDS$2.run(CDS.java:486)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:131)
    at weblogic.jms.common.CDS.lookupDestination(CDS.java:480)
    at weblogic.jms.common.CDS.lookupDDAndCalloutListener(CDS.java:345)
    at weblogic.jms.common.CDS.access$100(CDS.java:41)
    at weblogic.jms.common.CDS$DDListenerRegistrationTimerListener.timerExpired(CDS.java:193)
    at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    Caused by: java.rmi.ConnectException: Could not establish a connection with 3499163233583403748S:fsb-jms1-dev:[7901,-1,-1,-1,-1,-1,-1]:fsb-jms1-dev:7901,fsb-jms2-dev:7901:jmsdevdomain:jmsms1, java.rmi.ConnectException: Destination unreachab
    le; nested exception is:
    java.io.IOException: Empty server reply; No available router to destination; nested exception is:
    java.rmi.ConnectException: Destination unreachable; nested exception is:
    java.io.IOException: Empty server reply; No available router to destination
    at weblogic.rjvm.RJVMImpl.getOutputStream(RJVMImpl.java:352)
    at weblogic.rjvm.RJVMImpl.getRequestStreamInternal(RJVMImpl.java:612)
    at weblogic.rjvm.RJVMImpl.getRequestStream(RJVMImpl.java:563)
    at weblogic.rjvm.RJVMImpl.getOutboundRequest(RJVMImpl.java:789)
    at weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:159)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:341)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
    at weblogic.jndi.internal.ServerNamingNode_1034_WLStub.lookup(Unknown Source)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:423)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:412)
    at javax.naming.InitialContext.lookup(InitialContext.java:392)
    at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:221)
    at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
    at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
    at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:412)
    at javax.naming.InitialContext.lookup(InitialContext.java:392)
    at weblogic.jms.common.CDS$2.run(CDS.java:486)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:131)
    at weblogic.jms.common.CDS.lookupDestination(CDS.java:480)
    at weblogic.jms.common.CDS.lookupDDAndCalloutListener(CDS.java:345)
    at weblogic.jms.common.CDS.access$100(CDS.java:41)
    at weblogic.jms.common.CDS$DDListenerRegistrationTimerListener.timerExpired(CDS.java:194)
    ... 4 more
    Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
    java.io.IOException: Empty server reply; No available router to destination
    at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:470)
    at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:402)
    at weblogic.rjvm.RJVMImpl.ensureConnectionEstablished(RJVMImpl.java:306)
    at weblogic.rjvm.RJVMImpl.getOutputStream(RJVMImpl.java:350)
    at weblogic.rjvm.RJVMImpl.getRequestStreamInternal(RJVMImpl.java:613)
    ... 30 more
    >
    I've allready ensured that the managed servers of the jms cluster are reachable by issuing a connect command from WLST (although making the connection can be time consuming)
    wls:/offline> connect('weblogic','******','t3://fsb-jms1-dev:7901')
    Connecting to t3://fsb-jms1-dev:7901 with userid weblogic ...
    Successfully connected to managed Server 'jmsms1' that belongs to domain 'jmsdevdomain'.
    Warning: An insecure protocol was used to connect to the
    server. To ensure on-the-wire security, the SSL port or
    Admin port should be used instead.
    wls:/jmsdevdomain/serverConfig> disconnect()
    Disconnected from weblogic server: jmsms1
    wls:/offline> connect('weblogic','******','t3://fsb-jms2-dev:7901')
    Connecting to t3://fsb-jms2-dev:7901 with userid weblogic ...
    Successfully connected to managed Server 'jmsms2' that belongs to domain 'jmsdevdomain'.
    Warning: An insecure protocol was used to connect to the
    server. To ensure on-the-wire security, the SSL port or
    Admin port should be used instead.
    In my search for a solution I've also read that this could be caused by a bad configured DNS server. Therefore I configured my /etc/nsswitch.conf file to contain only the property files under the parameter hosts.
    Following is an extraction of my /etc/hosts file:
    10.16.85.50 fsb-jms1-dev.localdomain fsb-jms1-dev
    10.16.85.51 fsb-jms2-dev.localdomain fsb-jms2-dev
    10.16.85.52 fsb-osb1-dev.localdomain fsb-osb1-dev
    10.16.85.53 fsb-osb2-dev.localdomain fsb-osb2-dev
    Does anybody have an idea how I can further debug this problem?
    Kind Regards,
    Davy

    Maybe this is of some help: http://www.bea-weblogic.com/namenotfoundexception-when-configuring-foreign-jms-server.html

  • How to access local connection factory created within Foreign Server in OSB

    Hi All
    I am facing an issue in my config plan. We have a RIB Foreign server with the following local connection factory:
    jms/RibAqJmsXATopicConnectionFactory
    I am using the below in my configuration plan:
    <cus:envValueAssignments>
    <xt:envValueType>Service URI</xt:envValueType>
    <xt:location xsi:nil="true"/>
    <xt:owner>
    <xt:type>ProxyService</xt:type>
    <xt:path>RLTPReturnToWarehouse/ProxyServices/ConsumeRIBRTWMessages</xt:path>
    </xt:owner>
    <xt:value xsi:type="xs:string" xmlns:xs="http://www.w3.org/2001/XMLSchema">jms://localhost:7001/jms.RibAqJmsXATopicConnectionFactory/jms.etASNInFromRIBToWH1</xt:value>
    </cus:envValueAssignments>
    and i am getting the below error:
    [java]
    [java] Loading customization File ./dev/OSBCustomizationFile.xml
    [java] Customization applied to the created resources only []
    [java] com.bea.wli.config.customization.EnvValueCustomization@553c13
    [java] Unexpected error: com.bea.wli.sb.transports.TransportException
    [java] Problem invoking WLST - Traceback (innermost last):
    [java] File "D:\VFUKScripts\DeploymentScripts\osb\import.py", line 200, in ?
    [java] File "D:\VFUKScripts\DeploymentScripts\osb\import.py", line 122, in importToALSBDomain
    [java] com.bea.wli.sb.transports.TransportException: Failed to lookup connection factory jms.RibAqJmsXATopicConnectionFactory
    what am i missing here?

    [java] com.bea.wli.sb.transports.TransportException: Failed to lookup connection factory jms.RibAqJmsXATopicConnectionFactory
    Looks like the JNDI that you created for the ConnectionFactory is not reflected in the server.
    Login to WLS Console> Summary of Servers > server_name > View JNDI Tree
    Browse to the JNDI tree and see if your JNDI is visible there. If it is not then, please restart the server and recheck.
    Once you are able to find it in the JNDI tree, then execute the customization file.
    If you have modified the existing JNDI properties (that have a small exclamatory symbol) then any changes to those are not reflected till all the servers in the cluster are restarted.
    If it still does not work, then recreate a new Connection with a different name and then retry. It should work then.
    Thanks,
    Patrick

  • Query while configuring foreign server in JMS module

    Hi All,
    I'm configuring foreign server in my weblogic 10.3 to access the queues in the remote weblogic server 10.3. while configuring the foreign server it is asking for the destination and connection factory JNDIs for both local and remote server. My question is whatever JNDI we gave for the local destination or connection factory whether it should be already existing one or do we need to give that JNDI value unique for that Foreign server. I mean whether we have to create queue and connection factory and use their JNDIs or no need to create queues and connection factory and directly giving the JNDI names.
    And one more question is while configuring JMS adapter in Jdev11g what should be the JNDI name to be given in the JMS adapter configuration wizard.
    Thanks.

    my scenario is I have created a queue and connection factory in one weblogic server A and i have created foreign server in other weblogic server B and using the unique local JNDI names and JNDI names of B in remote JNDI for destination and connection factory tabs. Now in the deployment plan i have created one connection pool in the resource adapter(in my scenario it is JMS adapter) where i have gave the connection factory as local JNDI connection factory.
    Now I created one composite in which i have created one JMS adapter to place data into the queue and deployed the composite. when executing the composite i'm getting an error saying that the resource adapter could not able to find the JNDI name.

  • Weblogic 8.1: Remote/Foreign Server JMS - Destination not found error

    Hi
    This is our current setup: Weblogic Server 8.1 with JMS module running on the same instance as the application. We would like to move JMS out into its own box. I am currently setting up my development environment to test the new setup. These are the steps I followed:
    * Setup the server instance running the application on one box (Box1). Removed the existing JMS Connection Factory and Destination JNDI setup
    * Setup a server instance on another box (Box2) without the application. Created the necessary JMS Connection Factories and Destinations. Started the server instance on Box2
    * Added a Foreign Server configuration on Box1. Created the connection factory and destinations under this foreign server pointing to Box2
    * The Foreign JNDI names are being bound correctly (I verified the JNDI tree on Box1). Restarted the server instance of Box1
    Message-Driven Beans deployed on Box1 are unable to retrieve messages from Box2. The exception thrown is given below. Any help in troubleshooting and resolving this issue is appreciated.
    <Warning> <EJB> <myserver> <main> <<WLS Kernel>> <> <BEA-010061> <The Message-Driven EJB: MyBean is unable to connect to the JMS destination: jms/my.application.firstQueue. The Error was:
    weblogic.jms.common.JMSException: Destination not found
    weblogic.jms.common.JMSException: Destination not found
    at weblogic.jms.dispatcher.InvocableManager.invocableFind(InvocableManager.java:136)
    at weblogic.jms.backend.BESession.createConsumer(BESession.java:153)
    at weblogic.jms.backend.BESession.invoke(BESession.java:1457)
    at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:643)
    at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:179)
    at weblogic.jms.frontend.FEConsumer.<init>(FEConsumer.java:232)
    at weblogic.jms.frontend.FESession$3.run(FESession.java:1058)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    at weblogic.jms.frontend.FESession.consumerCreate(FESession.java:1054)
    at weblogic.jms.frontend.FESession.invoke(FESession.java:2552)
    at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:643)
    at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:179)
    at weblogic.jms.client.JMSSession.consumerCreate(JMSSession.java:1860)
    at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:1691)
    at weblogic.jms.client.JMSSession.createReceiver(JMSSession.java:1530)
    at weblogic.ejb20.internal.JMSConnectionPoller.setUpQueueSessions(JMSConnectionPoller.java:1720)
    at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:2019)
    at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1180)
    at weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSConnectionPoller.java:846)
    at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.start(MessageDrivenBeanPoolInfoImpl.java:234)
    at weblogic.ejb20.deployer.EJBDeployer.deployMessageDrivenBeans(EJBDeployer.java:1660)
    at weblogic.ejb20.deployer.EJBDeployer.startMessageDrivenBeans(EJBDeployer.java:1555)
    at weblogic.t3.srvr.T3Srvr.startMDBs(T3Srvr.java:948)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:1024)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
    at weblogic.Server.main(Server.java:32)
    Edited by: user8773992 on Sep 2, 2009 11:31 AM

    1 - Ensure that the MDB is configured to reference the remote connection factory AND remote destination.
    2 - If using the foreign JMS server facility, ensure that it defines the URL of the remote cluster/server, a connection factory mapping, and a destination mapping. Also ensure that the MDB connection factory and destination descriptor fields reference the local JNDI names for the mappings.
    3 - If not using the foreign JMS server facility, ensure that the MDB descriptor has the URL of the remote cluster, and a destination JNDI name that's in the remote cluster. (The connection factory JNDI name is not needed in this case, as the MDB will automatically look for a default connection factory that MDB's use.)
    I think the MDB chapter of the EJB programmer's guide will likely be helpful here. The latest documentation for the latest release may be more up-to-date than 8.1 -- the concepts are the same with the newer releases.
    Tom

  • OSB to MQ, using Foreign Server

    Hi All,
               I am working on OSB to MQ connectivity, using Foreign Server. I was able to establish the connectivity using Sun JDK 1.6. However when I JRockit 1.6 is used, connectivity is not working. There are stuck threads in Weblogic, when weblogic has to invoke the MQ Jars. Any suggestions, will be greatly appreciated.
    Regards.

    Hi
    Thats very strange behavioural diffrerence between Sun & Jrockit.
    Take it you have gone through the stuck threads and realised threads were marked stuck when trying to invoke / load MQ jars? can you copy the stuck threads referring that please.
    Have you tried loading those MQ jars in the classpath of the server .. That way all the necessary jars/classes will be available local to the instance
    and can be located by classloader without much delay.
    HTH
    Sri

  • Foreign server or JMS Bridge?

    Weblogic 11g
    WebsphereMQ 7
    Good morning,
    I have a question regarding JMS architecture.
    We’re going to deploy a new app using JMS but all the messaging architecture will be on WebshereMQ.
    Our middleware team recommends us to create a foreign server to communicate with MQ.
    So my question is quite simple, why using a Foregin server instead of a JMS Bridge?
    I’d have used the latter as it aims to communicated with other Message Oriented Middleware.
    Thanks for your wise advices

    You can find more information about integrating with a remote or foreign JMS provider at
    http://docs.oracle.com/cd/E17904_01/web.1111/e13727/interop.htm#i1009767
    This doc discusses a number of approaches and best practices for each of them.
    The messaging bridge does introduce an extra hop; messages are put into a local destination and then forwarded to the final destination. This is useful when the remote destination is not highly available. The bridge will take the messages even when remote destination is not available and then forward them with build-in retry logic when the remote destination becomes available.
    If the remote destination is highly available, foreign JMS server is preferable since it directly access the final destination without an extra hop.
    Hope this helps.
    Dongbo

  • Not able to connect to a queue under a foreign server.

    Not able to connect to a queue under a foreign server.
    I'm using WebLogic Server Version: 10.3.3.0. The foreign server is running, and can be pinged from this local server. Also the port where queue resides on foreign server, can be accessed through the my local server.
    OS used is AIX 6.0 on both servers.
    Tried restarting the local server but nothing helps. Same error continues.
    HAS ANYBODY FACED THIS PROBLEM? WHAT IS THE CAUSE AND SOLUTION FOR THIS?
    It throws following errors:
    <Jun 25, 2012 12:14:15 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
    javax.naming.NoInitialContextException: Failed to create InitialContext using factory specified in hashtable [Root exception is java.lang.ClassCastException: Expected RemoteException, RuntimeException, or Error but received: 'java.io.IOException: RJVM has already been shutdown']
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:247)
         at javax.naming.InitialContext.initializeDefaultInitCtx(InitialContext.java:318)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:348)
         at javax.naming.InitialContext.internalInit(InitialContext.java:286)
         at javax.naming.InitialContext.<init>(InitialContext.java:211)
         at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:179)
         at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
         at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
         at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
         at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
         at javax.naming.InitialContext.lookup(InitialContext.java:436)
         at weblogic.jms.common.CDS$2.run(CDS.java:503)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
         at weblogic.jms.common.CDS.lookupDestination(CDS.java:497)
         at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:276)
         at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1455)
         at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1252)
         at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
         at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
         at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:531)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:157)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
         at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: java.lang.ClassCastException: Expected RemoteException, RuntimeException, or Error but received: 'java.io.IOException: RJVM has already been shutdown'
         at weblogic.common.internal.BootServicesStub.getMsg(BootServicesStub.java:34)
         at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
         at weblogic.security.acl.internal.RemoteAuthenticate.authenticate(RemoteAuthenticate.java:90)
         at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRemotely(WLInitialContextFactoryDelegate.java:746)
         at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:678)
         at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:469)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:376)
         at weblogic.jndi.Environment.getContext(Environment.java:315)
         at weblogic.jndi.Environment.getContext(Environment.java:285)
         at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:239)
         ... 46 more
    >
    <Jun 25, 2012 12:14:15 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
    Can not get destination information. The destination JNDI name is NOTIFY_QUEUE, the provider URL is null>
    <Jun 25, 2012 12:14:45 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
    java.io.IOException: RJVM has already been shutdown
    java.io.IOException: RJVM has already been shutdown
         at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
         at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
         at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
         at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
         at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
         Truncated. see log file for complete stacktrace
    >
    <Jun 25, 2012 12:15:03 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
    java.io.IOException: RJVM has already been shutdown
    java.io.IOException: RJVM has already been shutdown
         at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
         at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
         at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
         at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
         at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
         Truncated. see log file for complete stacktrace
    >
    <Jun 25, 2012 12:15:25 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
    java.io.IOException: RJVM has already been shutdown
    java.io.IOException: RJVM has already been shutdown
         at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
         at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
         at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
         at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
         at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
         Truncated. see log file for complete stacktrace
    >
    <Jun 25, 2012 12:15:35 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
    java.io.IOException: RJVM has already been shutdown
    java.io.IOException: RJVM has already been shutdown
         at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
         at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
         at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
         at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
         at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
         Truncated. see log file for complete stacktrace
    >
    <Jun 25, 2012 12:15:43 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
    java.io.IOException: RJVM has already been shutdown
    java.io.IOException: RJVM has already been shutdown
         at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
         at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
         at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
         at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
         at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
         Truncated. see log file for complete stacktrace
    >
    <Jun 25, 2012 12:20:53 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
    java.io.IOException: RJVM has already been shutdown
    java.io.IOException: RJVM has already been shutdown
         at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
         at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
         at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
         at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
         at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
         Truncated. see log file for complete stacktrace
    >
    <Jun 25, 2012 12:24:16 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
    java.io.IOException: RJVM has already been shutdown
    java.io.IOException: RJVM has already been shutdown
         at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
         at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
         at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
         at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
         at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
         Truncated. see log file for complete stacktrace
    Edited by: 942523 on Jun 24, 2012 11:38 PM

    Thanks René van Wijk for the reply.
    I have a foreign server created in my local server, where i have already given the provider URL. This foreign server has the one queue and one queue connection factory under it to which I'm referring to.
    Under JNDI tree i noticed this, for the queue(NOTIFY_QUEUE) i'm trying to read from one of the EJB:
    This page displays details about this bound object.
    Failed to create InitialContext using factory specified in hashtable
    Also,etc/hosts has already these IP entries. Even after hardcoding the provider URL its throwing following:
    <Jun 25, 2012 3:01:31 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
    javax.naming.CommunicationException [Root exception is weblogic.rjvm.PeerGoneException: ; nested exception is:
         java.io.EOFException]
         at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:74)
         at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:452)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:408)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
         at javax.naming.InitialContext.lookup(InitialContext.java:436)
         at weblogic.jms.common.CDS$2.run(CDS.java:503)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
         at weblogic.jms.common.CDS.lookupDestination(CDS.java:497)
         at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:276)
         at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1455)
         at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1252)
         at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
         at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
         at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:531)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:157)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
         at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: weblogic.rjvm.PeerGoneException: ; nested exception is:
         java.io.EOFException
         at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
         at weblogic.jndi.internal.ServerNamingNode_1033_WLStub.lookup(Unknown Source)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:405)
         ... 36 more
    Caused by: java.io.EOFException
         at weblogic.rjvm.t3.MuxableSocketT3.endOfStream(MuxableSocketT3.java:338)
         at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:768)
         at weblogic.socket.SocketMuxer.deliverEndOfStream(SocketMuxer.java:702)
         at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:890)
         at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:840)
         at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:130)
         at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
         at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
    >
    <Jun 25, 2012 3:01:31 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
    Can not get destination information. The destination JNDI name is NOTIFY_QUEUE, the provider URL is t3://10.52.50.51:7002>
    Let me know if any other thing i'm missing or it can be something else like network or some other issue.

  • OSB jms clustering - load balancing seems to be not working

    Hi All,
    I have one admin server and two managed servers running ( one of these managed server is running in the remote linux machine) in a cluster
    I have connectionfactory created with load balance enabled with round robin
    and server affinity is disabled
    I have queue created as uniformly distributed Q
    I have a proxy service with load balancing as roundrobin and endpoint URL as below
    jms://rdoelapp001011:61703,rdoelapp001013:61703/synergyConnectionFactory1/MM_gridQ0
    If I execute this proxy sending messages it always go to one server only. There is no message going to the other server.
    If I shutdown the server that receives messages then the other server is receiving messages. Seems like fail-over is working but not the load-balancing
    There is one point may be worth mentioning here is, from the admin console if I look at the servers for the clusters it has below information
    Name      State      Drop-out Frequency      Remote Groups Discovered      Local Group Leader      Total Groups      Discovered Group Leaders      Groups      Primary      
    synergyOSBServer1     RUNNING     Never     0     synergyOSBServer1     1     synergyOSBServer1     *{synergyOSBServer1}*     0          
    synergyOSBServer2     RUNNING     Never     0     synergyOSBServer1     1     synergyOSBServer1     *{synergyOSBServer1, synergyOSBServer2}* 0
    one server has groups as {synergYOSBServer1} instead of {synergyOSBServer1, synergyOSBServer2}. Does that look correct?
    here is my jms xml file
    <?xml version='1.0' encoding='UTF-8'?>
    <weblogic-jms xmlns="http://xmlns.oracle.com/weblogic/weblogic-jms" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-jms http://xmlns.oracle.com/weblogic/weblogic-jms/1.1/weblogic-jms.xsd">
    *<connection-factory name="synergyConnectionFactory1">*
    *<sub-deployment-name>synergySubDeploy1</sub-deployment-name>*
    *<default-targeting-enabled>false</default-targeting-enabled>*
    *<jndi-name>synergyConnectionFactory1</jndi-name>*
    *<client-params>*
    *<client-id-policy>Restricted</client-id-policy>*
    *<subscription-sharing-policy>Exclusive</subscription-sharing-policy>*
    *<messages-maximum>10</messages-maximum>*
    *</client-params>*
    *<transaction-params>*
    *<xa-connection-factory-enabled>false</xa-connection-factory-enabled>*
    *</transaction-params>*
    *<load-balancing-params>*
    *<load-balancing-enabled>true</load-balancing-enabled>*
    *<server-affinity-enabled>false</server-affinity-enabled>*
    *</load-balancing-params>*
    *<security-params>*
    *<attach-jmsx-user-id>false</attach-jmsx-user-id>*
    *</security-params>*
    *</connection-factory>*
    <uniform-distributed-queue name="errorQ">
    <sub-deployment-name>synergySubDeploy1</sub-deployment-name>
    <default-targeting-enabled>false</default-targeting-enabled>
    <jndi-name>errorQ</jndi-name>
    <load-balancing-policy>Round-Robin</load-balancing-policy>
    <forward-delay>-1</forward-delay>
    <reset-delivery-count-on-forward>true</reset-delivery-count-on-forward>
    </uniform-distributed-queue>
    <uniform-distributed-queue name="undlvQ">
    <sub-deployment-name>synergySubDeploy1</sub-deployment-name>
    <default-targeting-enabled>false</default-targeting-enabled>
    <jndi-name>undlvQ</jndi-name>
    <load-balancing-policy>Round-Robin</load-balancing-policy>
    <forward-delay>-1</forward-delay>
    <reset-delivery-count-on-forward>true</reset-delivery-count-on-forward>
    </uniform-distributed-queue>
    *<uniform-distributed-queue name="MM_gridQ0">*
    *<sub-deployment-name>synergySubDeploy1</sub-deployment-name>*
    *<default-targeting-enabled>false</default-targeting-enabled>*
    *<jndi-name>MM_gridQ0</jndi-name>*
    *<load-balancing-policy>Round-Robin</load-balancing-policy>*
    *<forward-delay>5</forward-delay>*
    *<reset-delivery-count-on-forward>true</reset-delivery-count-on-forward>*
    *</uniform-distributed-queue>*
    <saf-imported-destinations name="synergySAFImportedDest1">
    <sub-deployment-name>synergySubDeploy1</sub-deployment-name>
    <default-targeting-enabled>false</default-targeting-enabled>
    <saf-queue name="gridQ0">
    <remote-jndi-name>MB_gridQ0</remote-jndi-name>
    <local-jndi-name>gridQ0</local-jndi-name>
    <non-persistent-qos>At-Least-Once</non-persistent-qos>
    <time-to-live-default>0</time-to-live-default>
    <use-saf-time-to-live-default>false</use-saf-time-to-live-default>
    <unit-of-order-routing>Hash</unit-of-order-routing>
    </saf-queue>
    <jndi-prefix>MB_</jndi-prefix>
    <saf-remote-context>synergySAFContext1</saf-remote-context>
    <saf-error-handling>synergySAFErrorHndlr1</saf-error-handling>
    <time-to-live-default>0</time-to-live-default>
    <use-saf-time-to-live-default>false</use-saf-time-to-live-default>
    <unit-of-order-routing>Hash</unit-of-order-routing>
    </saf-imported-destinations>
    <saf-remote-context name="synergySAFContext1">
    <saf-login-context>
    <loginURL>t3://rdoelapp001013:7001</loginURL>
    <username>weblogic</username>
    <password-encrypted>{AES}z9VY/K4M7ItAr2Vedvhx+j9htR/HkbY2LRh1ED+Cz5Y=</password-encrypted>
    </saf-login-context>
    <compression-threshold>2147483647</compression-threshold>
    </saf-remote-context>
    <saf-error-handling name="synergySAFErrorHndlr1">
    <policy>Log</policy>
    <log-format xsi:nil="true"></log-format>
    <saf-error-destination xsi:nil="true"></saf-error-destination>
    </saf-error-handling>
    </weblogic-jms>
    Any help will be greatly appriciated
    Edited by: 818591 on Feb 16, 2011 11:28 AM

    I am not getting you here "the right approach is to make OSB run on the man server cluster and not on admin server. "
    I have a jms proxy service that I created from admin console
    And also I have gone thru the step 5 in the link below
    http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/deploy/config.html#wp1524235
    If I am not wrong, the proxy service endpoint URI determines where it is pointing to. If it is a cluster environment, it should point to a clustered address
    My proxy has below endpoint URI
    jms://rdoelapp001011:61703,rdoelapp001013:61703/synergyConnectionFactory1/MM_gridQ0
    and rdoelapp001011:61703,rdoelapp001013:61703 is my cluster address
    As per your suggestion "To fix your problem, *make osb to run on the cluster* and specify the same URL for the jms proxy service"
    Could you please provide some instruction how would I "make osb jms proxy service to run in a cluster"
    As a note, I have Q defined as a distributed Q and connection factory targets to the cluster. UDQ also targtes to the cluster.
    Just for a testing I have created another manged server running local to the machine where my admin server is running
    And I created a proxy by following steps as I mentioned above and with endpoint URI as below
    jms://rdoelapp001011:61703,rdoelapp001013:61703,*rdoelapp001011:61700*/synergyConnectionFactory1/MM_gridQ0
    where the new address of my cluster is rdoelapp001011:61703,rdoelapp001013:61703,rdoelapp001011:61700
    It did create consumers in both the managed servers in the cluster that are running locally, but no consumers in the remote managed server.
    So I am kind of leaning towards thinking that there is some incorrect setup for the remote managed server and may be admin server is not able to communicate to the remote server for some reason but not sure about it..
    As a note the cluster is setup to communicate using "unicast" channel
    and I created a channel in each manged server with the same name
    here is the cluster configuration
    <name>synergyCluster1</name>
    <cluster-address>rdoelapp001011:61703,rdoelapp001013:61703,rdoelapp001011:61700</cluster-address>
    <default-load-algorithm>round-robin</default-load-algorithm>
    *<cluster-messaging-mode>unicast</cluster-messaging-mode>*
    *<cluster-broadcast-channel>synergyChannel1</cluster-broadcast-channel>*
    *<number-of-servers-in-cluster-address>3</number-of-servers-in-cluster-address>*
    </cluster>
    here are the twoOSBserver configuration
    <server>
    <name>synergyOSBServer1</name>
    <machine xsi:nil="true"></machine>
    <listen-port>61703</listen-port>
    <cluster>synergyCluster1</cluster>
    <web-server>
    <web-server-log>
    <number-of-files-limited>false</number-of-files-limited>
    </web-server-log>
    </web-server>
    <server-debug>
    <debug-scope>
    <name>weblogic.jms.saf</name>
    <enabled>true</enabled>
    </debug-scope>
    <debug-jmssaf>true</debug-jmssaf>
    <debug-saf-sending-agent>true</debug-saf-sending-agent>
    </server-debug>
    <listen-address>localhost</listen-address>
    <network-access-point>
    *<name>synergyChannel1</name>*
    *<protocol>cluster-broadcast</protocol>*
    *<listen-address>localhost</listen-address>*
    *<listen-port>61702</listen-port>*
    <http-enabled-for-this-protocol>true</http-enabled-for-this-protocol>
    <tunneling-enabled>false</tunneling-enabled>
    *<outbound-enabled>true</outbound-enabled>*
    *<enabled>true</enabled>*
    <two-way-ssl-enabled>false</two-way-ssl-enabled>
    <client-certificate-enforced>false</client-certificate-enforced>
    </network-access-point>
    <jta-migratable-target>
    <user-preferred-server>synergyOSBServer1</user-preferred-server>
    <cluster>synergyCluster1</cluster>
    </jta-migratable-target>
    </server>
    <server>
    <name>synergyOSBServer2</name>
    <ssl>
    <enabled>false</enabled>
    </ssl>
    <machine xsi:nil="true"></machine>
    <listen-port>61703</listen-port>
    <listen-port-enabled>true</listen-port-enabled>
    <cluster>synergyCluster1</cluster>
    <web-server>
    <web-server-log>
    <number-of-files-limited>false</number-of-files-limited>
    </web-server-log>
    </web-server>
    <listen-address>rdoelapp001013</listen-address>
    <network-access-point>
    *<name>synergyChannel1</name>*
    *<protocol>cluster-broadcast</protocol>*
    *<listen-address>rdoelapp001013</listen-address>*
    *<listen-port>61702</listen-port>*
    <http-enabled-for-this-protocol>true</http-enabled-for-this-protocol>
    <tunneling-enabled>false</tunneling-enabled>
    *<outbound-enabled>true</outbound-enabled>*
    *<enabled>true</enabled>*
    <two-way-ssl-enabled>false</two-way-ssl-enabled>
    <client-certificate-enforced>false</client-certificate-enforced>
    </network-access-point>
    <java-compiler>javac</java-compiler>
    <jta-migratable-target>
    <user-preferred-server>synergyOSBServer2</user-preferred-server>
    <cluster>synergyCluster1</cluster>
    </jta-migratable-target>
    <client-cert-proxy-enabled>false</client-cert-proxy-enabled>
    </server>
    <server>
    Edited by: 818591 on Feb 18, 2011 11:26 AM

Maybe you are looking for

  • Setting pl/sql procedure as the data source in a Report Query

    Is there a way to set PL/SQL as the data source in a Report Query? we want to able to use the ReportQuery function and query results returned by a PL/SQL procedure. thanks

  • From fcp to wmv?...

    ultimately i need my finished video in windows media format. does anyone know how to convert it over from a quicktime movie or any other format coming out of the mac?

  • I just rented a movie from the ITunes store ...

    This is my first attempt at downloading a movie to my laptop, via Verizon MiFi 2200, to sync on to my Ipad to watch.  It appears that the movie takes 8 to 10 hours to download.  Is this correct?  If not, what am I doing wrong.  When I want to watch a

  • Memory card not detected in lumia 520

    Micro sd card is not getting detected in my lumia 520 pls help......

  • UTC date conversion:

    Is there a function to convert UTC time to a normal date format? I have the stored seconds since the 'epoch' -1970 and would like to convert that over to a normal date in a report.