October 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1288) Remove deprecated code from messagefilter quickstart

by Kevin Conner (JIRA)

Remove deprecated code from messagefilter quickstart ---------------------------------------------------- Key: JBESB-1288 URL: http://jira.jboss.com/jira/browse/JBESB-1288 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 IR2 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1289) Fix groovy gateway actions

by Kevin Conner (JIRA)

Fix groovy gateway actions -------------------------- Key: JBESB-1289 URL: http://jira.jboss.com/jira/browse/JBESB-1289 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 IR2 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1219) Helloworld_sql_action throws exceptions

by Tom Cunningham (JIRA)

Helloworld_sql_action throws exceptions --------------------------------------- Key: JBESB-1219 URL: http://jira.jboss.com/jira/browse/JBESB-1219 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 IR2 Reporter: Tom Cunningham Assigned To: Mark Little Fix For: 4.2.1 Helloworld_sql_action is throwing exceptions related to the recent payload changes in SqlTableGatewayListener.java 10:29:04,115 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 10:29:04,116 WARN [ActionProcessingPipeline] Unexpected exception caught while processing the action pipeline: header: [ To: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/A/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:message-selector : source='fromHelloworldSQLAction'/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : 1/> > ] MessageID: ID:JBM-12294 RelatesTo: jms:correlationID#e0eb8628-3ee6-4dca-bced-2059fcee1aac ] org.jboss.soa.esb.actions.ActionProcessingException: Unexpected invocation target exception from processor at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:127) at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:273) at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:303) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:613) Caused by: java.lang.NullPointerException at org.jboss.soa.esb.samples.quickstart.helloworldsqlaction.MyAction.displayMessage(MyAction.java:45) 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.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102) ... 6 more 10:29:04,131 WARN [ActionProcessingPipeline] No fault address defined for fault message! header: [ To: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/A/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:message-selector : source='fromHelloworldSQLAction'/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : 1/> > ] MessageID: ID:JBM-12294 RelatesTo: jms:correlationID#e0eb8628-3ee6-4dca-bced-2059fcee1aac ] 10:29:04,160 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

4
4
0 / 0

[JBoss JIRA] Created: (JBESB-1286) AbstractFileGateway dosn't handle a null File[] coming back from the filter

by Tom Fennelly (JIRA)

AbstractFileGateway dosn't handle a null File[] coming back from the filter --------------------------------------------------------------------------- Key: JBESB-1286 URL: http://jira.jboss.com/jira/browse/JBESB-1286 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2.1 IR2 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2.1 This can happen if the config is wrong... just add a check and a warn log. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1284) Incorrect warning emitted during default action processing

by Kevin Conner (JIRA)

Incorrect warning emitted during default action processing ---------------------------------------------------------- Key: JBESB-1284 URL: http://jira.jboss.com/jira/browse/JBESB-1284 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 IR2 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 If an implicit chain returns a null message then there should be no warning emitted, it is treated as a one way service. There should be a test around the warning in the reply to processing of the main process method. Also, it would be better to rename the warnResponses variable to defaultProcessing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1188) Check SQL resource usage for transacted environment

by Kevin Conner (JIRA)

Check SQL resource usage for transacted environment --------------------------------------------------- Key: JBESB-1188 URL: http://jira.jboss.com/jira/browse/JBESB-1188 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 IR2 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-1282) How does DLQ work when message payload types are out of scope of the service?

by Tom Fennelly (JIRA)

How does DLQ work when message payload types are out of scope of the service? ----------------------------------------------------------------------------- Key: JBESB-1282 URL: http://jira.jboss.com/jira/browse/JBESB-1282 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Process flow, Rosetta Affects Versions: 4.2.1 IR2 Reporter: Tom Fennelly Assigned To: Kurt Stam Fix For: 4.2.1 triage Just wondering e.g. the DLQ is running as a centralized service... it's forwarded a failed message that contains payload types that it knows nothing about... what should happen? I'm seeing an exception related to this on th aggregator quickstart. The DLQ service is running on the AS, while the individual serives are all running standalone. The DLQ Service has no visibility on the payload types bound to them failed messages that get delivered to it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

3
8
0 / 0

[JBoss JIRA] Created: (JBESB-1276) Update documentation PDFs

by Kevin Conner (JIRA)

Update documentation PDFs ------------------------- Key: JBESB-1276 URL: http://jira.jboss.com/jira/browse/JBESB-1276 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1246) SqlTableGatewayListener : Field names not handled well in terms of case (Upper/Lowercase)

by Tom Cunningham (JIRA)

SqlTableGatewayListener : Field names not handled well in terms of case (Upper/Lowercase) ----------------------------------------------------------------------------------------- Key: JBESB-1246 URL: http://jira.jboss.com/jira/browse/JBESB-1246 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2.1 IR2 Reporter: Tom Cunningham Assigned To: Mark Little Fix For: 4.2.1 In SqlTableGatewayListener, a row is grabbed and then turned into a hash, which is checked to change status. If the case of the field name in the hash doesn't match the case of the field name in jboss-esb.xml, the row will never be updated. The case in which the drivers return the field name differs from database to database, so we should probably do something here to make the field names case-insensitive by uppercasing what we see in jboss-esb.xml for status_column, message-id-column, order-by-column, etc. and upper casing what is in the currentRow hash. I saw problems in MySQL with this code while testing the helloworld_sql_action example. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-1278) The Message type is Serializable, but it's constituent parts are not (Header, Body etc)

by Tom Fennelly (JIRA)

The Message type is Serializable, but it's constituent parts are not (Header, Body etc) --------------------------------------------------------------------------------------- Key: JBESB-1278 URL: http://jira.jboss.com/jira/browse/JBESB-1278 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 IR2 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues October 2007