[JBoss JIRA] Created: (JBPM-1052) getAllTaskInstances(), getAllProcessInstances()
by s b (JIRA)
getAllTaskInstances(), getAllProcessInstances()
-----------------------------------------------
Key: JBPM-1052
URL: http://jira.jboss.com/jira/browse/JBPM-1052
Project: JBoss jBPM
Issue Type: Feature Request
Components: Core Engine
Affects Versions: jBPM jPDL 3.2
Reporter: s b
Assigned To: Tom Baeyens
Businesses often want a "super manager" to have the ability to see and work on the tasks of all users. With the current jBPM, it is very difficult to generate a list of all TaskInstances.
The feature requested is a method for listing all TaskInstances regardless of user. It appears to be a simple variation on the current methods which request TaskInstances by ActorId or an array of ActorIds.
One possibility might be to modify the query used by TaskManagementSession.findTaskInstances(String actorId) to use the SQL "LIKE" operator instead of "=" so that the % wildcard could be used to retrieve all TaskInstances. I don't know if that is portable to all databases; it works well for Oracle.
It has been suggested that this feature can be created as custom code, but custom code becomes very expensive to maintain and integrate with new releases of jBPM for small development companies like ours.
A similar feature to retrieve all ProcessInstances regardless of ProcessDefinition would also be highly useful for similar reasons.
A criticism is that the method would introduce scalability / performance problems. That is always an issue that is difficult to avoid completely depending on the application. For example, a business that has thousands of workers all performing the same workflow could generate a very large list using "GraphSession.findProcessInstances(long processDefinitionId)" which would be on the same order as a hypothetical "TaskManagementSession.getAllTaskInstances()" for that particular application.
--
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, 3 months
[JBoss JIRA] Created: (JBAS-4748) TransactionLocal.get() not sufficiently pluggable
by Jonathan Halliday (JIRA)
TransactionLocal.get() not sufficiently pluggable
-------------------------------------------------
Key: JBAS-4748
URL: http://jira.jboss.com/jira/browse/JBAS-4748
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Transaction Manager
Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
Reporter: Jonathan Halliday
Assigned To: Jonathan Halliday
Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
per discussion in forum thread ref below, the TransactionLocal.get() method calls storeValue in certain cases. Although the javadoc warns that the method may throw IllegalStateException, not all of the code in the app server that uses it can actually deal with that. With the old delegate implementation it did not need to. With changes to the way the TransactionLocalDelegate is implemented by JBossTS, this stared to cause problems. Per Adrian's suggestion this is resolved by masking the exception if it occurs.
--
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, 3 months
[JBoss JIRA] Created: (JBPM-848) Incorrect mail.smtp.host property + configurable mail from address
by Bruno Dumon (JIRA)
Incorrect mail.smtp.host property + configurable mail from address
------------------------------------------------------------------
Key: JBPM-848
URL: http://jira.jboss.com/jira/browse/JBPM-848
Project: JBoss jBPM
Issue Type: Patch
Components: Core Engine
Affects Versions: jBPM jPDL 3.2 beta 2
Reporter: Bruno Dumon
Assigned To: Tom Baeyens
jBPM incorrectly sets "jbpm.mail.smtp.host" instead of "mail.smtp.host" in the properties passed to JavaMail. As a consequence, JavaMail always tries to send to localhost. It seems this was introduced by accident here:
http://fisheye.jboss.com/browse/JBPM/jbpm.3/src/java.jbpm/org/jbpm/mail/M...
The attached patch fixes this.
Also, the from address for mails is currently hardcoded to "jbpm@noreply". Many SMTP servers don't allow an invalid origin domain name (as do many spam filters), this is the exception I get:
javax.mail.SendFailedException: Sending failed;
nested exception is:
class javax.mail.SendFailedException: Invalid Addresses;
nested exception is:
class javax.mail.SendFailedException: 450 <jbpm@noreply>: Sender address rejected: Domain not found
The attached patch also makes the from address configurable via jbpm.cfg.xml.
Patches are against current CVS and taken with the jbpm.3/jpdl directory as root.
Thanks for taking the time to look at this.
--
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, 3 months
[JBoss JIRA] Created: (JBAS-4675) TransactionLocal cannot be locked when transaction is marked rollback only
by Adrian Brock (JIRA)
TransactionLocal cannot be locked when transaction is marked rollback only
--------------------------------------------------------------------------
Key: JBAS-4675
URL: http://jira.jboss.com/jira/browse/JBAS-4675
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Transaction Manager
Affects Versions: JBossAS-4.2.1.GA
Reporter: Adrian Brock
Assigned To: Jonathan Halliday
Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Related to the parent issue, the proposed fix does not work in jboss-4.2.x because
the transaction local cannot be locked when the status is ABORT.
Here's the stacktrace of the error:
2007-09-05 17:50:44,899 DEBUG [org.jboss.resource.connectionmanager.CachedConnectionManager] Unable to synchronize with transaction
java.lang.IllegalStateException: Transaction not active
at com.arjuna.ats.jbossatx.TransactionLocalDelegateImpl.lock(TransactionLocalDelegateImpl.java:119)
at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.lock(BaseTransactionManagerDelegate.java:200)
at org.jboss.tm.TransactionLocal.lock(TransactionLocal.java:120)
at org.jboss.resource.connectionmanager.TransactionSynchronizer.lock(TransactionSynchronizer.java:223)
at org.jboss.resource.connectionmanager.CachedConnectionManager.getCloseConnectionSynchronization(CachedConnectionManager.java:550)
at org.jboss.resource.connectionmanager.CachedConnectionManager.unregisterConnection(CachedConnectionManager.java:315)
at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionClosed(TxConnectionManager.java:622)
at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.closeHandle(BaseWrapperManagedConnection.java:266)
at org.jboss.resource.adapter.jdbc.WrappedConnection.close(WrappedConnection.java:129)
You shouldn't be able to create a new delegate if the transaction is not active,
but you should be able to retrieve existing ones.
--
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, 3 months
[JBoss JIRA] Created: (JBAS-4768) TransactionLocal cannot be locked when transaction is marked rollback only
by Dimitris Andreadis (JIRA)
TransactionLocal cannot be locked when transaction is marked rollback only
--------------------------------------------------------------------------
Key: JBAS-4768
URL: http://jira.jboss.com/jira/browse/JBAS-4768
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Transaction Manager
Affects Versions: JBossAS-4.2.1.GA
Reporter: Adrian Brock
Assigned To: Jonathan Halliday
Priority: Critical
Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Related to the parent issue, the proposed fix does not work in jboss-4.2.x because
the transaction local cannot be locked when the status is ABORT.
Here's the stacktrace of the error:
2007-09-05 17:50:44,899 DEBUG [org.jboss.resource.connectionmanager.CachedConnectionManager] Unable to synchronize with transaction
java.lang.IllegalStateException: Transaction not active
at com.arjuna.ats.jbossatx.TransactionLocalDelegateImpl.lock(TransactionLocalDelegateImpl.java:119)
at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.lock(BaseTransactionManagerDelegate.java:200)
at org.jboss.tm.TransactionLocal.lock(TransactionLocal.java:120)
at org.jboss.resource.connectionmanager.TransactionSynchronizer.lock(TransactionSynchronizer.java:223)
at org.jboss.resource.connectionmanager.CachedConnectionManager.getCloseConnectionSynchronization(CachedConnectionManager.java:550)
at org.jboss.resource.connectionmanager.CachedConnectionManager.unregisterConnection(CachedConnectionManager.java:315)
at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionClosed(TxConnectionManager.java:622)
at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.closeHandle(BaseWrapperManagedConnection.java:266)
at org.jboss.resource.adapter.jdbc.WrappedConnection.close(WrappedConnection.java:129)
You shouldn't be able to create a new delegate if the transaction is not active,
but you should be able to retrieve existing ones.
--
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, 3 months
[JBoss JIRA] Closed: (JBMESSAGING-312) Refactor persistencemanager
by Tim Fox (JIRA)
[ http://jira.jboss.com/jira/browse/JBMESSAGING-312?page=all ]
Tim Fox closed JBMESSAGING-312.
-------------------------------
Resolution: Out of Date
> Refactor persistencemanager
> ---------------------------
>
> Key: JBMESSAGING-312
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-312
> Project: JBoss Messaging
> Issue Type: Task
> Reporter: Tim Fox
> Assigned To: Tim Fox
> Fix For: 2.0.0 Beta 1
>
> Original Estimate: 4 days
> Remaining Estimate: 4 days
>
> Refactor PersistenceManager to make less monolithic.
> The PersistenceManager should really only deal with simple persistence operations, e..g. addReference, removeReference, addMessage, removeMessage etc. This makes it easy to re-implement for another type of store.
> Currently the PM contains logic that belongs elsewhere e.g. in the ChannelState.
> The TransactionCallback should be removed to it's own java file.
> The locking operations should occur in the caller.
> There should be an abstraction PMTxContext which can be passed into PM operations to group them.
> This should dramatically clarify and simplify things
--
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, 3 months
