JBOSS AS 7.1 issue on deployment-scanner
Few days back on faced an issue on JBOSS AS7.1 startup - as seen in the log below the "deployment-scanner" was not activated in JBOSS resulting in my apps not deployed.
AS log when issue was reported:
06:30:05,252 INFO [configadmin] JBAS016200: Activating ConfigAdmin Subsystem
06:30:05,256 INFO [infinispan] JBAS010280: Activating Infinispan subsystem.
06:30:05,260 INFO [jacorb] JBAS016300: Activating JacORB Subsystem
06:30:05,284 INFO [security] JBAS013101: Activating Security Subsystem
06:30:05,286 INFO [naming] JBAS011800: Activating Naming Subsystem
06:30:05,286 INFO [webservices] JBAS015537: Activating WebServices Extension
06:30:05,286 INFO [osgi] JBAS011940: Activating OSGi Subsystem
06:30:05,304 INFO [security] JBAS013100: Current PicketBox version=4.0.7.Final
06:30:05,325 INFO [connector] JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
06:30:05,391 INFO [naming] JBAS011802: Starting Naming Service
06:30:05,405 INFO [extension] JBAS015400: Bound mail session [java:jboss/mail/Default]
06:30:05,437 INFO [jaxr] JBAS014000: Started JAXR subsystem, binding JAXR connection factory into JNDI as: java:jboss/jaxr/ConnectionFactory
06:30:05,524 INFO [datasources] JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
06:30:05,547 INFO [AbstractServerConfig] JBoss Web Services - Stack CXF Server 4.0.2.GA
06:30:05,560 INFO [datasources] JBAS010404: Deploying non-JDBC-compliant driver class com.sybase.jdbc3.jdbc.SybDriver (version 6.0)
06:30:05,620 INFO [Http11Protocol] Coyote HTTP/1.1､・http-rb-aws-vm-10.11.12.13-18580 ､ﾇｵｯﾆｰ､ｷ､ﾞ､ｹ
06:30:05,641 WARN [messaging] JBAS011600: AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal
06:30:05,750 ｾ・ [HornetQServerImpl] live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/home/rb/apps/jboss-as-7.1.1.Final/standalone/data/messagingjournal,bindingsDirectory=/home/rb/apps/jboss-as-7.1.1.Final/standalone/data/messagingbindings,largeMessagesDirectory=/home/rb/apps/jboss-as-7.1.1.Final/standalone/data/messaginglargemessages,pagingDirectory=/home/rb/apps/jboss-as-7.1.1.Final/standalone/data/messagingpaging)
06:30:05,759 ｾ・ [HornetQServerImpl] Waiting to obtain live lock
06:30:05,780 WARN [codeset] Warning - unknown codeset (EUC_JP_Solaris) - defaulting to ISO-8859-1
06:30:05,823 INFO [JournalStorageManager] Using NIO Journal
06:30:05,844 INFO [jacorb] JBAS016330: CORBA ORB Service started
06:30:05,943 INFO [FileLockNodeManager] Waiting to obtain live lock
06:30:05,944 INFO [FileLockNodeManager] Live Server Obtained live lock
06:30:06,006 INFO [jacorb] JBAS016328: CORBA Naming Service started
AS log - A clean log
06:30:04,839 INFO [configadmin] JBAS016200: Activating ConfigAdmin Subsystem
06:30:04,841 INFO [infinispan] JBAS010280: Activating Infinispan subsystem.
06:30:04,846 INFO [jacorb] JBAS016300: Activating JacORB Subsystem
06:30:04,860 INFO [security] JBAS013101: Activating Security Subsystem
06:30:04,865 INFO [osgi] JBAS011940: Activating OSGi Subsystem
06:30:04,867 INFO [naming] JBAS011800: Activating Naming Subsystem
06:30:04,869 INFO [webservices] JBAS015537: Activating WebServices Extension
06:30:04,894 INFO [security] JBAS013100: Current PicketBox version=4.0.7.Final
06:30:04,909 INFO [connector] JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
06:30:04,974 INFO [naming] JBAS011802: Starting Naming Service
06:30:04,987 INFO [extension] JBAS015400: Bound mail session [java:jboss/mail/Default]
06:30:05,063 INFO [jaxr] JBAS014000: Started JAXR subsystem, binding JAXR connection factory into JNDI as: java:jboss/jaxr/ConnectionFactory
06:30:05,102 INFO [datasources] JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
06:30:05,112 INFO [AbstractServerConfig] JBoss Web Services - Stack CXF Server 4.0.2.GA
06:30:05,137 INFO [datasources] JBAS010404: Deploying non-JDBC-compliant driver class com.sybase.jdbc3.jdbc.SybDriver (version 6.0)
06:30:05,193 INFO [Http11Protocol] Coyote HTTP/1.1､・http-rb-aws-vm-10.11.12.13-18580 ､ﾇｵｯﾆｰ､ｷ､ﾞ､ｹ
06:30:05,218 WARN [messaging] JBAS011600: AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal
06:30:05,311 ｾ・ [HornetQServerImpl] live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/home/rb/apps/jboss-as-7.1.1.Final/standalone/data/messagingjournal,bindingsDirectory=/home/rb/apps/jboss-as-7.1.1.Final/standalone/data/messagingbindings,largeMessagesDirectory=/home/rb/apps/jboss-as-7.1.1.Final/standalone/data/messaginglargemessages,pagingDirectory=/home/rb/apps/jboss-as-7.1.1.Final/standalone/data/messagingpaging)
06:30:05,319 ｾ・ [HornetQServerImpl] Waiting to obtain live lock
06:30:05,321 WARN [codeset] Warning - unknown codeset (EUC_JP_Solaris) - defaulting to ISO-8859-1
06:30:05,381 INFO [JournalStorageManager] Using NIO Journal
06:30:05,391 INFO [jacorb] JBAS016330: CORBA ORB Service started
06:30:05,475 INFO [scanner] JBAS015012: Started FileSystemDeploymentService for directory /home/rb/apps/jboss-as-7.1.1.Final/standalone/deployments
06:30:05,476 INFO [remoting] JBAS017100: Listening on rb-aws-vm/10.11.12.13:20499
06:30:05,476 INFO [remoting] JBAS017100: Listening on rb-aws-vm/10.11.12.13:14947
06:30:05,496 INFO [FileLockNodeManager] Waiting to obtain live lock
06:30:05,497 INFO [FileLockNodeManager] Live Server Obtained live lock
As seen in the logs above "scanner" was not activated which impacted my apps EAR deployment .
JBOSS process was force killed and started again - was successful. This is one-off event - however would like to know under what condition "deployment-scanner" activation can be skipped by JBOSS.