4:21 p.m.
Martin Malina created JBIDE-12156:
-------------------------------------
Summary: Apps are not deployed after EAP 6 restart
Key: JBIDE-12156
URL: https://issues.jboss.org/browse/JBIDE-12156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.CR1
Environment: jbdevstudio-product-universal-5.0.0.v20120605-2229-H183-CR1.jar
JBoss EAP 6 CR1
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 3.3.1
Found this when verifying JBIDE-11509.
When you have EAP 6 up and running with an app deployed (any app, e.g. a simple dynamic
web project) and then you stop and start the server, the app won't be deployed
anymore. This is specific to EAP. In AS 7.1.1 the app gets deployed at the server start.
With EAP 6 CR1 you will be shown this in the server log:
{code}
15:46:25,828 INFO [org.jboss.as.server.deployment.scanner] JBAS015003: Found dynproj.war
in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy
{code}
I understand this is an issue of EAP, but we need to decide if we can do something to
overcome this limitation.
--
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:29 p.m.
[
https://issues.jboss.org/browse/JBIDE-12156?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-12156:
---------------------------------------
This is the console output after the server restart:
{code}
16:25:11,821 INFO [org.jboss.modules] JBoss Modules version 1.1.2.GA-redhat-1
16:25:12,019 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA-redhat-1
16:25:12,064 INFO [org.jboss.as] JBAS015899: JBoss EAP 6.0.0.GA (AS 7.1.2.Final-redhat-1)
starting
16:25:12,929 INFO [org.jboss.as.server.deployment.scanner] JBAS015003: Found dynproj.war
in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy
16:25:12,951 INFO [org.jboss.as.server] JBAS015888: Creating http management service
using socket-binding (management-http)
16:25:12,958 INFO [org.xnio] XNIO Version 3.0.4.GA-redhat-1
16:25:12,973 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.4.GA-redhat-1
16:25:12,986 INFO [org.jboss.remoting] JBoss Remoting version 3.2.8.GA-redhat-1
16:25:13,004 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
16:25:13,008 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26)
JBAS016200: Activating ConfigAdmin Subsystem
16:25:13,049 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread
Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
16:25:13,068 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31)
JBAS010280: Activating Infinispan subsystem.
16:25:13,130 INFO [org.jboss.as.connector.logging] (MSC service thread 1-5) JBAS010408:
Starting JCA Subsystem (JBoss IronJacamar 1.0.11.Final-redhat-1)
16:25:13,173 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800:
Activating Naming Subsystem
16:25:13,176 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011906:
Activating OSGi Subsystem
16:25:13,190 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400:
Bound mail session [java:jboss/mail/Default]
16:25:13,193 INFO [org.jboss.as.naming] (MSC service thread 1-6) JBAS011802: Starting
Naming Service
16:25:13,264 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101:
Activating Security Subsystem
16:25:13,270 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48)
JBAS015537: Activating WebServices Extension
16:25:13,276 INFO [org.jboss.as.security] (MSC service thread 1-8) JBAS013100: Current
PicketBox version=4.0.9.Final-redhat-1
16:25:13,454 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service
thread 1-2) JBoss Web Services - Stack CXF Server 4.0.4.GA-redhat-1
16:25:13,483 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1)
Starting Coyote HTTP/1.1 on http-localhost/127.0.0.1:8080
16:25:13,701 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread
1-6) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
16:25:13,942 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1)
JBAS015012: Started FileSystemDeploymentService for directory
/Users/rasp/jbossqa/runtimes/jboss-eap-6.0.0.CR1/standalone/deployments
16:25:13,966 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening
on 127.0.0.1:4447
16:25:13,966 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening
on 127.0.0.1:9999
16:25:14,011 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console
listening on http://127.0.0.1:9990
16:25:14,011 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.0.0.GA
(AS 7.1.2.Final-redhat-1) started in 2480ms - Started 134 of 214 services (79 services are
passive or on-demand)
{code}
Apps are not deployed after EAP 6 restart
-----------------------------------------
Key: JBIDE-12156
URL: https://issues.jboss.org/browse/JBIDE-12156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.CR1
Environment: jbdevstudio-product-universal-5.0.0.v20120605-2229-H183-CR1.jar
JBoss EAP 6 CR1
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 3.3.1
Found this when verifying JBIDE-11509.
When you have EAP 6 up and running with an app deployed (any app, e.g. a simple dynamic
web project) and then you stop and start the server, the app won't be deployed
anymore. This is specific to EAP. In AS 7.1.1 the app gets deployed at the server start.
With EAP 6 CR1 you will be shown this in the server log:
{code}
15:46:25,828 INFO [org.jboss.as.server.deployment.scanner] JBAS015003: Found dynproj.war
in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy
{code}
I understand this is an issue of EAP, but we need to decide if we can do something to
overcome this limitation.
--
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
11:55 a.m.
[
https://issues.jboss.org/browse/JBIDE-12156?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-12156:
---------------------------------------------
This is definitely an EAP issue if anything - haven't seen this happen on AS7.x nor
previous EAP's.
Are we 100% sure this happens, even when using a clean EAP 6 installation and just using
command line copying before starting the server ?
Apps are not deployed after EAP 6 restart
-----------------------------------------
Key: JBIDE-12156
URL: https://issues.jboss.org/browse/JBIDE-12156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.CR1
Environment: jbdevstudio-product-universal-5.0.0.v20120605-2229-H183-CR1.jar
JBoss EAP 6 CR1
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 3.3.1
Found this when verifying JBIDE-11509.
When you have EAP 6 up and running with an app deployed (any app, e.g. a simple dynamic
web project) and then you stop and start the server, the app won't be deployed
anymore. This is specific to EAP. In AS 7.1.1 the app gets deployed at the server start.
With EAP 6 CR1 you will be shown this in the server log:
{code}
15:46:25,828 INFO [org.jboss.as.server.deployment.scanner] JBAS015003: Found dynproj.war
in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy
{code}
I understand this is an issue of EAP, but we need to decide if we can do something to
overcome this limitation.
--
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:09 p.m.
[
https://issues.jboss.org/browse/JBIDE-12156?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-12156:
---------------------------------------
To be sure this has nothing to do with JBDS/JBT, I tried this completely without our
tools. What I did:
1. Unzip EAP 6.0 CR1
2. Start the server using ./standalone.sh
3. Copy exploded war in deployments: cp -R dynproj.war
$JBOSS_HOME/standalone/deployments/
5. This told me I needed .dodeploy, so I did that: touch
$JBOSS_HOME/standalone/deployments/dynproj.war.dodeploy
6. Stop server
7. Start server again using ./standalone.sh
8. dynproj.war is not deployed - this is in server log:
{code}
12:01:48,788 INFO [org.jboss.as.server.deployment.scanner] JBAS015003: Found dynproj.war
in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy
{code}
Apps are not deployed after EAP 6 restart
-----------------------------------------
Key: JBIDE-12156
URL: https://issues.jboss.org/browse/JBIDE-12156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.CR1
Environment: jbdevstudio-product-universal-5.0.0.v20120605-2229-H183-CR1.jar
JBoss EAP 6 CR1
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 3.3.1
Found this when verifying JBIDE-11509.
When you have EAP 6 up and running with an app deployed (any app, e.g. a simple dynamic
web project) and then you stop and start the server, the app won't be deployed
anymore. This is specific to EAP. In AS 7.1.1 the app gets deployed at the server start.
With EAP 6 CR1 you will be shown this in the server log:
{code}
15:46:25,828 INFO [org.jboss.as.server.deployment.scanner] JBAS015003: Found dynproj.war
in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy
{code}
I understand this is an issue of EAP, but we need to decide if we can do something to
overcome this limitation.
--
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:11 p.m.
[
https://issues.jboss.org/browse/JBIDE-12156?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-12156:
---------------------------------------
Created JIRA in EAP project: JBPAPP-9328
Apps are not deployed after EAP 6 restart
-----------------------------------------
Key: JBIDE-12156
URL: https://issues.jboss.org/browse/JBIDE-12156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.CR1
Environment: jbdevstudio-product-universal-5.0.0.v20120605-2229-H183-CR1.jar
JBoss EAP 6 CR1
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 3.3.1
Found this when verifying JBIDE-11509.
When you have EAP 6 up and running with an app deployed (any app, e.g. a simple dynamic
web project) and then you stop and start the server, the app won't be deployed
anymore. This is specific to EAP. In AS 7.1.1 the app gets deployed at the server start.
With EAP 6 CR1 you will be shown this in the server log:
{code}
15:46:25,828 INFO [org.jboss.as.server.deployment.scanner] JBAS015003: Found dynproj.war
in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy
{code}
I understand this is an issue of EAP, but we need to decide if we can do something to
overcome this limitation.
--
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:49 p.m.
[
https://issues.jboss.org/browse/JBIDE-12156?page=com.atlassian.jira.plugi...
]
Len DiMaggio commented on JBIDE-12156:
--------------------------------------
Martin - can you confirm whether this bug exists with EAP 6 ER8? Thanks!
Apps are not deployed after EAP 6 restart
-----------------------------------------
Key: JBIDE-12156
URL: https://issues.jboss.org/browse/JBIDE-12156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.CR1
Environment: jbdevstudio-product-universal-5.0.0.v20120605-2229-H183-CR1.jar
JBoss EAP 6 CR1
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 3.3.1
Found this when verifying JBIDE-11509.
When you have EAP 6 up and running with an app deployed (any app, e.g. a simple dynamic
web project) and then you stop and start the server, the app won't be deployed
anymore. This is specific to EAP. In AS 7.1.1 the app gets deployed at the server start.
With EAP 6 CR1 you will be shown this in the server log:
{code}
15:46:25,828 INFO [org.jboss.as.server.deployment.scanner] JBAS015003: Found dynproj.war
in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy
{code}
I understand this is an issue of EAP, but we need to decide if we can do something to
overcome this limitation.
--
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:23 p.m.
[
https://issues.jboss.org/browse/JBIDE-12156?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-12156:
---------------------------------------
Len, see JBPAPP-9328 for more comments. The issue was introduced in EAP 6.0.0.ER7.
Apps are not deployed after EAP 6 restart
-----------------------------------------
Key: JBIDE-12156
URL: https://issues.jboss.org/browse/JBIDE-12156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.CR1
Environment: jbdevstudio-product-universal-5.0.0.v20120605-2229-H183-CR1.jar
JBoss EAP 6 CR1
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 3.3.1
Found this when verifying JBIDE-11509.
When you have EAP 6 up and running with an app deployed (any app, e.g. a simple dynamic
web project) and then you stop and start the server, the app won't be deployed
anymore. This is specific to EAP. In AS 7.1.1 the app gets deployed at the server start.
With EAP 6 CR1 you will be shown this in the server log:
{code}
15:46:25,828 INFO [org.jboss.as.server.deployment.scanner] JBAS015003: Found dynproj.war
in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy
{code}
I understand this is an issue of EAP, but we need to decide if we can do something to
overcome this limitation.
--
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
11:33 a.m.
[
https://issues.jboss.org/browse/JBIDE-12156?page=com.atlassian.jira.plugi...
]
Rob Stryker updated JBIDE-12156:
--------------------------------
Fix Version/s: 3.3.2
(was: 3.3.1)
Apps are not deployed after EAP 6 restart
-----------------------------------------
Key: JBIDE-12156
URL: https://issues.jboss.org/browse/JBIDE-12156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.CR1
Environment: jbdevstudio-product-universal-5.0.0.v20120605-2229-H183-CR1.jar
JBoss EAP 6 CR1
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 3.3.2
Found this when verifying JBIDE-11509.
When you have EAP 6 up and running with an app deployed (any app, e.g. a simple dynamic
web project) and then you stop and start the server, the app won't be deployed
anymore. This is specific to EAP. In AS 7.1.1 the app gets deployed at the server start.
With EAP 6 CR1 you will be shown this in the server log:
{code}
15:46:25,828 INFO [org.jboss.as.server.deployment.scanner] JBAS015003: Found dynproj.war
in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy
{code}
I understand this is an issue of EAP, but we need to decide if we can do something to
overcome this limitation.
--
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:08 p.m.
[
https://issues.jboss.org/browse/JBIDE-12156?page=com.atlassian.jira.plugi...
]
Rob Stryker updated JBIDE-12156:
--------------------------------
Fix Version/s: 4.0.x
(was: 3.3.2)
Apps are not deployed after EAP 6 restart
-----------------------------------------
Key: JBIDE-12156
URL: https://issues.jboss.org/browse/JBIDE-12156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.CR1
Environment: jbdevstudio-product-universal-5.0.0.v20120605-2229-H183-CR1.jar
JBoss EAP 6 CR1
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.0.x
Found this when verifying JBIDE-11509.
When you have EAP 6 up and running with an app deployed (any app, e.g. a simple dynamic
web project) and then you stop and start the server, the app won't be deployed
anymore. This is specific to EAP. In AS 7.1.1 the app gets deployed at the server start.
With EAP 6 CR1 you will be shown this in the server log:
{code}
15:46:25,828 INFO [org.jboss.as.server.deployment.scanner] JBAS015003: Found dynproj.war
in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy
{code}
I understand this is an issue of EAP, but we need to decide if we can do something to
overcome this limitation.
--
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
4298
days inactive
4400
days old
jbosstools-issues@lists.jboss.org
8 comments
4 participants
participants (4)
-
Len DiMaggio (JIRA) -
Martin Malina (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Rob Stryker (JIRA)