[JBoss JIRA] (AS7-4819) Read timed out on server shutdown and DIST SYNC
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-4819?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-4819:
----------------------------------
Fix Version/s: 8.0.0.Alpha1
(was: 7.2.0.CR1)
> Read timed out on server shutdown and DIST SYNC
> -----------------------------------------------
>
> Key: AS7-4819
> URL: https://issues.jboss.org/browse/AS7-4819
> Project: Application Server 7
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 7.1.2.Final (EAP)
> Reporter: Radoslav Husar
> Assignee: Paul Ferraro
> Fix For: 8.0.0.Alpha1
>
>
> Some of the clients are getting read timeout when using dist sync and the node is gracefully shut down.
> This is even more suspicions since the TOs in clustering are probably all set to max 15 seconds but the client timeout is set to 30 seconds. This looks fishy.
> {noformat}
> 2012/05/13 17:22:54:388 EDT [WARN ][Runner - 1749] SFCORE_LOG - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: IO error: java.net.SocketTimeoutException: Read timed out>
> {noformat}
> The exceptions seem to correlate with
> {noformat}
> ./perf20.log:[JBossINF] 17:23:11,344 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host]] (ajp-perf20/10.16.90.58:8009-109) Exception sending request initialized lifecycle event to listener instance of class org.jboss.weld.servlet.WeldListener: java.lang.RuntimeException: JBAS018060: Exception acquiring ownership of K5VcZ4gGFzRaLKYMesOQk0zD
> {noformat}
> being thrown on the server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-3947) TS: -Dtest=*<something>* only matches one test per module.
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-3947?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-3947:
----------------------------------
Fix Version/s: 8.0.0.Alpha1
(was: 7.2.0.CR1)
> TS: -Dtest=*<something>* only matches one test per module.
> -----------------------------------------------------------
>
> Key: AS7-3947
> URL: https://issues.jboss.org/browse/AS7-3947
> Project: Application Server 7
> Issue Type: Sub-task
> Components: Test Suite
> Reporter: Pavel Janousek
> Assignee: Aslak Knutsen
> Fix For: 8.0.0.Alpha1
>
>
> It seems like some regression.
> When I've tried run like:
> {code}
> mvn3 clean install -Dts.basic '-Dtest=*.jaxrs.*'
> {code}
> I got this result:
> {code}
> [pjanouse@pjanouse testsuite]$ mvn3 clean install -Dts.basic '-Dtest=*.jaxrs.*'
> Running org.jboss.as.test.smoke.jaxrs.JaxrsTestCase
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.689 sec
> ...
> ------ basic module:
> Running org.jboss.as.test.integration.osgi.jaxrs.RestEasyIntegrationTestCase
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.099 sec
> ...
> {code}
> So you can see - Integration basic is invoked, but only TestCases org.jboss.as.test.smoke.jaxrs.JaxrsTestCase and org.jboss.as.test.integration.osgi.jaxrs.RestEasyIntegrationTestCas were run although there are plenty of other TestCases fulfilled mask *\*.jaxrs.\** - many of them are localted in testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/jaxrs/ + sub=dirs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-4146) JGroups diag failure "failed sending diag rsp to /10.16.88.172:47231: java.io.IOException: Message too long"
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-4146?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-4146:
----------------------------------
Fix Version/s: 8.0.0.Alpha1
(was: 7.2.0.CR1)
> JGroups diag failure "failed sending diag rsp to /10.16.88.172:47231: java.io.IOException: Message too long"
> ------------------------------------------------------------------------------------------------------------
>
> Key: AS7-4146
> URL: https://issues.jboss.org/browse/AS7-4146
> Project: Application Server 7
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 7.1.1.Final
> Environment: Linux
> Reporter: Radoslav Husar
> Assignee: Paul Ferraro
> Priority: Minor
> Labels: eap6_need_triage
> Fix For: 8.0.0.Alpha1
>
>
> Implications of the issue are not currently known to me.
> {noformat}
> [JBossINF] 23:18:35,935 SEVERE [org.jgroups.protocols.UDP] (DiagnosticsHandler,null) failed sending diag rsp to /10.16.88.172:47231: java.io.IOException: Message too long
> [JBossINF] at java.net.PlainDatagramSocketImpl.send(Native Method) [rt.jar:1.6.0_30]
> [JBossINF] at java.net.DatagramSocket.send(DatagramSocket.java:625) [rt.jar:1.6.0_30]
> [JBossINF] at org.jgroups.stack.DiagnosticsHandler.sendResponse(DiagnosticsHandler.java:146) [jgroups-3.0.6.Final-redhat-1.jar:3.0.6.Final-redhat-1]
> [JBossINF] at org.jgroups.stack.DiagnosticsHandler.handleDiagnosticProbe(DiagnosticsHandler.java:135) [jgroups-3.0.6.Final-redhat-1.jar:3.0.6.Final-redhat-1]
> [JBossINF] at org.jgroups.stack.DiagnosticsHandler.run(DiagnosticsHandler.java:95) [jgroups-3.0.6.Final-redhat-1.jar:3.0.6.Final-redhat-1]
> [JBossINF] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
> {noformat}
> preceed by
> {noformat}
> [JBossINF] 23:18:30,699 ERROR [org.infinispan.transaction.tm.DummyTransaction] (EJB default - 5) ISPN000111: afterCompletion() failed for SynchronizationAdapter{localTransaction=LocalTransaction{remoteLockedNodes=[perf19/ejb, perf21/ejb], isMarkedForRollback=false, transaction=DummyTransaction{xid=DummyXid{id=9740}, status=3}, lockedKeys=null, backupKeyLocks=null, viewId=13} org.infinispan.transaction.synchronization.SyncLocalTransaction@2607} org.infinispan.transaction.synchronization.SynchronizationAdapter@2626: org.infinispan.CacheException: org.jgroups.TimeoutException: timeout sending message to perf21/ejb
> [JBossINF] at org.infinispan.util.Util.rewrapAsCacheException(Util.java:524)
> [JBossINF] at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.invokeRemoteCommand(CommandAwareRpcDispatcher.java:168)
> [JBossINF] at org.infinispan.remoting.transport.jgroups.JGroupsTransport.invokeRemotely(JGroupsTransport.java:478)
> [JBossINF] at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:148)
> [JBossINF] at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:169)
> [JBossINF] at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:219)
> [JBossINF] at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:206)
> [JBossINF] at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:201)
> [JBossINF] at org.infinispan.transaction.AbstractEnlistmentAdapter.removeTransactionInfoRemotely(AbstractEnlistmentAdapter.java:81)
> [JBossINF] at org.infinispan.transaction.AbstractEnlistmentAdapter.releaseLocksForCompletedTransaction(AbstractEnlistmentAdapter.java:73)
> [JBossINF] at org.infinispan.transaction.synchronization.SynchronizationAdapter.afterCompletion(SynchronizationAdapter.java:94)
> [JBossINF] at org.infinispan.transaction.tm.DummyTransaction.notifyAfterCompletion(DummyTransaction.java:272)
> [JBossINF] at org.infinispan.transaction.tm.DummyTransaction.runCommitTx(DummyTransaction.java:321)
> [JBossINF] at org.infinispan.transaction.tm.DummyTransaction.commit(DummyTransaction.java:90)
> [JBossINF] at org.infinispan.transaction.tm.DummyBaseTransactionManager.commit(DummyBaseTransactionManager.java:100)
> [JBossINF] at org.infinispan.batch.BatchContainer.resolveTransaction(BatchContainer.java:123)
> [JBossINF] at org.infinispan.batch.BatchContainer.endBatch(BatchContainer.java:105)
> [JBossINF] at org.infinispan.batch.BatchContainer.endBatch(BatchContainer.java:86)
> [JBossINF] at org.infinispan.CacheImpl.endBatch(CacheImpl.java:580)
> [JBossINF] at org.infinispan.AbstractDelegatingCache.endBatch(AbstractDelegatingCache.java:75)
> [JBossINF] at org.infinispan.AbstractDelegatingCache.endBatch(AbstractDelegatingCache.java:75)
> [JBossINF] at org.jboss.as.clustering.infinispan.invoker.BatchOperation.invoke(BatchOperation.java:26)
> [JBossINF] at org.jboss.as.clustering.infinispan.invoker.RetryingCacheInvoker.invoke(RetryingCacheInvoker.java:61)
> [JBossINF] at org.jboss.as.clustering.ejb3.cache.backing.infinispan.InfinispanBackingCacheEntryStore.invoke(InfinispanBackingCacheEntryStore.java:225)
> [JBossINF] at org.jboss.as.clustering.ejb3.cache.backing.infinispan.InfinispanBackingCacheEntryStore.update(InfinispanBackingCacheEntryStore.java:200)
> [JBossINF] at org.jboss.as.ejb3.cache.impl.backing.SerializationGroupMemberContainer.update(SerializationGroupMemberContainer.java:269) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
> [JBossINF] at org.jboss.as.ejb3.cache.impl.backing.SerializationGroupMemberContainer.update(SerializationGroupMemberContainer.java:50) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
> [JBossINF] at org.jboss.as.ejb3.cache.impl.backing.PassivatingBackingCacheImpl.release(PassivatingBackingCacheImpl.java:223) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
> [JBossINF] at org.jboss.as.ejb3.cache.spi.impl.AbstractCache.release(AbstractCache.java:76) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
> [JBossINF] at org.jboss.as.ejb3.cache.spi.impl.AbstractCache.release(AbstractCache.java:39) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
> [JBossINF] at org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor.releaseInstance(StatefulSessionSynchronizationInterceptor.java:197) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
> [JBossINF] at org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor.access$200(StatefulSessionSynchronizationInterceptor.java:50) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
> [JBossINF] at org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor$StatefulSessionSynchronization.afterCompletion(StatefulSessionSynchronizationInterceptor.java:271) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
> [JBossINF] at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:96)
> [JBossINF] at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:402)
> [JBossINF] at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:103)
> [JBossINF] at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:164)
> [JBossINF] at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1165)
> [JBossINF] at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:117)
> [JBossINF] at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75)
> [JBossINF] at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
> [JBossINF] at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:232) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
> [JBossINF] at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:304) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
> [JBossINF] at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:190) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
> [JBossINF] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-1.jar:1.1.1.Final-redhat-1]
> [JBossINF] at org.jboss.as.ejb3.remote.EJBRemoteTransactionPropogatingInterceptor.processInvocation(EJBRemoteTransactionPropogatingInterceptor.java:80) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
> [JBossINF] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-1.jar:1.1.1.Final-redhat-1]
> [JBossINF] at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
> [JBossINF] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-1.jar:1.1.1.Final-redhat-1]
> [JBossINF] at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
> [JBossINF] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-1.jar:1.1.1.Final-redhat-1]
> [JBossINF] at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
> [JBossINF] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-1.jar:1.1.1.Final-redhat-1]
> [JBossINF] at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
> [JBossINF] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-1.jar:1.1.1.Final-redhat-1]
> [JBossINF] at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final-redhat-1.jar:1.1.1.Final-redhat-1]
> [JBossINF] at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
> [JBossINF] at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.invokeMethod(MethodInvocationMessageHandler.java:300) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
> [JBossINF] at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$200(MethodInvocationMessageHandler.java:64) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
> [JBossINF] at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:194) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
> [JBossINF] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [rt.jar:1.6.0_30]
> [JBossINF] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_30]
> [JBossINF] at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_30]
> [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
> [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
> [JBossINF] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
> [JBossINF] at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> [JBossINF] Caused by: org.jgroups.TimeoutException: timeout sending message to perf21/ejb
> [JBossINF] at org.jgroups.blocks.MessageDispatcher.sendMessage(MessageDispatcher.java:360)
> [JBossINF] at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.processSingleCall(CommandAwareRpcDispatcher.java:263)
> [JBossINF] at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.invokeRemoteCommand(CommandAwareRpcDispatcher.java:163)
> [JBossINF] ... 65 more
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-4480) IllegalStateException can happen on clean shutdown
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-4480?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-4480:
----------------------------------
Fix Version/s: 8.0.0.Alpha1
(was: 7.2.0.CR1)
> IllegalStateException can happen on clean shutdown
> --------------------------------------------------
>
> Key: AS7-4480
> URL: https://issues.jboss.org/browse/AS7-4480
> Project: Application Server 7
> Issue Type: Bug
> Components: Web
> Affects Versions: 7.1.1.Final
> Reporter: Radoslav Husar
> Assignee: Remy Maucherat
> Fix For: 8.0.0.Alpha1
>
>
> Randomly seen in SessionBasedConcurrentTestCase.
> Implications yet unknown.
> {noformat}
> 12:17:53,337 INFO [org.infinispan.jmx.CacheJmxRegistration] (pool-15-thread-1) ISPN000031: MBeans were successfully registered to the platform mbean server.
> 12:17:53,353 INFO [org.jboss.as.clustering.infinispan] (pool-15-thread-1) JBAS010281: Started repl cache from web container
> 12:17:53,362 INFO [org.jboss.as.clustering] (MSC service thread 1-3) JBAS010238: Number of cluster members: 1
> 12:17:53,399 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.
> 12:17:53,402 INFO [org.infinispan.config.ConfigurationValidatingVisitor] (MSC service thread 1-3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.
> 12:17:53,429 INFO [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-3) ISPN000031: MBeans were successfully registered to the platform mbean server.
> 12:17:53,446 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-3) JBAS010281: Started //default-host//concurrent-session-replication cache from web container
> 12:17:53,455 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.
> 12:17:53,458 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.
> 12:17:53,627 INFO [org.jboss.web] (MSC service thread 1-3) JBAS018210: Registering web context: /concurrent-session-replication
> 12:17:54,211 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "concurrent-session-replication.war"
> 12:18:02,060 INFO [org.jboss.as.clustering] (Incoming-1,null) JBAS010225: New cluster view for partition web (id: 1, delta: 1, merge: false) : [node-0/web, node-1/web]
> 12:18:02,061 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-1,null) ISPN000094: Received new cluster view: [node-0/web|1] [node-0/web, node-1/web]
> 12:18:04,834 INFO [org.jboss.as.osgi] (MSC service thread 1-4) JBAS011943: Unregister module: Module "deployment.concurrent-session-replication.war:main" from Service Module Loader
> 12:18:05,318 INFO [org.infinispan.eviction.PassivationManagerImpl] (MSC service thread 1-1) ISPN000029: Passivating all entries to disk
> 12:18:05,320 INFO [org.infinispan.eviction.PassivationManagerImpl] (MSC service thread 1-1) ISPN000030: Passivated 0 entries in 1 milliseconds
> 12:18:05,507 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-1) JBAS010282: Stopped //default-host//concurrent-session-replication cache from web container
> 12:18:05,592 ERROR [org.apache.catalina.connector.CoyoteAdapter] (http--127.0.0.1-8080-2) An exception or error occurred in the container during the request processing: java.lang.IllegalStateException
> at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
> at org.jboss.as.connector.deployers.processors.CachedConnectionManagerSetupProcessor$CachedConnectionManagerSetupAction.setup(CachedConnectionManagerSetupProcessor.java:74)
> at org.jboss.as.web.ThreadSetupBindingListener.bind(ThreadSetupBindingListener.java:50) [jboss-as-web-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:125) [jbossweb-7.0.14.Final.jar:]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.14.Final.jar:]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.14.Final.jar:]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.14.Final.jar:]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.14.Final.jar:]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.14.Final.jar:]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931) [jbossweb-7.0.14.Final.jar:]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_29]
> 12:18:05,615 INFO [org.infinispan.eviction.PassivationManagerImpl] (pool-15-thread-1) ISPN000029: Passivating all entries to disk
> 12:18:05,617 INFO [org.infinispan.eviction.PassivationManagerImpl] (pool-15-thread-1) ISPN000030: Passivated 0 entries in 1 milliseconds
> 12:18:05,634 INFO [org.jboss.as.clustering.infinispan] (pool-15-thread-1) JBAS010282: Stopped repl cache from web container
> 12:18:05,670 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment concurrent-session-replication.war in 851ms
> 12:18:05,818 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-14-thread-1) ISPN000082: Stopping the RpcDispatcher
> 12:18:06,496 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014901: Content removed from location /home/rhusar/git/jboss-as/testsuite/integration/clust/target/jbossas-clustering-udp-0/standalone/data/content/c9/8197dce9a6e7041f12dc1342fc4126bc1aa846/content
> 12:18:06,497 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018558: Undeployed "concurrent-session-replication.war"
> 12:18:07,007 INFO [org.apache.catalina.core.StandardContext] (MSC service thread 1-1) Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/] has not been started
> 12:18:07,012 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Pausing Coyote HTTP/1.1 on http--127.0.0.1-8080
> 12:18:07,013 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Stopping Coyote HTTP/1.1 on http--127.0.0.1-8080
> 12:18:07,016 INFO [org.apache.coyote.ajp.AjpProtocol] (MSC service thread 1-3) Pausing Coyote AJP/1.3 on ajp--127.0.0.1-8009
> 12:18:07,017 INFO [org.apache.coyote.ajp.AjpProtocol] (MSC service thread 1-3) Stopping Coyote AJP/1.3 on ajp--127.0.0.1-8009
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-4817) Sessions lost on server shutdown using DIST ASYNC
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-4817?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-4817:
----------------------------------
Fix Version/s: 8.0.0.Alpha1
(was: 7.2.0.Alpha1)
> Sessions lost on server shutdown using DIST ASYNC
> --------------------------------------------------
>
> Key: AS7-4817
> URL: https://issues.jboss.org/browse/AS7-4817
> Project: Application Server 7
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 7.1.2.Final (EAP)
> Reporter: Radoslav Husar
> Assignee: Paul Ferraro
> Fix For: 8.0.0.Alpha1
>
>
> Looking at the client, after it gets 500 waits and continues with the same session it, the session is lost.
> {noformat}
> ./perf17.log:2012/05/13 17:26:24:788 EDT [DEBUG][Runner - 106] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Session assigned: ER8NvbhQixAZmhQIHUDt-Zip
> ./perf17.log:2012/05/13 17:26:24:788 EDT [DEBUG][Runner - 106] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - JvmRoute assigned: perf20
> ./perf17.log:2012/05/13 17:33:28:943 EDT [WARN ][Runner - 106] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Invalid response code: 500 Content: >
> ./perf17.log:2012/05/13 17:33:28:944 EDT [WARN ][Runner - 106] SFCORE_LOG - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Invalid response code: 500 Content: >
> ./perf17.log:2012/05/13 17:33:32:947 EDT [INFO ][Runner - 106] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Failover detected, JvmRoute changed. perf20 -> perf21
> ./perf17.log:2012/05/13 17:35:41:023 EDT [WARN ][Runner - 106] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 138, received 0, Runner: 106>
> ./perf17.log:2012/05/13 17:35:41:024 EDT [WARN ][Runner - 106] SFCORE_LOG - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 138, received 0, Runner: 106>
> {noformat}
> No exceptions in the server logs including this session
> {noformat}
> ./perf20.log:[JBossINF] 17:26:24,786 INFO [org.jboss.test.clusterbench.common.session.CommonHttpSessionServlet] (ajp-perf20/10.16.90.58:8009-10) New session created: ER8NvbhQixAZmhQIHUDt-Zip.perf20
> ./perf17.log:2012/05/13 17:26:24:788 EDT [DEBUG][Runner - 106] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Session assigned: ER8NvbhQixAZmhQIHUDt-Zip
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-4818) Stale session data received when using DIST SYNC on node shutdown
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-4818?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-4818:
----------------------------------
Fix Version/s: 8.0.0.Alpha1
(was: 7.2.0.Alpha1)
> Stale session data received when using DIST SYNC on node shutdown
> -----------------------------------------------------------------
>
> Key: AS7-4818
> URL: https://issues.jboss.org/browse/AS7-4818
> Project: Application Server 7
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 7.1.2.Final (EAP)
> Reporter: Radoslav Husar
> Assignee: Paul Ferraro
> Priority: Critical
> Labels: as713tracking
> Fix For: 8.0.0.Alpha1
>
>
> There are few occurrences when client received older data even when using DIST SYNC.
> http://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Failover/job/eap-6x...
> {noformat}
> ./perf17.log:2012/05/13 17:11:47:416 EDT [DEBUG][Runner - 968] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Session assigned: hAzyrOe0KxA51coCNbSMUsrZ
> ./perf17.log:2012/05/13 17:11:47:416 EDT [DEBUG][Runner - 968] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - JvmRoute assigned: perf18
> ./perf17.log:2012/05/13 17:14:11:542 EDT [INFO ][Runner - 968] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Failover detected, JvmRoute changed. perf18 -> perf21
> ./perf17.log:2012/05/13 17:14:15:546 EDT [WARN ][Runner - 968] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 37, received 36, Runner: 968>
> ./perf17.log:2012/05/13 17:14:15:546 EDT [WARN ][Runner - 968] SFCORE_LOG - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 37, received 36, Runner: 968>
> ./perf17.log:2012/05/13 17:21:20:224 EDT [INFO ][Runner - 968] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Failover detected, JvmRoute changed. perf21 -> perf19
> ./perf17.log:2012/05/13 17:23:01:507 EDT [INFO ][Runner - 968] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Failover detected, JvmRoute changed. perf19 -> perf21
> {noformat}
> No logging about the session (hAzyrOe0KxA51coCNbSMUsrZ) in the logs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-3310) User insn't properly informed that APR is used
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-3310?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-3310:
----------------------------------
Fix Version/s: 8.0.0.Alpha1
(was: 7.2.0.CR1)
> User insn't properly informed that APR is used
> ----------------------------------------------
>
> Key: AS7-3310
> URL: https://issues.jboss.org/browse/AS7-3310
> Project: Application Server 7
> Issue Type: Bug
> Components: Web
> Affects Versions: 7.1.0.Beta1b
> Reporter: Rostislav Svoboda
> Assignee: Remy Maucherat
> Fix For: 8.0.0.Alpha1
>
>
> AS7 log doesn't show sufficient information that APR is used or not. Currently the only clue is that org.apache.coyote.http11.Http11AprProtocol is used instead of org.apache.coyote.http11.Http11Protocol. But it's implementation details and many users can miss that.
> Add log message to inform users if APR is used or not!
> For example APR affect https connector definition which must use openssl based keys and not keystore. And if users do not know APR is used they can be easily confused and blame AS7 as broken.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-4727) Minor logging: 'unloaded' string is not passed to JBAS018079 logging message
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-4727?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-4727:
----------------------------------
Fix Version/s: 8.0.0.Alpha1
(was: 7.2.0.Alpha1)
> Minor logging: 'unloaded' string is not passed to JBAS018079 logging message
> ----------------------------------------------------------------------------
>
> Key: AS7-4727
> URL: https://issues.jboss.org/browse/AS7-4727
> Project: Application Server 7
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 7.1.1.Final
> Reporter: Radoslav Husar
> Assignee: Paul Ferraro
> Priority: Minor
> Fix For: 8.0.0.Alpha1
>
>
> Nothing gets passed to message as unloaded
> From code:
> {code}
> @Message(id = 18079, value = "Failed to passivate %s session %s")
> String failToPassivate(String unloaded, String id);
> {code}
> so in logging you get
> {code}
> [JBossINF] 19:19:07,331 ERROR [org.apache.catalina.session.ManagerBase] (ContainerBackgroundProcessor[StandardEngine[jboss.web]])
> JBAS018079: Failed to passivate session gXJyH6Cd0xnPT2Gbw8Bb8Yh8:
> ...
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months