January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBXB-117) Map binding annotations

by Alexey Loubyansky (JIRA)

Map binding annotations ----------------------- Key: JBXB-117 URL: http://jira.jboss.com/jira/browse/JBXB-117 Project: JBoss XML Binding (JBossXB) Issue Type: Feature Request Affects Versions: JBossXB-2.0.0.CR5 Reporter: Alexey Loubyansky Assigned To: Alexey Loubyansky Fix For: JBossXB-2.0.0.CR6 Currently maps are bound with @XmlJavaTypeAdapter. See org.jboss.test.xb.builder.object.element.javatypeadapter.test.JavaTypeAdapterUnitTestCase. There was an idea to add map-specific binding annotations. -- 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, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBREM-854) Mechanism for interceptor-level communications

by David Lloyd (JIRA)

Mechanism for interceptor-level communications ---------------------------------------------- Key: JBREM-854 URL: http://jira.jboss.com/jira/browse/JBREM-854 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: Remoting 3 M2 Need a way for interceptors to "talk" across the wire, to implement interceptor operations and share state. -- 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, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-643) ClassConfigurator.getInstance() not thread safe

by Michael Newcomb (JIRA)

ClassConfigurator.getInstance() not thread safe ----------------------------------------------- Key: JGRP-643 URL: http://jira.jboss.com/jira/browse/JGRP-643 Project: JGroups Issue Type: Bug Reporter: Michael Newcomb Assigned To: Bela Ban Creating 2 or more JChannels simultaneously could result in multiple ClassConfigurators being created and inited at once or a ClassConfigurator being used before it has been inited. Recommend synchronizing the getInstance() method. -- 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, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (JGRP-297) Use deadlock detection (JDK 5) to find deadlocks in stress tests or during regular operation

by Bela Ban (JIRA)

Use deadlock detection (JDK 5) to find deadlocks in stress tests or during regular operation -------------------------------------------------------------------------------------------- Key: JGRP-297 URL: http://jira.jboss.com/jira/browse/JGRP-297 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 The java.lang.management.ThreadMXBean has a method to check for and (if found) enumerate deadlocked threads (only with simply synchronized locks, jav.util.concurrent locks currently not supported afaik). This can be run every N seconds, and is useful in both stress testing and possibly also during operation. -- 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, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JGRP-548) TCP_NIO: include in cruise control (beside UDP, TCP and MUX)

by Bela Ban (JIRA)

TCP_NIO: include in cruise control (beside UDP, TCP and MUX) ------------------------------------------------------------ Key: JGRP-548 URL: http://jira.jboss.com/jira/browse/JGRP-548 Project: JGroups Issue Type: Task Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6 -- 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, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JBRULES-682) Test real-life problem/constraints with large data sets

by Geoffrey De Smet (JIRA)

Test real-life problem/constraints with large data sets ------------------------------------------------------- Key: JBRULES-682 URL: http://jira.jboss.com/jira/browse/JBRULES-682 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Components: Solver Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Priority: Optional Exam Timetabling http://www.cs.nott.ac.uk/~rxq/data.htm Nurse rostering: http://www.cs.nott.ac.uk/~tec/NRP/ -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-679) Move code into JBoss svn + refactor rename packages

by Geoffrey De Smet (JIRA)

Move code into JBoss svn + refactor rename packages --------------------------------------------------- Key: JBRULES-679 URL: http://jira.jboss.com/jira/browse/JBRULES-679 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Priority: Minor Rename package net.sf.taseree to org.drools.solver -- 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, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1330) Using RuleBase in multithread application server environment

by Navaljit Bhasin (JIRA)

Using RuleBase in multithread application server environment ------------------------------------------------------------ Key: JBRULES-1330 URL: http://jira.jboss.com/jira/browse/JBRULES-1330 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Rule Flow Affects Versions: 4.0.3 Environment: Red Hat Linux as OS, weblogic 9.2 using jrockit-1.5.0_10 Reporter: Navaljit Bhasin We are deploying an applcation which has one major component which executes rules. At the startup of the application server, we load the various rules and save them in a hashmap with appropriate key. The value of these HashMaps is RuleBase. This is part of a singleton service. The applcation is based on JMS. A MDB receives message, calls the sigleton service to get stateful session from a specific RuleBase ( saved in HashMap by key as mentioned above). This singleton service get the RuleBase from Map, call newStatefulSession(false) on this RuleBase object and return the new StatefulSession. This works fine as long as we have one MDB on the application server. When we increase the number of MDB's to more than one, and both MDB's process the messages( different messages) simultaneously, the results from stateful session rule firing are messed up. It skips amny valid LHS and so on. I even tried using the Stateless Session, but the results are still messed up. So my question is: Can we use the Rulebase in multithreaded environment ? My understanding was that we can use it. There should be no interaction between various stateful sessions received from same rulebase object. If we can't use it this way, the we have build it form PackageBuilder for every invocation. There are lots of complex rules and for hundreds of calls it adds up to considerable waste of resources. Thanks for reading this bug report Can you please post or email me the code to use the statefule sessions from a RuleBase object in multithreaded environment? -- 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, 5 months

2
9
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1200) Session.executor is leaking the first classLoader used

by Clebert Suconic (JIRA)

Session.executor is leaking the first classLoader used ------------------------------------------------------ Key: JBMESSAGING-1200 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1200 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP2 Reporter: Clebert Suconic Assigned To: Clebert Suconic The Session.executor is holding the first ClassLoader reference on its ThreadContextClassLoader. This is also causing invalid classLoader usages when the first ClassLoader used was undeployed, and could lead to other problems on ObjectMessages and StreamMessages. (things like ClassNotFound becuase it's using the wrong classLoader on the executor). -- 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, 5 months

2
8
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-480) Change contract of Receiver

by Tim Fox (JIRA)

Change contract of Receiver --------------------------- Key: JBMESSAGING-480 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-480 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox -- 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, 5 months

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 January 2008