November 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2052) EBWS: WSDL produced by ESB Based Web Service endpoint is not consumable by .NET

by Burr Sutter (JIRA)

EBWS: WSDL produced by ESB Based Web Service endpoint is not consumable by .NET ------------------------------------------------------------------------------- Key: JBESB-2052 URL: https://jira.jboss.org/jira/browse/JBESB-2052 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 Reporter: Burr Sutter The WSDL and the quickstart that creates it are attached. Here is the exact error message from Visual Studio/Visual Basic: Error 1 Custom tool error: Unable to import WebService/Schema. Unable to import binding 'FetchCustomerBinding' from namespace 'http://soa.jboss.org/ESBWebServiceSample'. The operation 'FetchCustomerOp' on portType 'FetchCustomerPortType' from namespace 'http://soa.jboss.org/ESBWebServiceSample' had the following syntax error: The operation has no matching binding. Check if the operation, input and output names in the Binding section match with the corresponding names in the PortType section. C:\Users\Burr\AppData\Local\Temporary Projects\WindowsApplication1\My Project\Settings.settings 1 1 WindowsApplication1 -- 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

17 years, 3 months

4
13
0 / 0

[JBoss JIRA] Created: (JBESB-2173) SFTP certificate passphrase is not optional when using certificates

by Kevin Conner (JIRA)

SFTP certificate passphrase is not optional when using certificates ------------------------------------------------------------------- Key: JBESB-2173 URL: https://jira.jboss.org/jira/browse/JBESB-2173 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 CP1, 4.4, 4.2.1 TP2 Reporter: Kevin Conner Priority: Minor Fix For: 4.2.1 TP3, 4.4 CP2, 4.5 The certificate-passphrase should be optional but there is a bug in the ListenerUtil which prevents this. The resulting stacktrace is as follows 15:27:02,642 ERROR [STDERR] java.lang.IllegalArgumentException 15:27:02,644 ERROR [STDERR] at org.jboss.soa.esb.addressing.eprs.SFTPEpr.setPassphrase(SFTPEpr.java:196) 15:27:02,644 ERROR [STDERR] at org.jboss.soa.esb.addressing.eprs.SFTPEpr.<init>(SFTPEpr.java:127) 15:27:02,644 ERROR [STDERR] at org.jboss.soa.esb.listeners.ListenerUtil.fileEprFromElement(ListenerUtil.java:233) 15:27:02,644 ERROR [STDERR] at org.jboss.soa.esb.listeners.ListenerUtil.assembleEpr(ListenerUtil.java:94) -- 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

17 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-2141) Document client automatical XA transaction enlistment

by Martin Vecera (JIRA)

Document client automatical XA transaction enlistment ----------------------------------------------------- Key: JBESB-2141 URL: https://jira.jboss.org/jira/browse/JBESB-2141 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, Rosetta, Transports Affects Versions: 4.4 Reporter: Martin Vecera ESB client (e.g. ServiceInvoker) always uses XA transaction when sending JMS message using JBM. This automatic transaction enlistment should be documented. -- 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

17 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1958) JBoss Remoting Gateway not providing HTTP query string in composed message

by Tom Fennelly (JIRA)

JBoss Remoting Gateway not providing HTTP query string in composed message -------------------------------------------------------------------------- Key: JBESB-1958 URL: https://jira.jboss.org/jira/browse/JBESB-1958 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 Reporter: Tom Fennelly Fix For: 4.x This happens because the JBR CoyoteInvoker doesn't forward the query string in the request parameters object. -- 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

17 years, 4 months

4
8
0 / 0

[JBoss JIRA] Created: (JBESB-2049) Check for invalid synchronous invocations within a transactional context

by Kevin Conner (JIRA)

Check for invalid synchronous invocations within a transactional context ------------------------------------------------------------------------ Key: JBESB-2049 URL: https://jira.jboss.org/jira/browse/JBESB-2049 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Kevin Conner We support a number of transports which integrate with transactions in a manner such that the delivery of the message will not occur until the transaction has been committed. If these transports are used to delivery a synchronous message then the result is a timeout/failure. We should introduce a mechanism where we can identify these situations and throw a different exception, clarifying the failure for our users. -- 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

17 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-2168) Remove the Trailblazer and its documentation

by Daniel Bevenius (JIRA)

Remove the Trailblazer and its documentation -------------------------------------------- Key: JBESB-2168 URL: https://jira.jboss.org/jira/browse/JBESB-2168 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, Examples Reporter: Daniel Bevenius Fix For: 4.5 The Trailblazer is out of date and should be removed. Also remove any documentation that exists. Go through the docs folder and see if the Trailblazer is referenced in any of them. -- 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

17 years, 4 months

5
11
0 / 0

[JBoss JIRA] Created: (JBESB-2148) Document org.jboss.soa.esb.actions.routing.http.HttpRouter in programmer's guide

by Kevin Conner (JIRA)

Document org.jboss.soa.esb.actions.routing.http.HttpRouter in programmer's guide -------------------------------------------------------------------------------- Key: JBESB-2148 URL: https://jira.jboss.org/jira/browse/JBESB-2148 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.4 CP1, 4.4 Reporter: Kevin Conner Fix For: 4.4 CP2, 4.5 I have had a quick look at the programmer's guide and cannot find the details of this action. -- 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

17 years, 4 months

3
8
0 / 0

[JBoss JIRA] Created: (JBESB-2187) AQInitialContextFactory: Add support for a URL property to enable usage with RAC(Real Application Cluster)

by Daniel Bevenius (JIRA)

AQInitialContextFactory: Add support for a URL property to enable usage with RAC(Real Application Cluster) ---------------------------------------------------------------------------------------------------------- Key: JBESB-2187 URL: https://jira.jboss.org/jira/browse/JBESB-2187 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Configuration Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 4.5 Add support for an URL in the configuration. When an URL is specified only the username and password must also be specified. Davide Antoni(Forum Username: Sm0k3rz) has been able to successfully verify that this works. -- 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

17 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2160) Caching registry interceptor impacts must be documented and configuration values updated

by Kevin Conner (JIRA)

Caching registry interceptor impacts must be documented and configuration values updated ---------------------------------------------------------------------------------------- Key: JBESB-2160 URL: https://jira.jboss.org/jira/browse/JBESB-2160 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration, Documentation Affects Versions: 4.4 Reporter: Jiri Pechanec Assignee: Daniel Bevenius Priority: Critical Fix For: 4.4 CP1 If the CachingRegistryInterceptor is used in out-of-process binary - client or another ESB it can cause serious headache. The problem is that if the service is undeployed or EPRs changed then there are still old values in the cache. So for example it reports it cannot connect to the queue that is not already there etc. Another problem is that default value for load balancer cache timeout is 60 seconds and CachingRegistryIntreceptor is 600 secods. So if there is a service undeployed in the cluster the load balancer will repeatedly receive stale EPRs. See example of records in log 2008-08-27 09:39:42,785 DEBUG [main][org.jboss.internal.soa.esb.couriers.JmsCourier] Error from JMS system. javax.jms.JMSException: There is no administratively defined queue with name:queue/banker_deploy_process_esb at org.jboss.jms.server.endpoint.ServerSessionEndpoint.createQueue(ServerSessionEndpoint.java:291) at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$createQueue$aop(SessionAdvised.java:105) at org.jboss.jms.server.endpoint.advised.SessionAdvised$createQueue_6431069199924553036.invokeNext(SessionAdvised$createQueue_6431069199924553036.java) at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105) at org.jboss.jms.server.endpoint.advised.SessionAdvised$createQueue_6431069199924553036.invokeNext(SessionAdvised$createQueue_6431069199924553036.java) at org.jboss.jms.server.endpoint.advised.SessionAdvised.createQueue(SessionAdvised.java) at org.jboss.jms.wireformat.SessionCreateQueueRequest.serverInvoke(SessionCreateQueueRequest.java:74) at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:866) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:608) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:420) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:173) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163) at org.jboss.remoting.Client.invoke(Client.java:1634) at org.jboss.remoting.Client.invoke(Client.java:548) at org.jboss.remoting.Client.invoke(Client.java:536) at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:189) at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:160) at org.jboss.jms.client.delegate.ClientSessionDelegate.org$jboss$jms$client$delegate$ClientSessionDelegate$createQueue$aop(ClientSessionDelegate.java:297) at org.jboss.jms.client.delegate.ClientSessionDelegate$createQueue_6431069199924553036.invokeNext(ClientSessionDelegate$createQueue_6431069199924553036.java) at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) at org.jboss.jms.client.delegate.ClientSessionDelegate$createQueue_6431069199924553036.invokeNext(ClientSessionDelegate$createQueue_6431069199924553036.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$createQueue_6431069199924553036.invokeNext(ClientSessionDelegate$createQueue_6431069199924553036.java) at org.jboss.jms.client.delegate.ClientSessionDelegate.createQueue(ClientSessionDelegate.java) at org.jboss.jms.client.JBossSession.createQueue(JBossSession.java:250) at org.jboss.internal.soa.esb.rosetta.pooling.JmsSession.createQueue(JmsSession.java:186) at org.jboss.internal.soa.esb.couriers.JmsCourier.createMessageProducer(JmsCourier.java:334) at org.jboss.internal.soa.esb.couriers.JmsCourier.deliver(JmsCourier.java:188) at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.deliver(TwoWayCourierImpl.java:189) at org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.attemptDelivery(ServiceInvoker.java:530) at org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.access$200(ServiceInvoker.java:452) at org.jboss.soa.esb.client.ServiceInvoker.post(ServiceInvoker.java:318) at org.jboss.soa.esb.client.ServiceInvoker.deliverSync(ServiceInvoker.java:198) at org.jboss.soa.esb.qa.framework.SendESBMessage.sendSync(SendESBMessage.java:103) at org.jboss.soa.esb.qa.framework.ESBTestServices.deployJBPMProcess(ESBTestServices.java:675) at org.jboss.soa.esb.samples.quickstart.jbpmrulesaction.BPMRulesActionHandlerTest.setupClass(BPMRulesActionHandlerTest.java:31) 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.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:604) at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:394) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:142) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:79) at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:165) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:103) at org.testng.TestRunner.runWorkers(TestRunner.java:678) at org.testng.TestRunner.privateRun(TestRunner.java:624) at org.testng.TestRunner.run(TestRunner.java:495) at org.testng.SuiteRunner.runTest(SuiteRunner.java:300) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:295) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:275) at org.testng.SuiteRunner.run(SuiteRunner.java:190) at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:792) at org.testng.TestNG.runSuitesLocally(TestNG.java:765) at org.testng.TestNG.run(TestNG.java:699) at org.testng.TestNG.privateMain(TestNG.java:824) at org.testng.TestNG.main(TestNG.java:802) 2008-08-27 09:39:42,787 WARN [main][org.jboss.soa.esb.client.ServiceInvoker] Possible configuration error while using Courier for EPR [JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/banker_deploy_process_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <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/> > ]] and Service [test:jbpm-deploy] and Message [header: [ To: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/banker_deploy_process_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <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/> > ] ReplyTo: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/banker_deploy_process_esb_reply/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 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.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:message-selector : jbossESBresponseUUID='5b468d68-faa0-47dd-86a5-aef5deaec823'/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/> > ] MessageID: 88e0c518-fadc-4546-b16f-599872258cee ]]. javax.jms.JMSException: There is no administratively defined queue with name:queue/banker_deploy_process_esb -- 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

17 years, 4 months

2
11
0 / 0

[JBoss JIRA] Created: (JBESB-2159) The variables from services started in forked branches are lsot

by Kevin Conner (JIRA)

The variables from services started in forked branches are lsot --------------------------------------------------------------- Key: JBESB-2159 URL: https://jira.jboss.org/jira/browse/JBESB-2159 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.4 Environment: IR1 on FC8 Reporter: Jiri Pechanec Assignee: Kevin Conner Priority: Critical Fix For: 4.4 CP1, 4.5 The bpm_orchestartion2 qs provides different results in 4.2 and 4.3 versions. The problem is the the message modifications done in forked branches are not propagated back to the process. There are two possible explanations for this behaviour 1) The ProcessInstance.setVaribale method in jBPM does not set variable on root context - which means that there is bug in jBPM 2) Or behaviour with default configuration has changed I am attaching modified jboss-esb.xml and process definiton file that stores the service outcome under different variables in different branches so they are not overwritten in join node. You will see that in 4.3 the branch slots are not progpagated after the join node. -- 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

17 years, 4 months

2
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues November 2008