February 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3187) SOAPClient and EsbWsdlLoader on different services shares configuration

by Kevin Conner (JIRA)

SOAPClient and EsbWsdlLoader on different services shares configuration ----------------------------------------------------------------------- Key: JBESB-3187 URL: https://jira.jboss.org/jira/browse/JBESB-3187 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 CP1 -- 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

14 years, 12 months

1
5
0 / 0

[JBoss JIRA] Created: (JBESB-3188) HttpClient connection parameters being ignored

by Kevin Conner (JIRA)

HttpClient connection parameters being ignored ---------------------------------------------- Key: JBESB-3188 URL: https://jira.jboss.org/jira/browse/JBESB-3188 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.7 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 CP1 -- 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

14 years, 12 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-3186) SOAPProxies on different services shares configuration

by Kevin Conner (JIRA)

SOAPProxies on different services shares configuration ------------------------------------------------------ Key: JBESB-3186 URL: https://jira.jboss.org/jira/browse/JBESB-3186 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 Environment: ER4 Reporter: Jiri Pechanec Assignee: David Ward Priority: Critical Fix For: 4.7 CP1 If a jboss-esb.xml file contains definition of two services and each uses SOAPProxy, then the configuration is shared between them. Check the attached example 1) Remove Proxy-breaker service from the config file, deploy and do ant runtest. The execution is performed correctly and target service is invoked. 2) Enable Proxy-breaker service but disable <http-client-property name="protocol-socket-factory"... in it, deploy and do ant run test. Although you are invoking the first service the invocation will fail due to strict SSL setting. 3) Enable Proxy-breaker service and enable <http-client-property name="protocol-socket-factory"... in it, deploy and do ant run test. The execution is performed correctly and target service is invoked. It proves that SOAPProxy settings on Proxy-breaker service DIRECTLY infulennces SOAPProxy settings of Proxy service. -- 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

14 years, 12 months

1
6
0 / 0

[JBoss JIRA] Created: (JBESB-3152) ExecuteJobCommand in ESB's jBPM integration doesn't roll back the transaction even if the action handler throws Exception

by Toshiya Kobayashi (JIRA)

ExecuteJobCommand in ESB's jBPM integration doesn't roll back the transaction even if the action handler throws Exception ------------------------------------------------------------------------------------------------------------------------- Key: JBESB-3152 URL: https://jira.jboss.org/jira/browse/JBESB-3152 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.4 CP3 Reporter: Toshiya Kobayashi In case that Job execution of an async node is processed by JCA inflow messaging service (SOA-P integration), the transaction is not rolled back even if the action handler throws Exception/RuntimeException. The transaction is commtted and then org.jboss.soa.esb.services.jbpm.integration.job.ExecuteJobCommand.executeJob() kicks one retry which would lead to duplicate commit. It looks inconsistent with docs: http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.CP02/html-single/... ============ If execution of a command message fails, the transaction will be rolled back. After that, a new transaction will be started that adds the error message to the message in the database. The command executor filters out all messages that contain an exception. ============ I've attatched a reproducer. - unzip jobexecution.zip - modify build.properties - ant deploypar - ant deploy - ant ejbclient (or access jbpm-console to start process instance) - access jbpm-console to check process instance's id which is created by the action handler (which should be rolled back) -- 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

14 years, 12 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-3151) JbpmContext.setRollbackOnly() in Job execution leads to "JbpmException: cannot mark externally managed transaction for rollback" with JCA inflow message service

by Toshiya Kobayashi (JIRA)

JbpmContext.setRollbackOnly() in Job execution leads to "JbpmException: cannot mark externally managed transaction for rollback" with JCA inflow message service ---------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBESB-3151 URL: https://jira.jboss.org/jira/browse/JBESB-3151 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.4 CP3 Reporter: Toshiya Kobayashi In case that Job execution of an async node is processed by ESB's JCA inflow message service, if you call jbpmContext.setRollbackOnly() in the action handler, the Exception below will be thrown: 19:11:51,045 ERROR [JmsServerSession] Unexpected error delivering message delegator->JBossMessage[5177979334393866]:PERSISTENT, deliveryId=1 org.jbpm.JbpmException: cannot mark externally managed transaction for rollback at org.jbpm.persistence.db.DbPersistenceService.endTransaction(DbPersistenceService.java:129) at org.jbpm.persistence.db.DbPersistenceService.close(DbPersistenceService.java:201) at org.jbpm.svc.Services.close(Services.java:247) at org.jbpm.JbpmContext.close(JbpmContext.java:131) at org.jboss.soa.esb.services.jbpm.integration.command.AbstractMessageListener.onMessage(AbstractMessageListener.java:80) 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:597) at org.jboss.internal.soa.esb.dependencies.JCAInflowAdapter$1.invoke(JCAInflowAdapter.java:276) at org.jboss.soa.esb.listeners.jca.EndpointProxy.delivery(EndpointProxy.java:242) at org.jboss.soa.esb.listeners.jca.EndpointProxy.invoke(EndpointProxy.java:145) at $Proxy92.onMessage(Unknown Source) at org.jboss.resource.adapter.jms.inflow.JmsServerSession.onMessage(JmsServerSession.java:178) at org.jboss.jms.client.container.ClientConsumer.callOnMessageStatic(ClientConsumer.java:160) at org.jboss.jms.client.container.SessionAspect.handleRun(SessionAspect.java:831) at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect16.invoke(SessionAspect16.java) at org.jboss.jms.client.delegate.ClientSessionDelegate$run_N8003352271541955702.invokeNext(ClientSessionDelegate$run_N8003352271541955702.java) at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) at org.jboss.jms.client.delegate.ClientSessionDelegate$run_N8003352271541955702.invokeNext(ClientSessionDelegate$run_N8003352271541955702.java) at org.jboss.jms.client.delegate.ClientSessionDelegate.run(ClientSessionDelegate.java) at org.jboss.jms.client.JBossSession.run(JBossSession.java:199) at org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:237) at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:213) at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:756) at java.lang.Thread.run(Thread.java:619) Actually, this causes rollback. But this looks messy on the console (stacktrace etc) so it's better to explicitly handle the rollback rather than forcing it as a side effect of invoking the jBPM context close(). -- 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

14 years, 12 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-2208) JON plugin can not be compiled against JOPR source

by Thorbj?rn Blixen-Finecke (JIRA)

JON plugin can not be compiled against JOPR source -------------------------------------------------- Key: JBESB-2208 URL: https://jira.jboss.org/jira/browse/JBESB-2208 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.4 CP1 Environment: All Reporter: Thorbj?rn Blixen-Finecke Priority: Minor The org.jbosson.plugins.jbossesb.DeploymentComponent imports the class org.rhq.plugins.utils.FileUtils. This class does not exist in the RHQ 1.2.0 or JOPR 2.2.0 source. The JON plugin can therefore not be compiled against the JOPR source. -- 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

14 years, 12 months

4
7
0 / 0

[JBoss JIRA] Created: (JBESB-2840) bpm_orchestration2 quickstart Extra Credit.

by Neil Wallace (JIRA)

bpm_orchestration2 quickstart Extra Credit. -------------------------------------------- Key: JBESB-2840 URL: https://jira.jboss.org/jira/browse/JBESB-2840 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.4 CP2 Reporter: Neil Wallace Priority: Minor Fix For: 4.4 CP3 In the extra credit section, after a call of ant refreshProcess, the ant startProcess gives this error. startProcess: [echo] Sends a message to start the process instance [java] Exception in thread "main" javax.naming.NameNotFoundException: quickstart_bpm_orchestration2_start_Request_gw not bound [java] at org.jnp.server.NamingServer.getBinding(NamingServer.java:581) [java] at org.jnp.server.NamingServer.getBinding(NamingServer.java:589) [java] at org.jnp.server.NamingServer.getObject(NamingServer.java:595) [java] at org.jnp.server.NamingServer.lookup(NamingServer.java:342) [java] at org.jnp.server.NamingServer.lookup(NamingServer.java:316) [java] at sun.reflect.GeneratedMethodAccessor83.invoke(Unknown Source) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [java] at java.lang.reflect.Method.invoke(Method.java:597) [java] at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305) [java] at sun.rmi.transport.Transport$1.run(Transport.java:159) [java] at java.security.AccessController.doPrivileged(Native Method) [java] at sun.rmi.transport.Transport.serviceCall(Transport.java:155) [java] at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) [java] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) [java] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) [java] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) [java] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) [java] at java.lang.Thread.run(Thread.java:619) [java] at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:255) [java] at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233) [java] at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142) [java] at org.jnp.server.NamingServer_Stub.lookup(Unknown Source) [java] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:667) [java] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627) [java] at javax.naming.InitialContext.lookup(InitialContext.java:392) [java] at org.jboss.soa.esb.samples.quickstarts.bpm_orchestration2.test.SendJMSMessageStart.setupConnection(SendJMSMessageStart.java:55) [java] at org.jboss.soa.esb.samples.quickstarts.bpm_orchestration2.test.SendJMSMessageStart.main(SendJMSMessageStart.java:80) BUILD FAILED -- 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

14 years, 12 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-2842) webservice_consumer1 error on deployment

by Neil Wallace (JIRA)

webservice_consumer1 error on deployment ---------------------------------------- Key: JBESB-2842 URL: https://jira.jboss.org/jira/browse/JBESB-2842 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.4 CP2 Reporter: Neil Wallace Priority: Minor Fix For: 4.4 CP3 webservice_consumer1 threw this error in the server log when running ant deploy 2009-09-16 10:29:00,745 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner ] Incomplete Deployment listing: --- Incompletely deployed packages --- org.jboss.deployment.DeploymentInfo@8ce1d89e { url=file:/home/nwallace/jboss-soa -p.4.3.0/jboss-as/server/production/deploy/Quickstart_webservice_consumer1.esb } deployer: org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer@feb215 status: Deployment FAILED reason: Could not create deployment: file:/home/nwal lace/jboss-soa-p.4.3.0/jboss-as/server/production/tmp/deploy/tmp14613Quickstart_ webservice_consumer1.esb-contents/Quickstart_webservice_consumer1.war; - nested throwable: (java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootst rap classloader, but this RI (from jar:file:/home/nwallace/jboss-soa-p.4.3.0/jbo ss-as/server/production/tmp/deploy/tmp14529jaxb-impl.jar!/com/sun/xml/bind/v2/mo del/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2 se/1.5.0/docs/guide/standards/)) state: FAILED watch: file:/home/nwallace/jboss-soa-p.4.3.0/jboss-as/server/production/deploy /Quickstart_webservice_consumer1.esb altDD: null lastDeployed: 1253093321232 lastModified: 1253093321000 mbeans: -- 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

14 years, 12 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-2844) WebService invocation is sometimes handled by CoyoteInvoker belonging to undeployed package

by Kevin Conner (JIRA)

WebService invocation is sometimes handled by CoyoteInvoker belonging to undeployed package ------------------------------------------------------------------------------------------- Key: JBESB-2844 URL: https://jira.jboss.org/jira/browse/JBESB-2844 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2.1, 4.4 CP3 Reporter: Jiri Pechanec Assignee: Tom Fennelly Priority: Minor Fix For: 4.2.1 CP4 There were multiple packages deployed/undeployed in the test. The deployment of Quickstart_webservice_mtom.esb is started on line 413471. This package starts coyote invoker with hashCode 17a4c54 at the line 413681. The undeploymetn of this package starts on line 414408. The CoyoteInvoker with the given hashCode is stopped at line 414457. The Quickstart_webservice_wsa.esb package deployment starts at line 414599. The CoyotInvoker with hashCode d93db8 is started at line 414806. Then the test message is sent via HTTP/SOAP and this request fails on line 515535 because it was served by the CoyoteInvoker with hashCode 17a4c54 so the one that belongs to previously undeployed package. -- 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

14 years, 12 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2838) Link in readme.txt doesn't exist

by Neil Wallace (JIRA)

Link in readme.txt doesn't exist -------------------------------- Key: JBESB-2838 URL: https://jira.jboss.org/jira/browse/JBESB-2838 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.4 CP2 Reporter: Neil Wallace Priority: Minor Fix For: 4.4 CP3 transform_XML2XML_simple and transform_XML2XML_date_manipulation readme's are talking about demos at http://labs.jboss.com/portal/jbossesb/resources/tutorials/xformation-demo... but they don't exist. Just get left on the JBoss ESB Downloads page. -- 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

14 years, 12 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues February 2010