[jbosstools-issues] [JBoss JIRA] (JBIDE-11035) No notification when errors occur during publish

Wed Mar 21 01:27:47 EDT 2012

     [ https://issues.jboss.org/browse/JBIDE-11035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker resolved JBIDE-11035.
---------------------------------

    Resolution: Done

I've committed this change.  To verify, you can do the following:

1) Make a dynamic web project
2) Add a .java file somewhere in teh source folder
3) Verify project is build and .class file exist
4) Deploy the project to a jboss as7 server (no need for it to actually run on the server)
5) Verify deployment goes as planned, all files are where they belong, error log is empty, etc
6) Via terminal, remove the .class file for this java class
7) right-click on the module and select "full publish"
8) verify error log, server log both have events
9) verify the module in the servers view has an error decorator on the bottom left corner. 

> No notification when errors occur during publish
> ------------------------------------------------
>
>                 Key: JBIDE-11035
>                 URL: https://issues.jboss.org/browse/JBIDE-11035
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS/Servers
>    Affects Versions: 3.3.0.M5
>         Environment: Windows 7 64-bit / Eclipse Indigo SR1 32-bit / JBoss 4.2.3 (32-bit JVM)
>            Reporter: Daniel Atallah
>            Assignee: Rob Stryker
>             Fix For: 3.3.0.Beta3
>
>
> I've been experiencing issues with the reliability of publishing an EAR to the local server.
> While trying to debug the issue, I've noticed that in the eclipse log there are lots of failures (examples follow) - these aren't reported anywhere and it looks like the publish succeeded (the server is even marked as "Synchronized").
> Here are some examples of the errors in the log:
> {noformat}
> !ENTRY org.jboss.ide.eclipse.as.core 4 1644298242 2012-02-23 09:04:48.883
> !MESSAGE Full publish failed for module Rating
> !SUBENTRY 1 org.jboss.ide.eclipse.as.core 4 0 2012-02-23 09:04:48.883
> !MESSAGE The system cannot find the path specified
> !STACK 0
> java.io.IOException: The system cannot find the path specified
> 	at java.io.WinNTFileSystem.createFileExclusively(Native Method)
> 	at java.io.File.checkAndCreate(File.java:1704)
> 	at java.io.File.createTempFile(File.java:1792)
> 	at org.jboss.ide.eclipse.as.core.publishers.AbstractServerToolsPublisher.createForceZippedChild(AbstractServerToolsPublisher.java:246)
> 	at org.jboss.ide.eclipse.as.core.publishers.AbstractServerToolsPublisher.transferForceZippedChild(AbstractServerToolsPublisher.java:282)
> 	at org.jboss.ide.eclipse.as.core.publishers.AbstractServerToolsPublisher.fullPublish(AbstractServerToolsPublisher.java:216)
> 	at org.jboss.ide.eclipse.as.core.publishers.AbstractServerToolsPublisher.publishModule(AbstractServerToolsPublisher.java:113)
> 	at org.jboss.ide.eclipse.as.core.server.internal.v7.JBoss7JSTPublisher.publishModule(JBoss7JSTPublisher.java:39)
> 	at org.jboss.ide.eclipse.as.core.publishers.AbstractPublishMethod.publishModule(AbstractPublishMethod.java:79)
> 	at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:103)
> 	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1046)
> 	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1138)
> 	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:955)
> 	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
> 	at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3027)
> 	at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:341)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {noformat}
> The above appears to be specifically related to just the deployment.
> {noformat}
> !ENTRY org.jboss.ide.eclipse.as.core 4 1644298242 2012-02-23 08:28:12.652
> !MESSAGE Full publish failed for module RatingEngine
> !SUBENTRY 1 org.eclipse.wst.server.core 4 1644298251 2012-02-23 08:28:12.652
> !MESSAGE Error copying file META-INF\MANIFEST.MF: The system cannot find the path specified
> !SUBENTRY 1 org.eclipse.wst.server.core 4 1644298251 2012-02-23 08:28:12.652
> !MESSAGE Error copying file com\foo\rating\czar\Accessor$ShutdownHook.class: The system cannot find the path specified
> !SUBENTRY 1 org.eclipse.wst.server.core 4 1644298251 2012-02-23 08:28:12.652
> !MESSAGE Error copying file com\foo\rating\czar\Accessor.class: The system cannot find the path specified
> !SUBENTRY 1 org.eclipse.wst.server.core 4 1644298251 2012-02-23 08:28:12.652
> !MESSAGE Error copying file com\foo\rating\czar\ClassWeight.class: The system cannot find the path specified
> !SUBENTRY 1 org.eclipse.wst.server.core 4 1644298251 2012-02-23 08:28:12.652
> !MESSAGE Error copying file com\foo\rating\czar\Client.class: The system cannot find the path specified
> !SUBENTRY 1 org.eclipse.wst.server.core 4 1644298251 2012-02-23 08:28:12.652
> !MESSAGE Error copying file com\foo\rating\czar\CommunicationException.class: The system cannot find the path specified
> ...
> {noformat}
> The above was a case of eclipse not having actually built the project but thinking it had.
> With the way it works now, we have no idea if the publish succeeded or not - we only know if code changes don't seem to take effect (or in the case of a Clean publish, when the EAR deployment fails).
> There is something odd going on to cause the deployment issues (any pointers about the root cause are certainly welcome), but regardless of the reason, I think it is important that it's clear when a deployment isn't successful.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira