[JBoss JIRA] (JGRP-1508) MessageDispatcher allows sending messages after the channel has been closed
by Dan Berindei (JIRA)
Dan Berindei created JGRP-1508:
----------------------------------
Summary: MessageDispatcher allows sending messages after the channel has been closed
Key: JGRP-1508
URL: https://issues.jboss.org/browse/JGRP-1508
Project: JGroups
Issue Type: Bug
Affects Versions: 3.1, 3.0.13
Reporter: Dan Berindei
Assignee: Bela Ban
Channel.send() throws an exception if the channel is already closed, but MessageDispatcher goes around this and doesn't throw an exception immediately. Instead, if castMessage() was synchronous, it blocks and it times out after the request timeout expires.
--
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, 8 months
[JBoss JIRA] (AS7-5403) CLONE - Adding modcluster via the CLI fails.
by Joe Wertz (JIRA)
[ https://issues.jboss.org/browse/AS7-5403?page=com.atlassian.jira.plugin.s... ]
Joe Wertz commented on AS7-5403:
--------------------------------
The basic problem is that the modcluster subsystem cannot start without certain values in the mod-cluster-config being configured. However, the mod-cluster-config can't be set up until there is a subsystem. The composite operation works because the subsystem does not attempt to start until after the mod-cluster-config is set up.
I've found a few solutions, but the best seems to be this one.
1) Start the modcluster in a disabled mode. Adding a new attribute to /subsystem=modcluster:add(), 'enabled', and defaulting it to 'false', would allow the subsystem to be installed. Then the user could go into the mod-cluster-config and set up whatever they wanted, and go back and start the subsystem service once the setup is complete.
This creates a small hassle, because the user has to go back and manually activate the subsystem after it's installed and configured, but it allows the user to configure the subsystem to their liking.
Thoughts?
> CLONE - Adding modcluster via the CLI fails.
> --------------------------------------------
>
> Key: AS7-5403
> URL: https://issues.jboss.org/browse/AS7-5403
> Project: Application Server 7
> Issue Type: Bug
> Components: CLI
> Affects Versions: 7.1.2.Final (EAP)
> Reporter: Tom Fonteyne
> Assignee: Joe Wertz
>
> Adding modcluster via the CLI fails.
--
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, 8 months
[JBoss JIRA] (AS7-5497) Exception handling of EJB container for MDB is incorrect
by Adam Kovari (JIRA)
[ https://issues.jboss.org/browse/AS7-5497?page=com.atlassian.jira.plugin.s... ]
Adam Kovari moved JBPAPP-9833 to AS7-5497:
------------------------------------------
Project: Application Server 7 (was: JBoss Enterprise Application Platform)
Key: AS7-5497 (was: JBPAPP-9833)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: 7.1.2.Final (EAP)
(was: EAP 6.0.0)
Component/s: EJB
(was: EJB)
Security: (was: Public)
Fix Version/s: (was: TBD EAP 6)
Docs QE Status: (was: NEW)
> Exception handling of EJB container for MDB is incorrect
> --------------------------------------------------------
>
> Key: AS7-5497
> URL: https://issues.jboss.org/browse/AS7-5497
> Project: Application Server 7
> Issue Type: Bug
> Components: EJB
> Affects Versions: 7.1.2.Final (EAP)
> Environment: JBoss EAP 6.0.0
> Reporter: Adam Kovari
> Assignee: JBoss SET
> Priority: Minor
> Labels: eap6, ejb3.1
>
> After deploying a MDB with Container-Managed transaction and
> TransactionAttribute NOT_SUPPORTED, a RuntimeException thrown from
> within the MDB onMessage() is reported to the Adapter as such, with no
> EJBException wrapping. I.e.: the "((javax.jms.MessageListener)
> endPoint).onMessage(message)" call in our adapter fails with the
> exception type originally thrown.
> This does not look compliant with EJB 3.1 spec(JSR 318: Enterprise
> JavaBeansTM, Version 3.1, Table 20 page 392, last cell bottom right):
> "Throw EJBException that wraps the original exception to resource
> adapter".
> Another part of spec I was just made aware of says this:
> p383 of the spec states -
> In the case of a message-driven bean, the container logs the exception and then throws a javax.ejb.EJBException that wraps the original exception to the resource adapter. (See [15]).
--
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, 8 months
[JBoss JIRA] (AS7-4567) Weld does not find CDI Beans within AS7 modules
by Gernot P (JIRA)
Gernot P created AS7-4567:
-----------------------------
Summary: Weld does not find CDI Beans within AS7 modules
Key: AS7-4567
URL: https://issues.jboss.org/browse/AS7-4567
Project: Application Server 7
Issue Type: Bug
Components: Class Loading
Affects Versions: 7.1.1.Final, 7.1.0.Final
Reporter: Gernot P
Assignee: David Lloyd
I've a my.jar which contains cdi beans and cdi producer methods and a META-INF/beans.xml file.
Putting this jar to WEB-INF/lib in my war, the web app can use the cdi producer methods of my.jar.
After moving my.jar from WEB-INF/lib to a AS7 module(and adding a dependency in the war's MANIFEST.MF) AS7 reports
org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [BeanXY] with qualifiers [@Default] at injection point [[field] @Inject
It seams that weld does not (or cannot) scan my.jar which is inside AS7 module. (instantiating BeanXY directly ("new BeanXY()") works - so the module is loaded correctly)
--
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, 8 months
[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, 8 months
[JBoss JIRA] (AS7-5443) Lookup of application resources failed in PreDestroy
by Cheng Fang (JIRA)
Cheng Fang created AS7-5443:
-------------------------------
Summary: Lookup of application resources failed in PreDestroy
Key: AS7-5443
URL: https://issues.jboss.org/browse/AS7-5443
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.2.0.Alpha1
Reporter: Cheng Fang
Assignee: Eduardo Martins
JNDI lookup (e.g., java:app/AppName)in servlet or ejb @PreDestroy method failed:
{noformat}
13:33:32,223 INFO [stdout] (MSC service thread 1-16) In preDestroy of test.TestServlet@bea6b3
13:33:32,224 ERROR [stderr] (MSC service thread 1-16) javax.naming.NameNotFoundException: Error looking up AppName, service service jboss.naming.context.java.app.test.AppName is not started
13:33:32,224 ERROR [stderr] (MSC service thread 1-16) at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:126)
13:33:32,224 ERROR [stderr] (MSC service thread 1-16) at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:74)
13:33:32,224 ERROR [stderr] (MSC service thread 1-16) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)
13:33:32,224 ERROR [stderr] (MSC service thread 1-16) at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:129)
13:33:32,224 ERROR [stderr] (MSC service thread 1-16) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:215)
13:33:32,224 ERROR [stderr] (MSC service thread 1-16) at javax.naming.InitialContext.lookup(InitialContext.java:392)
13:33:32,224 ERROR [stderr] (MSC service thread 1-16) at javax.naming.InitialContext.doLookup(InitialContext.java:265)
13:33:32,224 ERROR [stderr] (MSC service thread 1-16) at test.TestServlet.preDestroy(TestServlet.java:25)
13:33:32,224 ERROR [stderr] (MSC service thread 1-16) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
13:33:32,225 ERROR [stderr] (MSC service thread 1-16) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
13:33:32,225 ERROR [stderr] (MSC service thread 1-16) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
13:33:32,225 ERROR [stderr] (MSC service thread 1-16) at java.lang.reflect.Method.invoke(Method.java:597)
13:33:32,225 ERROR [stderr] (MSC service thread 1-16) at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptorFactory$ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptorFactory.java:130)
13:33:32,225 ERROR [stderr] (MSC service thread 1-16) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
13:33:32,225 ERROR [stderr] (MSC service thread 1-16) at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
13:33:32,225 ERROR [stderr] (MSC service thread 1-16) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
13:33:32,225 ERROR [stderr] (MSC service thread 1-16) at org.jboss.as.ee.component.ManagedReferenceReleaseInterceptorFactory$ManagedReferenceReleaseInterceptor.processInvocation(ManagedReferenceReleaseInterceptorFactory.java:90)
13:33:32,225 ERROR [stderr] (MSC service thread 1-16) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
13:33:32,225 ERROR [stderr] (MSC service thread 1-16) at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
13:33:32,225 ERROR [stderr] (MSC service thread 1-16) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
13:33:32,225 ERROR [stderr] (MSC service thread 1-16) at org.jboss.as.ee.component.ManagedReferenceReleaseInterceptorFactory$ManagedReferenceReleaseInterceptor.processInvocation(ManagedReferenceReleaseInterceptorFactory.java:90)
13:33:32,226 ERROR [stderr] (MSC service thread 1-16) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
13:33:32,226 ERROR [stderr] (MSC service thread 1-16) at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
13:33:32,226 ERROR [stderr] (MSC service thread 1-16) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
13:33:32,226 ERROR [stderr] (MSC service thread 1-16) at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45)
13:33:32,226 ERROR [stderr] (MSC service thread 1-16) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
13:33:32,226 ERROR [stderr] (MSC service thread 1-16) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
13:33:32,226 ERROR [stderr] (MSC service thread 1-16) at org.jboss.as.ee.component.BasicComponentInstance.destroy(BasicComponentInstance.java:119)
13:33:32,226 ERROR [stderr] (MSC service thread 1-16) at org.jboss.as.web.deployment.component.WebComponentInstantiator$1.release(WebComponentInstantiator.java:63)
13:33:32,226 ERROR [stderr] (MSC service thread 1-16) at org.jboss.as.web.deployment.WebInjectionContainer.destroyInstance(WebInjectionContainer.java:69)
13:33:32,226 ERROR [stderr] (MSC service thread 1-16) at org.apache.catalina.core.StandardWrapper.unload(StandardWrapper.java:1389)
13:33:32,226 ERROR [stderr] (MSC service thread 1-16) at org.apache.catalina.core.StandardWrapper.stop(StandardWrapper.java:1682)
13:33:32,227 ERROR [stderr] (MSC service thread 1-16) at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3985)
13:33:32,227 ERROR [stderr] (MSC service thread 1-16) at org.jboss.as.web.deployment.WebDeploymentService.stop(WebDeploymentService.java:118)
13:33:32,227 ERROR [stderr] (MSC service thread 1-16) at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1911)
13:33:32,227 ERROR [stderr] (MSC service thread 1-16) at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1874)
13:33:32,227 ERROR [stderr] (MSC service thread 1-16) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
13:33:32,227 ERROR [stderr] (MSC service thread 1-16) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
13:33:32,227 ERROR [stderr] (MSC service thread 1-16) at java.lang.Thread.run(Thread.java:680)
{noformat}
jndi service and application resources should be available in @PreDestroy.
--
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, 8 months
[JBoss JIRA] (AS7-5112) Add deprecation information to management API metadata
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-5112:
-------------------------------------
Summary: Add deprecation information to management API metadata
Key: AS7-5112
URL: https://issues.jboss.org/browse/AS7-5112
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 7.3.0.Alpha1
Add metadata describing that we have deprecated:
1) Resources
2) Attributes
3) Operations
4) Operation parameters
We'll need to sort out exactly what info to provide. We can declare in what management API version an item was deprecated, and provide some localized text explaining. More problematic would be info on what "version" the item will be removed in (outside of vague wording in the description text). Probably including such info would be a mistake; prone to error.
--
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, 8 months
[JBoss JIRA] (AS7-3906) "JBAS010242: Partition web message wrapper does not contain Object[] object!" on node rejoining the cluster
by Radoslav Husar (JIRA)
Radoslav Husar created AS7-3906:
-----------------------------------
Summary: "JBAS010242: Partition web message wrapper does not contain Object[] object!" on node rejoining the cluster
Key: AS7-3906
URL: https://issues.jboss.org/browse/AS7-3906
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Affects Versions: 7.1.0.Final
Reporter: Radoslav Husar
Assignee: Paul Ferraro
Priority: Minor
Fix For: 7.1.1.Final
I started seeing lots of "(OOB-19,null) JBAS010242: Partition web message wrapper does not contain Object[] object!" recently. It happens when nodes rejoin the cluster. This also happens during SYNC replication.
Need to dig in deeper why is this happening and whether its causing some problems as well.
{noformat}
10:16:01,543 INFO [org.jboss.weld.Version] (MSC service thread 1-12) WELD-000900 1.1.5 (AS71)
10:16:01,567 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) JBAS016008: Starting weld service for deployment clusterbench-ee6.ear
10:16:01,885 INFO [stdout] (pool-14-thread-1)
10:16:01,885 INFO [stdout] (pool-14-thread-1) -------------------------------------------------------------------
10:16:01,886 INFO [stdout] (pool-14-thread-1) GMS: address=perf18/web, cluster=web, physical address=10.16.90.54:55200
10:16:01,886 INFO [stdout] (pool-14-thread-1) -------------------------------------------------------------------
10:16:01,887 INFO [stdout] (pool-19-thread-1)
10:16:01,887 INFO [stdout] (pool-19-thread-1) -------------------------------------------------------------------
10:16:01,888 INFO [stdout] (pool-19-thread-1) GMS: address=perf18/ejb, cluster=ejb, physical address=10.16.90.54:55200
10:16:01,888 INFO [stdout] (pool-19-thread-1) -------------------------------------------------------------------
10:16:01,989 INFO [org.jboss.as.clustering.impl.CoreGroupCommunicationService.web] (MSC service thread 1-15) JBAS010206: Number of cluster members: 4
10:16:01,990 INFO [org.jboss.as.clustering.impl.CoreGroupCommunicationService.ejb] (MSC service thread 1-7) JBAS010206: Number of cluster members: 4
10:16:02,096 WARN [org.jboss.as.clustering.impl.CoreGroupCommunicationService.web] (OOB-19,null) JBAS010242: Partition web message wrapper does not contain Object[] object!
10:16:02,096 WARN [org.jboss.as.clustering.impl.CoreGroupCommunicationService.web] (OOB-16,null) JBAS010242: Partition web message wrapper does not contain Object[] object!
10:16:02,097 WARN [org.jboss.as.clustering.impl.CoreGroupCommunicationService.web] (OOB-2,null) JBAS010242: Partition web message wrapper does not contain Object[] object!
10:16:02,097 WARN [org.jboss.as.clustering.impl.CoreGroupCommunicationService.web] (OOB-9,null) JBAS010242: Partition web message wrapper does not contain Object[] object!
10:16:02,098 WARN [org.jboss.as.clustering.impl.CoreGroupCommunicationService.web] (OOB-13,null) JBAS010242: Partition web message wrapper does not contain Object[] object!
10:16:02,098 WARN [org.jboss.as.clustering.impl.CoreGroupCommunicationService.web] (OOB-10,null) JBAS010242: Partition web message wrapper does not contain Object[] object!
...
{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, 8 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, 8 months