Hide Forgot
Description of problem: When I start any process which contains a human task to be stopped at some point, I'm not able to abort the process instance in Business central. It's still present there without any error. I'll attach the server log with SQLException escaped proxy: java.sql.SQLException: Connection is not associated with a managed connection.org.jboss.jca.adapters.jdbc.jdk6.WrappedConnectionJDK6@41693adb Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Start a process containing a human task 2. Abort the process instance in Business central 3. See the server log Actual results: Expected results: Additional info:
Created attachment 829096 [details] server log
After I changed the user, to not use admin, it's possible to abort it, so the problem is just for the admin.
Hi Ivo, Again, are you sure that you are not using the admin user for doing all of this? Also make sure that the task is not assigned to the admin user. Can you please confirm me that? Also please attach the process that you were using to test so I can try to reproduce the problem
Ok, so I'm marking this issue as modified based on Ivo's confirmation.
@Mauricio, this should not be set to modified unless it is fixed. If the issue only occurs when using the admin user, this makes it less severe but it is an issue nonetheless.
@Kris, completely agree, we should create a different issue then right? If not we will end up with tons of issues related with the use of the admin user, which will be solved all at once when we review the core cause of the issue.
Not really, if they happen to be caused by the same underlying issue, it will be possible to close several at the same time. But even then we would still have to verify each case. Feel free to link issues if you believe that would be useful.
This is already working in 6.0.x. Can you please try to verify that is already working with the latest build?
Couldn't reproduce this after several retries. Please confirm that this is already working.
@Mauricio, I am still able to reproduce the issue in BPMS 6.0.0.CR2. Did you use a user named "admin" with the role "admin"? This is the problem we talked about in this bug.
Hi Ivo, yes I've double checked with the admin user with the admin role in the 6.0.x branch with the latest source code and I couldn't reproduce it anymore. Are you testing with the latest build? From which day?
I test it with the product only (BPMS 6.0.0.CR2), not with any community release. It is possible it is currently working in 6.0.x branch. In the similar BZs (https://bugzilla.redhat.com/show_bug.cgi?id=1034242 and https://bugzilla.redhat.com/show_bug.cgi?id=1034258) you set them modified and changed the source code, so it probably fixed also this issue.
This no longer has a target release of 6.0.0.
Verified in BPMS 6.0.1.ER1
Test that a user is notified about using a username which is equal to a group (e.g. admin/admin).