[JBoss JIRA] Commented: (JBPM-619) MailTests failure
by Tom Baeyens (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-619?page=comments#action_12354424 ]
Tom Baeyens commented on JBPM-619:
----------------------------------
i still don't get the point.
is it a memory leak ? i have done some tests (see org.jbpm.perf.*) to check jBPM's memory and performance. there it seems ok. probably there are some other reasons why memory is being consumed in the unit tests. main reson will probably be initialization and no clean up of member fields in the tests. i don't feel like going back and fixing this for the test suite since there is a general execution test showing that there is no leakage in plain common operation.
is it the local workstation set up ? in that case, could you expand on that set up and what problem you are experiencing ? the only thing i found in the referenced forum was that the test suite needed to be broken down into 2 execution series to keep memory consumption within the default level.
i'll give the ant based test a try on my machine and see what that gives...
> MailTests failure
> -----------------
>
> Key: JBPM-619
> URL: http://jira.jboss.com/jira/browse/JBPM-619
> Project: JBoss jBPM
> Issue Type: Bug
> Components: Core Engine
> Affects Versions: jBPM jPDL 3.2
> Reporter: Jim Rigsbee
> Assigned To: Tom Baeyens
> Fix For: jBPM jPDL 3.2
>
>
> MailTests will fail if your local workstation is not setup correctly. These tests are failing in the cruise control build as well.
--
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
19 years, 4 months
[JBoss JIRA] Closed: (JBPM-618) Memory leak in DbTests
by Tom Baeyens (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-618?page=all ]
Tom Baeyens closed JBPM-618.
----------------------------
Fix Version/s: (was: jBPM jPDL 3.2)
Resolution: Duplicate Issue
see JBPM-619
> Memory leak in DbTests
> ----------------------
>
> Key: JBPM-618
> URL: http://jira.jboss.com/jira/browse/JBPM-618
> Project: JBoss jBPM
> Issue Type: Bug
> Components: Core Engine
> Affects Versions: jBPM 3.1
> Environment: Eclipse and command line Ant
> Reporter: Jim Rigsbee
> Assigned To: Tom Baeyens
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> When all of the tests are run through ant test or running the tests in eclipse (AllTests), some of the tests near the end fail with an out of memory error. JProfiler shows that a steady of use of unreleased memory grows.
> We suspect that objects are not being released in the teardown() as they should since JUnit does not release any of test tests until the end of execution.
--
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
19 years, 4 months
[JBoss JIRA] Closed: (JBPM-554) New tasks created with "taskMgmtInst.createStartTaskInstance()" cannot be "end()-ed"
by Tom Baeyens (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-554?page=all ]
Tom Baeyens closed JBPM-554.
----------------------------
Fix Version/s: (was: jBPM jPDL 3.2)
Resolution: Cannot Reproduce Bug
this tests were added to the test suite for trying to reproduce this bug:
public void testStartTaskPresent() {
ProcessDefinition processDefinition = ProcessDefinition.parseXmlString(
"<process-definition>" +
" <start-state>" +
" <task name='lets get it started' />" +
" <transition to='going steady' />" +
" </start-state>" +
" <state name='going steady' />" +
"</process-definition>"
);
ProcessInstance processInstance = new ProcessInstance(processDefinition);
TaskInstance taskInstance = processInstance.getTaskMgmtInstance().createStartTaskInstance();
assertNotNull(taskInstance);
assertEquals("lets get it started", taskInstance.getName());
taskInstance.end();
assertEquals("going steady", processInstance.getRootToken().getNode().getName());
}
public void testStartTaskAbsent() {
ProcessDefinition processDefinition = ProcessDefinition.parseXmlString(
"<process-definition>" +
" <start-state>" +
" <transition to='going steady' />" +
" </start-state>" +
" <state name='going steady' />" +
"</process-definition>"
);
ProcessInstance processInstance = new ProcessInstance(processDefinition);
TaskInstance taskInstance = processInstance.getTaskMgmtInstance().createStartTaskInstance();
assertNull(taskInstance);
}
> New tasks created with "taskMgmtInst.createStartTaskInstance()" cannot be "end()-ed"
> ------------------------------------------------------------------------------------
>
> Key: JBPM-554
> URL: http://jira.jboss.com/jira/browse/JBPM-554
> Project: JBoss jBPM
> Issue Type: Bug
> Affects Versions: jBPM 3.1 beta 2
> Reporter: James Schopp
> Assigned To: Tom Baeyens
> Priority: Critical
>
> The following code will generate an NPE:
> TaskInstance taskInstance = taskMgmtInst.createStartTaskInstance();
> taskInstance.end();
> It appears that the "task" datamember of TaskInstance may be null. In end( ) (line 350 of TaskInstance.java), there is a debug statements which accesses task.getName(), when task is null.
--
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
19 years, 4 months
[JBoss JIRA] Updated: (JBAS-3206) Quartz resource adaptor integration
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3206?page=all ]
Dimitris Andreadis updated JBAS-3206:
-------------------------------------
Fix Version/s: (was: JBossAS-5.0.0.CR1)
Assignee: Carlo de Wolf (was: Weston Price)
Assign to Carlo to close after having the integration test in place (if not already there). I've enabled the quartz-ra.rar by default in the build, in the default/all configurations.
> Quartz resource adaptor integration
> -----------------------------------
>
> Key: JBAS-3206
> URL: http://jira.jboss.com/jira/browse/JBAS-3206
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JCA service, Build System
> Reporter: Scott M Stark
> Assigned To: Carlo de Wolf
> Fix For: JBossAS-4.2.0.CR1
>
>
> A quartz inflow resource adaptor showed up at the last minute in the 4.0.4.GA release process. It has been excluded from that release and needs discussion, testcases and docs for inclusion into 4.0.5.GA.
--
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
19 years, 4 months
[JBoss JIRA] Created: (JBESB-445) Custom Action:Scripting
by Burr Sutter (JIRA)
Custom Action:Scripting
-----------------------
Key: JBESB-445
URL: http://jira.jboss.com/jira/browse/JBESB-445
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.0 Maintenance Pack 1
Reporter: Burr Sutter
Assigned To: Mark Little
Priority: Optional
Fix For: 4.0 Maintenance Pack 1
Provide an out-of-the-box action that allows for the integration of scripting languages for as ESB actions. An example of a scripting language would be Groovy or Beanshell. A quickstart example should also be created to illustrate the capabilities.
Gregory Pierce provided a quickstart for Groovy.
--
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
19 years, 4 months