Hide Forgot
++ This bug is a clone of bug 780535 ++ project_key: SOA There's a failure when deploying an esb archive (zipped and exploded) through the JON console: 2009-08-18 07:56:27,169 INFO [ResourceFactory.executor-1] (rhq.core.pc.inventory.CreateResourceRunner)- Creating resource through report: CreateResourceReport: ResourceType=[ResourceType[id=0, category=Service, name=JBoss ESB Deployment, plugin=JBossESB]], ResourceKey=[null] 2009-08-18 07:56:27,228 ERROR [ResourceContainer.invoker.nonDaemon-4] (org.rhq.plugins.jmx.MBeanResourceComponent)- Error deploying application for report: CreateResourceReport: ResourceType=[ResourceType[id=0, category=Service, name=JBoss ESB Deployment, plugin=JBossESB]], ResourceKey=[null] java.lang.NoSuchMethodError: org.rhq.plugins.jbossas.util.FileContentDelegate.createContent(Lorg/rhq/core/domain/content/PackageDetails;Ljava/io/InputStream;Z)V at org.jbosson.plugins.jbossesb.ESBComponent.esbCreate(Unknown Source) at org.jbosson.plugins.jbossesb.ESBComponent.createResource(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:484) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) at java.util.concurrent.FutureTask.run(FutureTask.java:123) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) 2009-08-18 07:56:32,234 WARN [ResourceFactory.executor-1] (rhq.core.pc.inventory.CreateResourceRunner)- Throwable was found in creation report for request [500051]: java.lang.NoSuchMethodError: org.rhq.plugins.jbossas.util.FileContentDelegate.createContent(Lorg/rhq/core/domain/content/PackageDetails;Ljava/io/InputStream;Z)V - Enable DEBUG logging to see the stack trace. 2009-08-18 07:56:32,235 INFO [ResourceFactory.executor-1] (rhq.core.pc.inventory.CreateResourceRunner)- Sending create response to server: CreateResourceResponse[RequestId=500051, Status=Failure]
Link: Added: This issue Cloned from SOA-1451
Link: Added: This issue is a dependency of JBESB-2789
Link: Added: This issue is related to SOA-764
This is a request to fix this issue in the AS4 ESB plugin in SOA-P 5.2 - this bug was considered for 4.3.CP05, but requires a plugin pack update to deliver the fix. We did not want to ship a plugin pack update for 4.3.CP05, so this bug was cloned and moved to SOA-P 5. Fix this issue against whatever the JON version 5.2.0 will be qualified against.
I think that this is fixed on the ESB side. On JON server 2.4.1, I'm blocked by this bug here :
I think that this is fixed on the ESB side. On JON server 2.4.1, I'm blocked by this bug here : https://bugzilla.redhat.com/show_bug.cgi?id=727976
Release Notes Docs Status: Added: Documented as Resolved Issue Writer: Added: dlesage Release Notes Text: Added: https://issues.jboss.org/browse/SOA-2970 Users would encounter this error when deploying an ESB archive (either zipped or exploded) through the JON console: java.lang.NoSuchMethodError. An update to the plug-in pack has fixed this error, so users can now deploy the archives without encountering problems.
I tested the case with: JON 2.4.1.GA, PostgreSQL 8.4.8, OpenJDK 1.6.0, SOA-P/EDS 5.2.0 ER5 JON plugin pack: https://brewweb.devel.redhat.com//buildinfo?buildID=184426 There is a failure status when deploying an ESB archive. See: https://issues.jboss.org/browse/SOA-3524
JON 3.0.0 BETA3, PostgreSQL 8.4.8, OpenJDK 1.6.0, SOA-P/EDS 5.2.0 ER5 JON + plugin packs: https://brewweb.devel.redhat.com//buildinfo?buildID=183867 The ESB deployment failed with an exception in SOA-P log: 2011-10-26 14:51:12,357 ERROR [org.jboss.remoting.transport.socket.ServerThread] (WorkerThread#1[127.0.0.1:43982]) WorkerThread#1[127.0.0.1:43982] exception occurred during first invocation java.io.NotSerializableException: org.jboss.system.server.profile.repository.AbstractImmutableProfile at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1180) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346) at org.jboss.aop.joinpoint.InvocationResponse.writeExternal(InvocationResponse.java:100) at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1443) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1414) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1528) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1493) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346) at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.sendObjectVersion2_2(JavaSerializationManager.java:120) at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.sendObject(JavaSerializationManager.java:95) at org.jboss.remoting.marshal.serializable.SerializableMarshaller.write(SerializableMarshaller.java:120) at org.jboss.invocation.unified.marshall.InvocationMarshaller.write(InvocationMarshaller.java:75) at org.jboss.remoting.transport.socket.ServerThread.versionedWrite(ServerThread.java:1072) at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:830) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:744) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:548) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:234)
JON 2.4.1.GA, PostgreSQL 8.4.8, OpenJDK 1.6.0, SOA-P/EDS 5.2.0 ER6 Plugin packs: https://brewweb.devel.redhat.com//buildinfo?buildID=185293 The problem is fixed with new SOA/EDS plugin packs.
Fixed.