Messaging Bridge Between 2 Weblogic Server

          Hi,
          I would like to create a messaging bridge between two Weblogic Server on two different
          server. One on Windows NT and one on Solaris.
          I have created one queue on NT and one other queue on Solaris, and the corresponding
          JMS Bridge destination for each queue on one server (and the other to test).
          And on one server (and the other to test), I have created a messaging bridge to
          transfert messages from one queue to the other, but I have a message on the Weblogic
          Server.
          javax.resource.spi.ResourceAllocationException: CreateManagedConnection Error:
          ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory,
          url = http://usv9007.rtc.ch:7001, user name = null, password = null
          at weblogic.connector.common.internal.ConnectionPool.makeResources(ConnectionPool.java:978)
          at weblogic.connector.common.internal.ConnectionPool.getConnection(ConnectionPool.java:1708)
          at weblogic.connector.common.internal.ConnectionPoolManager.getConnection(ConnectionPoolManager.java:163)
          at weblogic.connector.common.internal.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:25)
          at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseConnectionFactory.java:126)
          at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:733)
          at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:899)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
          <09.01.2003 13:48:51 CET> <Error> <Connector> <190006> <Error granting connection
          request.>
          Parameter for the distant queue
          Adapter JNDI Name : eis.jms.WLSConnectionFactoryJNDIXA (I have activated the XA
          ressources for the ConnectionFactory and the corresponding adapter)
          Connection URL : http://SolarisIP:7001
          InitialContextFactory : weblogic.jndi.WLInitialContextFactory
          ConnectionFactory JNDI Name : myConnectionFactory
          Destination JNDI Name : myQueueSolaris
          Destination Type : Queue
          I don't understand why I have this error, because all the parameters are correct,
          and the http tunneling is activated.
          Could you help me to configure correctly this messaging bridge ???
          Thanks a lot.
          

Looks like the error occurred on the target destination
          of the bridge. One way to find out if your configuration
          is correct is to use the same parameters (initial context factory,
          url, username and password) to get a connection to the
          target server from a standalone client.
          Dongbo
          Seb wrote:
          >
          > Hi,
          >
          > I would like to create a messaging bridge between two Weblogic Server on two different
          > server. One on Windows NT and one on Solaris.
          >
          > I have created one queue on NT and one other queue on Solaris, and the corresponding
          > JMS Bridge destination for each queue on one server (and the other to test).
          >
          > And on one server (and the other to test), I have created a messaging bridge to
          > transfert messages from one queue to the other, but I have a message on the Weblogic
          > Server.
          >
          > -----------------------------------------------------------------
          > javax.resource.spi.ResourceAllocationException: CreateManagedConnection Error:
          > ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory,
          > url = http://usv9007.rtc.ch:7001, user name = null, password = null
          > at weblogic.connector.common.internal.ConnectionPool.makeResources(ConnectionPool.java:978)
          > at weblogic.connector.common.internal.ConnectionPool.getConnection(ConnectionPool.java:1708)
          > at weblogic.connector.common.internal.ConnectionPoolManager.getConnection(ConnectionPoolManager.java:163)
          > at weblogic.connector.common.internal.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:25)
          > at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseConnectionFactory.java:126)
          > at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:733)
          > at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:899)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
          > <09.01.2003 13:48:51 CET> <Error> <Connector> <190006> <Error granting connection
          > request.>
          > -----------------------------------------------------------------
          >
          > Parameter for the distant queue
          >
          > Adapter JNDI Name : eis.jms.WLSConnectionFactoryJNDIXA (I have activated the XA
          > ressources for the ConnectionFactory and the corresponding adapter)
          > Connection URL : http://SolarisIP:7001
          > InitialContextFactory : weblogic.jndi.WLInitialContextFactory
          > ConnectionFactory JNDI Name : myConnectionFactory
          > Destination JNDI Name : myQueueSolaris
          > Destination Type : Queue
          >
          > I don't understand why I have this error, because all the parameters are correct,
          > and the http tunneling is activated.
          >
          > Could you help me to configure correctly this messaging bridge ???
          >
          > Thanks a lot.
          

Similar Messages

  • Unable to create a JMS Message bridge between Weblogic 12c and Weblogic 8.1

    Hi,
    I am unable to successfully create a Message Bridge between Weblogic 12.1.1.0 and Weblogic 8.1. The error message being received is:
    eis/jms/WLSConnectionFactoryJNDINoTX > ResourceAllocationException generated by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory, url = t3://localhost:8001, user name = System) ">
    The error on the monitoring tab is WARN: failed to connect to target.
    Both domains are deployed on one box for testing purposes. The bridge itself is deployed on Weblogic 12c. The areas of config that may be of interest are:
    <server>
    <name>AdminServer</name>
    <listen-address></listen-address>
    </server>
    <messaging-bridge>
    <name>Bridge</name>
    <target>AdminServer</target>
    <source-destination>JMSBridgeSource12c</source-destination>
    <target-destination>JMSBridgeTarget81</target-destination>
    <selector>Test</selector>
    <quality-of-service>Exactly-once</quality-of-service>
    <qos-degradation-allowed>false</qos-degradation-allowed>
    <durability-enabled>true</durability-enabled>
    <idle-time-maximum>60</idle-time-maximum>
    <async-enabled>true</async-enabled>
    <started>true</started>
    <preserve-msg-property>false</preserve-msg-property>
    </messaging-bridge>
    <app-deployment>
    <name>jms-xa-adp</name>
    <target>AdminServer</target>
    <module-type>rar</module-type>
    <source-path>D:\ORACLE~3\WLSERV~1.1\server\lib\jms-xa-adp.rar</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    </app-deployment>
    <jms-bridge-destination>
    <name>JMSBridgeSource12c</name>
    <adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDIXA</adapter-jndi-name>
    <user-name>System</user-name>
    <user-password-encrypted>{AES}nfFzhs+0J/O2Cenf0g4zDsDyvIKENMF7cZ5sAVUehX0=</user-password-encrypted>
    <classpath></classpath>
    <connection-factory-jndi-name>JMSConnectionFactory12c</connection-factory-jndi-name>
    <connection-url>t3://localhost:7001</connection-url>
    <destination-jndi-name>JMSQueue12c</destination-jndi-name>
    </jms-bridge-destination>
    <jms-bridge-destination>
    <name>JMSBridgeTarget81</name>
    <adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDIXA</adapter-jndi-name>
    <user-name>System</user-name>
    <user-password-encrypted>{AES}eBkO46cHvtrzEraOMIOdXow6WvEAtA4NCUDTQ4mC+9w=</user-password-encrypted>
    <classpath></classpath>
    <connection-factory-jndi-name>JMSConnectionFactory81</connection-factory-jndi-name>
    <connection-url>t3://localhost:8001</connection-url>
    <destination-jndi-name>JMSQueue81</destination-jndi-name>
    </jms-bridge-destination>
    I have enforced global trust between the two domains. I have disabled the guest user on the 8.1 domain but can’t see where to do this on 12c.
    Any suggestions would be much appreciated.
    Regards
    John
    Edited by: 958336 on 13-Sep-2012 03:11

    Thanks for the recommendation. Unfortunately it did not help solve the problem.
    I have managed to get a JMS bridge working between 12c and 8.1 by including the 8.1 weblogic.jar on the classpath. This setup was using eis.jms.WLSConnectionFactoryJNDINoTX.
    After trying to use the adapter that supports transactions, WLSConnectionFactoryJNDIXA I received the following error:
    java.lang.IllegalStateException: can only be called from server
    Is this because the Weblogic 12c server now views the 8.1 server as being foreign?

  • Message Bridge between WLS 6.1 sp3 and MQSeries 5.2

              Hi,
              I'm really struggling with getting the Message Bridge working with Weblogic 6.1
              sp3 and MQSeries 5.2. Currently I have both installed on the same Windows 2000
              machine. First I'll pose some questions that I have, then I discuss the error
              I'm getting. Here are my questions:
              1. With the jms-xa-adp.rar there is a ra.xml and a weblogic-ra.xml. Within the
              ra.xml deployment descriptor there are config-properties for ConnectionURL, InitialContextFactory,
              ConnectionFactoryJNDI, and DestinationType. If my MQSeries Queue is the source
              jms destination bridge and my weblogic queue is the target jms destination bridge,
              what values do I set for the listed config-properties? I can't seem to find any
              documentation on what these values should be. Am I missing something? Do these
              values even have to be set?
              2. When I go to install a Weblogic instance to a different physical machine what
              has to be installed in terms of MQSeries? So I'll have MQSeries on physical machineA
              and Weblogic on a different physical machineB. I want machineA to forward all
              messages placed on a MQSeries Queue to forward them to machineB where the weblogic
              Queue resides. Does machineB also have to contain an MQSeries installation?
              Or can I just grab the necessary libraries and jar files and place them on the
              Weblogic machineB so they can be included?
              3. Is it correct that if I distribute Weblogic onto one physical server and MQSeries
              onto a different physical server that I cannot use Exactly-once quality of service?
              Other notes:
              1. I have the following patches installed for Weblogic 6.1 sp3:
              CR081404_610sp3.jar
              CR081511_61sp3.jar
              2. Here is the commands I used to create my ConnectionFactory and Queue within
              MQSeries:
              def xaqcf(MQTestConnectionFactory) qmanager(QM_jeff)
              def q(MQTestQueue) qmanager(QM_jeff) queue(default)
              Okay...here is my error:
              <21-Aug-02 11:08:34 ADT AM> <Error> <MessagingBridge> <Error occurred in bridge
              "Messaging Bridge" during transferring messages (java.lang.Exception: java.lang.
              reflect.UndeclaredThrowableException: java.lang.reflect.InvocationTargetException:
              javax.resource.ResourceException: Error creating consumer or receiving message
              at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1086)
              at weblogic.jms.adapter.JMSBaseConnection.receiveInternal(JMSBaseConnection.java:774)
              at weblogic.jms.adapter.JMSBaseConnection.receiveCommon(JMSBaseConnection.java:656)
              at weblogic.jms.adapter.JMSBaseConnection.receive(JMSBaseConnection.java:811)
              at weblogic.jms.adapter.JMSConnectionHandle.receive(JMSConnectionHandle.java:111)
              at java.lang.reflect.Method.invoke(Native Method)
              at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:60)
              at $Proxy82.receive(Unknown Source)
              at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1215)
              at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:854)
              at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.
              Has anyone see this error before? Here is part of my ra.xml file....I just put
              these entries in to see what happens:
              <config-property>
              <config-property-name>ConnectionURL</config-property-name>
              <config-property-type>java.lang.String</config-property-type>
              <config-property value>file:/C:/Develop/app_servers/WebSphere/MQSeries</config-property-value>
              </config-property>
              <config-property>
              <config-property-name>InitialContextFactory</config-property-name>
              <config-property-type>java.lang.String</config-property-type>
              <config-property-value>com.sun.jndi.fscontext.RefFSContextFactory</config-property-value>
              </config-property>
              <config-property>
              <config-property-name>ConnectionFactoryJNDI</config-property-name>
              <config-property-type>java.lang.String</config-property-type>
              <config-property-value>MQTestConnectionFactory</config-property-value>
              </config-property>
              <config-property>
              <config-property-name>DestinationJNDI</config-property-name>
              <config-property-type>java.lang.String</config-property-type>
              <config-property-value>MQTestQueue</config-property-value>
              </config-property>
              <config-property>
              <config-property-name>DestinationType</config-property-name>
              <config-property-type>java.lang.String</config-property-type>
              <config-property-value></config-property-value>
              </config-property>
              <config-property>
              <config-property-name>AdapterType</config-property-name>
              <config-property-type>java.lang.String</config-property-type>
              <config-property-value>XATransaction</config-property-value>
              </config-property>
              Here is a snip of my config.xml:
              <MessagingBridge AsyncEnabled="false" DurabilityEnabled="false"
              Name="Messaging Bridge" QualityOfService="Atmost-once"
              SourceDestination="Source JMS Bridge Destination"
              TargetDestination="Target JMS Bridge Destination" Targets="myserver"/>
              <JMSBridgeDestination
              AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
              ConnectionFactoryJNDIName="MQTestConnectionFactory"
              ConnectionURL="file:/C:/Develop/app_servers/WebSphere/MQSeries"
              DestinationJNDIName="MQTestQueue" InitialContextFactory="com.sun.jndi.fscontext.RefFSContextFactory"
              Name="Source JMS Bridge Destination"/>
              <JMSBridgeDestination
              AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
              ConnectionFactoryJNDIName="imagictv.platform.ToolkitRequestCF"
              ConnectionURL="t3://localhost:7001"
              DestinationJNDIName="imagictv.platform.ToolkitRequestQueue"
              InitialContextFactory="weblogic.jndi.WLInitialContextFactory" Name="Target
              JMS Bridge Destination"/>
              Any help would be greatly appreciated. Thank you in advance for your help.
              Sincerely,
              Jeff
              

              I tried your suggestion and it worked!! The only thing is, it
              makes the deployment of the resource adapter a little more
              complicated. Now my customers are going to have to edit their
              config.xml, instead of just dropping in the appropriate rar into
              the applications directory. But one nice side affect of placing
              the rar's in a different directory is it makes the Message
              Bridge a little more stable. I was finding it to be very
              unstable. One time I would startup my Application Server and
              everything was fine, then I would shutdown. The next time I
              started it up, I would get exceptions. I have yet to see that
              behavior with this new configuration.
              Thanks again for all of your help, it is greatly appreciated!!
              Jeff
              Dongbo Xiao <[email protected]> wrote:
              >Looks like that somehow you have the adapter deployed
              >multiple times, may not be intended. The cause is that
              >everything in the application directory will be automatically
              >deployed and all of them are added to the config.xml. During
              >the next boot, those appear in the config.xml will be deployed and
              >everything in the application directory too. As a result, the adapters
              >are deployed twice. The complain about runtime mbean not found may
              >mean the one that is overridden by the new one.
              >
              >The work around is not to put your adapters in the application
              >directory, instead, put them in a different directory and point to
              >the directory in your config.xml.
              >
              >Dongbo
              >Jeff wrote:
              >>
              >> One more thing...
              >> I noticed that the exception specified that it couldn't find
              >> mydomain:Location=myserver,Name=jms-xa-
              >> adp_Pool_1,ServerRuntime=myserver,Type=ConnectorConnectionPoolRun
              >> time MBean, but what's interesting that if I run the following
              >> java weblogic.Admin GET -type ConnectorConnectionPoolRuntime -
              >> property ActiveConnectionsCurrentCount -url
              >> http://localhost:7001 -username xxxx -password xxxx I get the
              >> following output:
              >>
              >> {MBeanName="mydomain:Location=myserver,Name=jms-xa-
              >> adp_Pool_3,ServerRuntime=myse
              >> rver,Type=ConnectorConnectionPoolRuntime"{ActiveConnectionsCurren
              >> tCount=0}}
              >> {MBeanName="mydomain:Location=myserver,Name=jms-notran-
              >> adp_Pool_2,ServerRuntime=
              >> myserver,Type=ConnectorConnectionPoolRuntime"{ActiveConnectionsCu
              >> rrentCount=0}}
              >>
              >> So from that...it looks like the MBean is there. Any ideas why it
              >is not being
              >> found?
              >>
              >> Thanks,
              >>
              >> Jeff
              >>
              >> "Jeff" <[email protected]> wrote:
              >> >
              >> >
              >> >
              >> >Thank you very much!!
              >> >
              >> >I tried your suggestions and created a general Queue Connection Factory
              >> >within
              >> >MQSeries. Then I setup my MQSeries JMS Bridge Destination to use
              >the
              >> >jms-notrans-adp.rar
              >> >resource adapter. With this configuration, I can send messages to
              >MQSeries
              >> >and
              >> >they get forwarded to Weblogic.
              >> >
              >> >But, if I create a XAQueueConnectionFactory within MQSeries I cannot
              >> >get the bridge
              >> >working at all. I realize that MQSeries has a bug with Transactions
              >> >and remote
              >> >servers, but I have MQSeries and Weblogic running on the same machine.
              >> > I thought
              >> >I could setup an XAConnectionFactory in MQSeries, set the MQSeries
              >JMS
              >> >Bridge
              >> >Destination to use the jms-xa-adp.rar and specify Exactly-once QOS
              >and
              >> >it should
              >> >work? I tried it and it didn't work. ( see attachment for weblogic.log
              >> >showing
              >> >exception ).
              >> >
              >> >Here is my config.xml:
              >> > <MessagingBridge AsyncEnabled="false" DurabilityEnabled="false"
              >> > Name="Request Messaging Bridge" QOSDegradationAllowed="true"
              >> > QualityOfService="Exactly-once"
              >> > SourceDestination="Source JMS Bridge Destination"
              >> > TargetDestination="Target JMS Bridge Destination" Targets="myserver"/>
              >> > <JMSBridgeDestination
              >> > ConnectionFactoryJNDIName="imagictv.platform.ToolkitRequestCF"
              >> > ConnectionURL="t3://localhost:7001"
              >> > DestinationJNDIName="imagictv.platform.ToolkitRequestQueue"
              >Name="Target
              >> >JMS Bridge Destination"/>
              >> > <JMSBridgeDestination
              >> > AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
              >> > ConnectionFactoryJNDIName="MQTestConnectionFactory"
              >> > ConnectionURL="file:/C:/Develop/app_servers/WebSphere/MQSeries"
              >> > DestinationJNDIName="MQTestQueue"
              >> > InitialContextFactory="com.sun.jndi.fscontext.RefFSContextFactory"
              >> >Name="Source
              >> >JMS Bridge Destination"/>
              >> >
              >> >Again, thank you very much for your response. It helped me a great
              >deal.
              >> > Any
              >> >thoughts on the above problem please foward them along.
              >> >
              >> >Oh...and to answer the question posed to me, yes the CR081511_61sp3.jar
              >> >file is
              >> >dated 8/13/2002
              >> >
              >> >
              >> >Sincerely,
              >> >
              >> >Jeff
              >> >
              >> >Dongbo Xiao <[email protected]> wrote:
              >> >>Please see my comments inline.
              >> >>
              >> >>
              >> >>Jeff wrote:
              >> >>>
              >> >>> Hi,
              >> >>> I'm really struggling with getting the Message Bridge working with
              >> >>Weblogic 6.1
              >> >>> sp3 and MQSeries 5.2. Currently I have both installed on the same
              >> >>Windows 2000
              >> >>> machine. First I'll pose some questions that I have, then I discuss
              >> >>the error
              >> >>> I'm getting. Here are my questions:
              >> >>>
              >> >>> 1. With the jms-xa-adp.rar there is a ra.xml and a weblogic-ra.xml.
              >> >> Within the
              >> >>> ra.xml deployment descriptor there are config-properties for ConnectionURL,
              >> >>InitialContextFactory,
              >> >>> ConnectionFactoryJNDI, and DestinationType. If my MQSeries Queue
              >> >is
              >> >>the source
              >> >>> jms destination bridge and my weblogic queue is the target jms
              >destination
              >> >>bridge,
              >> >>> what values do I set for the listed config-properties? I can't
              >seem
              >> >>to find any
              >> >>> documentation on what these values should be. Am I missing something?
              >> >> Do these
              >> >>> values even have to be set?
              >> >>>
              >> >>
              >> >>You DON'T have to do anything to the adapter deployment descriptor
              >> >>files.
              >> >>The values given there for the listed config-properties are just
              >default
              >> >>values.
              >> >>The values configured in JMSBridgeDestination instances are the values
              >> >>used to
              >> >>override the default values in the dd file.
              >> >>
              >> >>> 2. When I go to install a Weblogic instance to a different physical
              >> >>machine what
              >> >>> has to be installed in terms of MQSeries? So I'll have MQSeries
              >on
              >> >>physical machineA
              >> >>> and Weblogic on a different physical machineB. I want machineA
              >to
              >> >>forward all
              >> >>> messages placed on a MQSeries Queue to forward them to machineB
              >where
              >> >>the weblogic
              >> >>> Queue resides. Does machineB also have to contain an MQSeries
              >installation?
              >> >>> Or can I just grab the necessary libraries and jar files and place
              >> >>them on the
              >> >>> Weblogic machineB so they can be included?
              >> >>>
              >> >>
              >> >>You don't have to install MQSeries on the machine that the WebLogic
              >> >>server is running. You need the necessary libraries and jar files
              >> >>though.
              >> >>
              >> >>> 3. Is it correct that if I distribute Weblogic onto one physical
              >server
              >> >>and MQSeries
              >> >>> onto a different physical server that I cannot use Exactly-once
              >quality
              >> >>of service?
              >> >>>
              >> >>
              >> >>That is correct and it is a MQSeries transaction limitation.
              >> >>
              >> >>> Other notes:
              >> >>> 1. I have the following patches installed for Weblogic 6.1 sp3:
              >> >>> CR081404_610sp3.jar
              >> >>> CR081511_61sp3.jar
              >> >>>
              >> >>
              >> >>What version of CR081511_61sp3.jar you have? You need the one dated
              >> >on
              >> >>8/13/2002.
              >> >>
              >> >>> 2. Here is the commands I used to create my ConnectionFactory
              >and
              >> >>Queue within
              >> >>> MQSeries:
              >> >>> def xaqcf(MQTestConnectionFactory) qmanager(QM_jeff)
              >> >>> def q(MQTestQueue) qmanager(QM_jeff) queue(default)
              >> >>>
              >> >>
              >> >>The only possible error I see here is that you create a xaqcf while
              >> >your
              >> >>bridge
              >> >>is configured to have "Atmost-once" QOS. The bridge adapter will
              >create
              >> >>XASession
              >> >>if the connection factory is xa because it knows nothing about QOS
              >of
              >> >>the bridge.
              >> >>As I said, there is a limitation in MQSeries transactions, which
              >prevent
              >> >>the
              >> >>transaction to happen between remote servers. Although the bridge
              >does
              >> >>not
              >> >>start the the transaction in your case, but MQSeries xa connection
              >> >>factory may
              >> >>throw error when it detects the other side is remote. Having said
              >that,
              >> >>I am not
              >> >>completely sure this is the problem caused the bridge to fail. I
              >suggest
              >> >>you use
              >> >>a non-xa connection factory on the MQSeries side and see if the problem
              >> >>goes away.
              >> >>
              >> >>> Okay...here is my error:
              >> >>>
              >> >>> <21-Aug-02 11:08:34 ADT AM> <Error> <MessagingBridge> <Error occurred
              >> >>in bridge
              >> >>> "Messaging Bridge" during transferring messages (java.lang.Exception:
              >> >>java.lang.
              >> >>> reflect.UndeclaredThrowableException: java.lang.reflect.InvocationTargetException:
              >> >>> javax.resource.ResourceException: Error creating consumer or receiving
              >> >>message
              >> >>> at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1086)
              >> >>> at weblogic.jms.adapter.JMSBaseConnection.receiveInternal(JMSBaseConnection.java:774)
              >> >>> at weblogic.jms.adapter.JMSBaseConnection.receiveCommon(JMSBaseConnection.java:656)
              >> >>> at weblogic.jms.adapter.JMSBaseConnection.receive(JMSBaseConnection.java:811)
              >> >>> at weblogic.jms.adapter.JMSConnectionHandle.receive(JMSConnectionHandle.java:111)
              >> >>> at java.lang.reflect.Method.invoke(Native Method)
              >> >>> at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:60)
              >> >>> at $Proxy82.receive(Unknown Source)
              >> >>> at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1215)
              >> >>> at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:854)
              >> >>> at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.
              >> >>>
              >> >>
              >> >>The latest patch CR081511_61sp3.jar (dated on 8/13/2002) will expose
              >> >>more error
              >> >>information.
              >> >>
              >> >>> Has anyone see this error before? Here is part of my ra.xml file....I
              >> >>just put
              >> >>> these entries in to see what happens:
              >> >>>
              >> >>> <config-property>
              >> >>> <config-property-name>ConnectionURL</config-property-name>
              >> >>> <config-property-type>java.lang.String</config-property-type>
              >> >>> <config-property value>file:/C:/Develop/app_servers/WebSphere/MQSeries</config-property-value>
              >> >>> </config-property>
              >> >>>
              >> >>> <config-property>
              >> >>> <config-property-name>InitialContextFactory</config-property-name>
              >> >>> <config-property-type>java.lang.String</config-property-type>
              >> >>> <config-property-value>com.sun.jndi.fscontext.RefFSContextFactory</config-property-value>
              >> >>> </config-property>
              >> >>>
              >> >>> <config-property>
              >> >>> <config-property-name>ConnectionFactoryJNDI</config-property-name>
              >> >>> <config-property-type>java.lang.String</config-property-type>
              >> >>> <config-property-value>MQTestConnectionFactory</config-property-value>
              >> >>> </config-property>
              >> >>>
              >> >>> <config-property>
              >> >>> <config-property-name>DestinationJNDI</config-property-name>
              >> >>> <config-property-type>java.lang.String</config-property-type>
              >> >>> <config-property-value>MQTestQueue</config-property-value>
              >> >>> </config-property>
              >> >>>
              >> >>> <config-property>
              >> >>> <config-property-name>DestinationType</config-property-name>
              >> >>> <config-property-type>java.lang.String</config-property-type>
              >> >>> <config-property-value></config-property-value>
              >> >>> </config-property>
              >> >>>
              >> >>> <config-property>
              >> >>> <config-property-name>AdapterType</config-property-name>
              >> >>> <config-property-type>java.lang.String</config-property-type>
              >> >>> <config-property-value>XATransaction</config-property-value>
              >> >>> </config-property>
              >> >>>
              >> >>
              >> >>As I said earlier, you are not supposed to change the adapter dd
              >file.
              >> >>
              >> >>
              >> >>> Here is a snip of my config.xml:
              >> >>>
              >> >>> <MessagingBridge AsyncEnabled="false" DurabilityEnabled="false"
              >> >>> Name="Messaging Bridge" QualityOfService="Atmost-once"
              >> >>> SourceDestination="Source JMS Bridge Destination"
              >> >>> TargetDestination="Target JMS Bridge Destination" Targets="myserver"/>
              >> >>> <JMSBridgeDestination
              >> >>> AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
              >> >>> ConnectionFactoryJNDIName="MQTestConnectionFactory"
              >> >>> ConnectionURL="file:/C:/Develop/app_servers/WebSphere/MQSeries"
              >> >>> DestinationJNDIName="MQTestQueue" InitialContextFactory="com.sun.jndi.fscontext.RefFSContextFactory"
              >> >>> Name="Source JMS Bridge Destination"/>
              >> >>>
              >> >>> <JMSBridgeDestination
              >> >>> AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
              >> >>> ConnectionFactoryJNDIName="imagictv.platform.ToolkitRequestCF"
              >> >>> ConnectionURL="t3://localhost:7001"
              >> >>> DestinationJNDIName="imagictv.platform.ToolkitRequestQueue"
              >> >>> InitialContextFactory="weblogic.jndi.WLInitialContextFactory"
              >Name="Target
              >> >>> JMS Bridge Destination"/>
              >> >>>
              >> >>
              >> >>Your configuration of the bridge and bridge destinations look fine.
              >> >
              >> >>The last thing is that you have to put MQSeries stuff in your CLASSPATH
              >> >>and PATH for starting the WebLogic server that the bridge is running
              >> >>on.
              >> >>
              >> >>You can also turn on debug for more information.
              >> >>-Dweblogic.Debug.DebugMessagingBridgeStartup=true
              >> >>-Dweblogic.Debug.DebugMessagingBridgeRuntime=true
              >> >>
              >> >>
              >> >>Thanks,
              >> >>Dongbo
              >> >
              

  • Problems with bridge between 2 weblogic

    Hello!
              We try to set up a bridge between 2 weblogic 8.0 on 2 machines to send JMS-messages.
              Our set up / system looks like:
              http://www.dsv.su.se/~fr-ander/images/Overview.jpg
              When we send our messages they do not seems to get all the way trough.
              Look at the following image that describes machine A during a send and receive.
              http://www.dsv.su.se/~fr-ander/images/weblogic_tables.JPG
              1 The bridge is running
              2 We have not send a message yet and the monotoring looks like this.
              3 We send a message from machine A to B.
              4 Very often, just after the message is sent, we get this message from the monotoring of the bridge:
              "WARN: faild and will connect later"
              It lokks like the bridge is connected again after 15-30 sec.
              How ever it seems that machine B indicates that something happens. In the next step (5) we have done the opposite and send from B to A. We get the same result on both machines when we monotor them after a send. In step 5 you see the monotoring of machine A after a send from B. The only difference is tha the bridge from B to A seems to be more stable and do not break down. It looks like it have the same state all the time "Forwarding messages".
              5 Assume that we have send a message from B to A then it seems that we get a indication about that at A ("Messages high" and Messages received" increase), something do get to the destination. (The same happens if the secnario is from A to B). But we do not get a indication in the "Messages" column!! When we try to read from the queue FredrikReceive or OscarReceive we get nothing.
              Do you guys got any idea why this happens?
              A) Why is the bridge "falling down" all the time when we send and why the bridge "get up" again a while later.
              B) Why do we do not find the real message, why do we get the indication that something happens but we can not read the message???
              Best regards
              Fredrik and Oscar

    Hi Fredrik.
              Message bridges are tricky things, and there are a number of requirements that need to be in place for them to work correctly:
              - <b>ALL</b> JMS objects need to be unique between domains for XA transactions to work correctly. From looking at your diagram, this appears to be the case, but I can't see the name of higher level objects like your connection factory and JMS server.
              - the domains must have trust enabled, which means setting the same domain security credential for both domains
              - the correct adapter rar file needs to be deployed for the domain.
              Soooo...
              - which adapter are you using for the JMS bridge? (what is the name of the RAR file?)
              - are you getting any warnings/errors as part of starting the message bridge? From looking at the administration console, everything looks OK on first flush because you're getting a consumer plugged in.
              But if you're not seeing those bytes pending disappear, that means there are transaction issues in communicating between the domains. (most likely caused by domain trust)
              Try enabling the following switches in your start script for both domains:
              -Dweblogic.Debug.DebugMessagingBridgeStartup=true
              -Dweblogic.Debug.DebugMessagingBridgeRuntime=true
              There's a pretty good FAQ for troubleshooting messaging bridges that I've used in the past here: http://e-docs.bea.com/wls/docs81/faq/msgbridge.html#251107
              ...and the general configuration reference for messaging bridges is here, if you haven't gone there already (apologies if you have) - http://edocs.bea.com/wls/docs81/ConsoleHelp/messaging_bridge.html#1107082
              <br>
              Kevin Powe
              http://www.integral-techsolutions.com

  • Message bridge between two instances

    I am trying to setup messaging bridge between two instances of weblogic server.
    Can the second instance belong to a different domain? If yes how to configure it?

    Yes, you can configure a messaging bridge to work between two WebLogic domains.
    The general instructions of configuring a message bridge, including the bridge instance itself, the bridge destinations and the adapter, can be found at
    http://edocs.bea.com/wls/docs103/bridge/basics.html#wp1168461
    The only extra thing that you may need to take care of for the cross-domain case is to configure cross-domain security as instructed at
    http://edocs.bea.com/wls/docs103/bridge/wls_interop.html#wp1126873
    Regards,
    Dongbo

  • Trouble defining BAM Enterprise Message Source for BEA WebLogic Server

    Hi all,
    I've just started to play a little with Oracle BAM Architect.
    I've WLS 10.0 and Oracle BAM Architect 10g release 3.
    On Oracle BAM Architect I've defined an Enterprise Message Source for BEA WebLogic Server as follows:
    Name: ALSBSource
    Owner: ...
    Type: BEA WebLogic Server
    Initial context factory: weblogic.jndi.WLInitialContextFactory
    JNDI Service Provider URL: t3://mypc:7001
    TopicConnectionFactory name: com.myConnectionFactory
    Topic name: com.myBAMTopic
    JMS message type: TextMessage
    Durable subscriber name: BAMSubscriber
    Client ID: BAMSubscriber
    Name | Flow name | Type | Max size | Formatting
    content | BAM | String | 1024 | (none)
    On WLS 10.0 I've defined the required JMS stuff.
    On Oracle Design Studio I've defined a plan that includes:
    - an Oracle BAM Enterprise Message Receiver from which I've selected the above 'ALSBSource' Enterprise Message Source
    - a simple Grid
    I've connected the BAM Enterprise Message Receiver to the Grid and clicked on 'Update' button.
    When I try to publish a message on 'com.myBAMTopic' I don't see anything on the grid defined in the Oracle Design Studio.
    The first question is about the definition of an Enterprise Message Source for BEA WebLogic Server in the Oracle BAM Architect.
    I did not change the Oracle BAM Architect classpath or Oracle Design Studio classpath adding the weblogic.jar, because no error has been raised during the configuration of the message source and the plan. Should I update Oracle classpath with the weblogic.jar ?
    Did I forget any other step ?
    I thank you in advance for any feedback.
    Regards
    ferp

    ferp - I got this to work with
    JNDI Service Provider URL: http://localhost
    When I add the port
    JNDI Service Provider URL: http://localhost:23891
    I cannot get my EMS to start.
    Hopefully this should fix your issue.
    Sudeep.

  • Not able to consume messages in the remote weblogic server from Oracle SOA

    I am able to see the messages in the Queue.
    I just created a simple JMS adapter for outboud connection
    Consume operations parameters
    Queue Name : eis/JMS/REmoteQueue
    JNDI Name : eis/JMS/REmoteQueue
    Configuration for
    Remote Weblogic server ( weblogic 9.2)
    JMSModule: MyJMSModule
    Queue Information:
    Queue Name : REmoteQueue
    Destination name :eis/JMS/REmoteQueue
    JNDI Name: eis/JMS/REmoteQueue
    ConnectionFactory: TestFactory
    JNDI Name : jms/TestFactory
    SOA Oracle Weblogic server : Local Machine
    general information for this resource adapter Outbound Connection.
    JNDI Name: eis/JMS/RemoteQueue
    Property Name Property Type Property Value
    AcknowledgeMode : AUTO_ACKNOWLEDGE
    ConnectionFactoryLocation : jms/TestFactory
    FactoryProperties: java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://servername:xx;java.naming.security.principal=xxxxx;java.naming.security.credentials=xxxxx
    IsTopic : false
    IsTransacted :false
    Password :
    Username:
    I am not able to see any consumers in the remote machine.

    There are no errors /exceptions. The project is deployed, since it is a JMS adapter with consume operation it should poll the queue and get the message if it is available.
    This is the *.jca file for adapter.
    <adapter-config name="psoftconsume" adapter="Jms Adapter" wsdlLocation="psoftconsume.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
    <connection-factory location="eis/JMS/RemoteQueue" UIConnectionName="remotewls" UIJmsProvider="WLSJMS" adapterRef=""/>
    <endpoint-activation portType="Consume_Message_ptt" operation="Consume_Message">
    <activation-spec className="oracle.tip.adapter.jms.inbound.JmsConsumeActivationSpec">
    <property name="DestinationName" value="eis/JMS/RemoteQueue"/>
    <property name="UseMessageListener" value="false"/>
    <property name="PayloadType" value="TextMessage"/>
    </activation-spec>
    </endpoint-activation>
    </adapter-config>

  • SP5 Messaging Bridge Problem

    Hi,
              I've set up a messaging bridge between 2 Weblogic 8.1 SP5 boxes, and am getting the following generic error when it's trying to connect to the target. I've got bridge debugging on.
              I've tried all the usual suspects: XA enabled connection factories, disabled certificate generation and set certificate to the same thing for both servers, disable guest is unchecked, connectors are deployed, etc.
              This error message is useless...anyone have any ideas?
              <Aug 16, 2006 2:56:24 PM IDT> <Debug> <MessagingBridge> <BEA-200006> <Messaging bridge debugging RUNTIME! Bridge bridge.test Getting target connection.>
              <Aug 16, 2006 2:56:24 PM IDT> <Warning> <Connector> <BEA-190032> << Weblogic Messaging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > ResourceAllocationException of javax.resource.ResourceException: Failed to start the connection on createManagedConnection.>

    The bridge just does a basic JNDI lookup, and there's nowhere to put additional parameters. However, you can do this using a "Foreign JMS Server".
              Create a "Foreign JMS Server" either using the console, or by putting a ForeignJMSServer entry in config.xml. There is a "JNDI Properties" field, where you can specify your security credentials in name/value form (you'll need the values of those JNDI constants, which are "javax.jndi.something.something", not SECURITY_PRINCIPAL and SECURITY_CREDENTIALS.)
              Then, have the bridge look up the "Local JNDI Name" from the Foreign JMS bean rather than the remote TIBCO JNDI object. (You do this by removing all the JNDI parameters from the bridge destination so that it uses the local JNDI provider, not the TIBCO JNDI provider.)
              Essentially, by doing this, the Foreign JMS code in WLS is going to delegate the JNDI lookup to the TIBCO provider using all the JNDI parameters you specify, including security.

  • Message bridge example

    Hi,
    I need the complete example on Message bridge in weblogic server. ie betwenn to weblogic jms server's??
    please help me out if some one know how to setup Message bridge between two weblogic servers
    Thank

    If your Sonic ESB is lik JMS poller then use JCA JMS adapter with BPEL for communication. It is a reliable option.
    If the Sonic ESB is a http service then access it as a webservice from BPEL.

  • Message Bridge error "Received message with no URI property"

    I have created a message bridge between two weblogic JMS servers on different domains.
              Message bridge has source and destinations.
              I have tested each ques seperately with MDB deployed on each server.
              When i am putting message on source que then i am getting this error "Received message with no URI property"
              It would be grat help if some could tell me what might be going wrong.
              Thanks
              Akash

    Hi,
              This exception indicates a failure to establish a JNDI context for either the source or target destination host. Check if the the bridge's configured URLs for both are correct. I'm not 100% sure, but it is likely that no URL need be configured for destination's that are in the same cluster as the bridge.
              For more information, I suggest looking at the Messaging Bridge FAQ, which contains some troubleshooting tips. You can find a link to it here:
              http://dev2dev.bea.com/technologies/jms/index.jsp
              Tom Barnes, BEA

  • CreateManagedConnection Error messaging bridge MQ

    Hi all,
              I've successfuly set up a messaging bridge between 2 Weblogic queues, but I
              get the following when setting up an MQSeries queue as source and WL queue
              as target:
              javax.resource.spi.ResourceAllocationException: CreateManagedConnection
              Error: Failed to start the connection
              at
              weblogic.connector.common.internal.ConnectionPool.makeResources(ConnectionPo
              ol.java:978)
              at
              weblogic.connector.common.internal.ConnectionPool.getConnection(ConnectionPo
              ol.java:1708)
              at
              weblogic.connector.common.internal.ConnectionPoolManager.getConnection(Conne
              ctionPoolManager.java:163)
              at
              weblogic.connector.common.internal.ConnectionManagerImpl.allocateConnection(
              ConnectionManagerImpl.java:25)
              at
              weblogic.jms.adapter.JMSBaseConnectionFactory.getSourceConnection(JMSBaseCon
              nectionFactory.java:97)
              at
              weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.
              java:699)
              at
              weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:89
              9)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
              <May 13, 2002 7:11:23 PM PDT> <Error> <Connector> <190006> <Error granting
              conne
              ction request.>
              It finds everything fine in LDAP for the MQ queue. Does anyone know what
              would cause this exception?
              I'm using Weblogic 7, and MQSeries 5.2.1
              Thanks,
              Duke
              [email protected]
              

    Hi Duke,
              Looks like that you have not configured the MQSeries
              side of the bridge. There are a couple of things you have to configure in
              order to make bridge work for 3rd party
              products. Please see details in the e-doc:
              http://edocs.bea.com/wls/docs70/adminguide/msgbridge.html#1063962
              Besides, you have to configure the security attributes according to the
              requirement of your MQSeries setup.
              Hope this helps.
              Dongbo
              "Duke Nguyen" <[email protected]> wrote in message
              news:[email protected]...
              > Hi all,
              >
              > I've successfuly set up a messaging bridge between 2 Weblogic queues, but
              I
              > get the following when setting up an MQSeries queue as source and WL queue
              > as target:
              >
              > javax.resource.spi.ResourceAllocationException: CreateManagedConnection
              > Error: Failed to start the connection
              > at
              >
              weblogic.connector.common.internal.ConnectionPool.makeResources(ConnectionPo
              > ol.java:978)
              > at
              >
              weblogic.connector.common.internal.ConnectionPool.getConnection(ConnectionPo
              > ol.java:1708)
              > at
              >
              weblogic.connector.common.internal.ConnectionPoolManager.getConnection(Conne
              > ctionPoolManager.java:163)
              > at
              >
              weblogic.connector.common.internal.ConnectionManagerImpl.allocateConnection(
              > ConnectionManagerImpl.java:25)
              > at
              >
              weblogic.jms.adapter.JMSBaseConnectionFactory.getSourceConnection(JMSBaseCon
              > nectionFactory.java:97)
              > at
              >
              weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.
              > java:699)
              > at
              >
              weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:89
              > 9)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
              > <May 13, 2002 7:11:23 PM PDT> <Error> <Connector> <190006> <Error granting
              > conne
              > ction request.>
              >
              > It finds everything fine in LDAP for the MQ queue. Does anyone know what
              > would cause this exception?
              > I'm using Weblogic 7, and MQSeries 5.2.1
              >
              > Thanks,
              > Duke
              > [email protected]
              >
              >
              

  • Foreign JMS Server vs Messaging bridge

    Could any body tell me which one is the best Whether Foreign JMS Server or Messaging bridge for connecting Weblogic to IBM MQ Series.I am trying to use foreign jms server but i dont know how to post the message to that queue i created in foreign jms server..

    Hi,
              For sending messages non-transactionally, foreign JMS server is sufficient. For sending messages transactionally using standard JTA transactions, the simplest way is to send them on the server and reference the foreign JMS through an EJB resource reference. See the the following FAQ for a walk-through of the various options, including guidance on when to use a bridge:
              http://e-docs.bea.com/wls/docs81/faq/interop.html
              Tom

  • Messaging Bridge/Foreign JMS Server

    Can someone clarify what is the difference in using messaging bridge or Foreign JMS Server in listening to a topic from other weblogic server of same version.
    Edited by: user11359157 on 6 Jul, 2009 3:17 PM

    I always thought one has to use remote classes from the foreign JMS server in local the classpath to send or receive messages stored at
    the foreign JMS server / the remote side.
    <Jayesh> that is true of the remote side of the JMS is non-weblogic. </Jayesh>
    Also in the WLS bridge this can be specified. IMHO the bridge has the advantage that I can use the wls classe and the bridge knows
    the classpath and bridges to the foreign jms server, so the application developer doesn't have to use foreign classes, eg. tibco or mq.
    <Jayesh> When you have remote JMS is WebLogic it is obvious considering that both remote and local jms uses same weblogic classes. </Jayesh>
    Now, where does this happen for the foreign jms server (which is kind of alternative to wls bridge, without store and forward)?
    All I can see is a local JNDI lookup being translated to a remote one.
    Is really the local JMS implementation used to talk to the remote JMS server?
    When a JNDI lookup for a queue happens will then be WLS queue implementation returned?
    <Jayesh> No there is not local JMS store is used. Foreign JMS server just provides administrative convenience by moving remote JMS destination JNDI definitions in local JNDI definition. It allows to use this local definition by all EJBs, servlets and messaging bridges. If the remote definitions changes you can change those definition in admin console and does not need change in deployment descriptors of the EJBs and servlets to prevent redeployment. Again this is no administrative convenience and during run time it will behave exactly same as you are sending or receiving message directly from remote JMS destination.
    </Jayesh>
    Hope this clears confusion.
    jayesh@yagna

  • Messaging bridge with JBoss

    Hi
              I am trying to configure a messaging bridge between weblogic 8.1 sp4 and jboss-4.0.2 on my local machine.
              I have the bridge working for the following configuration:
              Adapter JNDI Name: eis.jms.WLSConnectionFactoryJNDINoTX
              Connection URL: jboss server URL with port
              Initial Context Factory: org.jnp.interfaces.NamingContextFactory
              Connection Factory JNDI Name: ConnectionFactory
              Destination JNDI Name: queue/testQueue
              and these jar's are in my weblogic class path:
              [jboss_home]/client/jboss-common-client.jar
              [jboss_home]/client/jbossmq-client.jar
              [jboss_home]/client/jboss-system-client.jar
              [jboss_home]/client/jboss-transaction-client.jar
              [jboss_home]/client/jnp-client.jar
              [jboss_home]/lib/concurrent.jar
              [jboss_home]/client/log4j.jar
              I have also deployed connector module jms-notran-adp.rar on my weblogic server.
              I am using "Duplicate-okay" Quality Of Service and the bridge functions correctly.:^O
              Now when I try to configure the bridge so that I can use "Exactly-once" Quality Of Service I use the following configuration:
              Adapter JNDI Name: eis.jms.WLSConnectionFactoryJNDIXA
              Connection URL: jboss server URL with port
              Initial Context Factory: org.jnp.interfaces.NamingContextFactory
              Connection Factory JNDI Name: XAConnectionFactory
              Destination JNDI Name: queue/testQueue
              and add these jar's in my weblogic class path:
              [jboss_home]/client/jboss-common-client.jar
              [jboss_home]/client/jbossmq-client.jar
              [jboss_home]/client/jboss-system-client.jar
              [jboss_home]/client/jboss-transaction-client.jar
              [jboss_home]/client/jnp-client.jar
              [jboss_home]/lib/concurrent.jar
              [jboss_home]/client/log4j.jar
              I also deployed the connector module jms-xa-adp.rar on my weblogic server.
              The connection factory that I use for the weblogic destination is also "XA enabled".
              The problem which I have is that no messages are transferred via the bridge and following error is printed out from the server :_|:
              <2005/08/15 12:20:22 PM> <Error> <Connector> <BEA-190091> <Call to implementation of ManagedConnection.getXAResource in resource adapter with jndiName = eis/jms/WLSConnectionFactoryJNDIXA failed: java.lang.IllegalStateException: can only be called from server>
              Could you please assist.
              Thanks in advance

    Hi,
              I am trying to do configure a bridge between weblogic 7.0 SP4 and JBOSS 4.0.3 SP1.
              I have set the classpath as mentioned but I am getting an error
              ####<Apr 11, 2006 2:02:34 PM CEST> <Debug> <MessagingBridge> <DNI6> <dni6testser
              ver> <ExecuteThread: '10' for queue: 'default'> <kernel identity> <> <200006> <M
              essaging Bridge Debugging RUNTIME! Bridge WebOSSTEST Getting target connection>
              ####<Apr 11, 2006 2:02:34 PM CEST> <Warning> <Connector> <DNI6> <dni6testserver>
              <ExecuteThread: '10' for queue: 'default'> <kernel identity> <> <190032> << Web
              logic Messaging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > Resourc
              eAllocationException of javax.resource.ResourceException: Failed to start the co
              nnection on createManagedConnection.>
              ####<Apr 11, 2006 2:02:34 PM CEST> <Info> <MessagingBridge> <DNI6> <dni6testserv
              er> <ExecuteThread: '10' for queue: 'default'> <kernel identity> <> <200043> <Br
              idge "WebOSSTEST" failed to connect to the target destination and will try again
              in 60 seconds. (java.lang.Exception: javax.resource.spi.ResourceAllocationExcep
              tion: CreateManagedConnection Error: Failed to start the connection
              at weblogic.connector.common.internal.ConnectionPool.makeResources(Conne
              ctionPool.java:1009)
              at weblogic.connector.common.internal.ConnectionPool.getConnection(Conne
              ctionPool.java:1769)
              at weblogic.connector.common.internal.ConnectionPoolManager.getConnectio
              n(ConnectionPoolManager.java:191)
              at weblogic.connector.common.internal.ConnectionManagerImpl.allocateConn
              ection(ConnectionManagerImpl.java:25)
              at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMS
              BaseConnectionFactory.java:126)
              at weblogic.jms.bridge.internal.MessagingBridge.getConnections(Messaging
              Bridge.java:764)
              at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.
              java:930)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
              -------------- Linked Exception ------------
              javax.resource.ResourceException: Failed to start the connection
              at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBase
              Connection.java:1273)
              at weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnectio
              n.java:357)
              at weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:2
              29)
              at weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnect
              ion(JMSManagedConnectionFactory.java:190)
              at weblogic.connector.common.internal.ConnectionPool.makeResources(Conne
              ctionPool.java:1002)
              at weblogic.connector.common.internal.ConnectionPool.getConnection(Conne
              ctionPool.java:1769)
              at weblogic.connector.common.internal.ConnectionPoolManager.getConnectio
              n(ConnectionPoolManager.java:191)
              at weblogic.connector.common.internal.ConnectionManagerImpl.allocateConn
              ection(ConnectionManagerImpl.java:25)
              Does anyone have a solution

  • MQ 6 WLS 9.2 JMS Message Bridge Error

    I tried to set up a JMS message bridge between MQ 9.2 and WLS 9.2 collocated on the same server following the BEA example:
              1.Create local queue on MQ
              2.Bind queue using JMSAdmin
              3.Create JMS bridge betwen a source destination using JNDI name in #2 and a local WLS queue.
              Here is the WLS config:
              <messaging-bridge>
              <name>MQ-WLSBridge</name>
              <target>adminServer</target>
              <source-destination>MQ-WLSSource</source-destination>
              <target-destination>MQ-WLSTarget</target-destination>
              <selector></selector>
              <quality-of-service>Exactly-once</quality-of-service>
              <qos-degradation-allowed>true</qos-degradation-allowed>
              <durability-enabled>true</durability-enabled>
              <idle-time-maximum>60</idle-time-maximum>
              <async-enabled>true</async-enabled>
              <started>true</started>
              <preserve-msg-property>false</preserve-msg-property>
              </messaging-bridge>
              <jms-bridge-destination>
              <name>MQ-WLSTarget</name>
              <adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDINoTX</adapter-jndi-name>
              <classpath></classpath>
              <connection-factory-jndi-name>com.MetaSolv.Security.QueueConnectionFactory</connection-factory-jndi-name>
              <connection-url>t3://localhost:7005</connection-url>
                   <destination-jndi-name>WLSMessageQueue</destination-jndi-name>
              </jms-bridge-destination>
              <jms-bridge-destination>
              <name>MQ-WLSSource</name>
              <adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDINoTX</adapter-jndi-name>
              <classpath></classpath>
              <connection-factory-jndi-name>QCF</connection-factory-jndi-name>
              <initial-context-factory>com.sun.jndi.fscontext.RefFSContextFactory</initial-context-factory>
              <connection-url>file:///usr/mqm/java/jndi</connection-url>
              <destination-jndi-name>MQMessageQueus</destination-jndi-name>
              </jms-bridge-destination>
              I used a standalone JMS client and was able to connect to the MQ queue using the above JNDI name, factory so the MQ side was set up properly.
              When I start up WLS, I saw that
              <The messaging bridge "MQ-WLSBridge" has been successfully deployed.>
              and the exception:
              <MessagingBridge> <BEA-200042> <Bridge MQ-WLSBridge failed to connect to the source destination and will try again in 20 seconds. This could be a temporary condition unless the messages repeat several times. (java.lang.Exception: javax.resource.ResourceException: Failed to start the connection
                   at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1458)
                   at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1438)
                   at weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnection.java:403)
                   at weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:242)
                   at weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:190)
                   at weblogic.connector.security.layer.AdapterLayer.createManagedConnection(AdapterLayer.java:802)
                   at weblogic.connector.outbound.ConnectionFactory.createResource(ConnectionFactory.java:91)
                   at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1057)
                   at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:346)
                   at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:294)
                   at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:277)
                   at weblogic.connector.outbound.ConnectionPool.reserveResource(ConnectionPool.java:606)
                   at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:271)
                   at weblogic.connector.outbound.ConnectionManagerImpl.getConnectionInfo(ConnectionManagerImpl.java:352)
                   at weblogic.connector.outbound.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:307)
                   at weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:115)
                   at weblogic.jms.adapter.JMSBaseConnectionFactory.getSourceConnection(JMSBaseConnectionFactory.java:92)
                   at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:809)
                   at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1042)
                   at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
                   at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
                   at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
              )>
              There is no error in the MQ logs. What is the problem?
              CS

    C S <> wrote:
              > I tried to set up a JMS message bridge between MQ 9.2 and WLS 9.2
              > collocated on the same server following the BEA example: 1.Create local
              > queue on MQ 2.Bind queue using JMSAdmin
              > 3.Create JMS bridge betwen a source destination using JNDI name in #2 and
              > a local WLS queue.
              >
              > Here is the WLS config:
              > <messaging-bridge>
              > <name>MQ-WLSBridge</name>
              > <target>adminServer</target>
              > <source-destination>MQ-WLSSource</source-destination>
              > <target-destination>MQ-WLSTarget</target-destination>
              > <selector></selector>
              > <quality-of-service>Exactly-once</quality-of-service>
              > <qos-degradation-allowed>true</qos-degradation-allowed>
              > <durability-enabled>true</durability-enabled>
              > <idle-time-maximum>60</idle-time-maximum>
              > <async-enabled>true</async-enabled>
              > <started>true</started>
              > <preserve-msg-property>false</preserve-msg-property>
              > </messaging-bridge>
              >
              > <jms-bridge-destination>
              > <name>MQ-WLSTarget</name>
              >
              <adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDINoTX</adapter-jndi-name>
              > <classpath></classpath>
              >
              <connection-factory-jndi-name>com.MetaSolv.Security.QueueConnectionFactory</connection-factory-jndi-name>
              > <connection-url>t3://localhost:7005</connection-url>
              > <destination-jndi-name>WLSMessageQueue</destination-jndi-name>
              > </jms-bridge-destination>
              > <jms-bridge-destination>
              > <name>MQ-WLSSource</name>
              >
              Hello,
              First of all, your classpath doesn't seem to be correct. You need to add the
              MQ jars in the bridge classpath. (DONT use the server classpath for
              this!!!)
              Secondly, enable debugging in Weblogic, which will give you some
              information: -Dweblogic.Debug.DebugMessagingBridgeStartup=true -Dweblogic.Debug.DebugMessagingBridgeRuntime=true -Dweblogic.Debug.DebugMessagingBridgeRuntimeVerbose=true
              IF you have more questions, pls reply also be mail.
              Bart
              Schelstraete Bart
              [email protected]
              http://www.schelstraete.org
              http://www.linkedin.com/in/bschelst

Maybe you are looking for

  • Material Number is not in table PLPO

    Gurus, I need to pull Material Production standard Time (Setup, Labor and Machine time) data from table PLPO into BW, however i do not see the field MATNR(Material) in this table. There is material group and BOM though. In this scenario, what are my

  • ATI Radeon HD 2600 XT - HDMI signal loss to LCD TV

    I have a new Mac Pro 2008 with ATI Radeon HD 2600 XT connected to a Sharp LC-42D64U 1080p TV via a DVI to HDMI cable. If I turn the TV off or change the input from the computer to TV and back I get an error message that an incompatible signal is bein

  • Error "Function G1 does not exist "

    Hi , While doing monitoring  got error " Function G1 does not exist ". Bdoc type : BUPA_REL Sate         : E04. Checked SMQ1,SMQ2 , no queues were in sysfail status.How to maintain this function. Help me how to clear . Thanks in advance, Regards, PA.

  • Netui:anchor

    Hi, I want to open a link(Fr eg www.yahoo.com) in a new browser window.I am using netui:anchor tag but a not able to display the link in the new page.A popup window opens but the url doesnt load. <netui:anchor href="${container.item.urlName}" popup="

  • Lion says "can't connect to internet" after sleep; network is fine

    So our two-month-old MacBook Pro has developed an unusual tic. Now when we wake it from sleep, it is initially unable to access the internet through browsers or mail -- even though AirPort is connecting to the network and other devices on the network