Thanks for your help Rado but I'm still confused.
Why would I need a web.xml file when my app is not a web app? Seems kind of odd.
Again not be a web app guy where does this file go?
My jar file structure looks like this:
com
main
mySLSB
META-INF
MANIFEST.MF
--web.xml
I created an web.xml and placed it into the META-INF folder
Is this the correct format?
<?xml version="1.0" encoding="ISO-8859-1"?>
<web-app>
<distributable/>
</web-app>
After build/deploy the log still does not display anything about clustering.
08:48:12,295 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 52) JBAS015537: Activating WebServices Extension
08:48:12,303 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 43) JBAS011940: Activating OSGi Subsystem
08:48:12,329 INFO [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 37) JBAS010260: Activating JGroups subsystem.
08:48:12,332 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 33) JBAS010280: Activating Infinispan subsystem.
08:48:12,356 INFO [org.jboss.as.connector] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.7.Final)
08:48:12,365 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 42) JBAS011800: Activating Naming Subsystem
08:48:12,379 INFO [org.jboss.as.security] (ServerService Thread Pool -- 48) JBAS013101: Activating Security Subsystem
08:48:12,433 INFO [org.jboss.as.security] (MSC service thread 1-2) JBAS013100: Current PicketBox version=4.0.6.final
08:48:12,440 INFO [org.jboss.as.naming] (MSC service thread 1-6) JBAS011802: Starting Naming Service
08:48:12,551 INFO [org.jboss.as.mail.extension] (MSC service thread 1-8) JBAS015400: Bound mail session [java:jboss/mail/Default]
08:48:12,603 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-6) JBoss Web Services - Stack CXF Server 4.0.1.GA
08:48:12,631 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 29) JBAS010403: Deploying JDBC-compliant driver class com.ibm.db2.jcc.DB2Driver (version 2.11)
08:48:12,723 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 33) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.
08:48:12,744 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 33) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.
08:48:12,744 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-7) Starting Coyote HTTP/1.1 on http--10.100.100.12-8080
08:48:12,772 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-6) JBAS015012: Started FileSystemDeploymentService for directory c:\apps\jboss-as-7.1.0.Final\standalone\deployments
08:48:12,777 INFO [org.jboss.as.remoting] (MSC service thread 1-8) JBAS017100: Listening on /10.100.100.12:9999
08:48:12,777 INFO [org.jboss.as.remoting] (MSC service thread 1-7) JBAS017100: Listening on /10.100.100.12:4447
08:48:12,824 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) JBAS010400: Bound data source [java:/admindatasource]
08:48:17,662 INFO [org.jboss.as.modcluster] (MSC service thread 1-4) JBAS011704: Mod_cluster uses default load balancer provider
08:48:17,678 INFO [org.jboss.modcluster.ModClusterService] (MSC service thread 1-4) Initializing mod_cluster 1.2.0.Final
08:48:17,685 INFO [org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl] (MSC service thread 1-4) Listening to proxy advertisements on 224.0.1.105:23364
08:48:17,721 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "LIDP-ADMI2.jar"
08:48:18,287 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named TestBean2 in deployment unit deployment "LIDP-ADMI2.jar" are as follows:
java:global/LIDP-ADMI2/TestBean2!com.lidp.main.TestBeanRemoteInf
java:app/LIDP-ADMI2/TestBean2!com.lidp.main.TestBeanRemoteInf
java:module/TestBean2!com.lidp.main.TestBeanRemoteInf
java:jboss/exported/LIDP-ADMI2/TestBean2!com.lidp.main.TestBeanRemoteInf
java:global/LIDP-ADMI2/TestBean2
java:app/LIDP-ADMI2/TestBean2
java:module/TestBean2
08:48:18,290 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named TestBean1 in deployment unit deployment "LIDP-ADMI2.jar" are as follows:
java:global/LIDP-ADMI2/TestBean1!com.lidp.main.TestBeanRemoteInf
java:app/LIDP-ADMI2/TestBean1!com.lidp.main.TestBeanRemoteInf
java:module/TestBean1!com.lidp.main.TestBeanRemoteInf
java:jboss/exported/LIDP-ADMI2/TestBean1!com.lidp.main.TestBeanRemoteInf
java:global/LIDP-ADMI2/TestBean1
java:app/LIDP-ADMI2/TestBean1
java:module/TestBean1
08:48:18,387 INFO [org.jboss.as] (MSC service thread 1-3) JBAS015874: JBoss AS 7.1.0.Final "Thunder" started in 7278ms - Started 196 of 318 services (120 services are passive or on-demand)
08:48:18,420 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "LIDP-ADMI2.jar"
Thanks.