[JBoss JIRA] Created: (JBESB-2870) war/esb archive deployment dependencies/ordering not guaranteed
by David Ward (JIRA)
war/esb archive deployment dependencies/ordering not guaranteed
---------------------------------------------------------------
Key: JBESB-2870
URL: https://jira.jboss.org/jira/browse/JBESB-2870
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.6
Reporter: David Ward
Fix For: 4.7
There should be a way to specify that an esb archive is dependent on a war archive to be deployed first before it is deployed.
An example of this is a SOAPProxy action which points to a JBossWS webservice deployed in the same container.
Right now, one can specify a deployment requirement of a war from an esb's deployment.xml file, but there are 2 problems with it:
1. You need to know the entire war deployment mbean object name, which unfortunately contains a generated id
2. The esb deployment will simply error instead of waiting for the dependent war to deploy.
It is probable that we need to create our own barrier for this to work properly.
We also need to test with wars contained inside esb archives, as well as exploded and zipped wars.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months
[JBoss JIRA] Created: (JBESB-2787) jbpm.esb causes AS 5 server to sometimes hang upon shutdown.
by Daniel Bevenius (JIRA)
jbpm.esb causes AS 5 server to sometimes hang upon shutdown.
-------------------------------------------------------------
Key: JBESB-2787
URL: https://jira.jboss.org/jira/browse/JBESB-2787
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Process flow
Affects Versions: 4.7
Reporter: Daniel Bevenius
The application server does not close down, well it hangs for a long while before finishing.
Console log (a few mins after the thread dump)
=============================================
16:54:33,395 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_40] - Abort called on already aborted atomic action 7f000001:a6d0:4a82d3c0:3cb
16:54:33,395 ERROR [STDERR] Exception in thread "JbpmJobExector:127.0.0.1:1"
16:54:33,395 ERROR [STDERR] java.lang.StackOverflowError
16:54:33,400 ERROR [STDERR] at java.lang.Class.isPrimitive(Native Method)
16:54:33,400 ERROR [STDERR] at java.lang.Class.getEnclosingMethodInfo(Class.java:923)
16:54:33,400 ERROR [STDERR] at java.lang.Class.getEnclosingClass(Class.java:1077)
16:54:33,400 ERROR [STDERR] at java.lang.Class.getSimpleBinaryName(Class.java:1216)
16:54:33,401 ERROR [STDERR] at java.lang.Class.getSimpleName(Class.java:1108)
16:54:33,401 ERROR [STDERR] at org.jboss.classloader.spi.base.BaseClassLoader.toString(BaseClassLoader.java:926)
16:54:33,401 ERROR [STDERR] at java.lang.String.valueOf(String.java:2615)
16:54:33,401 ERROR [STDERR] at java.lang.StringBuilder.append(StringBuilder.java:116)
16:54:33,401 ERROR [STDERR] at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:138)
16:54:33,401 ERROR [STDERR] at java.rmi.server.RMIClassLoader$2.loadClass(RMIClassLoader.java:620)
16:54:33,401 ERROR [STDERR] at org.jboss.system.JBossRMIClassLoader.loadClass(JBossRMIClassLoader.java:91)
16:54:33,401 ERROR [STDERR] at java.rmi.server.RMIClassLoader.loadClass(RMIClassLoader.java:247)
16:54:33,401 ERROR [STDERR] at sun.rmi.server.MarshalInputStream.resolveClass(MarshalInputStream.java:197)
16:54:33,401 ERROR [STDERR] at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1544)
16:54:33,401 ERROR [STDERR] at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
16:54:33,401 ERROR [STDERR] at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1699)
16:54:33,401 ERROR [STDERR] at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
16:54:33,401 ERROR [STDERR] at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1634)
16:54:33,401 ERROR [STDERR] at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
16:54:33,401 ERROR [STDERR] at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
16:54:33,402 ERROR [STDERR] at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
16:54:33,402 ERROR [STDERR] at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
16:54:33,402 ERROR [STDERR] at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
16:54:33,402 ERROR [STDERR] at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
16:54:33,402 ERROR [STDERR] at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:215)
16:54:33,402 ERROR [STDERR] at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
16:54:33,402 ERROR [STDERR] at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
16:54:33,402 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:726)
16:54:33,402 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
16:54:33,402 ERROR [STDERR] at javax.naming.InitialContext.lookup(InitialContext.java:351)
16:54:33,402 ERROR [STDERR] at org.hibernate.transaction.JTATransactionFactory.getUserTransaction(JTATransactionFactory.java:162)
16:54:33,402 ERROR [STDERR] at org.hibernate.transaction.JTATransactionFactory.getUserTransaction(JTATransactionFactory.java:172)
16:54:33,402 ERROR [STDERR] at org.hibernate.transaction.JTATransactionFactory.getUserTransaction(JTATransactionFactory.java:172)
16:54:33,402 ERROR [STDERR] at org.hibernate.transaction.JTATransactionFactory.getUserTransaction(JTATransactionFactory.java:172)
...
16:54:33,996 INFO [ConnectionFactoryBindingService] Unbound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=JbpmDS' from JNDI name 'java:JbpmDS'
16:54:34,044 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutting down.
16:54:34,044 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED paused.
16:54:34,045 INFO [SimpleThreadPool] There are still 35 worker threads active. See javadoc runInThread(Runnable) for a possible explanation
16:54:34,045 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutdown complete.
16:54:34,528 INFO [TransactionManagerService] Stopping transaction recovery manager
16:54:34,530 INFO [TransactionManagerService] Destroying TransactionManagerService
16:54:34,685 INFO [HypersonicDatabase] Database standalone closed clean
16:54:38,218 INFO [DefaultEndpointRegistry] remove: jboss.ws:context=Quickstart_webservice_consumer2,endpoint=OrderProcessorWS
16:54:38,402 INFO [HypersonicDatabase] Database standalone closed clean
16:54:38,661 INFO [H2Database] Database standalone closed clean
16:54:48,022 INFO [ServerImpl] Shutdown complete
Shutdown complete
Halting VM
Complete log will be attached with a thread dump.
I found this jira: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3481
The version of hibernate that is shipped with AS 5.1.0.GA is 3.3.1. Perhaps an upgrade to 3.3.2 will take care of the issue with the hang, though I still think
that we will in that case get an exception. Should the jbpm.esb/jbpm-service.xml's JbpmService depend on the TransactionManager?:
<mbean code="org.jboss.soa.esb.services.jbpm.configuration.JbpmService"
name="jboss.esb:service=JbpmService">
<depends>jboss.esb:service=JBPMDatabaseInitializer</depends>
<depends>jboss:service=TransactionManager</depends>
</mbean>
Lets say the TransactionManager sometimes gets deployed before the jbpm.esb, then this would probably trigger this issue. Sort of difficult to test this as this does not happen every time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months
[JBoss JIRA] Created: (JBESB-2916) Schema Validation - Non-conforming messages are not properly handled
by Jiri Pechanec (JIRA)
Schema Validation - Non-conforming messages are not properly handled
--------------------------------------------------------------------
Key: JBESB-2916
URL: https://jira.jboss.org/jira/browse/JBESB-2916
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.6
Reporter: Jiri Pechanec
Fix For: 4.7
I tried to send two kinds of messages two the validation action
1) Malformed XML - it works correctly
The log contains 10:13:39,213 ERROR [STDERR] [Fatal Error] :20:3: The element type "item" must be terminated by the matching end-tag "</item>", an exception is thrown and propagated as fault to the caller when synchornnous invocation is in place
2) In case of well-formed XML but non-conforming to schema an exception is thrown and the fault is not generated
09:09:04,997 ERROR [SchemaValidationAction] SAXExcption while trying to validate against schema '/schemas/valid-ns.xsd'
org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'p:orderperson'. One of '{orderperson}' is expected.
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
at org.apache.xerces.jaxp.validation.DOMValidatorHelper.beginNode(Unknown Source)
at org.apache.xerces.jaxp.validation.DOMValidatorHelper.validate(Unknown Source)
at org.apache.xerces.jaxp.validation.DOMValidatorHelper.validate(Unknown Source)
at org.apache.xerces.jaxp.validation.ValidatorImpl.validate(Unknown Source)
at org.jboss.soa.esb.actions.validation.SchemaValidationAction.validate(SchemaValidationAction.java:117)
at org.jboss.soa.esb.actions.validation.SchemaValidationAction.process(SchemaValidationAction.java:107)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:634)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:586)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:420)
at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:545)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
09:09:05,018 ERROR [ActionProcessingPipeline] Failed to send fault to address JMSEpr [ PortReference < <wsa:Address jms:jnp://127.0.0.1:1099#queue/quickstart_message_validation_esbns_reply/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : jnp://127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:destination-name : queue/quickstart_message_validation_esbns_reply/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:message-selector : jbossESBresponseUUID='27644272-0ca0-40fd-9465-5e1ed0b194f7'/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] for message header: [ To: JMSEpr [ PortReference < <wsa:Address jms:jnp://127.0.0.1:1099#queue/quickstart_message_validation_esbns_reply/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : jnp://127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:destination-name : queue/quickstart_message_validation_esbns_reply/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:message-selector : jbossESBresponseUUID='27644272-0ca0-40fd-9465-5e1ed0b194f7'/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] From: JMSEpr [ PortReference < <wsa:Address jms:jnp://127.0.0.1:1099#queue/quickstart_message_validation_esbns/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : jnp://127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:destination-name : queue/quickstart_message_validation_esbns/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] RelatesTo: 386d71a6-a767-4de1-8e17-e43d0da95be0 ]
org.jboss.soa.esb.couriers.CourierMarshalUnmarshalException: Failed to serialize ESB Message.
at org.jboss.internal.soa.esb.couriers.JmsCourier.internalDeliver(JmsCourier.java:225)
at org.jboss.internal.soa.esb.couriers.JmsCourier.deliver(JmsCourier.java:182)
at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.deliver(TwoWayCourierImpl.java:189)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.messageTo(ActionProcessingPipeline.java:861)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.faultTo(ActionProcessingPipeline.java:811)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:666)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:586)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:420)
at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:545)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.io.IOException: Util.serialize caught XMLStreamException:
at org.jboss.soa.esb.util.Util.serialize(Util.java:198)
at org.jboss.internal.soa.esb.couriers.JmsCourier.internalDeliver(JmsCourier.java:219)
... 11 more
Caused by: javax.xml.stream.XMLStreamException
at org.jboss.internal.soa.esb.message.format.xml.marshal.MarshalUnmarshalManager.marshal(MarshalUnmarshalManager.java:149)
at org.jboss.internal.soa.esb.message.format.xml.BodyImpl.writeChildContent(BodyImpl.java:146)
at org.jboss.internal.soa.esb.util.stax.ElementContent.writeContent(ElementContent.java:41)
at org.jboss.internal.soa.esb.util.stax.StreamHelper.writeElement(StreamHelper.java:125)
at org.jboss.internal.soa.esb.message.format.xml.MessageImpl.writeChildContent(MessageImpl.java:236)
at org.jboss.internal.soa.esb.util.stax.ElementContent.writeContent(ElementContent.java:41)
at org.jboss.soa.esb.util.Util.serialize(Util.java:188)
... 12 more
The behaviour should be same in both cases
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months