First you have to add two libraries to the project, The first is the AQJMS library ( even when we don't use AQ ) and the second library is the WebLogic 10.3 thin Client
Start the weblogic server. Menu Run , Start Server Instance
The url is http://localhost:7101/console. Username weblogic password weblogic.
Default the weblogic server has an empty configuration. We need to create a new jms server with a database of file persistance. We need this for the queue or topic persistence
create a new jms system module. In this module we will create a new connection factory and queue
Select the just created jms module and create a new connection factory first.
Create a new queue
Make sure that the queue uses the jms server. See the targets this can't be empty
And here is the java code to test the connection factory and the queue
The difference with oc4j is that you use other jndi properties. This are the right properties for WebLogic 10.3 in JDeveloper 11g
java.naming.factory.initial weblogic.jndi.WLInitialContextFactory
java.naming.provider.url t3://localhost:7101
java.naming.security.principal weblogic
java.naming.security.credentials weblogic
package nl.ordina.jms;
import java.io.FileInputStream;
import java.io.FileNotFoundException;
import java.io.IOException;
import java.sql.Timestamp;
import java.util.Properties;
import javax.jms.JMSException;
import javax.jms.Queue;
import javax.jms.QueueConnection;
import javax.jms.QueueConnectionFactory;
import javax.jms.QueueReceiver;
import javax.jms.QueueSender;
import javax.jms.QueueSession;
import javax.jms.Session;
import javax.jms.TextMessage;
import javax.naming.Context;
import javax.naming.InitialContext;
public class WeblogicClient {
private QueueConnection connection = null;
private QueueSession session = null;
private QueueSender sender = null;
private QueueReceiver receiver = null;
private Queue queue = null;
private long waitTime = 0;
public WeblogicClient() {
setUp();
put();
get();
tearDown();
}
public static void main(String[] args) {
WeblogicClient weblogicClient = new WeblogicClient();
}
public void tearDown() {
try {
sender.close();
receiver.close();
session.close();
connection.close();
} catch (JMSException je) {
je.printStackTrace();
} finally {
}
}
public void get(){
try {
javax.jms.TextMessage textMessage = (javax.jms.TextMessage)receiver.receive();
System.out.println("Receiving message [" + textMessage.getJMSMessageID() + "] enqueued at " + new Timestamp(textMessage.getJMSTimestamp()).toString());
String xmlText = textMessage.getText();
System.out.println(xmlText);
} catch (JMSException jmse) {
jmse.printStackTrace();
}
}
public void put(){
String messageId = null;
String xmlData = "";
FileInputStream fis;
try {
fis = new FileInputStream("D:\\projecten\\mhs_esb\\delfor.xml");
int x= fis.available();
byte b[]= new byte[x];
fis.read(b);
xmlData = new String(b);
} catch (FileNotFoundException e) {
// TODO
} catch (IOException e) {
// TODO
}
try {
TextMessage message = session.createTextMessage(xmlData);
sender.send(message);
} catch (JMSException jmse) {
jmse.printStackTrace();
}
}
protected void setUp() {
String queueName = "jms/QTest";
String queueConnectionFactoryName = "jms/CFTest";
Context ctx;
try {
Properties parm = new Properties();
parm.setProperty("java.naming.factory.initial","weblogic.jndi.WLInitialContextFactory");
parm.setProperty("java.naming.provider.url","t3://localhost:7101");
parm.setProperty("java.naming.security.principal","weblogic");
parm.setProperty("java.naming.security.credentials","weblogic");
ctx = new InitialContext(parm);
QueueConnectionFactory connectionFactory =
(QueueConnectionFactory)ctx.lookup(queueConnectionFactoryName);
connection = connectionFactory.createQueueConnection();
connection.start();
session = connection.createQueueSession(false, Session.CLIENT_ACKNOWLEDGE);
queue = (Queue)ctx.lookup(queueName);
sender = session.createSender(queue);
receiver = session.createReceiver(queue);
} catch (JMSException je) {
throw new RuntimeException("Fout opgetreden bij het starten ",je);
} catch (Throwable t) {
throw new RuntimeException("Fout opgetreden bij het starten ",t);
}
}
}
Hi.
ReplyDeleteI have followed you example, but created a bpel process that put the msg on a topic instead of using the java code.
I get this error:
The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12141
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor jms/mdm/personCF neither through JNDI nor instantiate it as a Java class
Please examine the log file to determine the problem.
; nested exception is:
ORABPEL-12511
Do you have any suggestions?
Hi
ReplyDeleteis your BPEL also installed on the wls. If it runs on OC4J then I think you don't have the wls jms libraries installed on the OC4J.
When I try to dequeue from Oracle Service Bus I use t://localhost:7001/ConnFact/QueueName as url.
thanks, worked on first try!
ReplyDeleteWorked great, thanks!
ReplyDeleteJust two suggestions:
1- it would be great if the exception messages were written in English too.
2- the default java.naming.provider.url value uses port 7001, instead of 7101, as in the example.
I had a JMSException the first time I tried the example, but after correcting the server port, it ran smooth.
Thanks a lot!
Hi,
ReplyDeleteI have configured the JMS queue and connection factory and used the servlet code to enqueue the message in the queue. But I am getting the following error :
===================================
javax.naming.NameNotFoundException: While trying to lookup 'jms.ConnectionFactor
y-LocalQueue' didn't find subcontext 'jms'. Resolved ''; remaining name 'jms/Con
nectionFactory-LocalQueue'
===================================
I am using JDeveloper 11g and weblogic 10.3.1. Also the servlet is being used to send the message to the queue.
Please suggest
Hi,
ReplyDeleteplease check the jndi name of the CF , you must use that and check if the target on this CF is right.
thanks
Thanks Edwin. The messages are getting queued up successfully. Now , I am using BPEL process with JMS adapter to de-queue the message from the same queue. I have configured the new JNDI in the JMS adapter resource running on weblogic and using the same connection factory name that is being used in the servlet.
ReplyDeleteBut when the JMS adapter of BPEL process is making the connection to the queue. It' giving the unresloved connection factory name though being successfully able to make the connection to the JMS adpater resource running on weblogic server. The target of JMS adapter is SOA and ADMIN server.
It seems like the JMS adapter in BPEL process that is running on SOA server is not being able to make the connection to the connection facotry/queue running on admin server.
Please suggest if there any configuration part I have missed to connect two processes running on admin server and managed SOA server respectively via the same the queue.
Ok,
ReplyDeleteMake sure you connect to the CF where the queue is also located. If the CF and the queue are located on the admin server and you need to use the t3 admin url in the soa server resource adapter.
hope this helps
Edwin,
ReplyDeleteIt works from the first time.
Have only one trouble during configuration Weblogic Server (10.3.2):
After creating Server, Modules and Connection Factory it should be create a Queue (not create a Subdeployment before). So on the second step of queue creating it should be create a new Subdeployment by pushing "Create a New Subdeployment" button.
If it will not do like this then Destination will not be create for queue (Control tab of queue settings).
And on the line "connection = connectionFactory.createQueueConnection();" get the error:
--------------------------------
Caused by: javax.naming.NameNotFoundException: Exception in lookup.: `jms/Queue-0' could not be found. [Root exception is weblogic.corba.cos.naming.NamingContextAnyPackage.NotFound: IDL:weblogic/corba/cos/naming/NamingContextAny/NotFound:1.0]
---------------------------------
May be it is just a bug of 10.3.2 and it not appear on 10.3.
Hello Edwin,
ReplyDeleteI think this example is quite good for getting started with WebLogic and JMS.
I have two questions regarding the use of JMS in combination with WebLogic and WebServices.
1. Is it possible to generate the packages that are mapping to the WSDL structure based on the WSDL for JMS communication?
2. How can you pass the WSDL stack including all policy enforcement points e.g. for security in WebLogic based on JMS messages?
Thank's for you're help,
Christoph
Hi,
ReplyDeleteyou can generate a proxu client based on a wsdl. The only difference is the endpoint.
and did you see this blogpost.
http://fusionsecurity.blogspot.com/2010/05/identity-propagation-using-jms.html
thanks
Hi. I tried test your code but, JDev throws following exception: Exception in thread "main" java.lang.RuntimeException: Error al iniciar
ReplyDeleteat jms.WeblogicClient.setUp(WeblogicClient.java:117)
at jms.WeblogicClient.(WeblogicClient.java:31)
at jms.WeblogicClient.main(WeblogicClient.java:38)
Caused by: javax.naming.NameNotFoundException: Exception in lookup.: `jms/CFTest' could not be found. [Root exception is weblogic.corba.cos.naming.NamingContextAnyPackage.NotFound: IDL:weblogic/corba/cos/naming/NamingContextAny/NotFound:1.0]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:65)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:289)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:227)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at jms.WeblogicClient.setUp(WeblogicClient.java:102)
... 2 more
Caused by: weblogic.corba.cos.naming.NamingContextAnyPackage.NotFound: IDL:weblogic/corba/cos/naming/NamingContextAny/NotFound:1.0
at weblogic.corba.cos.naming.NamingContextAnyPackage.NotFoundHelper.read(NotFoundHelper.java:72)
at weblogic.corba.cos.naming._NamingContextAnyStub.resolve_any(_NamingContextAnyStub.java:87)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:267)
... 5 more
Do you can help me?
I use JDev 11.1.1.3 and WLS 10.3.3
Hi
ReplyDeleteDid you add the weblogic remote library. and put it on top.
it looks like you are missing a library.
thanks
Excellent!!!
ReplyDeleteMany Thanks!!!
Hi
ReplyDeleteI followed your example, but I get the following error. Any advice please?
Exception in thread "main" java.lang.RuntimeException: Fout opgetreden bij het starten
at jms_project.WeblogicClient.setUp(WeblogicClient.java:118)
at jms_project.WeblogicClient.(WeblogicClient.java:32)
at jms_project.WeblogicClient.main(WeblogicClient.java:39)
Caused by: javax.naming.NamingException: Unhandled exception in lookup [Root exception is org.omg.CORBA.NO_PERMISSION: vmcid: 0x0 minor code: 0 completed: No]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:83)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:291)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:227)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at jms_project.WeblogicClient.setUp(WeblogicClient.java:104)
... 2 more
Caused by: org.omg.CORBA.NO_PERMISSION: vmcid: 0x0 minor code: 0 completed: No
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at com.sun.corba.se.impl.protocol.giopmsgheaders.MessageBase.getSystemException(MessageBase.java:897)
at com.sun.corba.se.impl.protocol.giopmsgheaders.ReplyMessage_1_2.getSystemException(ReplyMessage_1_2.java:99)
at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.getSystemExceptionReply(CorbaMessageMediatorImpl.java:572)
at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.processResponse(CorbaClientRequestDispatcherImpl.java:445)
at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.marshalingComplete(CorbaClientRequestDispatcherImpl.java:339)
at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.invoke(CorbaClientDelegateImpl.java:129)
at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:457)
at weblogic.corba.cos.naming._NamingContextAnyStub.resolve_any(_NamingContextAnyStub.java:80)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:267)
Hi,
ReplyDeleteDon't know this error, Can you please check the t3 url and username / password.
And maybe some targeting issues on your cf / queue or jms servers
thanks
I have encountered by following problem. Can anyone help me?
ReplyDeleteException in thread "main" java.lang.RuntimeException: Fout opgetreden bij het starten
at client.WeblogicClient.setUp(WeblogicClient.java:117)
at client.WeblogicClient.(WeblogicClient.java:30)
at client.WeblogicClient.main(WeblogicClient.java:37)
Caused by: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7101: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:787)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:366)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.(InitialContext.java:197)
at client.WeblogicClient.setUp(WeblogicClient.java:100)
... 2 more
Caused by: java.net.ConnectException: t3://localhost:7101: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination
at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:216)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:345)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)
... 10 more
Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:464)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:315)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:254)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteCluster(RJVMFinder.java:316)
at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:205)
... 16 more
Hi,
ReplyDeleteAre you connecting with a jms client to the WebLogic server. if so then your WebLogic server is not on your own machine and not running on port 7101
hope this helps
thanks
HI
ReplyDeleteI have configured weblogic and run your code but its giving following error:
Exception in thread "main" java.lang.RuntimeException: Fout opgetreden bij het starten
at client.WeblogicClient.setUp(WeblogicClient.java:117)
at client.WeblogicClient.(WeblogicClient.java:30)
at client.WeblogicClient.main(WeblogicClient.java:37)
Caused by: javax.naming.AuthenticationException [Root exception is java.lang.SecurityException: User: weblogic, failed to be authenticated.]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:42)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:787)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:681)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:469)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:376)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.(InitialContext.java:197)
at client.WeblogicClient.setUp(WeblogicClient.java:100)
... 2 more
Caused by: java.lang.SecurityException: User: weblogic, failed to be authenticated.
at weblogic.common.internal.RMIBootServiceImpl.authenticate(RMIBootServiceImpl.java:119)
at weblogic.common.internal.RMIBootServiceImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
can you help
Hi,
ReplyDeleteOk you got now a security exception. in the new Weblogic edition the default password = weblogic1
So change this.
parm.setProperty("java.naming.security.credentials","weblogic1");
thanks
Ur blog post on creating a jms client on jdev was excellent! thanks a lot.
ReplyDeleteHi This is good one but we wanted to post the message to remote jms queue but its having with gets stuck at code connection = connectionFactory.createQueueConnection(); just stays at that line... like waiting for something that never comes out.
ReplyDeleteAny idea on this please?
Hi,
ReplyDeleteplease check the jndi names of the CF and off course the settings of the CF , is the targetting ok.
Also you can set rmi and timeout parameters on the context
thanks
I already verified on that way.Anyway can you pls add that code snippet for pushing JMS message to Remote queues.
ReplyDeleteThank you very much
Hi,
ReplyDeleteare you using a java client to add a message to a queue. or doing it from an other j2ee server.
in the java client you need to change the localhost / port in parm.setProperty("java.naming.provider.url","t3://localhost:7101");
hope this helps
hi
ReplyDeletejavax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://10.44.235.38:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:792)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:366)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.(InitialContext.java:197)
at com.persistent.commons.impl.ServerConnectivity.trailConnectivity(ServerConnectivity.java:44)
at com.persistent.commons.impl.ServerConnectivity.main(ServerConnectivity.java:64)
Caused by: java.net.ConnectException: t3://10.44.235.38:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination
at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:216)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:165)
at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:345)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)
... 9 more
Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:470)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:321)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:260)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
... 15 more
Process exited with exit code 0.
C:\Oracle\Middleware\jdk160_24\bin\javaw.exe -client -classpath
ReplyDeletecom.persistent.commons.impl.ServerConnectivity
javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://10.44.235.38:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:792)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:366)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.(InitialContext.java:197)
at com.persistent.commons.impl.ServerConnectivity.trailConnectivity(ServerConnectivity.java:44)
at com.persistent.commons.impl.ServerConnectivity.main(ServerConnectivity.java:64)
Caused by: java.net.ConnectException: t3://10.44.235.38:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination
at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:216)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:165)
at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:345)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)
... 9 more
Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:470)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:321)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:260)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
... 15 more
Process exited with exit code 0.