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

Similar Messages

When restarting server after a crash, Messaging bridges are not starting

Hi,
We have Messaging bridge configured with Exactly-Once QOS to read messages from IBM Websphere MQ to Weblogic distributed Queue. We are using Weblogic 10gR3.
1. We killed the weblogic server which was reading message from source destination(IBM MQ). We did this to check whether any message is lost when a server crashes.
2. Then we restarted the weblogic application server and checked the weblogic messaging bridge status.
3. The messaging bridge was not started properly and the following Exception was thrown.
####<Apr 22, 2010 4:09:11 PM BST> <Error> <MessagingBridge> <machineA> <desb03-ms11> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-056A9014D88E2BE368B7> <> <12312323333> <BEA-200015> <An error occurred in bridge "BRIDGE" 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': XAER_RMFAIL : Resource manager is unavailable
javax.transaction.xa.XAException: Internal error: XAResource 'eis/jms/WLSConnectionFactoryJNDIXA' is unavailable
at weblogic.transaction.internal.XAResourceDescriptor.checkResource(XAResourceDescriptor.java:941)
at weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResourceDescriptor.java:630)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1182)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1116)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:275)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:511)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:438)
at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:118)
at weblogic.connector.outbound.ConnectionWrapper.invoke(ConnectionWrapper.java:218)
at $Proxy87.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)
.).>
####<Apr 22, 2010 4:09:11 PM BST> <Warning> <MessagingBridge> <machineA> <desb03-ms11> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1271948951881> <BEA-200026> <Bridge "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 weblogic.jms.bridge.internal.MessagingBridgeException.)>
####<Apr 22, 2010 4:09:12 PM BST> <Info> <MessagingBridge> <machineA> <desb03-ms11> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1271948952726> <BEA-200020> <Bridge "BRIDGE" is stopped.>
Please give your suggestions to fix this issue.
Thanks!
Edited by: user11340353 on 28-Apr-2010 06:34

Hi,
*The server was started in warning mode and the JTA was declared unhealthy. I saw 2 transaction alive for more than 2000 seconds which is uncommon.
*The resource adaptor was started properly.
*We are using file store. But will it make a difference?
Thanks!

Bridge still not starting in CS6 (extended)

Same issue; bridge will not start. As of this date, this is the second install of CS6. The first was a download and the second was from a disk. Bridge will not start ! I had Ps v 7 on here and that was removed as was the download copy. The problem is still here?!?

If you happen to be on a Mac running Mountain Poop (10.8.x) try re-installing the OS after you have installed CS6.
There have been reports that installing CS6 messes with some Mountain Poop files.

JMS Internal Error at Server Client Adapter!JMS Service is not started

Hi
Can any one tell me how to trouble shoot for following errors:
Failed to Create Connection! Reason: Response from the server could not be reached.
JMS Internal Error at Server Client Adapter!JMS Service is not started
The following hosts could not be reached 143:223:221:10:50310
We are trying to send the request from SONICMQ JMS to R/3 and trying to post the response to Sonic Queue. but we are facing some problems for JMS adapter .
but in JMS sender and receiver adapter i gave different IP and port for listen the SONIC queue. why it is showing in different IP here? this message got from logviewer.
regards
Rambarki...

Rambarki,
What is the error displayed on the Adapter Monitoring pages?
Generally the correct error descriptions for connectivity issues are found on adapter monitoring UI than any other.
Other possible reasons could be :
<i>JMS Service is not started
The following hosts could not be reached 143:223:221:10:50310</i> This might be issue with your network settings i.e. XI server is unable to reach the specified IP on specified port.
Regards,
Amol

Javax.jms.JMSException: QueueConnection not started

Hi,
I want use oc4j like jms server, so I put in jms.xml this configuration :
<jms-server port="9127">
<queue-connection-factory location="jms/simpleQueueConnectionFactory" port="9127" host="127.0.0.1"/>
<queue name="Simple Queue" location="jms/simpleQueue"/>
</jms-server>
and I try to post a message to JMS server with my webapp, and one exception occured :
javax.jms.JMSException: QueueConnection not started
this is my piece of code which post the JMS message (like example on http://otn.oracle.com/sample_code/tech/java/codesnippet/j2ee/p2p/PointToPoint_in_OC4J.html) :
QueueConnectionFactory connectionFactory = (QueueConnectionFactory)new InitialContext().lookup ("java:comp/env/jms/simpleQueueConnectionFactory");
QueueConnection connection = connectionFactory.createQueueConnection();
connection.start();
QueueSession queueSession = connection.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
Queue queue = (Queue)new InitialContext().lookup("java:comp/env/jms/simpleQueue");
QueueSender sender = queueSession.createSender(queue);
Message message = queueSession.createMessage();
message.setJMSType("theMessage");
message.setLongProperty("time", System.currentTimeMillis());
message.setStringProperty("subject", "Test Message Now");
message.setStringProperty("message", "Hi");
sender.send(message);
How can I get more JMS log ? because in jms.log I have only :
25/10/02 12:04 9.0.3.0.0 Started
25/10/02 12:05 9.0.3.0.0 Stopped (JVM termination)
My start command line for oc4j is (http://otn.oracle.com/tech/java/oc4j/htdocs/oc4j-logging-debugging-technote.html):
java -Djms.debug=true -jar oc4j.jar -userThreads -verbosity 5
thank you
best regards
jerome

Hi Jerome,
At this time Oracle recommends you use OJMS (AQ/JMS) as the J2EE 1.3 compatible JMS provider in Oracle9iAS v9.0.2 and v9.0.3. A future release of 9iAS will contain a lightweight JMS provider (OC4J/JMS) that is J2EE 1.3 compatible.
See the Metalink note below...
http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=205305.1

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

Bridge will not start in Mountain Lion

I originally had this problem with Lion but a reinstall of the system cleared things up. Now since installing Mountain Lion Bridge bounces once in the dock and thats it. There is not even a recognition there was a crash.

So, I've been having a problem very like this and perhaps can offer a bit of insight. At least I found what was going south for me.
My problem looked like this: Start Bridge and there'd be a flicker of a window followed by a dialog with "Bridge is unable to perform this action" (or words to that effect) followed by a crash.
After reading this thread I tried the previously-unknown-to-me OPTION start. That didn't fix the problem but it did eliminate the crash!
Interesting.
Now this problem began for me when I upgraded to Mountain Lion a while ago. After that my system began to become increasingly unstable. When I bought a large SSD to be my system volume I thought it would be a good time to do a clean install of everything.
That went well, actually. Bridge worked in the new account I created! Wonderful! But I needed to use Migration Assistant to bring over my old account which had existed, more or less unchanged, since OS X 10.0! But then I began to have the same kind of instability I had seen before: Finder crashing, Path Finder crashing, and Bridge not working although the other Adobe products including Lightroom 4 worked just fine.
So I poked around and here's what I found: different Groups. In older versions of OS X the user account was a part of group Wheel. This time it was a part of group Staff. Different group numbers. Hmmm. So I started at the top level directory of Users where all the accounts live and I changed the Group, recursively, to Staff.
And then Bridge worked fine and there were no more Finder crashes, at least until I shut down for the night.
So you might want to check both ownership, group and permissions in your accounts and see if this is a part of the probem.
Why Mountain Lion (or maybe even Lion) changed the assigned Group for new accounts I cannot explain although, as I was walking the critters tonight and gazing up at the just-past-full moon, I wondered if it isn't because OS X Server can be installed as a layer over ML and this is a part of that compatibility.
Now I do think that by changing the whole tree heirarchy I may have changed invisible files that shouldn't have been modified. But for right now I'll live with that and see what happens.
Now I just have to try to get Microsoft Office 2011 to install...argh!

Bridge will not start.

Hi all,
I have Adobe Bridge CS3, Windows Vista ultimate 32bit. When I start bridge from the desktop shortcut, or in the programs folder I get this error message "The procedure entry point sqlite3_prepare_v2 could not be located in the dynamiclink library SQLite3.dll."
Any ideas?
Thank you
josel

Hi,
Yes done that, but the error message appears, I press the cancel button on the error message and bridge then loads up, but no preference screen appears.
Thank you once again
josel

Bridge CC not starting. Have uninstalled/reinstalled multiple times.

Hi,
Is anyone else having this issue? When I try to boot up Bridge CC nothing happens. I've tried uninstalling it and reinstalling it multiple times to no avail.
Thank you!

Is anyone else having this issue?
first try this:
You might first want to try restarting Bridge holding down option (mac) or control (win) key and choose reset preferences.
otherwise provide more details:
read this for a start:
http://forums.adobe.com/thread/375816?tstart=0

Bridges monitoring not showing the newly configured Bridges

Hi all,
We have two WebLogic JMS- WebLogic JMS bridges to configure, we did with the appropriate XA based bridges with QoS as "Exactly-once". Both Source and Target Message destinations are defined as per the definitions and also configured Connection Factory separately configured for XA based messages. it is assigned to respective source and target connection factories. After doing every step that required for configuration of Bridges. When we clicked the monitoring tab these 2 bridges are not visible in the list. Strange thing!
Wehave configured another 8 bridges to MQ Series, the are visible in the monitoring tab but they are showing Warn messge "unable to connect to target".
WebLogic 10.3.5.0 version (11g)
Operating environment: Oracle Enterprise Linux 5
Anyone have such experiance in bridge configuration?
Please suggest what we are missing in the configuration? is there any bug? Security concern?

Hi,
Ideally if configuration is proper and connectivity to source and target destination available it should appear in monitoring tab.
Did you checked is bridge is started? You can check if " JMS Bridge > Configuration [General] > Started " is checked or not.
Thanks,
Ranjan

CS3 Bridge will not open on G5 quad and 10.5.2

Yesterday I installed 10.5.2 on my MacBook Pro and G5 quad. Once I got all my photoshop updates in order on the MacBook Pro both Photoshop and Bridge appear to work fine.
However, on my quad, which was up-to-date on Photoshop and Bridge, Bridge will not start up; it merely bounces on the dock for a bit and then even that stops and Bridge never opens up. Photoshop appears to be working fine.
On a Apple Mac forum it was suggested I look at version cue, but I do not want to go there without asking for more advice. I am afraid to make a big mess out of things.

Try asking in the Bridge forum.
Also see if it works in a new user.

Bridge CS6 bug: closing Bridge does NOT end process

Bridge does NOT started at boot.
Windows 7 -64 (all current updates).
Photoshop CS6 13.0 extended
Bridge 5.0.0 399x64
After closing Bridge by clicking on the Close X or file/exit, the process 'bridge.exe' does not terminate and therefore thereafter trying to restart bridge fails.
Have to open up Task Manager, kill the bridge.exe process, in order to restart bridge.
The bug is so variable that just when it appears repeatable, something changes.
Any idea of what to look for?

This is NOT TRUE. "FYI: In Windows, to exit a program/application, clicking the Close button in the upper-right corner of the program window is the same as using the File menu, and click Exit."
If you click the red X you close the window and force close of the program. Any changes you made to program will not be saved if you have the option "start Bridge at login" checked. If you click File>Exit the program will go through the procedure to normally close down, and any changes you made will be saved.
I tried to follow your steps but was confused on steps 3,4,5,8,10.
I used 1,2,3,7,9,11. Bridge was closed. Perhaps with all your "browse to bridge you are opening multiple copies?
Hey, how about trying and commenting on my problem with the Find function in CS6? http://forums.adobe.com/thread/1007726?tstart=0

Com.sap.aii.adapter.jdbc.svc and com.sap.aii.adapter.jms.svc don't start

Hello,
In order to configure JMS Receiver Adapter to access Websphere Application Server 7.0, I have recently deployed file com.sap.aii.adapter.lib.sca with the following libraries:
com.sap.aii.adapter.lib_api.jar
com.ibm.ws.ejb.thinclient_7.0.0.jar
com.ibm.ws.orb_7.0.0.jar
com.ibm.ws.sib.client.thin.jms_7.0.0.jar
com.ibm.ws.runtime.jar
javax.j2ee.jms.jar
The communication channel can reach the queue but when I send a message it fails because services sap.com/com.sap.aii.adapter.jdbc.svc and com.sap.aii.adapter.jms.svc are not started.
Checking dev_server0 file I found the following error.
==============================================================================================
Service com.sap.aii.adapter.jdbc.svc start ================= ERROR =================
com.sap.engine.frame.ServiceException: Could not obtain an initial context due to a communication failure. Since no provider
URL was specified, the default provider URL of "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService" was used. Make sure that any
bootstrap address information in the URL is correct and that the target name server is running. Possible causes other than
an incorrect bootstrap address or unavailable name server include the network environment and workstation network configurati
on.
at com.sap.aii.adapter.jdbc.SapAdapterServiceFrameImpl.start(SapAdapterServiceFrameImpl.java:151)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:155)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:113)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:60)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:162)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:260)
Caused by: javax.naming.ServiceUnavailableException: Could not obtain an initial context due to a communication failure. Sinc
e no provider URL was specified, the default provider URL of "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService" was used. Make
sure that any bootstrap address information in the URL is correct and that the target name server is running. Possible caus
es other than an incorrect bootstrap address or unavailable name server include the network environment and workstation netwo
rk configuration. [Root exception is org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=sapdpi-lpar,
port=2809 vmcid: 0x4942f000 minor code: 3586 completed: No]
at com.ibm.ws.naming.util.WsnInitCtxFactory.mapInitialReferenceFailure(WsnInitCtxFactory.java:2228)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getWsnNameService(WsnInitCtxFactory.java:1414)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootContextFromServer(WsnInitCtxFactory.java:944)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:865)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:545)
at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:242)
at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:255)
at javax.naming.InitialContext.rebind(InitialContext.java:367)
at javax.naming.InitialContext.rebind(InitialContext.java:367)
at com.sap.aii.adapter.jdbc.SapAdapterServiceFrameImpl.start(SapAdapterServiceFrameImpl.java:100)
... 6 more
Caused by: org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=sapdpi-lpar,port=2809 vmcid: 0x4942f0
00 minor code: 3586 completed: No
at com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConnectionBase.java:425)
at com.ibm.ws.orbimpl.transport.WSTransport.getConnection(WSTransport.java:436)
at com.ibm.CORBA.transport.TransportBase.getConnection(TransportBase.java:187)
at com.ibm.rmi.iiop.TransportManager.get(TransportManager.java:89)
at com.ibm.rmi.iiop.GIOPImpl.getConnection(GIOPImpl.java:120)
at com.ibm.rmi.iiop.GIOPImpl.locate(GIOPImpl.java:209)
at com.ibm.rmi.corba.Corbaloc.locateUsingINS(Corbaloc.java:307)
at com.ibm.rmi.corba.Corbaloc.resolve(Corbaloc.java:378)
at com.ibm.rmi.corba.ORB.objectURLToObject(ORB.java:3721)
at com.ibm.CORBA.iiop.ORB.objectURLToObject(ORB.java:3256)
at com.ibm.rmi.corba.ORB.string_to_object(ORB.java:3619)
at com.ibm.ws.naming.util.WsnInitCtxFactory.stringToObject(WsnInitCtxFactory.java:1524)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getWsnNameService(WsnInitCtxFactory.java:1389)
... 16 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:522)
at java.net.Socket.connect(Socket.java:470)
at java.net.Socket.<init>(Socket.java:367)
at java.net.Socket.<init>(Socket.java:180)
at com.ibm.ws.orbimpl.transport.WSTCPTransportConnection.createSocket(WSTCPTransportConnection.java:270)
at com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConnectionBase.java:354)
... 28 more
Service com.sap.aii.adapter.jms.svc start ================= ERROR =================
com.sap.engine.frame.ServiceRuntimeException: Could not obtain an initial context due to a communication failure. Since no pr
ovider URL was specified, the default provider URL of "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService" was used. Make sure t
hat any bootstrap address information in the URL is correct and that the target name server is running. Possible causes othe
r than an incorrect bootstrap address or unavailable name server include the network environment and workstation network conf
iguration.
at com.sap.aii.adapter.jms.core.service.AdapterServiceFrameImpl.bindAdapter(AdapterServiceFrameImpl.java:171)
at com.sap.aii.adapter.jms.core.service.AdapterServiceFrameImpl.start(AdapterServiceFrameImpl.java:125)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:155)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:113)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:60)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:162)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:260)
Caused by: javax.naming.ServiceUnavailableException: Could not obtain an initial context due to a communication failure. Sinc
e no provider URL was specified, the default provider URL of "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService" was used. Make
sure that any bootstrap address information in the URL is correct and that the target name server is running. Possible caus
es other than an incorrect bootstrap address or unavailable name server include the network environment and workstation netwo
rk configuration. [Root exception is org.omg.CORBA.TRANSIENT: Connection state: State: ABORT (5) vmcid: 0x4942f000 minor co
de: 775 completed: No]
at com.ibm.ws.naming.util.WsnInitCtxFactory.mapInitialReferenceFailure(WsnInitCtxFactory.java:2228)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getWsnNameService(WsnInitCtxFactory.java:1414)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootContextFromServer(WsnInitCtxFactory.java:944)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:865)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:545)
at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:242)
at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:255)
at javax.naming.InitialContext.rebind(InitialContext.java:367)
at javax.naming.InitialContext.rebind(InitialContext.java:367)
at com.sap.aii.adapter.jms.core.service.AdapterServiceFrameImpl.bindAdapter(AdapterServiceFrameImpl.java:163)
... 7 more
Caused by: org.omg.CORBA.TRANSIENT: Connection state: State: ABORT (5) vmcid: 0x4942f000 minor code: 775 completed: No
at com.ibm.rmi.iiop.Connection.checkEstablished(Connection.java:3091)
at com.ibm.rmi.iiop.Connection.send(Connection.java:2145)
at com.ibm.rmi.iiop.Connection._locate(Connection.java:463)
at com.ibm.rmi.iiop.Connection.locate(Connection.java:439)
at com.ibm.rmi.iiop.GIOPImpl.locate(GIOPImpl.java:219)
at com.ibm.rmi.corba.Corbaloc.locateUsingINS(Corbaloc.java:307)
at com.ibm.rmi.corba.Corbaloc.resolve(Corbaloc.java:378)
at com.ibm.rmi.corba.ORB.objectURLToObject(ORB.java:3721)
at com.ibm.CORBA.iiop.ORB.objectURLToObject(ORB.java:3256)
at com.ibm.rmi.corba.ORB.string_to_object(ORB.java:3619)
at com.ibm.ws.naming.util.WsnInitCtxFactory.stringToObject(WsnInitCtxFactory.java:1524)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getWsnNameService(WsnInitCtxFactory.java:1389)
... 17 more
==============================================================================================
Could anyone tell me why is trying to connect to "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService"? Do I have to configure a default provider URL for SAP PI server? If so, where I configure it? Any help will be appreciated.
Thank you in advance.
Roger Allué i Vall

Hi Roger,
we also experience the same issue and would be very keen to understand how you resolved this problem.
Many thanks.
Dieter

[SOLVED] Network bridge fails to start after systemd update

Hello,
After rebooting with the upgraded systemd (208-11 -> 210-2) by bridge could not start.
journal
Mar 06 00:08:45 myhost systemd[1]: Job sys-subsystem-net-devices-enp2s0.device/start timed out.
Mar 06 00:08:45 myhost systemd[1]: Timed out waiting for device sys-subsystem-net-devices-enp2s0.device.
Mar 06 00:08:45 myhost systemd[1]: Dependency failed for My network bridge with DHCP.
Mar 06 00:08:45 myhost systemd[1]: Starting Network.
Mar 06 00:08:45 myhost systemd[1]: Reached target Network.
# cat /etc/systemd/system/[email protected]
.include /usr/lib/systemd/system/[email protected]
[Unit]
Description=My network bridge with DHCP
BindsTo=sys-subsystem-net-devices-enp2s0.device
After=sys-subsystem-net-devices-enp2s0.device
# cat /etc/netctl/br0
Description="My network bridge with DHCP"
Interface=br0
Connection=bridge
BindsToInterfaces=(enp2s0)
IP=dhcp
Commenting out BindsTo and After in the unit file allows to start the service, but it would still throw an error
Mar 06 00:14:05 myhost systemd[1]: Starting My network bridge with DHCP...
Mar 06 00:14:05 myhost network[732]: Starting network profile 'br0'...
Mar 06 00:14:05 myhost kernel: Bridge firewalling registered
Mar 06 00:14:05 myhost systemd-udevd[739]: Could not apply link config to br0
I never renamed interfaces, it was always the system-assigned enp2s0.
What could have become wrong?
Last edited by aya (2014-03-11 14:31:31)

aya wrote:I do use a custom kernel and I did not have CONFIG_FHANDLE enabled. I wish it was posted as an announcement or something.
From the 210 release announcement:
systemd 210 announcement wrote:
Heya,
And here's the next release 210:
http://www.freedesktop.org/software/sys … 210.tar.xz
<snip>
Oh, and one reminder that kinda got lost when we announced 209: you have
to enable CONFIG_FHANDLE in your kernel to use systemd >= 209
successfully, otherwise udev won't find any devices.
<snip>

JMS Bridge is not starting up in Weblogic10

Similar Messages

Maybe you are looking for