October 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Commented: (JBPM-1448) jBPM does not initialise thread context classloader

by Alejandro Guizar (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1448?page=com.atlassian.jira.plug... ] Alejandro Guizar commented on JBPM-1448: ---------------------------------------- The tests pass when running under sun 1.5.0.15, so it has to do with openjdk (or my particular version of it). > jBPM does not initialise thread context classloader > --------------------------------------------------- > > Key: JBPM-1448 > URL: https://jira.jboss.org/jira/browse/JBPM-1448 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Engine > Reporter: Kevin Conner > Assignee: Bernd Ruecker > Priority: Critical > Fix For: SOA 4.2 CP03, SOA 4.3, jBPM 3.3.0 GA > > > jBPM does not initialise the thread context classloader when executing actions within the process. > The outcome of this decision is that code executed within the context of this action will not have access to classes/resources in the par unless the action classloader is an explicit parameter. > One example of this is the RMI marshalling layer, which has an implication on JNDI lookups. -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1448) jBPM does not initialise thread context classloader

by Alejandro Guizar (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1448?page=com.atlassian.jira.plug... ] Alejandro Guizar updated JBPM-1448: ----------------------------------- Comment: was deleted > jBPM does not initialise thread context classloader > --------------------------------------------------- > > Key: JBPM-1448 > URL: https://jira.jboss.org/jira/browse/JBPM-1448 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Engine > Reporter: Kevin Conner > Assignee: Bernd Ruecker > Priority: Critical > Fix For: SOA 4.2 CP03, SOA 4.3, jBPM 3.3.0 GA > > > jBPM does not initialise the thread context classloader when executing actions within the process. > The outcome of this decision is that code executed within the context of this action will not have access to classes/resources in the par unless the action classloader is an explicit parameter. > One example of this is the RMI marshalling layer, which has an implication on JNDI lookups. -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1448) jBPM does not initialise thread context classloader

by Alejandro Guizar (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1448?page=com.atlassian.jira.plug... ] Alejandro Guizar commented on JBPM-1448: ---------------------------------------- Bernd's latest changes (r2601) have made these failures disappear. They should also disappear from the Hudson build. > jBPM does not initialise thread context classloader > --------------------------------------------------- > > Key: JBPM-1448 > URL: https://jira.jboss.org/jira/browse/JBPM-1448 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Engine > Reporter: Kevin Conner > Assignee: Bernd Ruecker > Priority: Critical > Fix For: SOA 4.2 CP03, SOA 4.3, jBPM 3.3.0 GA > > > jBPM does not initialise the thread context classloader when executing actions within the process. > The outcome of this decision is that code executed within the context of this action will not have access to classes/resources in the par unless the action classloader is an explicit parameter. > One example of this is the RMI marshalling layer, which has an implication on JNDI lookups. -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1448) jBPM does not initialise thread context classloader

by Alejandro Guizar (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1448?page=com.atlassian.jira.plug... ] Alejandro Guizar commented on JBPM-1448: ---------------------------------------- I do see those failures outside Hudson. I only see the failures when running all tests (mvn test) but not when running ProcessArchiveDeploymentDbTest separately (mvn -Dtest=ProcessArchiveDeploymentDbTest test). My environment: aguizar@popolvuh:~/jbpm3/trunk/modules/core$ mvn --version Maven version: 2.0.8 Java version: 1.6.0_0 ** OpenJDK (build 1.6.0_0-b11) OS name: "linux" version: "2.6.24-21-generic" arch: "i386" Family: "unix" > jBPM does not initialise thread context classloader > --------------------------------------------------- > > Key: JBPM-1448 > URL: https://jira.jboss.org/jira/browse/JBPM-1448 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Engine > Reporter: Kevin Conner > Assignee: Bernd Ruecker > Priority: Critical > Fix For: SOA 4.2 CP03, SOA 4.3, jBPM 3.3.0 GA > > > jBPM does not initialise the thread context classloader when executing actions within the process. > The outcome of this decision is that code executed within the context of this action will not have access to classes/resources in the par unless the action classloader is an explicit parameter. > One example of this is the RMI marshalling layer, which has an implication on JNDI lookups. -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1448) jBPM does not initialise thread context classloader

by Bernd Ruecker (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1448?page=com.atlassian.jira.plug... ] Bernd Ruecker commented on JBPM-1448: ------------------------------------- Seems nobody can reproduce this test locally. Tom and me added some more testing and fixed a small bug there (well spotted Tom!), in my eyes everything should be fine now... Let's see what Hudson says (Heiko wanted to try it locally with Hudson as well) > jBPM does not initialise thread context classloader > --------------------------------------------------- > > Key: JBPM-1448 > URL: https://jira.jboss.org/jira/browse/JBPM-1448 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Engine > Reporter: Kevin Conner > Assignee: Bernd Ruecker > Priority: Critical > Fix For: SOA 4.2 CP03, SOA 4.3, jBPM 3.3.0 GA > > > jBPM does not initialise the thread context classloader when executing actions within the process. > The outcome of this decision is that code executed within the context of this action will not have access to classes/resources in the par unless the action classloader is an explicit parameter. > One example of this is the RMI marshalling layer, which has an implication on JNDI lookups. -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1448) jBPM does not initialise thread context classloader

by Ronald van Kuijk (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1448?page=com.atlassian.jira.plug... ] Ronald van Kuijk commented on JBPM-1448: ---------------------------------------- I do not see this locally (no hudson, just testing with maven) on java 6 (openjdk, linux)...strange. Maybe add some debug to the test to see where it tries to get the resource from (although if it is null that is kind of hard). Locally the URL is processresource://resourceprocess/classes/classes/org/jbpm/jpdl/par/classresource.txt > jBPM does not initialise thread context classloader > --------------------------------------------------- > > Key: JBPM-1448 > URL: https://jira.jboss.org/jira/browse/JBPM-1448 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Engine > Reporter: Kevin Conner > Assignee: Bernd Ruecker > Priority: Critical > Fix For: SOA 4.2 CP03, SOA 4.3, jBPM 3.3.0 GA > > > jBPM does not initialise the thread context classloader when executing actions within the process. > The outcome of this decision is that code executed within the context of this action will not have access to classes/resources in the par unless the action classloader is an explicit parameter. > One example of this is the RMI marshalling layer, which has an implication on JNDI lookups. -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1762) Fix JIRA config for subversion/fisheye views

by Thomas Diesler (JIRA)

Fix JIRA config for subversion/fisheye views -------------------------------------------- Key: JBPM-1762 URL: https://jira.jboss.org/jira/browse/JBPM-1762 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: jBPM 3.3.0 GA Please have a look at http://jbpm.dyndns.org/jbpmwiki/index.php?title=JBPM3ProjectInfrastructur... for the correct SVN and Fisheye locations -- 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

16 years, 2 months

1
4
0 / 0

[JBoss JIRA] Commented: (JBPM-1448) jBPM does not initialise thread context classloader

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1448?page=com.atlassian.jira.plug... ] Thomas Diesler commented on JBPM-1448: -------------------------------------- There is still a classloading problem showing up with jdk1.6 http://jbpm.dyndns.org:8280/hudson/job/jBPM3-JDK1.6/5/testReport/ Caused by: java.lang.NullPointerException at org.jbpm.jpdl.par.ResourceAction.execute(ResourceAction.java:24) at org.jbpm.graph.def.Action.execute(Action.java:129) at org.jbpm.graph.def.GraphElement.executeAction(GraphElement.java:256) > jBPM does not initialise thread context classloader > --------------------------------------------------- > > Key: JBPM-1448 > URL: https://jira.jboss.org/jira/browse/JBPM-1448 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Engine > Reporter: Kevin Conner > Assignee: Bernd Ruecker > Priority: Critical > Fix For: SOA 4.2 CP03, SOA 4.3, jBPM 3.3.0 GA > > > jBPM does not initialise the thread context classloader when executing actions within the process. > The outcome of this decision is that code executed within the context of this action will not have access to classes/resources in the par unless the action classloader is an explicit parameter. > One example of this is the RMI marshalling layer, which has an implication on JNDI lookups. -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-2) Add an analytical dashboard to the console

by Heiko Braun (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-2?page=com.atlassian.jira.plugin.... ] Heiko Braun updated JBPM-2: --------------------------- Summary: Add an analytical dashboard to the console (was: Initial Business Intelligence (BI) capabilities) Component/s: BI and BAM (was: Core Engine) Fix Version/s: GWT Console 1.0.0 GA (was: jBPM 3.3.0 GA) > Add an analytical dashboard to the console > ------------------------------------------ > > Key: JBPM-2 > URL: https://jira.jboss.org/jira/browse/JBPM-2 > Project: JBoss jBPM > Issue Type: Feature Request > Components: BI and BAM > Environment: N/A > Reporter: Ronald van Kuijk > Assignee: Heiko Braun > Fix For: GWT Console 1.0.0 GA > > > JBoss jBPM should provide information on how processes are or have been running. Some people would call this BAM (Business Activity Monitoring), some call it BI (Business Intelligence) Some info can be found on http://www.javareport.com/article.asp?id=9238 and http://bizintelligencepipeline.com/howto/showArticle.jhtml?articleId=4990... > 1. jBPM should store the duration and start date of a state/process in the logs > 2. Write some detailed info on wiki > 3. Show processinstance and data > 4. day/week/month overviews > 5. near realtime data per process > 6. produce graphs of day/week/month overviews > Some more ideas i got from a requirements document... > - Number of cases processed in through a particular process definition > - Number of cases flowing through a particular activity > - Longest work item delay by activity > - Workitems awaiting a particular task > - Workitems in a specific worklist claimed and/or completed by a particular user > - Longest end-to-end delay > - Mean time to approve by activity by participant > - Mean end-to-end completion time. > as background info, here's what the competition says about BAM: > http://appian.com/AppianEnt/Analytics/analytics.html > http://www.webmethods.com/meta/default/folder/0000005936 > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/introduc... > http://www.tibco.com/software/business_optimization/activity_monitoring.j... > http://www.vitria.com/products/platform/bam.html > http://looselycoupled.com/glossary/BAM -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-2) Initial Business Intelligence (BI) capabilities

by Heiko Braun (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-2?page=com.atlassian.jira.plugin.... ] Heiko Braun commented on JBPM-2: -------------------------------- Guys, discussion belong into the dev forum and should be referenced from here. I am moving all of this to http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183956#4183956. > Initial Business Intelligence (BI) capabilities > ----------------------------------------------- > > Key: JBPM-2 > URL: https://jira.jboss.org/jira/browse/JBPM-2 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Environment: N/A > Reporter: Ronald van Kuijk > Assignee: Heiko Braun > Fix For: jBPM 3.3.0 GA > > > JBoss jBPM should provide information on how processes are or have been running. Some people would call this BAM (Business Activity Monitoring), some call it BI (Business Intelligence) Some info can be found on http://www.javareport.com/article.asp?id=9238 and http://bizintelligencepipeline.com/howto/showArticle.jhtml?articleId=4990... > 1. jBPM should store the duration and start date of a state/process in the logs > 2. Write some detailed info on wiki > 3. Show processinstance and data > 4. day/week/month overviews > 5. near realtime data per process > 6. produce graphs of day/week/month overviews > Some more ideas i got from a requirements document... > - Number of cases processed in through a particular process definition > - Number of cases flowing through a particular activity > - Longest work item delay by activity > - Workitems awaiting a particular task > - Workitems in a specific worklist claimed and/or completed by a particular user > - Longest end-to-end delay > - Mean time to approve by activity by participant > - Mean end-to-end completion time. > as background info, here's what the competition says about BAM: > http://appian.com/AppianEnt/Analytics/analytics.html > http://www.webmethods.com/meta/default/folder/0000005936 > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/introduc... > http://www.tibco.com/software/business_optimization/activity_monitoring.j... > http://www.vitria.com/products/platform/bam.html > http://looselycoupled.com/glossary/BAM -- 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

16 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues October 2008