April 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4409) Add Keystore alias support to security realm keystore definition.

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-4409: ------------------------------------- Summary: Add Keystore alias support to security realm keystore definition. Key: AS7-4409 URL: https://issues.jboss.org/browse/AS7-4409 Project: Application Server 7 Issue Type: Sub-task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.2.Final-redhat1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
1
0 / 0

[JBoss JIRA] (AS7-4416) Collect module.xml files during JDR collection

by Jesse Jaggars (JIRA)

Jesse Jaggars created AS7-4416: ---------------------------------- Summary: Collect module.xml files during JDR collection Key: AS7-4416 URL: https://issues.jboss.org/browse/AS7-4416 Project: Application Server 7 Issue Type: Enhancement Components: JDR Affects Versions: 7.1.1.Final Reporter: Jesse Jaggars Assignee: Jesse Jaggars JDR should collect module.xml files from the modules/ directory. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-9360) MessagingClientTestCase is not using a deterministic approach to determining queue existence

by Jason Greene (JIRA)

MessagingClientTestCase is not using a deterministic approach to determining queue existence -------------------------------------------------------------------------------------------- Key: JBAS-9360 URL: https://issues.jboss.org/browse/JBAS-9360 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Jason Greene Clebert suggests the issue may be with having a session factory open. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

5
11
0 / 0

[JBoss JIRA] (AS7-4415) Default up handler of Channel created by jgroups subsystem interferes with custom receivers.

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-4415: --------------------------------- Summary: Default up handler of Channel created by jgroups subsystem interferes with custom receivers. Key: AS7-4415 URL: https://issues.jboss.org/browse/AS7-4415 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 7.1.2.Final-redhat1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-2480) Intermittent failure in JMSQueueManagementTestCase

by Brian Stansberry (Created) (JIRA)

Intermittent failure in JMSQueueManagementTestCase -------------------------------------------------- Key: AS7-2480 URL: https://issues.jboss.org/browse/AS7-2480 Project: Application Server 7 Issue Type: Task Components: JMS Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.1.0.CR1 Failed tests: testMessageRemoval(org.jboss.as.test.integration.messaging.mgmt.JMSQueueManagementTestCase): expected:<[success]> but was:<[failed]> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

5
6
0 / 0

[JBoss JIRA] (AS7-3800) JBOSS_BASE_DIR is checked in standalone.sh but not used to set -Djboss.server.base.dir

by Stian Lund (JIRA)

Stian Lund created AS7-3800: ------------------------------- Summary: JBOSS_BASE_DIR is checked in standalone.sh but not used to set -Djboss.server.base.dir Key: AS7-3800 URL: https://issues.jboss.org/browse/AS7-3800 Project: Application Server 7 Issue Type: Bug Components: Scripts, Server Affects Versions: 7.1.0.Final Environment: Linux, WIndows Reporter: Stian Lund Assignee: Brian Stansberry Priority: Minor In standalone/domain.sh JBOSS_BASE_DIR is checked for and and used to set vars JBOSS_LOG_DIR and JBOSS_CONFIG_DIR (introduced in 7.1 Final) but not actually used to set java property jboss.server.base.dir, resulting in $JBOSS_HOME/standalone(/domain) still being used for tmp and cache. Workaround is to still have -Djboss.server.base.dir set in launch parameter or init-script. Still should be put into script like: "-Djboss.server.base.dir=$JBOSS_BASE_DIR" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
2
0 / 0

[JBoss JIRA] (JGRP-1446) "viewChange" function doesnt work properly in ReplicatedHashMap.Notification<Object, Object>

by jerome tan (JIRA)

jerome tan created JGRP-1446: -------------------------------- Summary: "viewChange" function doesnt work properly in ReplicatedHashMap.Notification<Object,Object> Key: JGRP-1446 URL: https://issues.jboss.org/browse/JGRP-1446 Project: JGroups Issue Type: Bug Affects Versions: 3.0.9 Environment: Windows 7/JDK1.6.0_31 Reporter: jerome tan Assignee: Bela Ban When I ran the demo: ReplicatedHashMapDemo in the source code of version 3.0.9. The "viewChange" function did not always invoke when new members join. In the demo, the title of window changes when new member joins, but actually it is: When there is one member the title is: 'ReplicatedHashMapDemo: 1 server(s)' When there is two members titles are: 'ReplicatedHashMapDemo: 1 server(s)','ReplicatedHashMapDemo: 2 server(s)' When there is three members titles are: 'ReplicatedHashMapDemo: 3 server(s)','ReplicatedHashMapDemo: 2 server(s)','ReplicatedHashMapDemo: 3 server(s)' I am not sure if this demo program can be run one sever with multiple instance. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
3
0 / 0

[JBoss JIRA] (JGRP-1445) Null pointer exception in FLUSH.rejectFlush()

by David Hotham (JIRA)

David Hotham created JGRP-1445: ---------------------------------- Summary: Null pointer exception in FLUSH.rejectFlush() Key: JGRP-1445 URL: https://issues.jboss.org/browse/JGRP-1445 Project: JGroups Issue Type: Bug Affects Versions: 3.1 Reporter: David Hotham Assignee: Bela Ban Continuing to test JGRP-1426 / JGRP-1443, I noticed this go past: Exception in thread "Thread-10" java.lang.NullPointerException at org.jgroups.protocols.pbcast.FLUSH.rejectFlush(FLUSH.java:566) at org.jgroups.protocols.pbcast.FLUSH.access$100(FLUSH.java:42) at org.jgroups.protocols.pbcast.FLUSH$2.run(FLUSH.java:824) at java.lang.Thread.run(Thread.java:662) So far as I can see, this one is fairly benign; but I figure that reporting it is the right thing to do. Thanks! David -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
8
0 / 0

[JBoss JIRA] Created: (JBRULES-2685) Performance degradation from 5.0.1 to 5.1.0

by Greg Barton (JIRA)

Performance degradation from 5.0.1 to 5.1.0 ------------------------------------------- Key: JBRULES-2685 URL: https://jira.jboss.org/browse/JBRULES-2685 Project: Drools Issue Type: Quality Risk Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.1.0.FINAL Environment: OSX 1.6.2 Reporter: Greg Barton Assignee: Mark Proctor Priority: Minor Attachments: DroolsNested.tar.gz I've observed a sizable (25%) performance degradation between the 5.0.1 and 5.1.0 releases. I've attached a sample project that tests the performance of matching nested objects. (ANd compares direct reference matching and the performance pitfalls of "from," but that's beside the current point.) If you switch the pom.xml from using 5.0.1 to 5.1.0 for the drools dependencies you'll see 25% longer execution times on the tests. (mvn test) Here's the test output: 5.0.1 reference.drl Count: 2000 reference.drl Time: 267ms reference.drl Time per element: 0.1335ms BAR Duplicates: 780 FOO Duplicates: 880 reference.drl Count: 20000 reference.drl Time: 1249ms reference.drl Time per element: 0.06245ms BAR Duplicates: 7702 FOO Duplicates: 8040 from.drl Count: 200 from.drl Time: 1139ms from.drl Time per element: 5.695ms BAR Duplicates: 112 FOO Duplicates: 102 reference.drl Count: 200 reference.drl Time: 5ms reference.drl Time per element: 0.025ms BAR Duplicates: 86 FOO Duplicates: 60 5.1.0 reference.drl Count: 2000 reference.drl Time: 300ms reference.drl Time per element: 0.15ms BAR Duplicates: 788 FOO Duplicates: 820 reference.drl Count: 20000 reference.drl Time: 1564ms reference.drl Time per element: 0.0782ms BAR Duplicates: 8142 FOO Duplicates: 7960 from.drl Count: 200 from.drl Time: 3543ms from.drl Time per element: 17.715ms BAR Duplicates: 68 FOO Duplicates: 90 reference.drl Count: 200 reference.drl Time: 13ms reference.drl Time per element: 0.065ms BAR Duplicates: 84 FOO Duplicates: 74 On the most taxing test (20k objects) 5.0.1 took 1249ms while 5.1.0 took 1564ms, and for larger tests the effect is more pronounced. This is primarily a test of == on object references. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

5
23
0 / 0

[JBoss JIRA] (AS7-4410) Add Keystore alias support to CLI configuration.

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-4410: ------------------------------------- Summary: Add Keystore alias support to CLI configuration. Key: AS7-4410 URL: https://issues.jboss.org/browse/AS7-4410 Project: Application Server 7 Issue Type: Sub-task Components: CLI Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.2.Final-redhat1 The CLI handles it's own Keystore loading so should also be updated to support an alias. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2012