[JBoss JIRA] (JBIDE-16950) Very frequently, webapps are being undeployed right after being deployed
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16950?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-16950:
---------------------------------------
I tried this 3 times now with no success to replicate this issue:
deploy / undeploy / deploy / undeploy / deploy / undeploy
I'm on Mac. Perhaps this could be specific to Windows?
> Very frequently, webapps are being undeployed right after being deployed
> ------------------------------------------------------------------------
>
> Key: JBIDE-16950
> URL: https://issues.jboss.org/browse/JBIDE-16950
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta1
> Environment: Win 7-64, JDK 7, AS 7.1.1, WildFly 8.0.0
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-b
> Fix For: 4.2.0.Beta1
>
>
> I'm experiencing this issue where, after doing a full publishing, the deployed webapp is being undeployed right after being deployed.
> See http://screencast.com/t/JmwA0TlBrDWX
> The most reliable way (even though it's not 10% of the time) to reproduce the issue is to deploy a webapp to AS 7.1.1 or WF8, then remove it from the server, deploy it back. That's when the problem occurs :
> {noformat}
> 14:13:45,356 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "dontundeployme.war" (runtime-name: "dontundeployme.war")
> 14:13:45,485 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017534: Registered web context: /dontundeployme
> 14:13:45,683 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018559: Deployed "dontundeployme.war" (runtime-name : "dontundeployme.war")
> 14:13:50,708 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017535: Unregistered web context: /dontundeployme
> 14:13:50,730 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment dontundeployme.war (runtime-name: dontundeployme.war) in 23ms
> 14:13:50,999 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018558: Undeployed "dontundeployme.war" (runtime-name: "dontundeployme.war")
> 14:13:56,004 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) JBAS015003: Found dontundeployme.war in deployment directory. To trigger deployment create a file called dontundeployme.war.dodeploy
> {noformat}
> Also, pretty quite frequently, deployment just fails (but I haven't been able to figure out a decisive pattern yet) as the server thinks deployments are duplicates (see screencast)
--
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
12 years
[JBoss JIRA] (JBIDE-15969) Investigate removing some m2e extensions for TP
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15969?page=com.atlassian.jira.plugi... ]
Rastislav Wagner closed JBIDE-15969.
------------------------------------
verified in JBDS 8.0.0 and JBT 4.2.0 Beta1a. m2e-apt is installed by default and also present in central (marked as installed). m2e-wro-4j is present in central.
> Investigate removing some m2e extensions for TP
> -----------------------------------------------
>
> Key: JBIDE-15969
> URL: https://issues.jboss.org/browse/JBIDE-15969
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: target-platform
> Affects Versions: 4.1.1.CR1, 4.2.0.Alpha1
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.2.0.Alpha2
>
>
> It looks like m2e-wro4j is not used at all in JBoss Tools (only referenced in Central).
> It also appears that other m2e extensions (maven.apt and m2e.jdt) are not necessary to build JBT, and are only made available by default in JBDS installer and on Central.
> So I suggest the following changes:
> * Remove the 3 maven extensions (m2e.wro4j, maven.apt, m2e.jdt) from the JBT target-platform, and keep them only in Central
> * Remove m2e.wro4j from JBDS TP (as it's not part of installer)
--
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
12 years
[JBoss JIRA] (JBIDE-16950) Very frequently, webapps are being undeployed right after being deployed
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16950?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-16950:
--------------------------------
Labels: respin-b (was: )
> Very frequently, webapps are being undeployed right after being deployed
> ------------------------------------------------------------------------
>
> Key: JBIDE-16950
> URL: https://issues.jboss.org/browse/JBIDE-16950
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta1
> Environment: Win 7-64, JDK 7, AS 7.1.1, WildFly 8.0.0
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-b
> Fix For: 4.2.0.Beta1
>
>
> I'm experiencing this issue where, after doing a full publishing, the deployed webapp is being undeployed right after being deployed.
> See http://screencast.com/t/JmwA0TlBrDWX
> The most reliable way (even though it's not 10% of the time) to reproduce the issue is to deploy a webapp to AS 7.1.1 or WF8, then remove it from the server, deploy it back. That's when the problem occurs :
> {noformat}
> 14:13:45,356 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "dontundeployme.war" (runtime-name: "dontundeployme.war")
> 14:13:45,485 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017534: Registered web context: /dontundeployme
> 14:13:45,683 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018559: Deployed "dontundeployme.war" (runtime-name : "dontundeployme.war")
> 14:13:50,708 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017535: Unregistered web context: /dontundeployme
> 14:13:50,730 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment dontundeployme.war (runtime-name: dontundeployme.war) in 23ms
> 14:13:50,999 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018558: Undeployed "dontundeployme.war" (runtime-name: "dontundeployme.war")
> 14:13:56,004 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) JBAS015003: Found dontundeployme.war in deployment directory. To trigger deployment create a file called dontundeployme.war.dodeploy
> {noformat}
> Also, pretty quite frequently, deployment just fails (but I haven't been able to figure out a decisive pattern yet) as the server thinks deployments are duplicates (see screencast)
--
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
12 years
[JBoss JIRA] (JBIDE-16950) Very frequently, webapps are being undeployed right after being deployed
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16950?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-16950:
-------------------------------------
Sometimes, a full republish will work, sometimes it won't.
> Very frequently, webapps are being undeployed right after being deployed
> ------------------------------------------------------------------------
>
> Key: JBIDE-16950
> URL: https://issues.jboss.org/browse/JBIDE-16950
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta1
> Environment: Win 7-64, JDK 7, AS 7.1.1, WildFly 8.0.0
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-b
> Fix For: 4.2.0.Beta1
>
>
> I'm experiencing this issue where, after doing a full publishing, the deployed webapp is being undeployed right after being deployed.
> See http://screencast.com/t/JmwA0TlBrDWX
> The most reliable way (even though it's not 10% of the time) to reproduce the issue is to deploy a webapp to AS 7.1.1 or WF8, then remove it from the server, deploy it back. That's when the problem occurs :
> {noformat}
> 14:13:45,356 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "dontundeployme.war" (runtime-name: "dontundeployme.war")
> 14:13:45,485 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017534: Registered web context: /dontundeployme
> 14:13:45,683 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018559: Deployed "dontundeployme.war" (runtime-name : "dontundeployme.war")
> 14:13:50,708 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017535: Unregistered web context: /dontundeployme
> 14:13:50,730 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment dontundeployme.war (runtime-name: dontundeployme.war) in 23ms
> 14:13:50,999 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018558: Undeployed "dontundeployme.war" (runtime-name: "dontundeployme.war")
> 14:13:56,004 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) JBAS015003: Found dontundeployme.war in deployment directory. To trigger deployment create a file called dontundeployme.war.dodeploy
> {noformat}
> Also, pretty quite frequently, deployment just fails (but I haven't been able to figure out a decisive pattern yet) as the server thinks deployments are duplicates (see screencast)
--
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
12 years
[JBoss JIRA] (JBIDE-16950) Very frequently, webapps are being undeployed right after being deployed
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-16950:
-----------------------------------
Summary: Very frequently, webapps are being undeployed right after being deployed
Key: JBIDE-16950
URL: https://issues.jboss.org/browse/JBIDE-16950
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.0.Beta1
Environment: Win 7-64, JDK 7, AS 7.1.1, WildFly 8.0.0
Reporter: Fred Bricon
Assignee: Rob Stryker
Priority: Blocker
Fix For: 4.2.0.Beta1
I'm experiencing this issue where, after doing a full publishing, the deployed webapp is being undeployed right after being deployed.
See http://screencast.com/t/JmwA0TlBrDWX
The most reliable way (even though it's not 10% of the time) to reproduce the issue is to deploy a webapp to AS 7.1.1 or WF8, then remove it from the server, deploy it back. That's when the problem occurs :
{noformat}
14:13:45,356 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "dontundeployme.war" (runtime-name: "dontundeployme.war")
14:13:45,485 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017534: Registered web context: /dontundeployme
14:13:45,683 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018559: Deployed "dontundeployme.war" (runtime-name : "dontundeployme.war")
14:13:50,708 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017535: Unregistered web context: /dontundeployme
14:13:50,730 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment dontundeployme.war (runtime-name: dontundeployme.war) in 23ms
14:13:50,999 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018558: Undeployed "dontundeployme.war" (runtime-name: "dontundeployme.war")
14:13:56,004 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) JBAS015003: Found dontundeployme.war in deployment directory. To trigger deployment create a file called dontundeployme.war.dodeploy
{noformat}
Also, pretty quite frequently, deployment just fails (but I haven't been able to figure out a decisive pattern yet) as the server thinks deployments are duplicates (see screencast)
--
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
12 years
[JBoss JIRA] (JBIDE-16949) Active radio button should be checked
by Pavol Srna (JIRA)
Pavol Srna created JBIDE-16949:
----------------------------------
Summary: Active radio button should be checked
Key: JBIDE-16949
URL: https://issues.jboss.org/browse/JBIDE-16949
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: forge
Affects Versions: 4.2.0.Beta1
Reporter: Pavol Srna
Fix For: 4.2.0.Beta2
Attachments: forge-radio.png
Forge Console View contains dropdown list to switch between runtimes.
The list consists of radio buttons, but none is checked. The solution should be:
a) the active runtime radio btn is checked
b) or .. the list has no radio buttons.
--
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
12 years