September 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2826) JuddiRMIService overrides JNDI properties

by Kevin Conner (JIRA)

JuddiRMIService overrides JNDI properties ----------------------------------------- Key: JBESB-2826 URL: https://jira.jboss.org/jira/browse/JBESB-2826 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.4 CP2 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP3 JuddiRMIService overrides the JNDI properties when starting the jUDDI service. It looks like this code was a workaround for the lack of support for service binding manager/property substitution but now overrides any optimisation the app server may make. -- 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, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2820) jBPM job integration does not detect deleted jobs

by Kevin Conner (JIRA)

jBPM job integration does not detect deleted jobs ------------------------------------------------- Key: JBESB-2820 URL: https://jira.jboss.org/jira/browse/JBESB-2820 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.4 CP2 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP3 The jBPM job integration, included directly within ESB, does not correctly detect deleted jobs. This has come to light through timer integration but also applies to jobs. The code in ExecuteJobCommand, copied from jBPM, checks for a missing job by comparing the value retrieved against null. Unfortunately this is not valid as hibernate returns a proxy object regardless of whether the row exists or not, deferring any check until the object is first accessed. The fixed code should also be applied to the ExecuteTimerCommand. -- 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, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2834) Remove BYPASS property from RequestResponseBaseWebService

by Kevin Conner (JIRA)

Remove BYPASS property from RequestResponseBaseWebService --------------------------------------------------------- Key: JBESB-2834 URL: https://jira.jboss.org/jira/browse/JBESB-2834 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.6 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 -- 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, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2808) EBWS webservice is instantiated on every invocation

by Kevin Conner (JIRA)

EBWS webservice is instantiated on every invocation --------------------------------------------------- Key: JBESB-2808 URL: https://jira.jboss.org/jira/browse/JBESB-2808 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Web Services Affects Versions: 4.4 CP3 Reporter: Martin Vecera Assignee: Kevin Conner Priority: Critical Fix For: 4.4 CP3 With every call of a Web Service published using EBWS, an instance of JAXWS provider (BaseWebService) is created, which requests new ServiceInvoker and a lookup into UDDI. Attached is a TrackingRegistryInterceptor which shows UDDI lookups and their duration. This is a significant performance issue - after applying a partial workaround (see Workaround field) the performance almost doubled. -- 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, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-2786) Add alerting mechanism for monitoring

by Kevin Conner (JIRA)

Add alerting mechanism for monitoring ------------------------------------- Key: JBESB-2786 URL: https://jira.jboss.org/jira/browse/JBESB-2786 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.6 Reporter: Kevin Conner Assignee: Tom Cunningham Fix For: 4.7 Alerts for messages which take over a specific amount of time to be processed and whether their size is bigger than a specified maximum. -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2809) EBWS creates SOAP message factory with every request

by Kevin Conner (JIRA)

EBWS creates SOAP message factory with every request ---------------------------------------------------- Key: JBESB-2809 URL: https://jira.jboss.org/jira/browse/JBESB-2809 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Transports Affects Versions: 4.4 CP3 Environment: SOA-P 4.3.CP02 CR2 Reporter: Martin Vecera Priority: Blocker Fix For: 4.4 CP3 Every request to an ESB service published via EBWS requests can request several new SOAP message factories (at least one is created) - lookup javax.xml.soap.MessageFactory.newInstance() in org.jboss.internal.soa.esb.webservice.BaseWebService. With a scenario, which causes ESB to create only one new message factory for a request, a 13% overhead is introduced. -- 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, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-2832) Allow static declaration of response headers on the new <http-gateway>

by Tom Fennelly (JIRA)

Allow static declaration of response headers on the new <http-gateway> ---------------------------------------------------------------------- Key: JBESB-2832 URL: https://jira.jboss.org/jira/browse/JBESB-2832 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.7 Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.7 -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-2829) Inconsistent Servlet API library versions in build

by David Ward (JIRA)

Inconsistent Servlet API library versions in build -------------------------------------------------- Key: JBESB-2829 URL: https://jira.jboss.org/jira/browse/JBESB-2829 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.7 Reporter: David Ward Assignee: David Ward Priority: Minor Fix For: 4.7 We actually have 3 different servlet-api.jar's in svn: ./product/tools/console/management/lib/servlet-api.jar ./product/tools/console/lib/servlet-api.jar ./product/lib/ext/servlet-api.jar The first two are Servlet spec 2.4 and the third is Servlet spec 2.5. I'm not about to go messing with the console builds and remove them, but they should all be the same. Considering we ship JBoss.org AS 4.2.3 with Servlet spec 2.5 for runtime, that's what we should be consistent with and build against. -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2816) WSSecurityInfoExtractor gets confused over SOAP header element named 'UserName'

by Rune Molin (JIRA)

WSSecurityInfoExtractor gets confused over SOAP header element named 'UserName' ------------------------------------------------------------------------------- Key: JBESB-2816 URL: https://jira.jboss.org/jira/browse/JBESB-2816 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 Environment: *Release ID: JBoss [SOA_STANDALONE] 4.3.0.GA_CP01_SOA_STANDALONE (build: SVNTag=4.3.0.GA_CP01_SOA_STANDALONE date=200904071212) *SUSE Linux Enterprise Server 10 (i586) Reporter: Rune Molin If I send this request to a service hooked up to a jbr-listener gateway configured for HTTP access: <?xml version="1.0"?> <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> <S:Header> <RequestHeader xmlns="..."> <UserName>johndoe</UserName> <HostName>xx123</HostName> <Timestamp>2009-09-09T07:22:04.706Z</Timestamp> </RequestHeader> </S:Header> <S:Body> ... <S:Body> <S:Envelope> The result is an exception: 2009-09-09 07:58:09,517 ERROR [org.jboss.soa.esb.listeners.gateway.JBossRemotingGatewayListener] JBoss Remoting Gateway failed to synchronously deliver message to target service [RefData:GateService]. org.milyn.SmooksException: Unable to filter InputStream for target profile [org.milyn.profile.Profile#default_profile]. at org.milyn.delivery.dom.SmooksDOMFilter.filter(SmooksDOMFilter.java:287) at org.milyn.delivery.dom.SmooksDOMFilter.doFilter(SmooksDOMFilter.java:235) at org.milyn.Smooks.filter(Smooks.java:288) at org.milyn.Smooks.filter(Smooks.java:253) at org.jboss.soa.esb.services.security.auth.ws.WSSecurityInfoExtractor.extractSecurityInfo(WSSecurityInfoExtractor.java:97) at org.jboss.soa.esb.listeners.gateway.JBossRemotingGatewayListener$JBossRemotingMessageComposer.populateMessage(JBossRemotingGatewayListener.java:523) at org.jboss.soa.esb.listeners.gateway.JBossRemotingGatewayListener$JBossRemotingMessageComposer.populateMessage(JBossRemotingGatewayListener.java:487) at org.jboss.soa.esb.listeners.message.AbstractMessageComposer.compose(AbstractMessageComposer.java:76) at org.jboss.soa.esb.listeners.message.UncomposedMessageDeliveryAdapter.deliverSyncWithoutDecomposing(UncomposedMessageDeliveryAdapter.java:104) at org.jboss.soa.esb.listeners.message.UncomposedMessageDeliveryAdapter.deliverSync(UncomposedMessageDeliveryAdapter.java:86) at org.jboss.soa.esb.listeners.gateway.JBossRemotingGatewayListener.invoke(JBossRemotingGatewayListener.java:345) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:866) at org.jboss.remoting.transport.coyote.CoyoteInvoker.service(CoyoteInvoker.java:310) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) Caused by: org.milyn.SmooksException: Failed to apply processing unit [org.milyn.javabean.BeanInstancePopulator] to [org:milyn:smooks:unknowndoc:/S:Envelope/S:Header/RequestHeader/UserName]. at org.milyn.delivery.dom.SmooksDOMFilter.processVisitorException(SmooksDOMFilter.java:748) at org.milyn.delivery.dom.SmooksDOMFilter.access$800(SmooksDOMFilter.java:134) at org.milyn.delivery.dom.SmooksDOMFilter$ElementProcessor.processMapping(SmooksDOMFilter.java:733) at org.milyn.delivery.dom.SmooksDOMFilter$ElementProcessor.process(SmooksDOMFilter.java:671) at org.milyn.delivery.dom.SmooksDOMFilter$ElementProcessor.access$000(SmooksDOMFilter.java:625) at org.milyn.delivery.dom.SmooksDOMFilter.filter(SmooksDOMFilter.java:352) at org.milyn.delivery.dom.SmooksDOMFilter.filter(SmooksDOMFilter.java:285) ... 16 more Caused by: org.milyn.cdr.SmooksConfigurationException: Bean instance [userNameToken] not available and bean runtime class not set on configuration. at org.milyn.javabean.BeanUtils.getBean(BeanUtils.java:130) at org.milyn.javabean.BeanInstancePopulator.populateAndSetPropertyValue(BeanInstancePopulator.java:328) at org.milyn.javabean.BeanInstancePopulator.populateAndSetPropertyValue(BeanInstancePopulator.java:317) at org.milyn.javabean.BeanInstancePopulator.bindDomDataValue(BeanInstancePopulator.java:232) at org.milyn.javabean.BeanInstancePopulator.visitAfter(BeanInstancePopulator.java:178) at org.milyn.delivery.dom.SmooksDOMFilter$ElementProcessor.processMapping(SmooksDOMFilter.java:727) ... 20 more 2009-09-09 07:58:09,517 DEBUG [org.jboss.remoting.transport.coyote.CoyoteInvoker] Error thrown calling invoke on server invoker. org.milyn.SmooksException: Unable to filter InputStream for target profile [org.milyn.profile.Profile#default_profile]. at org.milyn.delivery.dom.SmooksDOMFilter.filter(SmooksDOMFilter.java:287) at org.milyn.delivery.dom.SmooksDOMFilter.doFilter(SmooksDOMFilter.java:235) at org.milyn.Smooks.filter(Smooks.java:288) at org.milyn.Smooks.filter(Smooks.java:253) at org.jboss.soa.esb.services.security.auth.ws.WSSecurityInfoExtractor.extractSecurityInfo(WSSecurityInfoExtractor.java:97) at org.jboss.soa.esb.listeners.gateway.JBossRemotingGatewayListener$JBossRemotingMessageComposer.populateMessage(JBossRemotingGatewayListener.java:523) at org.jboss.soa.esb.listeners.gateway.JBossRemotingGatewayListener$JBossRemotingMessageComposer.populateMessage(JBossRemotingGatewayListener.java:487) at org.jboss.soa.esb.listeners.message.AbstractMessageComposer.compose(AbstractMessageComposer.java:76) at org.jboss.soa.esb.listeners.message.UncomposedMessageDeliveryAdapter.deliverSyncWithoutDecomposing(UncomposedMessageDeliveryAdapter.java:104) at org.jboss.soa.esb.listeners.message.UncomposedMessageDeliveryAdapter.deliverSync(UncomposedMessageDeliveryAdapter.java:86) at org.jboss.soa.esb.listeners.gateway.JBossRemotingGatewayListener.invoke(JBossRemotingGatewayListener.java:345) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:866) at org.jboss.remoting.transport.coyote.CoyoteInvoker.service(CoyoteInvoker.java:310) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) Caused by: org.milyn.SmooksException: Failed to apply processing unit [org.milyn.javabean.BeanInstancePopulator] to [org:milyn:smooks:unknowndoc:/S:Envelope/S:Header/RequestHeader/UserName]. at org.milyn.delivery.dom.SmooksDOMFilter.processVisitorException(SmooksDOMFilter.java:748) at org.milyn.delivery.dom.SmooksDOMFilter.access$800(SmooksDOMFilter.java:134) at org.milyn.delivery.dom.SmooksDOMFilter$ElementProcessor.processMapping(SmooksDOMFilter.java:733) at org.milyn.delivery.dom.SmooksDOMFilter$ElementProcessor.process(SmooksDOMFilter.java:671) at org.milyn.delivery.dom.SmooksDOMFilter$ElementProcessor.access$000(SmooksDOMFilter.java:625) at org.milyn.delivery.dom.SmooksDOMFilter.filter(SmooksDOMFilter.java:352) at org.milyn.delivery.dom.SmooksDOMFilter.filter(SmooksDOMFilter.java:285) ... 16 more Caused by: org.milyn.cdr.SmooksConfigurationException: Bean instance [userNameToken] not available and bean runtime class not set on configuration. at org.milyn.javabean.BeanUtils.getBean(BeanUtils.java:130) at org.milyn.javabean.BeanInstancePopulator.populateAndSetPropertyValue(BeanInstancePopulator.java:328) at org.milyn.javabean.BeanInstancePopulator.populateAndSetPropertyValue(BeanInstancePopulator.java:317) at org.milyn.javabean.BeanInstancePopulator.bindDomDataValue(BeanInstancePopulator.java:232) at org.milyn.javabean.BeanInstancePopulator.visitAfter(BeanInstancePopulator.java:178) at org.milyn.delivery.dom.SmooksDOMFilter$ElementProcessor.processMapping(SmooksDOMFilter.java:727) ... 20 more Changing <UserName>johndoe</UserName> into <NameOfUser>johndoe</NameOfUser> fixes the problem. My guess is that the smooks transformation that looks for the WS-Security element 'UserNameToken' is not specific enough, so it picks up this 'UserName' element, which is not related to WS-Security in any way -- 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, 8 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-2827) Add support for new HttpGateway on AS5 deployer code

by Tom Fennelly (JIRA)

Add support for new HttpGateway on AS5 deployer code ---------------------------------------------------- Key: JBESB-2827 URL: https://jira.jboss.org/jira/browse/JBESB-2827 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.7 Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.7 -- 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, 8 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues September 2009