8:56 a.m.
Daniel Atallah created JBIDE-11035:
--------------------------------------
Summary: 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
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
3:54 a.m.
[
https://issues.jboss.org/browse/JBIDE-11035?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-11035:
----------------------------------------
Fix Version/s: 3.3.0.Beta3
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
4:02 a.m.
[
https://issues.jboss.org/browse/JBIDE-11035?page=com.atlassian.jira.plugi...
]
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
12:21 a.m.
[
https://issues.jboss.org/browse/JBIDE-11035?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-11035:
-------------------------------------
We've decided to use decorators to indicate that there is SOME sort of problem, and
that the user should go investigate the error log or the server log view for further
details.
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
12:27 a.m.
[
https://issues.jboss.org/browse/JBIDE-11035?page=com.atlassian.jira.plugi...
]
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
4:03 p.m.
[
https://issues.jboss.org/browse/JBIDE-11035?page=com.atlassian.jira.plugi...
]
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
9:44 a.m.
[
https://issues.jboss.org/browse/JBIDE-11035?page=com.atlassian.jira.plugi...
]
Martin Malina closed JBIDE-11035.
---------------------------------
Verified it works as suggested by Rob (JBT nightly 3.3.0.v20120423-2057-H4719-Beta3).
Daniel, if you think there is still something to be done, please open a new JIRA.
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
5100
days inactive
5163
days old
jbosstools-issues@lists.jboss.org
6 comments
4 participants
participants (4)
-
Daniel Atallah (JIRA) -
Martin Malina (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Rob Stryker (JIRA)