[jbosstools-issues] [JBoss JIRA] (JBIDE-12156) Apps are not deployed after EAP 6 restart
Len DiMaggio (JIRA)
jira-events at lists.jboss.org
Fri Dec 7 10:49:17 EST 2012
[ https://issues.jboss.org/browse/JBIDE-12156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Len DiMaggio updated JBIDE-12156:
---------------------------------
Attachment: Screenshot-5.png
Seems OK now
[ldimaggi at ldimaggi bin]$ ./standalone.sh
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /opt/local/EAP6/jboss-eap-6.0
JAVA: /usr/lib/jvm/java-1.6.0-openjdk.x86_64/bin/java
JAVA_OPTS: -server -XX:+UseCompressedOops -Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml
=========================================================================
10:34:41,254 INFO [org.jboss.modules] JBoss Modules version 1.1.3.GA-redhat-1
10:34:41,705 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA-redhat-2
10:34:41,790 INFO [org.jboss.as] JBAS015899: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) starting
10:34:43,313 INFO [org.xnio] XNIO Version 3.0.7.GA-redhat-1
10:34:43,315 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
10:34:43,605 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.7.GA-redhat-1
10:34:43,702 INFO [org.jboss.remoting] JBoss Remoting version 3.2.14.GA-redhat-1
10:34:44,006 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
10:34:46,135 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
10:34:44,505 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
10:34:46,251 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011906: Activating OSGi Subsystem
10:34:46,255 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
10:34:46,284 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013171: Activating Security Subsystem
10:34:46,284 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
10:34:46,353 INFO [org.jboss.as.security] (MSC service thread 1-5) JBAS013170: Current PicketBox version=4.0.14.Final-redhat-2
10:34:46,403 INFO [org.jboss.as.connector.logging] (MSC service thread 1-8) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.13.Final-redhat-1)
10:34:46,440 INFO [org.jboss.as.naming] (MSC service thread 1-7) JBAS011802: Starting Naming Service
10:34:46,492 INFO [org.jboss.as.mail.extension] (MSC service thread 1-7) JBAS015400: Bound mail session [java:jboss/mail/Default]
10:34:46,718 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
10:34:46,826 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.0.6.GA-redhat-2
10:34:47,139 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http-/127.0.0.1:8080
10:34:47,639 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
10:34:47,696 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-5) JBAS015012: Started FileSystemDeploymentService for directory /opt/local/EAP6/jboss-eap-6.0/standalone/deployments
10:34:47,700 INFO [org.jboss.as.remoting] (MSC service thread 1-8) JBAS017100: Listening on 127.0.0.1:9999
10:34:47,700 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 127.0.0.1:4447
10:34:48,781 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
10:34:48,782 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
10:34:48,782 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) started in 10036ms - Started 136 of 217 services (80 services are passive or on-demand)
10:38:17,802 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found dynproj.war in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy
10:40:52,975 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "dynproj.war"
10:40:53,545 INFO [org.jboss.as.osgi] (MSC service thread 1-4) JBAS011907: Register module: Module "deployment.dynproj.war:main" from Service Module Loader
10:40:53,706 INFO [org.jboss.web] (MSC service thread 1-3) JBAS018210: Registering web context: /dynproj
10:40:53,903 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "dynproj.war"
^C10:41:36,875 INFO [org.apache.catalina.core.StandardContext] (MSC service thread 1-3) Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/] has not been started
10:41:36,877 INFO [org.jboss.as.osgi] (MSC service thread 1-5) JBAS011908: Unregister module: Module "deployment.dynproj.war:main" from Service Module Loader
10:41:36,907 INFO [org.jboss.as.logging] JBAS011503: Restored bootstrap log handlers
10:41:36,908 INFO [org.apache.coyote.http11.Http11Protocol] Pausing Coyote HTTP/1.1 on http-/127.0.0.1:8080
10:41:36,914 INFO [org.apache.coyote.http11.Http11Protocol] Stopping Coyote HTTP/1.1 on http-/127.0.0.1:8080
10:41:36,987 INFO [com.arjuna.ats.jbossatx] ARJUNA032018: Destroying TransactionManagerService
10:41:36,989 INFO [com.arjuna.ats.jbossatx] ARJUNA032014: Stopping transaction recovery manager
10:41:37,013 INFO [org.jboss.as.server.deployment] JBAS015877: Stopped deployment dynproj.war in 153ms
10:41:37,026 INFO [org.jboss.as] JBAS015950: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) stopped in 114ms
[ldimaggi at ldimaggi bin]$ ./standalone.sh
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /opt/local/EAP6/jboss-eap-6.0
JAVA: /usr/lib/jvm/java-1.6.0-openjdk.x86_64/bin/java
JAVA_OPTS: -server -XX:+UseCompressedOops -Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml
=========================================================================
10:41:46,079 INFO [org.jboss.modules] JBoss Modules version 1.1.3.GA-redhat-1
10:41:46,294 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA-redhat-2
10:41:46,673 INFO [org.jboss.as] JBAS015899: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) starting
10:41:47,731 INFO [org.jboss.as.server.deployment.scanner] JBAS015003: Found dynproj.war in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy
10:41:47,749 INFO [org.xnio] XNIO Version 3.0.7.GA-redhat-1
10:41:47,753 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
10:41:47,758 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.7.GA-redhat-1
10:41:47,767 INFO [org.jboss.remoting] JBoss Remoting version 3.2.14.GA-redhat-1
10:41:47,808 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
10:41:47,821 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
10:41:47,831 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
10:41:47,914 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011906: Activating OSGi Subsystem
10:41:47,927 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
10:41:47,947 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013171: Activating Security Subsystem
10:41:47,974 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
10:41:47,981 INFO [org.jboss.as.security] (MSC service thread 1-7) JBAS013170: Current PicketBox version=4.0.14.Final-redhat-2
10:41:48,027 INFO [org.jboss.as.connector.logging] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.13.Final-redhat-1)
10:41:48,076 INFO [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service
10:41:48,081 INFO [org.jboss.as.mail.extension] (MSC service thread 1-8) JBAS015400: Bound mail session [java:jboss/mail/Default]
10:41:48,157 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
10:41:48,229 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-6) JBoss Web Services - Stack CXF Server 4.0.6.GA-redhat-2
10:41:48,310 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http-/127.0.0.1:8080
10:41:48,526 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
10:41:48,750 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for directory /opt/local/EAP6/jboss-eap-6.0/standalone/deployments
10:41:48,751 INFO [org.jboss.as.remoting] (MSC service thread 1-5) JBAS017100: Listening on 127.0.0.1:4447
10:41:48,757 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on 127.0.0.1:9999
10:41:48,763 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "dynproj.war"
10:41:49,076 INFO [org.jboss.as.osgi] (MSC service thread 1-6) JBAS011907: Register module: Module "deployment.dynproj.war:main" from Service Module Loader
10:41:49,193 INFO [org.jboss.web] (MSC service thread 1-3) JBAS018210: Registering web context: /dynproj
10:41:49,210 INFO [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS018559: Deployed "dynproj.war"
10:41:49,454 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
10:41:49,455 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
10:41:49,455 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) started in 3710ms - Started 176 of 259 services (82 services are passive or on-demand)
^C10:44:15,677 INFO [org.jboss.as.logging] JBAS011503: Restored bootstrap log handlers
> 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.0.Final
>
> Attachments: Screenshot-5.png
>
>
> 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
More information about the jbosstools-issues
mailing list