March 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2425) BeanConfigActionProcessor swallows specialized exceptions

by Hudaverdi Cakir (JIRA)

BeanConfigActionProcessor swallows specialized exceptions --------------------------------------------------------- Key: JBESB-2425 URL: https://jira.jboss.org/jira/browse/JBESB-2425 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.5 Reporter: Hudaverdi Cakir The current implementation of BeanConfigActionProcessor catches at java.lang.Exception level and re-packages these exceptions into an ActionProcessingException. But when a particular Action throws a specialized exception, e.g. ActionProcessingFaultException, the information gets lost and the processing can not be controlled as desired. -- 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, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-2207) SqlTableGatewayListener does not support synchronous delivery.

by Tomasz Juchniewicz (JIRA)

SqlTableGatewayListener does not support synchronous delivery. -------------------------------------------------------------- Key: JBESB-2207 URL: https://jira.jboss.org/jira/browse/JBESB-2207 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Tomasz Juchniewicz -- 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, 6 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-2100) InVM exception

by Joakim Sandström (JIRA)

InVM exception -------------- Key: JBESB-2100 URL: https://jira.jboss.org/jira/browse/JBESB-2100 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 4.4 Reporter: Joakim Sandström >From my forum post: My logs gets filled up with the following exception, any ideas what is wrong with my configuration? I'm using jboss-4.2.3.GA, jbossesb-4.4.GA, jboss messaging 1.4.0.SP3 and MySQL 5.0.67. 2008-10-07 05:07:20,334 DEBUG [org.jboss.internal.soa.esb.couriers.InVMCourier] InVMCourier for EPR 'invm://6f72646572636865636b437573746f6d657246455342/false?false#10000' is not activ e. Cannot pickup/deliver on this courier. java.lang.Exception at org.jboss.internal.soa.esb.couriers.InVMCourier.isCourierActive(InVMCourier.java:281) at org.jboss.internal.soa.esb.couriers.InVMCourier.pickup(InVMCourier.java:217) at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:240) at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:216) at org.jboss.soa.esb.listeners.message.MessageAwareListener.waitForEventAndProcess(MessageAwareListener.java:280) at org.jboss.soa.esb.listeners.message.MessageAwareListener.doRun(MessageAwareListener.java:248) at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115) at java.lang.Thread.run(Thread.java:619) JBoss esb generates about 1GB of logs each minute due to this error, about 800K of InVM errors. -- 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, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-2075) PreparedStatement Factory for debugging

by Mark Little (JIRA)

PreparedStatement Factory for debugging --------------------------------------- Key: JBESB-2075 URL: https://jira.jboss.org/jira/browse/JBESB-2075 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta, Testing Affects Versions: 4.4 Reporter: Mark Little Consider reworking JDBC transport code to use a PreparedStatement factory pattern that can return a debug-enabled instance for improved traceability. I've got an implementation from JBossTS and I think Kevin has one too. -- 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, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2067) Revisit DataFilerScheduler and address scheduler

by Kevin Conner (JIRA)

Revisit DataFilerScheduler and address scheduler ------------------------------------------------ Key: JBESB-2067 URL: https://jira.jboss.org/jira/browse/JBESB-2067 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.4 Reporter: Kevin Conner It is currently setup to use the default quartz scheduler. -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2035) Spring Security as part of service definition.

by Chris Harris (JIRA)

Spring Security as part of service definition. ----------------------------------------------- Key: JBESB-2035 URL: https://jira.jboss.org/jira/browse/JBESB-2035 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 CP3 Reporter: Chris Harris A customer would like clean integration with Spring Security. It would be nice to be able to define the security constrains as part of the service definition. -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1897) ClassCastException while Drools is getting shadow object

by Martin Vecera (JIRA)

ClassCastException while Drools is getting shadow object -------------------------------------------------------- Key: JBESB-1897 URL: https://jira.jboss.org/jira/browse/JBESB-1897 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.3 Environment: Drools 4.0.2 and 4.0.7 (tried with both), mvel 1.2.24 and 1.3.1 (tried with both), QS bpm_orchestration4 Reporter: Martin Vecera Reproducible 100% = Basic plot = bpm_orchestration4 has the following message flow (it is little bit simplified but covers important parts): starter service -> jBPM process that calls -> intake service with Drools action -> back to jBPM process -> task assigned to an user -> jBPM process calls -> discount service with another Drools action (*) (*) Shows the part where problem arises (inside Drools action): 2008-08-04 08:42:16,210 WARN [org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] Unexpected exception caught while processing the action pipeline: header: [ To: InVMEpr [ PortReferenc org.drools.RuntimeDroolsException: Error creating shadow fact for object: 2, Wed Nov 15 19:45:28 GMT+01:00 2006, 0, 59.97, 64.92, 4.95, at org.drools.reteoo.Rete$ClassObjectTypeConf.getShadow(Rete.java:636) at org.drools.reteoo.Rete.assertObject(Rete.java:164) at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:192) at org.drools.reteoo.ReteooWorkingMemory.doInsert(ReteooWorkingMemory.java:71) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:911) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:883) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:684) at org.jboss.internal.soa.esb.services.routing.cbr.JBossRulesRouter.route(JBossRulesRouter.java:169) at org.jboss.soa.esb.actions.BusinessRulesProcessor.process(BusinessRulesProcessor.java:58) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316) at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:530) 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:595) Caused by: java.lang.ClassCastException: org.jboss.soa.esb.store.OrderHeader at org.jboss.soa.esb.store.OrderHeaderShadowProxy.setShadowedObject(Unknown Source) at org.drools.reteoo.Rete$ClassObjectTypeConf.getShadow(Rete.java:634) ... 13 more The same exception is thrown for both Drools/mvel versions. You have to execute the QS at least TWICE to get the exception (for the first time it works well)! Steps to reproduce: 1. get ESB 4.3.0GA binaries, start it 2. execute samples/quickstarts/bpm_orchestration4 (ant deploy, deployProcess, startProcess) 3. click "Save and Close" on every task that appears in jBPM console 4. the first time the QS finishes without problems so run ant startProcess once more 5. click "Save and Close" on the first task in jBPM console, you won't get the second task assigned since the exception is thrown This QS (from version 4.3.0.GA) works fine with ESB server from trunk (08/04/2008). When I skipped the return from the intake service to jBPM process and put static router from intake service directly to discount service (skipping appropriate process nodes as well), the problem didn't show up. -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1558) StringTemplateProcessor does not propagate message contents to template

by Jiri Pechanec (JIRA)

StringTemplateProcessor does not propagate message contents to template ----------------------------------------------------------------------- Key: JBESB-1558 URL: http://jira.jboss.com/jira/browse/JBESB-1558 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Adapters, Documentation Affects Versions: 4.2.1 CP1 Reporter: Jiri Pechanec Fix For: 4.2.1 CP2 There is a StringTemplateProcessor action. I would expect that it will take the contents of the message (all positions) and will propagate it to string template for processing. But instead of it it expects that there is Map store in message default position and propagates only this one. As there is no documentation related to this action I raise it as bug. If it is WAD please close 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

14 years, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-1603) Should have a JMS clustering QS

by Tom Cunningham (JIRA)

Should have a JMS clustering QS ------------------------------- Key: JBESB-1603 URL: http://jira.jboss.com/jira/browse/JBESB-1603 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 CP1 Reporter: Tom Cunningham Assigned To: Tom Cunningham We should have a QS that demonstrates clustered JMS queues/topics, and ideally, that will help setup clustering as part of the setup. -- 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

14 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-1349) ESB test suite hardcoded for hsqldb

by Len DiMaggio (JIRA)

ESB test suite hardcoded for hsqldb ----------------------------------- Key: JBESB-1349 URL: http://jira.jboss.com/jira/browse/JBESB-1349 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.2.1 Reporter: Len DiMaggio Assigned To: Kevin Conner ESB Project issue for SOA-150 ESB test suite seems hardcoded to use hsqldb. And I don't see it easily changing few properties and get it running against another database. Let Aleksandar Kostadinov <akostadi(a)redhat.com> know if you need access to databases in the QA Lab. -- 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

14 years, 6 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues March 2009