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

Thu Mar 22 17:03:48 EDT 2012

    [ https://issues.jboss.org/browse/JBIDE-11035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678806#comment-12678806 ] 

Daniel Atallah commented on JBIDE-11035:
----------------------------------------

The decorator addition sounds like a good start to me - at least there will be some sort of indication that all is not well.

I think the the ideal solution would be to mark the resources that weren't published successfully as requiring another incremental publish (at the most granular level possible), and this would cause the failed resources to be automagically re-published.

Given that the above isn't currently possible, for my use case (which is a local development server, and the publish is to a local directory on the same local drive as the server) (probably a common setup), it seems like when an issue occurs, I'd want to mark the whole module as needing to be republished (because that's what I need to do anyway to fix it once it gets to this inconsistent state).

I can see that this behavior may be undesirable for other use cases - perhaps it could be configurable via a "Publishing" option in the Server settings?

> 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