March 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2498) QS helloworld_bridge send message to wrong queue

by Martin Vecera (JIRA)

QS helloworld_bridge send message to wrong queue ------------------------------------------------ Key: JBESB-2498 URL: https://jira.jboss.org/jira/browse/JBESB-2498 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.4 CP2 Reporter: Martin Vecera In helloworld_bridge there is a bridge queue which bridges messages to GW queue for a helloworld service. In build.xml there is a message send directly to GW queue, hence it is not using the bridged one. I think that the original message should be sent to the bridge. -- 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

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-2496) XSD reference URL in Programmers Guide is wrong

by Tom Fennelly (JIRA)

XSD reference URL in Programmers Guide is wrong ----------------------------------------------- Key: JBESB-2496 URL: https://jira.jboss.org/jira/browse/JBESB-2496 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.4 CP2 Reporter: Tom Fennelly Fix For: 4.4 CP3 See SOA-1001 -- 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

15 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2491) JBossRemotingGatewayListener creating and instance of WSSecurityInfoExtractor on every request/invocation

by Tom Fennelly (JIRA)

JBossRemotingGatewayListener creating and instance of WSSecurityInfoExtractor on every request/invocation --------------------------------------------------------------------------------------------------------- Key: JBESB-2491 URL: https://jira.jboss.org/jira/browse/JBESB-2491 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Transports Affects Versions: 4.5 Reporter: Tom Fennelly Fix For: 4.6 This is resulting in an instance of Smooks being created on every request => Smooks config etc has to be processed every time etc etc. This is very inefficient. See the JBossRemotingMessageComposer inner class. -- 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

15 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2490) Thread related InVM resources created by DefaultInVMReplyToEpr not being cleaned up on thread cleanup

by Tom Fennelly (JIRA)

Thread related InVM resources created by DefaultInVMReplyToEpr not being cleaned up on thread cleanup ------------------------------------------------------------------------------------------------------ Key: JBESB-2490 URL: https://jira.jboss.org/jira/browse/JBESB-2490 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.5 Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.6 The DefaultInVMReplyToEpr class creates an InVMCourier + InVMEpr for handling async replies on a deliverSync over InVM. It attaches these details to the active thread. The logic at the time was that they could be reused. The obvious flaw in the logic (hindsight) is that when the threads are pooled and the pool is persiodically cleaned... new threads are created... more InVmCouriers are created, resulting in the InVMCourier list (held by the CourierFactory) growing and growing. -- 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

15 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2488) [SOAPClient] improved xstream support etc.

by Joakim Sandström (JIRA)

[SOAPClient] improved xstream support etc. ------------------------------------------ Key: JBESB-2488 URL: https://jira.jboss.org/jira/browse/JBESB-2488 Project: JBoss ESB Issue Type: Patch Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 Reporter: Joakim Sandström * xstream ** new configuration properties include: attributeAlias, omitField, converter and collection * ognl: ** support for href references in response ** support for attributes in response * updated javadoc ** xstream ** get-payload-location and set-payload-location -- 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

15 years, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-2481) Client and server side JBM information can become out of sync

by Kevin Conner (JIRA)

Client and server side JBM information can become out of sync ------------------------------------------------------------- Key: JBESB-2481 URL: https://jira.jboss.org/jira/browse/JBESB-2481 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.5 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.6 The issue appears to be occurring with the connection information and has been seen with a co-located (client and server in same VM) deployment. This may be indicative of a race condition, with the server side (even though co-located) deciding to close the connection at the same time as we access it. The result of this is the following Caused by: java.lang.IllegalStateException: Cannot find object in dispatcher with id jr51-zktjeurf-1-wxm28srf-0fpqee-t2p1hs4 at org.jboss.jms.wireformat.ConnectionCreateSessionDelegateRequest.serverInvoke(ConnectionCreateSessionDelegateRequest.java:84) 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) We should check for this during session creation and, if found, attempt to cleanup and re-establish the connection. -- 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

15 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2486) JBoss42ActivationBridge: ActivationConfigPropertyMetaData are being created with incorrectly set values

by Daniel Bevenius (JIRA)

JBoss42ActivationBridge: ActivationConfigPropertyMetaData are being created with incorrectly set values ------------------------------------------------------------------------------------------------------- Key: JBESB-2486 URL: https://jira.jboss.org/jira/browse/JBESB-2486 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Reporter: Daniel Bevenius Fix For: 4.6 The activate() methods contains the following lines of code: for (String key : activationProperties.keySet()) { String value = activationProperties.get(key); ActivationConfigPropertyMetaData propMetaData = new ActivationConfigPropertyMetaData(); propMetaData.setName(key); propMetaData.setValue(key); metaData.add(propMetaData); //metaData.add(new ActivationConfigPropertyMetaData(key, value)); } Value is being used and instead the value is set to the value of the key. -- 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

15 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2474) http-listener: Add config support for restricting the allowed HTTP methods on a per listener basis

by Tom Fennelly (JIRA)

http-listener: Add config support for restricting the allowed HTTP methods on a per listener basis -------------------------------------------------------------------------------------------------- Key: JBESB-2474 URL: https://jira.jboss.org/jira/browse/JBESB-2474 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta, Transports Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.4 FP1 Need to propagate the security info from the web container. -- 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

15 years, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-2475) Add http option support in the newest http gateway

by Jim Ma (JIRA)

Add http option support in the newest http gateway -------------------------------------------------- Key: JBESB-2475 URL: https://jira.jboss.org/jira/browse/JBESB-2475 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Reporter: Jim Ma Fix For: 4.4 FP1 I build the JBESB_4_4_GA_FP branch and deploy the http_gateway sample in it . When I use httpclient to send http option request , I can not get the allowed methods information in http headers. -- 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

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-2485) Apply JBESB-2484 to SOA CP branch

by Kevin Conner (JIRA)

Apply JBESB-2484 to SOA CP branch --------------------------------- Key: JBESB-2485 URL: https://jira.jboss.org/jira/browse/JBESB-2485 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.4 CP2 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP3 -- 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

15 years, 2 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues March 2009