January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBREM-681) Add the possibility to obtain lease period period from a Client (Client.getLeasePeriod())

by Ovidiu Feodorov (JIRA)

Add the possibility to obtain lease period period from a Client (Client.getLeasePeriod()) ----------------------------------------------------------------------------------------- Key: JBREM-681 URL: http://jira.jboss.com/jira/browse/JBREM-681 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Alpha6 Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Minor Client.getLeasePeriod() should return the actual lease period in effect for that client (the LeasePinger uses minimum of all lease periods for all its clients if more than one client is serviced by it), or -1 if no lease pinging is going on for that client. -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-924) PojoCache to re-throw Cache exception

by Ben Wang (JIRA)

PojoCache to re-throw Cache exception ------------------------------------- Key: JBCACHE-924 URL: http://jira.jboss.com/jira/browse/JBCACHE-924 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Priority: Minor Fix For: 2.0.0.BETA1 Currently, PojoCache will re-throw the underlying Cache exception during detach and attach becuase it is under tx context. However, find does not. We should do a try cacht on find and re-throw the Cache exception such as TimeoutException if needed. Case in point is in pojo.LocalTexTest.testConcurrentPuts -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-922) Merge src-50 into src

by Ben Wang (JIRA)

Merge src-50 into src --------------------- Key: JBCACHE-922 URL: http://jira.jboss.com/jira/browse/JBCACHE-922 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Ben Wang Assigned To: Ben Wang Fix For: 2.0.0.BETA1 We will merge src-50 and test-50 into regular src and test now that we are all running on jdk50 -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-762) JBossRemoting throws java.lang.Exception in certain cases

by Clebert Suconic (JIRA)

JBossRemoting throws java.lang.Exception in certain cases --------------------------------------------------------- Key: JBMESSAGING-762 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-762 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.Beta1 Reporter: Clebert Suconic Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Beta2 Places where remoting can't connect to a server such as establishLease are throwing java.lang.Exception("textual messages"). It's impossible to treat those events on Interceptors. There are already testcases failing because of these things... so I don't know if we should require a thirdparty test for 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBREM-680) An invocation into a "broken" client should throw a subclass of IOException

by Ovidiu Feodorov (JIRA)

An invocation into a "broken" client should throw a subclass of IOException --------------------------------------------------------------------------- Key: JBREM-680 URL: http://jira.jboss.com/jira/browse/JBREM-680 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 2.2.0.Alpha6 Currently it throws Exception -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-679) Add the possibility to obtain ConnectionValidator's ping period from a Client

by Ovidiu Feodorov (JIRA)

Add the possibility to obtain ConnectionValidator's ping period from a Client ----------------------------------------------------------------------------- Key: JBREM-679 URL: http://jira.jboss.com/jira/browse/JBREM-679 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Minor Fix For: 2.2.0.Alpha6 -- 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, 3 months

1
1
0 / 0

[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, 3 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-379) Rework console-demo-01 flash demo to a lower resolution

by Tom Fennelly (JIRA)

Rework console-demo-01 flash demo to a lower resolution ------------------------------------------------------- Key: JBESB-379 URL: http://jira.jboss.com/jira/browse/JBESB-379 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0 CR2 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 5.0 Comment from Kevin Barfield: ======================= Record the flash demo at a lower resolution (1024x768)! I couldn't see the whole page on my screen. -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-381) Rework console-demo-0x flashes to use more meaningfull Message Exchange Participant names

by Tom Fennelly (JIRA)

Rework console-demo-0x flashes to use more meaningfull Message Exchange Participant names ----------------------------------------------------------------------------------------- Key: JBESB-381 URL: http://jira.jboss.com/jira/browse/JBESB-381 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.0 CR2 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 5.0 People may find "A" and "B" a bit unhelpful and having it all within the context of a story might help. Micah Gideon Modell wrote: > I agree that this looks great, but I think it might be easier to follow > if it was placed in the context of a story. Maybe change "A" to student > and "B" to teacher so the student gives the teacher their name on the > first day of class and then the teacher puts it into "last name, first > name" for the attendance roster... > > ...or something? > > Cheers! > Micah -- 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, 3 months

2
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 January 2007