WLS JMS bridge not forwarding mesages

Hi All,
I want to send messages from a queue in the source weblogic domain to the target queue in another weblogic domain. Both the domains are weblogic server. On the source server agile PLM is deployed. For this communication I established JMS bridge and JMS destination on my source server. The resource adpater is deployed and active. But my bridge is not working. Is not forwarding message to the target queue on the target server.
I inspected the log files. I found the following error
"<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 =weblogic.jndi.WLInitialContextFactory, url = t3://<target_server_ip>:<port>, user name = null) "> "
Also on the monitoring tab of the JMS bridge initially it was showing message "Failed to look up the source adapter" then I deployed the resource adapter. Now on the monitoring tab its showing the message "Connected to the source" instead of shoing "Fowarding Messages" . can anyone tell me what could be the cause. Please help its really urgetnt!!!
Can anyone please tell me what can be the issue?
Thanks in Advance!!

Could you please provide the way you used the connection factory?
I am concerned about *(InitialContextFactory =weblogic.jndi.WLInitialContextFactory, url = t3://<target_server_ip>:<port>, user name = null) "> "*
Please check.
Thanks,
Jeets

Similar Messages

  • WLS JMS bridge not working

    Hi All,
    I have been looking for a solution for the last two days and this is my third post regarding JMS bridge. I configured ome JMS bridge which initially ,on the monitoring tab, was giving information "Failed to look uo the source adapter" then I deployed the resource adapter. Now on the monitoring tab its showing the message "Connected to the source" instead of shoing "Forwarding Messages" . can anyone tell me what could be thw cause. Please help its really urgetnt!!!

    Can anybody please help me?

  • 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

  • JMS Bridges not showing the right status

    I am using the weblogic 9.2 MP3 on production servers with around 300 managed servers in 7 clusters. There are around 1200 queues and 2500 JMS bridges connecting the queues to internal and external world.
    The JMS bridges on my system doesn't reflect the right status. Sometimes, it shows INACTIVE/Failed status but still keep forwarding the messages.
    Different bridge status and description that I can see:
    Inactive     Stopped by the administrator.
    Active     Forwarding messages.
    Inactive     WARN: failed to connect to the target.
    Active     Connected to the source.
    Also,
    I see lots of warnings in the logs as follows...
    ####<5/03/2013 10:33:33 AM EST> <Warning> <MessagingBridge> <HOSTNAME> <MS NAME> <[ACTIVE] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362440013003> <BEA-200026> <Bridge "BRIDGE NAME" 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 javax.resource.ResourceException: Error setting message listener.)>
    <27/01/2013 05:52:07 AM EST> <Warning> <Connector> <BEA-190024> << eis/jms/WLSConnectionFactoryJNDIXA > Error making initial connections for pool. Reason: javax.resource.ResourceException: Adapter internal error -- connectionFactory object is not instanceof ConnectionFactory>
    Any help on the issue will be appreciated...
    Thanks

    what does emctl status dbconsole show?
    Hi All,
    I have installed 10g in Win 2000. Enterprise manager
    was working fine after installation. I restarted the
    Oracle Service (DB Service, TNS, iSQL, DBControl)
    from services in Control Panel. Database is up and
    working fine but the Enterprise Manager is not
    working. When I am trying to use the EM through
    Internet Explorer, it is not asking for any login and
    showing as database as down. I am able to connect to
    DB from client PC. Please advice.

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

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

    Can anybody please help me?

  • Populating Database records to WLS JMS queue

    Hi All,
    Please suggest which is the performance effective approach in populating WLS JMS queue from the database tables?
    As I have to produce millions of records from the DB into the JMS queue and assuming using DB adapter and retreiving bulky data is a long running process.
    Please suggest whether I can write a pl/sql stored proc and populate the WLS JMS queue? or is there any other most optimistic approach to transfer data from db into WLS JMS queue?
    Thanks,
    Sudha

    Thanks Eric for the quick reply. Also, going through the other forum:
    Re: Publish message from Oracle database PL/SQL to a remote WLS JMS queue
    Just want to know which one would be performance effective one in the below whether using Java stored Procedures or populating AQ and WLS Messagin bridge?
    1) Java Stored Procedure can use JMS APIs to publish messages to WLS JMS destinations. JMS standard API jar file and WLS JMS client jars that you use need to be loaded into database.
    2) From PL/SQL, you can publish message to AQ using AQ PL/SQL APIs, then configure WLS Messaging Bridge to forward messages from AQ to WLS JMS.

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

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

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

  • 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

  • Using a  foreign WLS JMS queue (no bridge)

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

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

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

  • JMS bridge communication not working

    Hi,
    I am working on an application, Ap1, which uses Toplink as an ORM layer and also makes use of Toplink cache. The problem is that the database that this application uses
    is also used by another app, Ap2. So I need somehow to refresh Toplink cache of Ap1 when a database update is triggered by Ap2, otherwhise Ap1 will work with out of date data.
    The solution that I found is to use JMS for the communication between the 2 aps and it should work like this:
    - when Ap2 make a database update, it will add a message in a JMS topic that a MDB deployed on Ap1 listens to. And so the MDB will remove the entity from the cache.
    The thing is that A1 and A2 are deployed on different Weblogic servers so I need to have a remote JMS communication between the 2 servers.
    Ap1 is deployed on WLS1 (Weblogic 12C).
    Ap2 is deployed on WLS2 (Weblogic 11C).
    As solutions I tried to use a JMS bridge.
    on the WLS1 side I have created:
    - a JMS server, JmsServer-0
    - a JMS module, JmsModule
    - a local topic included in JmsModule and targeted to JmsServer-0
    - a ConnectionFactory included in JmsModule and targeted to JmsServer-0 (not sure if it is needed)
    - a JMS bridge with source and target configured OK (Bridge is in Active state)
    The outcome is that when Ap2 updates the database, I can see the message in Ap2 JMS server, but I can't see it in Ap1 JMS server even if the JMS bridge appears to be created OK, has state Active.
    I don't know why the message doesn't reach A1 JMS server and I don't know how to debug this problem. I am looking in the Jms Server, monitorring tab. Is there any other place Where I can get some useful info?
    I also tried using a JMS foreign server, but I had the same problem.
    Thanks for any suggestion!

    First of all, you can configure the MDB on WLS server1 to receive messages from a JMS destination that is running on WLS server2. You just need to provide the URL of the remote server.
    If you prefer using the messaging bridge, you can debug your bridge by turning on the bridge debugging flags.
    -Dweblogic.Debug.DebugMessagingBridgeStartup=true
    -Dweblogic.Debug.DebugMessagingBridgeRuntime=true
    -Dweblogic.Debug.DebugMessagingBridgeRuntimeVerbose=true
    Hope this helps.
    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 and MQSeries. looking for statistics

              Hi !
              I have to use Weblogic 7 SP4 in cluster with a distant MQSeries queue manager.
              I know I can't have a "exactly once" quality of service. I use a MDB (deplyed
              on each instance of the server).
              I'm looking for statistics about how often a message can be treated 2 (or more)
              times.
              Thanks a lot for any help !
              Florent
              

    Hi Florent,
              Since these are MQ messages, it might be possible to find
              such statistics in MQ. Also, I think that MQ stores a
              redelivery count in their messages - so you can likely
              instrument your application code to get at the count.
              Note that 7.0 actually does support exactly once with WL MDBs driven
              by MQ. If you use transactions you can infer some stats on redeliveries
              by checking the relevant transaction statistics for rollback counts.
              I'm attaching some notes on JMS integration for your
              convenience.
              Tom
              florent wrote:
              > Hi !
              >
              > I have to use Weblogic 7 SP4 in cluster with a distant MQSeries queue manager.
              > I know I can't have a "exactly once" quality of service. I use a MDB (deplyed
              > on each instance of the server).
              >
              > I'm looking for statistics about how often a message can be treated 2 (or more)
              > times.
              >
              > Thanks a lot for any help !
              >
              > Florent
              JMS Integration of Foreign Vendors with BEA WebLogic Server
              The following notes are derived mostly from "http://dev2dev.bea.com/technologies/jms/index.jsp".
              For additional questions, a good forum for WebLogic questions in general is "newsgroups.bea.com". These can be mined for information by using Google's newsgroup search function.
              JMS Integration Overview
              - For integration with "non-Java" and/or "non-JMS" platforms, see "Non-Java Integration Options" below.
              - For a foreign JMS vendor to participate in a WL transaction it must support XA. Specifically, it must support the javax.jms.XA* interfaces.
              - In WL versions 6.0 and up it is possible to make synchronous calls to foreign JMS vendors participate in a WL transaction as long as the foreign vendor supports XA.
              - WL 6.0 and 6.1 MDBs can be driven by foreign vendors non-transactionally. They can be driven transactionally by a select few foreign vendors (MQ is not part of the select few)
              - WL 7.0 and later, MDBs can be driven by foreign vendors transactionally and non-transationally.
              - WL 6.1 and later WL provides a messaging bridge feature. Messaging bridges forward messages between any two JMS destinations, including foreign destinations, and can transfer messages transactionally or non-transactionally.
              - WL 8.1 JMS provides additional features that simplify transactional and JNDI integration of foreign vendors. See http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features
              Integration with 8.1 Details
              A good overview of 8.1 JMS interop capability is the presentation "Integrating Foreign JMS Providers with BEA WebLogic Server" here:
              http://www.bea.com/content/files/eworld/presentations/Wed_03_05_03/Application_Servers/1097-Foreign_JMS_Providers_WLS.pdf
              This document refers to helpful new 8.1 features, which simplify integration. These include:
              http://edocs.bea.com/wls/docs81/ConsoleHelp/jms_config.html#accessing_foreign_providers
              http://edocs.bea.com/wls/docs81/jms/j2ee_components.html#1033768
              And are also summarized here (under interoperability):
              http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features
              Also read the extensive MDB documentation, which extensively covers integrating foreign vendors:
              http://edocs.bea.com/wls/docs81/ejb/message_beans.html
              The 8.1 features are likely sufficient for most 8.1 integration needs, and you may not need to refer "Using Foreign JMS Providers With WLS" white-paper mentioned below.
              Integration with 6.1 and 7.0 Details
              Read the "Using Foreign JMS Providers With WLS" white-paper:
              http://dev2dev.bea.com/products/wlserver/whitepapers/jmsproviders.jsp
              Note that this white-paper does not take into account 8.1 features.
              For 7.0 read the extensive 8.1 MDB documentation, which largely also applies to 7.0:
              http://edocs.bea.com/wls/docs81/ejb/message_beans.html
              Non-Java Integration Options
              - WL JMS has a JNI based C client which is available for Windows and some UNIX platforms. This C client supports 7.0 and up, and will be officially packaged with WLS in 9.0 (virtually unchanged). The C API is currently only supported through the jms newsgroup. See "JMS C API", here:
              http://dev2dev.bea.com/technologies/jms/index.jsp
              - WL supports direct Windows COM access through its "JCOM" feature. This doesn't include the JMS API, but one can invoke EJBs which in turn invoke JMS. See
              http://e-docs.bea.com/wls/docs61/jcom.html
              http://e-docs.bea.com/wls/docs70/jcom/
              http://e-docs.bea.com/wls/docs81/jcom/
              - Similar to JCOM, but more advanced, WL supports IIOP standard based access on multiple platforms. You can use the BEA Tuxedo C client for this purpose (no license fee). This doesn't include the JMS API, but one can invoke EJBs which in turn invoke JMS. See
              http://e-docs.bea.com/wls/docs81/rmi_iiop/
              http://e-docs.bea.com/wls/docs70/rmi_iiop/
              http://e-docs.bea.com/wls/docs61/rmi_iiop/
              Unlike most other approaches, the IIOP client approach also allows the client to begin and commit user (JTA) transactions (not configured).
              - If you already have a BEA Tuxedo license, one option is communicate through BEA Tuxedo (which has various APIs on Windows) and configure a WebLogic Server to respond to these requests via the WTC bridge. Search for "WTC" in the BEA docs. Unlike most other approaches, the Tuxedo API approach also allows the client to begin and commit user (JTA) transactions.
              - Another approach is to interop via web-service standards. Or even to simply to invoke a servlet on the WL server using a basic HTTP call from Windows. These in turn can invoke the JMS API. There is a white-paper on "Interoperability Study of BEA WebLogic Workshop 8.1 and Microsoft .NET 1.1 Web Services", that demonstrates web-services here:
              http://ftpna2.bea.com/pub/downloads/WebLogic-DotNet-Interop.pdf
              - Yet another approach is to use a third party product that is designed to wrap any JMS vendor. There are even open source versions. In no particular order, here are some examples: Open3 WinJMS, CodeMesh, Active JMS, SpiritSoft
              - Finally, there are .NET/C/C++ integration libraries that not specific to JMS, some examples are JNBridge, Jace, and CodeMesh.
              Notes on MQ Remote Capable XA Clients
              Until recently, IBM MQ JMS clients could not work transactionally unless they were running on the same host as their MQ server. This is a limitation unique to MQ that was relaxed with the introduction of IBM's new "WebSphere MQ Extended Transactional Client". See:
              http://publibfp.boulder.ibm.com/epubs/pdf/csqzar00.pdf
              The product is new, and for some reason, configuration of this client seems to be tricky, even when WebLogic is not involved at all. Oddly, the main sticking point seems to be simply making sure that class paths refer to the required IBM jars:
              - Required on WLS where MQ objects are bound into JNDI:
              com.ibm.mq.jar, com.ibm.mqjms.jar
              - Required only if MQ objects are bound into JNDI on a different server:
              com.ibm.mq.jar
              If there are problems when using this client, first get it to work using a pure IBM client without any BEA classes involved. Once that is working, search the WL JMS newsgroup for answers and/or contact BEA customer support.
              Notes on Oracle AQ Integration
              If problems are encountered integrating Oracle's built-in queuing (Oracle AQ) JMS client, there is publicly available wrapper code that can aid integrating AQ directly into MDBs, JMS, or the messaging bridge. The solution is titled "Startup class to bind AQ/Referenceable objects to WLS JNDI", is not supported by BEA, and is posted to:
              http://dev2dev.bea.com/codelibrary/code/startupclass.jsp
              Caveats:
              The solution doesn't directly support concurrent consumers. Perhaps Oracle requires that concurrent consumers each have a unique JMS connection? As a work-around, parallel message processing can be achieved indirectly by forwarding AQ messages into a WL JMS destination - which do support concurrent processing.
              Up-to-date versions of Oracle may be required. For more information, google search the weblogic.developer.interest.jms newsgroup for "Oracle" and "AQ".
              The solution doesn't seem to support transactions, it may be possible to extend it to do so.
              MDB Thread Pool Notes
              WL7.0SP? and WL8.1 and later support the "dispatch-policy" field to specify which thread pool an MDB uses to run its instances. In most cases this field should be configured to help address potential performance issues and/or dead-locks:
              http://edocs.bea.com/wls/docs81/ejb/DDreference-ejb-jar.html#dispatch-policy
              (Note that "dispatch-policy" is ignored for non-transactional foreign vendors; in this case, the MDB "onMessage" callback runs in the foreign vendor's thread.)
              MDB Concurrency Notes
              Queue MDBs driven by foreign providers can run multiple instances concurrently. Topic MDBs driven by foreign providers are limited to one instance (not sure, but transactional foreign driven topic MDBs may not have this limitation). The size of the thread pool that the MDB runs in and the "max-beans-in-free-pool" descriptor limit how many instances run concurrently.
              Design Guide-Lines and Performance Tuning Notes
              The "WebLogic JMS Performance Guide" white-paper contains detailed design, performance, and tuning information for Clustering, Messaging Bridge, JMS, and MDBs.
              http://dev2dev.bea.com/products/wlserver/whitepapers/WL_JMS_Perform_GD.jsp
              

  • Weblogic JMS Bridge betwwen WL 11g (10.3.3.0) and ActiveMQ 5.4.2

    Hi,
    I'm getting following warning when I try to connect two JMS Bridge Destinations (source WebLogic and destination ActiveMQ) through a Bridge.
    <Warning> <Connector> <BEA-190032> << eis/jms/WLSConnectionFactoryJNDINoTX > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: Failed to start the connection ">
    But when I test it by sending message WL does not forward that message to destination queue (ActiveMQ).
    When I try to send message individually in WL Queue and MQ Queue from POJO class to test it it works fine.
    Please find the setting details
    JMS Bridge Destination for ActiveMQ
    Adapter JNDI Name: eis.jms.WLSConnectionFactoryJNDINoTX
    Classpath: path of activemq-core-5.4.2.jar
    Connection URL: tcp://***.***.***.***:****
    Initial Context Factory: org.apache.activemq.jndi.ActiveMQInitialContextFactory
    Connection Factory JNDI Name: QueueConnectionFactory
    Destination JNDI Name: destination queue
    Destination Type: Queue
    JMS Bridge Destination for WebLogic
    Adapter JNDI Name: eis.jms.WLSConnectionFactoryJNDINoTX
    Classpath:
    Connection URL: t3://***.***.***.***:****
    Initial Context Factory: weblogic.jndi.WLInitialContextFactory
    Connection Factory JNDI Name: JNDI name of Connection Factory which is created in JMS module
    Destination JNDI Name: JNDI name of Queue which is created in JMS Module
    Destination Type: Queue
    User Name: given
    Password: given
    Thanks in advance
    Regards
    Amlendu
    Edited by: user7468329 on May 1, 2011 10:01 PM

    Hi,
    There's troubleshooting information in the bridge documentation.
    google: FAQs: WebLogic Messaging Bridge site:oracle.com
    Hope this helps.
    Tom

  • Foreign server or JMS Bridge?

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

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

Maybe you are looking for

  • After Upgrading to IOS5, iPad 1 Is No Longer Recognized by iTunes

    Hi, My iPad 1 with wifi/3G was working perfectly until I updated to iOS5. The update process seemed to have gone fine but at the end my iPad showed up in iTunes as an unrecognized device. Not only that, iTunes then gives the message: "We are unable t

  • Editting and re-jarring Jar files

    Hi. I've taken over someone else's code and I can't, for the life of me, figure out how to open the jar file in NetBeans for instance, edit some of the classes and jsp's, and then re-jar everything to deploy it. Thanks in advance for any help. Jeremy

  • Iphoto not printing full photo, cropping some photos

    After I create a photo with pixilmator or any horizontial and export to iphoto, I can see the full photo, but when i print it cuts off the edges and only prints the middle.  I have tried selecting different sizes, changing horizontial view to vertica

  • Installing Flash player in Vista 64

    I could not get player 10 to install in Vista 64 despite repeated attempts. It would fail to load a .dll to a specific directory. After repeated attempts, I realized the directory was never created by the installer. So, here's the deal: go to C:/Wind

  • I can't do photo merging or photo blending at all in Photoshop elements8

    I followed all the steps in photoblending like placing one photo over the other, clicking on the adjustment layer, using the gradient tool, clicking Cntrol G (or using a paintbrush to brush away the first layer)... nothing happens. I must have done t