[jbosstools-issues] [JBoss JIRA] (JBIDE-11035) No notification when errors occur during publish
Rob Stryker (JIRA)
jira-events at lists.jboss.org
Tue Mar 20 05:02:47 EDT 2012
[ https://issues.jboss.org/browse/JBIDE-11035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677894#comment-12677894 ]
Rob Stryker commented on JBIDE-11035:
-------------------------------------
A decision was made earlier that only critical errors, such as missing runtimes or configuration data, would make the publish "fail". A missing file or two does not necessarily make the entire publish fail. A publish may still function despite one or two files not being copied over. The files that are not copied are logged as errors in the error log view.
The alternative is to throw a CoreException and abort the publish with an error dialog. Some users have complained about this aggressive aborting in the past, saying that one or two files being out of shape should be logged but not abort the entire publish, especially since perhaps many large files (jars, etc) were already copied over. ABorting the publish over a single .class file being missed would cause them substantial time for redeployment.
I suppose a third option is to simply mark the module as not-synchronized, but then we need to decide what level to require the next publish. In the past, we also tried forcing this (without an error) to be unsynchronized with a "full publish" requirement on the next publish, and users found this just as annoying, since unchanged jars need to be re-uploaded. Another option is to mark it as still requiring an incremental publish, but there's no way to return exactly which resources were not copied in the servertools framework, so marking it as still requiring an incremental publish would not be very useful in itself. It will miss over the files that were not copied earlier. (This point is not extensively tested, to see the exact behaviour if an incremental flag is returned.)
> 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
More information about the jbosstools-issues
mailing list