February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3499) Use JBoss Cache for DistributedReplicantManager instead of HAPartition

by Brian Stansberry (JIRA)

Use JBoss Cache for DistributedReplicantManager instead of HAPartition ---------------------------------------------------------------------- Key: JBAS-3499 URL: http://jira.jboss.com/jira/browse/JBAS-3499 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Jerry Gauthier Fix For: JBossAS-5.0.0.Beta DRM remains as a service available via HAPartition, but it uses JBC for cluster-wide state management. This requires that the HAPartition and the JBC instance use the same underlying multiplexed JChannel. -- 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

18 years, 8 months

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-3735) Integrate JGroups 2.4 in JBossAS 5

by Brian Stansberry (JIRA)

Integrate JGroups 2.4 in JBossAS 5 ---------------------------------- Key: JBAS-3735 URL: http://jira.jboss.com/jira/browse/JBAS-3735 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta When 2.4 is released, need to integrate it into AS HEAD. I've been integrating various beta, snapshot and CR releases of 2.4 into AS HEAD for quite a while now, so most of the work for this task is done. -- 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

18 years, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-3896) Expose JChannel and protocol mbeans via JMX

by Brian Stansberry (JIRA)

Expose JChannel and protocol mbeans via JMX ------------------------------------------- Key: JBAS-3896 URL: http://jira.jboss.com/jira/browse/JBAS-3896 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.CR1 Reporter: Brian Stansberry Assigned To: Brian Stansberry JChannel and the protocols expose mbeans; when we create a channel we need to register those beans in JMX. API is via JmxConfigurator.reisterChannel(). Need to check how this works with a multiplexed channel. -- 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

18 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBFORUMS-128) Need to remove the phpBB graphics with our own

by Sohil Shah (JIRA)

Need to remove the phpBB graphics with our own ---------------------------------------------- Key: JBFORUMS-128 URL: http://jira.jboss.com/jira/browse/JBFORUMS-128 Project: JBoss Forums Issue Type: Sub-task Affects Versions: 1.0.0 Alpha Reporter: Sohil Shah Assigned To: James Cobb Fix For: 1.1.0 Alpha -- 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

18 years, 8 months

3
7
0 / 0

[JBoss JIRA] Created: (JBAS-3599) Implement MessageListener.block() in HAPartitionImpl

by Brian Stansberry (JIRA)

Implement MessageListener.block() in HAPartitionImpl ---------------------------------------------------- Key: JBAS-3599 URL: http://jira.jboss.com/jira/browse/JBAS-3599 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta Needed for proper use of JGroups FLUSH. -- 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

18 years, 8 months

4
3
0 / 0

[JBoss JIRA] Created: (JBAS-3720) Change structure of ClusteredSSO data in tree cache to avoid lock issues

by Brian Stansberry (JIRA)

Change structure of ClusteredSSO data in tree cache to avoid lock issues ------------------------------------------------------------------------ Key: JBAS-3720 URL: http://jira.jboss.com/jira/browse/JBAS-3720 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 For each SSO entry, their should be child node per server where the SSO has been used. This is different from the current where all the session data for an SSO is in one node. The data map in each child node would hold the session ids of the sessions active on that server. This kind of structure avoids most lock contention between different servers. Can't do this in 4.0.x as it prevents interoperation with earlier releases. -- 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

18 years, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-691) Decision class does not allow setting of Decision Delegation

by Chris OBrien (JIRA)

Decision class does not allow setting of Decision Delegation ------------------------------------------------------------ Key: JBPM-691 URL: http://jira.jboss.com/jira/browse/JBPM-691 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Affects Versions: jBPM 3.1.1 Environment: Windows XP MySQL WSAD 5.1.2 Reporter: Chris OBrien Assigned To: Tom Baeyens In programmatically creating/manipulating a process definition, one cannot specify a Decision Delegation on a Decision node. The Decision class just needs a method like: public void setDecisionDelegation( Delegation del ) { this.decisionDelegation = del; } I have added this to my install, and it allows me to programmatically change the process definition to define the handler. -- 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

18 years, 8 months

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-4093) Example XA datasource configuration for Sybase

by Darran Lofthouse (JIRA)

Example XA datasource configuration for Sybase ---------------------------------------------- Key: JBAS-4093 URL: http://jira.jboss.com/jira/browse/JBAS-4093 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JCA service Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: JBossAS-4.2.0.CR1 Create an example XA datasource configuration for Sybase. -- 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

18 years, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (JBPM-743) Optionally allow swimlanes to perform assignment for each evaluation

by Brian Greene (JIRA)

Optionally allow swimlanes to perform assignment for each evaluation -------------------------------------------------------------------- Key: JBPM-743 URL: http://jira.jboss.com/jira/browse/JBPM-743 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Environment: All Reporter: Brian Greene Assigned To: Tom Baeyens Swimlanes are a very effective way to perform assignment, and we have implemented several that are nicely reusable. A swimlane though, isn't always (to my mind) the same actor or actors throughout the life of a process instance. In our case (and we've several use cases where this is applicable) a swimlane may represent an actor(s) that are related to a particular object or object in the process. The problem arises when the user(s) that are related to said object change in a long-running process. For example, a long running requisition process. The manager of the user who made the requisition may wish to have notifications as the process goes along (we have integrated email functionality in a custom extension). The most intuitive way to handle this as a process author is to use a swimlane that defines the relationship. The current jBPM TaskMgtInstance will only perform the assignment once per swimlane though, assuming that the SAME actor(s) will be used for the life of the process. Depending on what you're orchestrating, this may not be tenable. I think at the least there ought to be a way to allow a swimlane to configure a swimlane to perform its work every time it is referenced rather than using the previously determined actor(s). I've made a modification to jBPM to force swimlane instances to ALWAYS perform assignment, and while this fixes the issue in the short term, eventually I plan to modify either the global config for swimlanes, and better, add an attribute to the swimlane declaration that allows configurable behavior on a swimlane that will override the global default. In this way you could have the current behavior or configure the global setting to behave as I've discussed and provide an override to the current behavior on a case by case basis. You can get this behavior using nested assignment delegations, but there are reusability issues as well as the general cleanliness of the jPDL language to consider. We think swimlanes are in many cases more intuitive, and make the process definition much more readable. As we've discussed in internally, this seems reasonable, and seems to be required in a flexible environment supporting long running processes. -- 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

18 years, 8 months

6
7
0 / 0

[JBoss JIRA] Created: (JBAS-4096) Cleanup the JBoss JTS implementation

by Dimitris Andreadis (JIRA)

Cleanup the JBoss JTS implementation ------------------------------------ Key: JBAS-4096 URL: http://jira.jboss.com/jira/browse/JBAS-4096 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: IIOP service Reporter: Dimitris Andreadis Assigned To: Francisco Reverbel Fix For: JBossAS-4.2.1.CR1 Under the J2EE spec, JTS support is optional. It is preferable not to support it by default, rather than maintaining a JTS implementation inside the app server code base in addition to JBossTS JTS as we go forward. App server users requiring transactions over RMI/IIOP will need to download and drop in the JBoss JTS. Some cleanup of the app server code will be beneficial to ensure elegant failure rather than the current exceptions. We may be able to achieve this though the jboss iiop-service.xml settings? See also JBAS-4024 -- 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

18 years, 8 months

1
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2007