facebook

Using WebLogic 9 connector

💡
Our Forums Have Moved

For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub

  1. MyEclipse Archived
  2.  > 
  3. Application Servers and Deployment
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #255590 Reply

    Baljit Singh
    Member

    I am using MyEclipse 5.0 M2 / WebLogic 9.2 on windows XP2.

    I have 2 issues

    First – When I do shutdown server, I get the message that it can’t find file shutdown.py.

    Second – Issue is that my application is deployed to applications folder under domain directory and WL 9 doesn’t seem to recognize it being there.
    I have to use weblogic admin console to deploy the application

    Thanks

    Baljit

    #255664

    Riyad Kalla
    Member

    Baljit,
    The second problem was a bug that will be addressed in the 5.0 GA release in a week. The first issue should have been address in 4.1.1 as noted here:
    http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-11178-highlight-shutdown+py.html

    Can you check your log file for an exception pertaining to the shutdown.py file, maybe the location in the 9.2 release changed?

    #255689

    Baljit Singh
    Member

    shutdown.py file is created when I stop the server using stopWebLogic.cmd file which is in bin directory of the domain.

    Weblogic Version : 9.2

    When I use MyEclipse stop weblogic server, I do get errors below:

    
     
    Initializing WebLogic Scripting Tool (WLST) ...
    
    Welcome to WebLogic Server Administration Scripting Shell
    
    Type help() for help on available commands
    
    Connecting to t3://localhost:80 with userid system ...
    
    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.
    This Exception occured at Thu Jul 27 16:34:35 PDT 2006.
    java.io.IOException
        at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:135)
        at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:79)
        at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:326)
        at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)
        at weblogic.management.scripting.WLSTHelper.lookupMBeanServerConnection(WLSTHelper.java:633)
        at weblogic.management.scripting.WLSTHelper.initRuntimeServerConnection(WLSTHelper.java:359)
        at weblogic.management.scripting.WLSTHelper.initConnections(WLSTHelper.java:288)
        at weblogic.management.scripting.WLSTHelper.connect(WLSTHelper.java:188)
        at weblogic.management.scripting.WLScriptContext.connect(WLScriptContext.java:60)
        at weblogic.management.scripting.utils.WLSTUtil.initializeOnlineWLST(WLSTUtil.java:121)
        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:585)
        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._pyx6.connect$1(<iostream>:16)
        at org.python.pycode._pyx6.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.PyFunction.__call__(PyFunction.java:184)
        at org.python.pycode._pyx18.f$0(E:\eclipse_env\Eclipse3.2_v5.0_M2_BEA\workspace\Servers\shutdown.py:1)
        at org.python.pycode._pyx18.call_function(E:\eclipse_env\Eclipse3.2_v5.0_M2_BEA\workspace\Servers\shutdown.py)
        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.util.PythonInterpreter.execfile(PythonInterpreter.java:167)
        at weblogic.management.scripting.WLST.main(WLST.java:106)
        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:585)
        at weblogic.WLST.main(WLST.java:29)
    Caused by: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:80: Destination unreachable; nested exception is: 
        java.net.ConnectException: Connection refused: connect; No available router to destination]
        at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:49)
        at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:765)
        at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:362)
        at weblogic.jndi.Environment.getContext(Environment.java:307)
        at weblogic.jndi.Environment.getContext(Environment.java:277)
        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 weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:125)
        ... 34 more
    Caused by: java.net.ConnectException: t3://localhost:80: Destination unreachable; nested exception is: 
        java.net.ConnectException: Connection refused: connect; No available router to destination
        at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:204)
        at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:154)
        at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:341)
        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:336)
        ... 42 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:472)
        at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:323)
        at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:259)
        at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:202)
        at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:226)
        at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:189)
        ... 47 more
    Problem invoking WLST - Traceback (innermost last):
      File "E:\eclipse_env\Eclipse3.2_v5.0_M2_BEA\workspace\Servers\shutdown.py", line 1, in ?
      File "<iostream>", line 22, in connect
    WLSTException: 'Error occured while performing connect : "Cannot connect to WLST." Use dumpStack() to view the full stacktrace'
    
    
    #255693

    Riyad Kalla
    Member

    I installed and confirmed this issue on my end as well. I have filed it as a bug.

Viewing 4 posts - 1 through 4 (of 4 total)
Reply To: Using WebLogic 9 connector

You must be logged in to post in the forum log in