[JBoss JIRA] (AS7-2227) Port the legacy jmx-console to AS7
by Dimitris Andreadis (Created) (JIRA)
Port the legacy jmx-console to AS7
----------------------------------
Key: AS7-2227
URL: https://issues.jboss.org/browse/AS7-2227
Project: Application Server 7
Issue Type: Feature Request
Components: Console
Affects Versions: 7.1.0.Alpha1, 7.0.2.Final
Reporter: Dimitris Andreadis
Assignee: Dimitris Andreadis
Fix For: 7.1.0.Beta1
I've seen a few people asking for a port of the old jmx-console to AS7, for monitoring purposes, until equivalent functionality is available through the new GWT-based console.
I've ported the old console in this branch:
https://github.com/dandreadis/jboss-as/commits/jmx-console
It only includes a new top-level directory 'jmx-console'. The directory is not build by default, and when you build it manually it does not alter the server configuration in any way, you need to manually copy the resulting target/jboss-as-jmx-console-VERSION.war to the server deployment directory (and rename it to jmx-console.war)
If there is interest, it could be included in the AS7 distro in some top level 'legacy' directory so it is not deployed by default?
The resulting .war is attached on this JIRA, in case someone wants to use it. It work just as well on AS 7.0.2 and the latest AS 7.1.x development branch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-3099) <distributable/> application with SFSBs fail to deploy in default configuration (standalone.xml)
by Radoslav Husar (Created) (JIRA)
<distributable/> application with SFSBs fail to deploy in default configuration (standalone.xml)
------------------------------------------------------------------------------------------------
Key: AS7-3099
URL: https://issues.jboss.org/browse/AS7-3099
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Affects Versions: 7.1.0.Beta1b, 7.1.0.Beta1
Reporter: Radoslav Husar
Assignee: Paul Ferraro
Fix For: 7.1.0.Final
Related to AS7-1313 but with @Clustered EJBs. The annotation should be just ignored in non-HA profiles.
{noformat}
13:52:48,772 INFO [org.jboss.modules] JBoss Modules version 1.1.0.CR4
13:52:49,024 INFO [org.jboss.msc] JBoss MSC version 1.0.1.GA
13:52:49,074 INFO [org.jboss.as] JBoss AS 7.1.0.CR1-SNAPSHOT "Tesla" starting
13:52:50,169 INFO [org.xnio] XNIO Version 3.0.0.CR5
13:52:50,176 INFO [org.jboss.as] Creating http management service using socket-binding (management-http)
13:52:50,192 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.0.CR5
13:52:50,217 INFO [org.jboss.remoting] JBoss Remoting version 3.2.0.CR6-darranl-1
13:52:50,269 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
13:52:50,312 INFO [org.jboss.as.remoting] (MSC service thread 1-3) Listening on /127.0.0.1:9999
13:52:50,404 INFO [org.jboss.as.clustering] (ServerService Thread Pool -- 30) JBAS010300: Activating Infinispan subsystem.
13:52:50,466 INFO [org.jboss.as.connector] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.6.Final)
13:52:50,467 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 26) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
13:52:50,476 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
13:52:50,492 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011910: Activating OSGi Subsystem
13:52:50,504 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) Activating Security Subsystem
13:52:50,581 INFO [org.jboss.as.security] (MSC service thread 1-2) Picketbox version=4.0.6.Beta2
13:52:50,607 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
13:52:50,627 INFO [org.jboss.as.naming] (MSC service thread 1-3) JBAS011802: Starting Naming Service
13:52:50,675 INFO [org.jboss.as.jaxr] (MSC service thread 1-3) Binding JAXR ConnectionFactory: java:jboss/jaxr/ConnectionFactory
13:52:50,678 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mail/Default]
13:52:50,723 INFO [org.jboss.as.remoting] (MSC service thread 1-3) Listening on /127.0.0.1:4447
13:52:50,964 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) null null
13:52:51,227 INFO [org.apache.coyote.http11.Http11AprProtocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
13:52:51,526 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
13:52:52,144 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory /home/rhusar/Download/jboss-as-7.1.0.CR1-SNAPSHOT/standalone/deployments
13:52:52,190 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.1.0.CR1-SNAPSHOT "Tesla" started in 3642ms - Started 130 of 200 services (68 services are passive or on-demand)
13:52:52,223 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) Starting deployment of "clusterbench-ee6.ear"
13:52:52,364 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "clusterbench-ee6-ejb.jar"
13:52:52,364 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) Starting deployment of "clusterbench-ee6-web.war"
13:52:52,493 INFO [org.jboss.weld] (MSC service thread 1-4) Processing CDI deployment: clusterbench-ee6.ear
13:52:52,575 INFO [org.jboss.weld] (MSC service thread 1-1) Processing CDI deployment: clusterbench-ee6-ejb.jar
13:52:52,576 INFO [org.jboss.weld] (MSC service thread 1-2) Processing CDI deployment: clusterbench-ee6-web.war
13:52:52,585 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named RemoteSingletonSBImpl in deployment unit subdeployment "clusterbench-ee6-ejb.jar" of deployment "clusterbench-ee6.ear" are as follows:
java:global/clusterbench-ee6/clusterbench-ee6-ejb/RemoteSingletonSBImpl!org.jboss.test.clusterbench.ejb.singleton.RemoteSingletonSB
java:app/clusterbench-ee6-ejb/RemoteSingletonSBImpl!org.jboss.test.clusterbench.ejb.singleton.RemoteSingletonSB
java:module/RemoteSingletonSBImpl!org.jboss.test.clusterbench.ejb.singleton.RemoteSingletonSB
java:global/clusterbench-ee6/clusterbench-ee6-ejb/RemoteSingletonSBImpl!org.jboss.test.clusterbench.ejb.singleton.RemoteSingletonSBImpl
java:app/clusterbench-ee6-ejb/RemoteSingletonSBImpl!org.jboss.test.clusterbench.ejb.singleton.RemoteSingletonSBImpl
java:module/RemoteSingletonSBImpl!org.jboss.test.clusterbench.ejb.singleton.RemoteSingletonSBImpl
13:52:52,589 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named RemoteStatefulSBImpl in deployment unit subdeployment "clusterbench-ee6-ejb.jar" of deployment "clusterbench-ee6.ear" are as follows:
java:global/clusterbench-ee6/clusterbench-ee6-ejb/RemoteStatefulSBImpl!org.jboss.test.clusterbench.ejb.stateful.RemoteStatefulSB
java:app/clusterbench-ee6-ejb/RemoteStatefulSBImpl!org.jboss.test.clusterbench.ejb.stateful.RemoteStatefulSB
java:module/RemoteStatefulSBImpl!org.jboss.test.clusterbench.ejb.stateful.RemoteStatefulSB
java:global/clusterbench-ee6/clusterbench-ee6-ejb/RemoteStatefulSBImpl
java:app/clusterbench-ee6-ejb/RemoteStatefulSBImpl
java:module/RemoteStatefulSBImpl
13:52:52,592 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named LocalStatefulSB in deployment unit subdeployment "clusterbench-ee6-ejb.jar" of deployment "clusterbench-ee6.ear" are as follows:
java:global/clusterbench-ee6/clusterbench-ee6-ejb/LocalStatefulSB!org.jboss.test.clusterbench.ejb.stateful.LocalStatefulSB
java:app/clusterbench-ee6-ejb/LocalStatefulSB!org.jboss.test.clusterbench.ejb.stateful.LocalStatefulSB
java:module/LocalStatefulSB!org.jboss.test.clusterbench.ejb.stateful.LocalStatefulSB
java:global/clusterbench-ee6/clusterbench-ee6-ejb/LocalStatefulSB
java:app/clusterbench-ee6-ejb/LocalStatefulSB
java:module/LocalStatefulSB
13:52:52,593 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named LocalSingletonSB in deployment unit subdeployment "clusterbench-ee6-ejb.jar" of deployment "clusterbench-ee6.ear" are as follows:
java:global/clusterbench-ee6/clusterbench-ee6-ejb/LocalSingletonSB!org.jboss.test.clusterbench.ejb.singleton.LocalSingletonSB
java:app/clusterbench-ee6-ejb/LocalSingletonSB!org.jboss.test.clusterbench.ejb.singleton.LocalSingletonSB
java:module/LocalSingletonSB!org.jboss.test.clusterbench.ejb.singleton.LocalSingletonSB
java:global/clusterbench-ee6/clusterbench-ee6-ejb/LocalSingletonSB
java:app/clusterbench-ee6-ejb/LocalSingletonSB
java:module/LocalSingletonSB
13:52:52,617 INFO [org.jboss.weld] (MSC service thread 1-1) Starting Services for CDI deployment: clusterbench-ee6.ear
13:52:52,690 INFO [org.jboss.weld.Version] (MSC service thread 1-1) WELD-000900 SNAPSHOT
13:52:52,805 INFO [org.jboss.weld] (MSC service thread 1-1) Starting weld service
13:52:53,428 WARN [org.jboss.as.web.deployment.JBossContextConfig] (MSC service thread 1-3) Clustering not supported, falling back to non-clustered session manager.: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.infinispan.web.___defaultcache not found
at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:447)
at org.jboss.as.clustering.web.infinispan.SessionCacheSource.getCache(SessionCacheSource.java:42)
at org.jboss.as.clustering.web.infinispan.DistributedCacheManagerFactory.getDistributedCacheManager(DistributedCacheManagerFactory.java:91)
at org.jboss.as.web.session.DistributableSessionManager.<init>(DistributableSessionManager.java:176) [jboss-as-web-7.1.0.CR1-SNAPSHOT.jar:]
at org.jboss.as.web.session.DistributableSessionManager.<init>(DistributableSessionManager.java:144) [jboss-as-web-7.1.0.CR1-SNAPSHOT.jar:]
at org.jboss.as.web.deployment.JBossContextConfig.processWebMetaData(JBossContextConfig.java:280) [jboss-as-web-7.1.0.CR1-SNAPSHOT.jar:]
at org.jboss.as.web.deployment.JBossContextConfig.applicationWebConfig(JBossContextConfig.java:164) [jboss-as-web-7.1.0.CR1-SNAPSHOT.jar:]
at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:417) [jbossweb-7.0.6.Final.jar:]
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:182) [jbossweb-7.0.6.Final.jar:]
at org.jboss.as.web.deployment.JBossContextConfig.lifecycleEvent(JBossContextConfig.java:157) [jboss-as-web-7.1.0.CR1-SNAPSHOT.jar:]
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:115) [jbossweb-7.0.6.Final.jar:]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3790) [jbossweb-7.0.6.Final.jar:]
at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:77) [jboss-as-web-7.1.0.CR1-SNAPSHOT.jar:]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_29]
13:52:53,485 INFO [org.jboss.web] (MSC service thread 1-3) registering web context: /clusterbench
13:52:53,693 INFO [org.jboss.as.deployment] (DeploymentScanner-threads - 2) Deployment of "clusterbench-ee6.ear" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.subunit.\"clusterbench-ee6.ear\".\"clusterbench-ee6-ejb.jar\".component.RemoteStatefulSBImpl.CREATEjboss.ejb.cache.clustered-sfsb-defaultMissing[jboss.deployment.subunit.\"clusterbench-ee6.ear\".\"clusterbench-ee6-ejb.jar\".component.RemoteStatefulSBImpl.CREATEjboss.ejb.cache.clustered-sfsb-default]","jboss.deployment.subunit.\"clusterbench-ee6.ear\".\"clusterbench-ee6-ejb.jar\".component.LocalStatefulSB.CREATEjboss.ejb.cache.clustered-sfsb-defaultMissing[jboss.deployment.subunit.\"clusterbench-ee6.ear\".\"clusterbench-ee6-ejb.jar\".component.LocalStatefulSB.CREATEjboss.ejb.cache.clustered-sfsb-default]"]}
13:52:53,750 INFO [org.jboss.weld] (MSC service thread 1-3) Stopping weld service
13:52:53,770 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Stopped deployment clusterbench-ee6-web.war in 75ms
13:52:53,774 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) Stopped deployment clusterbench-ee6-ejb.jar in 79ms
13:52:53,775 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Stopped deployment clusterbench-ee6.ear in 82ms
13:52:53,776 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.ejb.cache.clustered-sfsb-default (missing) dependents: [service jboss.deployment.subunit."clusterbench-ee6.ear"."clusterbench-ee6-ejb.jar".component.LocalStatefulSB.CREATE, service jboss.deployment.subunit."clusterbench-ee6.ear"."clusterbench-ee6-ejb.jar".component.RemoteStatefulSBImpl.CREATE]
13:52:53,777 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.subunit.\"clusterbench-ee6.ear\".\"clusterbench-ee6-ejb.jar\".component.RemoteStatefulSBImpl.CREATEjboss.ejb.cache.clustered-sfsb-defaultMissing[jboss.deployment.subunit.\"clusterbench-ee6.ear\".\"clusterbench-ee6-ejb.jar\".component.RemoteStatefulSBImpl.CREATEjboss.ejb.cache.clustered-sfsb-default]","jboss.deployment.subunit.\"clusterbench-ee6.ear\".\"clusterbench-ee6-ejb.jar\".component.LocalStatefulSB.CREATEjboss.ejb.cache.clustered-sfsb-defaultMissing[jboss.deployment.subunit.\"clusterbench-ee6.ear\".\"clusterbench-ee6-ejb.jar\".component.LocalStatefulSB.CREATEjboss.ejb.cache.clustered-sfsb-default]"]}}}
^C13:53:22,938 INFO [org.jboss.as.controller] (MSC service thread 1-1) JBAS014774: Service status report
JBAS014776: Newly corrected services:
service jboss.ejb.cache.clustered-sfsb-default (new available)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-3158) Requests around cluster memebership change with REPL+SYNC cache could take up to 17 seconds to respond
by Radoslav Husar (Created) (JIRA)
Requests around cluster memebership change with REPL+SYNC cache could take up to 17 seconds to respond
------------------------------------------------------------------------------------------------------
Key: AS7-3158
URL: https://issues.jboss.org/browse/AS7-3158
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Affects Versions: 7.1.0.CR1b, 7.1.0.CR1
Reporter: Radoslav Husar
Assignee: Paul Ferraro
Priority: Critical
Fix For: 7.1.0.Final
10:59:22:800 one of the 4 nodes was brought up
10:59:23:879 requested url
10:59:41:390 clustered replied 17.511 seconds later
nothing in the logs
{noformat}
2012/01/02 10:59:15:865 EST [DEBUG][Runner - 0] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Request took 11 ms.
2012/01/02 10:59:15:866 EST [DEBUG][Runner - 0] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Response size is 2. Processing Response Body.
2012/01/02 10:59:19:866 EST [DEBUG][Runner - 0] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Requesting URL: http://perf17:8080/clusterbench/session
2012/01/02 10:59:19:878 EST [DEBUG][Runner - 0] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Request took 12 ms.
2012/01/02 10:59:19:879 EST [DEBUG][Runner - 0] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Response size is 2. Processing Response Body.
2012/01/02 10:59:19:900 EST [INFO ][TestController] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Bringing back node 1 (perf19)
2012/01/02 10:59:22:800 EST [INFO ][TestController] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Node 1 (perf19) is up.
2012/01/02 10:59:22:800 EST [INFO ][TestController] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Cluster state: [UP, UP, UP, UP].
2012/01/02 10:59:23:879 EST [DEBUG][Runner - 0] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Requesting URL: http://perf17:8080/clusterbench/session
2012/01/02 10:59:24:212 EST [INFO ][StatsRunner] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Total: Sessions: 1, active: 1, samples: 2, throughput 0.2 samples/s, 0.0 MB/s, mean response: 11 ms, sampling errors: 0, invalid samples: 0, valid samples: 2 (100%)
2012/01/02 10:59:24:213 EST [DEBUG][StatsRunner] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Updated totals: Sessions: 0, active: 30, samples: 76, throughput 7.6 samples/s, 0.0 MB/s, mean response: 11 ms, sampling errors: 0, invalid samples: 0, valid samples: 76 (100%)
2012/01/02 10:59:24:213 EST [INFO ][StatsRunner] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - perf18: Sessions: 1, active: 0, samples: 0, throughput 0.0 samples/s, 0.0 MB/s, mean response: 0 ms, sampling errors: 0, invalid samples: 0, valid samples: 0 (0%)
2012/01/02 10:59:24:213 EST [INFO ][StatsRunner] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - perf19: Sessions: 1, active: 0, samples: 0, throughput 0.0 samples/s, 0.0 MB/s, mean response: 0 ms, sampling errors: 0, invalid samples: 0, valid samples: 0 (0%)
2012/01/02 10:59:24:213 EST [INFO ][StatsRunner] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - perf20: Sessions: 1, active: 1, samples: 2, throughput 0.2 samples/s, 0.0 MB/s, mean response: 11 ms, sampling errors: 0, invalid samples: 0, valid samples: 2 (100%)
2012/01/02 10:59:34:213 EST [INFO ][StatsRunner] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Total: Sessions: 1, active: 0, samples: 0, throughput 0.0 samples/s, 0.0 MB/s, mean response: 0 ms, sampling errors: 0, invalid samples: 0, valid samples: 0 (0%)
2012/01/02 10:59:34:214 EST [DEBUG][StatsRunner] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Updated totals: Sessions: 1, active: 30, samples: 76, throughput 7.6 samples/s, 0.0 MB/s, mean response: 11 ms, sampling errors: 0, invalid samples: 0, valid samples: 76 (100%)
2012/01/02 10:59:34:214 EST [INFO ][StatsRunner] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - perf18: Sessions: 1, active: 0, samples: 0, throughput 0.0 samples/s, 0.0 MB/s, mean response: 0 ms, sampling errors: 0, invalid samples: 0, valid samples: 0 (0%)
2012/01/02 10:59:34:214 EST [INFO ][StatsRunner] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - perf19: Sessions: 1, active: 0, samples: 0, throughput 0.0 samples/s, 0.0 MB/s, mean response: 0 ms, sampling errors: 0, invalid samples: 0, valid samples: 0 (0%)
2012/01/02 10:59:34:214 EST [INFO ][StatsRunner] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - perf20: Sessions: 1, active: 0, samples: 0, throughput 0.0 samples/s, 0.0 MB/s, mean response: 0 ms, sampling errors: 0, invalid samples: 0, valid samples: 0 (0%)
2012/01/02 10:59:41:390 EST [DEBUG][Runner - 0] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Request took 17511 ms.
2012/01/02 10:59:41:390 EST [DEBUG][Runner - 0] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Response size is 2. Processing Response Body.
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-3133) Using distributable cache results in ClassCastException: JGroupsAddress cannot be cast to SessionKey
by Radoslav Husar (Created) (JIRA)
Using distributable cache results in ClassCastException: JGroupsAddress cannot be cast to SessionKey
----------------------------------------------------------------------------------------------------
Key: AS7-3133
URL: https://issues.jboss.org/browse/AS7-3133
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Affects Versions: 7.1.0.CR1
Reporter: Radoslav Husar
Assignee: Richard Achmatowicz
Priority: Critical
Fix For: 7.1.0.Final
as-7.1.0.CR1-SNAPSHOT/standalone/data/messaginglargemessages,pagingDirectory=/tmp/hudson/jboss-as-7.1.0.CR1-SNAPSHOT/standalone/data/messagingpaging)
[JBossINF] 08:58:28,248 INFO [org.jboss.as.modcluster] (MSC service thread 1-12) JBAS011704: Mod_cluster uses default load balancer provider
[JBossINF] 08:58:28,276 WARNING [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-2) Security risk! It has been detected that the cluster admin user and password have not been changed from the installation default. Please see the HornetQ user guide, cluster chapter, for instructions on how to do this.
[JBossINF] 08:58:28,294 INFO [org.apache.coyote.http11.Http11AprProtocol] (MSC service thread 1-6) Starting Coyote HTTP/1.1 on http-perf18-10.16.90.54-8080
[JBossINF] 08:58:28,299 INFO [org.apache.coyote.ajp.AjpAprProtocol] (MSC service thread 1-3) Starting Coyote AJP/1.3 on ajp-perf18-10.16.90.54-8009
[JBossINF] 08:58:28,311 INFO [org.jboss.modcluster.ModClusterService] (MSC service thread 1-12) Initializing mod_cluster 1.2.0.Beta2
[JBossINF] 08:58:28,337 INFO [org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl] (MSC service thread 1-12) Listening to proxy advertisements on 230.3.90.52:23364
[JBossINF] 08:58:28,349 INFO [org.jboss.as.jacorb] (MSC service thread 1-13) CORBA ORB Service Started
[JBossINF] 08:58:28,442 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
[JBossINF] 08:58:28,450 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-2) Started Netty Acceptor version 3.2.3.Final-r${buildNumber} perf18:5445 for CORE protocol
[JBossINF] 08:58:28,452 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-2) Started Netty Acceptor version 3.2.3.Final-r${buildNumber} perf18:5455 for CORE protocol
[JBossINF] 08:58:28,453 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-2) Server is now live
[JBossINF] 08:58:28,454 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-2) HornetQ Server version 2.2.7.Final (HQ_2_2_7_FINAL_AS7, 121) [06237b66-2ca5-11e1-88a6-d48564693bb6] started
[JBossINF] 08:58:28,454 INFO [org.jboss.as.jacorb] (MSC service thread 1-4) CORBA Naming Service Started
[JBossINF] 08:58:28,457 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-7) trying to deploy queue jms.topic.testTopic
[JBossINF] 08:58:28,461 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-10) JBAS010406: Registered connection factory java:/JmsXA
[JBossINF] 08:58:28,470 INFO [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-10) HornetQ resource adaptor started
[JBossINF] 08:58:28,470 INFO [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-10) IJ020002: Deployed: file://RaActivatorhornetq-ra
[JBossINF] 08:58:28,473 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-4) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
[JBossINF] 08:58:28,532 INFO [org.jboss.as.messaging] (MSC service thread 1-7) JBAS011601: Bound messaging object to jndi name java:/topic/test
[JBossINF] 08:58:28,533 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-13) trying to deploy queue jms.queue.testQueue
[JBossINF] 08:58:28,550 INFO [org.jboss.as.messaging] (MSC service thread 1-13) JBAS011601: Bound messaging object to jndi name java:/queue/test
[JBossINF] 08:58:28,563 INFO [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011601: Bound messaging object to jndi name java:/RemoteConnectionFactory
[JBossINF] 08:58:28,564 INFO [org.jboss.as.messaging] (MSC service thread 1-16) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
[JBossINF] 08:58:28,851 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-11) JBAS015012: Started FileSystemDeploymentService for directory /tmp/hudson/jboss-as-7.1.0.CR1-SNAPSHOT/standalone/deployments
[JBossINF] 08:58:28,873 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.1.0.CR1-SNAPSHOT "Tesla" started in 2549ms - Started 153 of 261 services (103 services are passive or on-demand)
2011/12/22 08:58:28:873 EST [DEBUG][Thread-24] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - JBossStartup, server started!
[JBossINF] 08:58:28,887 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) Starting deployment of "clusterbench-ee6.ear"
[JBossINF] 08:58:28,952 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) Starting deployment of "clusterbench-ee6-ejb.jar"
[JBossINF] 08:58:28,952 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) Starting deployment of "clusterbench-ee6-web.war"
[JBossINF] 08:58:29,091 INFO [org.jboss.weld] (MSC service thread 1-10) Processing CDI deployment: clusterbench-ee6.ear
[JBossINF] 08:58:29,145 INFO [org.jboss.weld] (MSC service thread 1-7) Processing CDI deployment: clusterbench-ee6-web.war
[JBossINF] 08:58:29,146 INFO [org.jboss.weld] (MSC service thread 1-14) Processing CDI deployment: clusterbench-ee6-ejb.jar
[JBossINF] 08:58:29,149 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-14) JNDI bindings for session bean named RemoteSingletonSBImpl in deployment unit subdeployment "clusterbench-ee6-ejb.jar" of deployment "clusterbench-ee6.ear" are as follows:
[JBossINF]
[JBossINF] java:global/clusterbench-ee6/clusterbench-ee6-ejb/RemoteSingletonSBImpl!org.jboss.test.clusterbench.ejb.singleton.RemoteSingletonSB
[JBossINF] java:app/clusterbench-ee6-ejb/RemoteSingletonSBImpl!org.jboss.test.clusterbench.ejb.singleton.RemoteSingletonSB
[JBossINF] java:module/RemoteSingletonSBImpl!org.jboss.test.clusterbench.ejb.singleton.RemoteSingletonSB
[JBossINF] java:global/clusterbench-ee6/clusterbench-ee6-ejb/RemoteSingletonSBImpl!org.jboss.test.clusterbench.ejb.singleton.RemoteSingletonSBImpl
[JBossINF] java:app/clusterbench-ee6-ejb/RemoteSingletonSBImpl!org.jboss.test.clusterbench.ejb.singleton.RemoteSingletonSBImpl
[JBossINF] java:module/RemoteSingletonSBImpl!org.jboss.test.clusterbench.ejb.singleton.RemoteSingletonSBImpl
[JBossINF]
[JBossINF] 08:58:29,149 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-14) JNDI bindings for session bean named RemoteStatefulSBImpl in deployment unit subdeployment "clusterbench-ee6-ejb.jar" of deployment "clusterbench-ee6.ear" are as follows:
[JBossINF]
[JBossINF] java:global/clusterbench-ee6/clusterbench-ee6-ejb/RemoteStatefulSBImpl!org.jboss.test.clusterbench.ejb.stateful.RemoteStatefulSB
[JBossINF] java:app/clusterbench-ee6-ejb/RemoteStatefulSBImpl!org.jboss.test.clusterbench.ejb.stateful.RemoteStatefulSB
[JBossINF] java:module/RemoteStatefulSBImpl!org.jboss.test.clusterbench.ejb.stateful.RemoteStatefulSB
[JBossINF] java:global/clusterbench-ee6/clusterbench-ee6-ejb/RemoteStatefulSBImpl
[JBossINF] java:app/clusterbench-ee6-ejb/RemoteStatefulSBImpl
[JBossINF] java:module/RemoteStatefulSBImpl
[JBossINF]
[JBossINF] 08:58:29,150 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-14) JNDI bindings for session bean named LocalStatefulSB in deployment unit subdeployment "clusterbench-ee6-ejb.jar" of deployment "clusterbench-ee6.ear" are as follows:
[JBossINF]
[JBossINF] java:global/clusterbench-ee6/clusterbench-ee6-ejb/LocalStatefulSB!org.jboss.test.clusterbench.ejb.stateful.LocalStatefulSB
[JBossINF] java:app/clusterbench-ee6-ejb/LocalStatefulSB!org.jboss.test.clusterbench.ejb.stateful.LocalStatefulSB
[JBossINF] java:module/LocalStatefulSB!org.jboss.test.clusterbench.ejb.stateful.LocalStatefulSB
[JBossINF] java:global/clusterbench-ee6/clusterbench-ee6-ejb/LocalStatefulSB
[JBossINF] java:app/clusterbench-ee6-ejb/LocalStatefulSB
[JBossINF] java:module/LocalStatefulSB
[JBossINF]
[JBossINF] 08:58:29,150 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-14) JNDI bindings for session bean named LocalSingletonSB in deployment unit subdeployment "clusterbench-ee6-ejb.jar" of deployment "clusterbench-ee6.ear" are as follows:
[JBossINF]
[JBossINF] java:global/clusterbench-ee6/clusterbench-ee6-ejb/LocalSingletonSB!org.jboss.test.clusterbench.ejb.singleton.LocalSingletonSB
[JBossINF] java:app/clusterbench-ee6-ejb/LocalSingletonSB!org.jboss.test.clusterbench.ejb.singleton.LocalSingletonSB
[JBossINF] java:module/LocalSingletonSB!org.jboss.test.clusterbench.ejb.singleton.LocalSingletonSB
[JBossINF] java:global/clusterbench-ee6/clusterbench-ee6-ejb/LocalSingletonSB
[JBossINF] java:app/clusterbench-ee6-ejb/LocalSingletonSB
[JBossINF] java:module/LocalSingletonSB
[JBossINF]
[JBossINF] 08:58:29,182 INFO [org.jboss.weld] (MSC service thread 1-8) Starting Services for CDI deployment: clusterbench-ee6.ear
[JBossINF] 08:58:29,243 INFO [org.jboss.weld.Version] (MSC service thread 1-8) WELD-000900 1.1.4 (Final)
[JBossINF] 08:58:29,263 INFO [org.jboss.weld] (MSC service thread 1-13) Starting weld service
[JBossINF] 08:58:29,792 INFO [stdout] (MSC service thread 1-10)
[JBossINF] 08:58:29,792 INFO [stdout] (MSC service thread 1-10) -------------------------------------------------------------------
[JBossINF] 08:58:29,792 INFO [stdout] (MSC service thread 1-10) GMS: address=perf18/sfsb, cluster=sfsb, physical address=10.16.90.54:55200
[JBossINF] 08:58:29,792 INFO [stdout] (MSC service thread 1-10) -------------------------------------------------------------------
[JBossINF] 08:58:29,808 INFO [stdout] (MSC service thread 1-5)
[JBossINF] 08:58:29,809 INFO [stdout] (MSC service thread 1-5) -------------------------------------------------------------------
[JBossINF] 08:58:29,809 INFO [stdout] (MSC service thread 1-5) GMS: address=perf18/web, cluster=web, physical address=10.16.90.54:55200
[JBossINF] 08:58:29,809 INFO [stdout] (MSC service thread 1-5) -------------------------------------------------------------------
[JBossINF] 08:58:31,835 INFO [org.jboss.as.clustering.CoreGroupCommunicationService.web] (MSC service thread 1-15) JBAS010207: Number of cluster members: 1
[JBossINF] 08:58:31,835 INFO [org.jboss.as.clustering.CoreGroupCommunicationService.sfsb] (MSC service thread 1-3) JBAS010207: Number of cluster members: 1
[JBossINF] 08:58:32,204 WARN [org.infinispan.config.ConfigurationValidatingVisitor] (MSC service thread 1-12) ISPN000152: Passivation configured without a valid eviction policy. This could mean that the cache store will never get used unless code calls Cache.evict() manually.
[JBossINF] 08:58:32,337 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000078: Starting JGroups Channel
[JBossINF] 08:58:32,337 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-12) ISPN000078: Starting JGroups Channel
[JBossINF] 08:58:32,340 WARNING [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (MSC service thread 1-6) Channel Muxer already has a default up handler installed (org.jboss.as.clustering.jgroups.ClassLoaderAwareUpHandler@39223bf0) but now it is being overridden
[JBossINF] 08:58:32,340 WARNING [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (MSC service thread 1-12) Channel Muxer already has a default up handler installed (org.jboss.as.clustering.jgroups.ClassLoaderAwareUpHandler@768d26dd) but now it is being overridden
[JBossINF] 08:58:32,341 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000094: Received new cluster view: [perf18/sfsb|0] [perf18/sfsb]
[JBossINF] 08:58:32,341 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-12) ISPN000094: Received new cluster view: [perf18/web|0] [perf18/web]
[JBossINF] 08:58:32,342 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-12) ISPN000079: Cache local address is perf18/web, physical addresses are [10.16.90.54:55200]
[JBossINF] 08:58:32,342 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000079: Cache local address is perf18/sfsb, physical addresses are [10.16.90.54:55200]
[JBossINF] 08:58:32,346 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-12) ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.0.CR1
[JBossINF] 08:58:32,346 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-6) ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.0.CR1
[JBossINF] 08:58:32,434 INFO [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-10) ISPN000031: MBeans were successfully registered to the platform mbean server.
[JBossINF] 08:58:32,449 INFO [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-6) ISPN000031: MBeans were successfully registered to the platform mbean server.
[JBossINF] 08:58:32,450 INFO [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-12) ISPN000031: MBeans were successfully registered to the platform mbean server.
[JBossINF] 08:58:32,473 INFO [org.jboss.as.clustering] (MSC service thread 1-10) JBAS010301: Started registry cache from web container
[JBossINF] 08:58:32,473 INFO [org.jboss.as.clustering] (MSC service thread 1-12) JBAS010301: Started dist cache from web container
[JBossINF] 08:58:32,473 INFO [org.jboss.as.clustering] (MSC service thread 1-6) JBAS010301: Started repl cache from sfsb container
[JBossINF] 08:58:32,533 INFO [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-8) ISPN000031: MBeans were successfully registered to the platform mbean server.
[JBossINF] 08:58:32,535 INFO [org.jboss.as.clustering] (MSC service thread 1-8) JBAS010301: Started org.jboss.test.clusterbench.ejb.stateful.LocalStatefulSB cache from sfsb container
[JBossINF] 08:58:32,540 INFO [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-5) ISPN000031: MBeans were successfully registered to the platform mbean server.
[JBossINF] 08:58:32,543 INFO [org.jboss.as.clustering] (MSC service thread 1-5) JBAS010301: Started org.jboss.test.clusterbench.ejb.stateful.RemoteStatefulSBImpl cache from sfsb container
[JBossINF] 08:58:32,546 ERROR [org.apache.catalina.session.ManagerBase] (MSC service thread 1-3) Unable to start manager.: java.lang.ClassCastException: org.infinispan.remoting.transport.jgroups.JGroupsAddress cannot be cast to org.jboss.as.clustering.web.infinispan.SessionKey
[JBossINF] at org.jboss.as.clustering.web.infinispan.DistributedCacheManager.getSessionIds(DistributedCacheManager.java:391)
[JBossINF] at org.jboss.as.web.session.DistributableSessionManager.initializeUnloadedSessions(DistributableSessionManager.java:277) [jboss-as-web-7.1.0.CR1-SNAPSHOT.jar:7.1.0.CR1-SNAPSHOT]
[JBossINF] at org.jboss.as.web.session.DistributableSessionManager.start(DistributableSessionManager.java:179) [jboss-as-web-7.1.0.CR1-SNAPSHOT.jar:7.1.0.CR1-SNAPSHOT]
[JBossINF] at org.apache.catalina.core.ContainerBase.setManager(ContainerBase.java:459) [jbossweb-7.0.7.Final.jar:]
[JBossINF] at org.jboss.as.web.deployment.JBossContextConfig.processWebMetaData(JBossContextConfig.java:284) [jboss-as-web-7.1.0.CR1-SNAPSHOT.jar:7.1.0.CR1-SNAPSHOT]
[JBossINF] at org.jboss.as.web.deployment.JBossContextConfig.applicationWebConfig(JBossContextConfig.java:168) [jboss-as-web-7.1.0.CR1-SNAPSHOT.jar:7.1.0.CR1-SNAPSHOT]
[JBossINF] at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:417) [jbossweb-7.0.7.Final.jar:]
[JBossINF] at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:182) [jbossweb-7.0.7.Final.jar:]
[JBossINF] at org.jboss.as.web.deployment.JBossContextConfig.lifecycleEvent(JBossContextConfig.java:161) [jboss-as-web-7.1.0.CR1-SNAPSHOT.jar:7.1.0.CR1-SNAPSHOT]
[JBossINF] at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:115) [jbossweb-7.0.7.Final.jar:]
[JBossINF] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3790) [jbossweb-7.0.7.Final.jar:]
[JBossINF] at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:77) [jboss-as-web-7.1.0.CR1-SNAPSHOT.jar:7.1.0.CR1-SNAPSHOT]
[JBossINF] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
[JBossINF] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
[JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29]
[JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29]
[JBossINF] at java.lang.Thread.run(Thread.java:662) [:1.6.0_29]
[JBossINF]
[JBossINF] 08:58:32,548 ERROR [org.apache.catalina.core.ContainerBase] (MSC service thread 1-3) ContainerBase.setManager: start: : LifecycleException: java.lang.ClassCastException: org.infinispan.remoting.transport.jgroups.JGroupsAddress cannot be cast to org.jboss.as.clustering.web.infinispan.SessionKey
[JBossINF] at org.jboss.as.web.session.DistributableSessionManager.start(DistributableSessionManager.java:191) [jboss-as-web-7.1.0.CR1-SNAPSHOT.jar:7.1.0.CR1-SNAPSHOT]
[JBossINF] at org.apache.catalina.core.ContainerBase.setManager(ContainerBase.java:459) [jbossweb-7.0.7.Final.jar:]
[JBossINF] at org.jboss.as.web.deployment.JBossContextConfig.processWebMetaData(JBossContextConfig.java:284) [jboss-as-web-7.1.0.CR1-SNAPSHOT.jar:7.1.0.CR1-SNAPSHOT]
[JBossINF] at org.jboss.as.web.deployment.JBossContextConfig.applicationWebConfig(JBossContextConfig.java:168) [jboss-as-web-7.1.0.CR1-SNAPSHOT.jar:7.1.0.CR1-SNAPSHOT]
[JBossINF] at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:417) [jbossweb-7.0.7.Final.jar:]
[JBossINF] at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:182) [jbossweb-7.0.7.Final.jar:]
[JBossINF] at org.jboss.as.web.deployment.JBossContextConfig.lifecycleEvent(JBossContextConfig.java:161) [jboss-as-web-7.1.0.CR1-SNAPSHOT.jar:7.1.0.CR1-SNAPSHOT]
[JBossINF] at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:115) [jbossweb-7.0.7.Final.jar:]
[JBossINF] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3790) [jbossweb-7.0.7.Final.jar:]
[JBossINF] at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:77) [jboss-as-web-7.1.0.CR1-SNAPSHOT.jar:7.1.0.CR1-SNAPSHOT]
[JBossINF] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
[JBossINF] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
[JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29]
[JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29]
[JBossINF] at java.lang.Thread.run(Thread.java:662) [:1.6.0_29]
[JBossINF]
[JBossINF] 08:58:32,618 ERROR [org.jboss.as.web.session.DistributableSessionManager.clusterbench] (MSC service thread 1-3) Unable to start manager.: java.lang.ClassCastException: org.infinispan.remoting.transport.jgroups.JGroupsAddress cannot be cast to org.jboss.as.clustering.web.infinispan.SessionKey
[JBossINF] at org.jboss.as.clustering.web.infinispan.DistributedCacheManager.getSessionIds(DistributedCacheManager.java:391)
[JBossINF] at org.jboss.as.web.session.DistributableSessionManager.initializeUnloadedSessions(DistributableSessionManager.java:277) [jboss-as-web-7.1.0.CR1-SNAPSHOT.jar:7.1.0.CR1-SNAPSHOT]
[JBossINF] at org.jboss.as.web.session.DistributableSessionManager.start(DistributableSessionManager.java:179) [jboss-as-web-7.1.0.CR1-SNAPSHOT.jar:7.1.0.CR1-SNAPSHOT]
[JBossINF] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3859) [jbossweb-7.0.7.Final.jar:]
[JBossINF] at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:77) [jboss-as-web-7.1.0.CR1-SNAPSHOT.jar:7.1.0.CR1-SNAPSHOT]
[JBossINF] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
[JBossINF] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
[JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29]
[JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29]
[JBossINF] at java.lang.Thread.run(Thread.java:662) [:1.6.0_29]
[JBossINF]
[JBossINF] 08:58:32,619 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-3) Context [/clusterbench] startup failed due to previous errors: LifecycleException: java.lang.ClassCastException: org.infinispan.remoting.transport.jgroups.JGroupsAddress cannot be cast to org.jboss.as.clustering.web.infinispan.SessionKey
[JBossINF] at org.jboss.as.web.session.DistributableSessionManager.start(DistributableSessionManager.java:191) [jboss-as-web-7.1.0.CR1-SNAPSHOT.jar:7.1.0.CR1-SNAPSHOT]
[JBossINF] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3859) [jbossweb-7.0.7.Final.jar:]
[JBossINF] at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:77) [jboss-as-web-7.1.0.CR1-SNAPSHOT.jar:7.1.0.CR1-SNAPSHOT]
[JBossINF] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
[JBossINF] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
[JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29]
[JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29]
[JBossINF] at java.lang.Thread.run(Thread.java:662) [:1.6.0_29]
[JBossINF]
[JBossINF] 08:58:32,620 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-3) Context [/clusterbench] startup failed due to previous errors
[JBossINF] 08:58:32,621 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-3) Exception during cleanup after start failed: java.lang.NullPointerException
[JBossINF] at org.jboss.as.web.session.DistributableSessionManager.stop(DistributableSessionManager.java:438) [jboss-as-web-7.1.0.CR1-SNAPSHOT.jar:7.1.0.CR1-SNAPSHOT]
[JBossINF] at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3995) [jbossweb-7.0.7.Final.jar:]
[JBossINF] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3917) [jbossweb-7.0.7.Final.jar:]
[JBossINF] at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:77) [jboss-as-web-7.1.0.CR1-SNAPSHOT.jar:7.1.0.CR1-SNAPSHOT]
[JBossINF] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
[JBossINF] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
[JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29]
[JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29]
[JBossINF] at java.lang.Thread.run(Thread.java:662) [:1.6.0_29]
[JBossINF]
[JBossINF] 08:58:32,622 INFO [org.apache.catalina.core.ContainerBase] (MSC service thread 1-3) Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/clusterbench].[GranularSessionServlet] has not been started
[JBossINF] 08:58:32,622 INFO [org.apache.catalina.core.ContainerBase] (MSC service thread 1-3) Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/clusterbench].[jsp] has not been started
[JBossINF] 08:58:32,622 INFO [org.apache.catalina.core.ContainerBase] (MSC service thread 1-3) Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/clusterbench].[LocalEjbServlet] has not been started
[JBossINF] 08:58:32,622 INFO [org.apache.catalina.core.ContainerBase] (MSC service thread 1-3) Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/clusterbench].[HttpSessionServlet] has not been started
[JBossINF] 08:58:32,622 INFO [org.apache.catalina.core.ContainerBase] (MSC service thread 1-3) Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/clusterbench].[default] has not been started
[JBossINF] 08:58:32,623 INFO [org.apache.catalina.core.ContainerBase] (MSC service thread 1-3) Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/clusterbench].[LocalSingletonEjbServlet] has not been started
[JBossINF] 08:58:32,623 INFO [org.apache.catalina.core.ContainerBase] (MSC service thread 1-3) Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/clusterbench].[CdiServlet] has not been started
[JBossINF] 08:58:32,638 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.web.deployment.default-host./clusterbench: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./clusterbench: failed to start context
[JBossINF] at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:82)
[JBossINF] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
[JBossINF] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
[JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29]
[JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29]
[JBossINF] at java.lang.Thread.run(Thread.java:662) [:1.6.0_29]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] Created: (JBAS-9362) Long running thread leaks SimpleRole objects
by Tim Terlegard (JIRA)
Long running thread leaks SimpleRole objects
--------------------------------------------
Key: JBAS-9362
URL: https://issues.jboss.org/browse/JBAS-9362
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Security
Affects Versions: 6.0.0.Final
Environment: Tested on Mac OS X 10.6.7 with Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02-334, mixed mode) 1.6.0_24
Reporter: Tim Terlegard
Assignee: Anil Saldhana
Attachments: simpleroletest.tar.gz
When invoking a long-running EJB method which makes a bunch of calls to some method in another EJB, then JBoss leaks SimpleRole objects. The SimpleRole objects are not removed by a manually triggered garbage collection.
The SimpleRole object leakage seems to go away if I remove the security domain in jboss.xml. When running my jboss application during the night JBoss had 4GB of SimpleRole objects.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (JGRP-1405) TP: pool of hashmaps for message bundling
by Bela Ban (Created) (JIRA)
TP: pool of hashmaps for message bundling
-----------------------------------------
Key: JGRP-1405
URL: https://issues.jboss.org/browse/JGRP-1405
Project: JGroups
Issue Type: Enhancement
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 3.2
We currently have 2 message bundlers i TP: the default bundler which adds messages to a hashmap and, when full, has the sending thread serialize all queued messages into one and send it, and the transfer queue bundler, which has the sending thread place a message into a blocking queue and the dequeuer thread collect and send the bundled messages.
The disadvantage of the default bundler is that everyone has to wait adding messages to the hashmap, until message bundling has completed. OTOH, the transfer queue bundler blocks all sending threads when the blocking queue is full.
Let's create a third bundler, which behaves like the default bundler, but uses a *pool of hashmaps* rather than one. This way, when one hashmap is full, the other sending threads don't have to wait until bundling is complete, but can continue adding their messages to a different hashmap.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months