Solved

Unable to connect to the server at:t3://localhost:7001

Posted on 2004-08-31
2
6,060 Views
Last Modified: 2013-12-10
i deployed a session bean at the server, and try to run a client side, and i get
the following error. i try this example both at the wls 6.0 & wls 8.1
this is the following error:


** Unable to connect to the server at:t3://localhost:7001
javax.naming.CommunicationException.  Root exception is java.net.ConnectExceptio
n: No server found at T3://localhost:7001
        at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)


<2004-9-1 &#19979;&#21320;12&#26102;51&#20998;36&#31186;> <Info> <ConnectionManager> <Bootstrap unable to get
a routed: 'Protocol: 't3'' connection to: '0S:127.0.0.1:[7001,-1,-1,-1,-1,-1,-1]
' on port: '7001'
java.rmi.ConnectException: No available router to destination

** Unable to connect to the server at:t3://localhost:7001
javax.naming.CommunicationException.  Root exception is java.net.ConnectExceptio
n: No server found at T3://localhost:7001
        at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
        at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
        at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:235)


** Unable to connect to the server at:t3://localhost:7001
javax.naming.CommunicationException.  Root exception is java.net.ConnectExceptio
n: No server found at T3://localhost:7001
        at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
        at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
        at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:235)

0
Comment
Question by:she1
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 4

Accepted Solution

by:
illusionz70 earned 50 total points
ID: 11950393
replace localhost with the ip address of the machine where weblogic has been installed and try again...
also try
http://localhost:7001
0
 

Author Comment

by:she1
ID: 11951248
my client like the following: thanks, it use the default initial context.

package com.learnweblogic.examples.ch8.helloworld;

import com.learnweblogic.examples.BaseClient;

import javax.naming.Context;
import javax.naming.NamingException;
import javax.rmi.PortableRemoteObject;

public final class HelloWorldClient extends BaseClient {

  private Context ctx;

  HelloWorldClient(String [] argv)
    throws NamingException
  {
    super(argv);

    ctx = getInitialContext();

  }

  public void runClient()
    throws Exception
  {
   
    HelloWorldHome home = null;

    try {
      Object h = ctx.lookup("HelloWorldEJB");

      home = (HelloWorldHome)
        PortableRemoteObject.narrow(h, HelloWorldHome.class);
    } catch (NamingException ne) {
      System.err.println("Unable to lookup the HelloWorld EJB.");
      System.err.println("Please make sure that the bean has been deployed"+
        ", and the client's classpath has been set correctly.");

      throw ne;
    }

    try {
      HelloWorld hw = home.create();

      System.out.println("Say Hello to EJB.");

      String ejbSays = hw.helloWorld();

      System.out.println("The EJB said: "+ejbSays);
    } catch (Exception e) {
      System.err.println("Received an unexpected exception " + e
        + " while using the HelloWorldEJB.");

      throw e;
    }
  }

  public static void main(String[] argv)
    throws Exception
  {
    HelloWorldClient hwc = new HelloWorldClient(argv);

    hwc.runClient();

  }
}

0

Featured Post

How our DevOps Teams Maximize Uptime

Our Dev teams are like yours. They’re continually cranking out code for new features/bugs fixes, testing, deploying, responding to production monitoring events and more. It’s complex. So, we thought you’d like to see what’s working for us. Read the use case whitepaper.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Java Application is Unable to connect to correct schema(Error : 404) 11 93
splunk tool 1 80
oneTwo java challenge 31 702
listing all functions in JavaScript 19 254
Configure Web Service (server application) I. Configure security for Web Services methods First, we need to protect Session bean which implements the service: 1. Open EJB deployment descriptor (ejb-jar.xml) in the EJB project that contains you…
Upgrading Tomcat – There are a couple of methods to upgrade Tomcat is to use The Apache Installer is to download and unzip and run the services.bat remove|install Tomcat6 Because of the App that we are working with, we can only use Tomcat 6.…

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question