August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3482) Still a WARN message during failed close

by Adrian Brock (JIRA)

Still a WARN message during failed close ---------------------------------------- Key: JBAS-3482 URL: http://jira.jboss.com/jira/browse/JBAS-3482 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.0.4.GA Reporter: Adrian Brock Assigned To: Weston Price Fix For: JBossAS-4.0.5.GA Further to JBAS-1831, there is a still a WARN message in the path when it fails to close a connection. It is in the InternalManagedConnectionPool /** * Destroy a connection * * @param cl the connection to destroy */ private void doDestroy(ConnectionListener cl) { if (cl.getState() == ConnectionListener.DESTROYED) { log.trace("ManagedConnection is already destroyed " + cl); return; } connectionCounter.dec(); cl.setState(ConnectionListener.DESTROYED); try { cl.getManagedConnection().destroy(); } catch (Throwable t) { log.warn("Exception destroying ManagedConnection " + cl, t); // <----------- This should be a debug message } } It can be seen in the following stacktrace: org.jboss.resource.JBossResourceException: SQLException; - nested throwable: (java.sql.SQLException: Io exception: Broken pipe) at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkException(BaseWrapperManagedConnection.java:481) at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.destroy(BaseWrapperManagedConnection.java:206) at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.doDestroy(InternalManagedConnectionPool.java:550) at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.removeTimedOut(InternalManagedConnectionPool.java:415) at org.jboss.resource.connectionmanager.IdleRemover$1.run(IdleRemover.java:81) at java.lang.Thread.run(Thread.java:595) Caused by: java.sql.SQLException: Io exception: Broken pipe at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:255) at oracle.jdbc.driver.T4CConnection.logoff(T4CConnection.java:480) at oracle.jdbc.driver.PhysicalConnection.close(PhysicalConnection.java:1175) at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.destroy(BaseWrapperManagedConnection.java:202) ... 4 more -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] Resolved: (JBAS-2899) Externalize Tomcat Authenticators at the Host Level

by Anil Saldhana (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2899?page=all ] Anil Saldhana resolved JBAS-2899. --------------------------------- Resolution: Done There is a testcase for this. So if there is a breakage, we will know. > Externalize Tomcat Authenticators at the Host Level > --------------------------------------------------- > > Key: JBAS-2899 > URL: http://jira.jboss.com/jira/browse/JBAS-2899 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service, Security > Affects Versions: JBossAS-4.0.4.GA > Reporter: Anil Saldhana > Assigned To: Anil Saldhana > Fix For: JBossAS-4.0.5.CR1, JBossAS-5.0.0.Beta > > > This issue is related to JBAS-2481. My initial discussion with Remy on customization of authenticators at the tomcat sar level or webapp level via the injection of ContextConfig into StandardContext, was not agreed. Remy advised me to utilize the route of using the "configClass" attribute on the <host> element, to provide a custom version of the ContextConfig class. > I have tested this and it works perfectly. > ----------------------------------------------------------------------------------------------------------------------- > <Host name="localhost" > autoDeploy="false" deployOnStartup="false" deployXML="false" > configClass="org.jboss.web.tomcat.security.config.JBossContextConfig"> > ----------------------------------------------------------------------------------------------------------------------- > Here is the JBossContextConfig class that I tested: > ======================================================================================= > public class JBossContextConfig extends ContextConfig > { > /** > * Create a new JBossContextConfig. > */ > public JBossContextConfig() > { > super(); > try > { > Map authMap = this.getAuthenticators(); > if(authMap.size() > 0) > customAuthenticators = authMap; > }catch(Exception e) > { > throw new IllegalStateException("Failed to customize authenticators::" + > e.getMessage()); > } > > } > > private Map getAuthenticators() throws Exception > { > Map cmap = new HashMap(); > ClassLoader tcl = Thread.currentThread().getContextClassLoader(); > Authenticator basic = (Authenticator)tcl.loadClass("org.apache.catalina.authenticator.SSLAuthenticator").newInstance(); > Authenticator clientCert = (Authenticator)tcl.loadClass("org.apache.catalina.authenticator.BasicAuthenticator").newInstance(); > Authenticator digest = (Authenticator)tcl.loadClass("org.apache.catalina.authenticator.DigestAuthenticator").newInstance(); > Authenticator form = (Authenticator)tcl.loadClass("org.apache.catalina.authenticator.FormAuthenticator").newInstance(); > Authenticator none = (Authenticator)tcl.loadClass("org.apache.catalina.authenticator.NonLoginAuthenticator").newInstance(); > > cmap.put("BASIC",basic); > cmap.put("CLIENT-CERT",clientCert); > cmap.put("DIGEST",digest); > cmap.put("FORM", form); > cmap.put("NONE", none); > return cmap; > } > } > ====================================================================================================== > When I enabled jmx-console security, the error message in the browser: > HTTP Status 400 - No client certificate chain in this request > As you can see from the code above, I interchanged the authenticators for BASIC and CLIENT-CERT and default jmx-console security is BASIC. So > the SSLAuthenticator has kicked in. > This JIRA tasks involves writing a MBean service that provides the configurable map of authenticators, which the JBossContextConfig will solicit. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JGRP-111) Improve performance of RpcDispatcher/MessageDispatcher/RequestCorrelator/MethodCall

by Bela Ban (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-111?page=all ] Bela Ban updated JGRP-111: -------------------------- Fix Version/s: 2.4 (was: 2.5) > Improve performance of RpcDispatcher/MessageDispatcher/RequestCorrelator/MethodCall > ----------------------------------------------------------------------------------- > > Key: JGRP-111 > URL: http://jira.jboss.com/jira/browse/JGRP-111 > Project: JGroups > Issue Type: Task > Affects Versions: 2.2.8, 2.2.9, 2.3, 2.4, 2.2.9.1, 2.2.9.2, 2.2.9 SP3 (2.2.9.3), 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-267) RoundTrip is slow with bundling disabled

by Bela Ban (JIRA)

RoundTrip is slow with bundling disabled ---------------------------------------- Key: JGRP-267 URL: http://jira.jboss.com/jira/browse/JGRP-267 Project: JGroups Issue Type: Bug Affects Versions: 2.3 SP1 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.4 #1 Disable bundling in fc-fast-minimalthreads.xml: UDP.enable_bundling="false" #2 Run the server: jt RoundTrip -server -props ./fc-fast-minimalthreads.xml #3 Run the client: $ jt RoundTrip -props ./fc-fast-minimalthreads.xml -num 10 The first time, the client runs okay, but when it is run multiple times, it always slows down halfway through a run -- 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, 11 months

1
10
0 / 0

[JBoss JIRA] Commented: (JGRP-111) Improve performance of RpcDispatcher/MessageDispatcher/RequestCorrelator/MethodCall

by Bela Ban (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-111?page=comments#action_12340743 ] Bela Ban commented on JGRP-111: ------------------------------- Okay, one *BIG* change: in UDP, I disabled bundling (enable_bundling="false"), this took 2 * 30ms on average out of each call (see below). The problem with bundling is that while it is great for asynchronous message sending, it is fatal for RPC-style request-response interaction with small messages ! $ jt RpcDispatcherSpeedTest -mode id -num 10000 -props ./fc-fast-minimalthreads.xml ------------------------------------------------------- GMS: address is 192.168.5.2:2736 ------------------------------------------------------- -- new view: [192.168.5.2:2715|5] [192.168.5.2:2715, 192.168.5.2:2736] -- invoking 10000 methods using mode=ID 1000 2000 3000 4000 5000 6000 7000 8000 9000 10000 time for 10000 remote calls was 5719, avg=0.5719ms/invocation, 1748 calls/sec > Improve performance of RpcDispatcher/MessageDispatcher/RequestCorrelator/MethodCall > ----------------------------------------------------------------------------------- > > Key: JGRP-111 > URL: http://jira.jboss.com/jira/browse/JGRP-111 > Project: JGroups > Issue Type: Task > Affects Versions: 2.2.8, 2.2.9, 2.3, 2.4, 2.2.9.1, 2.2.9.2, 2.2.9 SP3 (2.2.9.3), 2.3 SP1 > Reporter: Bela Ban > Assigned To: Bela Ban > Fix For: 2.5 > > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBIDE-322) Unused plugin dependency in org.jboss.ide.eclipse.ejb3.wizards.ui on org.eclipse.jdt.source

by Pierre Raoul (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-322?page=comments#action_12340739 ] Pierre Raoul commented on JBIDE-322: ------------------------------------ There is still a reference to org.eclipse.jdt.source in eclipse\features\org.jboss.ide.eclipse.ejb3.feature_1.1.0.Alpha1a\feature.xml. Unless it's removed, the Eclipse Feature Update function is unavailable. > Unused plugin dependency in org.jboss.ide.eclipse.ejb3.wizards.ui on org.eclipse.jdt.source > -------------------------------------------------------------------------------------------- > > Key: JBIDE-322 > URL: http://jira.jboss.com/jira/browse/JBIDE-322 > Project: JBoss IDE > Issue Type: Bug > Components: EJB3 plugin > Affects Versions: 1.5 Final > Reporter: Francois Granade > Assigned To: Marshall Culpepper > Priority: Minor > Fix For: 2.0.0.Alpha > > > The plugin org.jboss.ide.eclipse.ejb3.wizards.ui declare a dependency on org.eclipse.jdt.source. You can see that in the Manifest file: > http://fisheye.labs.jboss.com/viewrep/JBoss/jbosside/ejb3/plugins/org.jbo... > Unless I'm mistaken, this dependency is not needed (why would the wizard have a dependency on JDT source code ???) > It's innocuous, but this causes an error to appear in Eclipse error log. > Also, for us at http://www.easyeclipse.org, it means that we have to patch the manifest when we build it. It's small, but useless -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1841) SAR/ServiceController should be a facade over the generic dependency controller

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1841?page=all ] Adrian Brock updated JBAS-1841: ------------------------------- Fix Version/s: JBossAS-5.0.0.Beta > SAR/ServiceController should be a facade over the generic dependency controller > ------------------------------------------------------------------------------- > > Key: JBAS-1841 > URL: http://jira.jboss.com/jira/browse/JBAS-1841 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: System service > Reporter: Adrian Brock > Assigned To: Adrian Brock > Priority: Critical > Fix For: JBossAS-5.0.0.Beta > > > Rework the ServiceCreator, ServiceConfigurator, ServiceController > to use the generic deployment controller. > This will allow MBeans to take part in the same dependency/injection protocol > as the plain javabeans provided by the MicroContainer. > It also adds the "Describe" stage to the lifecycle allowing classloading dependencies. > This will first be prototyped in system2 rather than system. > The initial work will not include reworking the XML to use JBossXB > schema binding, but that is obviously desirable. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-1841) SAR/ServiceController should be a facade over the generic dependency controller

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1841?page=all ] Adrian Brock reassigned JBAS-1841: ---------------------------------- Assignee: Adrian Brock > SAR/ServiceController should be a facade over the generic dependency controller > ------------------------------------------------------------------------------- > > Key: JBAS-1841 > URL: http://jira.jboss.com/jira/browse/JBAS-1841 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: System service > Reporter: Adrian Brock > Assigned To: Adrian Brock > Priority: Critical > Fix For: JBossAS-5.0.0.Beta > > > Rework the ServiceCreator, ServiceConfigurator, ServiceController > to use the generic deployment controller. > This will allow MBeans to take part in the same dependency/injection protocol > as the plain javabeans provided by the MicroContainer. > It also adds the "Describe" stage to the lifecycle allowing classloading dependencies. > This will first be prototyped in system2 rather than system. > The initial work will not include reworking the XML to use JBossXB > schema binding, but that is obviously desirable. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-1701) Rewrite to use Unified Container/Interceptors and MicroContainer

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1701?page=all ] Adrian Brock reassigned JBAS-1701: ---------------------------------- Assignee: (was: Adrian Brock) > Rewrite to use Unified Container/Interceptors and MicroContainer > ---------------------------------------------------------------- > > Key: JBAS-1701 > URL: http://jira.jboss.com/jira/browse/JBAS-1701 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JMX > Reporter: Adrian Brock > Priority: Critical > Fix For: JBossAS-5.0.0.Beta > > > Rewrite JBossMX to use the Unified Container/Interceptors and MicroContainer. > This will help the integration work of the MicroContainer into JBoss5 > and also provide a full test of the Unified Container/Interceptors. > The other advantage is that all aspects will be available to MBeans. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-1701) Rewrite to use Unified Container/Interceptors and MicroContainer

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1701?page=all ] Adrian Brock reassigned JBAS-1701: ---------------------------------- Assignee: Adrian Brock > Rewrite to use Unified Container/Interceptors and MicroContainer > ---------------------------------------------------------------- > > Key: JBAS-1701 > URL: http://jira.jboss.com/jira/browse/JBAS-1701 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JMX > Reporter: Adrian Brock > Assigned To: Adrian Brock > Priority: Critical > Fix For: JBossAS-5.0.0.Beta > > > Rewrite JBossMX to use the Unified Container/Interceptors and MicroContainer. > This will help the integration work of the MicroContainer into JBoss5 > and also provide a full test of the Unified Container/Interceptors. > The other advantage is that all aspects will be available to MBeans. -- 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, 11 months

1
0
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 August 2006