Can not connect to ther admin server with t3s in the WLST

Kaos
    Hi,
    Our server face a strange problem.
    We want to add SSL to our server, and I have set the SSL linsten port enabled, an we can access the admin console with https protocol and SSL listen port.
    Then I want to manage the server with

    ##start WLST with DemoTrust enable
    java -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.security.TrustKeyStore=DemoTrust weblogic.WLST
    ##connect
    If I use
    connect('system','testAdmin','t3://xxxx:10001')
    ##this can connect successful.
    If I use
    connect('system','testAdmin','t3s://xxxx:10002')
    It will cause an error

    WLSTException: Error occured while performing connect : Error getting the initial context. There is no server running at t3s://xxxx:10002 Use dumpStack() to view the full stacktrace

    I both enabled plain and SSL listen port and I can access the admin console with http and https without problem. But why I just can not use t3s to connect the server in the WLST? Is there any setting related this? Please advise, thanks.

    Here is the dumpStack()


    javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3s://xxxx:10002: Destination unreachable; nested exception is:
            java.io.IOException: Stream closed.; 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.InitialContext.<init>(InitialContext.java:197)
    at weblogic.management.scripting.WLSTHelper.populateInitialContext(WLSTHelper.java:512)
    at weblogic.management.scripting.WLSTHelper.initDeprecatedConnection(WLSTHelper.java:565)
    at weblogic.management.scripting.WLSTHelper.initConnections(WLSTHelper.java:305)
    at weblogic.management.scripting.WLSTHelper.connect(WLSTHelper.java:203)
    at weblogic.management.scripting.WLScriptContext.connect(WLScriptContext.java:60)
    at weblogic.management.scripting.utils.WLSTUtil.initializeOnlineWLST(WLSTUtil.java:125)
    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 org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160)
    at org.python.core.PyMethod.__call__(PyMethod.java:96)
    at org.python.core.PyObject.__call__(PyObject.java:248)
    at org.python.core.PyObject.invoke(PyObject.java:2016)
    at org.python.pycode._pyx4.connect$1(<iostream>:16)
    at org.python.pycode._pyx4.call_function(<iostream>)
    at org.python.core.PyTableCode.call(PyTableCode.java:208)
    at org.python.core.PyTableCode.call(PyTableCode.java:404)
    at org.python.core.PyTableCode.call(PyTableCode.java:287)
    at org.python.core.PyFunction.__call__(PyFunction.java:179)
    at org.python.pycode._pyx15.f$0(<console>:1)
    at org.python.pycode._pyx15.call_function(<console>)
    at org.python.core.PyTableCode.call(PyTableCode.java:208)
    at org.python.core.PyCode.call(PyCode.java:14)
    at org.python.core.Py.runCode(Py.java:1135)
    at org.python.core.Py.exec(Py.java:1157)
    at org.python.util.PythonInterpreter.exec(PythonInterpreter.java:148)
    at org.python.util.InteractiveInterpreter.runcode(InteractiveInterpreter.java:89)
    at org.python.util.InteractiveInterpreter.runsource(InteractiveInterpreter.java:70)
    at org.python.util.InteractiveInterpreter.runsource(InteractiveInterpreter.java:44)
    at weblogic.management.scripting.WLST.main(WLST.java:178)
    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 weblogic.WLST.main(WLST.java:29)
    Caused by: java.net.ConnectException: t3s://xxxx:10002: Destination unreachable; nested exception is:
    java.io.IOException: Stream closed.; No available router to destination
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:203)
    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(Unknown Source)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:339)
    ... 43 more
    Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
    java.io.IOException: Stream closed.; 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:251)
    at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:194)
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:225)
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:188)
    ... 48 more

    Edited by: Kaos on Feb 25, 2010 12:06 AM
      • 1. Re: Can not connect to ther admin server with t3s in the WLST
        Jay SenSharma MiddlewareMagic
        Hi,

        The command which u are running is absolutely correct...

        Few Things...Are u able to accesss your Admin Server using : https://xxxx:10002/console ?

        Second thing Just to check any FireWall restriction you can try to Ping the AdminServer using following Command:

        after running . ./setWLSEnv.sh

        java weblogic.Admin -url t3s://xxxx:10002 -username system -password testAdmin PING

        If above command runs successfully means Firewall may not be an issue. But is it doesn't run Successfully means that Some N/w Setting is not allowing t3s may be...

        In this case Please try enabling "Http Tunneling on AdminServer" and then try to run the following commands:

        java weblogic.Admin -url https://xxxx:10002 -username system -password testAdmin PING


        Thanks
        Jay SenSharma
        http://jaysensharma.wordpress.com  (WebLogic Wonders Are Here)

        Edited by: Jay SenSharma on Feb 25, 2010 1:52 PM
        • 2. Re: Can not connect to ther admin server with t3s in the WLST
          Faisal WebLogic Wonders
          try reordering the command line the following way..

          java -Dweblogic.security.TrustKeyStore=DemoTrust -Dssl.debug=true Dweblogic.security.SSL.ignoreHostnameVerification=true weblogic.WLST

          If it doesnt work, paste the debug output that you get on adding -Dssl.debug=true
          1 位用户发现它有用
          • 3. Re: Can not connect to ther admin server with t3s in the WLST
            vishal iyer
            Jai/Faisal,

            One strange thing i observe, i tried connecting to admin server through WLST, it works for first time and again it gave me the error next (Connecting alternatively).

            the error message which i am getting:

            This Exception occurred at Thu Jun 10 08:19:39 CDT 2010.
            javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3s://mo8xdwls0018.bankofamerica.com:8933: Destination unreachable; nested exception is:
                    java.io.IOException: Stream closed.; 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.InitialContext.<init>(InitialContext.java:197)
            at weblogic.management.scripting.WLSTHelper.populateInitialContext(WLSTHelper.java:512)
            at weblogic.management.scripting.WLSTHelper.initDeprecatedConnection(WLSTHelper.java:565)
            at weblogic.management.scripting.WLSTHelper.initConnections(WLSTHelper.java:305)
            at weblogic.management.scripting.WLSTHelper.connect(WLSTHelper.java:203)
            at weblogic.management.scripting.WLScriptContext.connect(WLScriptContext.java:60)
            at weblogic.management.scripting.utils.WLSTUtil.initializeOnlineWLST(WLSTUtil.java:125)
            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 org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160)
            at org.python.core.PyMethod.__call__(PyMethod.java:96)

            we are connecting to t3s://mo8xdwls0018.bankofamerica.com:8933.

            Any help would be appreciated.

            -Vishal Iyer
            • 5. Re: Can not connect to ther admin server with t3s in the WLST
              vishal iyer
              Linux mo8xdwls0018.bankofamerica.com 2.6.18-164.2.1.el5 #1 SMP Mon Sep 21 04:37:42 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
              • 6. Re: Can not connect to ther admin server with t3s in the WLST
                Faisal WebLogic Wonders
                use this flag

                -Djava.security.egd=file:/dev/urandom
                • 7. Re: Can not connect to ther admin server with t3s in the WLST
                  Charles Cao-Oracle
                  I think maybe you can try this flag - "-Djava.security.egd=file:/dev/./urandom". Please refer to the wls doc - http://download.oracle.com/docs/cd/E14571_01/doc.1111/e14773/weblogic_server_issues.htm#CIHBBDID
                  • 8. Re: Can not connect to ther admin server with t3s in the WLST
                    638959
                    Hey Kaos, has the probelm been resolved? I'm facing the same problem now :( If it's been resolved, can you please post what the fix is? Thanks!
                    • 9. Re: Can not connect to ther admin server with t3s in the WLST
                      Dono
                      We had the same problem, but only when running on centOS 5, the problem doesn't occur on our RedHat 5 hosts - the problem was with random number generation - the JVM sets the property "securerandom.source" with a value of "/dev/urandom" in $JAVA_HOME/jre/lib/security/java.security, apparently that setting does not work and I have yet to find out why.

                      A simple modification of this property to "/dev/./urandom" fixed the problem.

                      The details related to this problem are described here: http://www.itonguard.com/20090313/weblogic-starts-slow/

                      Hope this helps.
                      • 10. Re: Can not connect to ther admin server with t3s in the WLST
                        931082
                        Yes, fixing the random number generator resolved the issue.

                        Looks like it is known bug with Oracle, it happen mainly when SSL configuration is used.

                        http://devcorn.com/java-io-ioexception-stream-closed-no-available-router-to-destination/