I have tried to abort the task in different JBPM version. In Jbpm 5.2.0.Final version, aborted task status changed as 'Obsolete', but in Jbpm 5.4.0.Final version aborted task status changed as 'Exited'.
Could you please explain why this difference occurs also what is the difference between Obsolete & Exited status in jbpm.
Related to the latest offical documentation as well as the related Human-Task Standard
The task status Obsolete is set if the user skipping a task (possible if the task has been marked as skippable), in which case the task will not be executed. This gets handled as a 'positive outcome'.
The task status Exited is set if the parent application needs to end prematurely before the invoked human task has been completed. This is a 'negative outcome'.
Related
Sometimes, when one of our longer builds is running (around 2 hours), Jenkins will start displaying the "Jenkins is going to shutdown ..." message. And no, this has not been done by an admin (me).
When I last saw this, I checked the console output of the running job, and it was still churning through it's tests and was running normally. It was not hung.
Then later, I checked again, and the console had the "BUILD SUCCESSFUL" message, followed by "Pausing (Preparing for shutdown)" - and it just sat there.
So I clicked on the kill job button, and killed it. and got the "Aborted by ..." message.
Then 15 seconds later it displayed "Click here to forcibly terminate running steps". I did that. It then displayed "Terminating withAnt".
Then 15 seconds later, it displayed "Click here to forcibly kill entire build". Which I did - and Jenkins return to normal operation and cleared the "going to shutdown" message.
WHAT IS GOING ON!
One related note: Due to getting too much "state" bleedthrough on our JUNits, we recently added the forkmode="perTest" setting to the Ant JUnit task. This has resulted in random tests failing with a "vm exited unexpectedly" message. It happens randomly for different tests. (which is a PITA since we can no longer count on Test Failed status in jenkins meaning anything.) And no, I'm not sure if that has always happened when the Jenkins job has the termination problem.
Well, I think I figured this out.
The system was running low on disk space. So SOME jobs that used more were triggering this problem - and others would run without a problem.
When I finally received a low-disk space error in one of the logs, I did some cleaning (found a bunch of files that were supposed to have been deleted.). Since then, this error has stopped occuring.
NOPE! Still happening
Error Description:
The BAR File contains .msgflow files and this broker does not support them. To deploy this BAR file to the target broker save the BAR file selecting the 'Compile and in-line resources option'.
Check that,
1. The broker is running.
2. The TCP/IP port of the queue manager is active if it is remote.
Details Error Description:
Begin running task [Deploying [RecordAndReplyExample] to execution group [default]]
The deployment was unsuccessful due to unknown reason.
The task was unsuccessful: The deployment was unsuccessful due to unknown reason.
Did anyone know how to solve this?
It would appear that you are trying to use features in the message flow that are not supported by the broker you are attempting to deploy it to.
From that error message, and with no version info provided by the OP, I would guess that you are trying to use a BAR file that contains .msgflow files on a broker that only supports compiled flows in .cmf files. If this is the case then you will need to either use a later version of MB/IIB that supports this feature, 8 FP1 or later, or recreate your BAR file with the 'Compile and in-line resources option' option set in the toolkit on the save BAR file screen.
In SSIS, I am running a stored procedure in an ExecuteSQL Task. It is erroring out with:
Executing the query "EXEC [dbo].[mySP]" failed with the following error: "The Microsoft Distributed Transaction Coordinator (MS DTC) has cancelled the distributed transaction.Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
I don't have any parameters or resultset.
I was getting this same error. I had a Master Package that was executing multiple individual packages. I thought it was a permissions issue of some sort at first because those 2 packages were the only ones touching a different schema. Wrong. Turns out those 2 packages were the only ones in the entire Master Package that weren't serial in nature (were running concurrently). After I made one package run and complete before the other everything started working.
I get this error during ui automation and am unable to resolve it.
This stops my automation flow ...
instruments[34247:1345307] Attempting to set event horizon when core
is not engaged, request ignored
In my experience, this message is related to the startup or shutdown of the individual processes that enable UIAutomation; nothing in your javascript code or environment really has an effect on it. It's just a sporadic error that comes from somewhere in Apple's software.
Sometimes it happens at the beginning of the run (in which case your javascript code will never be executed), or at the end of the run (in which case your code has already run). If you are seeing this error at the end of a test run and your code did not fully execute, then the real error is probably happening sometime before this -- you are just seeing Apple's error as well on the test shutdown.
I am trying to figure out how to spawn a process / start an EXE from Rhozet Carbon Coder.
The manual mentions a task that sounds promising, "ExternalProcess", in section 5.8.2 but does not document this task.
Has anybody had success doing this, or knows where the ExternalProcess task is documented?
I have heard back from Rhozet that the ExternalProcess command mentioned tangentially in the manual is a typo, there isn't any task by that name.
Currently the only way to launch a process is to use the Notify task.
For example the folowing xml put in the Sources section of a configuration file launches notepad before running the job.
<Notify>
<PreTaskNotify>
<ProcessNotify_0 NotifyCommand="notepad.exe" />
</PostTaskNotify>
</Notify>