[Xanthros]

The person who claimed WebLogic won’t run with JDK 1.6 is totally false.

I’m running WebLogic 10 with JDK 1.6. I get the same error as above using MyEclipse and autodeploy.

If I log into the console, install my web app and start it. Everything works fine.

I believe the autodeploy feature is broken.

This is taken from their documentation: http://e-docs.bea.com/wls/docs100/deployment/autodeploy.html
——————————————————————————————
Auto-Deploying, Redeploying, and Undeploying Archived Applications

To auto-deploy an archived application, copy its archive file to the /autodeploy directory. WebLogic Server automatically sets the application’s deployment mode to stage mode.

A deployment unit that was auto-deployed can be dynamically redeployed while the server is running. To dynamically redeploy, copy the new version of the archive file over the existing file in the /autodeploy directory.

To undeploy an archived deployment unit that was auto-deployed, delete the application from the /autodeploy directory. WebLogic Server stops the application and removes it from the configuration.
Note: If you delete an application from the /autodeploy directory when the server is not active, WebLogic Server will not detect that the application was deleted even when the server is again in an active state. In order to prevent an out-of-sync domain tree, BEA recommends that you only remove applications from the /autodeploy directory when the server is in an active state.
—————————————————————————————————

While the server was running:

1) Added test-webapp.war to the /autodeploy directory under my domain.
2) Logged into the console
3) The console showed the web application as *NEW* (If you login too quickly it will show the application as being distributed, refresh and it will show as new)
4) Then I deleted the test-webapp.war from the /autodeploy directory
5) Refreshed the console and the app still shows as *NEW*
6) Logged out of the console and closed my browser
7) Opened a new browser and logged in
8) The console *STILL* shows the web application as *NEW*

Now if you click on the *Lock & Edit* button and try to delete the web application it will state that the application is autodeployed and must be deleted from the /autodeploy directory.

And if you try and stop or start the web application of course you get an error. I had to basically choose undo all changes under Lock & Edit then stop and start the server again.
Then it picked up the web application was no longer there.

Great job BEA!

The install for BEA WebLogic 10 is also flawed! Choose to install their version of Eclipse.
It creates a directory named Eclipse32. Then later in the install process it asks for your eclipse directory or the one they installed. I pointed to the Eclipse32 directory and it complained that the directory wasn’t named Eclipse. So I manually renamed the directory to eclipse. I pointed to the renamed directory and it complained the version wasn’t 3.3.
FREAKING AWESOME! Did any idiot test this before it was released? 🙂

[Riyad Kalla]

Xanthros,
Thank you for the heads up into some WebLogic wonkiness, atleast it will let other users running into the issues know what is going on and that they aren’t doing anything wrong.

[sreegan]

Hi

The problem has nothing to do with
1) myeclipse configuration
2) Java incompatibility issues

Summary::
The issue is first time when you try autodeploy you might have had the wrong/corrupted ear file in the folder..this might have made an entry in the config.xml…so even after you fix the ear later and try the same by stopping the server and restarting that doesn’t work…same bug carried by weblogic from 8.1 to 9.2…

Do the following…
a) stop the server
b) clear C:\bea9\user_projects\domains\base_domain\config\configCache folder contents
c) clear C:\bea9\user_projects\domains\base_domain\config\deployments [Note:: Clear only your application ]
d) remove the entry of your autodeployed application from the config.xml
<app-deployment>
<name>_appsdir_CDWrapperServiceEar_dir</name>
<target>AdminServer</target>
<module-type>ear</module-type>
<source-path>autodeploy\CDWrapperServiceEar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
e) restart the server…

You are good to go….

[support-joy]

sreegan,

Thank you for sharing your findings.

[Author]

Posts