May 2007 - jboss-jira - Jboss List Archives

[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, 10 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, 10 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, 10 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, 10 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, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-965) configuring DbPersistenceServiceFactory is not working

by Bernd Ruecker (JIRA)

configuring DbPersistenceServiceFactory is not working ------------------------------------------------------ Key: JBPM-965 URL: http://jira.jboss.com/jira/browse/JBPM-965 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Reporter: Bernd Ruecker Assigned To: Tom Baeyens Priority: Minor Configuring the DbPersistenceServiceFactory is not working like it is described in the documentation, see Forum reference for more details. -- 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, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPM-910) XML schema urn:jbpm.org:jpdl-3.2 incomplete (atrtibute missing in sub-process; documentation referring to old version)

by Arjan van Bentem (JIRA)

XML schema urn:jbpm.org:jpdl-3.2 incomplete (atrtibute missing in sub-process; documentation referring to old version) ---------------------------------------------------------------------------------------------------------------------- Key: JBPM-910 URL: http://jira.jboss.com/jira/browse/JBPM-910 Project: JBoss jBPM Issue Type: Bug Components: Core Engine, Documentation Affects Versions: jBPM jPDL 3.2 Environment: All Reporter: Arjan van Bentem Assigned To: Tom Baeyens Priority: Minor The XML schema at http://fisheye.labs.jboss.com/browse/JBPM/jbpm.3/jpdl/jar/src/main/java/o... is missing the attribute "binding" in element "sub-process" . And the documentation at http://fisheye.labs.jboss.com/browse/JBPM/jbpm.3/jpdl/userguide/en/module... still refers to version 3.1 instead of 3.2. However, when changing http://jbpm.org/jpdl-3.1.xsd (which redirects to http://docs.jboss.org/jbpm/xsd/jpdl-3.1.xsd) to http://jbpm.org/jpdl-3.2.xsd, then the jbpm.org web server must be configured to redirect to http://docs.jboss.org/jbpm/xsd/jpdl-3.2.xsd Or maybe the documentation should simply refer to the jboss.org server right away. And just for the archives: the binding attribute was added for http://jira.jboss.org/jira/browse/JBPM-733 and implemented in http://fisheye.labs.jboss.com/browse/JBPM/jbpm.3/jpdl/jar/src/main/java/o... -- 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, 10 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, 10 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, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (JBPM-972) org.jbpm.graph.action.Script does not provide specific (correct) handling for bsh.TargetError

by Olga Ivanova (JIRA)

org.jbpm.graph.action.Script does not provide specific (correct) handling for bsh.TargetError --------------------------------------------------------------------------------------------- Key: JBPM-972 URL: http://jira.jboss.com/jira/browse/JBPM-972 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2 Reporter: Olga Ivanova Assigned To: Tom Baeyens The recommended way of handling beanshel script TargerError is to use target exception (rethrow or printout), instead of using TargerError itself. see (http://www.beanshell.org/manual/bshmanual.html). The reason why this problem is reported is that when TargetError is not handled in a way it is proposed, stack trace where such error exists became inaccurate. This happends if TargetError is a cause for some other error on which printStackTrace is called, and TargetError itself contains targer exception with it's own causes. In this case, only target exception itself is printed out, all it's cause exceptions are not printed. Unit Test is attached. In JBPM org.jbpm.graph.action.Script , following code handles beanshell script exceptions (line 137): } catch (EvalError e) { log.warn("exception during evaluation of script expression", e); // try to throw the cause of the EvalError if (e.getCause() instanceof Exception) { throw (Exception) e.getCause(); } else if (e.getCause() instanceof Error) { throw (Error) e.getCause(); } else { throw e; } } Which does not work as expected, as TargerError which extends EvalError always returns null from getCause method. Another thing is that there are two child classes of EvalError - TargetError, which should be handled specially and ParseException, where no special handling is required. The correct way of handling these exceptions could be following: } catch (EvalError e) { log.warn("exception during evaluation of script expression", e); if (e instanceof TargetError) { TargetError te = (TargetError)e; // try to throw the cause of the TargetError if (te.getTarget() instanceof Exception) { throw (Exception) te.getTarget(); } else if (te.getTarget() instanceof Error) { throw (Error) te.getTarget(); } } throw e; -- 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, 10 months

2
3
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 May 2007