[toconnor]

Created “fresh” BEA 9.1 domain to use with 5.0M2. Set up server preferences the same as in myEclipse 4.1. Built small Enterprise (EAR) application with one web application (WAR). Started server. It started normally. Deployed application (EAR). MyEclipse says deployment succeeded, but WebLogic does not recognize deployment. Weblogic Administrative console (http://localhost:7001/console) does not show any deployments.

One thing that is different: In myEclipse 4.1, the default deployment for WebLogic 9.1 was to the domain/autodeploy directory. 5.0M2 is placing the EAR in the domain/applications directory. Does something extra have to be done to deploy through domain/applications?

That said, I can get around the problem by deploying to <Custom Location – Suffixed> and specifying the autodeploy directory as the target. This works.

On another issue, some time ago there was a bug in 4.1 concerning errors on shutdown for BEA 9.1. This was fixed, but is back in 5.0M2. On shutdown, I always get the following:

Initializing WebLogic Scripting Tool (WLST) …

Welcome to WebLogic Server Administration Scripting Shell

Type help() for help on available commands

Problem invoking WLST – java.io.FileNotFoundException: C:\bea\user_projects\domains\base_domainM2_01\shutdown.py (The system cannot find the file specified)

Thanks for your help. My configuration is shown below:

*** Date: Mon Jul 10 16:01:59 CDT 2006

*** System properties:
OS=Windows2000
OS version=5.0
Java version=1.5.0_04

*** MyEclipse details:
MyEclipse Enterprise Workbench

Version: 5.0 Milestone 2
Build id: 20060703-5.0-M2

*** Eclipse details:
Eclipse SDK

Version: 3.2.0
Build id: M20060629-1905

Eclipse Graphical Editing Framework

Version: 3.2.0.v20060626
Build id: 20060627-0816

Eclipse Platform

Version: 3.2.0.v20060609m-AgOexn6hlEUsvBO
Build id: M20060629-1905

Eclipse RCP

Version: 3.2.0.v20060609m-SVDNgVrNoh-MeGG
Build id: M20060629-1905

Eclipse Java Development Tools

Version: 3.2.0.v20060609m-F7snq1fxia-Z4XP
Build id: M20060629-1905

Eclipse Plug-in Development Environment

Version: 3.2.0.v20060609m——6zXJJzJzJq
Build id: M20060629-1905

Eclipse Project SDK

Version: 3.2.0.v20060609m-GNq6oQq-7es-Y81
Build id: M20060629-1905

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-launcher
C:\eclipse32\eclipse\eclipse.exe
-name
Eclipse
-showsplash
600
-exitdata
8dc_7c
-vm
C:\bea\jdk150_04\jre\bin\javaw.exe

[Scott Anderson]

Thanks for reporting the issue with the deployment directory. This looks like either a change in the WLS 9 implementation or a regression from 4.1.1. In either case, we’ve entered a bug report and we’ll fix it for the 5.0 GA build in early August.

On the shutdown issue: WLS 9 uses a python script to shutdown servers gracefully. However, the python script is only created when you use the BEA-provided shell script to shutdown the server for the first time. From the commandline you need to run <domain-dir>\bin\stopWeblogic.cmd one time to enable graceful shutdown from within MyEclipse to function properly. However, even if you don’t do this, the server will still be shutdown since we first try a graceful shutdown and if that fails perform a hard shutdown. You can verify that it is successful by noticing in the Debug view that the server process is indeed dead after the shutdown command is run from the server view.

[toconnor]

Thank you for your quick response. On the shudown issue, I ran stopWebLogic.cmd as suggested. That ran successfully. However now when I try and shutdown the server from myEclipse, I get the following mess. (The server does shutdown however)

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 …
This Exception occured at Tue Jul 11 09:43:32 CDT 2006
Problem invoking WLST – Traceback (innermost last):
File “C:\bea\user_projects\domains\base_domainM2_01\shutdown.py”, line 1, in ?
File “<iostream>”, line 11, in connect
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’

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.scripting.WLSTHelper.populateInitialContext(WLSTHelper.java:492)
at weblogic.management.scripting.WLSTHelper.initDeprecatedConnection(WLSTHelper.java:545)
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\base_domainM2_01\shutdown.py:1)
at org.python.pycode._pyx18.call_function(C:\bea\user_projects\domains\base_domainM2_01\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: 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)
… 37 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)
… 42 more

[toconnor]

Note: I believe this was a problem in 4.1 that got fixed in 4.1.1. Now it is back. See http://www.myeclipseide.com/modules.php?op=modload&name=PNphpBB2&file=viewtopic&t=11178 for example

[Scott Anderson]

Yep, it’s a regression in 5.0M2. It’s a bummer, but we’ll get it fixed again in 5.0GA. In the interim, the workaround of using a custom location will work fine. Sorry for the break.

[Author]

Posts