January 2013 - esb-issues - Jboss List Archives

[JBoss JIRA] (JBESB-3896) JBpmObjectMapper doesn't appear to handle missing variables properly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBESB-3896?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated JBESB-3896: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=896634, https://bugzilla.redhat.com/show_bug.cgi?id=896640 (was: https://bugzilla.redhat.com/show_bug.cgi?id=896634) > JBpmObjectMapper doesn't appear to handle missing variables properly > --------------------------------------------------------------------- > > Key: JBESB-3896 > URL: https://issues.jboss.org/browse/JBESB-3896 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Rick Wagner > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3896) JBpmObjectMapper doesn't appear to handle missing variables properly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBESB-3896?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBESB-3896: ------------------------------------------------ Rick Wagner <rwagner(a)redhat.com> made a comment on [bug 896640|https://bugzilla.redhat.com/show_bug.cgi?id=896640] +++ This bug was initially created as a clone of Bug #896634 +++ Description of problem: Customer has raised the point that JBpmObjectMapper doesn't make it to what appears to be the intended log statement when a jBPM-side variable is not present. This can be validated by inserting the following method into JBpmObjectMapperUnitTest.java: // Same as existing test, just commented out setting v1. @Test public void testMissingObject() throws Exception // Things to look for: // 1) If the variable does not exist in the jbpm variable map, the execution context is tested, but if not present there, an exception is thrown. // It looks like the intention was to arrive at "log.warn("The object " + mapping.getBpm() + " is null and cannot not be set on the message")" { SAXReader reader = new SAXReader(); Document document = reader.read(this.getClass().getResourceAsStream("/" + PROCESS_DEF_XML)); Element element = document.getRootElement(); DefaultElement bpmToEsbVars = (DefaultElement) element.element("start-state").element("transition").element("action").element("bpmToEsbVars"); String helloWorldTokenScope = "Hello world token scope"; String helloWorldGlobalScope = "Hello world process-instance scope"; TestJBPMVariable objectTokenScope = new TestJBPMVariable("Object token scope") ; TestJBPMVariable objectGlobalScope = new TestJBPMVariable("Object global scope") ; Token token = processInstance.getRootToken(); // Don't set v1, see what happens //processInstance.getContextInstance().setVariable("v1", helloWorldTokenScope, token); processInstance.getContextInstance().setVariable("g2", helloWorldGlobalScope); processInstance.getContextInstance().setVariable("h3", objectTokenScope, token); processInstance.getContextInstance().setVariable("i4", objectGlobalScope); ExecutionContext executionContext = new ExecutionContext(token); JBpmObjectMapper mapper = new JBpmObjectMapper(); Message message = mapper.mapFromJBpmToEsbMessage(bpmToEsbVars, Boolean.FALSE, executionContext); assertEquals(helloWorldTokenScope,String.valueOf(message.getBody().get("esbObj1"))); assertEquals(helloWorldGlobalScope,String.valueOf(message.getBody().get("esbObj2"))); assertEquals(objectTokenScope.getInternal(), String.valueOf(message.getBody().get("esbObj3"))); assertEquals(objectGlobalScope.getInternal(), String.valueOf(message.getBody().get("esbObj4"))); } > JBpmObjectMapper doesn't appear to handle missing variables properly > --------------------------------------------------------------------- > > Key: JBESB-3896 > URL: https://issues.jboss.org/browse/JBESB-3896 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Rick Wagner > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3896) JBpmObjectMapper doesn't appear to handle missing variables properly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBESB-3896?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated JBESB-3896: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=896634 > JBpmObjectMapper doesn't appear to handle missing variables properly > --------------------------------------------------------------------- > > Key: JBESB-3896 > URL: https://issues.jboss.org/browse/JBESB-3896 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Rick Wagner > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3896) JBpmObjectMapper doesn't appear to handle missing variables properly

by Rick Wagner (JIRA)

[ https://issues.jboss.org/browse/JBESB-3896?page=com.atlassian.jira.plugin... ] Rick Wagner commented on JBESB-3896: ------------------------------------ JBpmObjectMapper doesn't make it to what appears to be the intended log statement when a jBPM-side variable is not present. This can be validated by commenting out the setting of a variable (say 'v1') in method jBpmVariableMap(). It looks like you should expect a log warn, but an Exception happens upstream from that. > JBpmObjectMapper doesn't appear to handle missing variables properly > --------------------------------------------------------------------- > > Key: JBESB-3896 > URL: https://issues.jboss.org/browse/JBESB-3896 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Rick Wagner > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3896) JBpmObjectMapper doesn't appear to handle missing variables properly

by Rick Wagner (JIRA)

Rick Wagner created JBESB-3896: ---------------------------------- Summary: JBpmObjectMapper doesn't appear to handle missing variables properly Key: JBESB-3896 URL: https://issues.jboss.org/browse/JBESB-3896 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Rick Wagner -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3862) AbstractBpm5Action is registering handlers too freely

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3862?page=com.atlassian.jira.plugin... ] Tom Cunningham reopened JBESB-3862: ----------------------------------- > AbstractBpm5Action is registering handlers too freely > ----------------------------------------------------- > > Key: JBESB-3862 > URL: https://issues.jboss.org/browse/JBESB-3862 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Process flow > Affects Versions: 4.11 > Reporter: Tom Cunningham > Assignee: Tom Cunningham > Fix For: 4.11 CP1 > > > Explanation from Rick Wagner's BZ : > AbstractBpm5Action is doing some handler registration for *each* process instance start and service callback: > .... > ksession.getWorkItemManager().registerWorkItemHandler("JBossESB", esbhandler); > ksession.getWorkItemManager().registerWorkItemHandler("ESBAction", actionhandler); > ksession.getWorkItemManager().registerWorkItemHandler("Human Task", khandler); > 'khandler' in particular is an instance of CommandBasedHornetQWSHumanTaskHandler by default. > So when the user goes to close a task, all those handlers fire (JPA trips up, too): > 012-08-22 12:32:06,006 INFO [STDOUT] (Thread-32) Notification of completed task 132 > 2012-08-22 12:32:06,017 INFO [STDOUT] (Thread-34) Notification of completed task 132 > 2012-08-22 12:32:06,025 INFO [STDOUT] (Thread-35) Notification of completed task 132 > 2012-08-22 12:32:06,033 INFO [STDOUT] (Thread-36) Notification of completed task 132 > 2012-08-22 12:32:06,042 INFO [STDOUT] (Thread-37) Notification of completed task 132 > 2012-08-22 12:32:06,049 INFO [STDOUT] (Thread-37) Notification of completed task 132 > 2012-08-22 12:32:06,056 INFO [STDOUT] (Thread-38) Notification of completed task 132 > 2012-08-22 12:32:06,063 INFO [STDOUT] (Thread-39) Notification of completed task 132 > 2012-08-22 12:32:06,069 INFO [STDOUT] (Thread-40) Notification of completed task 132 > 2012-08-22 12:32:06,076 INFO [STDOUT] (Thread-41) Notification of completed task 132 > 2012-08-22 12:32:06,082 INFO [STDOUT] (Thread-41) Notification of completed task 132 > 2012-08-22 12:32:05,985 INFO [STDOUT] (Thread-31) Notification of completed task 132 > 2012-08-22 12:32:05,998 ERROR [org.hibernate.event.def.AbstractFlushingEventListener] (Thread-31) Could not synchronize database state with session > org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [org.jbpm.persistence.processinstance.ProcessInstanceInfo#44] > at org.hibernate.persister.entity.AbstractEntityPersister.check(AbstractEntityPersister.java:1782) > ....... > at org.jbpm.task.service.hornetq.CommandBasedHornetQWSHumanTaskHandler$GetCompletedTaskResponseHandler.execute(CommandBasedHornetQWSHumanTaskHandler.java:273) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3895) Need to increase the size of j3_key_data_value.key_data_value to 2048

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBESB-3895?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBESB-3895: ------------------------------------------------ tcunning(a)redhat.com changed the Status of [bug 894323|https://bugzilla.redhat.com/show_bug.cgi?id=894323] from NEW to MODIFIED > Need to increase the size of j3_key_data_value.key_data_value to 2048 > --------------------------------------------------------------------- > > Key: JBESB-3895 > URL: https://issues.jboss.org/browse/JBESB-3895 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Registry and Repository > Affects Versions: 4.11 CP2 > Reporter: Tom Cunningham > Assignee: Tom Cunningham > Fix For: 4.11 CP2 > > > Need to increase the size of j3_key_data_value to 2048 - see https://bugzilla.redhat.com/show_bug.cgi?id=894323 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3895) Need to increase the size of j3_key_data_value.key_data_value to 2048

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3895?page=com.atlassian.jira.plugin... ] Tom Cunningham closed JBESB-3895. --------------------------------- > Need to increase the size of j3_key_data_value.key_data_value to 2048 > --------------------------------------------------------------------- > > Key: JBESB-3895 > URL: https://issues.jboss.org/browse/JBESB-3895 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Registry and Repository > Affects Versions: 4.11 CP2 > Reporter: Tom Cunningham > Assignee: Tom Cunningham > Fix For: 4.11 CP2 > > > Need to increase the size of j3_key_data_value to 2048 - see https://bugzilla.redhat.com/show_bug.cgi?id=894323 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3895) Need to increase the size of j3_key_data_value.key_data_value to 2048

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3895?page=com.atlassian.jira.plugin... ] Tom Cunningham resolved JBESB-3895. ----------------------------------- Assignee: Tom Cunningham Resolution: Done > Need to increase the size of j3_key_data_value.key_data_value to 2048 > --------------------------------------------------------------------- > > Key: JBESB-3895 > URL: https://issues.jboss.org/browse/JBESB-3895 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Registry and Repository > Affects Versions: 4.11 CP2 > Reporter: Tom Cunningham > Assignee: Tom Cunningham > Fix For: 4.11 CP2 > > > Need to increase the size of j3_key_data_value to 2048 - see https://bugzilla.redhat.com/show_bug.cgi?id=894323 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3895) Need to increase the size of j3_key_data_value.key_data_value to 2048

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3895?page=com.atlassian.jira.plugin... ] Tom Cunningham updated JBESB-3895: ---------------------------------- Fix Version/s: 4.11 CP2 > Need to increase the size of j3_key_data_value.key_data_value to 2048 > --------------------------------------------------------------------- > > Key: JBESB-3895 > URL: https://issues.jboss.org/browse/JBESB-3895 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Registry and Repository > Reporter: Tom Cunningham > Fix For: 4.11 CP2 > > > Need to increase the size of j3_key_data_value to 2048 - see https://bugzilla.redhat.com/show_bug.cgi?id=894323 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues January 2013