karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré ...@nanthrax.net>
Subject Re: Cellar Clustering in karaf
Date Tue, 16 Aug 2016 15:03:51 GMT
What's your karaf version, cellar version and hazel cast.xml file ? I think you don't use the
hazelcast XML provided with cellar.

Regards
JB



On Aug 16, 2016, 10:33, at 10:33, Chandan <chandan.mysorebalakrishna@in.bosch.com> wrote:
>Hello,
>
>I have encountered below exception. All my proxy servlet are failed not
>showing it as deployed
>
>208 | CellarBalancerProxyServlet | ServletModel-13            | *Failed
>    
>*| /features           | [/features/*]
>208 | CellarBalancerProxyServlet | ServletModel-14            | *Failed
>    
>*| /gogo               | [/gogo/*]
>208 | CellarBalancerProxyServlet | ServletModel-15            | *Failed
>    
>*| /instance           | [/instance/*]
>208 | CellarBalancerProxyServlet | ServletModel-16            | *Failed
>    
>*| /cxf                | [/cxf/*]
>208 | CellarBalancerProxyServlet | ServletModel-17            | *Failed
>    
>*| /system/console     | [/system/console/*]
>
>Console:
>I am seeing 
>
>Exception in thread "hz.cellar.IO.thread-in-2"
>java.lang.IllegalThreadStateException: hz.cellar.IO.thread-in-2 cannot
>make
>remote call:
>com.hazelcast.map.impl.operation.PutOperation{identityHash=1269781987,
>serviceName='hz:impl:mapService'
>at
>com.hazelcast.spi.impl.operationservice.impl.Invocation.invokeInternal(Invocation.java:208)
>at
>com.hazelcast.spi.impl.operationservice.impl.Invocation.invoke(Invocation.java:180)
>at
>com.hazelcast.spi.impl.operationservice.impl.InvocationBuilderImpl.invoke(InvocationBuilderImpl.java:46)
>at
>com.hazelcast.map.impl.proxy.MapProxySupport.invokeOperation(MapProxySupport.java:316)
>at
>com.hazelcast.map.impl.proxy.MapProxySupport.putInternal(MapProxySupport.java:290)
>at com.hazelcast.map.impl.proxy.MapProxyImpl.put(MapProxyImpl.java:109)
>at com.hazelcast.map.impl.proxy.MapProxyImpl.put(MapProxyImpl.java:99)
>at
>org.apache.karaf.cellar.log.LogAppender.doAppend(LogAppender.java:55)
>at
>org.ops4j.pax.logging.service.internal.PaxAppenderProxy.doAppend(PaxAppenderProxy.java:63)
>at
>org.ops4j.pax.logging.service.internal.AppenderBridgeImpl.append(AppenderBridgeImpl.java:67)
>at
>org.ops4j.pax.logging.service.internal.AppenderBridgeImpl.doAppend(AppenderBridgeImpl.java:61)
>at
>org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:59)
>at org.apache.log4j.Category.callAppenders(Category.java:179)
>at org.apache.log4j.Category.forcedLog(Category.java:333)
>at org.apache.log4j.Category.log(Category.java:724)
>at
>org.ops4j.pax.logging.service.internal.PaxLoggerImpl.log(PaxLoggerImpl.java:335)
>at
>org.ops4j.pax.logging.service.internal.JdkHandler.publish(JdkHandler.java:114)
>at java.util.logging.Logger.log(Logger.java:738)
>at
>com.hazelcast.logging.StandardLoggerFactory$StandardLogger.log(StandardLoggerFactory.java:49)
>at
>com.hazelcast.logging.LoggingServiceImpl$DefaultLogger.log(LoggingServiceImpl.java:167)
>at com.hazelcast.logging.AbstractLogger.warning(AbstractLogger.java:90)
>
>
>What could be the issue?
>
>Regards,
>Chandan
>
>
>
>
>--
>View this message in context:
>http://karaf.922171.n3.nabble.com/Cellar-Clustering-in-karaf-tp4047542p4047550.html
>Sent from the Karaf - Dev mailing list archive at Nabble.com.

Mime
  • Unnamed multipart/alternative (inline, 8-Bit, 0 bytes)
View raw message