December 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-913) Nodes added via state transfer ignored by eviction policies

by Brian Stansberry (JIRA)

Nodes added via state transfer ignored by eviction policies ----------------------------------------------------------- Key: JBCACHE-913 URL: http://jira.jboss.com/jira/browse/JBCACHE-913 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.ALPHA1, 1.4.0.SP1, 1.4.0.GA Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 1.4.1.GA, 2.0.0.GA When state transfer creates new nodes and adds them to the tree, any eviction policy is unaware of the addition. As a result, those nodes are ignored for eviction unless they are accessed. This is a side effect of the addition of the EvictionInterceptor in 1.4.0. The state transfer code generates TreeCacheListener node addition events, but with the EvictionInterceptor, the eviction policies are no longer listening for the events. Probable solution is to modify notifyAllNodesCreated to have it find any eviction region for any nodes it has added. Then have it generate an EvictedEventNode and pass it to Region.putNodeEvent. -- 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 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-127) Secure ftp

by Mark Little (JIRA)

Secure ftp ---------- Key: JBESB-127 URL: http://jira.jboss.com/jira/browse/JBESB-127 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0 Beta 1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.0 -- 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, 7 months

3
10
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-655) Modify release-admin to allow for XARecovery-enabled and non-XARecovery-enabled configurations

by Ovidiu Feodorov (JIRA)

Modify release-admin to allow for XARecovery-enabled and non-XARecovery-enabled configurations ---------------------------------------------------------------------------------------------- Key: JBMESSAGING-655 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-655 Project: JBoss Messaging Issue Type: Sub-task Components: AS Integration Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.0.2.CR1 -- 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, 7 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-297) Need for an SQL gateway that does not require altering 'legacy' data in any way

by Esteban Schifman (JIRA)

Need for an SQL gateway that does not require altering 'legacy' data in any way ------------------------------------------------------------------------------- Key: JBESB-297 URL: http://jira.jboss.com/jira/browse/JBESB-297 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 5.0 Reporter: Esteban Schifman Assigned To: Esteban Schifman Priority: Minor Fix For: 4.0 Kurt has made a very valid point a couple of days ago regarding sql gateways. Current SQL gateway requires an 'ad hoc' column in the watched table as an access indicator to avoid concurrency problems and repeated processing of the same event Many legacy applications do not allow tampering with their data model, not even to have your own stored procedures in place, We should try and find a way to have a version of the SqlTableListener that can work without the need to alter in any way (updating, deleting, adding stored procedures, etc.) the legacy database This alternative would also allow to watch legacy 'views' (instead of simply db tables), thus broadening the scope of use of sql gateways. Configuration will be somewhat more complex than our current sql gateway, but I think it's really worthwhile. -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBTM-182) Missing synchronization?

by Mark Little (JIRA)

Missing synchronization? ------------------------ Key: JBTM-182 URL: http://jira.jboss.com/jira/browse/JBTM-182 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.3 Reporter: Mark Little Assigned To: Jonathan Halliday Fix For: 4.2.3 In addSynchronization for TwoPhaseCoordinator, the synchronization object is created if it isn't already set: if (_synchs == null) { // Synchronizations should be stored (or at least iterated) in their natural order _synchs = new TreeSet(); } if (_synchs.add(sr)) { result = AddOutcome.AR_ADDED; } However, because multiple threads could be calling the same transaction instance concurrently, shouldn't there be a synchronization around this block? It's possible that two threads could test and try to set the _synchs and because of interleaving one thread creates _synchs after the other thread already has and added it's resource (which would then become garbage). -- 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, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-813) GraphElement - hibernate - "this==runtimeAction.getGraphElement()"

by Rainer Alfoeldi (JIRA)

GraphElement - hibernate - "this==runtimeAction.getGraphElement()" ------------------------------------------------------------------ Key: JBPM-813 URL: http://jira.jboss.com/jira/browse/JBPM-813 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.1.2 Reporter: Rainer Alfoeldi Assigned To: Tom Baeyens See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96099 for the corresponding forums entry (the field below won't accept this link...) Is it possible that GraphElement .... List getRuntimeActionsForEvent(ExecutionContext executionContext, String eventType) { List runtimeActionsForEvent = null; List runtimeActions = executionContext.getProcessInstance().getRuntimeActions(); if (runtimeActions!=null) { Iterator iter = runtimeActions.iterator(); while (iter.hasNext()) { RuntimeAction runtimeAction = (RuntimeAction) iter.next(); // if the runtime-action action is registered on this element and this eventType if ( ( ===>>>>> this==runtimeAction.getGraphElement() <<<<===== ) && (eventType.equals(runtimeAction.getEventType())) ) { // ... add its action to the list of runtime actions if (runtimeActionsForEvent==null) runtimeActionsForEvent = new ArrayList(); runtimeActionsForEvent.add(runtimeAction.getAction()); } } } return runtimeActionsForEvent; } isn't really what you want? If you debug it you will (sometimes) have the situation that this is a straight forward Java Object and runtimeAction.getGraphElement() resolves to a Node$$EnhancerByCGLIB$$xxxxx. Both objects represent the same node (same id, the CGLIB even refs to the 'this' instance in its 'target' field.... but '==' obviously fails. -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-909) FileCacheLoader preload of a cached object containing a Map object bad behavior

by emailms box (JIRA)

FileCacheLoader preload of a cached object containing a Map object bad behavior -------------------------------------------------------------------------------- Key: JBCACHE-909 URL: http://jira.jboss.com/jira/browse/JBCACHE-909 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: PojoCache Affects Versions: 1.4.0.SP1, 1.4.0.GA Environment: Jboss 4.0.0 cache 1.4.1.BETA ,jboss-aop-1.5.2.GA Reporter: emailms box Assigned To: Ben Wang After Jboss restart a cached object containing a Map object bad behavior Map m m.size = 0 m.values is empty but m.getObject(key ) returns the value -- 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, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (BPEL-215) Add JBoss EULA

by Rajesh Rajasekaran (JIRA)

Add JBoss EULA -------------- Key: BPEL-215 URL: http://jira.jboss.com/jira/browse/BPEL-215 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Reporter: Rajesh Rajasekaran Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 Attachments: JBossORG-EULA.txt Attached is the JBossORG-EULA.txt 1. The eula should be checked into the project's source tree. 2. The project's build should include the EULA in project distributables, ie, whatever is the unit of publish: zip, tgz, etc. -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JGRP-391) Port from concurrent.jar to JDK 5's java.util.concurrent

by Bela Ban (JIRA)

Port from concurrent.jar to JDK 5's java.util.concurrent -------------------------------------------------------- Key: JGRP-391 URL: http://jira.jboss.com/jira/browse/JGRP-391 Project: JGroups Issue Type: Task Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-650) Correct MessageStore integration with kernel

by Juha Lindfors (JIRA)

Correct MessageStore integration with kernel -------------------------------------------- Key: JBMESSAGING-650 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-650 Project: JBoss Messaging Issue Type: Sub-task Components: Messaging Core Reporter: Juha Lindfors Assigned To: Juha Lindfors Fix For: 1.0.2.CR1 As per the comments added to the original patch, the access and integration between MessageStore and TransactionRepository must be corrected. This may involve an added MBean dependecy configuration that does not exist in previous versions (message store reference injected via JMX kernel). -- 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, 7 months

2
6
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 December 2006