[JBoss JIRA] Created: (JBPM-1072) Concurrent JobExecutors can process the same job in parallel
by Jiri Pechanec (JIRA)
Concurrent JobExecutors can process the same job in parallel
------------------------------------------------------------
Key: JBPM-1072
URL: http://jira.jboss.com/jira/browse/JBPM-1072
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
MySQL 5.0.22
Reporter: Jiri Pechanec
Assigned To: Tom Baeyens
Attachments: expl.tar.gz
Attached is a simple test case that
1) Deploys process definition with two nodes
2) Starts 20 executor threads
2) Starts the process instance that will asynchronously execute action on the second node
4) The second node writes a record to the database
The test case needs to be executed multiple times to see the incorrect behaviour.
This is an example of run output
Isol 8
Action 1
Success 0
Failure 0
Action 2
Action 2 1
Action 2
Action 2 1
Action 2
Action 2 1
Action 2
Action 2 1
Action 2
Action 2 1
Action 2
Action 2 1
Action 2
Action 2
Action 2 1
Action 2 1
Action 2
Action 2 1
Explanation of the outcome
9 job executors successfully executed the node action (same job) including database operation. All database operations were comitted (9 new records were created)
--
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
17 years, 1 month
[JBoss JIRA] Updated: (GPD-179) pages.xml doesn't work with pageflow editor
by Koen Aers (JIRA)
[ http://jira.jboss.com/jira/browse/GPD-179?page=all ]
Koen Aers updated GPD-179:
--------------------------
Fix Version/s: jBPM jPDL Designer 3.1.2
(was: jBPM jPDL Designer 3.1.1)
> pages.xml doesn't work with pageflow editor
> -------------------------------------------
>
> Key: GPD-179
> URL: http://jira.jboss.com/jira/browse/GPD-179
> Project: JBoss jBPM GPD
> Issue Type: Bug
> Components: jpdl
> Reporter: Max Andersen
> Assigned To: Koen Aers
> Fix For: jBPM jPDL Designer 3.1.2
>
>
> a pages.xml with a proper page flow syntax does not have the pageflow editor in the right click menu.
> and when using Open with... and choosing jBpm pageflow designer (not the correct name is it ?) I get
> java.lang.NullPointerException
> at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addProcessDiagramDimension(Unknown Source)
> at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addGraphicalInfo(Unknown Source)
> at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addGraphicalInfo(Unknown Source)
> at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addGraphicalInfo(Unknown Source)
> at org.jbpm.ui.pageflow.editor.PageFlowGraphicalEditorPage.initInput(Unknown Source)
> at org.jbpm.ui.pageflow.editor.PageFlowGraphicalEditorPage.init(Unknown Source)
> at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:186)
> at org.jbpm.ui.pageflow.editor.PageFlowEditor.addGraphPage(Unknown Source)
> at org.jbpm.ui.pageflow.editor.PageFlowEditor.createPages(Unknown Source)
> at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:283)
> at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661)
> at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:426)
> at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:592)
> at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:263)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2721)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2633)
--
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
17 years, 1 month
[JBoss JIRA] Created: (GPD-189) Changing the node name does not update arriving edges
by Matthias Hanisch (JIRA)
Changing the node name does not update arriving edges
-----------------------------------------------------
Key: GPD-189
URL: http://jira.jboss.com/jira/browse/GPD-189
Project: JBoss jBPM GPD
Issue Type: Bug
Components: jpdl
Environment: Windows 2000, Eclipse 3.3.1.1, GEF 3.3.1
Latest designer sources from CVS.
Reporter: Matthias Hanisch
Assigned To: Koen Aers
Following steps to reproduce:
- Create new process definition
- Add a start and an end node
- Create a transition between start and end
- Rename the end node
Problem: Transition "to" attribute is not updated to the new name of the end node.
Happens with the latest CVS tree. Problem seems to be around the recent changes of JpdlNode. The added condition
if (evt.getSource() != getSemanticElement()) {
updateArrivingEdges((String)evt.getNewValue());
}
prevents, that the arriving transition is updated in the example above (evt.getSource is identical to getSemanticElement()).
Hope this description helps a little bit to localize this bug. As a workaround, I will call updateArrivingEdges() unconditionally, as it was in previous versions.
--
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
17 years, 1 month
[JBoss JIRA] Created: (JBPORTAL-1778) SynchronizingLoginModule synchronizeRoles still syncs existing roles when set to false
by Guy M. Spillman, Jr. (JIRA)
SynchronizingLoginModule synchronizeRoles still syncs existing roles when set to false
--------------------------------------------------------------------------------------
Key: JBPORTAL-1778
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1778
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal Security
Affects Versions: 2.6.2 Final
Environment: Pentium 3 - 2GB memroy - 20 GB of Free Space
Windows XP Professional Service Pack 2
JBoss Portal 2.6.2 + JBoss AS 4.2.1 Bundle
Reporter: Guy M. Spillman, Jr.
Assigned To: Julien Viet
Problem was discovered using JaasLounge(http://jaaslounge.sourceforge.net/ ) NTLMLoginModule, but can be duplicated using JBoss' UsersRolesLoginModule.
Configuration:
${jboss.server.home.dir}\deploy\jboss-portal.sar\conf\login-config.xml:
Code:
<login-module code="org.jboss.portal.identity.auth.IdentityLoginModule" flag="sufficient">
<module-option name="unauthenticatedIdentity">guest</module-option>
<module-option name="userModuleJNDIName">java:/portal/UserModule</module-option>
<module-option name="roleModuleJNDIName">java:/portal/RoleModule</module-option>
<module-option name="userProfileModuleJNDIName">java:/portal/UserProfileModule</module-option>
<module-option name="membershipModuleJNDIName">java:/portal/MembershipModule</module-option>
<module-option name="additionalRole">Authenticated</module-option>
<module-option name="password-stacking">useFirstPass</module-option>
</login-module>
<login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule" flag="required" />
<login-module code="org.jboss.portal.identity.auth.SynchronizingLoginModule" flag="optional">
<module-option name="synchronizeIdentity">true</module-option>
<module-option name="synchronizeRoles">false</module-option>
<module-option name="additionalRole">Authenticated</module-option>
<module-option name="defaultAssignedRole">User</module-option>
<module-option name="userModuleJNDIName">java:/portal/UserModule</module-option>
<module-option name="roleModuleJNDIName">java:/portal/RoleModule</module-option>
<module-option name="membershipModuleJNDIName">java:/portal/MembershipModule</module-option>
<module-option name="userProfileModuleJNDIName">java:/portal/UserProfileModule</module-option>
</login-module>
${jboss.server.home.dir}\conf\defaultRoles.properties:
Code:
testuser=test
testuser2=test2
${jboss.server.home.dir}\conf\defaultUsers.properties:
Code:
testuser=testrole1,testrole2
testuser2=testrole3,testrole4
Procedure:
1. Apply above configuration, run JBoss, and navigate to portal using browser.
2. Login using testuser/test.
3. Logout
4. Login using admin/admin
5. Click on the "Admin" link
6. Click on the "Members" tab
7. Click on "User Management" sub tab
8. Click on "Search Users" link
9. Find the "testuser" that should have been auto created in step #2
10. Click on "Role Management" sub tab
11. Click on "Create New Role" link
12. Enter "portalrole" for both "Role" and "Display Name" edit boxes (Role must not exist in defaultRoles.properties)
13. Click "Submit" button
14. Click on "User Management" sub tab
15. Click on "Search Users" link
16. Click on the "Roles" link to the right of "testuser"
17. Click the "portalrole" checkbox.
18. Click the "Submit" button.
19. Logout
20. Login using testuser/test
21. Navigate around the portal at your leisure (Sometimes this step can be skipped)
22. Logout
23. Login using admin/admin
24. Click on the "Admin" link
25. Click on the "Members" tab
26. Click on "User Management" sub tab
27. Click on "Search Users" link
28. Click on the "Roles" link to the right of "testuser"
The "portalrole" is no longer checked. Expected it to remain checked.
--
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
17 years, 1 month
[JBoss JIRA] Created: (JBREM-853) HTTP server invokers should not put null URL path in metadata map
by Ron Sigal (JIRA)
HTTP server invokers should not put null URL path in metadata map
-----------------------------------------------------------------
Key: JBREM-853
URL: http://jira.jboss.com/jira/browse/JBREM-853
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Priority: Minor
Fix For: 2.4.0.Beta1 (Pinto)
org.jboss.remoting.transport.servlet.ServletServerInvoker calls javax.servlet.http.HttpServletRequest.getPathTranslated() and puts the result in the invocation's requestPayload with key "Path". If the path of the URL is null, then a null value goes in the map, and using Map.putAll() can result in a NullPointerException. This phenomenon was observed in the execution of org.jboss.test.remoting.transport.servlet.ssl.SSLServletClientAddressTestClient when the contents of the requestPayload map are added to the callback Client configuration map. The callback transport is "socket", and a call to Map.putAll() occurs in org.jboss.remoting.transport.socket.MicroSocketClientInvoker.
--
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
17 years, 1 month