torquebox-lite 0.1.0

data/jboss/standalone/deployments/README.txt

@@ -0,0 +1,190 @@
+The standalone/deployments directory in the JBoss Application Server
+distribution is the location end users can place their deployment content
+(e.g. war, ear, jar, sar files) to have it automatically deployed into the server
+runtime.
+
+Users, particularly those running production systems, are encouraged to use the
+JBoss AS management APIs to upload and deploy deployment content instead of
+relying on the deployment scanner subsystem that periodically scans this
+directory.  See the JBoss AS documentation for details.
+
+DEPLOYMENT MODES
+
+The filesystem deployment scanner in AS 7 and later works differently from
+previous JBoss AS releases. The scanner can operate in one of two different
+modes, depending on whether it will directly monitor the deployment content
+in order to decide to deploy (or redeploy) it.
+
+1) Auto-deploy mode: The scanner will directly monitor the deployment content,
+automatically deploying new content and redeploying content whose timestamp
+has changed. This is similiar to the behavior of previous AS releases, although
+there are differences:
+
+a) A change in any file in an exploded deployment triggers redeploy. Because
+EE 6 applications do not require deployment descriptors, there is no attempt
+to monitor deployment descriptors and only redeploy when a deployment
+descriptor changes.
+b) The scanner will place marker files in this directory as an indication of
+the status of its attempts to deploy or undeploy content. These are detailed
+below.
+
+2) Manual deploy mode: The scanner will not attempt to directly monitor the
+deployment content and decide if or when the end user wishes the content to
+be deployed or undeployed. Instead, the scanner relies on a system of marker
+files, with the user's addition or removal of a marker file serving as a sort
+of command telling the scanner to deploy, undeploy or redeploy content.
+
+
+Auto-deploy mode and manual deploy mode can be independently configured for
+zipped deployment content and exploded deployment content. This is done
+via the "auto-deploy" attributes on the deployment-scanner element in the
+standalone.xml configuration file:
+
+<deployment-scanner scan-interval="5000" relative-to="jboss.server.base.dir"
+    path="deployments" auto-deploy-zipped="true" auto-deploy-exploded="false"/>
+
+By default, auto-deploy of zipped content is enabled, and auto-deploy of
+exploded content is disabled. Manual deploy mode is strongly recommended for
+exploded content, as exploded content is inherently vulnerable to the scanner
+trying to auto-deploy partially copied content. Manual deploy mode also allows
+deployment resources (e.g. html and css files) to be replaced without
+triggering a redeploy of the application.
+
+
+MARKER FILES
+
+The marker files always have the same name as the deployment content to which
+they relate, but with an additional file suffix appended. For example, the
+marker file to indicate the example.war file should be deployed is named
+example.war.dodeploy. Different marker file suffixes have different meanings.
+
+The relevant marker file types are:
+
+.dodeploy      -- Placed by the user to indicate that the given content should
+                  be deployed into the runtime (or redeployed if already
+                  deployed in the runtime.)
+
+.skipdeploy    -- Disables auto-deploy of the content for as long as the file
+                  is present. Most useful for allowing updates to exploded
+                  content without having the scanner initiate redeploy in the
+                  middle of the update. Can be used with zipped content as
+                  well, although the scanner will detect in-progress changes
+                  to zipped content and wait until changes are complete.
+
+.isdeploying   -- Placed by the deployment scanner service to indicate that it
+                  has noticed a .dodeploy file or new or updated auto-deploy
+                  mode content and is in the process of deploying the content.
+                  This marker file will be deleted when the deployment process
+                  completes.
+
+.deployed      -- Placed by the deployment scanner service to indicate that the
+                  given content has been deployed into the runtime. If an end
+                  user deletes this file, the content will be undeployed.
+
+.failed        -- Placed by the deployment scanner service to indicate that the
+                  given content failed to deploy into the runtime. The content
+                  of the file will include some information about the cause of
+                  the failure. Note that with auto-deploy mode, removing this
+                  file will make the deployment eligible for deployment again.
+
+.isundeploying -- Placed by the deployment scanner service to indicate that it
+                  has noticed a .deployed file has been deleted and the
+                  content is being undeployed. This marker file will be deleted
+                  when the undeployment process completes.
+
+.undeployed    -- Placed by the deployment scanner service to indicate that the
+                  given content has been undeployed from the runtime. If an end
+                  user deletes this file, it has no impact.
+
+.pending       -- Placed by the deployment scanner service to indicate that it
+                  has noticed the need to deploy content but has not yet
+                  instructed the server to deploy it. This file is created if
+                  the scanner detects that some auto-deploy content is still in
+                  the process of being copied or if there is some problem that
+                  prevents auto-deployment. The scanner will not instruct the
+                  server to deploy or undeploy any content (not just the
+                  directly affected content) as long as this condition holds.
+
+Basic workflows:
+
+All examples assume variable $AS points to the root of the JBoss AS distribution.
+Windows users: the examples below use Unix shell commands; see the "Windows
+Notes" below.
+
+A) Add new zipped content and deploy it:
+
+1. cp target/example.war $AS/standalone/deployments
+2. (Manual mode only) touch $AS/standalone/deployments/example.war.dodeploy
+
+B) Add new unzipped content and deploy it:
+
+1. cp -r target/example.war/ $AS/standalone/deployments
+2. (Manual mode only) touch $AS/standalone/deployments/example.war.dodeploy
+
+C) Undeploy currently deployed content:
+
+1. rm $AS/standalone/deployments/example.war.deployed
+
+D) Auto-deploy mode only: Undeploy currently deployed content:
+
+1. rm $AS/standalone/deployments/example.war
+
+Note that this approach is not recommended with unzipped content as the server
+maintains no other copy of unzipped content and deleting it without first
+triggering an undeploy temporarily results in a live application with
+potentially critical resources no longer available. For unzipped content use
+the 'rm $AS/standalone/deployments/example.war.deployed' approach.
+
+E) Replace currently deployed zipped content with a new version and deploy it:
+
+1. cp target/example.war/ $AS/standalone/deployments
+2. (Manual mode only) touch $AS/standalone/deployments/example.war.dodeploy
+
+F) Manual mode only: Replace currently deployed unzipped content with a new
+   version and deploy it:
+
+1. rm $AS/standalone/deployments/example.war.deployed
+2. wait for $AS/standalone/deployments/example.war.undeployed file to appear
+3. cp -r target/example.war/ $AS/standalone/deployments
+4. touch $AS/standalone/deployments/example.war.dodeploy
+
+G) Auto-deploy mode only: Replace currently deployed unzipped content with a
+   new version and deploy it:
+
+1. touch $AS/standalone/deployments/example.war.skipdeploy
+2. cp -r target/example.war/ $AS/standalone/deployments
+3. rm $AS/standalone/deployments/example.war.skipdeploy
+
+H) Manual mode only: Live replace portions of currently deployed unzipped
+   content without redeploying:
+
+1. cp -r target/example.war/foo.html $AS/standalone/deployments/example.war
+
+I) Auto-deploy mode only: Live replace portions of currently deployed unzipped
+   content without redeploying:
+
+1. touch $AS/standalone/deployments/example.war.skipdeploy
+2. cp -r target/example.war/foo.html $AS/standalone/deployments/example.war
+
+J) Manual or auto-deploy mode: Redeploy currently deployed content (i.e. bounce
+   it with no content change):
+
+1. touch $AS/standalone/deployments/example.war.dodeploy
+
+K) Auto-deploy mode only: Redeploy currently deployed content (i.e. bounce
+   it with no content change):
+
+1. touch $AS/standalone/deployments/example.war
+
+
+Windows Notes:
+
+The above examples use Unix shell commands. Windows equivalents are:
+
+cp src dest --> xcopy /y src dest
+cp -r src dest --> xcopy /e /s /y src dest
+rm afile --> del afile
+touch afile --> echo>> afile
+
+Note that the behavior of 'touch' and 'echo' are different but the
+differences are not relevant to the usages in the examples above.

data/jboss/standalone/log/boot.log

@@ -0,0 +1,148 @@
+17:38:27,338 INFO  [org.jboss.modules] JBoss Modules version 1.1.2.GA
+17:38:27,623 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
+17:38:27,683 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.x.incremental.1 "Steropes" starting
+17:38:27,692 DEBUG [org.jboss.as.config] Configured system properties:
+	[Standalone] = 
+	awt.nativeDoubleBuffering = true
+	awt.toolkit = apple.awt.CToolkit
+	file.encoding = MacRoman
+	file.encoding.pkg = sun.io
+	file.separator = /
+	ftp.nonProxyHosts = local|*.local|169.254/16|*.169.254/16
+	gopherProxySet = false
+	http.nonProxyHosts = local|*.local|169.254/16|*.169.254/16
+	java.awt.graphicsenv = apple.awt.CGraphicsEnvironment
+	java.awt.headless = true
+	java.awt.printerjob = apple.awt.CPrinterJob
+	java.class.path = /Users/bbrowning/src/torquebox/build/assembly/target/stage/torquebox/jboss/jboss-modules.jar
+	java.class.version = 50.0
+	java.endorsed.dirs = /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/endorsed
+	java.ext.dirs = /Library/Java/Extensions:/System/Library/Java/Extensions:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/ext
+	java.home = /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
+	java.io.tmpdir = /var/folders/ak/ak4JdjHqGAq17hqpLCzISk+++TI/-Tmp-/
+	java.library.path = .:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java
+	java.net.preferIPv4Stack = true
+	java.runtime.name = Java(TM) SE Runtime Environment
+	java.runtime.version = 1.6.0_35-b10-428-10M3811
+	java.specification.name = Java Platform API Specification
+	java.specification.vendor = Sun Microsystems Inc.
+	java.specification.version = 1.6
+	java.util.logging.manager = org.jboss.logmanager.LogManager
+	java.vendor = Apple Inc.
+	java.vendor.url = http://www.apple.com/
+	java.vendor.url.bug = http://bugreport.apple.com/
+	java.version = 1.6.0_35
+	java.vm.info = mixed mode
+	java.vm.name = Java HotSpot(TM) Client VM
+	java.vm.specification.name = Java Virtual Machine Specification
+	java.vm.specification.vendor = Sun Microsystems Inc.
+	java.vm.specification.version = 1.0
+	java.vm.vendor = Apple Inc.
+	java.vm.version = 20.10-b01-428
+	javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
+	javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
+	javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
+	javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
+	javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
+	javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
+	javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
+	javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
+	javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
+	javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
+	jboss.home.dir = /Users/bbrowning/src/torquebox/build/assembly/target/stage/torquebox/jboss
+	jboss.host.name = bbrowning-mbp
+	jboss.modules.dir = /Users/bbrowning/src/torquebox/build/assembly/target/stage/torquebox/jboss/modules
+	jboss.modules.system.pkgs = org.jboss.byteman
+	jboss.node.name = bbrowning-mbp
+	jboss.qualified.host.name = bbrowning-mbp.local
+	jboss.server.base.dir = /Users/bbrowning/src/torquebox/build/assembly/target/stage/torquebox/jboss/standalone
+	jboss.server.config.dir = /Users/bbrowning/src/torquebox/build/assembly/target/stage/torquebox/jboss/standalone/configuration
+	jboss.server.data.dir = /Users/bbrowning/src/torquebox/build/assembly/target/stage/torquebox/jboss/standalone/data
+	jboss.server.default.config = standalone.xml
+	jboss.server.deploy.dir = /Users/bbrowning/src/torquebox/build/assembly/target/stage/torquebox/jboss/standalone/data/content
+	jboss.server.log.dir = /Users/bbrowning/src/torquebox/build/assembly/target/stage/torquebox/jboss/standalone/log
+	jboss.server.name = bbrowning-mbp
+	jboss.server.temp.dir = /Users/bbrowning/src/torquebox/build/assembly/target/stage/torquebox/jboss/standalone/tmp
+	jruby.compile.invokedynamic = false
+	jruby.home = /Users/bbrowning/src/torquebox/build/assembly/target/stage/torquebox/jruby
+	line.separator = 
+
+	logging.configuration = file:/Users/bbrowning/src/torquebox/build/assembly/target/stage/torquebox/jboss/standalone/configuration/logging.properties
+	module.path = /Users/bbrowning/src/torquebox/build/assembly/target/stage/torquebox/jboss/modules
+	mrj.build = 10M3811
+	mrj.version = 1060.1.6.0_35-428
+	org.jboss.boot.log.file = /Users/bbrowning/src/torquebox/build/assembly/target/stage/torquebox/jboss/standalone/log/boot.log
+	org.jboss.resolver.warning = true
+	org.xml.sax.driver = __redirected.__XMLReaderFactory
+	os.arch = i386
+	os.name = Mac OS X
+	os.version = 10.6.8
+	path.separator = :
+	socksNonProxyHosts = local|*.local|169.254/16|*.169.254/16
+	sun.arch.data.model = 32
+	sun.boot.class.path = /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/jsfd.jar:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/classes.jar:/System/Library/Frameworks/JavaVM.framework/Frameworks/JavaRuntimeSupport.framework/Resources/Java/JavaRuntimeSupport.jar:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/ui.jar:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/laf.jar:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/sunrsasign.jar:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/jsse.jar:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/jce.jar:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/charsets.jar
+	sun.boot.library.path = /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Libraries
+	sun.cpu.endian = little
+	sun.cpu.isalist = 
+	sun.io.unicode.encoding = UnicodeLittle
+	sun.java.command = /Users/bbrowning/src/torquebox/build/assembly/target/stage/torquebox/jboss/jboss-modules.jar -mp /Users/bbrowning/src/torquebox/build/assembly/target/stage/torquebox/jboss/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -Djboss.home.dir=/Users/bbrowning/src/torquebox/build/assembly/target/stage/torquebox/jboss -Djboss.server.base.dir=/Users/bbrowning/src/torquebox/build/assembly/target/stage/torquebox/jboss/standalone -Djruby.home=/Users/bbrowning/src/torquebox/build/assembly/target/stage/torquebox/jruby --server-config=standalone.xml
+	sun.java.launcher = SUN_STANDARD
+	sun.jnu.encoding = MacRoman
+	sun.management.compiler = HotSpot Client Compiler
+	sun.os.patch.level = unknown
+	sun.rmi.dgc.client.gcInterval = 3600000
+	sun.rmi.dgc.server.gcInterval = 3600000
+	user.country = US
+	user.dir = /Users/bbrowning/src/torquebox/build/assembly/target/stage/torquebox/jboss
+	user.home = /Users/bbrowning
+	user.language = en
+	user.name = bbrowning
+	user.timezone = America/New_York
+17:38:27,695 DEBUG [org.jboss.as.config] VM Arguments: -D[Standalone] -Xms64m -Xmx512m -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 -Xss2048k -Djruby.compile.invokedynamic=false -Dorg.jboss.boot.log.file=/Users/bbrowning/src/torquebox/build/assembly/target/stage/torquebox/jboss/standalone/log/boot.log -Dlogging.configuration=file:/Users/bbrowning/src/torquebox/build/assembly/target/stage/torquebox/jboss/standalone/configuration/logging.properties 
+17:38:28,374 INFO  [org.torquebox.bootstrap] Bootstrapping TorqueBox with a JRuby home of /Users/bbrowning/src/torquebox/build/assembly/target/stage/torquebox/jruby
+17:38:28,921 INFO  [org.torquebox.core.as] Initializing TorqueBox Core Subsystem
+17:38:28,925 INFO  [org.torquebox.cdi.as] Initializing TorqueBox CDI Subsystem
+17:38:28,925 INFO  [org.torquebox.jobs.as] Initializing TorqueBox Jobs Subsystem
+17:38:28,932 INFO  [org.torquebox.security.as] Initializing TorqueBox Auth Subsystem
+17:38:28,938 INFO  [org.torquebox.web.as] Initializing TorqueBox Web Subsystem
+17:38:28,940 INFO  [org.torquebox.stomp.as] Initializing TorqueBox STOMP Subsystem
+17:38:28,943 INFO  [org.torquebox.messaging.as] Initializing TorqueBox Messaging Subsystem
+17:38:28,945 INFO  [org.torquebox.services.as] Initializing TorqueBox Services Subsystem
+17:38:28,947 INFO  [org.projectodd.polyglot.hasingleton.as] Initializing HA-Singleton Subsystem
+17:38:28,948 INFO  [org.projectodd.polyglot.cache.as] Initializing Polyglot Cache Subsystem
+17:38:28,954 INFO  [org.torquebox.core.as] Welcome to TorqueBox AS - http://torquebox.org/
+17:38:28,954 INFO  [org.torquebox.core.as]   version........... 2.1.2-SNAPSHOT
+17:38:28,969 INFO  [org.torquebox.core.as]   build............. development (bbrowning)
+17:38:28,970 INFO  [org.torquebox.core.as]   revision.......... 73ec27cbb650ba498afc468efe4b1cd5801386f1
+17:38:28,970 INFO  [org.torquebox.core.as]   built with:
+17:38:28,970 INFO  [org.torquebox.core.as]     HornetQ......... 2.2.18.Final (HQ_2_2_18_FINAL, 122)
+17:38:28,970 INFO  [org.torquebox.core.as]     JBossAS......... 7.1.x.incremental.1
+17:38:28,970 INFO  [org.torquebox.core.as]     Infinispan...... 5.1.5.FINAL
+17:38:28,971 INFO  [org.torquebox.core.as]     Quartz.......... 1.8.5
+17:38:28,971 INFO  [org.torquebox.core.as]     JRuby........... 1.6.7.2
+17:38:29,213 WARN  [org.jboss.as.server] JBAS015883: No security realm defined for native management service; all access will be unrestricted.
+17:38:29,220 INFO  [org.xnio] XNIO Version 3.0.4.GA
+17:38:29,227 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.4.GA
+17:38:29,237 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
+17:38:29,238 WARN  [org.jboss.as.server] JBAS015884: No security realm defined for http management service; all access will be unrestricted.
+17:38:29,250 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.8.GA
+17:38:29,382 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
+17:38:39,127 INFO  [org.jboss.as.logging] JBAS011503: Restored bootstrap log handlers
+17:38:39,128 INFO  [org.jboss.as.messaging] JBAS011605: Unbound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
+17:38:39,129 INFO  [org.jboss.as.clustering.infinispan] JBAS010282: Stopped sessions cache from polyglot container
+17:38:39,139 INFO  [jacorb.poa] POA Naming destroyed
+17:38:39,140 INFO  [jacorb.poa] POA IRPOA destroyed
+17:38:39,140 INFO  [jacorb.poa] POA RootPOA destroyed
+17:38:39,141 INFO  [jacorb.orb] prepare ORB for shutdown...
+17:38:39,141 INFO  [jacorb.orb] ORB going down...
+17:38:39,142 INFO  [org.apache.coyote.http11.Http11Protocol] Pausing Coyote HTTP/1.1 on http-localhost/127.0.0.1:8080
+17:38:39,142 INFO  [org.apache.coyote.http11.Http11Protocol] Stopping Coyote HTTP/1.1 on http-localhost/127.0.0.1:8080
+17:38:39,151 INFO  [jacorb.orb] ORB shutdown complete
+17:38:39,153 INFO  [jacorb.orb] ORB run, exit
+17:38:39,153 INFO  [jacorb.orb.iiop] Listener exited
+17:38:39,160 INFO  [org.hornetq.ra.HornetQResourceAdapter] HornetQ resource adapter stopped
+17:38:39,166 INFO  [com.arjuna.ats.jbossatx] ARJUNA032018: Destroying TransactionManagerService
+17:38:39,167 INFO  [com.arjuna.ats.jbossatx] ARJUNA032014: Stopping transaction recovery manager
+17:38:39,170 INFO  [org.jboss.as.clustering.infinispan] JBAS010282: Stopped __recoveryInfoCacheName__ cache from polyglot container
+17:38:39,205 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] HornetQ Server version 2.2.18.Final (HQ_2_2_18_FINAL, 122) [334192ff-f86b-11e1-8224-078f279d8a3d] stopped
+17:38:39,209 INFO  [org.jboss.as] JBAS015950: JBoss AS 7.1.x.incremental.1 "Steropes" stopped in 97ms

data/jboss/standalone/log/server.log

@@ -0,0 +1,47 @@
+17:38:29,412 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 42) JBAS016200: Activating ConfigAdmin Subsystem
+17:38:29,413 INFO  [org.jboss.as.remoting] (MSC service thread 1-7) JBAS017100: Listening on 127.0.0.1:9999
+17:38:29,424 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 47) JBAS010280: Activating Infinispan subsystem.
+17:38:29,429 INFO  [org.jboss.as.jacorb] (ServerService Thread Pool -- 48) JBAS016300: Activating JacORB Subsystem
+17:38:29,439 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 58) JBAS011800: Activating Naming Subsystem
+17:38:29,448 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 59) JBAS011906: Activating OSGi Subsystem
+17:38:29,484 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 64) JBAS013171: Activating Security Subsystem
+17:38:29,497 INFO  [org.jboss.as.security] (MSC service thread 1-7) JBAS013170: Current PicketBox version=4.0.9.Final
+17:38:29,593 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-6) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.11.Final)
+17:38:29,641 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 68) JBAS015537: Activating WebServices Extension
+17:38:29,682 INFO  [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service
+17:38:29,693 INFO  [org.jboss.jaxr] (MSC service thread 1-1) JBAS014000: Started JAXR subsystem, binding JAXR connection factory into JNDI as: java:jboss/jaxr/ConnectionFactory
+17:38:29,702 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]
+17:38:29,761 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 43) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
+17:38:29,903 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.2.GA
+17:38:30,034 WARN  [org.jboss.as.messaging] (MSC service thread 1-1) 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
+17:38:30,319 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-1) live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/Users/bbrowning/src/torquebox/build/assembly/target/stage/torquebox/jboss/standalone/data/messagingjournal,bindingsDirectory=/Users/bbrowning/src/torquebox/build/assembly/target/stage/torquebox/jboss/standalone/data/messagingbindings,largeMessagesDirectory=/Users/bbrowning/src/torquebox/build/assembly/target/stage/torquebox/jboss/standalone/data/messaginglargemessages,pagingDirectory=/Users/bbrowning/src/torquebox/build/assembly/target/stage/torquebox/jboss/standalone/data/messagingpaging)
+17:38:30,322 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-1) Waiting to obtain live lock
+17:38:30,328 WARN  [jacorb.codeset] (MSC service thread 1-2) Warning - unknown codeset (MacRoman) - defaulting to ISO-8859-1
+17:38:30,367 INFO  [org.torquebox.core.runtime] (MSC service thread 1-6) Creating ruby runtime (ruby_version: RUBY1_8, compile_mode: JIT, context: global)
+17:38:30,402 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-4) Starting Coyote HTTP/1.1 on http-localhost/127.0.0.1:8080
+17:38:30,536 INFO  [org.hornetq.core.persistence.impl.journal.JournalStorageManager] (MSC service thread 1-1) Using NIO Journal
+17:38:30,580 INFO  [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016330: CORBA ORB Service started
+17:38:30,769 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
+17:38:30,780 INFO  [org.hornetq.core.server.impl.FileLockNodeManager] (MSC service thread 1-1) Waiting to obtain live lock
+17:38:30,781 INFO  [org.hornetq.core.server.impl.FileLockNodeManager] (MSC service thread 1-1) Live Server Obtained live lock
+17:38:30,904 INFO  [org.infinispan.factories.GlobalComponentRegistry] (CacheService lifecycle - 1) ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.5.FINAL
+17:38:30,955 INFO  [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016328: CORBA Naming Service started
+17:38:31,231 INFO  [org.jboss.as.clustering.infinispan] (CacheService lifecycle - 1) JBAS010281: Started __recoveryInfoCacheName__ cache from polyglot container
+17:38:31,270 INFO  [org.infinispan.jmx.CacheJmxRegistration] (CacheService lifecycle - 1) ISPN000031: MBeans were successfully registered to the platform mbean server.
+17:38:31,270 INFO  [org.jboss.as.clustering.infinispan] (CacheService lifecycle - 1) JBAS010281: Started sessions cache from polyglot container
+17:38:31,305 INFO  [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-1) Started Netty Acceptor version 3.2.5.Final-a96d88c 127.0.0.1:5455 for CORE protocol
+17:38:31,307 INFO  [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-1) Started Netty Acceptor version 3.2.5.Final-a96d88c 127.0.0.1:5445 for CORE protocol
+17:38:31,315 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-1) Server is now live
+17:38:31,316 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-1) HornetQ Server version 2.2.18.Final (HQ_2_2_18_FINAL, 122) [334192ff-f86b-11e1-8224-078f279d8a3d]) started
+17:38:31,357 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 80) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
+17:38:31,360 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 81) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
+17:38:31,483 INFO  [org.jboss.as.deployment.connector] (MSC service thread 1-1) JBAS010406: Registered connection factory java:/JmsXA
+17:38:31,589 INFO  [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-1) HornetQ resource adaptor started
+17:38:31,591 INFO  [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) IJ020002: Deployed: file://RaActivatorhornetq-ra
+17:38:31,599 INFO  [org.jboss.as.deployment.connector] (MSC service thread 1-1) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
+17:38:33,048 INFO  [org.jboss.as.remoting] (MSC service thread 1-5) JBAS017100: Listening on 127.0.0.1:4447
+17:38:33,048 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /Users/bbrowning/src/torquebox/build/assembly/target/stage/torquebox/jboss/standalone/deployments
+17:38:33,615 INFO  [org.torquebox.core.runtime] (MSC service thread 1-6) Created ruby runtime (ruby_version: RUBY1_8, compile_mode: JIT, context: global) in 3.24s
+17:38:33,657 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
+17:38:33,658 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
+17:38:33,660 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.x.incremental.1 "Steropes" started in 6666ms - Started 171 of 270 services (98 services are passive or on-demand)