December 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-696) Closing a connection that failed over can close the Invoker

by Clebert Suconic (JIRA)

Closing a connection that failed over can close the Invoker ----------------------------------------------------------- Key: JBMESSAGING-696 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-696 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.Beta1 Reporter: Clebert Suconic Assigned To: Tom Elrod Fix For: 1.2.0.Beta2 There is a bug on remoting, where connections created inside Lease will loose reference counting. HATest::testCloseOnFailover reproduces this problem. -- 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

3
5
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: (JBMICROCONT-134) Introduce KernelControllerContextAware into each KernelControllerContextAction

by Ales Justin (JIRA)

Introduce KernelControllerContextAware into each KernelControllerContextAction ------------------------------------------------------------------------------ Key: JBMICROCONT-134 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-134 Project: JBoss MicroContainer Issue Type: Task Components: Kernel Reporter: Ales Justin Assigned To: Ales Justin Priority: Minor Fix For: JBossMC_2_0_0_CR1 Since there were issues on where this KernelControllerContextAware support should be, we can introduce it in all Actions - as an optional overridding implementation. Maybe we can also introduce some fine grained Aware interfaces - depending on the state they support / are 'aware' of. -- 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
2
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-136) Metadata Builder util class

by Ales Justin (JIRA)

Metadata Builder util class --------------------------- Key: JBMICROCONT-136 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-136 Project: JBoss MicroContainer Issue Type: Task Components: MetaData Reporter: Ales Justin Assigned To: Ales Justin Priority: Optional Fix For: JBossMC_2_0_0_CR1 Introducing C++ or StringBuffer kind of metadata Builder class: public class Builder { public Builder addPropertyMetaData(String propertyName) { ... return this; } } -- 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

[JBoss JIRA] Created: (JBMICROCONT-119) Add support for integer progression

by Adrian Brock (JIRA)

Add support for integer progression ----------------------------------- Key: JBMICROCONT-119 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-119 Project: JBoss MicroContainer Issue Type: Feature Request Components: BeanInfo Affects Versions: JBossMC_2_0_0 Beta Reporter: Adrian Brock There are a number of places where it might be useful to support integer progression, e.g. float -> int or Float -> Integer and vice versa. This will mean that the exact type is not necessary when doing for example injection from one bean to another. -- 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
5
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-137) VirtualFile.findChild("WEB-INF/classes") fails for SyntheticDirEntries

by Thomas Diesler (JIRA)

VirtualFile.findChild("WEB-INF/classes") fails for SyntheticDirEntries ---------------------------------------------------------------------- Key: JBMICROCONT-137 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-137 Project: JBoss MicroContainer Issue Type: Bug Components: VFS Reporter: Thomas Diesler Priority: Blocker I have two WARs. The first (generated by the CTS porting layer) fails because the DeploymentUnit.classLoader cannot load com.sun.ts.tests.webservices.deploy.warDeploy.HelloJavaBean The reason is that WEB-INF/classes is not added to the the the classloader [tdiesler@localhost cts]$ jar -tf WarDeployApp_web.war WarDeploy.xml WEB-INF/webservices.xml WEB-INF/wsdl/WarDeploy.wsdl WEB-INF/classes/com/sun/ts/tests/webservices/deploy/warDeploy/HelloJavaBean.class WEB-INF/classes/com/sun/ts/tests/webservices/deploy/warDeploy/HelloWs.class WEB-INF/web.xml META-INF/MANIFEST.MF The second (generated by ant) is fine. It contains jar entries for every directory level [tdiesler@localhost cts]$ jar -tf jaxrpc-samples-jsr109pojo-rpc.war META-INF/ META-INF/MANIFEST.MF WEB-INF/ WEB-INF/classes/ WEB-INF/classes/org/ WEB-INF/classes/org/jboss/ WEB-INF/classes/org/jboss/test/ WEB-INF/classes/org/jboss/test/ws/ WEB-INF/classes/org/jboss/test/ws/jaxrpc/ WEB-INF/classes/org/jboss/test/ws/jaxrpc/samples/ WEB-INF/classes/org/jboss/test/ws/jaxrpc/samples/jsr109pojo/ WEB-INF/classes/org/jboss/test/ws/jaxrpc/samples/jsr109pojo/JaxRpcJSEEndpoint.class WEB-INF/classes/org/jboss/test/ws/jaxrpc/samples/jsr109pojo/JaxRpcTestService.class WEB-INF/classes/org/jboss/test/ws/jaxrpc/samples/jsr109pojo/SimpleUserType.class WEB-INF/wsdl/ WEB-INF/jaxrpc-mapping.xml WEB-INF/webservices.xml WEB-INF/wsdl/TestService.wsdl WEB-INF/web.xml I set this as blocking issue because all WS war deployments fail that don't have a WEB-INF/classes jar entry. -- 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

3
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-699) Ensure remoting implements true asynchronous callbacks

by Tim Fox (JIRA)

Ensure remoting implements true asynchronous callbacks ------------------------------------------------------ Key: JBMESSAGING-699 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-699 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Priority: Blocker We need to chase remoting to make sure they implement true asynchronous invocations. We need these for delivering messages from the server to the client, and for sending certain invocations from client to server. Without this, performance will greatly suffer. A "true" asynchonous callback is where the invocation is written to the transport using the same thread as the invoking thread, and returns immediately. It does not wait to read a response, and it just execute a normal invocation using a thread from a pool and discard the result. -- 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
5
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-296) Service description language and contracts

by Mark Little (JIRA)

Service description language and contracts ------------------------------------------ Key: JBESB-296 URL: http://jira.jboss.com/jira/browse/JBESB-296 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) 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
2
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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2006