2:55 a.m.
Rob Stryker created JBIDE-11776:
-----------------------------------
Summary: No errors for remote deploy only server
Key: JBIDE-11776
URL: https://issues.jboss.org/browse/JBIDE-11776
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta3
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.3.0.CR1
If what I'm seeing is different from the original scenario, let me know and I can
create another JIRA.
My steps:
1. Create a Deploy only server pointing to a remote host.
2. Quit Eclipse
3. Make sure the remote host is not reachable
4. Start Eclipse
5. Drag a simple Dynamic Web Project on the Deploy only server in the Server View
6. ASSERT some sort of error (e.g. Cannot publish to server, server not found...)
FAIL - no error, everything seems to be ok
--
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
2:59 a.m.
[
https://issues.jboss.org/browse/JBIDE-11776?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-11776:
-------------------------------------
I found a silent NPE which made deploy-only-server's "Server Behaviour"
section in the editor show nothing. I have committed this targeting this jira.
No errors for remote deploy only server
---------------------------------------
Key: JBIDE-11776
URL: https://issues.jboss.org/browse/JBIDE-11776
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta3
Reporter: Rob Stryker
Assignee: Martin Malina
Fix For: 3.3.0.CR1
If what I'm seeing is different from the original scenario, let me know and I can
create another JIRA.
My steps:
1. Create a Deploy only server pointing to a remote host.
2. Quit Eclipse
3. Make sure the remote host is not reachable
4. Start Eclipse
5. Drag a simple Dynamic Web Project on the Deploy only server in the Server View
6. ASSERT some sort of error (e.g. Cannot publish to server, server not found...)
FAIL - no error, everything seems to be ok
--
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
2:17 a.m.
[
https://issues.jboss.org/browse/JBIDE-11776?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-11776:
-------------------------------------
I am unable to replicate this. After doing exactly as mentioned, setting my hosts file to
map my remote server to a dummy ip with no response, I note the following:
1) The publishing job seems to last a significant amount of time
2) Once the timeout is reached, an error does pop up
(message is: failed to delete /remote/server/home/deploymentarea/DynWeb.war.
Operation failed. File system input or output error)
3) The rse thread trying to connect remains and is not terminated for a significant amount
of time, up to 4 minutes. This seems by design, judging by the code in
com.jcraft.jsch.Util
I will update the error messages to be a bit more clear and mention the host as well as
the remote resource, but in general I would argue this bug was fixed already.
No errors for remote deploy only server
---------------------------------------
Key: JBIDE-11776
URL: https://issues.jboss.org/browse/JBIDE-11776
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta3
Reporter: Rob Stryker
Assignee: Martin Malina
Fix For: 3.3.0.CR1
If what I'm seeing is different from the original scenario, let me know and I can
create another JIRA.
My steps:
1. Create a Deploy only server pointing to a remote host.
2. Quit Eclipse
3. Make sure the remote host is not reachable
4. Start Eclipse
5. Drag a simple Dynamic Web Project on the Deploy only server in the Server View
6. ASSERT some sort of error (e.g. Cannot publish to server, server not found...)
FAIL - no error, everything seems to be ok
--
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:12 a.m.
[
https://issues.jboss.org/browse/JBIDE-11776?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-11776.
---------------------------------
Resolution: Done
I've cleaned up the code a tiny bit and modified the error strings to be more clear,
but it seems to me it properly notes that there was an error.
No errors for remote deploy only server
---------------------------------------
Key: JBIDE-11776
URL: https://issues.jboss.org/browse/JBIDE-11776
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta3
Reporter: Rob Stryker
Assignee: Martin Malina
Fix For: 3.3.0.CR1
If what I'm seeing is different from the original scenario, let me know and I can
create another JIRA.
My steps:
1. Create a Deploy only server pointing to a remote host.
2. Quit Eclipse
3. Make sure the remote host is not reachable
4. Start Eclipse
5. Drag a simple Dynamic Web Project on the Deploy only server in the Server View
6. ASSERT some sort of error (e.g. Cannot publish to server, server not found...)
FAIL - no error, everything seems to be ok
--
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
8:31 a.m.
[
https://issues.jboss.org/browse/JBIDE-11776?page=com.atlassian.jira.plugi...
]
Martin Malina closed JBIDE-11776.
---------------------------------
Deploy only server now errors out, if the publish doesn't work. So I'm closing
this issue. But it would be nice if we could inform users that the remote host is
unavailable rather than wait what breaks which in this case is deleting of the deployment
from the server before trying to copy it there. I created a feature request here:
JBIDE-12046
Verified in jbdevstudio-product-universal-5.0.0.v201205272317M-H143-CR1.jar
No errors for remote deploy only server
---------------------------------------
Key: JBIDE-11776
URL: https://issues.jboss.org/browse/JBIDE-11776
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta3
Reporter: Rob Stryker
Assignee: Martin Malina
Fix For: 3.3.0.CR1
If what I'm seeing is different from the original scenario, let me know and I can
create another JIRA.
My steps:
1. Create a Deploy only server pointing to a remote host.
2. Quit Eclipse
3. Make sure the remote host is not reachable
4. Start Eclipse
5. Drag a simple Dynamic Web Project on the Deploy only server in the Server View
6. ASSERT some sort of error (e.g. Cannot publish to server, server not found...)
FAIL - no error, everything seems to be ok
--
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
5060
days inactive
5085
days old
jbosstools-issues@lists.jboss.org
4 comments
2 participants
participants (2)
-
Martin Malina (JIRA) -
Rob Stryker (JIRA)