- This topic has 9 replies, 8 voices, and was last updated 16 years ago by
.
-
Posts
-
Yep, me again. 🙂
So I upgraded to the new MyEclipse release today as well as Eclipse 3.2 and starting WebLogic works fine, but I get all this when it tries to shutdown WebLogic. Using BEA’s script to shutdown WL works fine. I also tried deleting the shutdown.py file and getting a new one generated, but it didn’t make any difference. Also, no projects deployed to the server.
Initializing WebLogic Scripting Tool (WLST) ... Welcome to WebLogic Server Administration Scripting Shell Type help() for help on available commands Connecting to weblogic server instance running at t3://localhost:7001 as username weblogic ... javax.management.RuntimeOperationsException at weblogic.management.mbeanservers.compatibility.internal.MBeanProxy.getAttribute(MBeanProxy.java:306) at weblogic.management.mbeanservers.compatibility.internal.MBeanProxy.invoke(MBeanProxy.java:110) at $Proxy0.getName(Unknown Source) at weblogic.management.scripting.WLSTHelper.initDeprecatedConnection(WLSTHelper.java:551) at weblogic.management.scripting.WLSTHelper.initConnections(WLSTHelper.java:285) at weblogic.management.scripting.WLSTHelper.connect(WLSTHelper.java:187) at weblogic.management.scripting.WLScriptContext.connect(WLScriptContext.java:61) at weblogic.management.scripting.utils.WLSTUtil.initializeOnlineWLST(WLSTUtil.java:124) 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>:5) 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(C:\bea\user_projects\domains\CROWN\shutdown.py:1) at org.python.pycode._pyx18.call_function(C:\bea\user_projects\domains\CROWN\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:91) 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: weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception at weblogic.management.mbeanservers.compatibility.internal.RemoteMBeanServerImpl_910_WLStub.getAttribute(Unknown Source) at weblogic.management.mbeanservers.compatibility.internal.MBeanProxy.getAttribute(MBeanProxy.java:302) ... 32 more Caused by: java.io.IOException: RJVM has already been shutdown at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:191) at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:176) ... 34 more Caused by: java.io.IOException: RJVM has already been shutdown at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:488) at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:837) at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:390) at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:400) at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108) at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:175) ... 34 more The CompatabilityMBeanServer is not initialized properly. This might happen if the CompatabilityMBeanServer is disabled via the JMXMBean.To view the real 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 Aug 10 14:30:30 EDT 2006 java.io.IOException at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:133) at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:77) 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:644) at weblogic.management.scripting.WLSTHelper.initRuntimeServerConnection(WLSTHelper.java:360) at weblogic.management.scripting.WLSTHelper.initConnections(WLSTHelper.java:287) at weblogic.management.scripting.WLSTHelper.connect(WLSTHelper.java:187) at weblogic.management.scripting.WLScriptContext.connect(WLScriptContext.java:61) at weblogic.management.scripting.utils.WLSTUtil.initializeOnlineWLST(WLSTUtil.java:124) 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>:5) 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(C:\bea\user_projects\domains\CROWN\shutdown.py:1) at org.python.pycode._pyx18.call_function(C:\bea\user_projects\domains\CROWN\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:91) 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: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:48) at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:739) at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:343) at weblogic.jndi.Environment.getContext(Environment.java:263) 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:123) ... 34 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.findOrCreate(RJVMFinder.java:199) at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:137) at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:324) 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:319) ... 41 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:465) at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:316) at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:255) at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:199) at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:220) at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:187) ... 46 more Problem invoking WLST - Traceback (innermost last): File "C:\bea\user_projects\domains\CROWN\shutdown.py", line 1, in ? File "<iostream>", line 11, in connect WLSTException: 'Error occured while performing connect : Cannot connect to WLST. Use dumpStack() to view the full stacktrace'Thanks,
JeffJeff,
Caused by: java.io.IOException: RJVM has already been shutdown
This looks like what you’d get if you issued a shutdown and WebLogic was already shutdown. I retested locally and my instance started and shutdown as expected so I’m not sure what could be causing this. Can you verify externally that WebLogic is indeed running just before you issue the shutdown?
Yes, it is indeed still running and if I run bea’s shutdown script it is able to successfully stop the instance started by MyEclipse. Actually, it seems to be behaving like it was back in the MyEclipse 4.1 release. http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-11178.html
I am having the same issue and as described in http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-11178.html it only occurs when I launch weblogic 9.1 (from myEclipse) in “debug” mode. If I launch weblogic 9.1 (from myEclipse) in “running” mode, then the myEclipse shutdown seems to work. It is only if I launch in debug mode (which is usually the case) that the shutdown fails as described.
I’m running 5.0.1 and it’s still a problem. However if I change the configuration to Run mode then back to debug mode the error goes away. If I restart the workbench the problem comes back and I have to do the mode switch workaround again.
I’m having this problem and similar problems with WebLogic 9.2 on MyEclipse 5.1 GA.
I have similar problems on 4.0.2, and 5.5.
Is there a known cause or work around yet?
Thanks.
Rich Katz
======================================
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 …
WLST lost connection to the WebLogic Server that you were
connected to, this may happen if the server was shutdown or
partitioned. You will have to re-connect to the server once the
server is available.
Disconnected from weblogic server: myserverThe 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.
java.lang.StringIndexOutOfBoundsException: String index out of range: -2
at java.lang.String.substring(String.java:1768)
at weblogic.management.scripting.WLSTUtils.getListenAddress(WLSTUtils.java:179)
at weblogic.management.scripting.WLSTHelper.lookupMBeanServerConnection(WLSTHelper.java:619)
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)This Exception occured at Fri Apr 06 13:36:13 PDT 2007.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(C:\cygwin\opt\alerts\messaging-wl9\shutdown.py:1)
at org.python.pycode._pyx18.call_function(C:\cygwin\opt\alerts\messaging-wl9\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)
Problem invoking WLST – Traceback (innermost last):
File “C:\cygwin\opt\alerts\messaging-wl9\shutdown.py”, line 1, in ?
File “<iostream>”, line 22, in connect
WLSTException: ‘Error occured while performing : “Cannot connect to WLST.”String index out of range: -2 Use dumpStack() to view the full stacktrace’Rich,
Is there anything odd about the domain? Setting up a default WL install and a default domain I can start, stop and restart the domains without any problems. Is it maybe a managed domain?I have the same problems when I shutdown the weblogic from the myeclipes, and the problems are described as the above.
Thanks.
