JMS Bridge Between HornetQ (on Jboss 5.1) and WebLogic 10.3

Greetings!
I'm trying to set up a bridge between HornetQ (JBoss 5.1) and WebLogic 10.3. The bridge should be set up on WebLogic. It'll read messages from queue on HornetQ and post them on WebLogic Queue.
Here are my preferences on Source Destination:
Adapter JNDI Name eis.jms.WLSConnectionFactoryJNDINoTx
Classpath: empty (?)
Connection URL: jnp://<hostName>:1099
Initial Context Factory: org.jnp.interfaces.NamingContextFactory
Connection Factory JNDI Name: /tp/ConnectionFactory
Connection JNDI Name: /etgreceiver/queue
Destination Type: Queue
User Name: guest
User Password: guest.
WebLogic prints a warning: <12.10.2010 18:25:40 MSD> <Warning> <Connector> <BEA-190032> << eis/jms/WLSConnectionFactoryJNDINoTX > resourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: ConnectionFactory: failed to get initial context (InitialContextFactory =org.jnp.interfaces.NamingContextFactory, url = jnp://AIskrich:11099, user name = guest) ">
I have no idea what the problem is, could anyone help?

Yes - I think "pre_classpath" is probably the right place to reference the non-WebLogic jars. That said, layered products like BPEL often provide tooling that simplifies messaging integration -- I assume some even help setup classpaths and may have their own recommended unique way to set them. So I recommend consulting your layered product's documentation and forums.
It looks like this posting already covers the needed HornetQ specific settings. If it turns out that you're still interested in working directly at the WebLogic layer instead of the BPEL layer, see the interop FAQ http://docs.oracle.com/cd/E21764_01/web.1111/e13727/interop.htm#JMSPG553 for a full treatment of WebLogic's built in JMS provider integration features.
HTH,
Tom

Similar Messages

  • Nd help configuring JMS Bridges between COM and SOM

    We skip the JMS Bridge between SOM and COM because we deploy the O2A cartridge using the:
    - When Central Order Management and Service Order Management Exist in the Same
    OSM Instance in a Non-Cluster Environment.
    - Customer and Service Order Management in the Same OSM Instance
    "Deploy the following cartridges through Design Studio for the simple fulfillment
    topology"
    Now what happening is: the flow of the order taking time before it was completed or need manually submit the task using oms-automation user.
    But even with the above work around we cannot see the billing data in BRM.
    UpdateSalesOrderSiebelCommsProvABCSImpl (v. 1.0) this is the last BPEL process we see in BPEL.
    FulfillBillingFunction.BRM-ALL.BundleGranularity.FulfillBillingSignificantUpdates is the last Activity we can see in osmwebui if not manually update the task.
    Then ProvisionOrderSIResponseTask is the current task in osm task web client where order state is In-Progress.
    With that it seems the SOM is not processing.
    Do you have any idea why we can't complete the order and see the billing data in BRM?
    Is'it the COM and SOM not properly configured, or have some issue with other application(RODOD)?
    Thanks,
    Ace

    Hi All,
    This issue already resolve by configuring the routing in AIA.

  • Configuring JMS Bridges between COM and SOM

    Hi,
    We started working on OSM 7.0.2 and I have a question about the configuration of JMS Bridges between COM and SOM.
    When COM and SOM Cartridges are installed in the same OSM instance on non-cluster env., it is mandatory to configure JMS Bridges between COM and SOM?
    If it is case, could you please detail the procedure to follow?
    In the document called "Application Integration Architecture Order-to-Activate Cartridge Guide Release 7.0.2 E18005-01" it is not obvious to understand. If you have a look in the table 2-1 page 2-15, I don't see all the mandatory field values to create a new destination bridges (for instance, what is the value of destination JNDI name?). Does anyone configure this part in the setting up OSM to the Order-to-Activate Solution?
    Best regards.

    The COM-SOM bridge is only required when COM and SOM are deployed on separate osm server instances and AIA Emulators are deployed (on both) for development/demo/quick testing purposes.
    In QA/SIT/PRODUCTION environments, OSM should be integrated via AIA, this means that all participant applications ( CRM , OSM-COM, OMS-SOM, BRM ) should be using queue bridges (or SAF in 7.0.3)

  • Weblogic JMS bridge between Weblogic and oracle Advanced Queue

    Hi,
    We are facing some issues when we are trying to integrate with Oracle AQ JMS through Weblogic.
    We have configured a Foreign AQ server which points to the oracle Advanced Queue and we are trying to create a Weblogic JMS bridge between AQ and weblogic. The bridge works perfectly if create the connection factories and bridge destinations with NonTX mode. The issue is with XA mode. Also we have deployed the Resource adaper for XAResource to use XA transactions.
    No help is available for the exception on google too :)
    Following is the exception we are getting.
    <An error occurred in bridge "aqjmsbridge" during the transfer of messages (javax.resource.ResourceException: Failed to setup the Resource Adapter Connection for enlistment in the transaction, Pool = 'eis/jms/WLSConnectionFactoryJNDIXA', javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XA_OK
    javax.transaction.xa.XAException: method start should not be called on weblogic.transaction.internal.IgnoreXAResource
    at weblogic.jms.foreign.IgnoreXAResourceImpl.start(ForeignAQIntegration.java:260)
    at weblogic.connector.security.layer.AdapterLayer.start(AdapterLayer.java:513)
    at weblogic.connector.transaction.outbound.XAWrapper.start(XAWrapper.java:466)
    at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1184)
    at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1117)
    at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:275)
    at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:516)
    at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:443)
    at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:118)
    at weblogic.connector.outbound.ConnectionWrapper.invoke(ConnectionWrapper.java:218)
    at $Proxy59.receive(Unknown Source)
    at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1427)
    at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1002)
    at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1079)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    .).>
    Will appriciate any help for the above.
    Thanks and Regards,
    Navin

    Maybe this if of any help:
    - Re: Help with creating AQ JMS
    or
    - Re: AQ Weblogic integration - JMS-107: Operation not allowed on Connection

  • Configure a Bridge between Websphere MQ 6.0(MQSeries) and Weblogic9.2

    Bridge between Websphere MQ 6.0(Previously MQSeries) and Weblogic 9.2
    At Websphere MQ 6.0 side:
    „³ Create a folder by the name JNDI-Directory under C drive
    „³ Create the queue manager by using the command at the command prompt:
    crtmqm testqmgr or you can create it by GUI also.
    „³ Start the queue manager: strmqm testqmgr. or you can start it by GUI also
    „³Define Local Queues in the newly created queue manager testqmgr by using GUI or by using Commands .Assume we have created a local queue by the name MyMDBQueue.
    „³ Create a file by the name MyAdmin.config,It¡¦s a configuration file under C:\Program Files\IBM\WebSphere MQ\Java\bin directory.
    Now add the following entries into the config file
    INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
    PROVIDER_URL=file:/C:/JNDI-Directory
    SECURITY_AUTHENTICATION=none
    Without the above step also you can do that. How it means
    You have a file called JMSAdmin.config under C:\Program Files\IBM\WebSphere MQ\Java\bin directory.jsut uncomment the above mentioned 3 properties and comment the remaing that¡¦s it.
    Next run the below command
    C:\Program Files\IBM\WebSphere MQ\Java\bin>JMSAdmin.bat ¡Vcfg MyAdmin.config
    Once you run the above command you will see
    this prompt InitCtx>.
    Now your command prompt will stop at
    InitCtx>
    Just type the following commands
    a) InitCtx> def xaqcf(SenderQCF) qmgr(testqmgr) press enter
    b) InitCtx> def q(MyMDBQueue) qmgr(testqmgr) queue(MyMDBQueue) press enter
    c) InitCtx> end press enter
    At step a it will create a queue connection factory by the name SenderQCF UNDER QueueManager testqmgr
    At step b it will create a queue by the name MyMDBQueue UNDER
    QueueManager testqmgr
    At step c Its ends the Context cration process
    At Weblogic 9.2 side:
    Go to your domain location lib folder i.e. In my system it¡¦s in C:\bea\user_projects\domains\bplus_domain\lib. Add the following jars in lib folder
    1) com.ibm.mq.jar
    2) com.ibm.mqjms.jar
    3) commonservices.jar
    4) connector.jar
    5) dhbcore.jar
    6) fscontext.jar
    7) jms.jar
    8) jta.jar
    9) ldap.jar
    10) postcard.jar
    11) providerutil.jar
    Now restart the weblogic server. now the server reads all the jars
    Open console of weblogic9
    Go to Services„³Messaging„³Bridges„³Jms bridge destination. under this create new
    jms bridge destination.
    Source of jms bridge destination:
    Adapter JNDI Name: eis.jms.WLSConnectionFactofyNoTX
    Classpath:<optional>
    Connection URL: file:/C:/JNDI-Directory
    Initial Context Factory: com.sun.jndi.fscontext.RefFSContextFactory
    Connection Factory JNDI Name: SenderQCF
    Destination JNDI Name: MyMDBQueue
    Destination Type:Queue
    User Name: <optional>
    User Password: <optional>
    Confirm User Password: <optional>
    Now activate the changes what you have made
    Destination of jms bridge destination:
    Adapter JNDI Name: eis.jms.WLSConnectionFactofyNoTX
    Classpath: < optional>
    Connection URL: t3://localhost:7001
    Initial Context Factory: weblogic.jndi.WLInitialContextFactory
    Connection Factory JNDI Name: ConnectionFactory1
    Destination JNDI Name: ResponseQueue
    Destination Type:Queue
    User Name: < optional>
    User Password: < optional>
    Confirm User Password: < optional>
    Now configure a new Bridge by using above configured two source and destination
    jms bridge destinations
    At source you have to select Other JMS.don¡¦t select Weblogic7 or Higher because the source of this bridge is WebsphreMQ, not weblogic
    Now once again RESTART The weblogic9.2 serever and put one message on WebsphreMq queue and check whether it reaches the destination queue of weblogic
    Enjoy the session

    Is this working for you? What errors do you get in the logs (bam, EL)?

  • Patch Issues on JMS bridges configuration between OSM and AIA

    Hi,
    As mentioned in the OSM AIA Order to activate cartridge guide, we want confirm whether the below private patch is mantatory to create the JMS bridge between OSM and AIA.
    Your Oracle Support ID is not sufficient to obtain the private patch. You will need the
    following credentials to access it.
    Patch identifier: 4CFJ
    What will be the outcome if we doesn't install the above mentioned patch.
    Regards,
    Murali

    Hi Murali,
    I would encourage you to use the Oracle Community (via the My Oracle Support) for questions related to patches. Please post your question in the community and I will be happy to assist you.
    - Deep
    (OSM Product Management)

  • 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
              >> >
              

  • JMS bridge is not working in clustered env

              We have set up a JMS bridge between WLS7SP3 and WLS8.1. It works very well in
              stand alone server env (testing env). However, we cannot get it to work on clustered
              env (preprod env). Anyone has experienced working with clustered env? If so,
              please help!
              Thanks.
              

    I forgot to say, we are using WLS8.1 SP1
              "Pete Inman" <[email protected]> wrote in message
              news:[email protected]...
              > If you are in a clusterd environment and you deploy a bridge to the WHOLE
              > cluster it does not work and will not find the adapter. If you deploy to
              the
              > INDIVIDUAL cluster members it will work.
              >
              > We have a cluster with 4 managed servers, deploy to whole cluster - no
              > bridge working, deploy to Server1,2,3,4 bridges work fine.
              >
              > I have a case logged with BEA on this topic.
              >
              > "Tom Barnes" <[email protected]> wrote in message
              > news:[email protected]...
              > > "Not working" is too little information. I suggest
              > > that you start with the messaging bridge FAQ. There is
              > > a link to it here:
              > >
              > > http://dev2dev.bea.com/technologies/jms/index.jsp
              > >
              > > Then post with traces, exceptions, configuration, etc, if
              > > you are still having trouble.
              > >
              > > Tom, BEA
              > >
              > > jyang wrote:
              > >
              > > > We have set up a JMS bridge between WLS7SP3 and WLS8.1. It works very
              > well in
              > > > stand alone server env (testing env). However, we cannot get it to
              work
              > on clustered
              > > > env (preprod env). Anyone has experienced working with clustered env?
              > If so,
              > > > please help!
              > > >
              > > > Thanks.
              > >
              >
              >
              

  • JMS bridge from Tibco to WLS 8.1(sp4) problems

    We have a WLS that contains a MDB for receiving messages from another system. When messages are received on the Tibco topic and are try to be delivered to the WLS, we get the exception below.
              However, if we change the MDB to connect directly to the topic in the other WLS (the publisher), the message is received fine. Also, when using the Tibco bridge, if we use a simple command-line client to place a simple text-based message on the message topic, it is delivered to our server just fine.
              Is this an authentication related issue? If so, then why does it work when the WLS servers are linked directly, but not when Tibco server is being used as bridge between them?
              The publisher of the message is running on Linux, and the subscriber on Windows/XP. The Tibco server on Solaris and is v4.2.
              Thanks,
              Craig
              <Nov 1, 2005 4:11:02 PM MST> <Warning> <MessagingBridge> <BEA-200026> <Bridge "MyMessaging Bridge" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was java.lang.Exception
              : javax.resource.ResourceException: Error sending message
              at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1339
              at weblogic.jms.adapter.JMSBaseConnection.send(JMSBaseConnection.java:654)
              at weblogic.jms.adapter.JMSConnectionHandle.send(JMSConnectionHandle.java:144)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
              at java.lang.reflect.Method.invoke(Method.java:324)
              at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:149)
              at $Proxy8.send(Unknown Source)
              at weblogic.jms.bridge.internal.MessagingBridge.onMessageInternal(MessagingBridge.java:1258)
              at weblogic.jms.bridge.internal.MessagingBridge.onMessage(MessagingBridge.java:1181)
              at weblogic.jms.adapter.JMSBaseConnection$27.run(JMSBaseConnection.java:1943)
              at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
              at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
              at weblogic.jms.adapter.JMSBaseConnection.onMessage(JMSBaseConnection.java:1939)
              at com.tibco.tibjms.TibjmsSession._submit(TibjmsSession.java:3567)
              at com.tibco.tibjms.TibjmsSession._dispatchAsyncMessage(TibjmsSession.java:1963)
              at com.tibco.tibjms.TibjmsSession$Dispatcher.run(TibjmsSession.java:3098)
              -------------- Linked Exception ------------
              javax.resource.ResourceException: Error creating producer or sending message
              at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1339
              at weblogic.jms.adapter.JMSBaseConnection.sendInternal(JMSBaseConnection.java:719)
              at weblogic.jms.adapter.JMSBaseConnection.access$200(JMSBaseConnection.java:80)
              at weblogic.jms.adapter.JMSBaseConnection$6.run(JMSBaseConnection.java:647)
              at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
              at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
              at weblogic.jms.adapter.JMSBaseConnection.send(JMSBaseConnection.java:644)
              at weblogic.jms.adapter.JMSConnectionHandle.send(JMSConnectionHandle.java:144)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
              at java.lang.reflect.Method.invoke(Method.java:324)
              at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:149)
              at $Proxy8.send(Unknown Source)
              at weblogic.jms.bridge.internal.MessagingBridge.onMessageInternal(MessagingBridge.java:1258)
              at weblogic.jms.bridge.internal.MessagingBridge.onMessage(MessagingBridge.java:1181)
              at weblogic.jms.adapter.JMSBaseConnection$27.run(JMSBaseConnection.java:1943)
              at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
              at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
              at weblogic.jms.adapter.JMSBaseConnection.onMessage(JMSBaseConnection.java:1939)
              at com.tibco.tibjms.TibjmsSession._submit(TibjmsSession.java:3567)
              at com.tibco.tibjms.TibjmsSession._dispatchAsyncMessage(TibjmsSession.java:1963)
              at com.tibco.tibjms.TibjmsSession$Dispatcher.run(TibjmsSession.java:3098)
              .)>

    We have a WLS that contains a MDB for receiving messages from another system. When messages are received on the Tibco topic and are try to be delivered to the WLS, we get the exception below.
              However, if we change the MDB to connect directly to the topic in the other WLS (the publisher), the message is received fine. Also, when using the Tibco bridge, if we use a simple command-line client to place a simple text-based message on the message topic, it is delivered to our server just fine.
              Is this an authentication related issue? If so, then why does it work when the WLS servers are linked directly, but not when Tibco server is being used as bridge between them?
              The publisher of the message is running on Linux, and the subscriber on Windows/XP. The Tibco server on Solaris and is v4.2.
              Thanks,
              Craig
              <Nov 1, 2005 4:11:02 PM MST> <Warning> <MessagingBridge> <BEA-200026> <Bridge "MyMessaging Bridge" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was java.lang.Exception
              : javax.resource.ResourceException: Error sending message
              at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1339
              at weblogic.jms.adapter.JMSBaseConnection.send(JMSBaseConnection.java:654)
              at weblogic.jms.adapter.JMSConnectionHandle.send(JMSConnectionHandle.java:144)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
              at java.lang.reflect.Method.invoke(Method.java:324)
              at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:149)
              at $Proxy8.send(Unknown Source)
              at weblogic.jms.bridge.internal.MessagingBridge.onMessageInternal(MessagingBridge.java:1258)
              at weblogic.jms.bridge.internal.MessagingBridge.onMessage(MessagingBridge.java:1181)
              at weblogic.jms.adapter.JMSBaseConnection$27.run(JMSBaseConnection.java:1943)
              at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
              at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
              at weblogic.jms.adapter.JMSBaseConnection.onMessage(JMSBaseConnection.java:1939)
              at com.tibco.tibjms.TibjmsSession._submit(TibjmsSession.java:3567)
              at com.tibco.tibjms.TibjmsSession._dispatchAsyncMessage(TibjmsSession.java:1963)
              at com.tibco.tibjms.TibjmsSession$Dispatcher.run(TibjmsSession.java:3098)
              -------------- Linked Exception ------------
              javax.resource.ResourceException: Error creating producer or sending message
              at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1339
              at weblogic.jms.adapter.JMSBaseConnection.sendInternal(JMSBaseConnection.java:719)
              at weblogic.jms.adapter.JMSBaseConnection.access$200(JMSBaseConnection.java:80)
              at weblogic.jms.adapter.JMSBaseConnection$6.run(JMSBaseConnection.java:647)
              at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
              at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
              at weblogic.jms.adapter.JMSBaseConnection.send(JMSBaseConnection.java:644)
              at weblogic.jms.adapter.JMSConnectionHandle.send(JMSConnectionHandle.java:144)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
              at java.lang.reflect.Method.invoke(Method.java:324)
              at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:149)
              at $Proxy8.send(Unknown Source)
              at weblogic.jms.bridge.internal.MessagingBridge.onMessageInternal(MessagingBridge.java:1258)
              at weblogic.jms.bridge.internal.MessagingBridge.onMessage(MessagingBridge.java:1181)
              at weblogic.jms.adapter.JMSBaseConnection$27.run(JMSBaseConnection.java:1943)
              at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
              at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
              at weblogic.jms.adapter.JMSBaseConnection.onMessage(JMSBaseConnection.java:1939)
              at com.tibco.tibjms.TibjmsSession._submit(TibjmsSession.java:3567)
              at com.tibco.tibjms.TibjmsSession._dispatchAsyncMessage(TibjmsSession.java:1963)
              at com.tibco.tibjms.TibjmsSession$Dispatcher.run(TibjmsSession.java:3098)
              .)>

  • 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.
              

  • JMS Bridge is not starting up in Weblogic10

    Hi,
    I am new to Weblogic10 and I configured the JMS server and JMS bridge to send and receive the messages from MQ queues. When starting the weblogic server I am continuously getting error like,
    <21-Mar-2009 07:24:08 o'clock GMT> <Error> <MessagingBridge> <blx25ao01> <aadev100-01> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1237620248164> <BEA-200044> <The following exception has occurred:
    java.lang.AbstractMethodError: getTransactionSupport
    at weblogic.jms.bridge.internal.MessagingBridge.startInternal(MessagingBridge.java:615)
    at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1030)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    >
    Could you please help me what is the route cause for the above exception.

    Hi,
    Please remove the UME inconsistencies as advised in note 818947.
    Once done restart the server and JMS Provider service should start. Please update back regarding the result.
    Thanks & Regards,
    Vijith

  • How to Configure Selector For JMS Bridge

    Hi,
    I was trying with Selector option in working with multiple Bridges, here is the scenario i applied.
    Created five Queues ( Q1, Q2, Q3, Q4 and Q5 ) and configured JMS Bridge Destinations having each queue with unique connection factory ( CF1, CF2, CF3, CF4 and CF5 ) and named it as D1, D2, D3, D4 and D5.
    Then created JMS Bridges as JB2 with source as D1 and destination as D2. Similarly JB3 as D1-D3, JB4 as D1-D4 and JB5 as D1-D5.
    And set Sector for each of JB2, JB3, JB4 and JB5 as Two, Three, Four and Five respectively and did restart after the changes.
    Now i am expecting the following scenario to work
    Pushing message to Q1/CF1 having Two in the content of message, hence expecting the message to be delivered to Q2/CF2 through JB2, but the messages is not moved through JB2.
    Similarly, Pushed message to Q1/CF1 having Three in the content of message, hence expecting the message to be delivered to Q3/CF3 through JB3, but the messages is not moved through JB3. Similar behavior for other messages having Four and Five in the message content.
    During the bridge configuration, selected QOS as "Atmost-Once".
    Note: All the configurations were done in same domain and the WL version is 10.3.6.0.*
    The sample message i am pushing to Q1/CF1 say "Two Test Data"* and expecting to reach Queue Q2/CF2
    Regards
    Venkata Madhu
    Edited by: vv**** on Sep 12, 2012 1:05 PM

    Hi Venkata,
    The expected selector syntax is the standard SQL-like JMS syntax. There's an extensive description of the syntax in the javadoc for javax.jms.Message.
    Selectors should normally only reference message header fields and message properties. I don't normally recommend using a selector that is based on message body as this requires using a proprietary WebLogic extension based on "xpath" XML expressions, and can have an large impact on performance. (The performance hit is caused by two factors - the need for the JMS server to unmarshal/decompress/page-in the body in order to get at its contents, and the natural cost of scanning a message body to see if it matches a string.)
    HTH,
    Tom

  • Jms.bridge.TemporaryResourceException

    Folks,
              I would very grateful if anyone has seen this one:
              I'm attempting to connect to a remote weblogic server, my bridge destination is configured (as best I can see, correctly, as its a clone of a working environment on another server).
              I am receiving the following error when the server tries to connect to the Bridge destination.
              Some Points:
              1. The remote WLE has a username/password on it, they've been configured.
              2. The domain credentials have been changed to match those of the remote server.
              3. The interoperability mode are the same across the domains.
              4. The remote server is active, I have sent messages across on a client tester.
              LOG
              ####<25-Jan-2007 14:02:45 o'clock GMT> <Info> <MessagingBridge> <serverName> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1169733765045>
              <BEA-200043> <Bridge "aTOb" failed to connect to the target destination and will try again in 60 seconds. This could be a temporary condition unless the messages repeat several times. (java.lang.Exception: weblogic.jms.bridge.TemporaryResourceException
              at weblogic.jms.adapter.JMSBaseConnection.throwTempResourceException(JMSBaseConnection.java:14
              31)
              at weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnection.java:390)
              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.getTargetConnection(JMSBaseConnectionFactory.
              java:123)
              at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:854)
              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)
              )>
              ####<25-Jan-2007 14:02:46 o'clock GMT> <Info> <Console> <serverName> <AdminServer> <[ACTIVE] ExecuteThread
              : '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <

    Enable debug flags for message bridge to capture more details:
    -Dweblogic.Debug.DebugMessagingBridgeStartup=true
    -Dweblogic.Debug.DebugMessagingBridgeRuntime=true
    Edited by: atheek1 on 07-Jul-2010 03:21

  • 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?

  • JMS Bridge not Working

    Hi,
    I have a weblogic 9.2 running one application.
    I what that application to post messages on a internal JMS queue. That message gets fw to a Weblogic 8 JMS queue.
    To achieve this I created a JMS Bridge with the Weblogic 8 destination, and the Weblogic 9 source.
    When i activate the bridge, i did not see anything on the logs, so i restarted the server.
    Once the server was Up I went to check how many consumers where register on my internal queue, and to my surprise there where none.
    I posted a message to that queue and still nothing. not even on the logs.
    On the source and destination, i put the following:
    Adapter JNDI Name: the XA one
    Classpath: weblogic.jar
    Connection URL: t3://172.16.76.28:8001 on the internal and t3://172.16.76.29:7001 on the external
    weblogic.jndi.WLInitialContextFactory: weblogic.jndi.WLInitialContextFactory
    and the JNDI stuff, user and password.
    I do not see anything in the logs. Any idea?

    I would like to make sure that I understand where you are now.
    1. The bridge is always running on 9.2.
    2. When the bridge is configured to forward messages from local (9.2) to remote (8.1), everything works.
    3. When the bridge is configured to forward messages from remote to local, you run into the SecurityException.
    Is my understanding correct? Where did you see the Exception (on the 9.2 side or the 8.1 side)?
    Are you always using the adapter from the same release as the server that is running the bridge?
    Assuming that you have configured everything correctly, I don't see why remote-to-local case does not work for you. There was an issue similar to what you are seeing in 8.1 GA, which has been fixed in 8.1SP1 and 9.2. You should not see this issue as long as your bridge is running on 9.2 (or 8.1SP1) or later.
    At this point you could try the following:
    1. Change the bridge to run in sync mode (by setting AsyncEnabled to false, the default is true) and see if the problem persists.
    2. Enable domain trust on both the 9.2 and 8.2 domains (see http://edocs.bea.com/wls/docs92/bridge/wls_interop.html#wp1126213 for details).
    3. Run the bridge on 8.1 (using the 8.1 adapter) to forward messages to 9.2. (I know the doc recommends that one should run the bridge on the later version of WebLogic when forwarding between two different releases, but it does not hurt to try as long as your source destination is on the same release are the bridge).
    Thanks,
    Dongbo

Maybe you are looking for

  • Unable to run a report from developer 10g

    Hi, i can´t run a report from developer 10g when i run the report with the web icon appears the message Thu Jan 07 14:44:29 CST 2010 javax.servlet.jsp.JspException javax.servlet.jsp.JspException      at oracle.reports.jsp.ReportTag.doStartTag(ReportT

  • ICal 'to do' tasks on the iPhone 4

    So, I worked through the import/export fiasco of getting my calendars onto MobileMe appropriately, step one! Now I finally have my 'to do' tasks listed on my MobileMe account. Problem is, while the 'to do' tasks show on MobileMe.com, they do not get

  • Connecting direct to serial port

    Hi to all!! I need to connect flash direct to serial port to send and receive data. I know that i have to look for some API, but all that i fund is some other software to do the interface, but i realy need is distribut only the flash and not the flas

  • Can I make slides in slideshow larger?

    Since upgrading to iWeb '08 just yesterday, I cannot believe how much worse the photos look on the website! They seem to be less sharp and the slide show photos are not much bigger than the thumbnails. The pause button is HUGE unnecessarily, I think.

  • How can I retrieve deleted emails from the trash?

    How do I retrieve deleted emails from the trash?  I have not emptied the trash.