- This topic has 26 replies, 4 voices, and was last updated 20 years, 2 months ago by
.
-
Posts
-
Hi
I am using Eclipse 3.0.1 and ME 3.8.2
The old application I had will no longer deploy to the Sun Java App Server 8 which in the J2EE SDK Q42004 Beta…The message I get is:
Deployment is out of date due to changes in the underlying project contents. You’ll need to manually ‘Redeploy’ the project to update the deployed archive.
I tried manuall redeployment, project recreation…Nothing helped…
Try this:
-
1) Stop your application server
2) Refresh your project by right clicking on the root and selcting “refresh”
3) Go back and “redeploy” your project
4) Start the app server againUsually this error occurs when the app server is running, it has read-locks on the files, so when you try and “redeploy” your app, it is unable to overwrite the locked files. You can highlight the deployment in the deployment list to see the error that occured below in the text box.
When I try to stop the App Server via ME I get the following:
[#|2004-09-30T10:45:46.765-0400|SEVERE|sun-appserver-pe8.1|javax.enterprise.system.core|_ThreadID=10;|CORE5071: An error occured during initialization
java.lang.IllegalArgumentException: null source
at java.util.EventObject.<init>(EventObject.java:34)
at javax.management.Notification.<init>(Notification.java:202)
at com.sun.enterprise.admin.event.AdminEvent.<init>(AdminEvent.java:102)
at com.sun.enterprise.admin.event.ShutdownEvent.<init>(ShutdownEvent.java:32)
at com.sun.enterprise.server.PEMain.shutdown(PEMain.java:314)
at com.sun.enterprise.server.PEMain.main(PEMain.java:122)
|#]If you start/stop this application server from the console, does it work, or does it also throw exceptions?
I can stop the server using server tools directly but not through ME/Eclipse…
In my case I can use “asadmin stop-domain domain1” from command propmt and the server will stop.
If I stop the server that way I am still not able to redeploy using the steps indicated in previous post.I am also using VSS plugin since my project is SCM based….If that has anything to do with this particular issue…But it worked with J2EE SDK Update 1.
I also verified teh app server setup and domain home…Everything looks exactly as before…
Are you deploying an exploded or packaged deployment? IIRC Sun Server only accepts WAR files, that you then have to deploy internally using the app server’s console.
In my case I can use “asadmin stop-domain domain1” from command propmt and the server will stop.
This may be a change in the interface since the 8.0 release. The 8.0 product stopped with “asadmin stop domain1”. Can you try that command from the commandline and see if it also works? I fear that they might have changed the interface to the server a bit.
Hmm the plot thikens….There is an error saying it couldn’t delete .myeclipse subdir..
But that dir is not part of the SCM (and it shouldnt be) and I can delete it manually.
There is no “read only” lock on that subdir either….After deleting it manually the redeploy fails again….
Here is an error:!ENTRY com.genuitec.eclipse.ast.deploy.core 1 1 Sep 30, 2004 12:11:12.928
!MESSAGE Build Exception
!STACK 0
com.genuitec.eclipse.core.GenuitecCoreException: Unable to clean build area C:/PROJECTS/mywebapp/.myeclipse
at com.genuitec.eclipse.ast.deploy.ant.J2EEArchiveDeployer.privExportWebProject(Unknown Source)
at com.genuitec.eclipse.ast.deploy.ant.J2EEArchiveDeployer.exportWebProject(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.DeploymentPackager.exportWebProject(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.WebDeployment.deployAsPackageArchive(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.Deployment.deploy(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.Deployment.redeploy(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.ui.dialog.DeploymentManagerDialog.ą(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.ui.dialog.DeploymentManagerDialog.access$2(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.ui.dialog.DeploymentManagerDialog$5.handleEvent(Unknown Source)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:796)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2772)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2431)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:668)
at org.eclipse.jface.window.Window.open(Window.java:648)
at com.genuitec.eclipse.ast.deploy.core.ui.action.DeploymentMgmtActionDelegate.runWithEvent(Unknown Source)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:266)
at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:206)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:915)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:866)
at org.eclipse.jface.action.ActionContributionItem$8.handleEvent(ActionContributionItem.java:824)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:796)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2772)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2431)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1377)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1348)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:254)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:141)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:96)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:335)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:273)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:129)
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:324)
at org.eclipse.core.launcher.Main.basicRun(Main.java:185)
at org.eclipse.core.launcher.Main.run(Main.java:704)
at org.eclipse.core.launcher.Main.main(Main.java:688)
Caused by: org.eclipse.core.runtime.CoreException: Unable to clean build area C:/PROJECTS/mywebapp/.myeclipse
at com.genuitec.eclipse.ast.deploy.ant.J2EEArchiveDeployer$1.run(Unknown Source)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1673)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1693)
… 40 moreI’m wonder if your source control plugin is interfering here… can you try and create a new project, and copy over some resources from your other project and try and use that, does it work fine?
@support-scott wrote:
In my case I can use “asadmin stop-domain domain1” from command propmt and the server will stop.
This may be a change in the interface since the 8.0 release. The 8.0 product stopped with “asadmin stop domain1”. Can you try that command from the commandline and see if it also works? I fear that they might have changed the interface to the server a bit.
The command you mentioned will not work…only asadmin stop-domain domin1 works
Amir
@support-rkalla wrote:
I’m wonder if your source control plugin is interfering here… can you try and create a new project, and copy over some resources from your other project and try and use that, does it work fine?
I doubt the VSS plugin is the culprit since it worked with last 2 releases of the J2EE SDK from Sun…
However, I did what you sugested and I am still having the same problem…Amir
The command you mentioned will not work…only asadmin stop-domain domin1 works
Then Sun has changed the operations interface of the server, which explains why stop no longer works. However, since it’s a beta release, I doubt we’ll be able to support the server until the final release comes out since they obviously don’t mind changing the interface during the beta cycle.
