• RELEVANCY SCORE 4.56

    DB:4.56:Unable To Start Stand-Alone Web Server mc






    Folowing error message received while attempting to start web server:
    C:\java -classpath %CLASSPATH%;c:\bea\weblogic700\server\lib\weblogic.jar weblogic.Admin
    -url localhost:7001 -username abari -pas
    sword abarihol START myserver
    Failed to connect to t3://localhost:7001 due to:[javax.naming.CommunicationException
    [Root exception is java.net.ConnectException:
    t3://localhost:7001: Destination unreachable; nested exception is:
    java.net.ConnectException: Connection refused: connect; No available router
    to destination]]

    DB:4.56:Unable To Start Stand-Alone Web Server mc

    Looks like there is no server running.

    "Connection refused"

    mbg

    "Arkady Bari" abari@vertexinc.com wrote in message
    news:3d517337$1@newsgroups.bea.com...

    Folowing error message received while attempting to start web server:
    C:\java -classpath %CLASSPATH%;c:\bea\weblogic700\server\lib\weblogic.jarweblogic.Admin
    -url localhost:7001 -username abari -pas
    sword abarihol START myserver
    Failed to connect to t3://localhost:7001 dueto:[javax.naming.CommunicationException
    [Root exception is java.net.ConnectException:
    t3://localhost:7001: Destination unreachable; nested exception is:
    java.net.ConnectException: Connection refused: connect; No
    available router to destination]

  • RELEVANCY SCORE 4.45

    DB:4.45:Unable To Create Application Server Connection Using Jdevloper 11g 9d





    In process to deploy BPEL projects, I want to create a application server connection in JDevloper 11g.
    I have configured a WebLogic domain.

    While creating a application server connection in JDev, it gives me the following errors.

    Testing JSR-88 ... failed.
    [J2EE Deployment SPI:260010]Unable to connect to 't3://localhost:7001' as user, 'weblogic'. Error received: null
    Testing JSR-88-LOCAL ... failed.
    [J2EE Deployment SPI:260010]Unable to connect to 't3://localhost:7001' as user, 'weblogic'. Error received: null
    Testing JNDI ... failed.
    t3://localhost:7001: Destination unreachable; nested exception is:
    java.net.ConnectException: Connection refused: connect; No available router to destination
    Testing JSR-160 DomainRuntime ... failed.
    t3://localhost:7001: Destination unreachable; nested exception is:
    java.net.ConnectException: Connection refused: connect; No available router to destination
    Testing JSR-160 Runtime ... failed.
    t3://localhost:7001: Destination unreachable; nested exception is:
    java.net.ConnectException: Connection refused: connect; No available router to destination
    Testing JSR-160 Edit ... failed.
    t3://localhost:7001: Destination unreachable; nested exception is:
    java.net.ConnectException: Connection refused: connect; No available router to destination
    Testing HTTP ... failed.
    Unable to open conection: Connection refused: connect
    Testing Server MBeans Model ... failed.
    t3://localhost:7001: Destination unreachable; nested exception is:
    java.net.ConnectException: Connection refused: connect; No available router to destination

    0 of 8 tests successful.

    Please let me know if someone can help me.

    Really appreciate your help.

    Thanks,
    Mac

    DB:4.45:Unable To Create Application Server Connection Using Jdevloper 11g 9d

    The link document suggested is a tutorial for building a web app.

    Nothing to do with deploying web apps from JDeveloper to the Weblogic Server which is a hornets nest of confusion. I wonder why Oracle or BEA doesn't have a streamlined option for simple web apps running on one machine. Node Manager is documented as being optional but when you create and use a Managed Server it won't start unless Node Manager is running as a service in Windows Vista.

    I'm trying to find a tutorial that deploys a simple web app. No Beans, No Database usage. Just an Applet and an HTML page to launch the Applet.
    Right out of Java in easy steps book. Runs in the IDE with no problems.

    I can deploy a desktop app with an Applet to a JAR and run it with the JRE no problem.

    As an app that will now be a WAR and deployed on a Managed Server of the domain I created in Weblogic 10.3 no go...............

    The latest is I get the following message from JDeveloper attempting the deploy.

    [04:32:45 PM] ---- Deployment started. ----
    [04:32:45 PM] Target platform is (Weblogic 10.3).
    [04:32:45 PM] #### Deployment incomplete. ####
    [04:32:45 PM] [J2EE Deployment SPI:260010]Unable to connect to 't3://localhost:7003' as user, 'weblogic'. Error received: Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'weblogic.management.mbeanservers'
    [04:32:45 PM] [J2EE Deployment SPI:260010]Unable to connect to 't3://localhost:7003' as user, 'weblogic'. Error received: Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'weblogic.management.mbeanservers'
    [04:32:45 PM] [J2EE Deployment SPI:260010]Unable to connect to 't3://localhost:7003' as user, 'weblogic'. Error received: Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'weblogic.management.mbeanservers'
    [04:32:45 PM] Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'weblogic.management.mbeanservers'
    [04:32:45 PM] Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'weblogic.management.mbeanservers'
    [04:32:45 PM] Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'weblogic.m

    Now when I tried to create an application connection with which the deploy will work I got failures on DomainRunTime.
    i don't know what the DomainRunTime is. No apparent mention of these in the Weblogic documentation for configuring
    the domains and Managed Servers. The seem to be connected however.

    Any thoughts on these Mbeanservers.domainruntime things? Again the web app is just an Applet with an HTML for the Applet launch.

    Thanks,

  • RELEVANCY SCORE 4.43

    DB:4.43:Inconsistent Behavior From Servelt's Init Method. px





    Hi,
    I am using a servlet which is initialized at start up, and it tries to
    make a t3connection to the server in the init method (t3.connect(), with the
    url like t3://localhost:7001 or http://localhost:7001) and it actually is
    successfully most of time(the server starts listening at 7001 after this!),
    some times it fails in Solaris boxes.

    I am surprised it is successful sometimes!!. why does it work sometimes?

    Any help is appreciated

    regards
    viswa.

    DB:4.43:Inconsistent Behavior From Servelt's Init Method. px

    Hi,
    I am using a servlet which is initialized at start up, and it tries to
    make a t3connection to the server in the init method (t3.connect(), with the
    url like t3://localhost:7001 or http://localhost:7001) and it actually is
    successfully most of time(the server starts listening at 7001 after this!),
    some times it fails in Solaris boxes.

    I am surprised it is successful sometimes!!. why does it work sometimes?

    Any help is appreciated

    regards
    viswa.

  • RELEVANCY SCORE 4.13

    DB:4.13:Javax.Naming.Communicationexception 77


    Hello all , I am making a JMS application where in i am unable to get a context object . The following exception is thrown

    Could not create JNDI API context: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
    java.net.ConnectException: Connection refused: connect; No available router to destination]

    Can anyone explain the reason and for this ? and the fix for it .

    DB:4.13:Javax.Naming.Communicationexception 77

    It's a network routing problem. Talk to your netadmin.

  • RELEVANCY SCORE 4.11

    DB:4.11:Jndi Connection To Java J2ee Server mx


    I am new to JNDI and trying to run some examples on Sun J2EE server. I am using env.put(Context.PROVIDER_URL, "ldap://localhost:7001/"); as a paramete but it is giving exception :
    javax.naming.CommunicationException: localhost:7001 [Root exception is java.net.ConnectException: Connection refused: connect] . Pl let me know the problem.

    DB:4.11:Jndi Connection To Java J2ee Server mx

    new code :
    Hashtable env = new Hashtable();
    env.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.jndi.ldap.LdapCtxFactory");
    env.putContext.PROVIDER_URL, "ldap://hpnsez10.india.ipolicynet.com:7676/");
    Context jndi = new InitialContext(env);

    Error that i am getting :
    Hashtable env = new Hashtable();
    env.put(Context.INITIAL_CONTEXT_FACTORY,
    "com.sun.jndi.ldap.LdapCtxFactory");

    env.put(Context.PROVIDER_URL, "ldap://hpnsez10.india.ipolicynet.com:389/");

    out.println("1");

    Context jndi = new InitialContext(env);

  • RELEVANCY SCORE 4.10

    DB:4.10:Jaas Sample Program In Weblogic 6.0 Sp2 Giving Java.Lang.Securityexception: Unable To Locate A Login Exception 93



    i am tried to run the sample program in weblogic with the following commands after
    editing server.policy file in weblogic\lib folder.
    D:\beac:\jdk1.3\jre\bin\java examples.security.jaas.SampleClient
    t3://localhost :7001
    giving following out put---------
    java.lang.SecurityException: Unable to locate a login configuration
    at com.sun.security.auth.login.ConfigFile.getAppConfigurationEntry(Confi
    gFile.java:221)
    at javax.security.auth.login.LoginContext.init(LoginContext.java:172)
    at javax.security.auth.login.LoginContext.init(LoginContext.java:319)
    at examples.security.jaas.SampleClient.main(examples/security/jaas/Sampl
    eClient.java:73)

    1)what is the reason for this error and is it needed to edit
    server.policy file..?
    pls reply me ASAP

    DB:4.10:Jaas Sample Program In Weblogic 6.0 Sp2 Giving Java.Lang.Securityexception: Unable To Locate A Login Exception 93


    on runnig the program during the call of method
    Authenticate.authenticate(env, subject);
    giving following exceptions
    Error: Login Exception on authenticate, java.lang.SecurityException: attempting
    to add an object which is not an instance of java.security.Principal to a Subjec
    t's Principal Set
    Authentication Failed: Unexpected Exception, javax.security.auth.login.LoginExce
    ption: java.lang.SecurityException: attempting to add an object which is not an
    instance of java.security.Principal to a Subject's Principal Set
    javax.security.auth.login.LoginException: javax.security.auth.login.LoginExcepti
    on: java.lang.SecurityException: attempting to add an object which is not an ins
    tance of java.security.Principal to a Subject's Principal Set
    at examples.security.jaas.SampleLoginModule.login(SampleLoginModule.java
    :192)
    at java.lang.reflect.Method.invoke(Native Method)
    at javax.security.auth.login.LoginContext.invoke(LoginContext.java:595)
    at javax.security.auth.login.LoginContext.access$000(LoginContext.java:1
    25)
    at javax.security.auth.login.LoginContext$3.run(LoginContext.java:531)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java
    :528)
    at javax.security.auth.login.LoginContext.login(LoginContext.java:449)
    at examples.security.jaas.SampleClient.main(SampleClient.java:96)
    1)what is the reason for this problem
    2)in weblogic document they told to edit server.policy file
    in webligic\lib folder
    a)what the modification is needed in this file..?

  • RELEVANCY SCORE 3.94

    DB:3.94:A Question For Oracle Xsu m7


    Hi,

    Our environment: weblogic server 5.1 Oracle8i

    Now we want use Oracle XML SQL Utility for Java(XSU) to retrieve data in
    XML format from database directly. The following code run in server side:

    InitialContext ctx= null;
    new weblogic.jdbc20.jts.Driver();
    Connection conn =
    DriverManager.getConnection("jdbc20:weblogic:jts:oraclePool");
    Statement stmt = conn.createStatement();
    ResultSet rset = stmt.executeQuery(sqlString);
    OracleXMLQuery oracleXMLQuery = new OracleXMLQuery(conn,rset);
    XMLString = oracleXMLQuery.getXMLString();
    ...

    At the beginning , we use the version XSU111 which only support JDBC 1.x,
    everything is right. Later, because we must use some new method in JDBC2.0,
    we upgrade the XSU version from 111 to 12 and meanwhile change the source
    code:

    ...
    Statement stmt =
    conn.createStatement(ResultSet.TYPE_SCROLL_INSENSITIVE,ResultSet.CONCUR_READ
    _ONLY);
    ResultSet rset = stmt.executeQuery(sqlString);
    OracleXMLQuery oracleXMLQuery = new OracleXMLQuery(conn,rset);
    XMLString = oracleXMLQuery.getXMLString();
    ...

    But then oracleXMLQuery can't be created any more.

    At last, we tried to use the same env in the client side: XSU12 JDBC2.0
    Oracle connection pool

    T3Client t3 = new T3Client("t3://localhost:7001");
    t3.connect();
    Properties t3props = new Properties();
    t3props.put("weblogic.t3", t3);
    t3props.put("weblogic.t3.connectionPoolID", "oraclePool");
    Class.forName("weblogic.jdbc20.t3.Driver").newInstance();
    conn =
    (weblogic.jdbc20.t3.Connection)DriverManager.getConnection("jdbc20:weblogic:
    t3",t3props);
    conn.cacheRows(0);
    Statement stmt =
    conn.createStatement(ResultSet.TYPE_SCROLL_INSENSITIVE,ResultSet.CONCUR_READ
    _ONLY);
    ResultSet rset = stmt.executeQuery(sqlString);
    OracleXMLQuery qry = new OracleXMLQuery(conn,rset);
    String xmlString = qry.getXMLString();

    It can work!

    I don't know the reason is the diffrence between server side and client
    side, or t3 and jts(pool).

    Can anyone help us? Thanks a lot.

    DB:3.94:A Question For Oracle Xsu m7

    Hi,

    Our environment: weblogic server 5.1 Oracle8i

    Now we want use Oracle XML SQL Utility for Java(XSU) to retrieve data in
    XML format from database directly. The following code run in server side:

    InitialContext ctx= null;
    new weblogic.jdbc20.jts.Driver();
    Connection conn =
    DriverManager.getConnection("jdbc20:weblogic:jts:oraclePool");
    Statement stmt = conn.createStatement();
    ResultSet rset = stmt.executeQuery(sqlString);
    OracleXMLQuery oracleXMLQuery = new OracleXMLQuery(conn,rset);
    XMLString = oracleXMLQuery.getXMLString();
    ...

    At the beginning , we use the version XSU111 which only support JDBC 1.x,
    everything is right. Later, because we must use some new method in JDBC2.0,
    we upgrade the XSU version from 111 to 12 and meanwhile change the source
    code:

    ...
    Statement stmt =
    conn.createStatement(ResultSet.TYPE_SCROLL_INSENSITIVE,ResultSet.CONCUR_READ
    _ONLY);
    ResultSet rset = stmt.executeQuery(sqlString);
    OracleXMLQuery oracleXMLQuery = new OracleXMLQuery(conn,rset);
    XMLString = oracleXMLQuery.getXMLString();
    ...

    But then oracleXMLQuery can't be created any more.

    At last, we tried to use the same env in the client side: XSU12 JDBC2.0
    Oracle connection pool

    T3Client t3 = new T3Client("t3://localhost:7001");
    t3.connect();
    Properties t3props = new Properties();
    t3props.put("weblogic.t3", t3);
    t3props.put("weblogic.t3.connectionPoolID", "oraclePool");
    Class.forName("weblogic.jdbc20.t3.Driver").newInstance();
    conn =
    (weblogic.jdbc20.t3.Connection)DriverManager.getConnection("jdbc20:weblogic:
    t3",t3props);
    conn.cacheRows(0);
    Statement stmt =
    conn.createStatement(ResultSet.TYPE_SCROLL_INSENSITIVE,ResultSet.CONCUR_READ
    _ONLY);
    ResultSet rset = stmt.executeQuery(sqlString);
    OracleXMLQuery qry = new OracleXMLQuery(conn,rset);
    String xmlString = qry.getXMLString();

    It can work!

    I don't know the reason is the diffrence between server side and client
    side, or t3 and jts(pool).

    Can anyone help us? Thanks a lot.

  • RELEVANCY SCORE 3.94

    DB:3.94:Weblogic With Soa T3://Soaebs.Iwarlogic.Com:7001 Destination Unreachable 9k


    Hello,

    I just installed WebLogic 10.3.4 on RHEL 5.4 and then SOASuite 11.1.1.5.0
    Created a weblogic domain yo_domain with EM, SOA and BPM selected, had only Admin server in the domain and no Managed server(s).

    When I go to location
    /home/oracle/Oracle/Middleware/user_projects/domains/yo_domain/bin

    and do
    ./setDoaminEnv.sh and then
    ./startWebLogic.sh

    I get following exception
    Unable to connect to the Oracle WSM Policy manager due to following error
    "javax.naming.CommunicationException [ Root exception is java.net.ConnectException: t3://soaebs.iwarelogic.com:7001: Destination unreachable; nested exceptio nis:
    java.net.ConnectException: Connection refused; No available router to destination]".

    soaebs.iwarelogic.com is the machine name and has correct entry in /etc/hosts file

    I am able to connect to both
    http://soaebs.iwarelogic.com:7001/console and
    http://soaebs.iwarelogic.com:7001/em

    What can be cause of this error?
    When domain got created, message dialogue said
    Admin Server Url is "http://soaebs.iwarelogic.com:7001"

    regards, Yora

    DB:3.94:Weblogic With Soa T3://Soaebs.Iwarlogic.Com:7001 Destination Unreachable 9k

    Hello,

    I just installed WebLogic 10.3.4 on RHEL 5.4 and then SOASuite 11.1.1.5.0
    Created a weblogic domain yo_domain with EM, SOA and BPM selected, had only Admin server in the domain and no Managed server(s).

    When I go to location
    /home/oracle/Oracle/Middleware/user_projects/domains/yo_domain/bin

    and do
    ./setDoaminEnv.sh and then
    ./startWebLogic.sh

    I get following exception
    Unable to connect to the Oracle WSM Policy manager due to following error
    "javax.naming.CommunicationException [ Root exception is java.net.ConnectException: t3://soaebs.iwarelogic.com:7001: Destination unreachable; nested exceptio nis:
    java.net.ConnectException: Connection refused; No available router to destination]".

    soaebs.iwarelogic.com is the machine name and has correct entry in /etc/hosts file

    I am able to connect to both
    http://soaebs.iwarelogic.com:7001/console and
    http://soaebs.iwarelogic.com:7001/em

    What can be cause of this error?
    When domain got created, message dialogue said
    Admin Server Url is "http://soaebs.iwarelogic.com:7001"

    regards, Yora

  • RELEVANCY SCORE 3.91

    DB:3.91:Error T3 Connection ps


    i am getting the following error while trying to access session bean..java.rmi.RemoteException: Exception thrown in ejbCreate(); nested exception is: [Root exception is java.io.IOException: Bootstrap unable to get a t3 connection to localhost/127.0.0.1]javax.naming.CommunicationException[Root exception is java.io.IOException: Bootstrap unable to get a t3 connectionto localhost/127.0.0.1]javax.naming.CommunicationExceptioncan anyone help me...thanx in advance

    DB:3.91:Error T3 Connection ps

    i am getting the following error while trying to access session bean..java.rmi.RemoteException: Exception thrown in ejbCreate(); nested exception is: [Root exception is java.io.IOException: Bootstrap unable to get a t3 connection to localhost/127.0.0.1]javax.naming.CommunicationException[Root exception is java.io.IOException: Bootstrap unable to get a t3 connectionto localhost/127.0.0.1]javax.naming.CommunicationExceptioncan anyone help me...thanx in advance

  • RELEVANCY SCORE 3.83

    DB:3.83:Where Is The Class Of 'Userinfo'? 8c


    i am new to weblogic JMS. i try out the example(bea\wlserver_10.3\samples\server\examples\src\examples\jms\queue) given by weblogic server in the server machine it work fine, 't3://localhost:7001'. But when i try to connect from other machine to weblogic JMS it have problem, the 't3://ServerIP:7001' parameter. The following is the exception it throw.

    Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/security/acl/UserInfo
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
    at javax.naming.InitialContext.init(InitialContext.java:223)
    at javax.naming.InitialContext.init(InitialContext.java:197)
    at examples.jms.queue.MviQueueSend.getInitialContext(MviQueueSend.java:122)
    at examples.jms.queue.MviQueueSend.main(MviQueueSend.java:89)

    Please help me.
    Thanks.

    DB:3.83:Where Is The Class Of 'Userinfo'? 8c

    Sorry for my late reply because i am busy with some other things for last few weeks.

    My problem solve. It because of the wlfullclient.jar not added into classpath.

    I am following the below step to create a wlfullclient.jar
    http://edocs.bea.com/wls/docs100/client/jarbuilder.html

    A Million Thanks.

  • RELEVANCY SCORE 3.80

    DB:3.80:Using Weblogic Jdbc Driver 33


    Hi,

    When i am trying to run...

    utils.t3dbping t3://localhost:7001 "" "" "" COM.cloudscape.core.JDBCDriver jdbc:cloudscape:demo

    i get the following error...

    Connecting to WebLogic with the WebLogic JDBC Driver
    Can't connect with the WebLogic JDBC driver:
    weblogic.rmi.UnexpectedException: Marshalling:
    - with nested exception:
    [weblogic.rmi.UnmarshalException: While providing boot service
    - with nested exception:
    [java.io.NotSerializableException: weblogic.common.internal.LogOutputStream]]

    please help!!!

    regards,
    S.C.Jothi

    DB:3.80:Using Weblogic Jdbc Driver 33

    Hi.

    Not sure what your environment is, but on WLS 5.1 I can execute this same command fine. The one
    thing I am doing that may be different from your setup is that I have a recent service pack
    installed on WLS AND I have the main service pack jar file also in the front of the classpath for
    the t3dbping process.

    Michael

    scjothi wrote:

    Hi,

    When i am trying to run...

    utils.t3dbping t3://localhost:7001 "" "" "" COM.cloudscape.core.JDBCDriver jdbc:cloudscape:demo

    i get the following error...

    Connecting to WebLogic with the WebLogic JDBC Driver
    Can't connect with the WebLogic JDBC driver:
    weblogic.rmi.UnexpectedException: Marshalling:
    - with nested exception:
    [weblogic.rmi.UnmarshalException: While providing boot service
    - with nested exception:
    [java.io.NotSerializableException: weblogic.common.internal.LogOutputStream]]

    please help!!!

    regards,
    S.C.Jothi--
    Michael Young
    Developer Relations Engineer
    BEA Support

    [att1.html]

  • RELEVANCY SCORE 3.64

    DB:3.64:Alert Purge Wlst Script 3s


    All,

    I just wanted to share a WLST script I wrote that will purge old ALSB alerts older than 'n' days. Enjoy.

    -John

    ----------------------------
    import sys

    # Usage:
    #
    # java weblogic.WLST deleteAlerts.py url username password keep_days
    #
    # eg, following will deleteAlerts older than 'n' days from the ALSB Alerts
    #
    # Example:
    # java weblogic.WLST deleteAlerts.py t3://localhost:7001 weblogic weblogic 2
    #

    def getParam(pos, default):
    value=None
    try:
    value=sys.argv[pos]
    except:
    value=default
    return value

    url = getParam(1, "t3://localhost:7001")
    user = getParam(2, "weblogic")
    password = getParam(3, "weblogic")
    days = Integer(getParam(4, "2")).intValue() # need to do this because the ARGs are strings.

    connect(user,password,url)
    now=System.currentTimeMillis()
    startTime=0
    endTime=(now - days*3600*24*1000)

    serverRuntime()

    print "Deleting records older than", days, "days old from ALSB Alerts"
    alsbAlerts = cmo.getWLDFRuntime().getWLDFAccessRuntime().lookupWLDFDataAccessRuntime('CUSTOM/com.bea.wli.monitoring.alert')
    numDeleted = alsbAlerts.deleteDataRecords(startTime,endTime,"")
    print "Number deleted =", numDeleted

    disconnect()----------------------------

    --
    Edited by jgraves at 10/11/2007 9:00 PM

    DB:3.64:Alert Purge Wlst Script 3s

    John,
    thank you for sharing the code with the community. I am sure it will be usefull to a lot of people.
    Dev2Dev has a placeholder for product samples. Samples usually come from BEA employees but everybody can contribute.
    You can find more details at:
    https://codesamples.projects.dev2dev.bea.com/

    --
    Gregory Haardt
    ALSB Prg. Manager
    ghaardt@bea.com

  • RELEVANCY SCORE 3.63

    DB:3.63:Java Client Calls Getting Failed To Connect To Weblogic Server a1


    Hi,

    We are having issue in TIBCO iProcess EAI JAVA Plugin where we are getting below mentioned error. Can some help us regarding where in the weblogic.jar default rmi://127.0.0.1:10021/server and t3://localhost:7001 are defined.

    Configuration of New Environment:-
    (Server1) Weblogic: 11g
    (Server2)iProcess 11.1.3
    (Server2)TIBCO iProcess Java Server Plugin 11.2.0.0
    (Server2)TIBCO iProcess BusinessWorks Plugin 11.2.0.0
    (Server3)DB Servers SQL 2008
    All servers on Windows 2008 Servers

    *****Error Log******
    2011-12-12 13:10:40,065 [INFO ] SWJMXUtils - Starting connector

    2011-12-12 13:10:46,138 [ERROR] SWJMXUtils - Unable to start RMI connector

    java.io.IOException: Cannot bind to URL [rmi://127.0.0.1:10021/server]: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
    java.net.ConnectException: Connection refused: connect; No available router to destination]
    at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:804)
    at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:417)
    at com.staffware.eaicommon.runtime.library.jmx.SWJMXUtils.initialiseListenerSystem(SWJMXUtils.java:370)
    at com.staffware.eaicommon.runtime.library.jmx.SWJMXUtils.initialise(SWJMXUtils.java:319)
    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:597)
    at com.staffware.eaijava.bootstrap.library.SWEAIJavaClassLoader.initialiseJMX(SWEAIJavaClassLoader.java:443)
    at com.staffware.eaijava.bootstrap.library.SWEAIJavaClassLoader.initialize(SWEAIJavaClassLoader.java:339)
    Caused by: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost: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:787)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:368)
    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.init(InitialContext.java:197)
    at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:619)
    at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:412)
    ... 8 more
    Caused by: java.net.ConnectException: t3://localhost: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:153)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:353)
    ... 17 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)
    ... 20 more
    2011-12-12 13:10:46,140 [ERROR] SWEAIJavaClassLoader - Unable to initialise JMX

    java.lang.reflect.InvocationTargetException
    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:597)
    at com.staffware.eaijava.bootstrap.library.SWEAIJavaClassLoader.initialiseJMX(SWEAIJavaClassLoader.java:443)
    at com.staffware.eaijava.bootstrap.library.SWEAIJavaClassLoader.initialize(SWEAIJavaClassLoader.java:339)
    Caused by: com.staffware.eaicommon.runtime.library.jmx.SWJMXException: Unable to start RMI connector
    at com.staffware.eaicommon.runtime.library.jmx.SWJMXUtils.initialiseListenerSystem(SWJMXUtils.java:385)
    at com.staffware.eaicommon.runtime.library.jmx.SWJMXUtils.initialise(SWJMXUtils.java:319)
    ... 6 more
    Caused by: java.io.IOException: Cannot bind to URL [rmi://127.0.0.1:10021/server]: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
    java.net.ConnectException: Connection refused: connect; No available router to destination]
    at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:804)
    at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:417)
    at com.staffware.eaicommon.runtime.library.jmx.SWJMXUtils.initialiseListenerSystem(SWJMXUtils.java:370)
    ... 7 more
    Caused by: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost: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:787)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:368)
    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.init(InitialContext.java:197)
    at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:619)
    at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:412)
    ... 8 more
    Caused by: java.net.ConnectException: t3://localhost: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:153)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:353)
    ... 17 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)
    ... 20 more
    2011-12-12 13:10:46,151 [FATAL] SWEAIJavaClassLoader - Failed to initialise class loader

    Regards,
    Suraj

    DB:3.63:Java Client Calls Getting Failed To Connect To Weblogic Server a1

    I would suggest that you double check two things.
    1. if the WebLogic server is running and which ports it listens to (you can check the server log file).
    2. check the WebLogic client jar that you use on the TIBCO side. It seems that you are using weblogic.jar. Please be aware that you can only use weblogic.jar from a full WebLogic installation. In other words, you should not move/copy weblogic.jar to a different places. For information about all WebLogic standalone client jars, please refer to
    http://docs.oracle.com/cd/E17904_01/web.1111/e13717/basics.htm#i1062773

  • RELEVANCY SCORE 3.63

    DB:3.63:Jndi Errors On Bootstrap?? 3d


    I'm having trouble making connections through code to our Oracle
    ConnectionPool. Below is the error:
    javax.naming.CommunicationException [Root exception is
    java.net.ConnectException: t3://localhost:7001: Bootstrap unable to get a t3
    connection to localhost/127.0.0.1]

    Can anyone explain (at least partly) what this message means? I have not
    been able to find anything useful regarding this problem (yet). Weblogic
    can connect to Oracle just fine, but whenever the code tries to connect, it
    gets an error. Specifically, the ctx object is always null (it can't seem
    to connect).

    I know nothing about configuring JNDI in weblogic, and the guy who used to
    do this stuff doesn't work here anymore. Any suggestions are welcome,

    Thanks,
    Greg

    DB:3.63:Jndi Errors On Bootstrap?? 3d

    I'm having trouble making connections through code to our Oracle
    ConnectionPool. Below is the error:
    javax.naming.CommunicationException [Root exception is
    java.net.ConnectException: t3://localhost:7001: Bootstrap unable to get a t3
    connection to localhost/127.0.0.1]

    Can anyone explain (at least partly) what this message means? I have not
    been able to find anything useful regarding this problem (yet). Weblogic
    can connect to Oracle just fine, but whenever the code tries to connect, it
    gets an error. Specifically, the ctx object is always null (it can't seem
    to connect).

    I know nothing about configuring JNDI in weblogic, and the guy who used to
    do this stuff doesn't work here anymore. Any suggestions are welcome,

    Thanks,
    Greg

  • RELEVANCY SCORE 3.62

    DB:3.62:Problem When I Starting Weblogic Server Under Eclipse Suddenly Stop 7p


    Hi everyone:

    I've a problem, I'm working with IDE Eclipse 3.2 and weblogic server 8.1 I need to debug the application, when I'm trying to start the server and everything look fine and almost at the end suddenly the server stop with this message:

    Stopping Weblogic Server...

    Failed to connect to t3://localhost:7001: Destination unreachable; nested exception is:
    java.net.ConnectException: Connection refused; No available router to destination

    please I need Help.

    Thanks in advance

    DB:3.62:Problem When I Starting Weblogic Server Under Eclipse Suddenly Stop 7p

    hi jprivas,

    i am having the same problem (but with wls 9.0). please, can you share with us how you solved your problem?

    many thanks

  • RELEVANCY SCORE 3.62

    DB:3.62:Starting A Newly Created Server s9


    Hi there,

    I have created a new server in the 'mydomain' domain called 'server1' using
    the admin console. To do this of course the admin server is running. When
    attempting to start the new server I run the 'startManagedServer' script
    with the parameters for the new server as follows:

    startManagedServer server1 http://localhost:7001

    the server then requests for the password (which I assume is the password
    for the admin server corresponding to the 'system' user)

    Entering the password I get the following stack trace and the server exits.
    It appears that I am unable to connect to the admin server for some reason.
    Any Ideas??

    ...
    Starting WebLogic Server ....
    Connecting to http://127.0.0.1:7001...
    22-Jan-01 11:29:15 GMT Info Logging Only log messages of severity
    "Error"
    or worse will be displayed in this window. This can be changed at Admin
    Console
    mydomain Servers sparzaserver Logging Debugging Stdout severitythreshold

    22-Jan-01 11:29:15 GMT Error Configuration Management Error
    connecting to
    admin server and initializing admin home: admin URL: t3://127.0.0.1:7001
    java.lang.NullPointerException
    at
    weblogic.security.acl.Security.getPasswordGuessing(Security.java:674)

    at weblogic.security.acl.Realm.authenticate(Realm.java:181)
    at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:229)
    at
    weblogic.security.acl.internal.Security.authenticate(Security.java:11
    3)
    at
    weblogic.security.acl.internal.Security.authenticate(Security.java:90
    )
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialConte
    xtFactoryDelegate.java:430)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialCon
    textFactoryDelegate.java:272)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
    tialContextFactoryDelegate.java:244)
    at weblogic.jndi.Environment.getContext(Environment.java:133)
    at weblogic.jndi.Environment.getInitialContext(Environment.java:116)
    at
    weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:797)
    at weblogic.management.Admin.start(Admin.java:292)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
    at weblogic.Server.main(Server.java:35)

    22-Jan-01 11:29:15 GMT Emergency Server Unable to initialize the
    server:
    'Fatal initialization exception
    Throwable: weblogic.management.configuration.ConfigurationException: admin
    URL:
    t3://127.0.0.1:7001 - with nested exception:
    [java.lang.NullPointerException]
    weblogic.management.configuration.ConfigurationException: admin URL:
    t3://127.0.
    0.1:7001 - with nested exception:
    [java.lang.NullPointerException]
    at
    weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:802)
    at weblogic.management.Admin.start(Admin.java:292)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
    at weblogic.Server.main(Server.java:35)
    '
    ***************************************************************************
    The WebLogic Server did not start up properly.
    Exception raised: weblogic.management.configuration.ConfigurationException:
    admi
    n URL: t3://127.0.0.1:7001 - with nested exception:
    [java.lang.NullPointerException]
    java.lang.NullPointerException
    at
    weblogic.security.acl.Security.getPasswordGuessing(Security.java:674)

    at weblogic.security.acl.Realm.authenticate(Realm.java:181)
    at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:229)
    at
    weblogic.security.acl.internal.Security.authenticate(Security.java:11
    3)
    at
    weblogic.security.acl.internal.Security.authenticate(Security.java:90
    )
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialConte
    xtFactoryDelegate.java:430)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialCon
    textFactoryDelegate.java:272)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
    tialContextFactoryDelegate.java:244)
    at weblogic.jndi.Environment.getContext(Environment.java:133)
    at weblogic.jndi.Environment.getInitialContext(Environment.java:116)
    at
    weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:797)
    at weblogic.management.Admin.start(Admin.java:292)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
    at weblogic.Server.main(Server.java:35)
    --------------- nested within: ------------------
    weblogic.management.configuration.ConfigurationException: admin URL:
    t3://127.0.
    0.1:7001 - with nested exception:
    [java.lang.NullPointerException]
    at
    weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:802)
    at weblogic.management.Admin.start(Admin.java:292)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    ***************************************************************************

    DB:3.62:Starting A Newly Created Server s9

    uh-duh...

    The newly created server was trying to listen at the default port 7001,
    which of course is where the admin server was listening... :)

    "Callum Wallach" callum.wallach@sparza.com wrote in message
    news:3a6c1c2d$1@newsgroups.bea.com...
    By the way I am using Weblogic 6.0 on Windows 2000

    Thanks

    "Callum Wallach" callum.wallach@sparza.com wrote in message
    news:3a6c1bea$1@newsgroups.bea.com...
    Hi there,

    I have created a new server in the 'mydomain' domain called 'server1'using
    the admin console. To do this of course the admin server is running.When
    attempting to start the new server I run the 'startManagedServer' script
    with the parameters for the new server as follows:

    startManagedServer server1 http://localhost:7001

    the server then requests for the password (which I assume is thepassword
    for the admin server corresponding to the 'system' user)

    Entering the password I get the following stack trace and the serverexits.
    It appears that I am unable to connect to the admin server for somereason.
    Any Ideas??

    ...
    Starting WebLogic Server ....
    Connecting to http://127.0.0.1:7001...
    22-Jan-01 11:29:15 GMT Info Logging Only log messages of severity
    "Error"
    or worse will be displayed in this window. This can be changed at Admin
    Console
    mydomain Servers sparzaserver Logging Debugging Stdout severitythreshold

    22-Jan-01 11:29:15 GMT Error Configuration Management Error
    connecting to
    admin server and initializing admin home: admin URL:t3://127.0.0.1:7001
    java.lang.NullPointerException
    at
    weblogic.security.acl.Security.getPasswordGuessing(Security.java:674)

    at weblogic.security.acl.Realm.authenticate(Realm.java:181)
    atweblogic.security.acl.Realm.getAuthenticatedName(Realm.java:229)
    at
    weblogic.security.acl.internal.Security.authenticate(Security.java:11
    3)
    at
    weblogic.security.acl.internal.Security.authenticate(Security.java:90
    )
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialConte
    xtFactoryDelegate.java:430)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialCon
    textFactoryDelegate.java:272)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
    tialContextFactoryDelegate.java:244)
    at weblogic.jndi.Environment.getContext(Environment.java:133)
    atweblogic.jndi.Environment.getInitialContext(Environment.java:116)
    at
    weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:797)
    at weblogic.management.Admin.start(Admin.java:292)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
    at weblogic.Server.main(Server.java:35)

    22-Jan-01 11:29:15 GMT Emergency Server Unable to initialize the
    server:
    'Fatal initialization exception
    Throwable: weblogic.management.configuration.ConfigurationException:admin
    URL:
    t3://127.0.0.1:7001 - with nested exception:
    [java.lang.NullPointerException]
    weblogic.management.configuration.ConfigurationException: admin URL:
    t3://127.0.
    0.1:7001 - with nested exception:
    [java.lang.NullPointerException]
    at
    weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:802)
    at weblogic.management.Admin.start(Admin.java:292)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
    at weblogic.Server.main(Server.java:35)
    '***************************************************************************
    The WebLogic Server did not start up properly.
    Exception raised:weblogic.management.configuration.ConfigurationException:
    admi
    n URL: t3://127.0.0.1:7001 - with nested exception:
    [java.lang.NullPointerException]
    java.lang.NullPointerException
    at
    weblogic.security.acl.Security.getPasswordGuessing(Security.java:674)

    at weblogic.security.acl.Realm.authenticate(Realm.java:181)
    atweblogic.security.acl.Realm.getAuthenticatedName(Realm.java:229)
    at
    weblogic.security.acl.internal.Security.authenticate(Security.java:11
    3)
    at
    weblogic.security.acl.internal.Security.authenticate(Security.java:90
    )
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialConte
    xtFactoryDelegate.java:430)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialCon
    textFactoryDelegate.java:272)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
    tialContextFactoryDelegate.java:244)
    at weblogic.jndi.Environment.getContext(Environment.java:133)
    atweblogic.jndi.Environment.getInitialContext(Environment.java:116)
    at
    weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:797)
    at weblogic.management.Admin.start(Admin.java:292)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
    at weblogic.Server.main(Server.java:35)
    --------------- nested within: ------------------
    weblogic.management.configuration.ConfigurationException: admin URL:
    t3://127.0.
    0.1:7001 - with nested exception:
    [java.lang.NullPointerException]
    at
    weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:802)
    at weblogic.management.Admin.start(Admin.java:292)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception***************************************************************************

  • RELEVANCY SCORE 3.62

    DB:3.62:Unable To Create User.Xml Using Weblogicexportmetadata.Sh In Oim 11gr2 mj


    I want to export user.xml file using the $OIM_ORACLE_HOME/server/bin/weblogicImportMetadata.sh shell file.
    I have set all the necessary attributes in weblogic.properties file:
    while running the shell i get the below trace on unix:
    but the file is not getting created in the specified location, any help please...
    Initializing WebLogic Scripting Tool (WLST) ...

    Welcome to WebLogic Server Administration Scripting Shell

    Type help() for help on available commands

    Starting export metadata script ....
    Please enter your username :******
    Please enter your password :
    +Please enter your server URL [t3://localhost:7001] :t3://localhost:7001+
    Connecting to t3://localhost:7001 with userid weblogic ...
    Successfully connected to Admin Server 'AdminServer' that belongs to domain 'oimdomain'.

    Warning: An insecure protocol was used to connect to the
    server. To ensure on-the-wire security, the SSL port or
    Admin port should be used instead.

    Location changed to domainRuntime tree. This is a read-only tree with DomainMBean as the root.
    For more help, use help(domainRuntime)

    Disconnected from weblogic server: AdminServer
    End of export metadata script ...

    Exiting WebLogic Scripting Tool.

    Edited by: 955130 on Aug 29, 2012 4:58 AM

    DB:3.62:Unable To Create User.Xml Using Weblogicexportmetadata.Sh In Oim 11gr2 mj

    Thanks, we need to set the attribute as metadata_files=/file/User.xml

    best,:)

  • RELEVANCY SCORE 3.59

    DB:3.59:Newbie Problem: Ejb Manager Password mx


    Hi,

    I have installed weblogic 6.1 server on unix. I haven't made any changes to anything whatsoever. When I start, say the default server, I get this:

    Sep 29, 2004 9:20:51 PM EDT Notice WebLogicServer ListenThread listening on port 7001
    Sep 29, 2004 9:20:52 PM EDT Notice WebLogicServer Started WebLogic Admin Server "myserver" for domain "mydomain" running in Production Mode

    Now, I try to ping it or shut it down using weblogic.Admin, I get something like this:

    java weblogic.Admin t3://localhost:7001 PING 1 1Failed to connect to t3://localhost:7001 due to: [weblogic.socket.UnrecoverableConnectException: [Login failed: 'Incompatible version:Incompatible versions - this server:6.1.0.0 client:5.1.0]]

    Any help... Thanks..

    DB:3.59:Newbie Problem: Ejb Manager Password mx

    Sorry, that question wasn't meant to be posted here. My problem was the EJB Manager password. After I start my server, if I want to do something minor like list all EJBs deployed, I get the following error:

    java weblogic.deploy list mypasswordConnecting to localhost, port 7001...
    Error getting EJB manager - have you supplied a password?
    Error: class javax.naming.CommunicationException [null]

    I have tried to find any documentation on this, but all I found is 1 or 2 other people asking the same on different forums.

    "mypassword" is the same that I supply while starting weblogic server. I'm running the examples server in development mode so all EJBs in examples directory should be deployed. (By the way, if I go into web console
    and look under ejb deployments, I see all the jar files in examples directory and they are marked as deployed. Yet, I can't call any client on them from command line).

    I would appreciate any help.

    Thanks a lot.

  • RELEVANCY SCORE 3.58

    DB:3.58:The Problem With T3s Connection cj



    hi,

    I have a question about making a t3s connection with wls7.0.
    for example, there is a package called examples.ejb20.basic.statelessSession
    in the samples of wls7.0. It is just an example of stateless SessionBean.
    If I use t3://localhost:7001 to run the EJB Client, it works normally, but if
    I use t3s://localhost:7002 to run the EJB Client, it doesn't work.

    Failed to connect to t3s://127.0.0.1:7002 due to: [java.net.ConnectException:No server found at t3s://localhost:7002]

    I have configured the SSL with the WLS. and https works. I used " -Dweblogic.security.SSL.IgnoreHostnameVerification=true"

    too.

    Regards,
    Meng

    thanks.

    DB:3.58:The Problem With T3s Connection cj


    hi,

    I have a question about making a t3s connection with wls7.0.
    for example, there is a package called examples.ejb20.basic.statelessSession
    in the samples of wls7.0. It is just an example of stateless SessionBean.
    If I use t3://localhost:7001 to run the EJB Client, it works normally, but if
    I use t3s://localhost:7002 to run the EJB Client, it doesn't work.

    Failed to connect to t3s://127.0.0.1:7002 due to: [java.net.ConnectException:No server found at t3s://localhost:7002]

    I have configured the SSL with the WLS. and https works. I used " -Dweblogic.security.SSL.IgnoreHostnameVerification=true"

    too.

    Regards,
    Meng

    thanks.

  • RELEVANCY SCORE 3.52

    DB:3.52:Installation Of Aia jj


    IN aia installation iam unable to fill soa server details..i given localhost,7001,weblogic,welcome1..And before that i started node manager,by using admin console i started managed servers server1,soa_server1..But in installation screen shot it is showing managed server list box::cannot connect to server..Kindly help for the installation of AIA

    DB:3.52:Installation Of Aia jj

    there is a bug in aia 11.1.1.2 while installing through graphical mode.Try to use silent mode installation.

  • RELEVANCY SCORE 3.52

    DB:3.52:Unable To Login Process Integrator Studio/Worklist 9k


    I'm unable to login the weblogic process integrator's studio/worklist.(evaluation copy). I successfully installed the Process Integrator with cloudscape database and commented out "weblogic.security.realmClass=..." and created the users, groups and orgs. Having done so, I am able to bring the server up, but unalbe to login the studio. It does not take any of the 5 users (defined in weblgic.properties) with the respective passwords, though these useraccounts are sucessfully created in the database. message reads: make sure username, password and server URL are all correct. null No server found at T3://localhost:7001 It also diplays "com.bea.wlpi.WLPIPrincipal".

    DB:3.52:Unable To Login Process Integrator Studio/Worklist 9k


    Vasudevan Atteeri vatteeri@armature.com wrote:
    I'm unable to login the weblogic process integrator's
    studio/worklist.(evaluation copy). Vasudevan: Your server hasn't started properly. When running server.cmd
    watch the console. The At the end, you should see the message
    " ListenThread Listening on port: 7001"
    ..
    "Weblogic Server started"

    message reads: make sure username, password and server
    URL are all correct. null No server found at T3://localhost:7001
    It also diplays "com.bea.wlpi.WLPIPrincipal".

  • RELEVANCY SCORE 3.52

    DB:3.52:Web Logic Server Found Error d1


    hi guys, i have successfully deployed my first container managed persistence entity bean
    on web logic server 5.1 but i am unable to run my client application the following error
    occurs when i try to run my client application on windows 98 platform

    we are unable to get a connection to the web logic server at t3:\\localhost:7001
    please make sure that the server is running
    unable to lookup the beans home: cannot instantiate
    class:weblogic.jndi.WLInitialContextFactory

    plz let me know how to overcome this problem

    and what does it mean by t3 why we use it instead of http.

    with regards

    abid

    DB:3.52:Web Logic Server Found Error d1

    You have not mentioned whether the client code is in the same machins as the server.
    Anyway the problem is of classpath setting.For the client to be able to find the weblogic.jndi.WLInitialContextFactory class weblogic.jar file should be in the classpath.
    Try running setEnv batch file from the command prompt for the client if your client is a standalone application

  • RELEVANCY SCORE 3.50

    DB:3.50:'Unknownhostexception ' During Obpm Enterprise For Weblogic Configuration 18


    Hi,

    I am configuring OBPM enterprise 10.3 for weblogic on Windows 7 machine.
    Below is the error that I receive,
    [I 18/01/12 14:52:23] t3://esp50ws19444-7:7001
    [I 18/01/12 14:52:23] Connecting to t3://esp50ws19444-7:7001 with userid weblogic ...
    [I 18/01/12 14:52:23] This Exception occurred at Wed Jan 18 14:52:23 CET 2012.
    [I 18/01/12 14:52:23] javax.naming.ServiceUnavailableException [Root exception is java.net.UnknownHostException: esp50ws19444-7]
    .....
    .....
    [I 18/01/12 14:52:23] No server running at t3://esp50ws19444-7:7001 or the user/password is wrong

    1) With WLST on comand prompt, I am able to connect to t3://esp50ws19444-7:7001
    2) I tried using the 'IP address' and Full DNS name 'esp50ws19444-7.CRB.APMOLLER.NET' but BPM configuration still fails
    3) Referred below threads but no success,
    UnknownHostException during OBPM Enterprise Setup
    [Urgent]Oracle BPM 10gR3 integrate with Oracle weblogic 10gR3 failed.
    Unable to configure the Directory in BPM Enterprise Edition for WebLogic
    WLST Failed in Oracle BPM Enterprise for Weblogic Server

    I see that my C:\windows\system32\drivers\etc\hosts file is empty and it says that the name resoultion is managed in DNS itself.
    Giving localhost and computername/ipaddress in 'hosts' file did not help me.

    Can anybody tell me if this can be resolved?

    Regards,
    Akshay

    DB:3.50:'Unknownhostexception ' During Obpm Enterprise For Weblogic Configuration 18

    Hi,

    This pain in the a** can be avoided by updating the BPM to latest build.
    I update my BPM to 10.3.2 Build # 101228 and everything works like a dream come true ;-)

    Regards,
    Akshay

  • RELEVANCY SCORE 3.50

    DB:3.50:Sessionhelper.Getremotedeploymentmanager Doesn't Work In Fmw 12.1.3 sa


    A particular weblogic API that was working in FMW 12.1.2 is not working after upgrading to FMW 12.1.3SessionHelper.getRemoteDeploymentManager(String protocol, String host,String port, String userName,String password)message priority="warn"![CDATA[javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException: t3://slc03fzz.us.oracle.com:7001: Bootstrap to: host/ip_address:7001' over: 't3' got an error or timed out while trying to connect to host/ip_address:7001]]/message message priority="warn"![CDATA[ at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.init(WebLogicDeploymentManagerImpl.java:137)]]/message message priority="warn"![CDATA[ at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:86)]]/message message priority="warn"![CDATA[ at weblogic.deploy.api.tools.SessionHelper.getRemoteDeploymentManager(SessionHelper.java:530)]]/message

    DB:3.50:Sessionhelper.Getremotedeploymentmanager Doesn't Work In Fmw 12.1.3 sa

    Please check start-up log and confirm if it is listening in the host/port for t3, or post the log from start-up when the issue occurs.Best RegardsLuz

  • RELEVANCY SCORE 3.49

    DB:3.49:Can Ping With T3 But Not With Http? d1


    Hello,

    I'm hoping someone can enlighten me as to why I can ping my WLS using
    t3, but not with http. I'm running WLS 5.1 on solaris 2.6 with JDK
    1.2.1.

    This command works:
    java weblogic.Admin t3://localhost:7001 PING 1 1

    this command does not:
    java weblogic.Admin http://localhost:7001 PING 1 1

    as I get

    "Failed to connect to http://localhost:7001 due to:
    [java.net.ConnectException: No server found at HTTP://localhost:7001]"

    Is it wrong that I can't ping using http? What does t3 stand for/mean?

    Many thanks for your help.
    Jeff

    DB:3.49:Can Ping With T3 But Not With Http? d1

    Great, thanks for the tip!

    Jeff

    Kumar Allamraju wrote:

    http tunneling is disabled by default.

    Add "weblogic.httpd.tunnelingenabled=true" in properties file and
    re-start the server.
    you should be able to ping the server with http protocol.

    --
    Kumar

    Jeff Van Dorn wrote:

    Hello,

    I'm hoping someone can enlighten me as to why I can ping my WLS
    using
    t3, but not with http. I'm running WLS 5.1 on solaris 2.6 with JDK
    1.2.1.

    This command works:
    java weblogic.Admin t3://localhost:7001 PING 1 1

    this command does not:
    java weblogic.Admin http://localhost:7001 PING 1 1

    as I get

    "Failed to connect to http://localhost:7001 due to:
    [java.net.ConnectException: No server found at
    HTTP://localhost:7001]"

    Is it wrong that I can't ping using http? What does t3 stand
    for/mean?

    Many thanks for your help.
    Jeff

  • RELEVANCY SCORE 3.46

    DB:3.46:Problem Of Deployment(Weblogic8.1.4+Jbuilder2006) z8


    Unable to connect to server t3://localhost:7001 as user weblogic.
    Reason: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost: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:47)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:636)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:306)
    at weblogic.jndi.Environment.getContext(Environment.java:166)
    at weblogic.jndi.Environment.getInitialContext(Environment.java:145)
    at weblogic.management.deploy.utils.MBeanHomeTool.getMBeanHome(MBeanHomeTool.java:172)
    at weblogic.Deployer.runBody(Deployer.java:721)
    at weblogic.utils.compiler.Tool.run(Tool.java:192)
    at weblogic.utils.compiler.Tool.run(Tool.java:147)
    at weblogic.Deployer.runMain(Deployer.java:574)
    at weblogic.Deployer.main(Deployer.java:557)
    Caused by: java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
    java.net.ConnectException: Connection refused: connect; No available router to destination
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:296)
    ... 8 more

    Check option -adminurl, -username and -password.

    but the configuration is right,i am confused.

    DB:3.46:Problem Of Deployment(Weblogic8.1.4+Jbuilder2006) z8

    Unable to connect to server t3://localhost:7001 as user weblogic.
    Reason: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost: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:47)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:636)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:306)
    at weblogic.jndi.Environment.getContext(Environment.java:166)
    at weblogic.jndi.Environment.getInitialContext(Environment.java:145)
    at weblogic.management.deploy.utils.MBeanHomeTool.getMBeanHome(MBeanHomeTool.java:172)
    at weblogic.Deployer.runBody(Deployer.java:721)
    at weblogic.utils.compiler.Tool.run(Tool.java:192)
    at weblogic.utils.compiler.Tool.run(Tool.java:147)
    at weblogic.Deployer.runMain(Deployer.java:574)
    at weblogic.Deployer.main(Deployer.java:557)
    Caused by: java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
    java.net.ConnectException: Connection refused: connect; No available router to destination
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:296)
    ... 8 more

    Check option -adminurl, -username and -password.

    but the configuration is right,i am confused.

  • RELEVANCY SCORE 3.46

    DB:3.46:Can We Pass The Ant Property To The Wlst Script? sd


    Hi,
    I am using WLST to configure domain. Is there ant way in which we can pass the ant property to script tag? Rite now we are hardcoding the username, password and serverIp in the script.

    target name="configServer"
    wlst debug="false" failOnError="false" executeScriptBeforeFile="true" fileName="./myscript.py"
    script connect('weblogic','weblogic','t3://localhost:7001')
    /script
    /wlst
    /target

    So essentially the above script will lok like following

    target name="configServer"
    wlst debug="false" failOnError="false" executeScriptBeforeFile="true" fileName="./myscript.py"
    script connect(${username},${password},'t3://${serverIP}:7001')
    /script
    /wlst
    /target

    Thanks,

    DB:3.46:Can We Pass The Ant Property To The Wlst Script? sd

    In 10.3, we added a replaceProperties option to allow ant properties to be
    evaluated in script tag.

    In the meantime, you may be able to use the load properties command in WLST.

    Scott Ding wrote in message news:570002784@newsgroups.bea.com...
    Hi,
    I am using WLST to configure domain. Is there ant way in which we can pass
    the ant property to script tag? Rite now we are hardcoding the username,
    password and serverIp in the script.

    target name="configServer"
    wlst debug="false" failOnError="false" executeScriptBeforeFile="true"
    fileName="./myscript.py"
    script connect('weblogic','weblogic','t3://localhost:7001')
    /script
    /wlst
    /target

    So essentially the above script will lok like following

    target name="configServer"
    wlst debug="false" failOnError="false" executeScriptBeforeFile="true"
    fileName="./myscript.py"
    script connect(${username},${password},'t3://${serverIP}:7001')
    /script
    /wlst
    /target

    Thanks,

  • RELEVANCY SCORE 3.46

    DB:3.46:Crs Unable To Identify Status Of Weblogic Server s3


    Hi,

    I am new to ATG e commerce tool so started exploring it by going through some basic docs. Currently I am installing CRS and while doing it I encountered below issue.

    raiseWLSTException
    **** infoWed Feb 15 15:11:55 EST 20121329336715498atg.cim.task.ant.utility.AntLogger[exec] WLSTException: Error occured while performing connect : Error getting the initial context. There is no server running at t3://localhost:7001
    **** infoWed Feb 15 15:11:55 EST 20121329336715499atg.cim.task.ant.utility.AntLogger[exec] Use dumpStack() to view the full stacktrace
    **** infoWed Feb 15 15:11:55 EST 20121329336715499atg.cim.task.ant.utility.AntLogger[exec]
    **** infoWed Feb 15 15:11:55 EST 20121329336715567atg.cim.task.ant.utility.AntLogger
    **** infoWed Feb 15 15:11:55 EST 20121329336715567atg.cim.task.ant.utility.AntLoggerBUILD FAILED
    **** infoWed Feb 15 15:11:55 EST 20121329336715567atg.cim.task.ant.utility.AntLoggerC:\ATG\ATG10.0.3\CIM\plugins\Base\ant\cim-ant.xml:307: The following error occurred while executing this line:
    **** infoWed Feb 15 15:11:55 EST 20121329336715567atg.cim.task.ant.utility.AntLoggerC:\ATG\ATG10.0.3\CIM\plugins\Base\ant\cim-ant.xml:245: The following error occurred while executing this line:
    **** infoWed Feb 15 15:11:55 EST 20121329336715567atg.cim.task.ant.utility.AntLoggerC:\ATG\ATG10.0.3\CIM\plugins\Base\ant\cim-ant.xml:205: exec returned: 1
    **** infoWed Feb 15 15:11:55 EST 20121329336715567atg.cim.task.ant.utility.AntLogger
    **** infoWed Feb 15 15:11:55 EST 20121329336715567atg.cim.task.ant.utility.AntLoggerTotal time: 31 seconds

    NOTE: WEBLOGIC was already running at localhost:7001 but CRS was not able to pull it

    May i know the reason for the failure?

    Regards,
    Jameel.

    DB:3.46:Crs Unable To Identify Status Of Weblogic Server s3

    Hi ,

    May be your firewall / antivirus is blocking the port.Please check.

    Also

    There is a known bug in JDK 1.7 related to IPv6.

    Add -Djava.net.preferIPv4Stack=true in JAVA_OPTIONS in setDomainEnv.cmd and try.

    Try changing JDK version use the recommended one , or the one which comes along with weblogic itself.

    ~ Praveer

  • RELEVANCY SCORE 3.44

    DB:3.44:Problem Running The Sample Jaas Example Provided 8x


    Hi

    I am new to JAAS as well as to the WebLogic6.0 .While trying to run the
    sample JAAS program provided with WLS i got the following error:

    java examples.security.jaas.
    SampleClient t3://localhost:7001
    SampleLoginModule.initialize(), debug enabled
    SampleLoginModule.initialize(), URL t3://localhost:7001
    username: guest
    password: guest
    SampleLoginModule.login(), username guest
    SampleLoginModule.login(), password guest
    javax.naming.NameNotFoundException: Unable to resolve frobtarget. Resolved:
    '' U
    nresolved:'frobtarget' ; remaining name ''
    at
    weblogic.rmi.internal.AbstractOutboundRequest.sendReceive(AbstractOut
    boundRequest.java:90)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteR
    ef.java:247)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteR
    ef.java:225)
    at
    weblogic.jndi.internal.ServerNamingNode_WLStub.lookup(ServerNamingNod
    e_WLStub.java:121)
    at
    weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:323)
    at javax.naming.InitialContext.lookup(InitialContext.java:350)
    at examples.security.jaas.SampleAction.run(SampleAction.java:61)
    at javax.security.auth.Subject.doAs(Subject.java:80)
    at examples.security.jaas.SampleClient.main(SampleClient.java:121)
    Failed to frob

    can someone help me out in over coming this error.

    regards
    Siddharth

    DB:3.44:Problem Running The Sample Jaas Example Provided 8x

    Hi

    I am new to JAAS as well as to the WebLogic6.0 .While trying to run the
    sample JAAS program provided with WLS i got the following error:

    java examples.security.jaas.
    SampleClient t3://localhost:7001
    SampleLoginModule.initialize(), debug enabled
    SampleLoginModule.initialize(), URL t3://localhost:7001
    username: guest
    password: guest
    SampleLoginModule.login(), username guest
    SampleLoginModule.login(), password guest
    javax.naming.NameNotFoundException: Unable to resolve frobtarget. Resolved:
    '' U
    nresolved:'frobtarget' ; remaining name ''
    at
    weblogic.rmi.internal.AbstractOutboundRequest.sendReceive(AbstractOut
    boundRequest.java:90)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteR
    ef.java:247)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteR
    ef.java:225)
    at
    weblogic.jndi.internal.ServerNamingNode_WLStub.lookup(ServerNamingNod
    e_WLStub.java:121)
    at
    weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:323)
    at javax.naming.InitialContext.lookup(InitialContext.java:350)
    at examples.security.jaas.SampleAction.run(SampleAction.java:61)
    at javax.security.auth.Subject.doAs(Subject.java:80)
    at examples.security.jaas.SampleClient.main(SampleClient.java:121)
    Failed to frob

    can someone help me out in over coming this error.

    regards
    Siddharth

  • RELEVANCY SCORE 3.44

    DB:3.44:T3 Connect Problem kj



    Does anybody know what causes this error?

    java.io.IOException: Bootstrap unable to get a t3 connection to
    localhost
    at
    weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:315)
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)
    at
    weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:230)
    at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:201)
    at
    weblogic.common.internal.DNSBasedRJVMFinder.findOrCreate(Compiled Code)
    at
    weblogic.common.internal.ServerURL.findOrCreateRJVM(ServerURL.java:156)
    at weblogic.common.T3Client.connect(T3Client.java:382)
    at events.foobar.init(foobar.java:107)
    at EventApplet.init(EventApplet.java:27)
    at sun.applet.AppletPanel.run(Compiled Code)
    at java.lang.Thread.run(Thread.java:479)

    It's produced by the following code snippet:

    public class foobar {

    static T3Client t3 = null;

    public foobar() {

    t3 = new T3Client("t3://localhost");
    t3.connect();
    }
    }

    Thanks,
    Craig

    DB:3.44:T3 Connect Problem kj

    Could be because you have not specified the port and WLS is listening on any
    other port than the default 7001.

    "Craig MacFarlane" craigm@chemconnect.com wrote in message
    news:38BC102E.AF9DDE10@chemconnect.com...

    Does anybody know what causes this error?

    java.io.IOException: Bootstrap unable to get a t3 connection to
    localhost
    at
    weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:315)
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)
    at
    weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:230)
    at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:201)
    at
    weblogic.common.internal.DNSBasedRJVMFinder.findOrCreate(Compiled Code)
    at
    weblogic.common.internal.ServerURL.findOrCreateRJVM(ServerURL.java:156)
    at weblogic.common.T3Client.connect(T3Client.java:382)
    at events.foobar.init(foobar.java:107)
    at EventApplet.init(EventApplet.java:27)
    at sun.applet.AppletPanel.run(Compiled Code)
    at java.lang.Thread.run(Thread.java:479)

    It's produced by the following code snippet:

    public class foobar {

    static T3Client t3 = null;

    public foobar()

    t3 = new T3Client("t3://localhost");
    t3.connect();
    }
    }

    Thanks,
    Craig

  • RELEVANCY SCORE 3.43

    DB:3.43:Accessing Weblogi Jndi 3f


    i'm trying to access weblogic JNDI from my code and it gaves me this Error:

    Caused by: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost: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:783)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:365)
    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.ldap.InitialLdapContext.init(InitialLdapContext.java:134)
    at com.etech.common.ldap.ad.UserLdapHandler.initLdapContext(UserLdapHandler.java:141)
    ... 42 more
    Caused by: java.net.ConnectException: t3://localhost: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:153)
    at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:344)
    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:339)
    ... 50 more

    the enviroment i use is like this :
    environment.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
    environment.put(Context.PROVIDER_URL, "t3://localhost:7001");
    environment.put(Context.REFERRAL, "follow");

    Any help will be great.

    DB:3.43:Accessing Weblogi Jndi 3f

    i'm trying to access weblogic JNDI from my code and it gaves me this Error:

    Caused by: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost: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:783)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:365)
    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.ldap.InitialLdapContext.init(InitialLdapContext.java:134)
    at com.etech.common.ldap.ad.UserLdapHandler.initLdapContext(UserLdapHandler.java:141)
    ... 42 more
    Caused by: java.net.ConnectException: t3://localhost: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:153)
    at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:344)
    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:339)
    ... 50 more

    the enviroment i use is like this :
    environment.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
    environment.put(Context.PROVIDER_URL, "t3://localhost:7001");
    environment.put(Context.REFERRAL, "follow");

    Any help will be great.

  • RELEVANCY SCORE 3.43

    DB:3.43:Is There An Acl For Restricting File Access Via T3filesystem zp


    with client code like that below I am able to access any file on my weblogic
    server. How can I set access restrictions???

    Thanks
    Robert

    T3Client t3 = new T3Client("t3://localhost:7001");
    t3.connect();

    T3FileSystem _t3FileSystem = t3.services.io().getFileSystem("");
    T3File file = _t3FileSystem.getFile("c:/weblogic/.../.../sample.txt");
    InputStream in = file.getFileInputStream();

    DB:3.43:Is There An Acl For Restricting File Access Via T3filesystem zp

    with client code like that below I am able to access any file on my weblogic
    server. How can I set access restrictions???

    Thanks
    Robert

    T3Client t3 = new T3Client("t3://localhost:7001");
    t3.connect();

    T3FileSystem _t3FileSystem = t3.services.io().getFileSystem("");
    T3File file = _t3FileSystem.getFile("c:/weblogic/.../.../sample.txt");
    InputStream in = file.getFileInputStream();

  • RELEVANCY SCORE 3.43

    DB:3.43:Remote-Deploy Weblogic With Http/Https? 8j


    Hi,

    I want to do remote-deploy on WebLogic from command-line, and using the java-class weblogic.Deployer.

    After some experimentation locally, I can only get it to work by using the t3 protocol, like:

    java weblogic.Deployer -adminurl t3://localhost:7001/console ...

    If I say, instead:

    java weblogic.Deployer -adminurl http://localhost:7001/console ...

    I get Exception "Destination unreachable" so it seems the client cannot even detect the server.

    Is there a way to configure WebLogic, so it will accept http/https-connections for remote-control?

    DB:3.43:Remote-Deploy Weblogic With Http/Https? 8j

    http://download.oracle.com/docs/cd/E21764_01/web.1111/e13702/wldeployer.htm#i1010724

    From the documentation:
    "In order to use an adminurl with the HTTP protocol, you must enable the HTTP tunneling option in the Administration Console."

  • RELEVANCY SCORE 3.42

    DB:3.42:Statelesssession Example: We Were Unable To Get A Connection To The Weblogic Server At T3://Localhost:7001 3x



    I have seen other related posts on this site but really no answers, the users seem to be left hanging.
    Anyway, I am trying to run the statelessSession example, with the WebLogic server running and listening
    on port 7001 on the current machine (i.e. localhost).
    Here is what I am seeing:

    c:\weblogic\myserver\clientclassesjava examples.ejb.basic.statelessSession.Client

    Beginning statelessSession.Client...

    We were unable to get a connection to the WebLogic server at t3://localhost:7001

    Please make sure that the server is running.

    System Configuration:
    Win2000, WebLogic 5.1, WL Sp2, Java 1.2.2, weblogic home== c:\weblogic

    I have attached the weblogic.log.

    Regards,
    John

    DB:3.42:Statelesssession Example: We Were Unable To Get A Connection To The Weblogic Server At T3://Localhost:7001 3x


    Hello John,

    When I first install "weblogic", I am successfully able to run the examples, but after some time which I completely forget how I make them run, I install it again and encounter the same problem as you.

    After spending nearly a whole day on restarting computer, viewing ports etc. :) :(, I remember that I make weblogic run from the command line. First, in a console run setenv and startWebLogic tools which are located under weblogic directory and in an another console run setenv again(for possible errors, I want to be sure that it is correct again) and run your client as explained in the tutorials html pages.

    As seen, in computer science, simple things, not hard things, always cause you to lose time :)))

    Best regards

    Banu

    "John Pda" javapda@yahoo.com wrote:

    I have seen other related posts on this site but really no answers, the users seem to be left hanging.
    Anyway, I am trying to run the statelessSession example, with the WebLogic server running and listening
    on port 7001 on the current machine (i.e. localhost).
    Here is what I am seeing:

    c:\weblogic\myserver\clientclassesjava examples.ejb.basic.statelessSession.Client

    Beginning statelessSession.Client...

    We were unable to get a connection to the WebLogic server at t3://localhost:7001

    Please make sure that the server is running.

    System Configuration:
    Win2000, WebLogic 5.1, WL Sp2, Java 1.2.2, weblogic home== c:\weblogic

    I have attached the weblogic.log.

    Regards,
    John

  • RELEVANCY SCORE 3.39

    DB:3.39:Could Not Connect To Admin Server Using Wlst jx


    Hi All,I have a dmz server running at 10.7.3.102:7001.I could not connect to that server from some of my Exalogic VMs:wls:/offline connect('weblogic','pass','t3://10.7.3.102:7001')Connecting to t3://10.7.3.102:7001 with userid weblogic ...Traceback (innermost last): File "console", line 1, in ? File "iostream", line 22, in connect File "iostream", line 648, in raiseWLSTExceptionWLSTException: Error occured while performing connect : Error getting the initial context. There is no server running at t3://10.7.3.102:7001Use dumpStack() to view the full stacktraceBut when I tried connecting to 10.7.3.102:7001 using my other Exalogic VMs, it was a success.Note: All the VMs are in one exalogic box.I don't know where to start investigating here. Do you have ideas?

    DB:3.39:Could Not Connect To Admin Server Using Wlst jx

    I also tried to telnet in the IP:Porttelnet 10.7.3.102 7001and it was a success. So it is not an infrastructure issue. Any other ideas?

  • RELEVANCY SCORE 3.39

    DB:3.39:Client Accessing Wl5.1 On Rh Linux6.1 cd


    Does anyone know of a problem where a client cannot find the server when
    both are running on RH Linux 6.1? My getInitialContext is failing when
    using t3://localhost:7001 or t3://192.168.145.75:7001. The server is
    running on port 7001 and I can connect to it when running the Java client on
    my NT box. Here is my code for getInitialContext( ):

    private Context getInitialContext() throws NamingException
    {
    String url = "t3://localhost:7001";
    String user = blah;
    String password = blah;

    try
    {
    // Get an InitialContext
    Properties h = new Properties();
    h.put(Context.INITIAL_CONTEXT_FACTORY,
    "weblogic.jndi.WLInitialContextFactory");
    h.put(Context.PROVIDER_URL, url);
    if (user != null)
    {
    h.put(Context.SECURITY_PRINCIPAL, user);
    if (password == null)
    password = "";
    h.put(Context.SECURITY_CREDENTIALS, password);
    }
    return new InitialContext(h);
    }
    catch (NamingException ne)
    {
    log("We were unable to get a connection to the WebLogic server
    at "+url);
    log("Please make sure that the server is running.");
    throw ne;
    }
    }

    Any help is appreciated
    -Brad

    DB:3.39:Client Accessing Wl5.1 On Rh Linux6.1 cd

    b Does anyone know of a problem where a client cannot find the server
    b when both are running on RH Linux 6.1?

    This works fine for me, and for several other developers here who use
    Linux all the time. If you can post more information about what
    actually goes wrong, that would help.

    b

    --
    Let us pray:
    What a Great System.
    Please Do Not Crash.
    ^G^IP@P6

  • RELEVANCY SCORE 3.38

    DB:3.38:Registering For Weblogic Events xx


    Hi,
    I am using a servlet which is initialized at start up, and it tries to
    make a t3connection to the server in the init method (t3.connect(), with the
    url like t3://localhost:7001 or http://localhost:7001) and it actually is
    successfully most of time(the server starts listening at 7001 after this!),
    some times it fails in solaris boxes.

    I am surprised it is successful sometimes!!. why does it work sometimes?

    Any help is appreciated

    regards
    viswa.

    DB:3.38:Registering For Weblogic Events xx

    1. Register your servlet in weblogic.properties with a virtual name.
    2. Put your servlet class under
    %weblogic_root_directory/myserver/servletclasses directory
    3. Use url like this http://localhost:7001/virtualServletname in your client
    browser
    4. start weblogic using a new command prompt using setenv.sh and
    startweblogic.sh shell scripts.
    5. Servlet will work anytime.
    Chandra

    "viswanathan" viswa@trapezo.com wrote in message
    news:8au3eb$288$1@bayview.weblogic.com...
    Hi,
    I am using a servlet which is initialized at start up, and it tries to
    make a t3connection to the server in the init method (t3.connect(), with
    the
    url like t3://localhost:7001 or http://localhost:7001) and it actually is
    successfully most of time(the server starts listening at 7001 after
    this!),
    some times it fails in solaris boxes.

    I am surprised it is successful sometimes!!. why does it work sometimes?

    Any help is appreciated

    regards
    viswa.

  • RELEVANCY SCORE 3.38

    DB:3.38:6.1 Servicepack1-≫Servicepack 2: Rmi Stopped Working! dk



    Hi!

    I just upgraded my Weblogic Server from 6.1 to 6.1sp2. This made my client program
    connecting to WLS over T3 stop working!

    Has anyone else experienced the same problem?

    This is the error message:

    Caught exception: javax.naming.CommunicationException [Root exception is java.net.ConnectException:
    t3://localhost:7001: Destination unreachable; nested exception is: java.net.ConnectException:
    Connection refused: connect; No available router to destination]

    And this is my calling code:

    public static Object lookupHome(String jndiName) throws VMException
    {
    try { Context ctx = getInitialContext("t3://localhost:7001", "system", "password");

    return ctx.lookup(jndiName);
    }
    catch(Exception e)
    {
    throw new VMException("VMUtil", "lookupHome", e, "Problems looking up the requested
    home interface", jndiName, "General user error msg");
    }
    }

    static Context getInitialContext(String url, String user, String password)
    throws NamingException
    {
    try
    { Hashtable h = new Hashtable(5);
    h.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");

    h.put(Context.PROVIDER_URL, url);
    h.put(Context.SECURITY_PRINCIPAL, user);
    h.put(Context.SECURITY_CREDENTIALS, password);
    return new InitialContext(h);
    }
    catch(NamingException ne)
    { System.out.println("Main.getInitialContext: Were not able to get in touch with
    the server!");
    throw ne;
    }
    }

    The port for the server is 7001.

    Can anyone help me with this?

    Thanks in advance!

    Regards,
    Vidar Moe
    Norway

    DB:3.38:6.1 Servicepack1-≫Servicepack 2: Rmi Stopped Working! dk


    Hi!

    I just upgraded my Weblogic Server from 6.1 to 6.1sp2. This made my client program
    connecting to WLS over T3 stop working!

    Has anyone else experienced the same problem?

    This is the error message:

    Caught exception: javax.naming.CommunicationException [Root exception is java.net.ConnectException:
    t3://localhost:7001: Destination unreachable; nested exception is: java.net.ConnectException:
    Connection refused: connect; No available router to destination]

    And this is my calling code:

    public static Object lookupHome(String jndiName) throws VMException
    {
    try { Context ctx = getInitialContext("t3://localhost:7001", "system", "password");

    return ctx.lookup(jndiName);
    }
    catch(Exception e)
    {
    throw new VMException("VMUtil", "lookupHome", e, "Problems looking up the requested
    home interface", jndiName, "General user error msg");
    }
    }

    static Context getInitialContext(String url, String user, String password)
    throws NamingException
    {
    try
    { Hashtable h = new Hashtable(5);
    h.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");

    h.put(Context.PROVIDER_URL, url);
    h.put(Context.SECURITY_PRINCIPAL, user);
    h.put(Context.SECURITY_CREDENTIALS, password);
    return new InitialContext(h);
    }
    catch(NamingException ne)
    { System.out.println("Main.getInitialContext: Were not able to get in touch with
    the server!");
    throw ne;
    }
    }

    The port for the server is 7001.

    Can anyone help me with this?

    Thanks in advance!

    Regards,
    Vidar Moe
    Norway

  • RELEVANCY SCORE 3.38

    DB:3.38:Jms Bridge Status 3c


    Hi,

    I am trying to find out the bridge status using the below wlst script. But failed to execute it.

    Please help me.

    connect(weblogic,'weblogic','t3://localhost:7001')
    servers = domainRuntimeService.getServerRuntimes();
    if (len(servers) 0):
    for server in servers:
    messagingBridgeRuntime = server.getMessagingBridgeRuntime;
    messageBridges = messageBrigdeRuntime.getMessageBridges();
    for messageBridge in messageBridges:
    destinations = messageBridges.getDestinations();
    for destination in destinations:
    print ' BridgeName' , destination.getName()
    print ' State ' , destination.getState()

    DB:3.38:Jms Bridge Status 3c

    The "state" of a bridge instance is on the runtime mbean not the config mbean.
    I am able to access a messaging bridge instance (and its state) using WLST. Here is the output.

    wls:/mydomain/serverRuntime cd('MessagingBridgeRuntime')
    wls:/mydomain/serverRuntime/MessagingBridgeRuntime ls()
    dr-- Bridge-0

    wls:/mydomain/serverRuntime/MessagingBridgeRuntime cd('Bridge-0')
    wls:/mydomain/serverRuntime/MessagingBridgeRuntime/Bridge-0 ls()

    -r-- Description Stopped by the administrator.
    -r-- Name Bridge-0
    -r-- State Inactive
    -r-- Type MessagingBridgeRuntime

    -r-x preDeregister Void :
    -r-x start Void :
    -r-x stop Void :

    But I am using a recent WebLogic release (10.3.5). You may want to contact Oracle Support to get a patch for this on 9.2.3 if you are not able to upgrade to 10.3.5 or later release.

    Dongbo

  • RELEVANCY SCORE 3.36

    DB:3.36:Weblogic.Admin Shutdown c3



    All,

    I'm getting a ConnectException (see below) when running the weblogic.Admin SHUTDOWN
    command. The mydomain server is configured to use port 80 instead of the default
    7001. It seems the admin shutdown expects the default port to be used. Is there
    a command line option that allows the correct port to be specified? TIA.

    JohnH

    # java -classpath /opt/weblogic/wlserver6.1/lib/weblogic.jar
    weblogic.Admin SHUTDOWN
    Failed to connect to t3://localhost:7001 due to: [java.net.ConnectException: No
    server found at T3://localhost:7001]

    DB:3.36:Weblogic.Admin Shutdown c3


    All,

    I'm getting a ConnectException (see below) when running the weblogic.Admin SHUTDOWN
    command. The mydomain server is configured to use port 80 instead of the default
    7001. It seems the admin shutdown expects the default port to be used. Is there
    a command line option that allows the correct port to be specified? TIA.

    JohnH

    # java -classpath /opt/weblogic/wlserver6.1/lib/weblogic.jar
    weblogic.Admin SHUTDOWN
    Failed to connect to t3://localhost:7001 due to: [java.net.ConnectException: No
    server found at T3://localhost:7001]

  • RELEVANCY SCORE 3.34

    DB:3.34:Oim 11g Uploadjars Issue 91


    Hi All,

    I am getting error, when i try to upload a jar file in oim 11.1.1.5.0.

    Have set WL_HOME="MWHOME/wlserver_10.3
    run ./UploadJars.sh

    [Enter Xellerate admin username :]xelsysadm
    [Enter the admin password :]passwd of xelsysadm
    [Enter serverURL :[ t3://localhost:7001 ]]t3://localhost:7001
    [Enter context Factory :[ weblogic.jndi.WLInitialContextFactory ]]weblogic.jndi.WLInitialContextFactory
    l

    log4j:WARN No such property [datePattern] in org.apache.log4j.RollingFileAppender.
    Error occurred in performing the operation:
    Exception in thread "main" java.lang.NullPointerException
    at oracle.iam.platformservice.utils.JarUploadUtility.main(JarUploadUtility.java:229)

    I tried giving full serverURL, but the result was same.

    Can you please help me.

    Note: 3 days back, I was uploaded jars sucessfully. but right now its giving this error.

    Thanks.

    DB:3.34:Oim 11g Uploadjars Issue 91

    Hi,

    Please provide OIM server url while uploading jars t3://localhost:14000

  • RELEVANCY SCORE 3.34

    DB:3.34:Cluster Problem df



    Hi,
    when I exam my logs I found out these lines. what are these threads trying to
    do? The reported 2 servers did log anything 5 mins before the timestamp here.

    ###Sept 7, 2002 6:37:54 PM PDT Warning RJVM asd srv1 ExecuteThread:
    '5' for queue: 'default' kernel identity 000519 Unable to connect to
    a remote server on address 10.11.21.50 and port 7001 with protocol t3. The Exception
    is java.net.ConnectException: Operation timed out: connect

    ####Sept 7, 2002 10:05:47 PM PDT Warning RJVM asd srv1 ExecuteThread:
    '3' for queue: 'default' kernel identity 000519 Unable to connect to
    a remote server on address 10.11.21.51 and port 7001 with protocol t3. The Exception
    is java.net.SocketException: Connection reset by peer: JVM_recv in socket input
    stream read

    ####Sept 7, 2002 10:05:47 PM PDT Warning RJVM asd srv1 ExecuteThread:
    '1' for queue: 'default' kernel identity 000519 Unable to connect to
    a remote server on address 10.11.21.512 and port 7001 with protocol t3. The Exception
    is java.net.SocketException: Connection reset by peer: socket write error

    DB:3.34:Cluster Problem df

    Did anyone fix this issue ?? We are having the same issue in production.

    Thanks,
    Chris

  • RELEVANCY SCORE 3.34

    DB:3.34:Unable To Start Cluster Via Weblogic.Admin 8j


    I'm trying to start my WebLogic cluster via Java but it fails almost every time with the following error:

    url "t3://localhost:7001" is required to be of Administration Server ...

    Using:

    java weblogic.Admin -url localhost:7001 -username username -password password STARTCLUSTER -clustername clustername

    I can do STOPCLUSTER other Cluster commands without any problems. Anyone else seen this problem? Any suggestions?

    DB:3.34:Unable To Start Cluster Via Weblogic.Admin 8j

    I see the same issue after creating multiple clusters. As posted above ALL other commands including individual server startup commands work.... Just not starting a cluster

  • RELEVANCY SCORE 3.33

    DB:3.33:Weblogic.Deploy Tool ps



    I tried to use weblogic.deploy to deploy my EAR file on weblogic server called localhost
    on 7001. When I try to run it gives me following error: [java] JNDI naming exception:
    Naming exception trying to connect to: t3://localhost:7001 as: system: password

    system password is correct. I have tried http://localhost:7001 to but doesen't seem
    to work. Any ideas.

    HS

    DB:3.33:Weblogic.Deploy Tool ps


    I tried to use weblogic.deploy to deploy my EAR file on weblogic server called localhost
    on 7001. When I try to run it gives me following error: [java] JNDI naming exception:
    Naming exception trying to connect to: t3://localhost:7001 as: system: password

    system password is correct. I have tried http://localhost:7001 to but doesen't seem
    to work. Any ideas.

    HS

  • RELEVANCY SCORE 3.33

    DB:3.33:Warning: Unable To Connect To Url: In Oracle B2b Adaptor px


    Hi

    I am facing the following error while configuring the b2b in jdev

    WARNING: Unable to connect to URL: http://localhost:7001/integration/services/b2b/B2BMetadataWSPort due to javax.xml.soap.SOAPException: Message send failed: emeacache.uk.oracle.com

    DB:3.33:Warning: Unable To Connect To Url: In Oracle B2b Adaptor px

    Hi,

    Check whether admin server is up and running.

    Regards,
    Anuj

  • RELEVANCY SCORE 3.31

    DB:3.31:Unable To Login Wlpi Studio/Worklist 38


    I'm unable to login into the weblogic process integrator's studio/worklist with the evaluation copy of wlpi. I'm able to create the database(oracle) connection properly and also set up the users etc tables as specified in ddl/wlpi_oracle.ddl file. However when I try to login by giving the user/password and url(t3://localhost:7001) a message pops up asking to check the user/password/url .It also display "com.bea.wlpi.WLPIPrincipal". However WLPIPrincipal class exists in some other package (com.bea.wlpi.server.WLPIPrincipal). There is no file with the displayed package.Can anyone help me. I'm really tired with this problem!!!

    DB:3.31:Unable To Login Wlpi Studio/Worklist 38


    Install the ejb20.jar upgrade from bea and it should work fine.

    Cheers/Sanjay

    "Richard Bourke" rbourke@bea.com wrote:

    Vinkal,
    I had the same problem. The cause was an incorrect path to the
    wlpi-ejb
    in weblogic properties. Take a look in the weblogic.log to see
    if
    you have errors in this area. The server was started, but without
    the wlpi beans, it didn't know what to do with the (correct) login
    information.
    a message pops up asking to check the user/password/url
    .It also display "com.bea.wlpi.WLPIPrincipal". However
    WLPIPrincipal class exists in some other package (com.bea.wlpi.server.WLPIPrincipal).
    There is no file with the displayed package.Can anyone
    help me. I'm really tired with this problem!!!

  • RELEVANCY SCORE 3.31

    DB:3.31:Jndi Lookup In Resin a3


    Hi,
    I'm facing problems while lookingup Home, from Resin to
    wlserver6.1.
    I'm new to Resin and unable to find any clean documentation either.
    I'm able to lookup the server from Tomcat, but not from resin.

    The Resin.conf file is like this, jndi props....
    jndiname is: ReteAdminBean

    jndi-link
    jndi-namejava:comp/env/ReteAdminBean/jndi-name
    jndi-factoryweblogic.jndi.WLInitialContextFactory/jndi-factory
    init-param java.naming.provider.url="t3://localhost:7001"/
    init-param java.naming.security.principal="system"/
    init-param java.naming.security.credentials="calvin2k"/
    jndi-lookupReteAdminHome/jndi-lookup
    /jndi-link

    I'm not very sure of the syntax. Any help?????
    Thanks in advance..
    regards
    tapas

    DB:3.31:Jndi Lookup In Resin a3

    tapas tapasc_pradhan@yahoo.com wrote:
    Hi,
    I'm facing problems while lookingup Home, from Resin to
    wlserver6.1.
    I'm new to Resin and unable to find any clean documentation either.
    I'm able to lookup the server from Tomcat, but not from resin.

    The Resin.conf file is like this, jndi props....
    jndiname is: ReteAdminBean

    Then why jndi-lookup says ReteAdminHome ?

    Also, make sure that you have WebLogic classes in the classpath
    (classpath id='c:/bea/wlserver6.1/lib/weblogic.jar'/)

    jndi-link
    jndi-namejava:comp/env/ReteAdminBean/jndi-name
    jndi-factoryweblogic.jndi.WLInitialContextFactory/jndi-factory
    init-param java.naming.provider.url="t3://localhost:7001"/
    init-param java.naming.security.principal="system"/
    init-param java.naming.security.credentials="calvin2k"/
    jndi-lookupReteAdminHome/jndi-lookup
    /jndi-link

    I'm not very sure of the syntax. Any help?????
    Thanks in advance..
    regards
    tapas

    --
    Dimitri

  • RELEVANCY SCORE 3.28

    DB:3.28:Bootstraperror: Connect To Localhost:7001, But Listenport Is 7003 17



    Hi,
    I have configure WLS 5.1 to listen on Port 7003. Now, if I call in an Servlet
    the function java.beans.Bean.instantiate(getClass().getClassLoader(), de.foo.bar);
    the log say this:
    ConMan Bootstrap unable to get a t3 connection to localhost/127.0.0.1
    javax.naming.CommunicationException. Root exception is java.net.ConnectException:
    No server found at T3://localhost:7001 at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java,
    Compiled Code)
    I think the problem is the classloader.
    If I run the WLS under the port 7001 everything is ok.
    Any suggestion?

    Thanks in advance,
    Boris Huxhorn

    DB:3.28:Bootstraperror: Connect To Localhost:7001, But Listenport Is 7003 17


    I have the same problem with Weblogic 6.1 !! I have my server listening to port
    80 but I still get this when hitting MyServlet : (I have no managed server I
    am just running the admin server)

    MyServlet.init: javax.naming.CommunicationException [Root exception is java.net.ConnectException:
    No server found at T3://localHost:7001]
    MyServlet.showSummaries: java.lang.NullPointerException

    Can anyone please help ? Thanks in advance !!

    "Boris Huxhorn" boris.huxhorn@avinci.de wrote:

    Hi,
    I have configure WLS 5.1 to listen on Port 7003. Now, if I call in an
    Servlet
    the function java.beans.Bean.instantiate(getClass().getClassLoader(),
    de.foo.bar);
    the log say this:
    ConMan Bootstrap unable to get a t3 connection to localhost/127.0.0.1
    javax.naming.CommunicationException. Root exception is java.net.ConnectException:
    No server found at T3://localhost:7001 at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java,
    Compiled Code)
    I think the problem is the classloader.
    If I run the WLS under the port 7001 everything is ok.
    Any suggestion?

    Thanks in advance,
    Boris Huxhorn

  • RELEVANCY SCORE 3.26

    DB:3.26:Exception In Thread "Main" Java.Lang.Noclassdeffounderror: Weblogic/Admin cp


    Hi everyone,

    I have set $WL_HOME\server\lib\weblogic.jar and $WL_HOME\server\lib\weblogicaux.jar to classpath after run setWLSEnv.sh

    If I run this:
    java weblogic.Admin -url t3://localhost:7001 -unername johnny -password jy2003 SHUTDOWN

    Error :'Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/Admin

    Matthew

    DB:3.26:Exception In Thread "Main" Java.Lang.Noclassdeffounderror: Weblogic/Admin cp

    Hi everyone,

    I have set $WL_HOME\server\lib\weblogic.jar and $WL_HOME\server\lib\weblogicaux.jar to classpath after run setWLSEnv.sh

    If I run this:
    java weblogic.Admin -url t3://localhost:7001 -unername johnny -password jy2003 SHUTDOWN

    Error :'Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/Admin

    Matthew

  • RELEVANCY SCORE 3.26

    DB:3.26:Unable To Get Weblogic Initialcontext From Jboss-As-7.2.0.Alpha1-Snapshot 3p



    I have a very simple application deployed on jboss-as-7.2.0.Alpha1-SNAPSHOT and the application tries to lookup a queue on a weblogic server(10.0) which runs on jdk1.5.

    Both the jboss and weblogic are running on my local machine.

    Below is the code in a java file related to the lookup:

    Hashtable prop = new Hashtable();
    prop.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
    prop.put(Context.PROVIDER_URL, "t3://localhost:7001/");
    InitialContext context = new InitialContext(prop);

    DB:3.26:Unable To Get Weblogic Initialcontext From Jboss-As-7.2.0.Alpha1-Snapshot 3p


    I had already tried by adding the following path: path name="com/sun/corba/se/spi/legacy/connection"/ but with no luck.

    I just tried by following your suggestion of adding the path: path name="com/sun/corba"/ but still getting the same issue.

    Below is the part of the stacktrace:

    Caused by: java.lang.NoClassDefFoundError: com/sun/corba/se/spi/legacy/connection/ORBSocketFactory
    at java.lang.ClassLoader.defineClass1(Native Method) [rt.jar:1.6.0_35]
    at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) [rt.jar:1.6.0_35]
    at java.lang.ClassLoader.defineClass(ClassLoader.java:615) [rt.jar:1.6.0_35]
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) [rt.jar:1.6.0_35]
    at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:327) [jboss-modules.jar:1.1.3.GA]
    at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:391) [jboss-modules.jar:1.1.3.GA]
    ... 45 more

  • RELEVANCY SCORE 3.26

    DB:3.26:Problem With Stopweblogic.Sh dj


    Hello,

    When I launch stopWebLogic.sh, I get an "java.net.ProtocolException: Tunneling result unspecified"

    The problem seems to be with the admin_url;
    I tried t3://localhost:7001 or http://localhost:80 or http://server:80

    Any Idea?

    DB:3.26:Problem With Stopweblogic.Sh dj

    Hello,

    When I launch stopWebLogic.sh, I get an "java.net.ProtocolException: Tunneling result unspecified"

    The problem seems to be with the admin_url;
    I tried t3://localhost:7001 or http://localhost:80 or http://server:80

    Any Idea?

  • RELEVANCY SCORE 3.25

    DB:3.25:Migration Error ap


    Hi
    I am using OBIEE10 server1 Linux Box.Same machine i installed OBIEE11g.
    I am trying to migrate 10g into 11g. Ua wizard through error like

    when i give weblogic details:

    "UPGAST-00014:unable to connect to weblogic server at localhost:7001
    t3://localhost:7001: Destination unreachable;nested exception is: java.net.socketException:
    Connection reset;No available router to destination"

    All the services i can connecting well.
    http://ip:7001/em/
    http://ip:7001/console/
    http://ip:7001/analytics/

    How will fix this error.Pls advice me.

    DB:3.25:Migration Error ap

    When enter those detail then i apply all changes button.
    It return error messages
    "An error occurred during activation of changes, please see the log for details.
    [Management:141191]The prepare phase of the configuration update failed with an exception:
    Inconsistent channel updates"

    Admin server error log:
    EmbeddedLDAP Critical BEA-000000
    java.lang.NegativeArraySizeException at com.octetstring.vde.EntryChanges.readBytes(EntryChanges.java:274) at com.octetstring.vde.EntryChanges.init(EntryChanges.java:72) at com.octetstring.vde.replication.BackendChangeLog.getChange(BackendChangeLog.java:548) at com.octetstring.vde.replication.Replicator.run(Replicator.java:180) at com.octetstring.vde.replication.Replication.run(Replication.java:339)

    thanks

    Edited by: Raj on Nov 22, 2012 3:11 PM

    Edited by: Raj on Nov 22, 2012 6:14 PM

  • RELEVANCY SCORE 3.25

    DB:3.25:Managed Server-≫Admin Connection Problem 18


    Hi, I'm trying to get a managed server running (see my previous post re: the
    admin.host property problem). My latest attempts result in the managed
    server apparently failing to contact my running admin server. The managed
    server waits for 1 minute before producing the following traceback: (note
    that I can successfully ping the admin server at the attempted URL with
    "java weblogic.Admin -url T3://10.0.0.3:7001 PING"), and that I've tried
    various combinations of URL (http://, t3:// and T3://) and with all
    variations on hostname and IP address for this machine -- PING always works,
    and the managed server always fails).

    Any ideas?

    Thanks in advance,

    Tim

    Starting WebLogic Server ....
    Wed Oct 25 12:57:38 GMT-05:00 2000 Warning Management Unrecognized
    property: admin.host
    Wed Oct 25 12:58:39 GMT-05:00 2000 Error Configuration Management
    Error connecting to admin server and initializing admin home: admin URL:
    t3://10.0.0.3:7001
    javax.naming.CommunicationException. Root exception is
    java.net.ConnectException: No server found at T3://10.0.0.3:7001
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:215)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
    textFactoryDelegate.java:219)
    at weblogic.jndi.Environment.getContext(Environment.java:129)
    at weblogic.jndi.Environment.getInitialContext(Environment.java:112)
    at
    weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:712)
    at weblogic.management.Admin.start(Admin.java:295)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:357)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
    at weblogic.Server.main(Server.java:32)

    Wed Oct 25 12:58:39 GMT-05:00 2000 Emergency Server Unable to
    initialize the server: Fatal initialization exception
    Throwable: weblogic.management.configuration.ConfigurationException: admin
    URL: t3://10.0.0.3:7001 - with nested exception:
    [javax.naming.CommunicationException [Root exception is
    java.net.ConnectException: No server found at T3://10.0.0.3:7001]]
    weblogic.management.configuration.ConfigurationException: admin URL:
    t3://10.0.0.3:7001 - with nested exception:
    [javax.naming.CommunicationException [Root exception is
    java.net.ConnectException: No server found at T3://10.0.0.3:7001]]
    at
    weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:719)
    at weblogic.management.Admin.start(Admin.java:295)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:357)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
    at weblogic.Server.main(Server.java:32)
    .
    .
    .

    DB:3.25:Managed Server-≫Admin Connection Problem 18

    More on this:

    I should mention that this is happening on Solaris 2.7, with all the
    recommended patches. It all seems to work fine on Windows 2000. Also, the
    admin server does appear to be sending the managed server its config data
    etc. -- at least according to the 'truss' command I ran against the admin VM
    as I was starting the managed server.

    Tim

    "Timothy Fry" tim@imoney.com wrote in message
    news:39f7230a$1@newsgroups.bea.com...
    Hi, I'm trying to get a managed server running (see my previous post re:the
    admin.host property problem). My latest attempts result in the managed
    server apparently failing to contact my running admin server. The managed
    server waits for 1 minute before producing the following traceback: (note
    that I can successfully ping the admin server at the attempted URL with
    "java weblogic.Admin -url T3://10.0.0.3:7001 PING"), and that I've tried
    various combinations of URL (http://, t3:// and T3://) and with all
    variations on hostname and IP address for this machine -- PING alwaysworks,
    and the managed server always fails).

    Any ideas?

    Thanks in advance,

    Tim

    Starting WebLogic Server ....
    Wed Oct 25 12:57:38 GMT-05:00 2000 Warning Management Unrecognized
    property: admin.host
    Wed Oct 25 12:58:39 GMT-05:00 2000 Error Configuration Management
    Error connecting to admin server and initializing admin home: admin URL:
    t3://10.0.0.3:7001
    javax.naming.CommunicationException. Root exception is
    java.net.ConnectException: No server found at T3://10.0.0.3:7001
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:215)
    atweblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
    textFactoryDelegate.java:219)
    at weblogic.jndi.Environment.getContext(Environment.java:129)
    atweblogic.jndi.Environment.getInitialContext(Environment.java:112)
    at
    weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:712)
    at weblogic.management.Admin.start(Admin.java:295)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:357)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
    at weblogic.Server.main(Server.java:32)

    Wed Oct 25 12:58:39 GMT-05:00 2000 Emergency Server Unable to
    initialize the server: Fatal initialization exception
    Throwable: weblogic.management.configuration.ConfigurationException: admin
    URL: t3://10.0.0.3:7001 - with nested exception:
    [javax.naming.CommunicationException [Root exception is
    java.net.ConnectException: No server found at T3://10.0.0.3:7001]]
    weblogic.management.configuration.ConfigurationException: admin URL:
    t3://10.0.0.3:7001 - with nested exception:
    [javax.naming.CommunicationException [Root exception is
    java.net.ConnectException: No server found at T3://10.0.0.3:7001]]
    at
    weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:719)
    at weblogic.management.Admin.start(Admin.java:295)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:357)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
    at weblogic.Server.main(Server.java:32)
    .
    .
    .

  • RELEVANCY SCORE 3.25

    DB:3.25:Jdeveloper - Weblogic - Javax.Naming.Communicationexception 3x


    When I tried to connect to weblogic 7.0 through jdeveloper ide, I got the following error message.

    javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
    java.net.ConnectException: Connection refused: connect; No available router to destination]

    Plz let me know any information or fix for this problem

  • RELEVANCY SCORE 3.24

    DB:3.24:Connecto To Localhost Got Broken s8


    I installed OBIEE. Verified that all three urls work and was able to login as weblogic.
    After I created RPD and wanted to use

    http://localhost:7001/em

    but getting error message that
    Oops! Google Chrome could not connect to localhost:7001.

    I can not go to any of the three urls
    Oracle Business Intelligence- http://localhost:9704/analytics
    WebLogic Console- http://localhost:7001/console
    Enterprise Manager- http://localhost:7001/em

    I have rebooted the system few times.

    Thank you very much
    Sincerely
    j

    DB:3.24:Connecto To Localhost Got Broken s8

    please check the status of services by using opmnctl command check whether are all services are "Alive".

    http://123obi.com/2011/03/manage-opmn-processes-in-obiee-11g/

  • RELEVANCY SCORE 3.24

    DB:3.24:Authenticationexception While Using Weblogic.Deployer Utility.. d3



    Hello All,

    when I try to deploy an application using weblogic.Deployer utility the application
    throws an AuthenticationException stating user is installadministrator.

    Can anybody please advise me on this???

    thanks in advance..

    here is the stack trace...
    Unable to connect server t3://localhost:7001 as user installadministrator.
    Reason: javax.naming.AuthenticationException [Root exception is java.lang.SecurityException:
    User:
    installadministrator, failed to be authenticated.

    Check option -adminurl, -user and -password.


    DB:3.24:Authenticationexception While Using Weblogic.Deployer Utility.. d3


    Hi Yeshwant,

    I thank your efforts but I 've been trying with the usr/pwd which I use to boot
    the WLS server still it is giving me this exception.

    I also tried to create a user with administrative rights in Realms in the console
    admin. but this time too it was throwing the same Exception.

    please advise me further.

    Thnaks and regards
    pavan

    Yeshwant ymk@nospam.com wrote:
    Hi Pavan,
    weblogic.Deployer uses the defaut user called "installadministrator"
    If this user doesnot exist you will get the exception
    I suggest that you use
    java weblogic.Deployer -user username -password password
    where username and password are valid in your system.
    For example you can use the username and password which you use to boot
    the weblogic server
    If you dont specify any username and password it will try to use installadministrator
    and fail
    with that exception.

    Pavan wrote:

    Hello All,

    when I try to deploy an application using weblogic.Deployer utilitythe application
    throws an AuthenticationException stating user is installadministrator.

    Can anybody please advise me on this???

    thanks in advance..

    here is the stack trace...
    Unable to connect server t3://localhost:7001 as user installadministrator.
    Reason: javax.naming.AuthenticationException [Root exception is java.lang.SecurityException:
    User:
    installadministrator, failed to be authenticated.

    Check option -adminurl, -user and -password.

  • RELEVANCY SCORE 3.24

    DB:3.24:Java.Net.Noroutetohostexception jx



    Hello,

    I am getting a strange exception. It is like this
    Info ConnectionManager medha examplesServer ExecuteThread: '14' for queue:
    'default' 000000 Bootstrap unable to get a direct: 'Protocol: 't3''connection
    to: '0S:68.100.54.176:[7001,-1,-1,-1,-1,-1,-1]' on port: '7001'

    I observe a strange thing. 68.100.54.176, I presume it as a IP address. I dont know
    where server is picking up this address. I am running this on localhost(127.0.0.1).
    Every time the above OS:68... is changing.

    Can any one tell what is this about?

    Thanks.
    Jag

    DB:3.24:Java.Net.Noroutetohostexception jx


    Hi Jag,
    Please delete the .tlog files in your logs directory.This should solve the problem.

    Regards
    Siva

    "jag" jvelaga1@yahoo.com wrote:

    Hello,

    I am getting a strange exception. It is like this
    Info ConnectionManager medha examplesServer ExecuteThread: '14'
    for queue:
    'default' 000000 Bootstrap unable to get a direct: 'Protocol:
    't3''connection
    to: '0S:68.100.54.176:[7001,-1,-1,-1,-1,-1,-1]' on port: '7001'

    I observe a strange thing. 68.100.54.176, I presume it as a IP address.
    I dont know
    where server is picking up this address. I am running this on localhost(127.0.0.1).
    Every time the above OS:68... is changing.

    Can any one tell what is this about?

    Thanks.
    Jag

  • RELEVANCY SCORE 3.24

    DB:3.24:Need Help With Wlst Script dp


    I am having problems with the below code. Its failing at the second connect statement. Any help appreciated

    username='monitor'
    password='monitors
    urldict={}
    connect(username,password,'t3://localhost:7001')
    serverlist=adminHome.getMBeansByType('Server')
    #serverlist=getRunningServerNames()
    for svr in serverlist:
    #cd("/Servers/"+svr.getName())
    urldict[svr.getName()]='t3://'+svr.getListenAddress()+':'+str(svr.getListenPort())

    disconnect()

    for svr,url in urldict.items():
    try:
    connect(username,password,url)
    print 'connected'
    jvmrtlist=home.getMBeansByType('JVMRuntime')
    for jvmRT in jvmrtlist:
    freejvm = jvmRT.getAttribute("HeapFreeCurrent")
    print freejvm

    disconnect()
    except:
    print "Skipping "+svr
    continue

    Output is:

    Connecting to t3://localhost:7001 with userid monitor ...
    Successfully connected to Admin Server 'adminServer that belongs to domain 'TestDomain.

    Disconnected from weblogic server: adminServer
    Connecting to t3://localhost:1280 with userid ...

    The CompatabilityMBeanServer is not initialized properly.
    This might happen if the CompatabilityMBeanServer is
    disabled via the JMXMBean.

    To view the root cause exception use dumpStack()

    WLST detected that the RuntimeMBeanServer is not enabled. This
    might happen if the RuntimeMBeanServer is disabled via the JMXMBean.
    Please ensure that this MBeanServer is enabled. Online WLST cannot
    function without this MBeanServer.
    Skipping mngServer1

    DB:3.24:Need Help With Wlst Script dp

    I am having problems with the below code. Its failing at the second connect statement. Any help appreciated

    username='monitor'
    password='monitors
    urldict={}
    connect(username,password,'t3://localhost:7001')
    serverlist=adminHome.getMBeansByType('Server')
    #serverlist=getRunningServerNames()
    for svr in serverlist:
    #cd("/Servers/"+svr.getName())
    urldict[svr.getName()]='t3://'+svr.getListenAddress()+':'+str(svr.getListenPort())

    disconnect()

    for svr,url in urldict.items():
    try:
    connect(username,password,url)
    print 'connected'
    jvmrtlist=home.getMBeansByType('JVMRuntime')
    for jvmRT in jvmrtlist:
    freejvm = jvmRT.getAttribute("HeapFreeCurrent")
    print freejvm

    disconnect()
    except:
    print "Skipping "+svr
    continue

    Output is:

    Connecting to t3://localhost:7001 with userid monitor ...
    Successfully connected to Admin Server 'adminServer that belongs to domain 'TestDomain.

    Disconnected from weblogic server: adminServer
    Connecting to t3://localhost:1280 with userid ...

    The CompatabilityMBeanServer is not initialized properly.
    This might happen if the CompatabilityMBeanServer is
    disabled via the JMXMBean.

    To view the root cause exception use dumpStack()

    WLST detected that the RuntimeMBeanServer is not enabled. This
    might happen if the RuntimeMBeanServer is disabled via the JMXMBean.
    Please ensure that this MBeanServer is enabled. Online WLST cannot
    function without this MBeanServer.
    Skipping mngServer1

  • RELEVANCY SCORE 3.22

    DB:3.22:Lookup An Object From Jndi Using Http Instead Of T3 3z


    Hi All,

    I have written a JMS client sending message to my WLS JMS server. I success
    while looking up objects and connecting to t3://localhost:7001. But when I
    changed the connection url to http://localhost:7001. Below error occur:

    javax.naming.CommunicationException. Root exception is
    java.net.ConnectExceptio
    n: http://localhost:7001: Destination unreachable; nested exception is:
    java.net.ProtocolException: Tunneling result unspecified - is the
    HTTP s
    erver at host: 'localhost' and port: '7001' a WebLogic Server?; No available
    rou
    ter to destination
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:173)
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:262)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
    tialContextFactoryDelegate.java:323)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
    tialContextFactoryDelegate.java:221)
    at
    weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialCont
    extFactory.java:149)
    at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
    at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
    at javax.naming.InitialContext.init(Unknown Source)
    at javax.naming.InitialContext.init(Unknown Source)
    at chat.Chat.init(Chat.java:28)
    at chat.Chat.main(Chat.java:104)

    How can I connect to WLS using http instead of t3? What I have to set or
    enable in the console? Is it better to use http rather than t3 while
    connecting remotely passing through firewall? Thx a lot.

    DB:3.22:Lookup An Object From Jndi Using Http Instead Of T3 3z

    You have to enable HTTP tunneling - in the console-server-protocols.

    Karen Law kawai@alumni.cse.cuhk.edu.hk wrote:
    Hi All,I have written a JMS client sending message to my WLS JMS server. I success
    while looking up objects and connecting to t3://localhost:7001. But when I
    changed the connection url to http://localhost:7001. Below error occur:javax.naming.CommunicationException. Root exception is
    java.net.ConnectExceptio
    n: http://localhost:7001: Destination unreachable; nested exception is:
    java.net.ProtocolException: Tunneling result unspecified - is the
    HTTP s
    erver at host: 'localhost' and port: '7001' a WebLogic Server?; No available
    rou
    ter to destination
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:173)
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:262)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
    tialContextFactoryDelegate.java:323)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
    tialContextFactoryDelegate.java:221)
    at
    weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialCont
    extFactory.java:149)
    at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
    at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
    at javax.naming.InitialContext.init(Unknown Source)
    at javax.naming.InitialContext.init(Unknown Source)
    at chat.Chat.init(Chat.java:28)
    at chat.Chat.main(Chat.java:104)How can I connect to WLS using http instead of t3? What I have to set or
    enable in the console? Is it better to use http rather than t3 while
    connecting remotely passing through firewall? Thx a lot.--
    Dimitri

  • RELEVANCY SCORE 3.21

    DB:3.21:Re: Managed Server-≫Admin Connection Problem jx


    Do you get any error on the Admin server, when you attempt to start the
    managed server ?

    Timothy Fry tim@imoney.com wrote in message
    news:39f7230a$1@newsgroups.bea.com...
    Hi, I'm trying to get a managed server running (see my previous post re:the
    admin.host property problem). My latest attempts result in the managed
    server apparently failing to contact my running admin server. The managed
    server waits for 1 minute before producing the following traceback: (note
    that I can successfully ping the admin server at the attempted URL with
    "java weblogic.Admin -url T3://10.0.0.3:7001 PING"), and that I've tried
    various combinations of URL (http://, t3:// and T3://) and with all
    variations on hostname and IP address for this machine -- PING alwaysworks,
    and the managed server always fails).

    Any ideas?

    Thanks in advance,

    Tim

    Starting WebLogic Server ....
    Wed Oct 25 12:57:38 GMT-05:00 2000 Warning Management Unrecognized
    property: admin.host
    Wed Oct 25 12:58:39 GMT-05:00 2000 Error Configuration Management
    Error connecting to admin server and initializing admin home: admin URL:
    t3://10.0.0.3:7001
    javax.naming.CommunicationException. Root exception is
    java.net.ConnectException: No server found at T3://10.0.0.3:7001
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:215)
    atweblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
    textFactoryDelegate.java:219)
    at weblogic.jndi.Environment.getContext(Environment.java:129)
    atweblogic.jndi.Environment.getInitialContext(Environment.java:112)
    at
    weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:712)
    at weblogic.management.Admin.start(Admin.java:295)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:357)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
    at weblogic.Server.main(Server.java:32)

    Wed Oct 25 12:58:39 GMT-05:00 2000 Emergency Server Unable to
    initialize the server: Fatal initialization exception
    Throwable: weblogic.management.configuration.ConfigurationException: admin
    URL: t3://10.0.0.3:7001 - with nested exception:
    [javax.naming.CommunicationException [Root exception is
    java.net.ConnectException: No server found at T3://10.0.0.3:7001]]
    weblogic.management.configuration.ConfigurationException: admin URL:
    t3://10.0.0.3:7001 - with nested exception:
    [javax.naming.CommunicationException [Root exception is
    java.net.ConnectException: No server found at T3://10.0.0.3:7001]]
    at
    weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:719)
    at weblogic.management.Admin.start(Admin.java:295)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:357)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
    at weblogic.Server.main(Server.java:32)
    .
    .
    .

    DB:3.21:Re: Managed Server-≫Admin Connection Problem jx

    i am starting the managed server and it is giving an error unable to instantiate admin home

  • RELEVANCY SCORE 3.21

    DB:3.21:Wlst - Cd Does Not Work!?! xx


    Hi,

    I have some WLST jython scripts I got of the dev2dev site and I even ventured to write a simple one myself. The problem is that I can not create any JMSQueue with the following sequence in a WLI domain:

    connect("weblogic", "weblogic", "t3://localhost:7001")
    cd("/")
    cd("JMSServers/cgJMSServer")
    create("myq", "JMSQueue")The error I get is:
    "Error occured while performing create : Cannot create MBean of type JMSQueue. You can only create MBean's children to the current cmo of type: Domain. Use dumpStack() to view the error stack trace"

    When I do the following:

    connect("weblogic", "weblogic", "t3://localhost:7001")
    cd("/")
    cd("JMSServers/cgJMSServer")
    pwd()I get empty string back. Of course, the server is up and running.

    Any help/hints will be highly appreciated.

    Thanks,
    G

    DB:3.21:Wlst - Cd Does Not Work!?! xx

    Yes, i found an answer - I got a later version of WLST! Now, the real issue was to find out where to download WLST. Try this link:

    https://codesamples.projects.dev2dev.bea.com/servlets/Scarab?id=13

    Cheers,
    G

  • RELEVANCY SCORE 3.21

    DB:3.21:Upgrade From 3.1.1.305 To 399 Failing 97


    Running the upgrade process results in the following error being presented

    Last section of the message
    Welcome to WebLogic Server Administration Scripting Shell Type help() for help on available commands wls:/offline Connecting to t3://localhost:7001 with userid weblogic ... Traceback (innermost last): File "console", line 1, in ? File "iostream", line 22, in connect File "iostream", line 646, in raiseWLSTException WLSTException: Error occured while performing connect : Error getting the initial context. There is no server running at t3://localhost:7001 Use dumpStack() to view the full stacktrace wls:/offline You will need to be connected to a running server to execute this command wls:/offline

    For some reason the upgrade process is trying to connect to the app on localhost:7001 but it's not listening on that interface.

    [root@ovm media]# netstat -tulpn | grep -E 700
    tcp 0 0 ::ffff:192.168.40.10:7001 :::* LISTEN 17238/java
    tcp 0 0 ::ffff:192.168.40.10:7002 :::* LISTEN 17238/java

    DB:3.21:Upgrade From 3.1.1.305 To 399 Failing 97

    Greetings,

    I saw this one a couple weeks ago with both demo and prod installs on OL58 and OL63. Looks like a bug :-)

    We opned an SR and about 5 days later Oracle support said it was an ipv6 issue! We did not evan enable IPV6. It killed the project!

    Check this: Re: Failed to enable Https - OVM installation

    Regards,
    Roddy

  • RELEVANCY SCORE 3.20

    DB:3.20:Cannot Be Deployed m8



    javax.naming.CommunicationException. Root exception is java.net.ConnectException:
    t3://localhost:7001: Destination unreachable; nested exception is:
    java.net.ConnectException: Connection refused: connect; No available router to
    destination

    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)

    at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125)

    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:291)

    at weblogic.jndi.Environment.getContext(Environment.java:164)

    at weblogic.jndi.Environment.getInitialContext(Environment.java:143)

    at weblogic.marathon.server.ServerData.initHome(ServerData.java:401)

    at weblogic.marathon.server.ServerData.connectToServer(ServerData.java:121)

    at weblogic.marathon.tasks.ConnectServerTask.runBackground(ConnectServerTask.java:22)

    at weblogic.tools.jellybeans.core.task.TaskThread.execute(TaskThread.java:127)

    at weblogic.tools.jellybeans.core.task.TaskThread.run(TaskThread.java:64)

    --------------- nested within: ------------------

    weblogic.marathon.server.ServerException - with nested exception:

    [javax.naming.CommunicationException [Root exception is java.net.ConnectException:
    t3://localhost:7001: Destination unreachable; nested exception is:
    java.net.ConnectException: Connection refused: connect; No available router to
    destination]]

    at weblogic.marathon.server.ServerData.connectToServer(ServerData.java:134)

    at weblogic.marathon.tasks.ConnectServerTask.runBackground(ConnectServerTask.java:22)

    at weblogic.tools.jellybeans.core.task.TaskThread.execute(TaskThread.java:127)

    at weblogic.tools.jelly

  • RELEVANCY SCORE 3.20

    DB:3.20:Weblogic With Soa T3://Soaebs.Iwarlogic.Com:7001 Destination Unreachable 1k


    Hello,

    I just installed WebLogic 10.3.4 on RHEL 5.4 and then SOASuite 11.1.1.5.0
    Created a weblogic domain yo_domain with EM, SOA and BPM selected, had only Admin server in the domain and no Managed server(s).

    When I go to location
    */home/oracle/Oracle/Middleware/user_projects/domains/yo_domain/bin*

    and do
    ./setDoaminEnv.sh and then
    ./startWebLogic.sh

    I get following exception
    Unable to connect to the Oracle WSM Policy manager due to following error
    "javax.naming.CommunicationException [ Root exception is java.net.ConnectException: t3://soaebs.iwarelogic.com:7001: Destination unreachable; nested exceptio nis:
    java.net.ConnectException: Connection refused; No available router to destination]".soaebs.iwarelogic.com is the machine name and has correct entry in /etc/hosts file

    I am able to connect to both
    http://soaebs.iwarelogic.com:7001/console and
    http://soaebs.iwarelogic.com:7001/em

    What can be cause of this error?
    When domain got created, message dialogue said
    Admin Server Url is "http://soaebs.iwarelogic.com:7001"

    regards, Yora

    DB:3.20:Weblogic With Soa T3://Soaebs.Iwarlogic.Com:7001 Destination Unreachable 1k

    Cross check the listen address of Weblogic server's in the domain. Have you provided any value in listen address and if yes then what?

    Regards,
    Anuj

  • RELEVANCY SCORE 3.20

    DB:3.20:Error With Sessionbeans:Destination Unreachable 3d


    Hi all,
    I'm trying to develop a simple Session Bean using Weblogic 8.1.
    While deploying i got message as ejbc successful.
    But while running client application i got following error.
    Please anyone help to resolve this.
    Thanks,
    latha

    E:\slsbjava Client
    Exception in thread "main" javax.naming.CommunicationException [Root exception i
    s java.net.ConnectException: t3://raghu:7001: Destination unreachable; neste
    d exception is:
    java.net.SocketException: Invalid argument: connect; No available router
    to destination]
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(Exceptio
    nTranslator.java:47)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLIni
    tialContextFactoryDelegate.java:636)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
    tialContextFactoryDelegate.java:306)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
    tialContextFactoryDelegate.java:239)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialCont
    extFactory.java:135)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
    62)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243
    )
    at javax.naming.InitialContext.init(InitialContext.java:219)
    at javax.naming.InitialContext.init(InitialContext.java:195)
    at Client.main(Client.java:12)
    Caused by: java.net.ConnectException: t3://localhost:7001: Destination unreachab
    le; nested exception is:
    java.net.SocketException: Invalid argument: connect; No available router
    to destination
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
    tialContextFactoryDelegate.java:296)
    ... 7 more

    DB:3.20:Error With Sessionbeans:Destination Unreachable 3d

    Please check the following:
    1. Check whether the weblogic is running on the localhost.
    2. Check the port address is right or wrong
    (I have never used weblogic so I can't tell you how to check it, if you don't know then browse the google)

    3. Change the server name to 127.0.0.1 in the client code.

    If the server is running perfectly at 127.0.0.1:7001 then there should be no problem. So check this constraints first.

    Note: I have used Websphere there are lots of ports, the one I need for lookup in websphere is the BOOTSTRAP_ADDRESS. There are many other ports also. In websphere one can create multiple profile and for that profil;e this prot address varies from 2809,2810... etc.. I don't know whether in weblogic it is called as BOOTSTRAP_ADDRESS or not. But you have ensure that the particular port for weblogic (to perform lookup) is 7001 in your m/c. Please search through google for getting information on how to know the port in weblogic.

  • RELEVANCY SCORE 3.19

    DB:3.19:How To Connect Admin Server Thorugh Wlst sj


    Hi ,

    I am connecting to nodemanager thorugh nmConnect() command but i am getting follwoing error..

    Welcome to WebLogic Server Administration Scripting Shell

    Type help() for help on available commands

    wls:/offline connect()
    Please enter your username ["weblogic"] : system
    Please enter your password ["weblogic"] :
    Please enter the url ["t3://localhost:7001"] : t3://localhost:7001

    Connecting to weblogic server instance running at t3://localhost:7001 as username system ...

    Successfully connected to Admin Server 'AdminServer' that belongs to domain 'dizzyworld'.

    Warning: An insecure protocol was used to connect to the server.
    To ensure on-the-wire security, the SSL port or Admin port
    should be used instead.

    wls:/dizzyworld/serverConfig nmConnect('weblogic'.'weblogic','localhost','5556','dizzyworld','c:/student/course/work/domains','plain')
    Traceback (innermost last):
    (no code object) at line 0
    File "console", line 1
    nmConnect('weblogic'.'weblogic','localhost','5556','dizzyworld','c:/student/course/work/domains','plain')
    ^
    SyntaxError: invalid syntax
    wls:/dizzyworld/serverConfig nmConnect('system','weblogic','localhost','5556','dizzyworld','c:/student/course/work/domains','plain')

    Connecting to Node Manager ...
    Traceback (innermost last):
    File "console", line 1, in ?
    File "iostream", line 1447, in nmConnect
    WLSTException: "Error occured while performing nmConnect : Cannot connect to the Node Manager.Connection refused: connect. Couldn't connect to
    r. Check that it is running at localhost:5556 Use dumpStack() to view the full stacktrace"
    wls:/dizzyworld/serverConfig

    DB:3.19:How To Connect Admin Server Thorugh Wlst sj

    Hello

    ('weblogic'.'weblogic'

    You put a dot, so the jython syntax is invalid.

    Regards.

  • RELEVANCY SCORE 3.18

    DB:3.18:Jdev 11.1 And Bea 8.1 fj


    I just istalled JDev 11.1.1.01, since I want to compare it to Eclipse with the MyEclipse extension.

    This project uses Bea 8.1 and Bea 9.2 servers with DSP and the Service Bus. When I try to create a connection to existing server domains on the local machine the connection fails withe errors:

    Testing JSR-88 ... failed.
    [J2EE Deployment SPI:260010]Unable to connect to 't3://localhost:7001' as user, 'weblogic'. Error received: While trying to lookup 'weblogic.management.mbeanservers.domainruntime' didn't find subcontext 'mbeanservers' Resolved weblogic.management
    Testing JSR-88-LOCAL ... failed.
    [J2EE Deployment SPI:260010]Unable to connect to 't3://localhost:7001' as user, 'weblogic'. Error received: While trying to lookup 'weblogic.management.mbeanservers.domainruntime' didn't find subcontext 'mbeanservers' Resolved weblogic.management
    Testing JSR-160 DomainRuntime ... failed.
    While trying to lookup 'weblogic.management.mbeanservers.domainruntime' didn't find subcontext 'mbeanservers' Resolved weblogic.management
    Testing JSR-160 Runtime ... failed.
    While trying to lookup 'weblogic.management.mbeanservers.runtime' didn't find subcontext 'mbeanservers' Resolved weblogic.management
    Testing JSR-160 Edit ... failed.
    While trying to lookup 'weblogic.management.mbeanservers.edit' didn't find subcontext 'mbeanservers' Resolved weblogic.management
    Testing HTTP ... success.
    Testing Server MBeans Model ... failed.
    While trying to lookup 'weblogic.management.mbeanservers.domainruntime' didn't find subcontext 'mbeanservers' Resolved weblogic.management

    1 of 7 tests successful.

    When I creates the server connection from File = Create Application Server Connection Step 1 of 5 I only have the possibility to create a Weblogic 10.3 Connection Type.

    Is JDev 11g not able to connect to a Bea 8.1 domain?

    DB:3.18:Jdev 11.1 And Bea 8.1 fj

    Thanks for the replies. I will try JDev 10.3 which also should be fine for this project

  • RELEVANCY SCORE 3.18

    DB:3.18:Wl Passwords Reported In Clear Text jk



    WL 6.1 SP1:
    weblogic.deploy reports passwords in clear text when connection to the server
    failed. The command is inside a batch file (with @echo off) so the password is
    not visible when the command is sent but anyone looking over your shoulders can
    read your password as the error comes back to the screen.

    JNDI naming exception: Naming exception trying to connect to: t3://localhost:7001
    as: system: myPassword

    DB:3.18:Wl Passwords Reported In Clear Text jk


    WL 6.1 SP1:
    weblogic.deploy reports passwords in clear text when connection to the server
    failed. The command is inside a batch file (with @echo off) so the password is
    not visible when the command is sent but anyone looking over your shoulders can
    read your password as the error comes back to the screen.

    JNDI naming exception: Naming exception trying to connect to: t3://localhost:7001
    as: system: myPassword

  • RELEVANCY SCORE 3.18

    DB:3.18:Connect To Weblogic Server's Jvm fd


    Hello everybody,

    Im trying connect to weblogic servers JVM to execute a class inside the jar.

    It works fine, but my jar has a class with static atributes that I want change its values calling the following command line:

    %JAVA_HOME%\bin\java -Djavax.naming.Context.INITIAL_CONTEXT_FACTORY=weblogic.jndi.WLInitialContextFactory -Djavax.naming.Context.PROVIDER_URL=t3://localhost:7001 -jar %_APP_HOME%\WEB-INF\lib\AdminServer.jar -1

    Afer it the values of my class atribute has changed but my web application does not see this news values.

    I thinking... Am I connected to weblogic servers JVM ?

    Could Anyone help me?

    DB:3.18:Connect To Weblogic Server's Jvm fd

    You need to take a step back and think about what you're trying to achieve, Denilson.

    Using static attributes in classes has all sorts of side-effects because of how classloaders work in J2EE - if you're referencing a class used inside the web application and poking a static property, what is most likely happening is that your local application is loading the class in its own classloader, modifying the property, and then exiting. A separate copy of the class has been loaded by the web application.

    You can see more information on classloaders here: http://edocs.bea.com/wls/docs81/programming/classloading.html#1089798

    If you want to run an application to change some value on the server, there are a number of options available:

    - getting, changing and replacing an object in the JNDI tree (this is still an ugly solution)
    - using a servlet or stateless session bean to get the job done (this is a better solution - simple, but still not as good as you could potentially get)

    I'd suggest using a servlet to modify an attribute scoped at the web application level as a lightweight way to do what you're trying to. i(if I'm understanding what your goal is correctly)/i. That way you could test making changes with your browser, not just a Java application.

    Does any of that help?
    br
    --
    Kevin Powe
    http://www.integral-techsolutions.com

  • RELEVANCY SCORE 3.15

    DB:3.15:Weblogic.Admin Start Command Not Working. Help sx


    I have a weblogic 8.1 domain. I have set weblogic.jar in classpath and i am using BEA JDK 1.4.2_05

    I tried to SHUTDOWN and do GETSTATE for a server, and it worked fine.

    The command is used is

    java weblogic.Admin -url localhost:7001 -username weblogic -password weblogic SHUTDOWN / GETSTATE.

    But after shuting down, when i used the command to START as

    java weblogic.Admin -url localhost:7001 -username weblogic -password weblogic START myserver

    i am getting the exception,
    Failed to connect to t3://localhost:7001: Destination unreachable; nested exception is:
    java.net.ConnectException: Connection refused: connect; No available router to des
    tination

    Obviously, the server has been shutdown, and i am using this command to start it back, Why am i getting this error. I need this to control the weblogic domain from remote machine.

    DB:3.15:Weblogic.Admin Start Command Not Working. Help sx

    Hello

    we need to specify ploicy file name and WLS home
    . and try

    http://e-docs.bea.com/wls/docs81/isv/startup.html

  • RELEVANCY SCORE 3.14

    DB:3.14:Diff B/W Creating Reports Using (Http://Localhost:7001/Analytics) And Using (Http://Localhost:7001/Xmlpserver) 77


    Hi,I am the beginner to OBIEE. Could you please tell me what is the difference between creating reports using (http://localhost:7001/analytics) and using (http://localhost:7001/xmlpserver).Why 2 ways to create reports?Waiting for your answer eagerly...............ThanksRamesh

    DB:3.14:Diff B/W Creating Reports Using (Http://Localhost:7001/Analytics) And Using (Http://Localhost:7001/Xmlpserver) 77

    As I said, two different products with different focuses:BIP: Oracle Business Intelligence PublisherBIEE: Oracle Business Intelligence Foundation SuiteThey didn't call it "Create Analysis" and "Create Report" without a reason...

  • RELEVANCY SCORE 3.14

    DB:3.14:Weblogic.Deployer Connection Exception ka



    java -classpath weblogic.jar weblogic.Deployer -adminurl http://localhost:7001
    -user test -password 12345678 -list
    always gives the result:

    Unable to connect server t3://localhost:7001 as user test.
    Reason: javax.naming.CommunicationException [Root exception is java.net.Connect
    Exception: t3://localhost:7001: Destination unreachable; nested exception
    is:
    java.net.ConnectException: Connection refused: connect; No available router
    to destination]
    Check option -adminurl, -user and -password.

    However if I try in my favorite browser http://localhost:7001/console then everything
    is fine. I get the same exception if I replace localhost with an IP number or
    the actual server name.

    What am I doing wrong?

    Thanks in advance,

    Lars.

    DB:3.14:Weblogic.Deployer Connection Exception ka

    Lars,
    Try connecting through t3 instead of http. You can use http only if you
    have enabled HTTPTunnelling.
    Try,
    java -classpath weblogic.jar weblogic.Deployer -adminurl
    t3://localhost:7001 -user test -password 12345678 -list

    Thanks,
    -satya

    Lars Nielsen wrote:
    java -classpath weblogic.jar weblogic.Deployer -adminurl http://localhost:7001
    -user test -password 12345678 -list
    always gives the result:

    Unable to connect server t3://localhost:7001 as user test.
    Reason: javax.naming.CommunicationException [Root exception is java.net.Connect
    Exception: t3://localhost:7001: Destination unreachable; nested exception
    is:
    java.net.ConnectException: Connection refused: connect; No available router
    to destination]
    Check option -adminurl, -user and -password.

    However if I try in my favorite browser http://localhost:7001/console then everything
    is fine. I get the same exception if I replace localhost with an IP number or
    the actual server name.

    What am I doing wrong?

    Thanks in advance,

    Lars.

  • RELEVANCY SCORE 3.14

    DB:3.14:Wlst : Error Connecting To A Remote Weblogic Server Instance From Oepe 3.7 df


    Attempting a to run a weblogic script connecting to a remote weblogic server instance (10.3.5), which is generating the following exception in OEPE 3.7.2 -

    username = 'weblogic'
    password = 'weblogic6'
    url='t3://xxx.xxx.com:7001'
    connect(username,password,url)

    Connecting to t3://xxx.xxx.com:7001 with userid weblogic ...
    This Exception occurred at Fri Feb 01 13:20:54 MST 2013.
    Error occured while performing connect : Error connecting to the server : Failed to generate class for weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl_1035_WLStub
    Use dumpStack() to view the full stacktrace :
    java.lang.AssertionError: Failed to generate class for weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl_1035_WLStubconnect
    Problem invoking WLST - Traceback (innermost last):
    File "C:\Users\hughese\workspace\12c_wlst\wlst\heapsize.py", line 13, in ?
    File "iostream", line 22, in connect
    File "iostream", line 648, in raiseWLSTException
    WLSTException: Error occured while performing connect : Error connecting to the server : Failed to generate class for weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl_1035_WLStub
    Use dumpStack() to view the full stacktrace

    Connecting to the local weblogic server instance (t3://localhost:7001) works okay.

    From the command prompt (wlst.cmd) I'm able to connect to the remote weblogic server instance -

    wls:/offline connect('weblogic','xxxxx','t3:xxx.xxx.com:7001') ;
    Connecting to t3://xxx.xxx.com:7001 with userid weblogic ...
    Successfully connected to Admin Server 'AdminServer' that belongs to domain 'IDMDomain'.

    I've compared the CLASSPATHs between OEPE and the command prompt.

    Any assistance would be greatly appreciated.

    Edited by: 950635 on Feb 1, 2013 7:47 PM

    DB:3.14:Wlst : Error Connecting To A Remote Weblogic Server Instance From Oepe 3.7 df

    Attempting a to run a weblogic script connecting to a remote weblogic server instance (10.3.5), which is generating the following exception in OEPE 3.7.2 -

    username = 'weblogic'
    password = 'weblogic6'
    url='t3://xxx.xxx.com:7001'
    connect(username,password,url)

    Connecting to t3://xxx.xxx.com:7001 with userid weblogic ...
    This Exception occurred at Fri Feb 01 13:20:54 MST 2013.
    Error occured while performing connect : Error connecting to the server : Failed to generate class for weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl_1035_WLStub
    Use dumpStack() to view the full stacktrace :
    java.lang.AssertionError: Failed to generate class for weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl_1035_WLStubconnect
    Problem invoking WLST - Traceback (innermost last):
    File "C:\Users\hughese\workspace\12c_wlst\wlst\heapsize.py", line 13, in ?
    File "iostream", line 22, in connect
    File "iostream", line 648, in raiseWLSTException
    WLSTException: Error occured while performing connect : Error connecting to the server : Failed to generate class for weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl_1035_WLStub
    Use dumpStack() to view the full stacktrace

    Connecting to the local weblogic server instance (t3://localhost:7001) works okay.

    From the command prompt (wlst.cmd) I'm able to connect to the remote weblogic server instance -

    wls:/offline connect('weblogic','xxxxx','t3:xxx.xxx.com:7001') ;
    Connecting to t3://xxx.xxx.com:7001 with userid weblogic ...
    Successfully connected to Admin Server 'AdminServer' that belongs to domain 'IDMDomain'.

    I've compared the CLASSPATHs between OEPE and the command prompt.

    Any assistance would be greatly appreciated.

    Edited by: 950635 on Feb 1, 2013 7:47 PM

  • RELEVANCY SCORE 3.13

    DB:3.13:Weblogic.Admin Thread_Dump Error m9


    I am getting this error when using weblogic.Admin THREAD_DUMP command , please help me to resolve this.

    java weblogic.Admin -url t3://localhost:7001 -username seblogic -password weblogic THREAD_DUMP
    Exception in thread "main" java.lang.NoClassDefFoundError: java/util/logging/Handler
    at weblogic.management.commandline.AdminMain.main(AdminMain.java:79)
    at weblogic.Admin.useAdminMain(Admin.java:169)
    at weblogic.Admin.main(Admin.java:54)

    DB:3.13:Weblogic.Admin Thread_Dump Error m9

    I am using HP UX operating system and the domain env is set, still getting the same error.

  • RELEVANCY SCORE 3.13

    DB:3.13:Using Node Manager... xx


    bI am using weblogic 8.1....I am using Node Manager...and its commands...I want that Node Manager command Execution from java Program... that working with exec command....like as follows..

    briFONT COLOR="#CC3366"Runtime r=Runtime.getRuntime();
    brProcess p=r.exec("java weblogic.Admin -url t3:/localhost:7001 -username arcturus -password arcturus START mynewserver3");/FONT/i
    brBut i want to run that as object as like below...

    br
    iFONT COLOR="#339933"new weblogic.Admin() -url t3:/localhost:7001 -username arcturus -password arcturus START mynewserver3;/FONT/i
    br
    But it giving compilation errors....

    Anyone can solve this problem..br
    Raju/b

    DB:3.13:Using Node Manager... xx

    bI am using weblogic 8.1....I am using Node Manager...and its commands...I want that Node Manager command Execution from java Program... that working with exec command....like as follows..

    briFONT COLOR="#CC3366"Runtime r=Runtime.getRuntime();
    brProcess p=r.exec("java weblogic.Admin -url t3:/localhost:7001 -username arcturus -password arcturus START mynewserver3");/FONT/i
    brBut i want to run that as object as like below...

    br
    iFONT COLOR="#339933"new weblogic.Admin() -url t3:/localhost:7001 -username arcturus -password arcturus START mynewserver3;/FONT/i
    br
    But it giving compilation errors....

    Anyone can solve this problem..br
    Raju/b

  • RELEVANCY SCORE 3.13

    DB:3.13:T3: Protocol zd


    What does the t3: protocol refer to?

    t3://someserver:7001";

    I know it's used to connect for an MBean, but should I be able to test
    it in a web browser?

    DB:3.13:T3: Protocol zd

    T3 Protocal can be used to invoke Application Server resource from a application running outside the application Server.

    For E.g. If you have a JNDI name registered on an Application server and you want to use it from a Plain Java file or a Java Project which is a stand alone and not a part of Application server then u can use T3 protocol.

    Regards
    vinaY
    vinaY

  • RELEVANCY SCORE 3.13

    DB:3.13:Problem In Importing To Mds Schema ck


    Hello,
    I am creating a pre process event handler in OIM 11gR2,in which there is one step "*importing custom event into MDS schema*" to do that:
    1)go to OIM_HOME/server/bin and edit the weblogic.props file as follows:
    wls_servername=oim_server1
    application_name=OIMMetadata
    metadata_from_loc=/home/oracle/eventhandlers
    Event Handler Config file location as /home/oracle/eventhandlers/metada/EventHandlers.xml
    2)weblogicImportmetada.bat file and it prompt
    Weblogic Admin User Name : weblogic
    Weblogic Admin Password : weblogic admin password
    weblogic Admin URL : t3://localhost:7001
    after connecting to the weblogic it shows the error message :

    Please enter your username :weblogic
    Please enter your password :
    *Please enter your server URL [t3://localhost:7001] :t3://localhost:7001*
    Connecting to t3://localhost:7001 with userid weblogic ...
    Successfully connected to Admin Server 'AdminServer' that belongs to domain 'base_domain'.

    Warning: An insecure protocol was used to connect to the
    server. To ensure on-the-wire security, the SSL port or
    Admin port should be used instead.

    Location changed to domainRuntime tree. This is a read-only tree with DomainMBean as the root.
    For more help, use help(domainRuntime)

    Problem invoking WLST - Traceback (innermost last):
    File "IDM_HOME\server\bin\weblogicImportMetadata.py", line 21, in ?
    File "C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\mdsWLSTCommands.py", line 289, in importMetadata
    File "C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\mdsWLSTCommands.py", line 795, in executeAppRuntimeMBeanOperation
    File "C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\mdsWLSTCommands.py", line 765, in getMDSAppRuntimeMBean
    UserWarning: MDS-91002: MDS Application runtime MBean for "oim" is not available. "importMetadata" operation failure.

    please advice how to resolve this error as i'm new in OIM

    thanks regards,
    Tushar Palekar

    DB:3.13:Problem In Importing To Mds Schema ck

    Try the suggestion given in the last post in the below forum link :

    Error while exporting metadata file /iam-features-ldap-sync/LDAPUser.xml

    HTH

  • RELEVANCY SCORE 3.13

    DB:3.13:Deployment Error T3://10.91.154.80:7001: Destination Unreachable zm


    Hi Experts,

    Jdev version: 11.1.1.4.0

    I am trying to deploy one service to server in Jdeveloper itself. I am using local server and for that i made server connection with host name as 'localhost'. Aslo I have tested server connetion, it was successfull.

    But when i am trying to deploy (In Jdev right click the service and deploy option)a BPEL server i am getting a below error,

    java.lang.RuntimeException: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://10.91.154.80:7001: Destination unreachable; nested exception is:
    java.net.ConnectException: Connection timed out: connect; No available router to destination]
    at oracle.tip.tools.ide.fabric.asbrowser.WeblogicSOAServer.initPartitions(WeblogicSOAServer.java:89)
    at oracle.tip.tools.ide.fabric.asbrowser.WeblogicSOAServer.init(WeblogicSOAServer.java:68)
    at oracle.tip.tools.ide.fabric.asbrowser.ASBrowserHelper.listWeblogicSOAServers(ASBrowserHelper.java:266)
    at oracle.tip.tools.ide.fabric.asbrowser.ASBrowserHelper.listSOAServers(ASBrowserHelper.java:199)
    at oracle.tip.tools.ide.fabric.asbrowser.ASBrowserHelper$RunnableListSOAServers.run(ASBrowserHelper.java:324)
    at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:655)
    at java.lang.Thread.run(Thread.java:619)
    Caused by: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://10.91.154.80:7001: Destination unreachable; nested exception is:
    java.net.ConnectException: Connection timed out: connect; No available router to destination]
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:788)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:368)
    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.init(InitialContext.java:197)
    at oracle.soa.management.internal.facade.ServerManagerImpl.init(ServerManagerImpl.java:76)
    at oracle.soa.management.internal.facade.ServerManagerFactoryImpl.createServerManager(ServerManagerFactoryImpl.java:28)
    at oracle.tip.tools.ide.fabric.asbrowser.WeblogicSOAServer.initPartitions(WeblogicSOAServer.java:85)
    ... 6 more
    Caused by: java.net.ConnectException: t3://10.91.154.80:7001: Destination unreachable; nested exception is:
    java.net.ConnectException: Connection timed out: 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.getInitialContext(WLInitialContextFactoryDelegate.java:353)
    ... 16 more
    Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
    java.net.ConnectException: Connection timed out: 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:254)
    at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
    at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)

    Any suggestion please??

    thanks,
    Santosh

    Edited by: Santosh M E on Jan 29, 2013 10:56 PM

    Edited by: Santosh M E on Jan 29, 2013 10:57 PM

    DB:3.13:Deployment Error T3://10.91.154.80:7001: Destination Unreachable zm

    Can you check if there are some unwanted settings in Tools - Preferences - Web Browsers and Proxies ?
    Also check by testing the server connection you would have created.

  • RELEVANCY SCORE 3.13

    DB:3.13:Problem When I Starting Weblogic Server Under Eclipse Suddenly Stop 99


    Hi everyone:

    I've a problem, I'm working with IDE Eclipse 3.2 and weblogic server 8.1 I need to debug the application, when I'm trying to start the server and everything look fine and almost at the end suddenly the server stop with this message:

    Stopping Weblogic Server...

    Failed to connect to t3://localhost:7001: Destination unreachable; nested exception is:
    java.net.ConnectException: Connection refused; No available router to destination

    please I need Help.

    Thanks in advance

    DB:3.13:Problem When I Starting Weblogic Server Under Eclipse Suddenly Stop 99

    i still haven't found a solution to the problem with the specific setup i originally mentioned (wls 9.0, eclipse 3.2 on solaris/sparc). even after upgrading to wls 9.2, the exact same bug occurs.

    in the end, i just gave up on the standalone eclipse 3.2 and started using workshop for weblogic 9.2 that comes bundled with the wls 9.2 installation; and the problem does not occur with that setup.

    wl workshop 9.2 is based on eclipse 3.1. so if you want to use regular eclipse with regular wls, then maybe eclipse 3.1 is the most stable version to use with wls. hth.

  • RELEVANCY SCORE 3.12

    DB:3.12:Problem With Stopweblogic.Sh 7f


    Hello,

    When I launch stopWebLogic.sh, I get an "java.net.ProtocolException: Tunneling result unspecified"

    The problem seems to be with the admin_url;
    I tried t3://localhost:7001 or http://localhost:80 or http://server:80

    Any Idea?

    DB:3.12:Problem With Stopweblogic.Sh 7f

    Hello,

    When I launch stopWebLogic.sh, I get an "java.net.ProtocolException: Tunneling result unspecified"

    The problem seems to be with the admin_url;
    I tried t3://localhost:7001 or http://localhost:80 or http://server:80

    Any Idea?

  • RELEVANCY SCORE 3.11

    DB:3.11:Help Communicating With Nodemanager Via Wlst Nmenroll() x3


    Need help: Trying to establish communication with Node Manager.

    # java weblogic.WLST

    Initializing WebLogic Scripting Tool (WLST) ...

    Welcome to WebLogic Server Administration Scripting Shell

    Type help() for help on available commands

    wls:/offline connect()
    Please enter your username [weblogic] :
    Please enter your password [welcome1] :
    Please enter your server URL [t3://localhost:7001] :t3://localhost:7001
    Connecting to t3://localhost:4001 with userid weblogic ...
    Successfully connected to Admin Server 'examplesServer' that belongs to domain 'wl_server'.

    Warning: An insecure protocol was used to connect to the
    server. To ensure on-the-wire security, the SSL port or
    Admin port should be used instead.

    wls:/wl_server/serverConfig nmEnroll('/export/home/weblogic/Oracle/Middleware/user_projects/domains/Solaris10.proxitec.com','/export/home/weblogic/Oracle/Middleware/wlserver_10.3/common/nodemanager')
    Enrolling this machine with the domain directory at /export/home/weblogic/Oracle/Middleware/user_projects/domains/Solaris10.proxitec.com ...
    Traceback (innermost last):
    File "console", line 1, in ?
    File "iostream", line 1447, in nmEnroll
    File "iostream", line 1848, in raiseWLSTException
    WLSTException: Error occured while performing nmEnroll : Problem occurred while encrypting a value : com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.
    Use dumpStack() to view the full stacktrace
    wls:/wl_server/serverConfig

    DB:3.11:Help Communicating With Nodemanager Via Wlst Nmenroll() x3

    Hi,

    The nmEnroll() which you are using is correct Syntax wise..But the problem looks like the encrypted Values present inside your "config.xml" So please try the below link regarding the : "om.rsa.jsafe.JSAFE_PaddingException" ..

    http://middlewaremagic.com/weblogic/?p=2982

    Looks like the NodeManager credentials mentioned in "config.xml" got corrupted... please edit with Manually as described in the above link. Or try to reset it through the AdminConsole.
    .
    .
    Thanks
    Jay SenSharma
    http://middlewaremagic.com/weblogic (Middleware Magic Is Here)

  • RELEVANCY SCORE 3.11

    DB:3.11:Startup Class Authentication Problem 37


    I have been unable to get authentication to work properly when I access a
    session bean from a startup class. However, it works fine when it's accessed
    from a regular client. The problem is that the when the startup class calls
    the session bean the getCallerPrincipal() method on the context always
    return "guest".

    I'm using the same code (below) in both the startup class and regular
    client. Is this a bug?

    Properties h = new Properties();
    h.put(Context.INITIAL_CONTEXT_FACTORY,
    "weblogic.jndi.WLInitialContextFactory");
    h.put(Context.PROVIDER_URL, t3://localhost:7001);
    h.put(Context.SECURITY_PRINCIPAL, "jim");
    h.put(Context.SECURITY_CREDENTIALS, "password");
    javax.naming.Context context = InitialContext(h);
    Object ref = context.lookup("SchedTransactionMgr");

    Thanks, Jim Corkey

    DB:3.11:Startup Class Authentication Problem 37

    I have been unable to get authentication to work properly when I access a
    session bean from a startup class. However, it works fine when it's accessed
    from a regular client. The problem is that the when the startup class calls
    the session bean the getCallerPrincipal() method on the context always
    return "guest".

    I'm using the same code (below) in both the startup class and regular
    client. Is this a bug?

    Properties h = new Properties();
    h.put(Context.INITIAL_CONTEXT_FACTORY,
    "weblogic.jndi.WLInitialContextFactory");
    h.put(Context.PROVIDER_URL, t3://localhost:7001);
    h.put(Context.SECURITY_PRINCIPAL, "jim");
    h.put(Context.SECURITY_CREDENTIALS, "password");
    javax.naming.Context context = InitialContext(h);
    Object ref = context.lookup("SchedTransactionMgr");

    Thanks, Jim Corkey

  • RELEVANCY SCORE 3.11

    DB:3.11:Can't Start The Web Server,Java Processes Die After Few Minute,Any Thoughs. 7k


    Error in the PIA_stderr.log file
    ***************************************************************************

    The WebLogic Server did not start up properly.
    Exception raised: 'weblogic.management.DeploymentException: [Deployer:149204]The deployment framework was unable to register with the Data Replication Service.
    RegisterException due to underlying exception java.rmi.RemoteException: Failed to get message receiver on t3://localhost:7001; nested exception is:
    java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
    java.net.ConnectException: Connection timed out; No available router to destination
    at weblogic.drs.internal.DataReplicationService.registerSlave(DataReplicationService.java:285)
    at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:377)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
    at weblogic.Server.main(Server.java:32)
    '
    Reason: [Deployer:149601]The deployment framework was unable to resume accepting requests.[Deployer:149204]The deployment framework was unable to register with the Data Replication Service.
    RegisterException due to underlying exception java.rmi.RemoteException: Failed to get message receiver on t3://localhost:7001; nested exception is:
    java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
    java.net.ConnectException: Connection timed out; No available router to destination
    at weblogic.drs.internal.DataReplicationService.registerSlave(DataReplicationService.java:285)
    at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:377)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
    at weblogic.Server.main(Server.java:32)

    ***************************************************************************

    Error messages in the PIA_stdout.log file

    Oct 14, 2008 3:07:42 PM EDT Notice WebLogicServer BEA-000356 Starting WebLogic Independent Managed Server "PIA" for domain "STAGE"
    Oct 14, 2008 3:09:10 PM EDT Warning DRS BEA-002527 The get deltas from version 0 to version timed out.
    Oct 14, 2008 3:13:16 PM EDT Error Deployer BEA-149204 The deployment framework was unable to register with the Data Replication Service.
    RegisterException due to underlying exception java.rmi.RemoteException: Failed to get message receiver on t3://localhost:7001; nested exception is:
    java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
    java.net.ConnectException: Connection timed out; No available router to destination
    at weblogic.drs.internal.DataReplicationService.registerSlave(DataReplicationService.java:285)
    at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:377)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
    at weblogic.Server.main(Server.java:32)

    Oct 14, 2008 3:13:16 PM EDT Error Deployer BEA-149601 The deployment framework was unable to resume accepting requests.
    Oct 14, 2008 3:13:16 PM EDT Emergency WebLogicServer BEA-000342 Unable to initialize the server: [Deployer:149601]The deployment framework was unable to resume accepting requests.[Deployer:149204]The deployment framework was unable to register with the Data Replication Service.
    RegisterException due to underlying exception java.rmi.RemoteException: Failed to get message receiver on t3://localhost:7001; nested exception is:
    java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
    java.net.ConnectException: Connection timed out; No available router to destination
    at weblogic.drs.internal.DataReplicationService.registerSlave(DataReplicationService.java:285)
    at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:377)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
    at weblogic.Server.main(Server.java:32)

    ***********************
    The status of PIA server is running in the running-managed-servers.xml file
    *********************
    /listen-port
    is-listen-port-secure
    false
    /is-listen-port-secure
    server-name
    PIA
    /server-name
    state
    running
    /state
    /managed-server
    /running-managed-servers

    DB:3.11:Can't Start The Web Server,Java Processes Die After Few Minute,Any Thoughs. 7k

    Hi,

    Dumb question : is one of your server listening on port 7001 ? If not, should it ?
    What is the expected behavior ? A managed trying to connect to the admin server ?
    Check the value for ADMIN_URL value, set in the startManagedServer.sh or cmd.

    Another dumb question : do you have a firewall ?

  • RELEVANCY SCORE 3.10

    DB:3.10:Jndi &Amp; Proxy df



    Hi all,

    I have this client application that needs to do a JNDI lookup via a proxy and
    a corporate firewall to a Weblogic server that is outside.

    How do i do a lookup ??
    I tried this- still get error "cannot connect to server at
    t3://192.74.56.123:7001", any ideas ??

    Thanks Jim

    public abstract class BaseClient {

    private Context ctx;

    private String url = "t3://192.74.56.123:7001";

    protected Object narrow(Object o, Class c) {
    return PortableRemoteObject.narrow(o, c);
    }

    protected Context getInitialContext()
    throws NamingException
    {
    if (ctx == null) {

    try {

    Properties props = System.getProperties();
    props.put("proxyHost", "http-proxy.myproxyserver.com");
    props.put("proxyPort", "80");
    props.put("proxySet", "true");
    System.setProperties(props);

    Properties p = new Properties();
    p.put(Context.INITIAL_CONTEXT_FACTORY,
    "weblogic.jndi.WLInitialContextFactory");
    p.put(Context.PROVIDER_URL, url);
    ctx = new InitialContext(p);

    } catch (NamingException ne) {
    System.err.println("** Unable to connect to the server at:"
    +url);
    ne.printStackTrace();
    throw ne;
    }

    }

    return ctx;
    }

    DB:3.10:Jndi &Amp; Proxy df


    Hi all,

    I have this client application that needs to do a JNDI lookup via a proxy and
    a corporate firewall to a Weblogic server that is outside.

    How do i do a lookup ??
    I tried this- still get error "cannot connect to server at
    t3://192.74.56.123:7001", any ideas ??

    Thanks Jim

    public abstract class BaseClient {

    private Context ctx;

    private String url = "t3://192.74.56.123:7001";

    protected Object narrow(Object o, Class c) {
    return PortableRemoteObject.narrow(o, c);
    }

    protected Context getInitialContext()
    throws NamingException
    {
    if (ctx == null) {

    try {

    Properties props = System.getProperties();
    props.put("proxyHost", "http-proxy.myproxyserver.com");
    props.put("proxyPort", "80");
    props.put("proxySet", "true");
    System.setProperties(props);

    Properties p = new Properties();
    p.put(Context.INITIAL_CONTEXT_FACTORY,
    "weblogic.jndi.WLInitialContextFactory");
    p.put(Context.PROVIDER_URL, url);
    ctx = new InitialContext(p);

    } catch (NamingException ne) {
    System.err.println("** Unable to connect to the server at:"
    +url);
    ne.printStackTrace();
    throw ne;
    }

    }

    return ctx;
    }

  • RELEVANCY SCORE 3.10

    DB:3.10:While Installing Bo 13.3 Authentication Error sj


    Hi All,

    Am trying to install ORBO 13.3 on Weblogic

    Installation is failing due to following error and it overrides the Weblogic log in user id and password

    deploy.app:
    [java]
    [java] Initializing WebLogic Scripting Tool (WLST) ...
    [java]
    [java] Welcome to WebLogic Server Administration Scripting Shell
    [java]
    [java] Type help() for help on available commands
    [java]
    [java] Connecting to t3://localhost:7001 with userid pos ...
    [java] Successfully connected to Admin Server 'AdminServer' that belongs to domain 'bo_domain'.
    [java]
    [java] Warning: An insecure protocol was used to connect to the
    [java] server. To ensure on-the-wire security, the SSL port or
    [java] Admin port should be used instead.
    [java]
    [java] extension is ear use timeout of 1800000
    [java] javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException: [J2EE Deployment SPI:260010]Unable to connect to 't3://localhost:7001' as user, 'pos'. Error received: User: pos, failed to be authenticated.
    [java] at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.init(WebLogicDeploymentManagerImpl.java:121)
    [java] at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:86)
    [java] at weblogic.deploy.api.tools.SessionHelper.getDeploymentManager(SessionHelper.java:446)
    [java] at weblogic.management.scripting.JSR88DeployHandler.init(JSR88DeployHandler.java:110)
    [java] at weblogic.management.scripting.JSR88DeployHandler.getWLDM(JSR88DeployHandler.java:73)
    [java] at weblogic.management.scripting.JSR88DeployHandler.deploy(JSR88DeployHandler.java:480)
    [java] at weblogic.management.scripting.WLScriptContext.deploy(WLScriptContext.java:430)
    [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [java] at java.lang.reflect.Method.invoke(Method.java:597)
    [java] at org.python.core.PyReflectedFunction.__call__(Unknown Source)
    [java] at org.python.core.PyMethod.__call__(Unknown Source)
    [java] at org.python.core.PyObject.__call__(Unknown Source)
    [java] at org.python.core.PyObject.invoke(Unknown Source)
    [java] at org.python.pycode._pyx16.deploy$8(iostream:235)
    [java] at org.python.pycode._pyx16.call_function(iostream)
    [java] at org.python.core.PyTableCode.call(Unknown Source)
    [java] at org.python.core.PyTableCode.call(Unknown Source)
    [java] at org.python.core.PyFunction.__call__(Unknown Source)
    [java] at org.python.pycode._pyx15.f$0(C:\ORBO-13.3\backoffice\appservers\weblogic\deploy.py:31)
    [java] at org.python.pycode._pyx15.call_function(C:\ORBO-13.3\backoffice\appservers\weblogic\deploy.py)
    [java] at org.python.core.PyTableCode.call(Unknown Source)
    [java] at org.python.core.PyCode.call(Unknown Source)
    [java] at org.python.core.Py.runCode(Unknown Source)
    [java] at org.python.util.PythonInterpreter.execfile(Unknown Source)
    [java] at weblogic.management.scripting.WLST.main(WLST.java:131)
    [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [java] at java.lang.reflect.Method.invoke(Method.java:597)
    [java] at weblogic.WLST.main(WLST.java:29)
    [java] Caused by: weblogic.deploy.api.spi.exceptions.ServerConnectionException: [J2EE Deployment SPI:260010]Unable to connect to 't3://localhost:7001' as user, 'pos'. Error received: User: pos, failed to be authenticated.
    [java] at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getMBeanServer(ServerConnectionImpl.java:249)
    [java] at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getMBeanServerForType(ServerConnectionImpl.java:189)
    [java] at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:145)
    [java] at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.getNewConnection(WebLogicDeploymentManagerImpl.java:148)
    [java] at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.init(WebLogicDeploymentManagerImpl.java:118)
    [java] ... 31 more
    [java] Caused by: java.lang.SecurityException: User: pos, failed to be authenticated.
    [java] at weblogic.common.internal.RMIBootServiceImpl.authenticate(RMIBootServiceImpl.java:119)
    [java] at weblogic.common.internal.RMIBootServiceImpl_WLSkel.invoke(Unknown Source)
    [java] at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
    [java] This Exception occurred at Fri Jul 08 12:14:12 GMT+05:30 2011.
    [java] at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
    [java] at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    [java] at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    [java] at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
    [java] at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
    [java] at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    [java] at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    [java] javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException: [J2EE Deployment SPI:260010]Unable to connect to 't3://localhost:7001' as user, 'pos'. Error received: User: pos, failed to be authenticated.
    [java] at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.init(WebLogicDeploymentManagerImpl.java:121)
    [java] at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:86)
    [java] at weblogic.deploy.api.tools.SessionHelper.getDeploymentManager(SessionHelper.java:446)
    [java] at weblogic.management.scripting.JSR88DeployHandler.init(JSR88DeployHandler.java:110)
    [java] at weblogic.management.scripting.JSR88DeployHandler.getWLDM(JSR88DeployHandler.java:73)
    [java] at weblogic.management.scripting.JSR88DeployHandler.deploy(JSR88DeployHandler.java:480)
    [java] at weblogic.management.scripting.WLScriptContext.deploy(WLScriptContext.java:430)
    [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [java] at java.lang.reflect.Method.invoke(Method.java:597)
    [java] at org.python.core.PyReflectedFunction.__call__(Unknown Source)
    [java] at org.python.core.PyMethod.__call__(Unknown Source)
    [java] at org.python.core.PyObject.__call__(Unknown Source)
    [java] at org.python.core.PyObject.invoke(Unknown Source)
    [java] at org.python.pycode._pyx16.deploy$8(iostream:235)
    [java] at org.python.pycode._pyx16.call_function(iostream)
    [java] at org.python.core.PyTableCode.call(Unknown Source)
    [java] at org.python.core.PyTableCode.call(Unknown Source)
    [java] at org.python.core.PyFunction.__call__(Unknown Source)
    [java] at org.python.pycode._pyx15.f$0(C:\ORBO-13.3\backoffice\appservers\weblogic\deploy.py:31)
    [java] at org.python.pycode._pyx15.call_function(C:\ORBO-13.3\backoffice\appservers\weblogic\deploy.py)
    [java] at org.python.core.PyTableCode.call(Unknown Source)
    [java] at org.python.core.PyCode.call(Unknown Source)
    [java] at org.python.core.Py.runCode(Unknown Source)
    [java] at org.python.util.PythonInterpreter.execfile(Unknown Source)
    [java] at weblogic.management.scripting.WLST.main(WLST.java:131)
    [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [java] at java.lang.reflect.Method.invoke(Method.java:597)
    [java] at weblogic.WLST.main(WLST.java:29)
    [java] Caused by: weblogic.deploy.api.spi.exceptions.ServerConnectionException: [J2EE Deployment SPI:260010]Unable to connect to 't3://localhost:7001' as user, 'pos'. Error received: User: pos, failed to be authenticated.
    [java] at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getMBeanServer(ServerConnectionImpl.java:249)
    [java] at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getMBeanServerForType(ServerConnectionImpl.java:189)
    [java] at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:145)
    [java] at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.getNewConnection(WebLogicDeploymentManagerImpl.java:148)
    [java] at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.init(WebLogicDeploymentManagerImpl.java:118)
    [java] ... 31 more
    [java] Caused by: java.lang.SecurityException: User: pos, failed to be authenticated.
    [java] at weblogic.common.internal.RMIBootServiceImpl.authenticate(RMIBootServiceImpl.java:119)
    [java] at weblogic.common.internal.RMIBootServiceImpl_WLSkel.invoke(Unknown Source)
    [java] at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
    [java] This Exception occurred at Fri Jul 08 12:14:12 GMT+05:30 2011.
    [java] at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
    [java] at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    [java] at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    [java] at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
    [java] at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
    [java] at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    [java] at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    [java] weblogic.management.scripting.ScriptException: Error occured while performing deploy : Could not create the Deployment Manager. : [J2EE Deployment SPI:260010]Unable to connect to 't3://localhost:7001' as user, 'pos'. Error received: User: pos, failed to be authenticated.
    [java] Use dumpStack() to view the full stacktrace
    [java] at weblogic.management.scripting.ExceptionHandler.handleException(ExceptionHandler.java:50)
    [java] at weblogic.management.scripting.WLSTUtils.throwWLSTException(WLSTUtils.java:181)
    [java] at weblogic.management.scripting.JSR88DeployHandler.init(JSR88DeployHandler.java:125)
    [java] at weblogic.management.scripting.JSR88DeployHandler.getWLDM(JSR88DeployHandler.java:73)
    [java] at weblogic.management.scripting.JSR88DeployHandler.deploy(JSR88DeployHandler.java:480)
    [java] at weblogic.management.scripting.WLScriptContext.deploy(WLScriptContext.java:430)
    [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [java] at java.lang.reflect.Method.invoke(Method.java:597)
    [java] at org.python.core.PyReflectedFunction.__call__(Unknown Source)
    [java] at org.python.core.PyMethod.__call__(Unknown Source)
    [java] at org.python.core.PyObject.__call__(Unknown Source)
    [java] at org.python.core.PyObject.invoke(Unknown Source)
    [java] at org.python.pycode._pyx16.deploy$8(iostream:235)
    [java] at org.python.pycode._pyx16.call_function(iostream)
    [java] at org.python.core.PyTableCode.call(Unknown Source)
    [java] at org.python.core.PyTableCode.call(Unknown Source)
    [java] at org.python.core.PyFunction.__call__(Unknown Source)
    [java] at org.python.pycode._pyx15.f$0(C:\ORBO-13.3\backoffice\appservers\weblogic\deploy.py:31)
    [java] at org.python.pycode._pyx15.call_function(C:\ORBO-13.3\backoffice\appservers\weblogic\deploy.py)
    [java] at org.python.core.PyTableCode.call(Unknown Source)
    [java] at org.python.core.PyCode.call(Unknown Source)
    [java] at org.python.core.Py.runCode(Unknown Source)
    [java] at org.python.util.PythonInterpreter.execfile(Unknown Source)
    [java] at weblogic.management.scripting.WLST.main(WLST.java:131)
    [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [java] at java.lang.reflect.Method.invoke(Method.java:597)
    [java] at weblogic.WLST.main(WLST.java:29)
    [java] Caused by: javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException: [J2EE Deployment SPI:260010]Unable to connect to 't3://localhost:7001' as user, 'pos'. Error received: User: pos, failed to be authenticated.
    [java] at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.init(WebLogicDeploymentManagerImpl.java:121)
    [java] at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:86)
    [java] at weblogic.deploy.api.tools.SessionHelper.getDeploymentManager(SessionHelper.java:446)
    [java] at weblogic.management.scripting.JSR88DeployHandler.init(JSR88DeployHandler.java:110)
    [java] ... 28 more
    [java] Caused by: weblogic.deploy.api.spi.exceptions.ServerConnectionException: [J2EE Deployment SPI:260010]Unable to connect to 't3://localhost:7001' as user, 'pos'. Error received: User: pos, failed to be authenticated.
    [java] at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getMBeanServer(ServerConnectionImpl.java:249)
    [java] at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getMBeanServerForType(ServerConnectionImpl.java:189)
    [java] at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:145)
    [java] at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.getNewConnection(WebLogicDeploymentManagerImpl.java:148)
    [java] at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.init(WebLogicDeploymentManagerImpl.java:118)
    [java] ... 31 more
    [java] Caused by: java.lang.SecurityException: User: pos, failed to be authenticated.
    [java] at weblogic.common.internal.RMIBootServiceImpl.authenticate(RMIBootServiceImpl.java:119)
    [java] at weblogic.common.internal.RMIBootServiceImpl_WLSkel.invoke(Unknown Source)
    [java] at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
    [java] at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
    [java] at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    [java] at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    [java] at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
    [java] at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
    [java] at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    [java] at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    [java] Problem invoking WLST - Traceback (innermost last):
    [java] File "C:\ORBO-13.3\backoffice\appservers\weblogic\deploy.py", line 31, in ?
    [java] File "iostream", line 246, in deploy
    [java] File "iostream", line 1848, in raiseWLSTException
    [java] WLSTException: Error occured while performing deploy : Target exception thrown while deploying application: Error occured while performing deploy : Could not create the Deployment Manager. : [J2EE Deployment SPI:260010]Unable to connect to 't3://localhost:7001' as user, 'pos'. Error received: User: pos, failed to be authenticated.
    [java] Use dumpStack() to view the full stacktrace : Error occured while performing deploy : Could not create the Deployment Manager. : [J2EE Deployment SPI:260010]Unable to connect to 't3://localhost:7001' as user, 'pos'. Error received: User: pos, failed to be authenticated.
    [java] Use dumpStack() to view the full stacktrace
    [java] Use dumpStack() to view the full stacktrace
    [java]

    BUILD FAILED

    C:\ORBO-13.3\build.xml:1095: The following error occurred while executing this line:
    C:\ORBO-13.3\build.xml:1116: The following error occurred while executing this line:
    C:\ORBO-13.3\backoffice\appservers\weblogic\build-common-wl.xml:660: Java returned: 1
    at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:539)
    at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:384)
    at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:107)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
    at org.apache.tools.ant.Task.perform(Task.java:364)
    at org.apache.tools.ant.Target.execute(Target.java:341)
    at org.apache.tools.ant.Target.performTasks(Target.java:369)
    at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
    at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
    at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
    at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
    at org.tp23.antinstaller.antmod.Main.runBuild(Main.java:704)
    at org.tp23.antinstaller.antmod.Main.startAnt(Main.java:216)
    at org.tp23.antinstaller.antmod.Launcher.run(Launcher.java:215)
    at org.tp23.antinstaller.runtime.exe.AntLauncherFilter.exec(AntLauncherFilter.java:76)
    at org.tp23.antinstaller.runtime.ExecInstall.exec(ExecInstall.java:85)
    at org.tp23.antinstaller.runtime.ExecInstall.main(ExecInstall.java:157)
    Caused by: C:\ORBO-13.3\build.xml:1116: The following error occurred while executing this line:
    C:\ORBO-13.3\backoffice\appservers\weblogic\build-common-wl.xml:660: Java returned: 1
    at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:539)
    at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:384)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
    at org.apache.tools.ant.Task.perform(Task.java:364)
    at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:64)
    at net.sf.antcontrib.logic.IfTask.execute(IfTask.java:197)
    at sun.reflect.GeneratedMethodAccessor40.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.apache.tools.ant.TaskAdapter.execute(TaskAdapter.java:123)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
    at org.apache.tools.ant.Task.perform(Task.java:364)
    at org.apache.tools.ant.Target.execute(Target.java:341)
    at org.apache.tools.ant.Target.performTasks(Target.java:369)
    at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
    at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:37)
    at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
    at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
    ... 15 more
    Caused by: C:\ORBO-13.3\backoffice\appservers\weblogic\build-common-wl.xml:660: Java returned: 1
    at org.apache.tools.ant.taskdefs.Java.execute(Java.java:87)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
    at org.apache.tools.ant.Task.perform(Task.java:364)
    at org.apache.tools.ant.Target.execute(Target.java:341)
    at org.apache.tools.ant.Target.performTasks(Target.java:369)
    at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
    at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:37)
    at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
    at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)

    Appreciate your help in resolving this issue\

    Regards
    KR

    Edited by: user9070294 on Jul 18, 2011 6:24 AM

    DB:3.10:While Installing Bo 13.3 Authentication Error sj

    Hi KR

    Few things are in my mind.

    As weblogic runs on port 7001 so first you cant configure BO/CO application on same port.Also weblogic runs on non ssl port but the BO and CO application runs on secure http protocol. So choose port 7002 and make it secure via using weblogic console.

    In the above mention ant.install.properties i am not able to see pasword to access backoffice application.Default user pos is there but no pasword given to the pos user.

    I have configured CO application on Weblogic but its not via using installer. I had deploy manually and few issues looks like same regarding port number.

    Thanks
    Kapil

  • RELEVANCY SCORE 3.09

    DB:3.09:Dspcontrolconfig.Properties 78


    We're using ODSI 10.3.0 and utilizing the dspControlConfig.properties file to override the endpoints for the data service controls. We've noticed that occasionally this file gets updated by the server at runtime. It adds these lines to the file even though the control is already specified in the property file:

    #The URL for the ODSI Control InternetDataspace.org.internet.security.dscontrol.InternetSecurityDSControl
    #Mon Feb 07 10:00:43 CST 2011
    InternetDataspace.org.internet.form.controls.InternetFormDSControl=t3\://....

    Why does it do that and how can we prevent it?

    Even though the control already exists in the file, the server sometimes updates the file with the control using localhost:7001 address at the end of the file. ie InternetDataspace.org.internet.security.dscontrol.InternetSecurityDSControl=t3\://localhost\:7001
    We need to prevent this b/c it's overriding the correct control reference with localhost:7001 which causes the call to the odsi service to fail.

    DB:3.09:Dspcontrolconfig.Properties 78

    you already have a case open. customer support is going to ask you for more information.

  • RELEVANCY SCORE 3.09

    DB:3.09:Messaging Bridge Status Using Wlst d1


    Hi,I am trying to build a WLST script which tells the state of n number of messaging bridges that I have on AdminServer. connect('uname','pswd','t3://localhost:7001');serverRuntime();bd= cmo.getMessagingBridgeRuntime();print bd.getName()print bd.getState();I am having issues in finding the mbean instance, error is as followsAttributeError: getMessagingBridgeRuntimewould be of great help if you already have this script which is working or help me in solving this.I am using weblogic 10.3.1

    DB:3.09:Messaging Bridge Status Using Wlst d1

    It can be done using weblogic.Admin utility, below is the script...you can modify this according to requirement...java weblogic.Admin -url t3://$admURL -username weblogic -password $admpasswd GET -pretty -type MessagingBridgeRuntime -mbean $domain:ServerRuntime=$mserver,Name=$bridge,Type=MessagingBridgeRuntime,Location=$mserver -property Description -property Name -property State | grep -v MBeanName

  • RELEVANCY SCORE 3.08

    DB:3.08:Stop Weblogic Server From The Wlst jd


    I am getting the error when I try to stop WebLogic server using WLST. The error happens when script tries to connect to the running server:
    wls:/offline connect('weblogic', 'weblogic123', 't3://topics:7001')
    Connecting to t3://localhost:7001 with userid weblogic ...
    Traceback (innermost last):
    File "console", line 1, in ?
    File "iostream", line 22, in connect
    File "iostream", line 648, in raiseWLSTException
    WLSTException: Error occured while performing connect : User: weblogic, failed to be authenticated.
    Use dumpStack() to view the full stacktrace
    wls:/offline dumpStack()
    This Exception occurred at Wed Dec 26 07:48:38 EST 2012.
    javax.naming.AuthenticationException [Root exception is java.lang.SecurityException: User: weblogic, failed to be authenticated.]
    javax.naming.AuthenticationException [Root exception is java.lang.SecurityException: User: weblogic, failed to be authenticated.]

    The username/password are correct. I am running java 1.7.

    DB:3.08:Stop Weblogic Server From The Wlst jd

    Application problem: application overrides LDAP credentials which were specified when weblogic server was created.

  • RELEVANCY SCORE 3.08

    DB:3.08:Samplecode For Mqnwls -- Unresolved:'Wlsmqxaqcf' am


    Hi,
    I try the Using MQSeries as a Transactional Resource Manager with Weblogic
    Server V. 1.0.

    When I excute the sample code: java MQClient t3://localhost:7001 "hihi"
    occurs some error-message.

    Have anybody know.... how to fix....

    Thanks in advance.

    --
    Best Regards,
    Arch.

    ** [My Client Side Error Message]

    java MQClient t3://localhost:7001 "hihi"
    sending: "hihi"
    Exception in thread "main" javax.naming.NameNotFoundException: Unable to
    resolve
    'wlsmqXAQCF' Resolved: '' Unresolved:'wlsmqXAQCF' ; remaining name
    'wlsmqXAQCF'

    no stack trace available

    --------------- nested within: ------------------
    weblogic.rmi.RemoteException: javax.naming.NameNotFoundException: Unable to
    reso
    lve 'wlsmqXAQCF' Resolved: '' Unresolved:'wlsmqXAQCF' ; remaining name
    'wlsmqXAQ
    CF'

    Start server side stack trace:
    javax.naming.NameNotFoundException: Unable to resolve 'wlsmqXAQCF' Resolved:
    ''
    Unresolved:'wlsmqXAQCF' ; remaining name 'wlsmqXAQCF'
    no stack trace available

    **[My Server-Side Error Message]

    Notice WebLogicServer Started WebLogic Admin
    erver "myserver" for domain "mydomain" running in Production Mode
    javax.naming.NameNotFoundException: Unable to resolve 'wlsmqXAQCF' Resolved:
    ''
    Unresolved:'wlsmqXAQCF' ; remaining name 'wlsmqXAQCF'
    no stack trace available

    DB:3.08:Samplecode For Mqnwls -- Unresolved:'Wlsmqxaqcf' am

    I'm not clear on what exactly you have done, but the MQSeries helper uses
    XA, and it is trying to cast your MQ and WLS connection factories to the
    XAQueueConnectionFactory class.

    Make sure that you are using connection factories for MQ and WLS that
    support XA, and make sure the helper uses those factories. To create a
    connection factory for WLS that supports XA, you must set the
    "XAConnectionFactoryEnabled" and "UserTransactionsEnabled" flags. To create
    one for MQ, you have to use the MQSeries "jmsadmin" tool to create an
    "XAQCF" object, rather than a "QCF".

    greg

    "A.H" arch@cm1.hinet.net wrote in message
    news:3d6db7ec@newsgroups.bea.com...
    Hi,
    I retry the sample code in WLS 7.0 MQ 5.2..
    But it still error messages...

    [ServerSide Error Message]
    Notice WebLogicServer 000360 Server started
    in RUNNING mode
    java.lang.ClassCastException: weblogic.jms.client.JMSConnectionFactory
    java.lang.ClassCastException: weblogic.jms.client.JMSConnectionFactory
    at
    MQSeriesHelperImpl$JMSObject.init(MQSeriesHelperImpl.java:226)
    at MQSeriesHelperImpl.sendWLSMessage(MQSeriesHelperImpl.java:82)
    at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
    at
    weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:359)
    at
    weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
    at
    weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
    eManager.java:762)
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
    a:308)
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
    .java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)

    [Client Side Error Message....]
    c:\examplejava MQClient t3://localhost:7001 "hihi"
    sending: "hihi"
    Exception in thread "main" java.lang.NullPointerException:
    Start server side stack trace:
    java.lang.NullPointerException
    at MQSeriesHelperImpl.sendWLSMessage(MQSeriesHelperImpl.java:102)
    at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
    at
    weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:359)
    at
    weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
    at
    weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
    eManager.java:762)
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
    a:308)
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
    .java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
    End server side stack trace

    at
    weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundR
    equest.java:109)
    at
    weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:127)
    at MQSeriesHelperImpl_WLStub.sendWLSMessage(Unknown Source)
    at MQClient.main(MQClient.java:51)

  • RELEVANCY SCORE 3.08

    DB:3.08:Weblogic.Deploy 3m



    Im using wls6.1 and java version "1.4.0". When im using this command:
    java weblogic.deploy list password

    the result is:
    JNDI naming exception: Naming exception trying to connect to: t3://localhost:7001
    as: system: password

    With java version "1.3.1" the command works correct. Is weblogic.jar not compatible
    with java 1.4??

    thanks

    DB:3.08:Weblogic.Deploy 3m


    Java14 includes javax.naming classes in the rt.jar. Java13 does not, so in 6.1
    which was built and certified agains 13 includes them in the weblogic.jar.

    http://e-docs.bea.com/wls/certifications/certifications/win2000.html#39967

    6.1 is only certified currently for 13, not for 14.

    cheers
    mbg

    "ro" robert.wunderl@cet.at wrote:

    Im using wls6.1 and java version "1.4.0". When im using this command:
    java weblogic.deploy list password

    the result is:
    JNDI naming exception: Naming exception trying to connect to: t3://localhost:7001
    as: system: password

    With java version "1.3.1" the command works correct. Is weblogic.jar
    not compatible
    with java 1.4??

    thanks

  • RELEVANCY SCORE 3.08

    DB:3.08:Setting Up The Initial Context sa


    Hi,

    When I try to do the following in weblogic 6.1
    ht.put(Context.INITIAL_CONTEXT_FACTORY,
    "weblogic.jndi.WLInitialContextFactory");
    ht.put(Context.PROVIDER_URL, "t3://localhost:7001");
    Context ctx = new InitialContext(ht);

    I am getting the exception "javax.naming.CommunicationException. Root
    exception is java.net.ConnectException: No server found at
    T3://localhost:7001".

    Then I read the T3 protocol is not supported by default, and hence I
    changed to iiop, I mean " ht.put(Context.PROVIDER_URL,
    "iiop://localhost:7001");"
    Now the exception thrown is: "java.lang.ClassCastException:
    com.sun.CORBA.idl.CORBAObjectImpl"

    I am not sure of the protocol for the correct use of RMI with JNDI.
    Please help.

    thanks a lot in advance,
    Prabin

    DB:3.08:Setting Up The Initial Context sa

    Prabin Gade gade@aztec.soft.net writes:

    Hi,

    When I try to do the following in weblogic 6.1
    ht.put(Context.INITIAL_CONTEXT_FACTORY,
    "weblogic.jndi.WLInitialContextFactory");
    ht.put(Context.PROVIDER_URL, "t3://localhost:7001");
    Context ctx = new InitialContext(ht);

    I am getting the exception "javax.naming.CommunicationException. Root
    exception is java.net.ConnectException: No server found at
    T3://localhost:7001".I can only assume that what it is telling you is correct, i.e. there
    is no server listening at locahost:7001. Note that if you are on W2K
    it can play funny games with IP addresses, try using the explicit IP
    address or hostname of your machine.

    Then I read the T3 protocol is not supported by default, and hence IEr, this is not correct. You may be referring to T3 services being deprecated which is different to t3 (which is supported by default).

    andy
    --

  • RELEVANCY SCORE 3.08

    DB:3.08:Two Instances On One Server; Call Routing 9d



    Hi out there,

    in a test installation we have set up two instances of WLS 6.1. One instance (web
    tier) listens on hostname.domain.net:7001 for web-requests and the servlet makes
    calls to the business tier at t3://hostname.domain.net:2600 where the second instance
    (business tier) runs.
    Note that the hostname is identical since we have not set up multiple IP-addresses
    on this machine.

    PROBLEM:
    The business tier does not receive calls, because the web-tier obviously has problems
    to connect to t3://hostname.domain.net:2600.
    I tried t3://localhost:2600 allready, since this is an obvious workaround (allthough
    not preferred). Does not work either.

    Any ideas on what to look after?
    I would prefer solutions that do NOT require reconfiguration of the local machine
    to use several IP-addresses.

    Thanks for suggestions.

    Carsten

    DB:3.08:Two Instances On One Server; Call Routing 9d


    Hi there,

    this error was caused by a configuration error where I find interesting, that
    WLS does not complain about an EJB deployment error unless I turn off the console.

    Cheers

    Carsten

  • RELEVANCY SCORE 3.07

    DB:3.07:How Do I Make Wls 9.2 Stop Shutting Itself Down Within Eclipse 3.2.2? p3


    after starting weblogic server 9.2 mp1 from within eclipse
    sdk 3.2.2 build M20070212-1330 for solaris gtk, something
    programatically requests weblogic server 9.2 to shut
    itself down only seconds after the server has started.

    steps to reproduce:

    1. download install [url http://download.eclipse.org/eclipse/downloads/drops/R-3.2.2-200702121330/]eclipse sdk 3.2.2 build M20070212-1330 for solaris
    (eclipse-SDK-3.2.2-solaris-gtk.zip)

    2. update eclipse sdk with the [url http://download.eclipse.org/webtools/downloads/drops/R1.5/R-1.5.3-200702082048/]Web Tools Platform (WTP)
    1.5.3 plus all of the WTP 1.5.3 pre-reqs

    3. download install [url http://commerce.bea.com/showallversions.jsp?family=WLS]bea weblogic server 9.2 mp1 binary
    package installer for solaris 9 sparc

    4. confirm that bea weblogic server's sample domain can
    be started from the solaris 9's shell

    $ $BEA_HOME/weblogic92/samples/domains/workshop/startWebLogic.sh

    5. create a j2ee enterprise application by following the
    instructions in [url http://www.eclipse.org/webtools/community/tutorials/BuildJ2EEWebApp/BuildJ2EEWebApp.html]this WTP tutorial

    a. in the "Choose a Server Runtime Environment" step,
    choose BEA WebLogic 9.2 server instead of Tomcat.

    6. start the generic bea weblogic server v9.2.1 from the
    servers view as instructed in the tutorial.

    the eclipse status bar in the bottom right hand corner of
    eclipse indicates that weblogic server 9.2 is starting.
    eclipse then switches focus from the servers view to the
    console view. the console view lists the typical weblogic
    server startup console entries:
    ...
    ...Server state changed to STANDBY
    ...Server state changed to STARTING
    ...No test table set up for pool "cgDataSource". Connections will not be
    tested.
    ...No test table set up for pool "cgDataSource-nonXA". Connections will not be
    tested.
    ...No test table set up for pool "samplesDataSource". Connections will not be
    tested.
    ...[see 13_05_07_eclipse_wls_startup.txt in [url https://bugs.eclipse.org/bugs/attachment.cgi?id=66989]comment #1 attachment of [url https://bugs.eclipse.org/bugs/show_bug.cgi?id=186716]eclipse bug #186716 for full
    console output]

    eventually - but only for a few seconds - the servers view indicates the state
    of the weblogic server as "Started". the following log entries snipped from
    weblogic server 9.2's filesystem logs confirm that the wls did actually start
    at some point:
    ...
    ...Server state changed to RUNNING
    ...Server started in RUNNING mode
    ...78% of the total memory in the server is free
    ...[see cgServer.log in [url https://bugs.eclipse.org/bugs/attachment.cgi?id=66989]comment #1 attachment of [url https://bugs.eclipse.org/bugs/show_bug.cgi?id=186716]eclipse bug #186716 for full log output]

    then eclipse automatically switches focus to the console view again; displaying
    the following:
    $BEA_HOME/weblogic92/samples/domains/workshop/bin/stopWebLogic.sh:

    Stopping Weblogic Server...

    Initializing WebLogic Scripting Tool (WLST) ...

    Welcome to WebLogic Server Administration Scripting Shell

    Type help() for help on available commands

    Connecting to t3://localhost:7001 with userid weblogic ...
    This Exception occured at Sun May 13 12:35:42 BST 2007.
    javax.naming.CommunicationException [Root exception is
    java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested
    exception is:
    java.net.ConnectException: Connection refused; No available router to
    destination]
    ...[see 13_05_07_eclipse_wls_shutdown.txt in [url https://bugs.eclipse.org/bugs/attachment.cgi?id=66989]comment #1 attachment of [url https://bugs.eclipse.org/bugs/show_bug.cgi?id=186716]eclipse bug #186716 for full
    stack trace]

    the servers view eventually indicates the server has transitioned to the
    "Stopped" state. the problem is, i never commanded neither eclipse or wls to
    shutdown the wls server.

    since the wls server can be successfully started outside of eclipse from the
    shell, and since - once it is successfully started outside of eclipse - wls
    doesn't automatically shutdown as soon as it starts; i suspect there is
    something in eclipse|wtp that is triggering the automatic
    shutdown. but of course, i could be wrong. maybe something
    in wls itself is at fault.

    i encountered this exact same bug in wls 9.0 with eclipse 3.2.2/wtp 1.5.3 on
    solaris 9 sparc (which is what prompted me to upgrade to wls 9.2 on solaris 9
    sparc; see [url https://bugs.eclipse.org/bugs/show_bug.cgi?id=169197]eclipse bug #169197); and i encounter this exact same bug with wls 9.2 with
    eclipse 3.2.2/wtp 1.5.3 in mac os x 10.4.9! there is a
    slight difference in what happens in solaris vs what happens on the mac. on the mac, the exception appears to
    be thrown at a different point (when a wldeploy.xml script
    is executed; not at the point of "Initializing WebLogic
    Scripting Tool (WLST)" like in the solaris installation):
    Buildfile: /Applications/eclipse/plugins/org.eclipse.jst.server.generic.weblogic_1.5.1.v200609141504/buildfiles/wldeploy.xml
    init:
    deploy:
    [echo] Deploying module WTP_WebApp_Tutorial
    [wldeploy] weblogic.Deployer -debug -verbose -noexit -name WTP_WebApp_Tutorial -source /Users/bilbo/development/projects/eclipse_3.2.2_tutorial/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/WTP_WebApp_Tutorial -adminurl t3://localhost:7001 -user weblogic -password ******** -deploy
    [wldeploy] weblogic.Deployer invoked with options: -debug -verbose -noexit -name WTP_WebApp_Tutorial -source /Users/bilbo/development/projects/eclipse_3.2.2_tutorial/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/WTP_WebApp_Tutorial -adminurl t3://localhost:7001 -user weblogic -deploy
    [wldeploy] [WebLogicDeploymentManagerImpl.init():103] : Constructing DeploymentManager for J2EE version V1_4 deployments
    [wldeploy] [WebLogicDeploymentManagerImpl.getNewConnection():146] : Connecting to admin server at localhost:7001, as user weblogic
    [wldeploy] [ServerConnectionImpl.getEnvironment():288] : setting environment
    [wldeploy] [ServerConnectionImpl.getEnvironment():291] : getting context using t3://localhost:7001
    [wldeploy] [ServerConnectionImpl.close():334] : Closing DM connection
    [wldeploy] [ServerConnectionImpl.close():354] : Unregistered all listeners
    [wldeploy] weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 't3://localhost:7001': Destination unreachable; nested exception is:
    [wldeploy] java.net.ConnectException: Connection refused; No available router to destination. Ensure the url represents a running admin
    ... also, on the mac the cgServer.log has the following additional log entries:
    ...
    ...Graceful shutdown of cgServer was issued remotely from 10.0.0.9
    ...Server shutdown has been requested by weblogic
    ...Server state changed to SUSPENDING
    ...
    ... Server state changed to ADMIN
    ...Server state changed to SHUTTING_DOWN
    ...
    ...Channel "Default[2]" listening on 127.0.0.1:7001 was shutdown.
    ...in all cases, i have done nothing
    more and nothing less than what the eclipse/wtp and weblogic documentation has
    instructed me to do.

    please, can anybody suggest a fix or a workaround. thanks in advance.

    --
    Edited by wboyd at 05/13/2007 7:48 AM

    DB:3.07:How Do I Make Wls 9.2 Stop Shutting Itself Down Within Eclipse 3.2.2? p3

    Hi,

    That release note applied to the custom WLS server adapter shipped with Workshop; fairly certain this use case (at least the bugzilla item) was related to the generic WLS server adapter that is included with WTP (completely different logic).

    -Rob

  • RELEVANCY SCORE 3.07

    DB:3.07:Error In Migrating Weblogic 8.2 To Weblogic 9.2 pj


    Hi,

    We are trying to upgrade to Weblogic 9.2 from Weblogic 8.2.
    We are using Queues in our application and we are using default host and port in our application for connecting that
    t3://localhost/

    But when we tried to migrate the application, Weblogic 9.2 expects the port to be supplied as part of Connection URL instead of taking the default port

    java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):null:7001:10.45.4.131:-1'; No available router to destination
    at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:475)
    at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:326)
    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:261)
    at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:204)
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:226)
    Truncated. see log file for complete stacktrace

    Please help me how to connect to JMS without specifying the default port in the connection string.

    -Vendhan

    DB:3.07:Error In Migrating Weblogic 8.2 To Weblogic 9.2 pj

    Has anyone sucessfully connected the JMS without specying the port in Weblogic 92?

  • RELEVANCY SCORE 3.07

    DB:3.07:Service Pack Versioning Problem cm


    Can anyone help me solve service pack versioning problem please. This
    problem may solve some of my other problems.

    I am trying to check if my service pack has been installed properly or not.
    I issue following command from command prompt:
    C:\java weblogic.Admin t3://localhost:7001 VERSION

    I get the following error: "Failed to connect to t3://localhost:7001 due to:
    [java.net.ConnectException: No server found at T3://localhost:7001]"

    At this time, I have weblogic 5.1 installed with service pack 2 installed.
    If I run server seems to be running, and connecting to my
    database.Eventually I am planning to upgrade to SP6 and run with jdk1.3.

    2nd problem: When I make JAVA_HOME= JDK1.3, wls does not run.

    DB:3.07:Service Pack Versioning Problem cm

    Thanks Mike, you are right. The server was not running while I was testing
    service pack test.
    And service pack is installed. Thanks
    WLAS5.1 does not run once I change JAVA_HOME TO "C:\jdk1.3.0_02", that
    where I have jdk1.3
    I get following error message:"wlserver.exe has generated error and will be
    closed by windows. You will need to restart the program."

    John

    "Mike Reiche" mreiche@pacbell.net wrote in message
    news:3ac8fe17$1@newsgroups.bea.com...

    1) You WLAS does not seem to be listening on port 7001 of your
    localhost. Is it listening on a different port? Running on a
    different machine?

    2) What error message do you get when trying to run WLAS with
    JDK 1.3? WLAS does definitely run with JDK 1.3

    Mike Reiche

    "John" adhindsa@entiresoft.com wrote:
    Can anyone help me solve service pack versioning problem please. This
    problem may solve some of my other problems.

    I am trying to check if my service pack has been installed properly or
    not.
    I issue following command from command prompt:
    C:\java weblogic.Admin t3://localhost:7001 VERSION

    I get the following error: "Failed to connect to t3://localhost:7001
    due to:
    [java.net.ConnectException: No server found at T3://localhost:7001]"

    At this time, I have weblogic 5.1 installed with service pack 2installed.
    If I run server seems to be running, and connecting to my
    database.Eventually I am planning to upgrade to SP6 and run with jdk1.3.

    2nd problem: When I make JAVA_HOME= JDK1.3, wls does not run.

  • RELEVANCY SCORE 3.07

    DB:3.07:Could Not Find Classloader xz



    Hi,

    I just installed WLS 8.1 and deployed my EJB jar file using the admin console.
    According to the console the my service has been deployed successfully. However
    looking into the server log I see the following error:
    .DeploymentException: [Deployer:149233]An unexpected error was encountered during
    the deployment process. - with nested exception:
    [weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Could not find classloader
    for MINAService.jar in {MINAService.jar=CLNode{[gcl], 18544571-10808772,[MINAService@],[MINAService.jar],[J2EEApplicationContainer$Component(MINAService)]}}
    ]]
    at weblogic.management.deploy.slave.SlaveDeployer.throwUnexpected(SlaveDeployer.java:2222)
    at weblogic.management.deploy.slave.SlaveDeployer.access$700(SlaveDeployer.java:132)
    at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2364)
    at weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDeployer.java:2431)
    at weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.java:2343)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:833)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:542)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
    at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

    The server is running on port 7001. When I try to connect to the server at t3://localhost:7001
    using my EJB client I get an excpetion saying:

    We were unable to get a connection to the WebLogic server at t3://localhost:7001

    Please make sure that the server is running.

    Any idea what's going on?

    Thanks very much.

    Tony.

    DB:3.07:Could Not Find Classloader xz


    My client code was wrong.

    Tony.

    "Tony Blair" hrh747@hotmail.com wrote:

    Hi,

    I just installed WLS 8.1 and deployed my EJB jar file using the admin
    console.
    According to the console the my service has been deployed successfully.
    However
    looking into the server log I see the following error:
    .DeploymentException: [Deployer:149233]An unexpected error was encountered
    during
    the deployment process. - with nested exception:
    [weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Could not
    find classloader
    for MINAService.jar in {MINAService.jar=CLNode{[gcl], 18544571-10808772,[MINAService@],[MINAService.jar],[J2EEApplicationContainer$Component(MINAService)]}}
    ]]
    at weblogic.management.deploy.slave.SlaveDeployer.throwUnexpected(SlaveDeployer.java:2222)
    at weblogic.management.deploy.slave.SlaveDeployer.access$700(SlaveDeployer.java:132)
    at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2364)
    at weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDeployer.java:2431)
    at weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.java:2343)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:833)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:542)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
    at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

    The server is running on port 7001. When I try to connect to the server
    at t3://localhost:7001
    using my EJB client I get an excpetion saying:

    We were unable to get a connection to the WebLogic server at t3://localhost:7001

    Please make sure that the server is running.

    Any idea what's going on?

    Thanks very much.

    Tony.

  • RELEVANCY SCORE 3.07

    DB:3.07:Not Able To Hit Bpm Engine *************** zk


    Hi Experts,
    I am trying hit a BPM engine hosted in a remote WLS cluster environment.
    I have a stand alone java papi client , which try to get instances...doing some session.getInstanceByFilter...

    I am getting the the Session but when it try to a session.getInstanceByFilter it fails ....I had set the system properties giving the path of my bpm engine jndi propeties files ...
    System.setProperty("fuego.j2ee.initialctx.file", JNDIPROS_PATH);

    And my property file conatins :

    java.naming.factory.initial = weblogic.jndi.WLInitialContextFactory
    java.naming.provider.url = t3://remoteserver:30434 .

    Any thing i missed out ? DO i need give the ENGINE.ID ?

    Not able to understand why its looking for t3://localhost:7001 ,where my BPM WLS server address is diffrent ..

    Err :

    An error occurred when subscribing to the JMS Topic engine. Reason:'javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:

    java.net.ConnectException: Connection refused; No available router to destination]

    Caused by: t3://localhost:7001: Destination unreachable; nested exception is:

    java.net.ConnectException: Connection refused; No available router to destination

    javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:

    java.net.ConnectException: Connection refused; No available router to destination]

    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:47)

    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:651)

    DB:3.07:Not Able To Hit Bpm Engine *************** zk

    Hi have faced similar kind of problem

    Edited by: Brijesh Kumar Singh on Dec 23, 2009 4:08 AM

  • RELEVANCY SCORE 3.07

    DB:3.07:Error:Destination Unreachable j9


    Hi all,
    I'm trying to develop a simple Session Bean using Weblogic 8.1.
    While deploying i got message as ejbc successful.
    But while running client application i got following error.
    Please anyone help to resolve this.
    Thanks,
    latha

    E:\slsbjava Client
    Exception in thread "main" javax.naming.CommunicationException [Root exception i
    s java.net.ConnectException: t3://localhost:7001: Destination unreachable; neste
    d exception is:
    java.net.SocketException: Invalid argument: connect; No available router
    to destination]
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(Exceptio
    nTranslator.java:47)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLIni
    tialContextFactoryDelegate.java:636)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
    tialContextFactoryDelegate.java:306)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
    tialContextFactoryDelegate.java:239)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialCont
    extFactory.java:135)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
    62)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243
    )
    at javax.naming.InitialContext.init(InitialContext.java:219)
    at javax.naming.InitialContext.init(InitialContext.java:195)
    at Client.main(Client.java:12)
    Caused by: java.net.ConnectException: t3://localhost:7001: Destination unreachab
    le; nested exception is:
    java.net.SocketException: Invalid argument: connect; No available router
    to destination
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
    tialContextFactoryDelegate.java:296)
    ... 7 more

    DB:3.07:Error:Destination Unreachable j9

    Hi all,
    I'm trying to develop a simple Session Bean using Weblogic 8.1.
    While deploying i got message as ejbc successful.
    But while running client application i got following error.
    Please anyone help to resolve this.
    Thanks,
    latha

    E:\slsbjava Client
    Exception in thread "main" javax.naming.CommunicationException [Root exception i
    s java.net.ConnectException: t3://localhost:7001: Destination unreachable; neste
    d exception is:
    java.net.SocketException: Invalid argument: connect; No available router
    to destination]
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(Exceptio
    nTranslator.java:47)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLIni
    tialContextFactoryDelegate.java:636)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
    tialContextFactoryDelegate.java:306)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
    tialContextFactoryDelegate.java:239)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialCont
    extFactory.java:135)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
    62)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243
    )
    at javax.naming.InitialContext.init(InitialContext.java:219)
    at javax.naming.InitialContext.init(InitialContext.java:195)
    at Client.main(Client.java:12)
    Caused by: java.net.ConnectException: t3://localhost:7001: Destination unreachab
    le; nested exception is:
    java.net.SocketException: Invalid argument: connect; No available router
    to destination
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
    tialContextFactoryDelegate.java:296)
    ... 7 more

  • RELEVANCY SCORE 3.07

    DB:3.07:Ejb Examples - T3 Client Problem mz


    I can't get the t3 client to connect to my WLS server installation on my local machine. I am trying to run the CMP ejb example. I set the url to t3://localhost:7001, t3://[hostname]:7001, t3://[ip]:7001 without success. I even edited and recompiled the .java source for the client with these changes. I have no problem connecting to the WLS server instance using http://localhost:7001.When I use http://, the server logs indicate that a connection was made. When I try to connect using t3://, no connection attempt is apparent in my WLS log file.My license is a developer licence packaged with Visual Cafe.System details:JDK_1.2.2Win 2000WLS 5.1 sp8Thank you for any insight,Mark C. Schwartz

    DB:3.07:Ejb Examples - T3 Client Problem mz

    I can't get the t3 client to connect to my WLS server installation on my local machine. I am trying to run the CMP ejb example. I set the url to t3://localhost:7001, t3://[hostname]:7001, t3://[ip]:7001 without success. I even edited and recompiled the .java source for the client with these changes. I have no problem connecting to the WLS server instance using http://localhost:7001.When I use http://, the server logs indicate that a connection was made. When I try to connect using t3://, no connection attempt is apparent in my WLS log file.My license is a developer licence packaged with Visual Cafe.System details:JDK_1.2.2Win 2000WLS 5.1 sp8Thank you for any insight,Mark C. Schwartz

  • RELEVANCY SCORE 3.07

    DB:3.07:Problems With Weblogic.Admin 9j


    When I run anything to do with the weblogic.Admin I get this error.

    root@devmix01::/opt/weblogic java -native weblogic.Admin t3://devmix01:7001 VERSION system `password`
    Failed to connect to t3://devmix01:7001 due to: [weblogic.socket.UnrecoverableConnectException: [Login failed: 'No license:License allows connections from only: '3' unique IP addresses.]]

    DB:3.07:Problems With Weblogic.Admin 9j

    When I run anything to do with the weblogic.Admin I get this error.

    root@devmix01::/opt/weblogic java -native weblogic.Admin t3://devmix01:7001 VERSION system `password`
    Failed to connect to t3://devmix01:7001 due to: [weblogic.socket.UnrecoverableConnectException: [Login failed: 'No license:License allows connections from only: '3' unique IP addresses.]]

  • RELEVANCY SCORE 3.07

    DB:3.07:Weblogic Ant Deployment c9


    weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 't3://localhost:7001': weblogic.rjvm.ServerURL.findOrCreateRJVM(ZLjava/lang/String;Lweblogic/rmi/spi/HostID;IZ)Lweblogic/rjvm/RJVM;. Ensure the url represents a running admin server and that the credentials are correct. If using http protocol, tunneling must be enabled on the admin server.I am getting the above exception even i am able to,login using the same credentials in Admin Console.

    DB:3.07:Weblogic Ant Deployment c9

    weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 't3://localhost:7001': weblogic.rjvm.ServerURL.findOrCreateRJVM(ZLjava/lang/String;Lweblogic/rmi/spi/HostID;IZ)Lweblogic/rjvm/RJVM;. Ensure the url represents a running admin server and that the credentials are correct. If using http protocol, tunneling must be enabled on the admin server.I am getting the above exception even i am able to,login using the same credentials in Admin Console.

  • RELEVANCY SCORE 3.07

    DB:3.07:Bug- User: Weblogic, Failed To Be Authenticated jp


    Seems like a bug in Oracle WebLogic Server 11gR1 (10.3.6) + Coherence - Package InstallerWhen a wldeploy task is run in a build script the following error is generated. weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 't3://localhost:7001': User: weblogic, failed to be authenticated.. Ensure the url represents a running admin server and that the credentials are correct. If using http protocol, tunneling must be enabled on the admin server.Login into Admin Console with same username and password is fine.

    DB:3.07:Bug- User: Weblogic, Failed To Be Authenticated jp

    Please try the following and let us know if it helps.Set your environment. From your domain bin directory (for example, /opt/bea/user_projects/domains/exampleDomain/bin), execute setDomainEnv.sh (UNIX) or setDomainEnv.cmd (Windows).Deploy the application using ant.