[
https://issues.jboss.org/browse/AS7-2106?page=com.atlassian.jira.plugin.s...
]
David Lloyd commented on AS7-2106:
----------------------------------
If there is, it's something you've made up. In AS7, modules don't
"execute", therefore they cannot be asynchronous.
If I have an async module extension that blocks then a CTRL-C to stop
the AS7 hangs the JVM and never exits
-----------------------------------------------------------------------------------------------------------
Key: AS7-2106
URL:
https://issues.jboss.org/browse/AS7-2106
Project: Application Server 7
Issue Type: Bug
Components: Modules
Environment: 7.0.2 GA FINAL
Reporter: Dan Sirbu
Assignee: David Lloyd
If I have a module extension that somehow blocks the startup a CTRL-C will not stop the
JVM. One needs to explicitely do a kill -KILL <jvm_pid>. kill -TERM would not work.
Let me know how this should be handled. I did see some ME's using some Runtime
environment to detect a shutdown but not familiar with it ....
^C03:48:18,951 INFO [org.jboss.as.logging] Restored bootstrap log handlers
03:48:18,977 INFO [org.jboss.as.connector.subsystems.datasources] Unbound data source
[java:jboss/datasources/ExampleDS]
03:48:18,991 INFO [com.arjuna.ats.jbossatx] ARJUNA32018: Destroying
TransactionManagerService
03:48:18,991 INFO [com.arjuna.ats.jbossatx] ARJUNA32014: Stopping transaction recovery
manager
./oam.sh: line 144: 24537 Killed "/opt/java/bin/java" -server
-Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true
-Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
-Djava.rmi.server.hostname=SC-1 -Djboss.server.name=oam_instance_SC-1
-Djboss.partition.name=oam -DINTERNAL_IP=192.168.105.1 -DLOCAL_IP=10.121.247.22
-XX:MaxPermSize=256m -XX:ParallelGCThreads=7 -Xmn128m -XX:MaxTenuringThreshold=8
-XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:LargePageSizeInBytes=2m -client -Xms3000m
-XX:SurvivorRatio=8 -XX:+DisableExplicitGC -XX:PermSize=64m -Xmx3000m -Xss256k
-XX:CMSInitiatingOccupancyFraction=1
-Djboss.server.base.dir=/home/jboss-as-web-7.0.2.Final/oam_instance_SC-1
-Djboss.server.config.dir=/home/jboss-as-web-7.0.2.Final/oam_instance_SC-1/configuration
-Dorg.jboss.boot.log.file=/home/jboss-as-web-7.0.2.Final/oam/log/boot.log
-Dlogging.configuration=file:/home/jboss-as-web-7.0.2.Final/oam/configuration/logging.properties
-Djava.library.path=/opt/JAVACAF/lib
-Djboss.server.lib.url=/home/jboss-as-web-7.0.2.Final/oam/lib
-Djboss.messaging.ServerPeerID=1
-Djboss.server.base.dir.host=/home/jboss-as-web-7.0.2.Final/oam/deployments_SC-1
-Djboss.modules.system.pkgs=org.jboss.byteman -Xdebug
-Xrunjdwp:transport=dt_socket,server=y,address=10.121.247.22:8000 -Djavaplugin.trace=true
-jar "/home/jboss-as-web-7.0.2.Final/jboss-modules.jar" -mp
"/home/jboss-as-web-7.0.2.Final/modules" -logmodule org.jboss.logmanager
-jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone
-Djboss.home.dir="/home/jboss-as-web-7.0.2.Final"
--
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