2:36 p.m.
AS 7 standalone instance doesn't shutdown
-----------------------------------------
Key: AS7-961
URL: https://issues.jboss.org/browse/AS7-961
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.0.0.Beta3
Environment: Ubuntu 11.04,
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode)
Reporter: Marek Novotny
After failed deployment server standalone instance doesn't shutdown.
I have pushed CTRL+C and it tried to shutdown:
{code}
21:11:24,194 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread
1-1) HornetQ Server version 2.1.2.Final (Colmeia, 120) started
21:11:25,026 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed
to start service jboss.deployment.unit."jboss-seam-jpa.war".PARSE:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."jboss-seam-jpa.war".PARSE: Failed to process phase PARSE
of deployment "jboss-seam-jpa.war"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:108)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to
parse "/content/jboss-seam-jpa.war/WEB-INF/jboss-web.xml"
at
org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:66)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:102)
... 4 more
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,3]
Message: Unexpected element 'class-loading' encountered
at
org.jboss.metadata.parser.util.MetaDataElementParser.unexpectedElement(MetaDataElementParser.java:109)
at
org.jboss.metadata.parser.jbossweb.JBossWebMetaDataParser.parse(JBossWebMetaDataParser.java:182)
at
org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:64)
... 5 more
^C21:12:05,801 INFO [org.jboss.as.logging] Restored bootstrap log handlers
21:12:05,818 INFO [org.jboss.as.connector.subsystems.datasources] Removed JDBC
Data-source [java:/H2DS]
21:12:05,833 INFO [org.jboss.as.server.deployment] Stopped deployment jboss-seam-jpa.war
in 52ms
21:12:05,832 INFO [com.arjuna.ats.jbossatx] ARJUNA-32018 Destroying
TransactionManagerService
21:12:05,834 INFO [com.arjuna.ats.jbossatx] ARJUNA-32014 Stopping transaction recovery
manager
21:12:05,845 INFO [org.hornetq.core.server.impl.HornetQServerImpl] HornetQ Server version
2.1.2.Final (Colmeia, 120) stopped
{code}
The above was last line of shutdown and it didn't return to terminal prompt.
I have tried also
{{./jboss-admin.sh --connect command=:shutdown}}
but it logs only:
{code}
Connected to localhost:9999
Communication error: Connection refused
Closed connection to localhost:9999
{code}
I have to kill manually AS 7 process by kill -9 <procid>
I also tried to start new standalone instance and tried to stop by {{./jboss-admin.sh
--connect command=:shutdown}} after failed deployment.
Both terminals hang up and didn't shutdown.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:14 p.m.
New subject: [JBoss JIRA] Commented: (AS7-961) AS 7 standalone instance doesn't shutdown
[
https://issues.jboss.org/browse/AS7-961?page=com.atlassian.jira.plugin.sy...
]
David Lloyd commented on AS7-961:
---------------------------------
If you can reproduce this problem - while the server is "hung" can you open up
jconsole, go to the jboss.msc mbean and get a service dump?
AS 7 standalone instance doesn't shutdown
-----------------------------------------
Key: AS7-961
URL: https://issues.jboss.org/browse/AS7-961
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.0.0.Beta3
Environment: Ubuntu 11.04,
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode)
Reporter: Marek Novotny
After failed deployment server standalone instance doesn't shutdown.
I have pushed CTRL+C and it tried to shutdown:
{code}
21:11:24,194 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread
1-1) HornetQ Server version 2.1.2.Final (Colmeia, 120) started
21:11:25,026 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed
to start service jboss.deployment.unit."jboss-seam-jpa.war".PARSE:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."jboss-seam-jpa.war".PARSE: Failed to process phase PARSE
of deployment "jboss-seam-jpa.war"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:108)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to
parse "/content/jboss-seam-jpa.war/WEB-INF/jboss-web.xml"
at
org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:66)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:102)
... 4 more
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,3]
Message: Unexpected element 'class-loading' encountered
at
org.jboss.metadata.parser.util.MetaDataElementParser.unexpectedElement(MetaDataElementParser.java:109)
at
org.jboss.metadata.parser.jbossweb.JBossWebMetaDataParser.parse(JBossWebMetaDataParser.java:182)
at
org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:64)
... 5 more
^C21:12:05,801 INFO [org.jboss.as.logging] Restored bootstrap log handlers
21:12:05,818 INFO [org.jboss.as.connector.subsystems.datasources] Removed JDBC
Data-source [java:/H2DS]
21:12:05,833 INFO [org.jboss.as.server.deployment] Stopped deployment jboss-seam-jpa.war
in 52ms
21:12:05,832 INFO [com.arjuna.ats.jbossatx] ARJUNA-32018 Destroying
TransactionManagerService
21:12:05,834 INFO [com.arjuna.ats.jbossatx] ARJUNA-32014 Stopping transaction recovery
manager
21:12:05,845 INFO [org.hornetq.core.server.impl.HornetQServerImpl] HornetQ Server
version 2.1.2.Final (Colmeia, 120) stopped
{code}
The above was last line of shutdown and it didn't return to terminal prompt.
I have tried also
{{./jboss-admin.sh --connect command=:shutdown}}
but it logs only:
{code}
Connected to localhost:9999
Communication error: Connection refused
Closed connection to localhost:9999
{code}
I have to kill manually AS 7 process by kill -9 <procid>
I also tried to start new standalone instance and tried to stop by {{./jboss-admin.sh
--connect command=:shutdown}} after failed deployment.
Both terminals hang up and didn't shutdown.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:53 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (AS7-961) AS 7 standalone instance doesn't shutdown
[
https://issues.jboss.org/browse/AS7-961?page=com.atlassian.jira.plugin.sy...
]
Marek Novotny edited comment on AS7-961 at 6/7/11 4:52 PM:
-----------------------------------------------------------
Here it is with another application for this time failed EAR deployment:
{code}
22:49:24,164 INFO [stdout] Services for jboss-as:
22:49:24,167 INFO [stdout] Service "jboss.as" (class
org.jboss.as.server.ApplicationServerService) mode REMOVE state UP (STOP_REQUESTED)
22:49:24,167 INFO [stdout] Service "jboss.as.external-module-service" (class
org.jboss.as.server.moduleservice.ExternalModuleService) mode REMOVE state UP
(STOP_REQUESTED) (parent: jboss.as)
22:49:24,167 INFO [stdout] Service "jboss.as.server-controller" (class
org.jboss.as.server.ServerControllerService) mode REMOVE state UP (STOP_REQUESTED)
(parent: jboss.as) (dependencies: jboss.as.external-module-service,
jboss.as.service-module-loader, jboss.deployment-repository)
22:49:24,167 INFO [stdout] Service "jboss.as.service-module-loader" (class
org.jboss.as.server.moduleservice.ServiceModuleLoader) mode REMOVE state UP
(STOP_REQUESTED) (parent: jboss.as)
22:49:24,168 INFO [stdout] Service "jboss.deployment.chains" (class
org.jboss.as.server.deployment.DeployerChainsService) mode REMOVE state UP
(STOP_REQUESTED) (parent: jboss.as.server-controller)
22:49:24,168 INFO [stdout] Service
"jboss.deployment.unit."seam-booking.ear"" (class
org.jboss.as.server.deployment.RootDeploymentUnitService) mode REMOVE state UP
(STOP_REQUESTED) (parent: jboss.as.server-controller) (dependencies:
jboss.deployment.chains, jboss.deployment-repository)
22:49:24,168 INFO [stdout] Service
"jboss.deployment.unit."seam-booking.ear".STRUCTURE" (class
org.jboss.as.server.deployment.DeploymentUnitPhaseService) mode REMOVE state STARTING
(parent: jboss.deployment.unit."seam-booking.ear") (dependencies:
jboss.deployment.chains)
22:49:24,168 INFO [stdout] Service "jboss.deployment-repository" (class
org.jboss.as.server.deployment.impl.ServerDeploymentRepositoryImpl) mode REMOVE state UP
(STOP_REQUESTED) (parent: jboss.as)
22:49:24,169 INFO [stdout] 8 services displayed
{code}
was (Author: manaRH):
Here it is with another deployed application for this time failed EAR deployment:
{code}
22:49:24,164 INFO [stdout] Services for jboss-as:
22:49:24,167 INFO [stdout] Service "jboss.as" (class
org.jboss.as.server.ApplicationServerService) mode REMOVE state UP (STOP_REQUESTED)
22:49:24,167 INFO [stdout] Service "jboss.as.external-module-service" (class
org.jboss.as.server.moduleservice.ExternalModuleService) mode REMOVE state UP
(STOP_REQUESTED) (parent: jboss.as)
22:49:24,167 INFO [stdout] Service "jboss.as.server-controller" (class
org.jboss.as.server.ServerControllerService) mode REMOVE state UP (STOP_REQUESTED)
(parent: jboss.as) (dependencies: jboss.as.external-module-service,
jboss.as.service-module-loader, jboss.deployment-repository)
22:49:24,167 INFO [stdout] Service "jboss.as.service-module-loader" (class
org.jboss.as.server.moduleservice.ServiceModuleLoader) mode REMOVE state UP
(STOP_REQUESTED) (parent: jboss.as)
22:49:24,168 INFO [stdout] Service "jboss.deployment.chains" (class
org.jboss.as.server.deployment.DeployerChainsService) mode REMOVE state UP
(STOP_REQUESTED) (parent: jboss.as.server-controller)
22:49:24,168 INFO [stdout] Service
"jboss.deployment.unit."seam-booking.ear"" (class
org.jboss.as.server.deployment.RootDeploymentUnitService) mode REMOVE state UP
(STOP_REQUESTED) (parent: jboss.as.server-controller) (dependencies:
jboss.deployment.chains, jboss.deployment-repository)
22:49:24,168 INFO [stdout] Service
"jboss.deployment.unit."seam-booking.ear".STRUCTURE" (class
org.jboss.as.server.deployment.DeploymentUnitPhaseService) mode REMOVE state STARTING
(parent: jboss.deployment.unit."seam-booking.ear") (dependencies:
jboss.deployment.chains)
22:49:24,168 INFO [stdout] Service "jboss.deployment-repository" (class
org.jboss.as.server.deployment.impl.ServerDeploymentRepositoryImpl) mode REMOVE state UP
(STOP_REQUESTED) (parent: jboss.as)
22:49:24,169 INFO [stdout] 8 services displayed
{code}
AS 7 standalone instance doesn't shutdown
-----------------------------------------
Key: AS7-961
URL: https://issues.jboss.org/browse/AS7-961
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.0.0.Beta3
Environment: Ubuntu 11.04,
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode)
Reporter: Marek Novotny
After failed deployment server standalone instance doesn't shutdown.
I have pushed CTRL+C and it tried to shutdown:
{code}
21:11:24,194 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread
1-1) HornetQ Server version 2.1.2.Final (Colmeia, 120) started
21:11:25,026 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed
to start service jboss.deployment.unit."jboss-seam-jpa.war".PARSE:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."jboss-seam-jpa.war".PARSE: Failed to process phase PARSE
of deployment "jboss-seam-jpa.war"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:108)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to
parse "/content/jboss-seam-jpa.war/WEB-INF/jboss-web.xml"
at
org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:66)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:102)
... 4 more
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,3]
Message: Unexpected element 'class-loading' encountered
at
org.jboss.metadata.parser.util.MetaDataElementParser.unexpectedElement(MetaDataElementParser.java:109)
at
org.jboss.metadata.parser.jbossweb.JBossWebMetaDataParser.parse(JBossWebMetaDataParser.java:182)
at
org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:64)
... 5 more
^C21:12:05,801 INFO [org.jboss.as.logging] Restored bootstrap log handlers
21:12:05,818 INFO [org.jboss.as.connector.subsystems.datasources] Removed JDBC
Data-source [java:/H2DS]
21:12:05,833 INFO [org.jboss.as.server.deployment] Stopped deployment jboss-seam-jpa.war
in 52ms
21:12:05,832 INFO [com.arjuna.ats.jbossatx] ARJUNA-32018 Destroying
TransactionManagerService
21:12:05,834 INFO [com.arjuna.ats.jbossatx] ARJUNA-32014 Stopping transaction recovery
manager
21:12:05,845 INFO [org.hornetq.core.server.impl.HornetQServerImpl] HornetQ Server
version 2.1.2.Final (Colmeia, 120) stopped
{code}
The above was last line of shutdown and it didn't return to terminal prompt.
I have tried also
{{./jboss-admin.sh --connect command=:shutdown}}
but it logs only:
{code}
Connected to localhost:9999
Communication error: Connection refused
Closed connection to localhost:9999
{code}
I have to kill manually AS 7 process by kill -9 <procid>
I also tried to start new standalone instance and tried to stop by {{./jboss-admin.sh
--connect command=:shutdown}} after failed deployment.
Both terminals hang up and didn't shutdown.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:53 p.m.
New subject: [JBoss JIRA] Commented: (AS7-961) AS 7 standalone instance doesn't shutdown
[
https://issues.jboss.org/browse/AS7-961?page=com.atlassian.jira.plugin.sy...
]
Marek Novotny commented on AS7-961:
-----------------------------------
Here it is with another deployed application for this time failed EAR deployment:
{code}
22:49:24,164 INFO [stdout] Services for jboss-as:
22:49:24,167 INFO [stdout] Service "jboss.as" (class
org.jboss.as.server.ApplicationServerService) mode REMOVE state UP (STOP_REQUESTED)
22:49:24,167 INFO [stdout] Service "jboss.as.external-module-service" (class
org.jboss.as.server.moduleservice.ExternalModuleService) mode REMOVE state UP
(STOP_REQUESTED) (parent: jboss.as)
22:49:24,167 INFO [stdout] Service "jboss.as.server-controller" (class
org.jboss.as.server.ServerControllerService) mode REMOVE state UP (STOP_REQUESTED)
(parent: jboss.as) (dependencies: jboss.as.external-module-service,
jboss.as.service-module-loader, jboss.deployment-repository)
22:49:24,167 INFO [stdout] Service "jboss.as.service-module-loader" (class
org.jboss.as.server.moduleservice.ServiceModuleLoader) mode REMOVE state UP
(STOP_REQUESTED) (parent: jboss.as)
22:49:24,168 INFO [stdout] Service "jboss.deployment.chains" (class
org.jboss.as.server.deployment.DeployerChainsService) mode REMOVE state UP
(STOP_REQUESTED) (parent: jboss.as.server-controller)
22:49:24,168 INFO [stdout] Service
"jboss.deployment.unit."seam-booking.ear"" (class
org.jboss.as.server.deployment.RootDeploymentUnitService) mode REMOVE state UP
(STOP_REQUESTED) (parent: jboss.as.server-controller) (dependencies:
jboss.deployment.chains, jboss.deployment-repository)
22:49:24,168 INFO [stdout] Service
"jboss.deployment.unit."seam-booking.ear".STRUCTURE" (class
org.jboss.as.server.deployment.DeploymentUnitPhaseService) mode REMOVE state STARTING
(parent: jboss.deployment.unit."seam-booking.ear") (dependencies:
jboss.deployment.chains)
22:49:24,168 INFO [stdout] Service "jboss.deployment-repository" (class
org.jboss.as.server.deployment.impl.ServerDeploymentRepositoryImpl) mode REMOVE state UP
(STOP_REQUESTED) (parent: jboss.as)
22:49:24,169 INFO [stdout] 8 services displayed
{code}
AS 7 standalone instance doesn't shutdown
-----------------------------------------
Key: AS7-961
URL: https://issues.jboss.org/browse/AS7-961
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.0.0.Beta3
Environment: Ubuntu 11.04,
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode)
Reporter: Marek Novotny
After failed deployment server standalone instance doesn't shutdown.
I have pushed CTRL+C and it tried to shutdown:
{code}
21:11:24,194 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread
1-1) HornetQ Server version 2.1.2.Final (Colmeia, 120) started
21:11:25,026 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed
to start service jboss.deployment.unit."jboss-seam-jpa.war".PARSE:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."jboss-seam-jpa.war".PARSE: Failed to process phase PARSE
of deployment "jboss-seam-jpa.war"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:108)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to
parse "/content/jboss-seam-jpa.war/WEB-INF/jboss-web.xml"
at
org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:66)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:102)
... 4 more
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,3]
Message: Unexpected element 'class-loading' encountered
at
org.jboss.metadata.parser.util.MetaDataElementParser.unexpectedElement(MetaDataElementParser.java:109)
at
org.jboss.metadata.parser.jbossweb.JBossWebMetaDataParser.parse(JBossWebMetaDataParser.java:182)
at
org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:64)
... 5 more
^C21:12:05,801 INFO [org.jboss.as.logging] Restored bootstrap log handlers
21:12:05,818 INFO [org.jboss.as.connector.subsystems.datasources] Removed JDBC
Data-source [java:/H2DS]
21:12:05,833 INFO [org.jboss.as.server.deployment] Stopped deployment jboss-seam-jpa.war
in 52ms
21:12:05,832 INFO [com.arjuna.ats.jbossatx] ARJUNA-32018 Destroying
TransactionManagerService
21:12:05,834 INFO [com.arjuna.ats.jbossatx] ARJUNA-32014 Stopping transaction recovery
manager
21:12:05,845 INFO [org.hornetq.core.server.impl.HornetQServerImpl] HornetQ Server
version 2.1.2.Final (Colmeia, 120) stopped
{code}
The above was last line of shutdown and it didn't return to terminal prompt.
I have tried also
{{./jboss-admin.sh --connect command=:shutdown}}
but it logs only:
{code}
Connected to localhost:9999
Communication error: Connection refused
Closed connection to localhost:9999
{code}
I have to kill manually AS 7 process by kill -9 <procid>
I also tried to start new standalone instance and tried to stop by {{./jboss-admin.sh
--connect command=:shutdown}} after failed deployment.
Both terminals hang up and didn't shutdown.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:07 p.m.
New subject: [JBoss JIRA] Commented: (AS7-961) AS 7 standalone instance doesn't shutdown
[
https://issues.jboss.org/browse/AS7-961?page=com.atlassian.jira.plugin.sy...
]
David Lloyd commented on AS7-961:
---------------------------------
Marke, we really need to be able to match the logs up with the service dump - having logs
from one run and a service dump from another are just going to cause confusion. Can you
attach a server log and service dump from the same run?
AS 7 standalone instance doesn't shutdown
-----------------------------------------
Key: AS7-961
URL: https://issues.jboss.org/browse/AS7-961
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.0.0.Beta3
Environment: Ubuntu 11.04,
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode)
Reporter: Marek Novotny
After failed deployment server standalone instance doesn't shutdown.
I have pushed CTRL+C and it tried to shutdown:
{code}
21:11:24,194 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread
1-1) HornetQ Server version 2.1.2.Final (Colmeia, 120) started
21:11:25,026 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed
to start service jboss.deployment.unit."jboss-seam-jpa.war".PARSE:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."jboss-seam-jpa.war".PARSE: Failed to process phase PARSE
of deployment "jboss-seam-jpa.war"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:108)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to
parse "/content/jboss-seam-jpa.war/WEB-INF/jboss-web.xml"
at
org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:66)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:102)
... 4 more
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,3]
Message: Unexpected element 'class-loading' encountered
at
org.jboss.metadata.parser.util.MetaDataElementParser.unexpectedElement(MetaDataElementParser.java:109)
at
org.jboss.metadata.parser.jbossweb.JBossWebMetaDataParser.parse(JBossWebMetaDataParser.java:182)
at
org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:64)
... 5 more
^C21:12:05,801 INFO [org.jboss.as.logging] Restored bootstrap log handlers
21:12:05,818 INFO [org.jboss.as.connector.subsystems.datasources] Removed JDBC
Data-source [java:/H2DS]
21:12:05,833 INFO [org.jboss.as.server.deployment] Stopped deployment jboss-seam-jpa.war
in 52ms
21:12:05,832 INFO [com.arjuna.ats.jbossatx] ARJUNA-32018 Destroying
TransactionManagerService
21:12:05,834 INFO [com.arjuna.ats.jbossatx] ARJUNA-32014 Stopping transaction recovery
manager
21:12:05,845 INFO [org.hornetq.core.server.impl.HornetQServerImpl] HornetQ Server
version 2.1.2.Final (Colmeia, 120) stopped
{code}
The above was last line of shutdown and it didn't return to terminal prompt.
I have tried also
{{./jboss-admin.sh --connect command=:shutdown}}
but it logs only:
{code}
Connected to localhost:9999
Communication error: Connection refused
Closed connection to localhost:9999
{code}
I have to kill manually AS 7 process by kill -9 <procid>
I also tried to start new standalone instance and tried to stop by {{./jboss-admin.sh
--connect command=:shutdown}} after failed deployment.
Both terminals hang up and didn't shutdown.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:24 p.m.
New subject: [JBoss JIRA] (AS7-961) AS 7 standalone instance doesn't shutdown
[
https://issues.jboss.org/browse/AS7-961?page=com.atlassian.jira.plugin.sy...
]
Kabir Khan closed AS7-961.
--------------------------
Resolution: Out of Date
AS 7 standalone instance doesn't shutdown
-----------------------------------------
Key: AS7-961
URL: https://issues.jboss.org/browse/AS7-961
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.0.0.Beta3
Environment: Ubuntu 11.04,
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode)
Reporter: Marek Novotny
After failed deployment server standalone instance doesn't shutdown.
I have pushed CTRL+C and it tried to shutdown:
{code}
21:11:24,194 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread
1-1) HornetQ Server version 2.1.2.Final (Colmeia, 120) started
21:11:25,026 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed
to start service jboss.deployment.unit."jboss-seam-jpa.war".PARSE:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."jboss-seam-jpa.war".PARSE: Failed to process phase PARSE
of deployment "jboss-seam-jpa.war"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:108)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to
parse "/content/jboss-seam-jpa.war/WEB-INF/jboss-web.xml"
at
org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:66)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:102)
... 4 more
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,3]
Message: Unexpected element 'class-loading' encountered
at
org.jboss.metadata.parser.util.MetaDataElementParser.unexpectedElement(MetaDataElementParser.java:109)
at
org.jboss.metadata.parser.jbossweb.JBossWebMetaDataParser.parse(JBossWebMetaDataParser.java:182)
at
org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:64)
... 5 more
^C21:12:05,801 INFO [org.jboss.as.logging] Restored bootstrap log handlers
21:12:05,818 INFO [org.jboss.as.connector.subsystems.datasources] Removed JDBC
Data-source [java:/H2DS]
21:12:05,833 INFO [org.jboss.as.server.deployment] Stopped deployment jboss-seam-jpa.war
in 52ms
21:12:05,832 INFO [com.arjuna.ats.jbossatx] ARJUNA-32018 Destroying
TransactionManagerService
21:12:05,834 INFO [com.arjuna.ats.jbossatx] ARJUNA-32014 Stopping transaction recovery
manager
21:12:05,845 INFO [org.hornetq.core.server.impl.HornetQServerImpl] HornetQ Server
version 2.1.2.Final (Colmeia, 120) stopped
{code}
The above was last line of shutdown and it didn't return to terminal prompt.
I have tried also
{{./jboss-admin.sh --connect command=:shutdown}}
but it logs only:
{code}
Connected to localhost:9999
Communication error: Connection refused
Closed connection to localhost:9999
{code}
I have to kill manually AS 7 process by kill -9 <procid>
I also tried to start new standalone instance and tried to stop by {{./jboss-admin.sh
--connect command=:shutdown}} after failed deployment.
Both terminals hang up and didn't shutdown.
--
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
4734
days inactive
4862
days old
5 comments
3 participants
participants (3)
-
David Lloyd (JIRA) -
Kabir Khan (Closed) (JIRA)
-
Marek Novotny (JIRA)