September 2011 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3691) EBWS generates wsdl soap action using response URI

by Kevin Conner (JIRA)

EBWS generates wsdl soap action using response URI -------------------------------------------------- Key: JBESB-3691 URL: https://issues.jboss.org/browse/JBESB-3691 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.10 Reporter: Kevin Conner Fix For: 4.10 CP1 ESBContractGenerator initialises the soap action URI to the response action URI rather than the request action URI It needs to be soapOperation.setSoapActionURI(serviceInfo.getRequestAction()) ; -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
5
0 / 0

[JBoss JIRA] Assigned: (JBESB-3686) alertLengthThreshold does not work for http-gateway

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3686?page=com.atlassian.jira.plugin... ] Tom Cunningham reassigned JBESB-3686: ------------------------------------- Assignee: Tom Cunningham > alertLengthThreshold does not work for http-gateway > --------------------------------------------------- > > Key: JBESB-3686 > URL: https://issues.jboss.org/browse/JBESB-3686 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.9 CP1, 4.10 > Reporter: Martin Weiler > Assignee: Tom Cunningham > > We added 'alertTimeThreshold' and 'alertLengthThreshold' properties to a service which only has a http-gateway listener. We see WARN messages if the time threshold is surpassed, but none for the lenght threshold. > Diagnostics: > The problem with the alertLengthThreshold is that this only works if the message contains a property 'Environment.MESSAGE_BYTE_SIZE', see the ActionStatusBean constructor: > http://anonsvn.jboss.org/repos/labs/labs/jbossesb/tags/JBESB_4_9_CP1_ER8_... > This property is set in either the Util.serialize(Message) or Util.deserialize() method: > http://anonsvn.jboss.org/repos/labs/labs/jbossesb/tags/JBESB_4_9_CP1_ER8_... > But while one of these methods is called when other gateways are used (eg. with JMS through the org.jboss.internal.soa.esb.couriers.helpers.JmsComposer), this is apparently not the case with http-gateway. > Todo: > Improve the algorithm in ActionStatusBean which calculates the message bytes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBESB-3686) alertLengthThreshold does not work for http-gateway

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3686?page=com.atlassian.jira.plugin... ] Tom Cunningham closed JBESB-3686. --------------------------------- > alertLengthThreshold does not work for http-gateway > --------------------------------------------------- > > Key: JBESB-3686 > URL: https://issues.jboss.org/browse/JBESB-3686 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.9 CP1, 4.10 > Reporter: Martin Weiler > Assignee: Tom Cunningham > > We added 'alertTimeThreshold' and 'alertLengthThreshold' properties to a service which only has a http-gateway listener. We see WARN messages if the time threshold is surpassed, but none for the lenght threshold. > Diagnostics: > The problem with the alertLengthThreshold is that this only works if the message contains a property 'Environment.MESSAGE_BYTE_SIZE', see the ActionStatusBean constructor: > http://anonsvn.jboss.org/repos/labs/labs/jbossesb/tags/JBESB_4_9_CP1_ER8_... > This property is set in either the Util.serialize(Message) or Util.deserialize() method: > http://anonsvn.jboss.org/repos/labs/labs/jbossesb/tags/JBESB_4_9_CP1_ER8_... > But while one of these methods is called when other gateways are used (eg. with JMS through the org.jboss.internal.soa.esb.couriers.helpers.JmsComposer), this is apparently not the case with http-gateway. > Todo: > Improve the algorithm in ActionStatusBean which calculates the message bytes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBESB-3686) alertLengthThreshold does not work for http-gateway

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3686?page=com.atlassian.jira.plugin... ] Tom Cunningham resolved JBESB-3686. ----------------------------------- Resolution: Done Added MESSAGE_BYTE_SIZE to HttpMessageComposer. > alertLengthThreshold does not work for http-gateway > --------------------------------------------------- > > Key: JBESB-3686 > URL: https://issues.jboss.org/browse/JBESB-3686 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.9 CP1, 4.10 > Reporter: Martin Weiler > > We added 'alertTimeThreshold' and 'alertLengthThreshold' properties to a service which only has a http-gateway listener. We see WARN messages if the time threshold is surpassed, but none for the lenght threshold. > Diagnostics: > The problem with the alertLengthThreshold is that this only works if the message contains a property 'Environment.MESSAGE_BYTE_SIZE', see the ActionStatusBean constructor: > http://anonsvn.jboss.org/repos/labs/labs/jbossesb/tags/JBESB_4_9_CP1_ER8_... > This property is set in either the Util.serialize(Message) or Util.deserialize() method: > http://anonsvn.jboss.org/repos/labs/labs/jbossesb/tags/JBESB_4_9_CP1_ER8_... > But while one of these methods is called when other gateways are used (eg. with JMS through the org.jboss.internal.soa.esb.couriers.helpers.JmsComposer), this is apparently not the case with http-gateway. > Todo: > Improve the algorithm in ActionStatusBean which calculates the message bytes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-3690) When deploying unzipped, jbossas5 plugin is not finding the name of the deployment

by Tom Cunningham (JIRA)

When deploying unzipped, jbossas5 plugin is not finding the name of the deployment ---------------------------------------------------------------------------------- Key: JBESB-3690 URL: https://issues.jboss.org/browse/JBESB-3690 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.10 CP1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 CP1 When deploying unzipped, the jbossas5 is not getting the correct name of the deployment - it is finding null. Need to add the "deploymentName" in the jbossesb plugin. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3689) http_gateway quickstart doesn't output http request body to console as it should

by Tom Cunningham (JIRA)

http_gateway quickstart doesn't output http request body to console as it should -------------------------------------------------------------------------------- Key: JBESB-3689 URL: https://issues.jboss.org/browse/JBESB-3689 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.10 CP1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 CP1 This minor bug is located in org.jboss.soa.esb.samples.quickstart.httpgateway.MyAction. The process method is defined in following way: MyAction.java public String printHttpRequestInfo(@BodyParam byte[] httpPayload But this way the http body is not extracted from the request. The correct httpPayload type should be String. I think it is good to fix this because (unfortunately) this is the only place where @BodyParam anotation is used. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3687) Make clear in the documentation where to install Camel components

by Tom Cunningham (JIRA)

Make clear in the documentation where to install Camel components ----------------------------------------------------------------- Key: JBESB-3687 URL: https://issues.jboss.org/browse/JBESB-3687 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 4.10 CP1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 CP1 Make clear in the documentation where camel components are to be installed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBESB-3686) alertLengthThreshold does not work for http-gateway

by Martin Weiler (JIRA)

[ https://issues.jboss.org/browse/JBESB-3686?page=com.atlassian.jira.plugin... ] Martin Weiler updated JBESB-3686: --------------------------------- > alertLengthThreshold does not work for http-gateway > --------------------------------------------------- > > Key: JBESB-3686 > URL: https://issues.jboss.org/browse/JBESB-3686 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.9 CP1, 4.10 > Reporter: Martin Weiler > > We added 'alertTimeThreshold' and 'alertLengthThreshold' properties to a service which only has a http-gateway listener. We see WARN messages if the time threshold is surpassed, but none for the lenght threshold. > Diagnostics: > The problem with the alertLengthThreshold is that this only works if the message contains a property 'Environment.MESSAGE_BYTE_SIZE', see the ActionStatusBean constructor: > http://anonsvn.jboss.org/repos/labs/labs/jbossesb/tags/JBESB_4_9_CP1_ER8_... > This property is set in either the Util.serialize(Message) or Util.deserialize() method: > http://anonsvn.jboss.org/repos/labs/labs/jbossesb/tags/JBESB_4_9_CP1_ER8_... > But while one of these methods is called when other gateways are used (eg. with JMS through the org.jboss.internal.soa.esb.couriers.helpers.JmsComposer), this is apparently not the case with http-gateway. > Todo: > Improve the algorithm in ActionStatusBean which calculates the message bytes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBESB-3686) alertLengthThreshold does not work for http-gateway

by Martin Weiler (JIRA)

[ https://issues.jboss.org/browse/JBESB-3686?page=com.atlassian.jira.plugin... ] Martin Weiler moved SOA-3397 to JBESB-3686: ------------------------------------------- Project: JBoss ESB (was: JBoss Enterprise SOA Platform) Key: JBESB-3686 (was: SOA-3397) Affects Version/s: 4.10 4.9 CP1 (was: 5.1.0 GA) Component/s: Rosetta (was: JBossESB) > alertLengthThreshold does not work for http-gateway > --------------------------------------------------- > > Key: JBESB-3686 > URL: https://issues.jboss.org/browse/JBESB-3686 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.10, 4.9 CP1 > Reporter: Martin Weiler > > We added 'alertTimeThreshold' and 'alertLengthThreshold' properties to a service which only has a http-gateway listener. We see WARN messages if the time threshold is surpassed, but none for the lenght threshold. > Diagnostics: > The problem with the alertLengthThreshold is that this only works if the message contains a property 'Environment.MESSAGE_BYTE_SIZE', see the ActionStatusBean constructor: > http://anonsvn.jboss.org/repos/labs/labs/jbossesb/tags/JBESB_4_9_CP1_ER8_... > This property is set in either the Util.serialize(Message) or Util.deserialize() method: > http://anonsvn.jboss.org/repos/labs/labs/jbossesb/tags/JBESB_4_9_CP1_ER8_... > But while one of these methods is called when other gateways are used (eg. with JMS through the org.jboss.internal.soa.esb.couriers.helpers.JmsComposer), this is apparently not the case with http-gateway. > Todo: > Improve the algorithm in ActionStatusBean which calculates the message bytes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-3648) Router in Smooks Creates Inverse Persistence

by Tom Cunningham (JIRA)

Router in Smooks Creates Inverse Persistence -------------------------------------------- Key: JBESB-3648 URL: https://issues.jboss.org/browse/JBESB-3648 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transformation Service Affects Versions: 4.10 Reporter: Tom Cunningham Assignee: Tom Fennelly Fix For: 4.10 CP1 Smooks' JMS Router configures message persistence incorrectly. The documentation suggests the following configuration will result in persistent messages to the ESB: <jms:router routeOnElement="student" beanId="studentFragment" destination="queue/StudentRecordQueue"> <jms:message deliveryMode="persistent"/> </jms:router> Instead, this leads to non-persistent messages. This is due to a bug in org.milyn.routing.jms.JMSRouter: final int deliveryModeInt = "non-persistent".equals( jmsProperties.getDeliveryMode() ) ? DeliveryMode.PERSISTENT : DeliveryMode.NON_PERSISTENT; This should instead be the inverse: final int deliveryModeInt = "non-persistent".equals( jmsProperties.getDeliveryMode() ) ? DeliveryMode.NON_PERSISTENT : DeliveryMode.PERSISTENT; This is a particularly major bug because the work around will cause incorrect functionality in future versions of the ESB, which will hopefully fix the issue with a patched version of Smooks' JMS Cartridge. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues September 2011