[JBoss JIRA] Created: (JBESB-2122) Investigate the jBPM security
by Kevin Conner (JIRA)
Investigate the jBPM security
-----------------------------
Key: JBESB-2122
URL: https://jira.jboss.org/jira/browse/JBESB-2122
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Security
Affects Versions: 4.4 CP1
Reporter: Kevin Conner
Fix For: 4.4 CP1
jBPM does not appear to support the JAAS context as a security measure, as a consequence the security information is currently being lost when communicating through jBPM.
We need to investigate the jBPM mechanisms and provide some way to propagate the context.
It may well be that the simplest solution, for now, will be for the context to be stored during the process creation and then have that reused for all communications.
The ideal solution would be to link in with the jBPM mechanism so that changed in 'actors' could be tracked and acted on accordingly.
--
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
17 years, 4 months
[JBoss JIRA] Created: (JBESB-1438) JMS Courrier does not support transacted mode
by Jiri Pechanec (JIRA)
JMS Courrier does not support transacted mode
---------------------------------------------
Key: JBESB-1438
URL: http://jira.jboss.com/jira/browse/JBESB-1438
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Process flow, Rosetta
Affects Versions: 4.2.1
Reporter: Jiri Pechanec
Assigned To: Mark Little
Priority: Blocker
Fix For: 4.2.1 CP1
JMS Courrier (deliver side) operates only with non-transacted queue sessions. This prevents jBPM integration to work correctly. The problem can be sketched this way
1) The message is received via JMS/JCA listener, transaction is started
2) jBPM process is invoked
3) jBPM process sends message (calls service) in non-transacted mode
Three situations can happen
1) Exception is thrown later, it means that global transaction is rolled back but another service was already invoked - BUG
2) jBPM process goes to the wait state and waits for response from ESB, global transaction is committed, called service sends back signal to continue process - OK
3) jBPM process goes to the wait state and waits for response from ESB, called service sends back signal to continue process - but the global transaction was not committed yet - BUG
This is key feature to have ESB/jBPM integration working safely.
--
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, 4 months
[JBoss JIRA] Created: (JBESB-1164) Crash creates multiple EPRs for same service in JUDDI
by Tom Cunningham (JIRA)
Crash creates multiple EPRs for same service in JUDDI
-----------------------------------------------------
Key: JBESB-1164
URL: http://jira.jboss.com/jira/browse/JBESB-1164
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Registry and Repository
Affects Versions: 4.2.1 IR1
Reporter: Tom Cunningham
Assigned To: Mark Little
If the AS or ESB server crashes or does not cleanly shut down, JUDDI will duplicate EPR records in its database table. For the monitoring/management console, this is a real problem because it depends on the fact that there will be only one EPR for its services per ESB server.
Post-crash, every time the console tries to collect data, it is getting back results from multiple EPRs on the same machine, which is causing ConstraintViolations when we try to store results. This is causing JBESB-1139.
JUDDI should probably clean up EPR records post-crash.
--
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, 5 months
[JBoss JIRA] Created: (JBESB-1590) Review File lifecycle management in the FileGateway
by Tom Fennelly (JIRA)
Review File lifecycle management in the FileGateway
---------------------------------------------------
Key: JBESB-1590
URL: http://jira.jboss.com/jira/browse/JBESB-1590
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Transports
Affects Versions: 4.2.1 CP1
Reporter: Tom Fennelly
Fix For: 4.2.1 CP2
Task JBESB-1568 identified an issue thrown up by the scheduler code, but in doing so also highlighted a secondary issue in the way that the gateway itself manages the lifecycles of the files it is processing. Specifically... when a file "disappears" while that instance of the gateway is processing it (or about to process it).
This could happen through a single FileGateway config before JBESB-1568 was fixed, but can still happen when multiple gateways are configured to process the same fileset in the same directory.
The gateway should handle such contention issue more cleanly.
Should it support multiple gateway instances processing a single fileset in a single directory? This could be a head wrecker to get right *and prove right* on all platforms! We could just document this as something that's not supported. It should def be able to handle different filesets in the same dir using multiple gateway instances!
--
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, 5 months
[JBoss JIRA] Created: (JBESB-866) jUDDI retains invalid EPRs
by Jiri Pechanec (JIRA)
jUDDI retains invalid EPRs
--------------------------
Key: JBESB-866
URL: http://jira.jboss.com/jira/browse/JBESB-866
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Registry and Repository
Affects Versions: 4.2 Milestone Release 3
Reporter: Jiri Pechanec
Assigned To: Mark Little
If the ESB is terminated (crashes) it will retain EPRs in the database. Unfortunately when the EPR is changed e.g. by renaming of underlaying queue, both old and new EPRs are stored in jUDDI registry on the next start. Then under heavier load both EPRs are selected with the result of lot error messages related to unavailable EPR.
--
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, 5 months