September 2011 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3667) Upgrade Apache HttpClient to 4.x

by Douglas Palmer (JIRA)

Upgrade Apache HttpClient to 4.x -------------------------------- Key: JBESB-3667 URL: https://issues.jboss.org/browse/JBESB-3667 Project: JBoss ESB Issue Type: Component Upgrade Security Level: Public (Everyone can see) Affects Versions: 4.10 Reporter: Douglas Palmer Assignee: Tom Cunningham Fix For: 4.10 CP1 Can you investigate whether or not you can upgrade from commons-httpclient:commons-httpclient:3.1 to org.apache.httpcomponents:httpclient:4.0? Don't commit this yet though as we need to investigate whether RiftSaw can upgrade too. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-3683) Upgrade jUDDI to 3.1.1

by Tom Cunningham (JIRA)

Upgrade jUDDI to 3.1.1 ---------------------- Key: JBESB-3683 URL: https://issues.jboss.org/browse/JBESB-3683 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.10 CP1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 CP1 Upgrade to jUDDI 3.1.1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3685) Quickstart security_cert produces strange output on client

by Tom Cunningham (JIRA)

Quickstart security_cert produces strange output on client ---------------------------------------------------------- Key: JBESB-3685 URL: https://issues.jboss.org/browse/JBESB-3685 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.10 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 CP1 Try security_cert quickstart. It works according to the description, but on the client the output is somewhat strange: ---------------------------------------------------------------------------------------- saygoodbye_over_http: [echo] [echo] Invoke JBR Gateway with successful login [java] Calling JBoss Remoting Listener using locator URI: http://localhost:8765 [java] JBR Class: java.lang.String [java] Response from JBoss Remoting Listener 'http://localhost:8765' was '��ysr%org.jboss.remoting.InvocationResponsea�3tm�Z isExceptionLpayloadtLjava/util/Map;LresulttLjava/lang/Object;L sessionIdtLjava/lang/String;xpsrjava.util.HashMap��`�FloadFactorI thresholdxp?@ tResponseCodeMessagetOKt ResponseCodesrjava.lang.Integer⠤��8Ivaluexrjava.lang.Number�� xp�t Content-Typettext/xml; charset=ISO-8859-1xt<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><ns2:sayGoodbyeResponse xmlns:ns2="http://security_cert/goodbyeworld"><return>... Ah Goodbye then!!!! - Goodbye!!</return></ns2:sayGoodbyeResponse></soap:Body></soap:Envelope>t"3j001-ofbv3n-gs063lgw-1-gs063lha-2'. [echo] [echo] [echo] Invoke JBR Gateway with unsuccessful login [java] Calling JBoss Remoting Listener using locator URI: http://localhost:8765 [java] Call was not successful. See server.log for details. Exception was: [java] org.jboss.remoting.transport.http.WebServerError: ��ysr%org.jboss.remoting.InvocationResponsea�3tm�Z isExceptionLpayloadtLjava/util/Map;LresulttLjava/lang/Object;L sessionIdtLjava/lang/String;xpsrjava.util.HashMap��`�FloadFactorI thresholdxp?@ tResponseCodeMessaget▒Invalid Login Credentials.t ResponseCodesrjava.lang.Integer⠤��8Ivaluexrjava.lang.Number�� xp�t Content-Typettext/plainxt�org.jboss.soa.esb.couriers.FaultMessageException: org.jboss.soa.esb.services.security.SecurityServiceException: Exception while trying to login: at org.jboss.soa.esb.listeners.message.errors.Factory.createExceptionFromFault(Factory.java:50) at org.jboss.internal.soa.esb.couriers.helpers.JmsComposer.compose(JmsComposer.java:82) at org.jboss.internal.soa.esb.couriers.JmsCourier.pickup(JmsCourier.java:461) at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:228) at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:204) at org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.attemptDelivery(ServiceInvoker.java:675) at org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.access$200(ServiceInvoker.java:569) at org.jboss.soa.esb.client.ServiceInvoker.post(ServiceInvoker.java:359) at org.jboss.soa.esb.client.ServiceInvoker.deliverSync(ServiceInvoker.java:219) at org.jboss.soa.esb.listeners.message.UncomposedMessageDeliveryAdapter.deliverSyncWithoutDecomposing(UncomposedMessageDeliveryAdapter.java:107) at org.jboss.soa.esb.listeners.message.UncomposedMessageDeliveryAdapter.deliverSync(UncomposedMessageDeliveryAdapter.java:86) at org.jboss.soa.esb.listeners.gateway.JBossRemotingGatewayListener.invoke(JBossRemotingGatewayListener.java:375) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:967) at org.jboss.remoting.transport.coyote.CoyoteInvoker.service(CoyoteInvoker.java:396) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:599) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:451) at java.lang.Thread.run(Thread.java:662)Caused by: org.jboss.soa.esb.services.security.SecurityServiceException: Exception while trying to login: at org.jboss.internal.soa.esb.services.security.JaasSecurityService.authenticate(JaasSecurityService.java:102) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:549) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:433) at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:550) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) ... 1 moreCaused by: javax.security.auth.login.LoginException: SignatureException : Signature does not match. at org.jboss.soa.esb.services.security.auth.login.CertificateLoginModule.login(CertificateLoginModule.java:181) 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 javax.security.auth.login.LoginContext.invoke(LoginContext.java:769) at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186) at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680) at javax.security.auth.login.LoginContext.login(LoginContext.java:579) at org.jboss.internal.soa.esb.services.security.JaasSecurityService.authenticate(JaasSecurityService.java:94) ... 6 moret"3j001-udaxx1-gs063mw0-1-gs063mw1-2 [java] at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:497) [java] at org.jboss.remoting.transport.http.HTTPClientInvoker.makeInvocation(HTTPClientInvoker.java:253) [java] at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:176) [java] at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:169) [java] at org.jboss.remoting.Client.invoke(Client.java:2070) [java] at org.jboss.remoting.Client.invoke(Client.java:879) [java] at org.jboss.remoting.Client.invoke(Client.java:867) [java] at org.jboss.soa.esb.samples.quickstart.securitycert.test.SendMessage.sendMessageToJBRListener(SendMessage.java:75) [java] at org.jboss.soa.esb.samples.quickstart.securitycert.test.SendMessage.main(SendMessage.java:115) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3665) Quickstart and base-build.xml reference obsolete JMS provider config files

by Len DiMaggio (JIRA)

Quickstart and base-build.xml reference obsolete JMS provider config files -------------------------------------------------------------------------- Key: JBESB-3665 URL: https://issues.jboss.org/browse/JBESB-3665 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.10 Reporter: Len DiMaggio Priority: Minor These files: jbossesb-listener.xml jbossesb-gateway.xml Are no longer be included in ESB releases. But - there are (2) references to these files: $ grep -r "jbossesb-listener.xml" * samples/quickstarts/helloworld_ftp_action/build.xml: <include name="jbossesb-listener.xml"/> samples/quickstarts/conf/base-build.xml: <include name="jbossesb-listener.xml"/> $ grep -r "jbossesb-gateway.xml" * samples/quickstarts/helloworld_ftp_action/build.xml: <include name="jbossesb-gateway.xml"/> samples/quickstarts/conf/base-build.xml: <include name="jbossesb-gateway.xml"/> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-3684) Configure JBPM asynchronous token signaling

by Tom Cunningham (JIRA)

Configure JBPM asynchronous token signaling ------------------------------------------- Key: JBESB-3684 URL: https://issues.jboss.org/browse/JBESB-3684 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.10 CP1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 CP1 See jbpm-3151 for details When incorporating this into SOA it is important that the SOA configuration has the asynchronous behaviour, i.e. the following must be configured <boolean name="jbpm.sub.process.async" value="true"/> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3622) DefaultJMSPropertiesSetter needs to filter out JMS properties

by Kevin Conner (JIRA)

DefaultJMSPropertiesSetter needs to filter out JMS properties ------------------------------------------------------------- Key: JBESB-3622 URL: https://issues.jboss.org/browse/JBESB-3622 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.9 CP1 Reporter: Kevin Conner The current property setter checks for properties that start with JMSX and JMS_ but we also need to include any properties that begin with JMS. The spec states that the prefixes JMSX and JMS_ are reserved for the JMS spec and implementations respectively, but it also states in a later section that any identifier name which does not begin with 'JMS' is application specific. Two implementations that will raise exceptions are WSMQ and HornetQ. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-3681) Upgrade Spring to 3.0.6.RELEASE

by Tom Cunningham (JIRA)

Upgrade Spring to 3.0.6.RELEASE ------------------------------- Key: JBESB-3681 URL: https://issues.jboss.org/browse/JBESB-3681 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.10 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 CP1 Upgrade Spring to 3.0.6.RELEASE -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3682) Revert qa/test.properties

by Kevin Conner (JIRA)

Revert qa/test.properties ------------------------- Key: JBESB-3682 URL: https://issues.jboss.org/browse/JBESB-3682 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.10 CP1 Reporter: Kevin Conner Assignee: Kevin Conner Priority: Minor Fix For: 4.10 CP1 test.properties contains local properties. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3680) Freemarker error when input files contains namespace declaration

by Tom Cunningham (JIRA)

Freemarker error when input files contains namespace declaration ---------------------------------------------------------------- Key: JBESB-3680 URL: https://issues.jboss.org/browse/JBESB-3680 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transformation Service Affects Versions: 4.10 CP1 Reporter: Tom Cunningham Assignee: Tom Fennelly Fix For: 4.10 CP1 Using an input file which contains a namespace declaration for a FreeMarker transformation leads to the following error: 13:58:42,859 ERROR [runtime] Error on line 1, column 3 in orderLinesFrag.ftl Expecting a string, date or number here, Expression item.nachname is instead a freemarker.ext.dom.NodeListModel The problematic instruction: ---------- ==> ${item.nachname} [on line 1, column 1 in orderLinesFrag.ftl] ---------- Java backtrace for programmers: ---------- freemarker.core.NonStringException: Error on line 1, column 3 in orderLinesFrag.ftl Expecting a string, date or number here, Expression item.nachname is instead a freemarker.ext.dom.NodeListModel at freemarker.core.Expression.getStringValue(Expression.java:126) at freemarker.core.Expression.getStringValue(Expression.java:93) at freemarker.core.DollarVariable.accept(DollarVariable.java:76) at freemarker.core.Environment.visit(Environment.java:208) at freemarker.core.MixedContent.accept(MixedContent.java:92) at freemarker.core.Environment.visit(Environment.java:208) at freemarker.core.Environment.process(Environment.java:188) at freemarker.template.Template.process(Template.java:232) at org.milyn.templating.freemarker.FreeMarkerTemplateProcessor.applyTemplate(FreeMarkerTemplateProcessor.java:356) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-3678) Wise SOAPFaultException processing relies on system property

by Kevin Conner (JIRA)

Wise SOAPFaultException processing relies on system property ------------------------------------------------------------ Key: JBESB-3678 URL: https://issues.jboss.org/browse/JBESB-3678 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.10 CP1 Reporter: Kevin Conner Priority: Blocker Fix For: 4.10 CP1 The fix for JBESB-3643 relies on passing information between the action class (SOAPClient) and aspect using a system property. This is unsafe. We need to change this to use a different mechanism otherwise there is a risk of conflict with multiple deployments. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues September 2011