November 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-1085) NakreceiverWindow: possibly replace ReadWriteLock

by Bela Ban (JIRA)

NakreceiverWindow: possibly replace ReadWriteLock ------------------------------------------------- Key: JGRP-1085 URL: https://jira.jboss.org/jira/browse/JGRP-1085 Project: JGroups Issue Type: Task Reporter: Bela Ban Priority: Minor Fix For: 2.9 Take a look at performance of RW locks, [1] suggests it is bad and writer threads get starved by many reader threads. [1] http://www.javaspecialists.eu/archive/Issue165.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
8
0 / 0

[JBoss JIRA] Created: (JGRP-1081) NAKACK: use NakReceiverWindow.removeMany() instead of remove()

by Bela Ban (JIRA)

NAKACK: use NakReceiverWindow.removeMany() instead of remove() -------------------------------------------------------------- Key: JGRP-1081 URL: https://jira.jboss.org/jira/browse/JGRP-1081 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 2.9 This is a performance optimization, similar to what's already done in UNICAST -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-7423) Make missing notifications.xml result in a clear error message/exception

by Andrew Lee Rubinger (JIRA)

Make missing notifications.xml result in a clear error message/exception ------------------------------------------------------------------------ Key: JBAS-7423 URL: https://jira.jboss.org/jira/browse/JBAS-7423 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Andrew Lee Rubinger Currently the exception is null input to JBossXB: org.jboss.xb.binding.JBossXBException: Failed to parse source: null at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:183) at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:190) at org.jboss.jmx.adaptor.snmp.agent.TrapFactorySupport.start(TrapFactorySupport.java:154) at org.jboss.jmx.adaptor.snmp.agent.TrapEmitter.start(TrapEmitter.java:120) Make a clearer error message for the user -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-211) JMX Management Console

by Jesper Pedersen (JIRA)

JMX Management Console ---------------------- Key: JBJCA-211 URL: https://jira.jboss.org/jira/browse/JBJCA-211 Project: JBoss JCA Issue Type: Task Components: Standalone Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha6 Add a basic JMX management console based on the AS/jmx-console -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBJCA-212) WAR deployer

by Jesper Pedersen (JIRA)

WAR deployer ------------ Key: JBJCA-212 URL: https://jira.jboss.org/jira/browse/JBJCA-212 Project: JBoss JCA Issue Type: Task Components: Deployer Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha6 Add a WARDeployer for the web server -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBJCA-213) KernelClassLoader should implement Closeable

by Jesper Pedersen (JIRA)

KernelClassLoader should implement Closeable -------------------------------------------- Key: JBJCA-213 URL: https://jira.jboss.org/jira/browse/JBJCA-213 Project: JBoss JCA Issue Type: Task Components: Fungal Affects Versions: 1.0.0.Alpha5 Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha6 The KernelClassLoader should implement the java.io.Closeable interface. The close() method should be a no-op, as deployment units may call the method. Add an explicit shutdown() method to implement the real close() functionality. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBJCA-209) Eclipse JDT 3.1.1

by Jesper Pedersen (JIRA)

Eclipse JDT 3.1.1 ----------------- Key: JBJCA-209 URL: https://jira.jboss.org/jira/browse/JBJCA-209 Project: JBoss JCA Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha6 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-210) DOM4J 1.6.1

by Jesper Pedersen (JIRA)

DOM4J 1.6.1 ----------- Key: JBJCA-210 URL: https://jira.jboss.org/jira/browse/JBJCA-210 Project: JBoss JCA Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha6 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2324) "TasksAssignedAsPotentialOwner" and "TasksOwned", etc. return empty List<TaskSummary>

by Julien Cheype (JIRA)

"TasksAssignedAsPotentialOwner" and "TasksOwned", etc. return empty List<TaskSummary> ------------------------------------------------------------------------------------- Key: JBRULES-2324 URL: https://jira.jboss.org/jira/browse/JBRULES-2324 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-process-task Affects Versions: 5.1.0.M1, 5.0.1.FINAL Reporter: Julien Cheype Assignee: Mark Proctor Current named queries like "TasksAssignedAsPotentialOwner" and "TasksOwned", etc. return empty List<TaskSummary> in any case if there is no description or subject. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-1088) TP: loopback=true does not discard multicast messages from self

by Bela Ban (JIRA)

TP: loopback=true does not discard multicast messages from self --------------------------------------------------------------- Key: JGRP-1088 URL: https://jira.jboss.org/jira/browse/JGRP-1088 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.8 In TP.handleMyMessage(), we have this code: if(loopback && multicast && msg.isFlagSet(Message.LOOPBACK)) { return; // drop message that was already looped back and delivered } Because LOOPBACK is *never* set in Message, a multicast message sent by A will always (1) get looped back to A and (2) get received but *not* discarded to to the above code. The correct code should check whether the sender and receiver are identical, e.g. if(loopback && multicast) { if(!isSingleton()) { if(local_addr != null && local_addr.equals(msg.getSrc())) return; // drop message that was already looped back and delivered } } The added twist is that we need to handle the case where the shared transport doesn't have a local_addr. In this case, TP.ProtocolAdapter.up() needs to run the same check and discard the message if needed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2009