November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCOMMON-1) ArchiveBrowser does not handle Windows directories with whitespace

by Emmanuel Bernard (JIRA)

ArchiveBrowser does not handle Windows directories with whitespace ------------------------------------------------------------------ Key: JBCOMMON-1 URL: http://jira.jboss.com/jira/browse/JBCOMMON-1 Project: JBoss Common Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Emmanuel Bernard Assigned To: Emmanuel Bernard Priority: Minor new File(url.toString()) fails on white spaced directories -- 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

19 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCOMMON-5) fix file structure of subprojects

by Ruel Loehr (JIRA)

fix file structure of subprojects --------------------------------- Key: JBCOMMON-5 URL: http://jira.jboss.com/jira/browse/JBCOMMON-5 Project: JBoss Common Issue Type: Feature Request Security Level: Public (Everyone can see) Components: core, logging-jdk, logging-log4j, logging-spi Reporter: Ruel Loehr Assigned To: Ruel Loehr Move the subprojects from repos/common/trunk/ ..... to repos/common -- 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

19 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-312) Make testsuite configurable to run with different stack configurations

by Bela Ban (JIRA)

Make testsuite configurable to run with different stack configurations ---------------------------------------------------------------------- Key: JGRP-312 URL: http://jira.jboss.com/jira/browse/JGRP-312 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 All test programs should use a system property (with a default if the system property is not defined). The testsuite can then be run with the system property, so all tests use TCP, for example. We could also use multiple targets, one for each major stack configuration. An 'all-unittests' target would run all of them. -- 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

19 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-321) CloseTest.testShutdown() fails with -Dconfig=tcp.xml

by Bela Ban (JIRA)

CloseTest.testShutdown() fails with -Dconfig=tcp.xml ---------------------------------------------------- Key: JGRP-321 URL: http://jira.jboss.com/jira/browse/JGRP-321 Project: JGroups Issue Type: Bug Affects Versions: 2.3 SP1 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.4 -- 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

19 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-840) Make testsuite configurable to run with different Jgroups stack configurations

by Vladimir Blagojevic (JIRA)

Make testsuite configurable to run with different Jgroups stack configurations ------------------------------------------------------------------------------ Key: JBCACHE-840 URL: http://jira.jboss.com/jira/browse/JBCACHE-840 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Vladimir Blagojevic Assigned To: Vladimir Blagojevic Fix For: 2.0.0.GA All junit tests should have a system property (with a default if the system property is not defined) to use a certain JGroups protocol stack. Thus, for example, we can run whole JBC testsuite with Jgroups tcp stack. We should have multiple tests targets that run testsuite with tcp,udp, and other supported protocols. -- 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

19 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-3851) Slow DataSource Failover - JCA Stale Connection Detection

by Jason Sicotte (JIRA)

Slow DataSource Failover - JCA Stale Connection Detection --------------------------------------------------------- Key: JBAS-3851 URL: http://jira.jboss.com/jira/browse/JBAS-3851 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.4.GA Environment: Windows XP Pro SP2, Java 1.5.0_05 Reporter: Jason Sicotte Assigned To: Weston Price JBoss customer support recommends I log our issue as a feature request. The following is my original description of the issue: "We are seeing a slow DataSource failover. I have attached a log file which shows said failover. The lines of interest are: 15:50:34,843 INFO [DatasourceConnectionProvider] Using datasource: java:/DefaultDS <a bunch of stack traces> 15:52:49,578 WARN [HALocalManagedConnectionFactory] Failed to create connection for jdbc:mysql: .... 15:52:49,671 INFO [SettingsFactory] RDBMS: MySQL, version: 4.1.7-nt This shows it takes about 135 seconds for the database failover. Some details on my setup: I have two clustered JBoss instances running on two computers. Both nodes are also running an instance of MySQL. Node 1 has the "primary" database, and Node 2 has a replicated "backup". Both JBoss instances have the HA DataSource configured to point to the MySQL server running on Node 1 first. To replicate the issue, I disconnect the network cable from Node 1. This then causes Node 2 to become the HA singleton master and a DataSource failover to the "backup" database." The issue I just described seemed to be caused by the connection pool staying alive while each connection failed. So even though the first connection dies, the others must fail in succession for the failure to be complete. According to Luc Texier, the crux of the issue is: "Each connection is individually checked when a client requests it. The issue is that the validation is performed by the connection factory e.g. BaseWrapperManagedConnectionFactory.isValidConnection() which is blocking other validations while the socket is wondering what's going on. After the timeout, this first connection is failing over but the second one has to be validated anyway...then blocking, timeout and so on" What we need here is for the pool to be invalidated if a single connection failure is detected. Perhaps add it as an option to turn on/off? -- 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

19 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-156) consistent packaging

by Kurt Stam (JIRA)

consistent packaging -------------------- Key: JBESB-156 URL: http://jira.jboss.com/jira/browse/JBESB-156 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kurt Stam Assigned To: Mark Little Can we do some more refactoring of package names? For example I'd like to see everything in 'product/core/common' directory to be rooted in the org.jboss.soa.esb.common.* package. 'product/core/services' directory to be rooted in the org.jboss.soa.esb.services.* package. Somehow it's all mixed up right now and I keep on having to click around to find classes. -- 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

19 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-145) Automate the trailblazer as part of QA

by Mark Little (JIRA)

Automate the trailblazer as part of QA -------------------------------------- Key: JBESB-145 URL: http://jira.jboss.com/jira/browse/JBESB-145 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples, Testing Affects Versions: 4.0 Beta 1 Reporter: Mark Little Assigned To: Daniel Brum Fix For: 4.0 -- 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

19 years, 6 months

1
10
0 / 0

[JBoss JIRA] Created: (JBESB-238) Remove dependency on W3C DOM

by Mark Little (JIRA)

Remove dependency on W3C DOM ---------------------------- Key: JBESB-238 URL: http://jira.jboss.com/jira/browse/JBESB-238 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ESB Core Reporter: Mark Little Assigned To: Mark Little -- 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

19 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-166) Update trailblazer to include FTP support (maybe a separate scenario)

by Mark Little (JIRA)

Update trailblazer to include FTP support (maybe a separate scenario) --------------------------------------------------------------------- Key: JBESB-166 URL: http://jira.jboss.com/jira/browse/JBESB-166 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.0 Beta 1 Maintenance Pack 1 Reporter: Mark Little Assigned To: Daniel Brum Priority: Minor Fix For: 4.0 -- 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

19 years, 6 months

1
3
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 November 2006