esb-issues March 2008

esb-issues@lists.jboss.org

1 participants
236 discussions

[JBoss JIRA] Created: (JBESB-1570) bpm_orchestration deployProcess targets use wrong dependency

by Kevin Conner (JIRA)

bpm_orchestration deployProcess targets use wrong dependency ------------------------------------------------------------ Key: JBESB-1570 URL: http://jira.jboss.com/jira/browse/JBESB-1570 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.1 CP1, 4.2.1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 CP2, 4.3 The target dependency is jbossesb-dependencies instead of dependencies. -- 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

18 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1580) notifications quickstart is missing from revision 18709

by Len DiMaggio (JIRA)

notifications quickstart is missing from revision 18709 -------------------------------------------------------- Key: JBESB-1580 URL: http://jira.jboss.com/jira/browse/JBESB-1580 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 CP2 Reporter: Len DiMaggio Assigned To: Trevor Kirby Priority: Minor The summary says it all - the notifications quickstart is missing from revision 18709 -- 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

18 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1578) Update jms_transacted quickstart to demo activation-config properties and transation rollback

by Daniel Bevenius (JIRA)

Update jms_transacted quickstart to demo activation-config properties and transation rollback --------------------------------------------------------------------------------------------- Key: JBESB-1578 URL: http://jira.jboss.com/jira/browse/JBESB-1578 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.3 Reporter: Daniel Bevenius Assigned To: Daniel Bevenius Priority: Minor Fix For: 4.3 Just update to show how to add activation-config properties so there is an example for this. Also add a RollbackTransactionAction that shows how a global transaction can be rollback. -- 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

18 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1573) boot.log is truncated upon ESB Server startup

by Daniel Bevenius (JIRA)

boot.log is truncated upon ESB Server startup --------------------------------------------- Key: JBESB-1573 URL: http://jira.jboss.com/jira/browse/JBESB-1573 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 CP1 Reporter: Daniel Bevenius Priority: Critical boot.log is truncated upon startup of the ESBServer. I've tracked this down to the soapui-client.sar. By "unscoping" it the boot.log is no longer be truncated. Why this is happening I'm not sure...I'll continue to investigate but though I create this Jira in case someone else has any ideas. This might also be the cause of an issue that we are currently seeing. Our ESB suddenly starts to log to boot.log at the DEBUG level. This has caused our file system to fill up and actually stop the servers from handling more requests. I think I remember something about the soapui-client.sar being scoped because of some versions conflict, but I can rememeber which it was...jbossws maybe? I just tested to unscope soapui-client.sar and removed: jbossesb-rosetta.jar milyn*, lib/log4j.jar lib/commons-logging.jar I then ran the web service producer quickstart without any trouble. Is this sufficient to verify that soapui-client.sar can now run unscoped with 4_2_1_GA_CP. Any thoughs on this would be much appriciated. Thanks, Daniel -- 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

18 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-1572) Make sure docs are clear about ServiceInvoker and ESB-unaware EPRs

by Mark Little (JIRA)

Make sure docs are clear about ServiceInvoker and ESB-unaware EPRs ------------------------------------------------------------------ Key: JBESB-1572 URL: http://jira.jboss.com/jira/browse/JBESB-1572 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.1 CP1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.1 CP2 Invalid EPR for service (probably ESB-unaware): ignoring for message. -- 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

18 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1563) Extends jms-jca-provider to support activation-config properties

by Daniel Bevenius (JIRA)

Extends jms-jca-provider to support activation-config properties ---------------------------------------------------------------- Key: JBESB-1563 URL: http://jira.jboss.com/jira/browse/JBESB-1563 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation, Examples, Transports Affects Versions: 4.2.1 CP1 Reporter: Daniel Bevenius Fix For: 4.3 We would like to be able to specify activation-config properties for the jms-jca-provider. This would give us a jms redelivery functionality by simple configuration. The reason for this extension is that we have listeners that are not gateways, but still need to be able to set properties like dLQMaxResent. This is the suggestion: <jms-jca-provider name="JBossMessaging" .... > <jms-bus busid="quickstartGwChannel"> .... </jms-bus> <activation-config> <property name="dLQMaxResent" value="12"/> <property name="dLQJNDIName" value="/queue/quickstart_jms_transacted_error"/> <property name="reconnectInterval" value="1000"/> </activation-config> </jms-jca-provider> This requires an update to the jbossesb-1.0.1.xsd and modifying JmsListenerMapper. The gain here is that we can then specify the number of times that we should try to redeliver a message. One can also specify an interval so that the message is not redelivered straight away. I noticed that jca seems to have the dLQMaxResent but the JMS queue definitions also have their own. If one has set dLQMaxResent to a value larger then the JMS queues MaxDeliveryAttempts value, then the JMS queues value will kickin. But by simply increasing MaxDeliveryAttempts to larger value then dLQMaxResent everything works. I've verified this by modifying the jms_transacted quickstart and trying it out. -- 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

18 years, 1 month

1
5
0 / 0

← Newer
1
...
21
22
23
24
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues March 2008