[JBoss JIRA] (JBIDE-12643) Deployment to EAP 5.1 does not work after stopping and starting the deployer using JMX
8:02 a.m.
Martin Malina created JBIDE-12643:
-------------------------------------
Summary: Deployment to EAP 5.1 does not work after stopping and starting the
deployer using JMX
Key: JBIDE-12643
URL: https://issues.jboss.org/browse/JBIDE-12643
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jmx
Affects Versions: 4.0.0.Alpha1
Environment: JBDS 6.0.0.Alpha1 H25
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.0.0.Alpha2
(This issue was discovered by rawagner and I was able to reproduce it myself.)
If you disable and then enable again the deployment on an EAP 5.1 server using JMX and
then try to deploy something, it doesn't get deployed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:04 a.m.
[
https://issues.jboss.org/browse/JBIDE-12643?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-12643:
---------------------------------------
Please note that I tried two other modified scenarios that work fine:
1. Avoid JBT altogether and just the server manually, copy the war manually and control
jmx via the jmx console - this seems to work
2. Only use JBT for server management, but copy the war manually - this also seems to
work
The above would suggest that it has something to do with copying the war after the
deployment was enabled again. But not sure about that.
Anyway, you should be able to reproduce this issue using the Steps to reproduce.
Deployment to EAP 5.1 does not work after stopping and starting the
deployer using JMX
--------------------------------------------------------------------------------------
Key: JBIDE-12643
URL: https://issues.jboss.org/browse/JBIDE-12643
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jmx
Affects Versions: 4.0.0.Alpha1
Environment: JBDS 6.0.0.Alpha1 H25
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.0.0.Alpha2
(This issue was discovered by rawagner and I was able to reproduce it myself.)
If you disable and then enable again the deployment on an EAP 5.1 server using JMX and
then try to deploy something, it doesn't get deployed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:23 a.m.
[
https://issues.jboss.org/browse/JBIDE-12643?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-12643:
-------------------------------------
present in jboss 5.1, eap 5.1. not present in jb6, not present in jb4.2.
Deployment to EAP 5.1 does not work after stopping and starting the
deployer using JMX
--------------------------------------------------------------------------------------
Key: JBIDE-12643
URL: https://issues.jboss.org/browse/JBIDE-12643
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jmx
Affects Versions: 4.0.0.Alpha1
Environment: JBDS 6.0.0.Alpha1 H25
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.0.0.Alpha2
(This issue was discovered by rawagner and I was able to reproduce it myself.)
If you disable and then enable again the deployment on an EAP 5.1 server using JMX and
then try to deploy something, it doesn't get deployed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:57 a.m.
[
https://issues.jboss.org/browse/JBIDE-12643?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-12643:
-------------------------------------
asking for feedback from other devs. I also need to investigate what can be done for the
eap5.1 release train, or whether anything *can* be done.
Deployment to EAP 5.1 does not work after stopping and starting the
deployer using JMX
--------------------------------------------------------------------------------------
Key: JBIDE-12643
URL: https://issues.jboss.org/browse/JBIDE-12643
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jmx
Affects Versions: 4.0.0.Alpha1
Environment: JBDS 6.0.0.Alpha1 H25
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.0.0.Alpha2
(This issue was discovered by rawagner and I was able to reproduce it myself.)
If you disable and then enable again the deployment on an EAP 5.1 server using JMX and
then try to deploy something, it doesn't get deployed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
8 a.m.
[
https://issues.jboss.org/browse/JBIDE-12643?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-12643:
---------------------------------------------
link to code:
http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/branches/JBPAPP_5_1/sy...
Deployment to EAP 5.1 does not work after stopping and starting the
deployer using JMX
--------------------------------------------------------------------------------------
Key: JBIDE-12643
URL: https://issues.jboss.org/browse/JBIDE-12643
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jmx
Affects Versions: 4.0.0.Alpha1
Environment: JBDS 6.0.0.Alpha1 H25
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.0.0.Alpha2
(This issue was discovered by rawagner and I was able to reproduce it myself.)
If you disable and then enable again the deployment on an EAP 5.1 server using JMX and
then try to deploy something, it doesn't get deployed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:08 a.m.
[
https://issues.jboss.org/browse/JBIDE-12643?page=com.atlassian.jira.plugi...
]
Rob Stryker updated JBIDE-12643:
--------------------------------
Fix Version/s: 4.0.x
(was: 4.0.0.Alpha2)
Deployment to EAP 5.1 does not work after stopping and starting the
deployer using JMX
--------------------------------------------------------------------------------------
Key: JBIDE-12643
URL: https://issues.jboss.org/browse/JBIDE-12643
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jmx
Affects Versions: 4.0.0.Alpha1
Environment: JBDS 6.0.0.Alpha1 H25
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.0.x
(This issue was discovered by rawagner and I was able to reproduce it myself.)
If you disable and then enable again the deployment on an EAP 5.1 server using JMX and
then try to deploy something, it doesn't get deployed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:52 a.m.
[
https://issues.jboss.org/browse/JBIDE-12643?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-12643.
---------------------------------
Fix Version/s: LATER
(was: 4.0.x)
Resolution: Duplicate Issue
Deployment to EAP 5.1 does not work after stopping and starting the
deployer using JMX
--------------------------------------------------------------------------------------
Key: JBIDE-12643
URL: https://issues.jboss.org/browse/JBIDE-12643
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jmx
Affects Versions: 4.0.0.Alpha1
Environment: JBDS 6.0.0.Alpha1 H25
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: LATER
(This issue was discovered by rawagner and I was able to reproduce it myself.)
If you disable and then enable again the deployment on an EAP 5.1 server using JMX and
then try to deploy something, it doesn't get deployed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:39 a.m.
[
https://issues.jboss.org/browse/JBIDE-12643?page=com.atlassian.jira.plugi...
]
Martin Malina closed JBIDE-12643.
---------------------------------
Verified.
Deployment to EAP 5.1 does not work after stopping and starting the
deployer using JMX
--------------------------------------------------------------------------------------
Key: JBIDE-12643
URL: https://issues.jboss.org/browse/JBIDE-12643
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jmx
Affects Versions: 4.0.0.Alpha1
Environment: JBDS 6.0.0.Alpha1 H25
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: LATER
(This issue was discovered by rawagner and I was able to reproduce it myself.)
If you disable and then enable again the deployment on an EAP 5.1 server using JMX and
then try to deploy something, it doesn't get deployed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4256
days inactive
4306
days old
jbosstools-issues@lists.jboss.org
7 comments
3 participants
participants (3)
-
Martin Malina (JIRA) -
Max Rydahl Andersen (JIRA)
-
Rob Stryker (JIRA)