[jboss-as7-dev] Deploy of a singleton service will not work in AS7 (upstream)

Wolf-Dieter Fink wfink at redhat.com
Wed Jul 18 10:13:36 EDT 2012


Hi,

my SingeltonService will run in EAP6 and AS7.1 but the start will fail 
in the current upstream (the service.jar is compiled against 7.1.1.Final 
maven dependencies)
I did not understand the error ATM because the method signature is still 
valid.
My service is packed as a jar without any org.jboss classes in it.

Any idea whats wrong?

Wolf


Caused by: java.lang.NoSuchMethodError: 
org.jboss.as.clustering.singleton.SingletonService.build(Lorg/jboss/msc/service/ServiceContainer;)Lorg/jboss/msc/service/ServiceBuilder;
     at 
org.jboss.as.quickstarts.cluster.hasingleton.service.ejb.StartupSingleton.startup(StartupSingleton.java:62)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
[rt.jar:1.6.0_22]
     at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) 
[rt.jar:1.6.0_22]
     at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
[rt.jar:1.6.0_22]
     at java.lang.reflect.Method.invoke(Method.java:616) [rt.jar:1.6.0_22]
     at 
org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptorFactory$ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptorFactory.java:130) 
[jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
     at 
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) 
[jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
     at 
org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) 
[jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
     at 
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) 
[jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
     at 
org.jboss.as.ee.component.ManagedReferenceInterceptorFactory$ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptorFactory.java:95) 
[jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
     at 
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) 
[jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
     at 
org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) 
[jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
     at 
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) 
[jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
     at 
org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) 
[jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
     at 
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) 
[jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
     at 
org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:227)
     ... 20 more

15:55:17,013 INFO  [org.jboss.as.server] (management-handler-thread - 2) 
JBAS015870: Deploy of deployment "jboss-as-cluster-ha-singleton-ejb.jar" 
was rolled back with failure message {"JBAS014671: Failed services" => 
{"jboss.deployment.unit.\"jboss-as-cluster-ha-singleton-ejb.jar\".component.StartupSingleton.START" 
=> "org.jboss.msc.service.StartException in service 
jboss.deployment.unit.\"jboss-as-cluster-ha-singleton-ejb.jar\".component.StartupSingleton.START: 
java.lang.IllegalStateException: JBAS011048: Failed to construct 
component instance
     Caused by: java.lang.IllegalStateException: JBAS011048: Failed to 
construct component instance
     Caused by: javax.ejb.EJBException: Unexpected Error
     Caused by: java.lang.NoSuchMethodError: 
org.jboss.as.clustering.singleton.SingletonService.build(Lorg/jboss/msc/service/ServiceContainer;)Lorg/jboss/msc/service/ServiceBuilder;"}}



More information about the jboss-as7-dev mailing list