Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-1930

Access via jndi to Infinispan cache in Singleton in standalone-full-ha.xml configuration

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Minor Minor
    • None
    • 5.1.2.FINAL
    • Core
    • None

      I,m trying to retrieve infinispan cache via jndi in @PostConstruct method of Singleton EJB marked with @Startup and i have the following issue :

      com.hp.dragon.loadingchain.common.LoadingChainCommonException: javax.naming.NameNotFoundException: Error looking up infinispan/cluster, service service jboss.naming.context.java.jboss.infinispan.cluster is not started
      at com.hp.dragon.loadingchain.common.ContextTool.lookupLocal(ContextTool.java:49)
      at com.hp.dragon.loadingchain.common.shared.SharedCacheContainer.<init>(SharedCacheContainer.java:16)
      at com.hp.dragon.loadingchain.common.shared.SharedCacheContainer.getInstance(SharedCacheContainer.java:23)
      at com.hp.dragon.loader.manager.CacheManager.checkForInitialization(CacheManager.java:53)
      at com.hp.dragon.loader.manager.InitializationManagerBean.addInitToken(InitializationManagerBean.java:39)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_30]
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_30]
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_30]
      at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_30]
      at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptorFactory$ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptorFactory.java:130)
      at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
      at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
      at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
      at org.jboss.as.ee.component.ManagedReferenceInterceptorFactory$ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptorFactory.java:95)
      at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
      at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
      at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
      at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
      at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
      at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:228)
      at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:333)
      at org.jboss.as.ejb3.tx.SingletonLifecycleCMTTxInterceptor.processInvocation(SingletonLifecycleCMTTxInterceptor.java:56)
      at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
      at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
      at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
      at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45)
      at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
      at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
      at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161)
      ... 9 more
      Caused by: javax.naming.NameNotFoundException: Error looking up infinispan/cluster, service service jboss.naming.context.java.jboss.infinispan.cluster is not started
      at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:126)
      at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:74)
      at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178)
      at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:123)
      at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:214)
      at javax.naming.InitialContext.lookup(InitialContext.java:392) [rt.jar:1.6.0_30]
      at com.hp.dragon.loadingchain.common.ContextTool.lookupLocal(ContextTool.java:46)
      ... 37 more

      My cache configuration is the default configuration of standalone-full-ha.xml , I have only added start="EAGER" and jndi-name to the cache-container configuration :
      .............
      <subsystem xmlns="urn:jboss:domain:infinispan:1.2" default-cache-container="cluster">
      <cache-container name="cluster" default-cache="default" jndi-name="java:jboss/infinispan/cluster" start="EAGER">
      <transport lock-timeout="60000"/>
      <replicated-cache name="default" mode="SYNC" batching="true">
      <locking isolation="REPEATABLE_READ"/>
      </replicated-cache>
      </cache-container>

      ........................ .

      If I perform an hot deploy of my application the problems does not occur.
      This is the entire server.log :

      11:24:14,818 INFO [org.jboss.as.configadmin] (ServerService Thread Pool – 34) JBAS016200: Activating ConfigAdmin Subsystem
      11:24:14,851 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool – 39) JBAS010280: Activating Infinispan subsystem.
      11:24:14,853 INFO [org.jboss.as.jacorb] (ServerService Thread Pool – 40) JBAS016300: Activating JacORB Subsystem
      11:24:14,869 INFO [org.jboss.as.clustering.jgroups] (ServerService Thread Pool – 45) JBAS010260: Activating JGroups subsystem.
      11:24:14,932 INFO [org.jboss.as.security] (ServerService Thread Pool – 58) JBAS013101: Activating Security Subsystem
      11:24:14,947 INFO [org.jboss.as.naming] (ServerService Thread Pool – 52) JBAS011800: Activating Naming Subsystem
      11:24:14,951 INFO [org.jboss.as.osgi] (ServerService Thread Pool – 53) JBAS011940: Activating OSGi Subsystem
      11:24:14,977 INFO [org.jboss.as.security] (MSC service thread 1-4) JBAS013100: Current PicketBox version=4.0.7.Final
      11:24:14,995 INFO [org.jboss.as.connector] (MSC service thread 1-7) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
      11:24:15,001 INFO [org.jboss.as.webservices] (ServerService Thread Pool – 62) JBAS015537: Activating WebServices Extension
      11:24:15,014 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool – 35) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
      11:24:15,072 INFO [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service
      11:24:15,119 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]
      11:24:15,185 INFO [org.jboss.jaxr] (MSC service thread 1-7) JBAS014000: Started JAXR subsystem, binding JAXR connection factory into JNDI as: java:jboss/jaxr/ConnectionFactory
      11:24:15,316 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.0.2.GA
      11:24:15,353 WARN [org.jboss.as.messaging] (MSC service thread 1-8) 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
      11:24:15,411 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http-localhost.localdomain-127.0.0.1-8080
      11:24:15,417 INFO [org.apache.coyote.ajp.AjpProtocol] (MSC service thread 1-3) Starting Coyote AJP/1.3 on ajp-localhost.localdomain-127.0.0.1-8009
      11:24:15,538 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-8) live server is starting with configuration HornetQ Configuration (clustered=true,backup=false,sharedStore=true,journalDirectory=/home/carmelo/Programs/jboss-as-7.1.1.Final/standalone/data/messagingjournal,bindingsDirectory=/home/carmelo/Programs/jboss-as-7.1.1.Final/standalone/data/messagingbindings,largeMessagesDirectory=/home/carmelo/Programs/jboss-as-7.1.1.Final/standalone/data/messaginglargemessages,pagingDirectory=/home/carmelo/Programs/jboss-as-7.1.1.Final/standalone/data/messagingpaging)
      11:24:15,541 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-8) Waiting to obtain live lock
      11:24:15,546 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool – 39) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.
      11:24:15,561 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool – 39) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.
      11:24:15,669 INFO [org.hornetq.core.persistence.impl.journal.JournalStorageManager] (MSC service thread 1-8) Using NIO Journal
      11:24:15,749 INFO [org.jboss.modcluster.ModClusterService] (MSC service thread 1-5) Initializing mod_cluster 1.2.0.Final
      11:24:15,772 INFO [org.jboss.as.jacorb] (MSC service thread 1-4) JBAS016330: CORBA ORB Service started
      11:24:15,798 INFO [org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl] (MSC service thread 1-5) Listening to proxy advertisements on 224.0.1.105:23364
      11:24:15,965 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
      11:24:16,008 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on /127.0.0.1:9999
      11:24:16,008 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on localhost.localdomain/127.0.0.1:4447
      11:24:16,015 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "loader-ear-0.1-SNAPSHOT.ear"
      11:24:16,028 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-7) JBAS015012: Started FileSystemDeploymentService for directory /home/carmelo/Programs/jboss-as-7.1.1.Final/standalone/deployments
      11:24:16,044 INFO [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016328: CORBA Naming Service started
      11:24:16,063 INFO [org.hornetq.core.server.impl.FileLockNodeManager] (MSC service thread 1-8) Waiting to obtain live lock
      11:24:16,064 INFO [org.hornetq.core.server.impl.FileLockNodeManager] (MSC service thread 1-8) Live Server Obtained live lock
      11:24:16,204 WARNING [org.jgroups.protocols.UDP] (pool-6-thread-1) send buffer of socket java.net.DatagramSocket@7e03f9ad was set to 640KB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max send buffer in the OS correctly (e.g. net.core.wmem_max on Linux)
      11:24:16,205 WARNING [org.jgroups.protocols.UDP] (pool-6-thread-1) receive buffer of socket java.net.DatagramSocket@7e03f9ad was set to 20MB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux)
      11:24:16,207 WARNING [org.jgroups.protocols.UDP] (pool-6-thread-1) send buffer of socket java.net.MulticastSocket@70ccbb35 was set to 640KB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max send buffer in the OS correctly (e.g. net.core.wmem_max on Linux)
      11:24:16,208 WARNING [org.jgroups.protocols.UDP] (pool-6-thread-1) receive buffer of socket java.net.MulticastSocket@70ccbb35 was set to 25MB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux)
      11:24:16,221 INFO [stdout] (pool-6-thread-1)
      11:24:16,221 INFO [stdout] (pool-6-thread-1) -------------------------------------------------------------------
      11:24:16,221 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "loader-business-logic-0.1-SNAPSHOT.jar"
      11:24:16,222 INFO [stdout] (pool-6-thread-1) GMS: address=carmelo/cluster, cluster=cluster, physical address=127.0.0.1:55200
      11:24:16,223 INFO [stdout] (pool-6-thread-1) -------------------------------------------------------------------
      11:24:16,223 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) Class Path entry loader-persistence-0.1-SNAPSHOT.jar in "/content/loader-ear-0.1-SNAPSHOT.ear/loader-business-logic-0.1-SNAPSHOT.jar" does not point to a valid jar for a Class-Path reference.
      11:24:16,224 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) Class Path entry runtime-0.2-SNAPSHOT.jar in "/content/loader-ear-0.1-SNAPSHOT.ear/loader-business-logic-0.1-SNAPSHOT.jar" does not point to a valid jar for a Class-Path reference.
      11:24:16,225 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) Class Path entry commonLib-0.1-SNAPSHOT.jar in "/content/loader-ear-0.1-SNAPSHOT.ear/loader-business-logic-0.1-SNAPSHOT.jar" does not point to a valid jar for a Class-Path reference.
      11:24:16,477 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named CacheManagerBean in deployment unit subdeployment "loader-business-logic-0.1-SNAPSHOT.jar" of deployment "loader-ear-0.1-SNAPSHOT.ear" are as follows:

      java:global/loader-ear-0.1-SNAPSHOT/loader-business-logic-0.1-SNAPSHOT/CacheManagerBean!com.hp.dragon.loader.manager.client.CacheManagerRemote
      java:app/loader-business-logic-0.1-SNAPSHOT/CacheManagerBean!com.hp.dragon.loader.manager.client.CacheManagerRemote
      java:module/CacheManagerBean!com.hp.dragon.loader.manager.client.CacheManagerRemote
      java:jboss/exported/loader-ear-0.1-SNAPSHOT/loader-business-logic-0.1-SNAPSHOT/CacheManagerBean!com.hp.dragon.loader.manager.client.CacheManagerRemote
      java:global/loader-ear-0.1-SNAPSHOT/loader-business-logic-0.1-SNAPSHOT/CacheManagerBean!com.hp.dragon.loader.manager.client.CacheManagerLocal
      java:app/loader-business-logic-0.1-SNAPSHOT/CacheManagerBean!com.hp.dragon.loader.manager.client.CacheManagerLocal
      java:module/CacheManagerBean!com.hp.dragon.loader.manager.client.CacheManagerLocal

      11:24:16,485 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named InitializationManagerBean in deployment unit subdeployment "loader-business-logic-0.1-SNAPSHOT.jar" of deployment "loader-ear-0.1-SNAPSHOT.ear" are as follows:

      java:global/loader-ear-0.1-SNAPSHOT/loader-business-logic-0.1-SNAPSHOT/InitializationManagerBean!com.hp.dragon.loader.manager.client.InitializationManagerLocal
      java:app/loader-business-logic-0.1-SNAPSHOT/InitializationManagerBean!com.hp.dragon.loader.manager.client.InitializationManagerLocal
      java:module/InitializationManagerBean!com.hp.dragon.loader.manager.client.InitializationManagerLocal
      java:global/loader-ear-0.1-SNAPSHOT/loader-business-logic-0.1-SNAPSHOT/InitializationManagerBean
      java:app/loader-business-logic-0.1-SNAPSHOT/InitializationManagerBean
      java:module/InitializationManagerBean

      11:24:16,657 WARN [org.hornetq.core.server.cluster.impl.BroadcastGroupImpl] (MSC service thread 1-8) local-bind-address specified for broadcast group but no local-bind-port specified so socket will NOT be bound to a local address/port
      11:24:16,770 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-8) Started Netty Acceptor version 3.2.5.Final-a96d88c localhost.localdomain:5455 for CORE protocol
      11:24:16,772 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-8) Started Netty Acceptor version 3.2.5.Final-a96d88c localhost.localdomain:5445 for CORE protocol
      11:24:16,776 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-8) Server is now live
      11:24:16,777 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-8) HornetQ Server version 2.2.13.Final (HQ_2_2_13_FINAL_AS7, 122) [63c580b1-71e6-11e1-9200-f0def1bf7be1]) started
      11:24:16,772 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.deployment.subunit."loader-ear-0.1-SNAPSHOT.ear"."loader-business-logic-0.1-SNAPSHOT.jar".component.InitializationManagerBean.START: org.jboss.msc.service.StartException in service jboss.deployment.subunit."loader-ear-0.1-SNAPSHOT.ear"."loader-business-logic-0.1-SNAPSHOT.jar".component.InitializationManagerBean.START: Failed to start service
      at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
      at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
      Caused by: java.lang.IllegalStateException: JBAS011048: Failed to construct component instance
      at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:163)
      at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:85)
      at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:116)
      at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:130)
      at org.jboss.as.ee.component.ComponentStartService.start(ComponentStartService.java:44)
      at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
      at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
      ... 3 more
      Caused by: com.hp.dragon.loadingchain.common.LoadingChainCommonException: javax.naming.NameNotFoundException: Error looking up infinispan/cluster, service service jboss.naming.context.java.jboss.infinispan.cluster is not started
      at com.hp.dragon.loadingchain.common.ContextTool.lookupLocal(ContextTool.java:49)
      at com.hp.dragon.loadingchain.common.shared.SharedCacheContainer.<init>(SharedCacheContainer.java:16)
      at com.hp.dragon.loadingchain.common.shared.SharedCacheContainer.getInstance(SharedCacheContainer.java:23)
      at com.hp.dragon.loader.manager.CacheManager.checkForInitialization(CacheManager.java:53)
      at com.hp.dragon.loader.manager.InitializationManagerBean.addInitToken(InitializationManagerBean.java:39)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_30]
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_30]
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_30]
      at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_30]
      at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptorFactory$ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptorFactory.java:130)
      at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
      at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
      at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
      at org.jboss.as.ee.component.ManagedReferenceInterceptorFactory$ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptorFactory.java:95)
      at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
      at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
      at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
      at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
      at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
      at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:228)
      at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:333)
      at org.jboss.as.ejb3.tx.SingletonLifecycleCMTTxInterceptor.processInvocation(SingletonLifecycleCMTTxInterceptor.java:56)
      at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
      at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
      at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
      at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45)
      at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
      at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
      at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161)
      ... 9 more
      Caused by: javax.naming.NameNotFoundException: Error looking up infinispan/cluster, service service jboss.naming.context.java.jboss.infinispan.cluster is not started
      at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:126)
      at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:74)
      at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178)
      at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:123)
      at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:214)
      at javax.naming.InitialContext.lookup(InitialContext.java:392) [rt.jar:1.6.0_30]
      at com.hp.dragon.loadingchain.common.ContextTool.lookupLocal(ContextTool.java:46)
      ... 37 more

      11:24:16,788 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) trying to deploy queue jms.queue.testQueue
      11:24:16,814 INFO [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011601: Bound messaging object to jndi name java:/queue/test
      11:24:16,827 INFO [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/test
      11:24:16,840 INFO [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
      11:24:16,843 INFO [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011601: Bound messaging object to jndi name java:/RemoteConnectionFactory
      11:24:16,857 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-3) trying to deploy queue jms.topic.testTopic
      11:24:16,892 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-6) JBAS010406: Registered connection factory java:/JmsXA
      11:24:16,911 INFO [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:/topic/test
      11:24:16,917 INFO [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/topic/test
      11:24:16,920 INFO [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-6) HornetQ resource adaptor started
      11:24:16,920 INFO [org.jboss.as.messaging] (MSC service thread 1-7) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
      11:24:16,929 INFO [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-6) IJ020002: Deployed: file://RaActivatorhornetq-ra
      11:24:16,947 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-7) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
      11:24:18,462 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS018559: Deployed "loader-ear-0.1-SNAPSHOT.ear"
      11:24:18,471 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
      JBAS014777: Services which failed to start: service jboss.deployment.subunit."loader-ear-0.1-SNAPSHOT.ear"."loader-business-logic-0.1-SNAPSHOT.jar".component.InitializationManagerBean.START: org.jboss.msc.service.StartException in service jboss.deployment.subunit."loader-ear-0.1-SNAPSHOT.ear"."loader-business-logic-0.1-SNAPSHOT.jar".component.InitializationManagerBean.START: Failed to start service

      11:24:18,573 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
      11:24:18,575 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 5760ms - Started 259 of 393 services (1 services failed or missing dependencies, 132 services are passive or on-demand)

      This is my Singleton bean :

      import javax.annotation.PostConstruct;
      import javax.annotation.PreDestroy;
      import javax.ejb.Singleton;
      import javax.ejb.Startup;
      import javax.ejb.TransactionAttribute;
      import javax.ejb.TransactionAttributeType;
      import javax.ejb.TransactionManagement;
      import javax.ejb.TransactionManagementType;

      import org.slf4j.Logger;
      import org.slf4j.LoggerFactory;

      import com.hp.dragon.loader.manager.client.InitializationManagerLocal;

      @Singleton
      @Startup
      public class InitializationManagerBean implements InitializationManagerLocal {

      /**

      • Serial Version UID
        */
        private static final long serialVersionUID = 1L;

      /**

      • Logger for this component
        */
        private static transient final Logger LOGGER = LoggerFactory
        .getLogger(InitializationManagerBean.class);

      /**

      • Performs initialization action for loading process
        */
        @PostConstruct
        private void addInitToken() throws Exception {
        if (CacheManager.getInstance().checkForInitialization()) { LOGGER.info("Start Initialization Loader module"); LOGGER.info("Initialization Loader module successfully executed"); }

        else

        { LOGGER.info("This node does not manage initialization process"); }

      }

      }

      This is CacheManager :

      public class CacheManager {

      /**

      • Serial Version UID
        */
        private static final long serialVersionUID = 1L;

      /**

      • Logger for this component
        */
        private static transient final Logger LOGGER = LoggerFactory
        .getLogger(CacheManager.class);

      private static CacheManager onlyInstance;

      private CacheManager() {

      }

      public static synchronized CacheManager getInstance()

      { if (onlyInstance == null) onlyInstance = new CacheManager(); return onlyInstance; }

      public synchronized boolean checkForInitialization() throws Exception {
      if (!SharedCacheContainer.getInstance().getDefaultCache()
      .containsKey("LOADER_INITILIZATION_CACHE_NAME"))

      { Object previuosValue = SharedCacheContainer .getInstance() .getDefaultCache() .put("LOADER_INITILIZATION_CACHE_NAME", "LOADER_INITILIZATION_CACHE_NAME"); return previuosValue == null; }

      else

      { return false; }

      }
      }

      This is SharedCacheContainer:

      public class SharedCacheContainer {

      private static SharedCacheContainer onlyInstance;
      private CacheContainer CACHE_MANAGER;

      private SharedCacheContainer() throws LoadingChainCommonException

      { CACHE_MANAGER = ContextTool.lookupLocal(CacheContainer.class, "java:jboss/infinispan/cluster"); }

      public static synchronized SharedCacheContainer getInstance()
      throws LoadingChainCommonException

      { if (onlyInstance == null) onlyInstance = new SharedCacheContainer(); return onlyInstance; }

      /**

      • Retrieves the default cache.
      • @param <K>
      • type used as keys in this cache
      • @param <V>
      • type used as values in this cache
      • @return a cache
        */
        public <K, V> Cache<K, V> getDefaultCache() { return CACHE_MANAGER.getCache(); }

      /**

      • Retrieves a named cache.
      • @param cacheName
      • name of cache to retrieve
      • @param <K>
      • type used as keys in this cache
      • @param <V>
      • type used as values in this cache
      • @return a cache
        */
        public <K, V> Cache<K, V> getCache(String cacheName) { if (cacheName == null) throw new NullPointerException("Cache name cannot be null!"); return CACHE_MANAGER.getCache(cacheName); }

      }

            [ISPN-1930] Access via jndi to Infinispan cache in Singleton in standalone-full-ha.xml configuration

            This is not an Infinispan issue:

            Caused by: javax.naming.NameNotFoundException: Error looking up infinispan/cluster, service service jboss.naming.context.java.jboss.infinispan.cluster is not started

            But if anything, it's an issue with AS7.

            If you're having issues getting Infinsipan running in AS 7.1, please start with the following quickstart: https://github.com/galderz/infinispan-quickstart/tree/t_710final

            And make sure you use 7.1.1 (7.1.0 has some funny issue in domain mode).

            This branch will soon be committed to to the main Infinispan quickstart.

            Galder Zamarreño added a comment - This is not an Infinispan issue: Caused by: javax.naming.NameNotFoundException: Error looking up infinispan/cluster, service service jboss.naming.context.java.jboss.infinispan.cluster is not started But if anything, it's an issue with AS7. If you're having issues getting Infinsipan running in AS 7.1, please start with the following quickstart: https://github.com/galderz/infinispan-quickstart/tree/t_710final And make sure you use 7.1.1 (7.1.0 has some funny issue in domain mode). This branch will soon be committed to to the main Infinispan quickstart.

            Sorry, but is possible to know the reason why you rejected the issue?

            carmelo aprile (Inactive) added a comment - Sorry, but is possible to know the reason why you rejected the issue?

              manik_jira Manik Surtani (Inactive)
              carmelo_jira carmelo aprile (Inactive)
              Archiver:
              rhn-support-adongare Amol Dongare

                Created:
                Updated:
                Resolved:
                Archived: