[JBoss JIRA] (AS7-2322) Stack trace improvements, summarize the things that broke to make them not so intimidating
by Jim Tyrrell (Created) (JIRA)
Stack trace improvements, summarize the things that broke to make them not so intimidating
------------------------------------------------------------------------------------------
Key: AS7-2322
URL: https://issues.jboss.org/browse/AS7-2322
Project: Application Server 7
Issue Type: Feature Request
Reporter: Jim Tyrrell
See the typical attached stack dump:
It would be nice if the stack dump could include all of the information above as a summary as shown below, basically just the first lines of the errors w/o the whole stack dump:
11:51:45,391 INFO [org.jboss.as.server.controller] (HttpManagementService-threads - 5) Deployment of "SpringWAR.war" was rolled back with failure message {"Failed services" => {"jboss.web.deployment.default-host./SpringWAR" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./SpringWAR: failed to start context"}}
11:51:45,392 INFO [org.jboss.as.controller] (HttpManagementService-threads - 5) Service status report
Services which failed to start:
service jboss.web.deployment.default-host./SpringWAR: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./SpringWAR: failed to start context
11:51:45,417 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Stopped deployment SpringWAR.war in 26ms
11:51:45,417 Error Summary of Exceptions in deployment:
- [org.springframework.web.context.ContextLoader] (MSC service thread 1-5) Context initialization failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jbossQueue' defined in class path resource [applicationContextServices.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: queue/B -- service jboss.naming.context.java.queue.B
- [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/SpringWAR]] (MSC service thread 1-5) Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jbossQueue' defined in class path resource [applicationContextServices.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: queue/B -- service jboss.naming.context.java.queue.B
- [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) Error listenerStart
- ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) Context [/SpringWAR] startup failed due to previous errors
- [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/SpringWAR]] (MSC service thread 1-5) Closing Spring root WebApplicationContext
- [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.web.deployment.default-host./SpringWAR:
ERROR Scroll up to see more info...
Or
11:51:45,417 Error Summary of Exceptions in deployment:
[1] [org.springframework.web.context.ContextLoader] (MSC service thread 1-5) Context initialization failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jbossQueue' defined in class path resource [applicationContextServices.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: queue/B -- service jboss.naming.context.java.queue.B
[2] [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/SpringWAR]] (MSC service thread 1-5) Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jbossQueue' defined in class path resource [applicationContextServices.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: queue/B -- service jboss.naming.context.java.queue.B
[3] [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) Error listenerStart
[4] ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) Context [/SpringWAR] startup failed due to previous errors
[5] [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/SpringWAR]] (MSC service thread 1-5) Closing Spring root WebApplicationContext
[6] [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.web.deployment.default-host./SpringWAR:
ERROR Scroll up to see more info...
--
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
12 years
[JBoss JIRA] (AS7-2385) Management - readding file handler logger fails
by Dominik Pospisil (Created) (JIRA)
Management - readding file handler logger fails
-----------------------------------------------
Key: AS7-2385
URL: https://issues.jboss.org/browse/AS7-2385
Project: Application Server 7
Issue Type: Bug
Components: Domain Management, Logging
Affects Versions: 7.1.0.Beta1
Reporter: Dominik Pospisil
Assignee: Brian Stansberry
Removing and adding file handler fails. Perhaps remove operation does not clean up all resources properlly.
Steps to reproduce:
[standalone@localhost:9999 /] /subsystem=logging/file-handler=test-fh:add(name="test-fh", level="WARN", file={"path" => "/home/dpospisi/testfh.log"})
{"outcome" => "success"}
[standalone@localhost:9999 /] /subsystem=logging/file-handler=test-fh:remove
{"outcome" => "success"}
[standalone@localhost:9999 /] /subsystem=logging/file-handler=test-fh:add(name="test-fh", level="WARN", file={"path" => "/home/dpospisi/testfh.log"})
{
"outcome" => "failed",
"failure-description" => "Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service jboss.logging.handler-file.test-fh is already registered",
"rolled-back" => true
}
[standalone@localhost:9999 /]
--
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
12 years, 1 month
[JBoss JIRA] (AS7-2873) EJB not defining an EJB 2 view method should not deploy
by Carlo de Wolf (Created) (JIRA)
EJB not defining an EJB 2 view method should not deploy
-------------------------------------------------------
Key: AS7-2873
URL: https://issues.jboss.org/browse/AS7-2873
Project: Application Server 7
Issue Type: Bug
Components: EJB
Reporter: Carlo de Wolf
Assignee: Stuart Douglas
A bean which does not implement the sayHello method of the following EJB 2 remote view:
{code:title=HelloRemote.java}
public interface HelloRemote extends EJBObject {
String sayHello(String name) throws RemoteException;
}
{code}
gets the following exception during invocation:
{noformat}
Caused by: javax.ejb.EJBException: org.jboss.invocation.CannotProceedException: INV-00002:Invocation cannot proceed (end of interceptor chain has been hit)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:241)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:316)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:201)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.remote.EJBRemoteTransactionPropogatingInterceptor.processInvocation(EJBRemoteTransactionPropogatingInterceptor.java:86)
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.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:70)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories$1.processInvocation(EjbExceptionTransformingInterceptorFactories.java:56)
... 126 more
{noformat}
Instead the EJB should not have deployed properly and throw a DeploymentException.
--
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
12 years, 1 month
[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
12 years, 1 month
[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
12 years, 1 month
[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
12 years, 1 month