May 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCOMMON-121) CLONE - JBossEntityResolver returns false positives in resolveClassName()

by Kyle Lape (JIRA)

CLONE - JBossEntityResolver returns false positives in resolveClassName() ------------------------------------------------------------------------- Key: JBCOMMON-121 URL: https://issues.jboss.org/browse/JBCOMMON-121 Project: JBoss Common Issue Type: Bug Security Level: Public (Everyone can see) Components: common-core (2.x) Affects Versions: 2.2.16.GA Environment: Found in EAP 5.0.0, reproduced in EAP 5.1.0 Reporter: Kyle Lape Given a URL with no filename, the entityResolver will return an incorrect match from the class loader. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1864) Deadlock in creating consumer during failover time

by Yong Hao Gao (JIRA)

Deadlock in creating consumer during failover time -------------------------------------------------- Key: JBMESSAGING-1864 URL: https://issues.jboss.org/browse/JBMESSAGING-1864 Project: JBoss Messaging Issue Type: Bug Components: JMS Clustering Affects Versions: 1.4.8.GA, 1.4.0.SP3.CP12 Reporter: Yong Hao Gao Assignee: Yong Hao Gao Fix For: 1.4.0.SP3.CP13, 1.4.8.SP1 When a node is performing failover for the dead node, there is a possible condition where a dead lock could happen if a new binding is created at that time (triggered by creating a new subscription on a topic). To reproduce you need manually 'instrument' the code to create a suitable timing: 1 set up a 2 node cluster node0 and node1 2 kill node0 and let the failover happen. Let it stops at MessagingPostOffice.performFailover(), after the line pm.mergeTransactions(failedNodeID.intValue(), thisNodeID); So at this point the write lock is just about to be obtained. 3 create a consumer (must be a new subscriber) on node1, let the calling thread proceed to MessagingPostOffice.addBindingInMemory(), before the line: clusterNotifier.sendNotification(notification); The ClusterConnectionManager is the listener to handle the notification, meaning this call will result in holding the lock on ClusterConnectionManager (its notify() mehtod is synchronized) 4 then resume Step 2, the failover thread will grab the write lock and proceed. Along the way let it stop for another time at MessagingPostOffice.removeBindingInMemory(), before the line: clusterNotifier.sendNotification(notification); Now this failover thread holds the write lock of the post office and is about to get the lock on ClusterConnectionManager (because it is the listener to handle the notification in its synchronized notify() method). 5 Resume step 3, the consumer creating thread grabs the lock on ClusterConnectionManager. As it goes on, it calls MessagingPostOffice.getBindings() method, which is going to get the read lock of MessagingPostOffice. However at this moment the failover thread is holding the write lock, which prevents it from getting the read lock. It has to wait for it. 6. Now resume step 4. As it happens, in step 5 the consumer creating thread already gets the lock on ClusterConnectionManager, so it cannot proceed. In the meantime it holds the write lock and never get released, so the consumer creating thread will never get it. The two thread get dead-locked. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2088) DroolsObjectIOTest.testFileIO test.dat

by Aleksandar Kostadinov (JIRA)

DroolsObjectIOTest.testFileIO test.dat -------------------------------------- Key: JBRULES-2088 URL: https://jira.jboss.org/jira/browse/JBRULES-2088 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.0.0.CR1 Environment: 5.0.0.26115.FINAL Reporter: Aleksandar Kostadinov Assignee: Mark Proctor Priority: Minor The DroolsObjectIOTest.testFileIO is trying to open /org/drools/common/test.dat which is located in the classes target directory. IMHO it should be put in resources so classes can be used in a jar. That's a minor issue with the test suite but good to be fixed as we are putting tests in jars for the product QA works. -- 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

13 years, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1096) Make SLSB and SFSB hot deployable for RAD

by Jason Long (JIRA)

Make SLSB and SFSB hot deployable for RAD ----------------------------------------- Key: EJBTHREE-1096 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1096 Project: EJB 3.0 Issue Type: Feature Request Affects Versions: AS 4.2.2.GA, AS 4.2.1.GA, AS 4.2.0 GA, AS 5.0.0.Beta3, AS 4.2.3.GA, Branch_4_2, Branch_4_4, HEAD Reporter: Jason Long Fix For: AS 4.2.3.GA Seam POJO components are hot deployable for RAD. It would be great if SFSB and SLSB could be used in the same manner. -- 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

13 years, 7 months

13
28
0 / 0

[JBoss JIRA] Created: (AS7-736) Datasource configuration: Turn "enabled" checkbox into state indicator

by Heiko Braun (JIRA)

Datasource configuration: Turn "enabled" checkbox into state indicator ----------------------------------------------------------------------- Key: AS7-736 URL: https://issues.jboss.org/browse/AS7-736 Project: Application Server 7 Issue Type: Enhancement Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.CR1 Jim wrote: I am confused in the second shot by the En/Disable button, and then a checkbox with is enabled? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1897) Implement (Internal)Resource on top of JBoss VFS

by Ales Justin (JIRA)

Implement (Internal)Resource on top of JBoss VFS ------------------------------------------------ Key: JBRULES-1897 URL: https://jira.jboss.org/jira/browse/JBRULES-1897 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-mc Affects Versions: 5.0.0.M3 Reporter: Ales Justin Assignee: Ales Justin Priority: Minor If we run Drools in environment which has JBoss VFS in its classpath, we should use VFSResource implementation for URL based resources. -- 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

13 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2208) Agenda-group not picked up in decision table

by Jaroslaw Kijanowski (JIRA)

Agenda-group not picked up in decision table -------------------------------------------- Key: JBRULES-2208 URL: https://jira.jboss.org/jira/browse/JBRULES-2208 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-decisiontables Affects Versions: 5.0.1.FINAL Reporter: Jaroslaw Kijanowski Assignee: Michael Neale The class drools-decisiontables/src/main/java/org/drools/decisiontable/parser/DefaultRuleSheetListener is missing AGENDAGROUP in the nextDataCell method. Attaching patch. This test class drools-decisiontables/src/test/java/org/drools/decisiontable/parser/ActionTypeTest.java could be also extended to verify the AGENDAGROUP keyword. -- 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

13 years, 7 months

4
4
0 / 0

[JBoss JIRA] Created: (JBRULES-851) Provide RuleFlow editing capabilities within JBRMS

by Michael Anstis (JIRA)

Provide RuleFlow editing capabilities within JBRMS -------------------------------------------------- Key: JBRULES-851 URL: http://jira.jboss.com/jira/browse/JBRULES-851 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Michael Anstis Assigned To: Mark Proctor Ruleflow should be available in the JBRMS (apologies is this JIRA should have been raised against JBRMS). -- 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

13 years, 7 months

5
9
0 / 0

[JBoss JIRA] Created: (JBAS-9331) Log JNDI locations of EJB Proxies on Deployment

by Andrew Rubinger (JIRA)

Log JNDI locations of EJB Proxies on Deployment ----------------------------------------------- Key: JBAS-9331 URL: https://issues.jboss.org/browse/JBAS-9331 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: EJB Reporter: Andrew Rubinger Assignee: Carlo de Wolf Previous versions of AS have logged out, at INFO level, the JNDI locations of EJB proxies when an EJB is deployed. This is helpful for developer debugging. For instance: 10:11:18,719 INFO [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI: SecureDeploymentManager/remote - EJB3.x Default Remote Business Interface SecureDeploymentManager/remote-org.jboss.deployers.spi.management.deploy.DeploymentManager - EJB3.x Remote Business Interface -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2336) Context assist in DSLR Editor

by Hamza Bakkali (JIRA)

Context assist in DSLR Editor ----------------------------- Key: JBRULES-2336 URL: https://jira.jboss.org/jira/browse/JBRULES-2336 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: All Affects Versions: 5.0.1.FINAL Environment: Eclipse 3.4.2 GANYMEDE Reporter: Hamza Bakkali Assignee: Mark Proctor Fix For: 4.0.8 I have been using drools 4 for couple of months now and I am starting to get the hang of it. We recently decided to move to Dools 5 with Eclipse 3.4.2 (Ganymede). We unfortunately hit a major 'show stopper' (for us). In the DSLR editor: Context Assist + space + enter removes/replaces the whole line, not only the place holder. In other words: DSL: [*][]Log : {msg}=System.out.println("{msg}"); [*][]id1="some id label" DSLR: rule "MyRule" when then end If I Press L , control space --> the line Log:{msg} appears in the context menu. Hit enter I get Log :{msg} Now, If want to replace msg by id1. I position the cursor in the {msg}, hit ctrl space, id1 shows in the list. I hit enter the whole line disappear, and I am left with id1 instead of Log : id1 Is this a setting somewhere in eclipse itself?? I doubt it. The same thing use to work as expected in Drools 4. thanks. -- 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

13 years, 7 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2011