March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAOP-287) Tighten integration with MC 2.0 once it is released

by Kabir Khan (JIRA)

Tighten integration with MC 2.0 once it is released --------------------------------------------------- Key: JBAOP-287 URL: http://jira.jboss.com/jira/browse/JBAOP-287 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.alpha2 -- 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

19 years

2
10
0 / 0

[JBoss JIRA] Created: (JBPM-783) isPropagated calculation for event is not correct

by Olga Ivanova (JIRA)

isPropagated calculation for event is not correct ------------------------------------------------- Key: JBPM-783 URL: http://jira.jboss.com/jira/browse/JBPM-783 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.2 alpha 1 Reporter: Olga Ivanova Assigned To: Tom Baeyens As it is stated in comment inside org.jbpm.graph.def.GraphElement.fireAndPropagateEvent method // calculate if the event was fired on this element or if it was a propagated event boolean isPropagated = (this.equals(executionContext.getEventSource())); I believe code does not correspond to the intent and should look following: boolean isPropagated = !(this.equals(executionContext.getEventSource())); i.e if event source is same element that this, event is not propagated, if they are different - event is propagated. -- 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

19 years

2
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-713) PojoCache when it has been detached remotely, accessing it again will throw PojoCacheAlreadyDetachedException

by Ben Wang (JIRA)

PojoCache when it has been detached remotely, accessing it again will throw PojoCacheAlreadyDetachedException ------------------------------------------------------------------------------------------------------------- Key: JBCACHE-713 URL: http://jira.jboss.com/jira/browse/JBCACHE-713 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Fix For: 2.0.0 This is the use case here: cacheA.attach(id, pojo); p = cacheB.find(id); cacheA.detach(id); p.getName(); // this will throw PojoCacheAlreadyDetachedException -- 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

19 years

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-3992) Race condition in JBossManagedConnectionFactory

by Derek Lewis (JIRA)

Race condition in JBossManagedConnectionFactory ----------------------------------------------- Key: JBAS-3992 URL: http://jira.jboss.com/jira/browse/JBAS-3992 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.0.4.GA Environment: I'm running JBoss 4.0.4.GA on jaba 1.5.0_07-b03. I haven't tried a newer JBoss, however the code I've determined is causing the problem looks the same on 5.0.0.Beta1. Reporter: Derek Lewis Assigned To: Weston Price The problem happens when calling flush() on JBossManagedConnectionPool via the jmx-console. If a call to getConnection() is made by the application at the same time, there is a potential for getConnection() to throw a ResourceException saying "The pool has been shutdown". Thread 1: calls flush() Thread 2: calls getConnection() In Thread 1, in JBossManagedConnectionPool.flush(), after the pools are iterated through and shut down (this is synchronized on subPools). Assume that a context switch happens here, and Thread 2 runs now, with Thread 1 paused, before calling subPools.clear(). When thread 2 gets to where it calls getSubPool(...), this is not synchronized, so subPools.get(key) returns a pool which is not null though it has been shutdown), and returns it. getConnection() is then called on this pool, causing the exception to be thrown. Thread 1 then proceeds to clear the pool, so that the shutdown subpools are not returned. (But it's too late for this one case) -- 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

19 years

4
4
0 / 0

[JBoss JIRA] Created: (JBBUILD-345) Mavenize JBoss Retro

by Paul Gier (JIRA)

Mavenize JBoss Retro -------------------- Key: JBBUILD-345 URL: http://jira.jboss.com/jira/browse/JBBUILD-345 Project: JBoss Build System Issue Type: Feature Request Affects Versions: MavenBuild 1.2 Reporter: Paul Gier The builds of JBoss Retro should be converted to maven. -- 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

19 years

1
4
0 / 0

[JBoss JIRA] Created: (JBBUILD-333) Implement translation of generic types

by Kabir Khan (JIRA)

Implement translation of generic types -------------------------------------- Key: JBBUILD-333 URL: http://jira.jboss.com/jira/browse/JBBUILD-333 Project: JBoss Build System Issue Type: Task Components: JBossRetro Affects Versions: JBossRetro-1.0.4.GA Reporter: Kabir Khan This causes jdk14 test failures in the retroed container project (and so in retroed aop which depends on container) Things like Class.getGenericInterfaces() Class.getGenericSuperClass() Field.getGenericType() Method/Constructor.getGenericExceptionTypes() Method/Constructor.getGenericParameterTypes() Method/Constructor.getTypeParameters() need to be moved into a GenericTypeRedirects or something. -- 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

19 years

4
5
0 / 0

[JBoss JIRA] Created: (GPD-64) When opening up processDefintion.xml created in 3.0.13 with the graphic designer all transtions are not showing up visually

by Bill Ted (JIRA)

When opening up processDefintion.xml created in 3.0.13 with the graphic designer all transtions are not showing up visually --------------------------------------------------------------------------------------------------------------------------- Key: GPD-64 URL: http://jira.jboss.com/jira/browse/GPD-64 Project: JBoss jBPM GPD Issue Type: Bug Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0.alpha3 Environment: Eclipse 3.2 Reporter: Bill Ted Assigned To: Koen Aers After creating process definitions with the eclipse plugin 3.0.13 and then installing the 3.1 alpha 3 version of the designer plugin you can open up the process definitions, but all the transitions are no longer visable. -- 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

19 years

2
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-624) Running on DB2

by Tomaz Cerar (JIRA)

Running on DB2 -------------- Key: JBMESSAGING-624 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-624 Project: JBoss Messaging Issue Type: Patch Components: Messaging Core Persistence Affects Versions: 1.0.1.GA Environment: jboss messaging 1.0.1GA, windows xp, DB2 8.2 iSeries Reporter: Tomaz Cerar Assigned To: Ovidiu Feodorov To make jboss messaging 1.0.1GA work with DB2 there must be attribute UsingBinaryStream in class JDBCPersistenceManager made configurable from service file. in JDBCPersistenceManager you add methods: /** * Managed attribute. */ public boolean isUsingBinaryStream()throws Exception { return usingBinaryStream; } /** * Managed attribute. */ public void setUsingBinaryStream(boolean usingBinaryStream)throws Exception { this.usingBinaryStream = usingBinaryStream; } and in JDBCPersistenceManager-xmbean.xml you have to add: <attribute access="read-write" getMethod="isUsingBinaryStream" setMethod="setUsingBinaryStream"> <description>Should JDBC read as binary stream be used?</description> <name>UsingBinaryStream</name> <type>boolean</type> </attribute> db2-persistence-service.xml -- 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

19 years

6
12
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-793) Modify testing framework to pick the file containing JGroups stack configurations based on the database tests are currently running in top of

by Ovidiu Feodorov (JIRA)

Modify testing framework to pick the file containing JGroups stack configurations based on the database tests are currently running in top of --------------------------------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-793 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-793 Project: JBoss Messaging Issue Type: Task Components: Tests and Performance Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.GA A place where this is currently hardcoded to use mysql is org.jboss.test.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOfficeTest.createClusteredPostOffice(). -- 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

19 years

4
8
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-919) Revive the performance framework

by Ovidiu Feodorov (JIRA)

Revive the performance framework -------------------------------- Key: JBMESSAGING-919 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-919 Project: JBoss Messaging Issue Type: Task Components: Tests and Performance Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Critical Fix For: 1.2.1.CR1 This is a container for all issues related to re-starting using the perfomance framework -- 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

19 years

3
5
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 March 2007