JMS between 2 WLS

One Java JMS class can send message to a JMS queue in a WebLogic Server(WLS). However, it reports error: 'could not connect to the queue' when I put the same Java class in a WLS. What should be configured between these 2 WLS?
          BTW, I also establish the trust between 2 WLS.

See my reply in the clustering newsgroup.
          Don Criscione wrote:
          > I'm trying to provide access to a JMS queue between two instances of WLS that are
          > not in a cluster. I keep running into
          > a problem with the createQueueSession: JMSException: Connection not found. The initial
          > context and connection seem to
          > both be valid, at least the metadata looks correct. I suspect it's a problem with
          > the connection factory, but I'm not sure what to try next. I've attached the code
          > and the output.
          >
          > ------------------------------------------------------------------------
          > Name: jmsSessionProblem.txt
          > jmsSessionProblem.txt Type: Plain Text (text/plain)
          > Encoding: base64
          Rajesh Mirchandani
          Developer Relations Engineer
          BEA Support
          

Similar Messages

  • Foreign JMS between 8.1 and 7.0

              We are experience strange behaviour when we are using foreign JMS between 8.1 and
              7.0. When one MDB on a 8.1 server connects to the JMS on the 7.0 server everything
              is fine. When a second 8.1 server connect to a JMS queue on the 7.0 server the
              it seems to connect but the messages on hanging as pending. If we writes the provider
              URL directly into the MDB descriptor it seems to work. Should foreign JMS work
              between WLS versions? Is there any way to get more debugging information?
              Björn Caroll
              

    It should work. All a "Foreign JMS Provider" is in 8.1 is a way to create
              sort of a "symbolic link" in JNDI between some objects in another JNDI
              provider and the local WLS JNDI tree.
              You can get more info out of the MDB startup process by setting the
              following command-line settings when you start weblogic.Server:
              -Dweblogic.ejb.jms.connect.debug=true
              -Dweblogic.ejb.jms.connect.verbose=true
              (You'll also have to have "StdoutDebugEnabled" set in the "Server" element
              of your config.xml file, or you'll have to turn on that checkbox in the
              console.)
              Also, if you post your MDB deployment descriptors and the ForeignJMS stuff
              from config.xml, we might have some ideas.
              greg
              "Björn Caroll" <[email protected]> wrote in message
              news:3fd6f281$[email protected]..
              >
              > We are experience strange behaviour when we are using foreign JMS between
              8.1 and
              > 7.0. When one MDB on a 8.1 server connects to the JMS on the 7.0 server
              everything
              > is fine. When a second 8.1 server connect to a JMS queue on the 7.0 server
              the
              > it seems to connect but the messages on hanging as pending. If we writes
              the provider
              > URL directly into the MDB descriptor it seems to work. Should foreign JMS
              work
              > between WLS versions? Is there any way to get more debugging information?
              >
              > Björn Caroll
              

  • Using foreign JMS providers with wls

    does anybody have a clou, where i can find that article, i think it's
              by steve felts on using foreign JMS providers with wls? i think the
              link on dev2dev is broken?
              

    The new article is called "Using Foreign JMS Providers with WLS" and it's
              here:
              http://dev2dev.bea.com/resourcelibrary/whitepapers.jsp?highlight=whitepapers
              greg
              "leopld goess" <[email protected]> wrote in message
              news:[email protected]..
              > does anybody have a clou, where i can find that article, i think it's
              > by steve felts on using foreign JMS providers with wls? i think the
              > link on dev2dev is broken?
              

  • JMS Bridge from WLS to OAS not working; automatic redirection to JMS Port

    We have setup a JMS Bridge inbetween Weblogic Server 10.3.0 and Oracle App Server 10.1.3. In our test environment it is working fine. But, in LIVE, we are facing a problem. Firewall is there inbetween OAS and WLS.
    1. OAS Admin port 6003, is blocked by firewall. So, from outside environment we can't connect to this port.
    2. OAS Port 12401 (RMI Port) is not-blocked
    3. OAS Port 12601 (JMS Port) is blocked by firewall
    4. We created credential "JMS_USER" while configuring QueueConnFactory at OAS end and used it while setting up WLS JMS Bridge
    We are using ormi://172.24.255.59:12401/default as Provider URL from Weblogic while creating JMS Bridge.
    Problem
    ========
    While connecting from WLS we are getting the following error from WLS end:
    javax.jms.JMSException: Unable to create a connection to "apgst366/172.24.255.59:12,601" as user "JMS_USER".
         at com.evermind.server.jms.JMSUtils.make(JMSUtils.java:1050)
         at com.evermind.server.jms.JMSUtils.toJMSException(JMSUtils.java:1130)
         at com.evermind.server.jms.EvermindConnection.<init>(EvermindConnection.java:132)
         at com.evermind.server.jms.EvermindQueueConnection.<init>(EvermindQueueConnection.java:71)
    Question
    =========
    1) We are requesting for 12401; then why the JMS Port 12601 is being referred?
    2) Is there any automatic redirection from OAS end?
    3) Will unblocking the 12601 port by Firewall help?
    Please help me, as this has become a burning issue for us.
    Thanks in advance.

    Can anybody please help me?

  • JMS Message Bridge - WLS to MQ

    Hi,
    Subsequent to my last posts on Foreign JMS Server setup (where I had to receive a msg from a remote MQ Queue), now I have a requirement to post messages to an remote MQ Queue for a diff application.
    As a POC, I configured the JMS Message Bridge with bridge source as my local JMS queue and bridge destination as the Remote MQ Queue and it works fine as expected !!
    just have couple of questions on that -
    1. For a long time, I was struggling with this error on server startup
    <BEA-190032> << eis/jms/WLSConnectionFactoryJNDINoTX > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: Failed to start the connection ">
    Then I realized from the server log that the actual reason was authentication failure in MQ Queue Manager :
    JMSWMQ2013: The security authentication was not valid that was supplied for QueueManager '' with connection mode 'Client' and host name '77.40.190.130'. Please check if the supplied username and password are correct on the QueueManager you are connecting to AND
    JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED').
    Since this MQ setup is managed by someone else, when they pass on the .binding file after creating queuemanager, queue, etc, Should I also ask them for the username and password for the QM?? I am not sure if this is a part of the .binding file.
    2. Some doubts around the QOS. As I understood, I am using the No-Transaction Adapter. This means I can use QOS as either "Atmost once" or "Duplicate OK". The latter seems to be ok so that I dont lost messages in any case. But I am yet to find out if the other application is ok to handle duplicates.
    But is there a restriction/limitation to use "Exactly Once" ?? I noticed that there is also an XA-Transaction Adapter in WLS. Is it not possible to use that with MQ?
    Thanks in advance.
    best regards,
    Murali

    In your binding file QCF or XAQCF definition , you will see a Channel field since you are using a client mode to connect to the queue manager. This channel is called a Server Connection Channel [ SVRCONN]. At the queue manager side of things, when this SVRCONN is defined, MQ Admin teams tend to define an attribute called MCAUSER. In this setup the userid used for authorisation at queue manager is the following in the below precedence:
    1. If MCAUSER is defined in the channel, that will be the user id and it overrides any security context sent from client application. This user id should have sufficient permissions to connect to queue manager , get , put. The MQ admin teams on certain platforms will be able to get the exact permission that is missed from the queue manager error logs when a 2035 security exception occurs.
    2. If no MCAUSER is defined then the userid passed in the createConnection JMS call will be the user context used.
    I am not exactly sure of the behaviour when no MCAUSER and no user id in createConnection calls, but i think it takes the user of the MQ Listener process which starts the SVRCONN channel instance when a client initiates the connection.
    So for your situation, it will be worth start checking with how the MQ side configuration is. This issue tends to be a very common issue with client applns connecting to qmgr.

  • JMS/RMI causes  WLS to hang

    Hello,
    Not sure if this is the right newsgroup-I am trying to
    diagnose a problem where the weblogic server(5.1, SP9) hangs. I have run
    it through JProbe's Threadalyzer and I checked for deadlocks and no
    deadlocks were reported. What was reported were three thread stalls (one
    block stall and two wait stalls) . All the three thread stalls were
    holding JMSServerSession(different instances of it).
    Here is the architecture -
    A third party application makes a HTTP request to a servlet running on
    WLS and that servlet posts a message to JMS and returns. We are using
    ServerSessionPool. The client class implementing the MessageListener
    then calls other RMI objects within the same JVM(its non-clustered
    weblogic).
    Here is the question-under heavy load this seems to hang the system
    eventually. I am unable to determine why at this point. The thread dump
    is different each time.
    The onMessage() method calls one RMI object which delegates to a
    detailed object tree several layers deep(other RMI objects). In one of
    those RMI objects there is a synchronized block.
    Currently there is no notifyAll() being issued when this synchronized
    block exits.
    Is it necessary then to issue a notifyAll() within any synchronized code
    that is within the 'scope' of the onMessage()
    I would like the JMS thread to return immediately. So that the rest of
    the RMI code is handled in other threads.
    Thanks in advance,
    Aswin.

    Here is the thread dump-JProbe did not report any deadlock again( I did not profile the
    weblogic.* classes). However the CPU usage was 100% and the server just hung-
    "Thread-5" daemon prio=5 tid=0x3e1e7470 nid=0xd9 runnable [0x3e2af000..0x3e2afdc
    0]
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:86)
    at java.io.BufferedInputStream.fill(BufferedInputStream.java:186)
    at java.io.BufferedInputStream.read1(BufferedInputStream.java:225)
    at java.io.BufferedInputStream.read(BufferedInputStream.java:280)
    - locked <619fd20> (a java.io.BufferedInputStream)
    at COM.activesw.api.client.BrokerConnection.readData(BrokerConnection.ja
    va:1584)
    at COM.activesw.api.client.BrokerConnection.run(BrokerConnection.java:15
    06)
    "SocketListener" daemon prio=5 tid=0x3cef3c30 nid=0xd4 runnable [0x3cf6f000..0x3
    cf6fdc0]
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:421)
    - locked <4fb6d10> (a java.net.PlainSocketImpl)
    at java.net.ServerSocket.implAccept(ServerSocket.java:243)
    at java.net.ServerSocket.accept(ServerSocket.java:222)
    at com.inprise.vbroker.IIOP.Listener.accept(Listener.java:102)
    at com.inprise.vbroker.orb.SocketSCM$ListenerThread.run(SocketSCM.java:3
    2)
    at java.lang.Thread.run(Thread.java:484)
    "AreYouAlive" daemon prio=5 tid=0x3cd1e520 nid=0x17a waiting on monitor [0x3ce2f
    000..0x3ce2fdc0]
    at java.lang.Object.wait(Native Method)
    - waiting on <4da7f58> (a com.inprise.vbroker.ds.DSUser$AreYouAlive)
    at com.inprise.vbroker.ds.DSUser$AreYouAlive.run(DSUser.java:115)
    - locked <4da7f58> (a com.inprise.vbroker.ds.DSUser$AreYouAlive)
    "DatagramThread" daemon prio=5 tid=0x3cd19af0 nid=0x138 runnable [0x3cdef000..0x
    3cdefdc0]
    at java.net.PlainDatagramSocketImpl.peek(Native Method)
    - locked <4da1a10> (a java.net.PlainDatagramSocketImpl)
    at java.net.DatagramSocket.receive(DatagramSocket.java:354)
    - locked <140c7130> (a java.net.DatagramPacket)
    - locked <4da19f8> (a java.net.DatagramSocket)
    at com.inprise.vbroker.ds.DSUser$DatagramThread.run(DSUser.java:157)
    "GarbageCollector" daemon prio=5 tid=0x3cb80100 nid=0x1a5 waiting on monitor [0x
    3ccaf000..0x3ccafdc0]
    at java.lang.Object.wait(Native Method)
    - waiting on <4bca9c0> (a com.inprise.vbroker.orb.GarbageCollector)
    at com.inprise.vbroker.orb.GarbageCollector.run(GarbageCollector.java:62
    - locked <4bca9c0> (a com.inprise.vbroker.orb.GarbageCollector)
    "ListenThread" prio=5 tid=0x3c57c310 nid=0x145 runnable [0x3c5df000..0x3c5dfdc0]
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:421)
    - locked <3533380> (a java.net.PlainSocketImpl)
    at java.net.ServerSocket.implAccept(ServerSocket.java:243)
    at java.net.ServerSocket.accept(ServerSocket.java:222)
    at weblogic.t3.srvr.ListenThread.run(ListenThread.java:286)
    "LDAPConnThread majestix.xyz.com:389" daemon prio=5 tid=0x3a20bc40 nid=0
    x110 runnable [0x3a29f000..0x3a29fdc0]
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:86)
    at java.io.BufferedInputStream.fill(BufferedInputStream.java:186)
    at java.io.BufferedInputStream.read(BufferedInputStream.java:204)
    - locked <3022d48> (a java.io.BufferedInputStream)
    at netscape.ldap.ber.stream.BERElement.getElement(BERElement.java:101)
    at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:420)
    "NBExecuteThread-1" daemon prio=5 tid=0x38283ed0 nid=0x1e0 waiting on monitor [0
    x388df000..0x388dfdc0]
    at java.lang.Object.wait(Native Method)
    - waiting on <2f0a498> (a weblogic.kernel.ExecuteThread)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    - locked <2f0a498> (a weblogic.kernel.ExecuteThread)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "NBExecuteThread-0" daemon prio=5 tid=0x38281180 nid=0x1ca waiting on monitor [0
    x3889f000..0x3889fdc0]
    at java.lang.Object.wait(Native Method)
    - waiting on <2f09ea8> (a weblogic.kernel.ExecuteThread)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    - locked <2f09ea8> (a weblogic.kernel.ExecuteThread)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-19" daemon prio=5 tid=0x3827f660 nid=0x1b1 runnable [0x3885f000..
    0x3885fdc0]
    at java.lang.StringBuffer.toString(StringBuffer.java:1068)
    at com.xyz.king.common.DiplomatBasicParser.parse(DiplomatBasicPa
    rser.java:78)
    at com.xyz.king.go.Tuvking.getExacgoatchFormat(Tuvking.java:56)
    at com.xyz.king.go.IndexerLocal.setExacgoatchKeys(IndexerLocal.j
    ava:72)
    at com.xyz.everest.integration.king.go.IndexerWLRMIImpl.setExact
    MatchKeys(IndexerWLRMIImpl.java:68)
    at com.xyz.everest.page.pageimport.PageImporter.createPageFromGx
    ml(PageImporter.java:464)
    at com.xyz.everest.page.pageimport.PageImporter.importSourcePage
    (PageImporter.java:231)
    at com.xyz.everest.page.pageimport.PageImporter.importPage(PageI
    mporter.java:152)
    at com.xyz.everest.page.PageManagerLocal.importPage(PageManagerL
    ocal.java:340)
    at com.xyz.everest.page.PageManagerWLRMIImpl.importPage(PageMana
    gerWLRMIImpl.java:254)
    at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
    ssLocalizationRequest(RequestProcessor.java:168)
    at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
    ssRequest(RequestProcessor.java:65)
    at com.xyz.everest.jobhandler.jobcreation.JobCreatorLocal.addReq
    uestToJob(JobCreatorLocal.java:89)
    at com.xyz.everest.jobhandler.jobcreation.JobCreatorWLRMIImpl.ad
    dRequestToJob(JobCreatorWLRMIImpl.java:41)
    at com.xyz.everest.request.RequestHandlerLocal.submitRequest(Req
    uestHandlerLocal.java:423)
    at com.xyz.everest.request.RequestHandlerLocal.onMessage(Request
    HandlerLocal.java:192)
    at weblogic.jms.client.JMSMessageConsumer.run(JMSMessageConsumer.java:27
    6)
    at weblogic.jms.client.JMSSession.run(JMSSession.java:342)
    at weblogic.jms.server.JMSServerSession.execute(JMSServerSession.java:44
    - locked <72e2d18> (a weblogic.jms.server.JMSServerSession)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    "ExecuteThread-18" daemon prio=5 tid=0x3827e850 nid=0x170 waiting on monitor [0x
    3881f000..0x3881fdc0]
    at java.lang.Object.wait(Native Method)
    - waiting on <2f08db0> (a weblogic.kernel.ExecuteThread)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    - locked <2f08db0> (a weblogic.kernel.ExecuteThread)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-17" daemon prio=5 tid=0x3827da10 nid=0x1e9 runnable [0x387df000..
    0x387dfdc0]
    at java.lang.StringBuffer.expandCapacity(StringBuffer.java:202)
    at java.lang.StringBuffer.append(StringBuffer.java:401)
    - locked <140f83b0> (a java.lang.StringBuffer)
    at com.xyz.king.common.DiplomatBasicParser.parse(DiplomatBasicPa
    rser.java:78)
    at com.xyz.king.go.Tuvking.getExacgoatchFormat(Tuvking.java:56)
    at com.xyz.king.go.IndexerLocal.setExacgoatchKeys(IndexerLocal.j
    ava:72)
    at com.xyz.everest.integration.king.go.IndexerWLRMIImpl.setExact
    MatchKeys(IndexerWLRMIImpl.java:68)
    at com.xyz.everest.page.pageimport.PageImporter.createPageFromGx
    ml(PageImporter.java:464)
    at com.xyz.everest.page.pageimport.PageImporter.importSourcePage
    (PageImporter.java:231)
    at com.xyz.everest.page.pageimport.PageImporter.importPage(PageI
    mporter.java:152)
    at com.xyz.everest.page.PageManagerLocal.importPage(PageManagerL
    ocal.java:340)
    at com.xyz.everest.page.PageManagerWLRMIImpl.importPage(PageMana
    gerWLRMIImpl.java:254)
    at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
    ssLocalizationRequest(RequestProcessor.java:168)
    at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
    ssRequest(RequestProcessor.java:65)
    at com.xyz.everest.jobhandler.jobcreation.JobCreatorLocal.addReq
    uestToJob(JobCreatorLocal.java:89)
    at com.xyz.everest.jobhandler.jobcreation.JobCreatorWLRMIImpl.ad
    dRequestToJob(JobCreatorWLRMIImpl.java:41)
    at com.xyz.everest.request.RequestHandlerLocal.submitRequest(Req
    uestHandlerLocal.java:423)
    at com.xyz.everest.request.RequestHandlerLocal.onMessage(Request
    HandlerLocal.java:192)
    at weblogic.jms.client.JMSMessageConsumer.run(JMSMessageConsumer.java:27
    6)
    at weblogic.jms.client.JMSSession.run(JMSSession.java:342)
    at weblogic.jms.server.JMSServerSession.execute(JMSServerSession.java:44
    - locked <6e04bf0> (a weblogic.jms.server.JMSServerSession)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    "ExecuteThread-16" daemon prio=5 tid=0x3827cc20 nid=0x1c8 runnable [0x3879f000..
    0x3879fdc0]
    at org.apache.regexp.RECompiler.closure(RECompiler.java:939)
    at org.apache.regexp.RECompiler.branch(RECompiler.java:1151)
    at org.apache.regexp.RECompiler.expr(RECompiler.java:1203)
    at org.apache.regexp.RECompiler.compile(RECompiler.java:1281)
    at org.apache.regexp.RE.<init>(RE.java:495)
    at com.xyz.king.common.Entities.decodeString(Entities.java:128)
    at com.xyz.king.common.XmlEntities.decodeStringBasic(XmlEntities
    .java:130)
    at com.xyz.king.go.Tuvking$ExacgoatchFormatHandler.handleText(Tu
    vking.java:264)
    at com.xyz.king.common.DiplomatBasicParser.processText(DiplomatB
    asicParser.java:196)
    at com.xyz.king.common.DiplomatBasicParser.parse(DiplomatBasicPa
    rser.java:85)
    at com.xyz.king.go.Tuvking.getExacgoatchFormat(Tuvking.java:56)
    at com.xyz.king.go.IndexerLocal.setExacgoatchKeys(IndexerLocal.j
    ava:72)
    at com.xyz.everest.integration.king.go.IndexerWLRMIImpl.setExact
    MatchKeys(IndexerWLRMIImpl.java:68)
    at com.xyz.everest.page.pageimport.PageImporter.createPageFromGx
    ml(PageImporter.java:464)
    at com.xyz.everest.page.pageimport.PageImporter.importSourcePage
    (PageImporter.java:231)
    at com.xyz.everest.page.pageimport.PageImporter.importPage(PageI
    mporter.java:152)
    at com.xyz.everest.page.PageManagerLocal.importPage(PageManagerL
    ocal.java:340)
    at com.xyz.everest.page.PageManagerWLRMIImpl.importPage(PageMana
    gerWLRMIImpl.java:254)
    at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
    ssLocalizationRequest(RequestProcessor.java:168)
    at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
    ssRequest(RequestProcessor.java:65)
    at com.xyz.everest.jobhandler.jobcreation.JobCreatorLocal.addReq
    uestToJob(JobCreatorLocal.java:89)
    at com.xyz.everest.jobhandler.jobcreation.JobCreatorWLRMIImpl.ad
    dRequestToJob(JobCreatorWLRMIImpl.java:41)
    at com.xyz.everest.request.RequestHandlerLocal.submitRequest(Req
    uestHandlerLocal.java:423)
    at com.xyz.everest.request.RequestHandlerLocal.onMessage(Request
    HandlerLocal.java:192)
    at weblogic.jms.client.JMSMessageConsumer.run(JMSMessageConsumer.java:27
    6)
    at weblogic.jms.client.JMSSession.run(JMSSession.java:342)
    at weblogic.jms.server.JMSServerSession.execute(JMSServerSession.java:44
    - locked <6805850> (a weblogic.jms.server.JMSServerSession)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    "ExecuteThread-15" daemon prio=5 tid=0x3827be10 nid=0x1a0 runnable [0x3875f000..
    0x3875fdc0]
    at java.lang.StringBuffer.<init>(StringBuffer.java:116)
    at java.lang.StringBuffer.<init>(StringBuffer.java:104)
    at com.xyz.king.common.DiplomatBasicParser.parse(DiplomatBasicPa
    rser.java:91)
    at com.xyz.king.go.Tuvking.getExacgoatchFormat(Tuvking.java:56)
    at com.xyz.king.go.IndexerLocal.setExacgoatchKeys(IndexerLocal.j
    ava:72)
    at com.xyz.everest.integration.king.go.IndexerWLRMIImpl.setExact
    MatchKeys(IndexerWLRMIImpl.java:68)
    at com.xyz.everest.page.pageimport.PageImporter.createPageFromGx
    ml(PageImporter.java:464)
    at com.xyz.everest.page.pageimport.PageImporter.importSourcePage
    (PageImporter.java:231)
    at com.xyz.everest.page.pageimport.PageImporter.importPage(PageI
    mporter.java:152)
    at com.xyz.everest.page.PageManagerLocal.importPage(PageManagerL
    ocal.java:340)
    at com.xyz.everest.page.PageManagerWLRMIImpl.importPage(PageMana
    gerWLRMIImpl.java:254)
    at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
    ssLocalizationRequest(RequestProcessor.java:168)
    at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
    ssRequest(RequestProcessor.java:65)
    at com.xyz.everest.jobhandler.jobcreation.JobCreatorLocal.addReq
    uestToJob(JobCreatorLocal.java:89)
    at com.xyz.everest.jobhandler.jobcreation.JobCreatorWLRMIImpl.ad
    dRequestToJob(JobCreatorWLRMIImpl.java:41)
    at com.xyz.everest.request.RequestHandlerLocal.submitRequest(Req
    uestHandlerLocal.java:423)
    at com.xyz.everest.request.RequestHandlerLocal.onMessage(Request
    HandlerLocal.java:192)
    at weblogic.jms.client.JMSMessageConsumer.run(JMSMessageConsumer.java:27
    6)
    at weblogic.jms.client.JMSSession.run(JMSSession.java:342)
    at weblogic.jms.server.JMSServerSession.execute(JMSServerSession.java:44
    - locked <7e02b88> (a weblogic.jms.server.JMSServerSession)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    "ExecuteThread-14" daemon prio=5 tid=0x38279020 nid=0x139 runnable [0x3871f000..
    0x3871fdc0]
    at oracle.net.ns.NetInputStream.read(Unknown Source)
    at oracle.jdbc.ttc7.MAREngine.unmarshalUB1(MAREngine.java:718)
    at oracle.jdbc.ttc7.TTIoer.unmarshal(TTIoer.java:129)
    at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:533)
    at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1405)
    at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:822
    - locked <2f22908> (a oracle.jdbc.ttc7.TTC7Protocol)
    at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.ja
    va:1446)
    at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.jav
    a:1371)
    at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStateme
    nt.java:1900)
    at oracle.jdbc.driver.OracleStatement.executeUpdate(OracleStatement.java
    :693)
    - locked <140d4428> (a oracle.jdbc.driver.OracleStatement)
    at weblogic.jdbc.pool.Statement.executeUpdate(Statement.java:59)
    at weblogic.jms.server.JDBCStore.purgeMessages(JDBCStore.java:1147)
    at weblogic.jms.server.JDBCStore.trigger(JDBCStore.java:880)
    at weblogic.time.common.internal.ScheduledTrigger.executeLocally(Schedul
    edTrigger.java:205)
    at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigg
    er.java:199)
    at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:6
    0)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    "ExecuteThread-13" daemon prio=5 tid=0x38278190 nid=0x1d1 runnable [0x386df000..
    0x386dfdc0]
    at java.lang.StringBuffer.toString(StringBuffer.java:1068)
    at com.xyz.king.common.DiplomatBasicParser.parse(DiplomatBasicPa
    rser.java:91)
    at com.xyz.king.go.Tuvking.getExacgoatchFormat(Tuvking.java:56)
    at com.xyz.king.go.IndexerLocal.setExacgoatchKeys(IndexerLocal.j
    ava:72)
    at com.xyz.everest.integration.king.go.IndexerWLRMIImpl.setExact
    MatchKeys(IndexerWLRMIImpl.java:68)
    at com.xyz.everest.page.pageimport.PageImporter.createPageFromGx
    ml(PageImporter.java:464)
    at com.xyz.everest.page.pageimport.PageImporter.importSourcePage
    (PageImporter.java:231)
    at com.xyz.everest.page.pageimport.PageImporter.importPage(PageI
    mporter.java:152)
    at com.xyz.everest.page.PageManagerLocal.importPage(PageManagerL
    ocal.java:340)
    at com.xyz.everest.page.PageManagerWLRMIImpl.importPage(PageMana
    gerWLRMIImpl.java:254)
    at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
    ssLocalizationRequest(RequestProcessor.java:168)
    at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
    ssRequest(RequestProcessor.java:65)
    at com.xyz.everest.jobhandler.jobcreation.JobCreatorLocal.addReq
    uestToJob(JobCreatorLocal.java:89)
    at com.xyz.everest.jobhandler.jobcreation.JobCreatorWLRMIImpl.ad
    dRequestToJob(JobCreatorWLRMIImpl.java:41)
    at com.xyz.everest.request.RequestHandlerLocal.submitRequest(Req
    uestHandlerLocal.java:423)
    at com.xyz.everest.request.RequestHandlerLocal.onMessage(Request
    HandlerLocal.java:192)
    at weblogic.jms.client.JMSMessageConsumer.run(JMSMessageConsumer.java:27
    6)
    at weblogic.jms.client.JMSSession.run(JMSSession.java:342)
    at weblogic.jms.server.JMSServerSession.execute(JMSServerSession.java:44
    - locked <64dbad0> (a weblogic.jms.server.JMSServerSession)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    "ExecuteThread-12" daemon prio=5 tid=0x38277660 nid=0x1d9 runnable [0x3869f000..
    0x3869fdc0]
    at weblogic.socket.NTSockegouxer.getNextSocket(Native Method)
    at weblogic.socket.NTSockegouxer.processSockets(NTSockegouxer.java:331)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:
    23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    "ExecuteThread-11" daemon prio=5 tid=0x38276850 nid=0x12e runnable [0x3865f000..
    0x3865fdc0]
    at weblogic.socket.NTSockegouxer.getNextSocket(Native Method)
    at weblogic.socket.NTSockegouxer.processSockets(NTSockegouxer.java:331)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:
    23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    "ExecuteThread-10" daemon prio=5 tid=0x38275a10 nid=0xce runnable [0x3861f000..0
    x3861fdc0]
    at org.apache.regexp.RECompiler$RERange.<init>(RECompiler.java:1305)
    at org.apache.regexp.RECompiler.characterClass(RECompiler.java:572)
    at org.apache.regexp.RECompiler.terminal(RECompiler.java:863)
    at org.apache.regexp.RECompiler.closure(RECompiler.java:942)
    at org.apache.regexp.RECompiler.branch(RECompiler.java:1151)
    at org.apache.regexp.RECompiler.expr(RECompiler.java:1203)
    at org.apache.regexp.RECompiler.compile(RECompiler.java:1281)
    at org.apache.regexp.RE.<init>(RE.java:495)
    at com.xyz.king.common.Entities.decodeString(Entities.java:128)
    at com.xyz.king.common.XmlEntities.decodeStringBasic(XmlEntities
    .java:130)
    at com.xyz.king.go.Tuvking$ExacgoatchFormatHandler.handleText(Tu
    vking.java:264)
    at com.xyz.king.common.DiplomatBasicParser.processText(DiplomatB
    asicParser.java:196)
    at com.xyz.king.common.DiplomatBasicParser.parse(DiplomatBasicPa
    rser.java:85)
    at com.xyz.king.go.Tuvking.getExacgoatchFormat(Tuvking.java:56)
    at com.xyz.king.go.IndexerLocal.setExacgoatchKeys(IndexerLocal.j
    ava:72)
    at com.xyz.everest.integration.king.go.IndexerWLRMIImpl.setExact
    MatchKeys(IndexerWLRMIImpl.java:68)
    at com.xyz.everest.page.pageimport.PageImporter.createPageFromGx
    ml(PageImporter.java:464)
    at com.xyz.everest.page.pageimport.PageImporter.importSourcePage
    (PageImporter.java:231)
    at com.xyz.everest.page.pageimport.PageImporter.importPage(PageI
    mporter.java:152)
    at com.xyz.everest.page.PageManagerLocal.importPage(PageManagerL
    ocal.java:340)
    at com.xyz.everest.page.PageManagerWLRMIImpl.importPage(PageMana
    gerWLRMIImpl.java:254)
    at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
    ssLocalizationRequest(RequestProcessor.java:168)
    at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
    ssRequest(RequestProcessor.java:65)
    at com.xyz.everest.jobhandler.jobcreation.JobCreatorLocal.addReq
    uestToJob(JobCreatorLocal.java:89)
    at com.xyz.everest.jobhandler.jobcreation.JobCreatorWLRMIImpl.ad
    dRequestToJob(JobCreatorWLRMIImpl.java:41)
    at com.xyz.everest.request.RequestHandlerLocal.submitRequest(Req
    uestHandlerLocal.java:423)
    at com.xyz.everest.request.RequestHandlerLocal.onMessage(Request
    HandlerLocal.java:192)
    at weblogic.jms.client.JMSMessageConsumer.run(JMSMessageConsumer.java:27
    6)
    at weblogic.jms.client.JMSSession.run(JMSSession.java:342)
    at weblogic.jms.server.JMSServerSession.execute(JMSServerSession.java:44
    - locked <7828f40> (a weblogic.jms.server.JMSServerSession)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    "ExecuteThread-9" daemon prio=5 tid=0x38274c20 nid=0x15c runnable [0x385df000..0
    x385dfdc0]
    at java.lang.Object.clone(Native Method)
    at weblogic.utils.collections.NumericHashtable.clone(NumericHashtable.ja
    va:267)
    - locked <353a790> (a weblogic.utils.collections.NumericHashtable)
    at weblogic.socket.NTSockegouxer.trigger(NTSockegouxer.java:107)
    at weblogic.time.common.internal.ScheduledTrigger.executeLocally(Schedul
    edTrigger.java:205)
    at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigg
    er.java:199)
    at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:6
    0)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    "ExecuteThread-8" daemon prio=5 tid=0x38273e10 nid=0x14b runnable [0x3859f000..0
    x3859fdc0]
    at oracle.jdbc.ttc7.MAREngine.unmarshalUB4(MAREngine.java:845)
    at oracle.jdbc.ttc7.MAREngine.unmarshalSWORD(MAREngine.java:946)
    at oracle.jdbc.ttc7.TTIoer.unmarshal(TTIoer.java:128)
    at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:533)
    at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1405)
    at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteDescribe(TTC7Protocol.java:
    643)
    - locked <13bd83a8> (a oracle.jdbc.ttc7.TTC7Protocol)
    at oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleStatement.jav
    a:1674)
    at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStateme
    nt.java:1870)
    at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:737)
    - locked <140e56f8> (a oracle.jdbc.driver.OracleStatement)
    at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:6
    88)
    - locked <13bcc130> (a weblogic.jdbc.common.internal.ConnectionEnv)
    at weblogic.common.internal.ResourceAllocator.trigger(ResourceAllocator.
    java:1484)
    at weblogic.time.common.internal.ScheduledTrigger.executeLocally(Schedul
    edTrigger.java:205)
    at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigg
    er.java:199)
    at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:6
    0)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    "ExecuteThread-7" daemon prio=5 tid=0x38271020 nid=0x164 runnable [0x3855f000..0
    x3855fdc0]
    at java.lang.StringBuffer.expandCapacity(StringBuffer.java:202)
    at java.lang.StringBuffer.append(StringBuffer.java:401)
    - locked <140f8450> (a java.lang.StringBuffer)
    at com.xyz.king.common.DiplomatBasicParser.parse(DiplomatBasicPa
    rser.java:78)
    at com.xyz.king.go.Tuvking.getExacgoatchFormat(Tuvking.java:56)
    at com.xyz.king.go.IndexerLocal.setExacgoatchKeys(IndexerLocal.j
    ava:72)
    at com.xyz.everest.integration.king.go.IndexerWLRMIImpl.setExact
    MatchKeys(IndexerWLRMIImpl.java:68)
    at com.xyz.everest.page.pageimport.PageImporter.createPageFromGx
    ml(PageImporter.java:464)
    at com.xyz.everest.page.pageimport.PageImporter.importSourcePage
    (PageImporter.java:231)
    at com.xyz.everest.page.pageimport.PageImporter.importPage(PageI
    mporter.java:152)
    at com.xyz.everest.page.PageManagerLocal.importPage(PageManagerL
    ocal.java:340)
    at com.xyz.everest.page.PageManagerWLRMIImpl.importPage(PageMana
    gerWLRMIImpl.java:254)
    at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
    ssLocalizationRequest(RequestProcessor.java:168)
    at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
    ssRequest(RequestProcessor.java:65)
    at com.xyz.everest.jobhandler.jobcreation.JobCreatorLocal.addReq
    uestToJob(JobCreatorLocal.java:89)
    at com.xyz.everest.jobhandler.jobcreation.JobCreatorWLRMIImpl.ad
    dRequestToJob(JobCreatorWLRMIImpl.java:41)
    at com.xyz.everest.request.RequestHandlerLocal.submitRequest(Req
    uestHandlerLocal.java:423)
    at com.xyz.everest.request.RequestHandlerLocal.onMessage(Request
    HandlerLocal.java:192)
    at weblogic.jms.client.JMSMessageConsumer.run(JMSMessageConsumer.java:27
    6)
    at weblogic.jms.client.JMSSession.run(JMSSession.java:342)
    at weblogic.jms.server.JMSServerSession.execute(JMSServerSession.java:44
    - locked <8ebc3e8> (a weblogic.jms.server.JMSServerSession)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    "ExecuteThread-6" daemon prio=5 tid=0x38270190 nid=0x142 runnable [0x3851f000..0
    x3851fdc0]
    at java.lang.StringBuffer.<init>(StringBuffer.java:116)
    at java.lang.StringBuffer.<init>(StringBuffer.java:104)
    at com.xyz.king.common.DiplomatBasicParser.processTag(DiplomatBa
    sicParser.java:154)
    at com.xyz.king.common.DiplomatBasicParser.parse(DiplomatBasicPa
    rser.java:72)
    at com.xyz.king.go.Tuvking.getExacgoatchFormat(Tuvking.java:56)
    at com.xyz.king.go.IndexerLocal.setExacgoatchKeys(IndexerLocal.j
    ava:72)
    at com.xyz.everest.integration.king.go.IndexerWLRMIImpl.setExact
    MatchKeys(IndexerWLRMIImpl.java:68)
    at com.xyz.everest.page.pageimport.PageImporter.createPageFromGx
    ml(PageImporter.java:464)
    at com.xyz.everest.page.pageimport.PageImporter.importSourcePage
    (PageImporter.java:231)
    at com.xyz.everest.page.pageimport.PageImporter.importPage(PageI
    mporter.java:152)
    at com.xyz.everest.page.PageManagerLocal.importPage(PageManagerL
    ocal.java:340)
    at com.xyz.everest.page.PageManagerWLRMIImpl.importPage(PageMana
    gerWLRMIImpl.java:254)
    at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
    ssLocalizationRequest(RequestProcessor.java:168)
    at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
    ssRequest(RequestProcessor.java:65)
    at com.xyz.everest.jobhandler.jobcreation.JobCreatorLocal.addReq
    uestToJob(JobCreatorLocal.java:89)
    at com.xyz.everest.jobhandler.jobcreation.JobCreatorWLRMIImpl.ad
    dRequestToJob(JobCreatorWLRMIImpl.java:41)
    at com.xyz.everest.request.RequestHandlerLocal.submitRequest(Req
    uestHandlerLocal.java:423)
    at com.xyz.everest.request.RequestHandlerLocal.onMessage(Request
    HandlerLocal.java:192)
    at weblogic.jms.client.JMSMessageConsumer.run(JMSMessageConsumer.java:27
    6)
    at weblogic.jms.client.JMSSession.run(JMSSession.java:342)
    at weblogic.jms.server.JMSServerSession.execute(JMSServerSession.java:44
    - locked <9dab220> (a weblogic.jms.server.JMSServerSession)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    "ExecuteThread-5" daemon prio=5 tid=0x3826f610 nid=0x14a runnable [0x384df000..0
    x384dfdc0]
    at java.lang.StringBuffer.expandCapacity(StringBuffer.java:202)
    at java.lang.StringBuffer.append(StringBuffer.java:401)
    - locked <140f84f8> (a java.lang.StringBuffer)
    at com.xyz.king.common.DiplomatBasicParser.parse(DiplomatBasicPa
    rser.java:91)
    at com.xyz.king.go.Tuvking.getExacgoatchFormat(Tuvking.java:56)
    at com.xyz.king.go.IndexerLocal.setExacgoatchKeys(IndexerLocal.j
    ava:72)
    at com.xyz.everest.integration.king.go.IndexerWLRMIImpl.setExact
    MatchKeys(IndexerWLRMIImpl.java:68)
    at com.xyz.everest.page.pageimport.PageImporter.createPageFromGx
    ml(PageImporter.java:464)
    at com.xyz.everest.page.pageimport.PageImporter.importSourcePage
    (PageImporter.java:231)
    at com.xyz.everest.page.pageimport.PageImporter.importPage(PageI
    mporter.java:152)
    at com.xyz.everest.page.PageManagerLocal.importPage(PageManagerL
    ocal.java:340)
    at com.xyz.everest.page.PageManagerWLRMIImpl.importPage(PageMana
    gerWLRMIImpl.java:254)
    at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
    ssLocalizationRequest(RequestProcessor.java:168)
    at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
    ssRequest(RequestProcessor.java:65)
    at com.xyz.everest.jobhandler.jobcreation.JobCreatorLocal.addReq
    uestToJob(JobCreatorLocal.java:89)
    at com.xyz.everest.jobhandler.jobcreation.JobCreatorWLRMIImpl.ad
    dRequestToJob(JobCreatorWLRMIImpl.java:41)
    at com.xyz.everest.request.RequestHandlerLocal.submitRequest(Req
    uestHandlerLocal.java:423)
    at com.xyz.everest.request.RequestHandlerLocal.onMessage(Request
    HandlerLocal.java:192)
    at weblogic.jms.client.JMSMessageConsumer.run(JMSMessageConsumer.java:27
    6)
    at weblogic.jms.client.JMSSession.run(JMSSession.java:342)
    at weblogic.jms.server.JMSServerSession.execute(JMSServerSession.java:44
    - locked <84612a8> (a weblogic.jms.server.JMSServerSession)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    "ExecuteThread-4" daemon prio=5 tid=0x3826e820 nid=0x1fb waiting on monitor [0x3
    849f000..0x3849fdc0]
    at java.lang.Object.wait(Native Method)
    - waiting on <2f03bc0> (a weblo

  • JMS on Remote WLS Domain

    Hi,
    I have been using Foreign JMS/Message Bridge to access the JMS Queues from Remote WLS domain.
    Is there any way to access JMS queue from remote domain (Same Weblogic version 10.3) without using Foreign JMS/Message Bridge.
    Thanks in Advance !!

    See the [url http://download.oracle.com/docs/cd/E14571_01/web.1111/e13727/interop.htm#JMSPG553]Integrating Remote JMS Providers FAQ.

  • Migrating JMS Persistence from WLS 4.5.2  to WLS 6.1

    Hi,
    we are migrating several applications from WLS 4.5.2 to WLS 6.1. A application use
    JMS with persistence in DB (JMS persistence WLS 4.5.2 is in DB) with WLS 6.1 we want
    to change persistence mode to FIles. Therefore during migration process we have to
    move the messages stored in the database to a file. The messages stored in the file
    will be recovered for WLS 6.1.
    My doubt is, Is there a automatic process for migrate messages in the DB to a persistence
    file?
    Thanks

    Hi.
    I'm not sure that there is an automatic process to accomplish this, but you might get a
    better answer by posting this on the JMS newsgroup.
    Regards,
    Michael
    Manuel Villalta wrote:
    Hi,
    we are migrating several applications from WLS 4.5.2 to WLS 6.1. A application use
    JMS with persistence in DB (JMS persistence WLS 4.5.2 is in DB) with WLS 6.1 we want
    to change persistence mode to FIles. Therefore during migration process we have to
    move the messages stored in the database to a file. The messages stored in the file
    will be recovered for WLS 6.1.
    My doubt is, Is there a automatic process for migrate messages in the DB to a persistence
    file?
    Thanks--
    Michael Young
    Developer Relations Engineer
    BEA Support

  • JMS Persistence with WLS 8.1SP3 in a cluster

    I have been following the BEA recommendations. I have configured my JMS to write to an Oracle DB for JMS persistence. This is in a clustered environment. I have had one server go down and then come back. During the outage or right before the outage there were request in the JMS queue. I would assume when the server that failed came back up it would then receive and process the JMS request that were waiting in the DB. That doesn't seem to be happening. My setup is one JMS topic for out bound. The JMS queue is set up for internal traffic. It uses Message Beans. We are also using XADrivers.
              The setup is WLS8.1SP3 on Solaris hitting an Oracle 9 db. Please forward me any questions or suggestions. Thank you in advance.

    WebLogic JMS won't automatically recover messages that enter an "in-doubt" state due to persistence errors that occur while they are being sent or received. To recover such messages, JMS needs to be restarted. You can contact customer support for an 8.1 sample program that automatically restarts JMS (without restarting all of WebLogic) when this problem occurs.
              Tom

  • JMS in Clustered WLS 5.1

              Has anyone used JMS in a 5.1 cluster ? I'm not able to lookup Topics from my client.
              Can someone help me with this ?
              

    Currently JMS Topics are not replicable objects in a cluster; you must bind it to a single Node.
              Once a Node has a bound Topic and joins a cluster, its local JNDI tree is broadcasted to the rest of
              the cluster, and you should be able to look up the local Topic from any Node. What problems are you
              having?
              Gene
              "Ashok Sridhar" <[email protected]> wrote in message news:3b2f6bb0$[email protected]..
              >
              > Has anyone used JMS in a 5.1 cluster ? I'm not able to lookup Topics from my client.
              > Can someone help me with this ?
              >
              >
              

  • Using a  foreign WLS JMS queue (no bridge)

              Hi,
              We have a configuration from which we communicate from WLS 7 to a foreign MQ via
              JMS. This works well and we have loaded the foreign MQ jms objects into WLS JNDI
              using a statup class (as the whitepaper available describes) and we look them
              up successfully.
              However, we now have a siutation where we briefly need to switch our application
              to point to a WLS JMS queue on another remote WLS server. Is there an easy way
              to load foreign (maybe remote would be a better word in this case) WLS JMS QCF's
              and destinations into my local WLS JNDI so that I can treat them the same way
              as my MQ objects?
              I can't seem to find any information on how to do this as all information seems
              to point towards the messaging bridge (we can't use this as the bridge changes
              the message JMSMessageID and screws our correlation mechanism up).
              I know we could just look the foreign objects up by using the JNDI environment
              of the remote WLS machine but this would mean changing code and this I can't to
              do (as all our code uses the local default WLS JNDI).
              Any ideas would be gratefully received.
              Cheers,
              Jay.
              

    WLS JMS and MQ JMS handle their JNDI objects a little differently, so I can
              see how this can be confusing. An MQ JMS "ConnectionFactory" or
              "Destination" object is like a little configuration file that tells you
              where the queue manager or queue is, so you can serialize it and look it up
              later and use it to find the queue manager.
              A WLS JMS ConnectionFactory or Destination object is a reference to an
              object on a running server. So, you connect to the server and look them up,
              and then you can use it for messaging. You don't have to store these objects
              in a separate place, like MQ makes you do. But it means that the WLS JNDI
              objects have to be looked up from a running server, and if the server
              restarts, you have to look them up again.
              Doing what you're asking is definitely trickier in 7.0. One thing you could
              do is, again using a servlet or an EJB, connect to the remote JMS cluster
              and look up the objects at the time you want to make the switch. (If the
              remote cluster is down, you'll have to retry from time to time.) If the
              remote cluster is down, you won't be able to look up those objects, but then
              again, if it were down you wouldn't be able to send messages there anyway.
              Using 8.1 would be less complicated, but this method should also work.
              greg
              "Jay Green" <[email protected]> wrote in message
              news:[email protected]...
              >
              > Thanks Greg. When I was searching the BEA website I read about the
              facility in
              > 8.1. Unfortunatley, as you point out, it doesn't help me much with WLS
              7.0.
              >
              > My first thought was to copy my exisiting MQ startup class but I couldn't
              work
              > out how to do this for the remote WLS jms objects as the standard jms
              classes
              > (for QCF etc) don't have methods that allow me to define the foreign WLS
              jms
              > host IP address etc. I checked the WLS 7 API and the jms package didn't
              seem
              > to offer anything to help me do this (as IBM do for MQ). Any ideas?
              >
              > Apologies if I'm being a bit slow here!
              >
              > "Greg Brail" <[email protected]> wrote:
              > >WLS 8.1 includes a feature called "Foreign JMS Providers" that lets you
              > >configure (using the console or config.xml) a link between a JMS JNDI
              > >object
              > >in your WLS servers' tree, and a JNDI object in another provider -- which
              > >could be WLS JMS, or a foreign vendor.
              > >
              > >Using this feature, your application could just look up the local JNDI
              > >objects in the local WLS tree, and then the server in turn performs the
              > >lookup from the actual JNDI provider using the parameters you put in
              > >the
              > >console (or config.xml). So, when you make a change in the console, new
              > >JNDI
              > >lookups will go to the new place.
              > >
              > >Unfortunately, this doesn't help you with 7.0. You could always
              > >programmitically update the local JNDI tree the way you're doing in your
              > >startup class, but instead do it from a servlet or an EJB.
              > >
              > > greg
              > >
              > >"Jay Green" <[email protected]> wrote in message
              > >news:[email protected]...
              > >>
              > >> Hi,
              > >>
              > >> We have a configuration from which we communicate from WLS 7 to a
              foreign
              > >MQ via
              > >> JMS. This works well and we have loaded the foreign MQ jms objects
              > >into
              > >WLS JNDI
              > >> using a statup class (as the whitepaper available describes) and we
              > >look
              > >them
              > >> up successfully.
              > >>
              > >> However, we now have a siutation where we briefly need to switch our
              > >application
              > >> to point to a WLS JMS queue on another remote WLS server. Is there
              > >an easy
              > >way
              > >> to load foreign (maybe remote would be a better word in this case)
              > >WLS JMS
              > >QCF's
              > >> and destinations into my local WLS JNDI so that I can treat them the
              > >same
              > >way
              > >> as my MQ objects?
              > >> I can't seem to find any information on how to do this as all
              information
              > >seems
              > >> to point towards the messaging bridge (we can't use this as the bridge
              > >changes
              > >> the message JMSMessageID and screws our correlation mechanism up).
              > >>
              > >> I know we could just look the foreign objects up by using the JNDI
              > >environment
              > >> of the remote WLS machine but this would mean changing code and this
              > >I
              > >can't to
              > >> do (as all our code uses the local default WLS JNDI).
              > >>
              > >> Any ideas would be gratefully received.
              > >>
              > >> Cheers,
              > >>
              > >> Jay.
              > >
              > >
              >
              

  • Problems in Sending Data through JMS Bridge - WLS 10.3 to WLS 11g

    I have a scenario where I need to send data from a queue configured on WLS 10.3 to WLS 11g. I am using OSB on WLS 10.3.
    What I have done is
    1. Created a JMS Based BS in OSB which sends data to jms://localhost:7001/ConnFactoryJNDI/QueueJNDI
    2. Created a JMS Bridge on WLS 10.3
    3. Source Destination has been configured as the one mentioned above.
    4. Target Destination has been configured to a queue on WLS 11g.
    When i execute the JMS Based BS in OSB, data is being written to the Source Queue directly. I am not sure of the JMS Bridge functionality but I assume that once data is written to the Source Destination, that data will be automatically pushed on the target destination.
    I have configured a JDBC store for the target queue but I no table is created with the data sent from the source.
    M i missing something here?

    I think this question belongs to weblogic server, but as far as I know bridge should be created always at higher version. means, you should create bridge at 11g and try to pull/drop data from 10g. To check any errors in bridge, check the server log and make sure status of bridge is "forwarding messages"
    Regards,
    Anuj

  • WLS 6.0 & WLCS 3.2 & interop between 5.1 & 6.0

    Hi,
    Apparently, WLCS 3.2 will support WLS 6.0 in spring (cf various posts). We
    are currently using WLS 5.1 for
    EJB dev & WLCS for JSP dev but wanted to migrate our EJB dev to WLS 6.0. Not
    possible !!! We thought of
    having two servers one for running WLCS 3.2 (5.1) and one for our EJB (6.0).
    Here it's a JNDI problem that
    make the thing impossible (no interop between 5.1 and 6.0).
    I find unacceptable that BEA delivers a new version of their server without
    upgrading at the same time all
    other applications running on top of that server (WLCS & WLPI). I find a lot
    more unacceptable the non interop between 5.1 and 6.0 !!!
    I evently tried to migrate WLCS 3.2 to WLS 6.0 (after all that should be
    possible as it's possible to migrate 5.1
    applications to 6.0) but got so many errors with EJB deployment that I will
    stop.
    Did anybody reach the same problem, did anybody succeed in migrating WLCS
    3.2 to WLS 6.0 ?
    Could BEA deliver a compatible version of WLCS 3.2 before "Spring" !!!! ?
    Thanks for any ideas,
    Olivier

    Hello Olivier,
    I am sorry that you are so frustrated by the lag between the WLS 6.0 release
    and WLCS certification on WLS 6.0. It is a large task and we want to do a
    thorough job to ensure the quality of our WLCS product.
    This spring we plan to release a top-quality personalization and commerce
    server that runs on the best application server in the world, just like we did
    with WLCS 3.2 on WLS 5.1 in December. I am confident in the technical
    superiority of WLCS over other personalization and commerce servers and I can
    assure you that our team puts a high priority on WLS 6.0 certification.
    If you have any problems using our products do not hesitate to contact our
    support team at http://www.bea.com/support/index.jsp . If you are not
    satisfied with any technical aspect of our product or our support, let me know.
    Ture Hoefner
    BEA Systems, Inc.
    2590 Pearl St.
    Suite 110
    Boulder, CO 80302
    www.bea.com

  • A trust between wls domains disables weblogic account

    Hi,
    I have a foreign jndi provider between two wls servers , the first is 10.3 and the second which has a foreign jndi provider to the first is 10.3.1
    I enabled Cross Domain Security Enabled and put the same password weblogic on these domains
    In 10.3.1 the user weblogic has weblogic1 as password.
    The 10.3.1 app works perfectly with the ejb's on 10.3 server
    but after a while I get this error User weblogic in security realm myrealm has had 5 invalid login attempts, locking account for 30 minutes.
    thanks Edwin

    Hi
    I already changed all password ( domain and weblogic account ) to weblogic1. but without results

  • Unable to Connect to JMS Queue in Websphere from WLS 10.3,3

    Hi Everyone,
    I'm trying to connect to JMS Queue in WebSphere 7.1 from WLS 10.3.3, I'm trying to using Foreign server connection to connect to the Websphere JMS Queue. Its normal Queue not MQ Queue. I have configured the Foreign server but i know for the fact that some weblogic jar files are need on the WLS home. Does anyone let me know what is needed so that i can place them on the WLS home and restart the server.
    Also i would like to consume and produce messages to the websphere queue.
    Thanks for the help..
    Regards
    Sabir

    Hi Everyone
    Has anyone tried connecting to the websphere jms queue from WLS 10.3.3
    Let me know if that can be done
    regards
    Sabir

Maybe you are looking for