June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-866) Allow the pattern binding variable to be used field constraints

by Mark Proctor (JIRA)

Allow the pattern binding variable to be used field constraints --------------------------------------------------------------- Key: JBRULES-866 URL: http://jira.jboss.com/jira/browse/JBRULES-866 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Proctor Assigned To: Edson Tirelli Fix For: 4.0.0.MR3 p : Person( p.name == "bob" ) Some users may write rules this way and it can help with code generation, so that you can use the same statements in the field constraints as you can in the eval (when using something like MVEL). -- 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 month

2
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-1096) UpgradeException should print IdentityLock instances

by Galder Zamarreno (JIRA)

UpgradeException should print IdentityLock instances ---------------------------------------------------- Key: JBCACHE-1096 URL: http://jira.jboss.com/jira/browse/JBCACHE-1096 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.4.1.SP3, 2.0.0.CR2 Reporter: Galder Zamarreno Assigned To: Manik Surtani Priority: Minor Fix For: 2.0.0.CR3, 1.4.1.SP4 When a TimeoutException is reported, the exception prints lock information (IdentityLock.toString(true)), ie. Read lock owners: [] Write lock owner: GlobalTransaction:<172.26.250.183:35277>:13350 , lock info: write owner=GlobalTransaction:<172.26.250.183:35277>:13350 (activeReaders=0, activeWriter=Thread[http-172.26.250.183-8180-10,5,jboss], waitingReaders=0, waitingWriters=0, waitingUpgrader=0) This is quite useful for debugging purpouses because it reports which thread is holding the lock as well as the transaction id. However, when an UpgradeException is reported, this information is not provided: Read lock owners: [GlobalTransaction:<adrxww03:32804>:1628] Write lock owner: null It'd be nice if UpgradeException could print IdentityLock information as it would help debugging which thread is holding the locks -- 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 month

2
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-1079) UML diagram in JBoss Cache User Guide is out of date

by Brian Stansberry (JIRA)

UML diagram in JBoss Cache User Guide is out of date ---------------------------------------------------- Key: JBCACHE-1079 URL: http://jira.jboss.com/jira/browse/JBCACHE-1079 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Eviction Affects Versions: 2.0.0.CR1 Reporter: Brian Stansberry Assigned To: Manik Surtani Priority: Minor Fix For: 2.0.0.GA Still uses the 1.x classes. -- 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 month

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-913) Download popups are not working in IE7

by Michael Neale (JIRA)

Download popups are not working in IE7 -------------------------------------- Key: JBRULES-913 URL: http://jira.jboss.com/jira/browse/JBRULES-913 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 4.0.0.MR2 Reporter: Michael Neale Assigned To: Michael Neale Priority: Critical Fix For: 4.0.0.MR3 -- 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 month

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-1097) XmlConfigurationParser to check system classloader as well as context classloader for cfg file

by Manik Surtani (JIRA)

XmlConfigurationParser to check system classloader as well as context classloader for cfg file ---------------------------------------------------------------------------------------------- Key: JBCACHE-1097 URL: http://jira.jboss.com/jira/browse/JBCACHE-1097 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR2 Reporter: Manik Surtani Assigned To: Manik Surtani Priority: Minor Fix For: 2.0.0.CR3 -- 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 month

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-505) UNICAST: sequence numbering after merge leads to messages never being delivered

by Vladimir Blagojevic (JIRA)

UNICAST: sequence numbering after merge leads to messages never being delivered ------------------------------------------------------------------------------- Key: JGRP-505 URL: http://jira.jboss.com/jira/browse/JGRP-505 Project: JGroups Issue Type: Bug Affects Versions: 2.4.1 Reporter: Vladimir Blagojevic Assigned To: Bela Ban Fix For: 2.5 During refactoring of TUNNEL to use TP I ran MultiplexerMergeTest very often. This test basically consists of two members A and B that are exchanging message through GossipRouter. When GossipRouter is killed members form their own subgroups that are subsequently merged once router starts again. I noticed that on very rare occasions (1 in 20 test runs) one of the members (say A) stops passing up unicast messages from B above UNICAST protocol. More detailed logging and inquiry at UNICAST revealed that upon merge A stops passing up messages from B and keeps adding messages from B seq>1 into B's window but does not pass up messages further since message seq B1 is missing. After further investigation I concluded that message B1 must have been delivered to A prior to MergeView. MergeView wiped clean all windows and added next sequence B2 to appropriate window. I am not sure if this is only applicable to Multiplexer setup. The issue is hard to reproduce. I will see if it is possible to make a unit test to reproduce it. -- 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 month

2
9
0 / 0

[JBoss JIRA] Created: (JGRP-523) Multicasts fail after a merge

by Bela Ban (JIRA)

Multicasts fail after a merge ----------------------------- Key: JGRP-523 URL: http://jira.jboss.com/jira/browse/JGRP-523 Project: JGroups Issue Type: Bug Affects Versions: 2.5 Reporter: Bela Ban Assigned To: Bela Ban Priority: Critical Fix For: 2.5 To reproduce: - Start GossipRouter - Start 2 Draws with tunnel.xml, connecting to the GR - Paint a bit in the 2 windows, to generate messages (and thus change the digests) - Kill GR - When both Draw instances become cluster singletons, start GR again ==> Observe that we get messages that indicate a requested retransmission couldn't be satisfied because the message was not found: 14:38:16,203 [WARN] [OOB Thread,demo,192.168.5.2:4397] NAKACK.handleMessage(): 192.168.5.2:4397] discarded message from non-member 192.168.5.2:4393, my view is [192.168.5.2:4397|2] [192.168.5.2:4397] 14:38:16,890 [WARN] [OOB Thread,demo,192.168.5.2:4393] NAKACK.handleMessage(): 192.168.5.2:4393] discarded message from non-member 192.168.5.2:4397, my view is [192.168.5.2:4393|2] [192.168.5.2:4393] -- 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 month

1
3
0 / 0

[JBoss JIRA] Closed: (JBREM-228) clustering

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-228?page=all ] Ron Sigal closed JBREM-228. --------------------------- Resolution: Done Assignee: (was: Tom Elrod) This issue has been replaced by http://jira.jboss.com/jira/browse/JBAS-4472. > clustering > ---------- > > Key: JBREM-228 > URL: http://jira.jboss.com/jira/browse/JBREM-228 > Project: JBoss Remoting > Issue Type: Task > Components: general > Affects Versions: 1.4.0 beta > Reporter: Tom Elrod > Priority: Critical > Fix For: 2.4.0.Beta1 (Pinto) > > > Need to seperate out clustering service so can run outside of JBossAS and then integrate with remoting so can use common clustering service with remoting (and other projects). -- 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 month

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-990) merge messageListenerInterface from annotation into descriptor annotation

by William DeCoste (JIRA)

merge messageListenerInterface from annotation into descriptor annotation ------------------------------------------------------------------------- Key: EJBTHREE-990 URL: http://jira.jboss.com/jira/browse/EJBTHREE-990 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.0 GA, EJB 3.0 RC9 - Patch 1 Reporter: William DeCoste Assigned To: William DeCoste -- 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 month

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1473) WSRP config GUI usability

by Prabhat Jha (JIRA)

WSRP config GUI usability ------------------------- Key: JBPORTAL-1473 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1473 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.6 Final Reporter: Prabhat Jha Assigned To: Chris Laprun Fix For: 2.6 Final Portal trunk code as of June 1, 2007. I am no usability expert but this is something needs to be fixed. Save, Refresh, Cancel button in WSRP Consumer configuration GUI is not alinged properly. Save button is slighly off balance. Please see the screen shot. -- 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 month

2
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 June 2007