May 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-723) Creating XA datasource requires driver name and version

by Heiko Braun (JIRA)

Creating XA datasource requires driver name and version ------------------------------------------------------- Key: AS7-723 URL: https://issues.jboss.org/browse/AS7-723 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.CR1 It's weird, because the XA datasource itself just relies on the DataSource class. The driver and version info is only needed to identify the module/service: Request { "operation" => "add", "address" => [ ("profile" => "default"), ("subsystem" => "datasources"), ("xa-data-source" => "H2XADS") ], "name" => "H2XADS", "jndi-name" => "H2XADS", "enabled" => true, "xa-data-source-class" => "org.h2.jdbcx.JdbcDataSource", "pool-name" => "H2XADS_Pool", "user-name" => "sa", "password" => "sa", "xa-data-source-properties" => [("URL" => "jdbc:h2:mem:test")], "child-type" => undefined } Response Internal Server Error { "outcome" => "failed", "result" => {"server-groups" => {"main-server-group" => { "server-two" => { "host" => "local", "response" => { "outcome" => "failed", "failure-description" => "java.util.NoSuchElementException: No child 'driver' exists" } }, "server-one" => { "host" => "local", "response" => { "outcome" => "failed", "failure-description" => "java.util.NoSuchElementException: No child 'driver' exists" } } }}}, "failure-description" => "Operation was not applied successfully to any servers" } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Moved: (JBBUILD-679) Add JPDFUnit to JBoss Repository

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBBUILD-679?page=com.atlassian.jira.plugi... ] George Gastaldi moved SEAMREPORTS-4 to JBBUILD-679: --------------------------------------------------- Project: JBoss Build System (was: Seam Reports) Key: JBBUILD-679 (was: SEAMREPORTS-4) Issue Type: Feature Request (was: Task) Workflow: jira (was: GIT Pull Request workflow ) > Add JPDFUnit to JBoss Repository > -------------------------------- > > Key: JBBUILD-679 > URL: https://issues.jboss.org/browse/JBBUILD-679 > Project: JBoss Build System > Issue Type: Feature Request > Reporter: George Gastaldi > > Check if it is possible to use http://jpdfunit.sourceforge.net on this project -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2238) Accumulate should be implemented with left-input incremental so they don't start from scratch on every left-input retraction/assertion

by Geoffrey De Smet (JIRA)

Accumulate should be implemented with left-input incremental so they don't start from scratch on every left-input retraction/assertion -------------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2238 URL: https://jira.jboss.org/jira/browse/JBRULES-2238 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-core (expert) Affects Versions: 5.0.1.FINAL Reporter: Geoffrey De Smet Assignee: Mark Proctor The current accumulate implementation has a severe performance loss in the drools-solver context. Edson said that this issue could be the culprit. However, for this to be implemented the true modify feature should first be implemented. See the discussion "Why is this DRL twice as slow?" on the dev user list. >From IRC: <ge0ffrey> more and more of my experiments show the poisones nature of accumulate for drools-solver. Probably because they are backwards chained (as I understand it?). Of course accummulate is great for many use cases, just not drools-solver. <ge0ffrey> The problem is, I have no way to workaround them. I need the sum of my logically inserted objects. <etirelli> ge0ffrey: no, accumulate are implemented as forward chain as usual <etirelli> the problem is that a left-input retraction on an accumulate node will throw away any result and a leftinput assert will recalculate everything from scratch <ge0ffrey> What do you mean by "must fully recalculate"? <etirelli> mean from scratch <ge0ffrey> Why does it do that? <etirelli> remember that modify = retract+assert <ge0ffrey> And right-input retractions won't recalculate everything from scratch? <etirelli> no... right input are incremental <ge0ffrey> would making leftinput assert incremental too be possible? <etirelli> ge0ffrey: the only way to do left-input incremental is with a feature called "true modify" -- 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

15 years, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBRULES-1466) please bail if user is using an incompatible MVEL

by Godmar Back (JIRA)

please bail if user is using an incompatible MVEL ------------------------------------------------- Key: JBRULES-1466 URL: http://jira.jboss.com/jira/browse/JBRULES-1466 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0.4 Reporter: Godmar Back When using MVEL, please check String constants org.mvel.MVEL.VERSION and org.mvel.MVEL.VERSION_SUB to see if it's compatible. Bail if it isn't. Ignoring version mismatches leads to difficult to diagnose problems, see: http://lists.jboss.org/pipermail/rules-users/2008-February/004759.html http://lists.jboss.org/pipermail/rules-users/2008-February/004709.html Thanks. -- 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

15 years, 1 month

6
20
0 / 0

[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

15 years, 1 month

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

15 years, 1 month

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

15 years, 1 month

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

15 years, 1 month

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

15 years, 1 month

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

15 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 May 2011