December 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4633) ClientAbortException stacktrace lines log as separate Log4J events.

by Matthew Robinson (JIRA)

ClientAbortException stacktrace lines log as separate Log4J events. ------------------------------------------------------------------- Key: JBAS-4633 URL: http://jira.jboss.com/jira/browse/JBAS-4633 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-4.0.5.GA Environment: SuSE Linux 10.0 Reporter: Matthew Robinson Assigned To: Remy Maucherat Priority: Minor A ClientAbortException is raised legitimately when an end-user closes thier browser before the web app is finished responding to the request. However, when the stacktrace is generated, it seems that each line is being logged using separate Log4J logger.log() call. This results in a nice looking file-base log: 2007-08-27 09:10:31,402 ERROR [STDERR] ClientAbortException: java.net.SocketException: Broken pipe 2007-08-27 09:10:31,640 ERROR [STDERR] at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:366) 2007-08-27 09:10:31,937 ERROR [STDERR] at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:353) 2007-08-27 09:10:32,131 ERROR [STDERR] at org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:392) 2007-08-27 09:10:32,326 ERROR [STDERR] at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:381) 2007-08-27 09:10:32,607 ERROR [STDERR] at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:88) ... But it causes unnecessary grief and clutter when using SMTP to log errors. Each line results in a separate email! So my inbox fills with an average of 60 emails per ClientAbortException! This problem seems to confined to the ClientAbortException. Other errors log the stacktrace as a single Log4J event. Please may I have this error logged in the same way? Ta. -- 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

16 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-4970) Hot redeployment displaying old content

by Petr Hejl (JIRA)

Hot redeployment displaying old content --------------------------------------- Key: JBAS-4970 URL: http://jira.jboss.com/jira/browse/JBAS-4970 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-5.0.0.Beta2 Environment: Linux 2.6.22-14-generic java version "1.5.0_13" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05) Java HotSpot(TM) Server VM (build 1.5.0_13-b05, mixed mode) Reporter: Petr Hejl Assigned To: Remy Maucherat Priority: Critical If the war is hot redeployed (delete war, copy the new one) fast enough, the server still displays the old content. It notes the new one - the expanded content at tmp/deploy/webaap-....war is the fresh one, however the (freshly) compiled jsps (in work/jboss.web/localhost/webapp/org/apache/jsp) are still the old. Same occurs for the war inside the ear. Occurs for both J2EE1.4 and Java EE5 projects. -- 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

16 years, 5 months

2
2
0 / 0

[JBoss JIRA] Updated: (JBCACHE-60) Partitioned Cache

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-60?page=all ] Manik Surtani updated JBCACHE-60: --------------------------------- Complexity: High > Partitioned Cache > ----------------- > > Key: JBCACHE-60 > URL: http://jira.jboss.com/jira/browse/JBCACHE-60 > Project: JBoss Cache > Issue Type: Feature Request > Reporter: Bela Ban > Assigned To: Manik Surtani > Fix For: 3.2.0 > > Original Estimate: 10 weeks > Remaining Estimate: 10 weeks > > - Distributed load across multiple nodes in a cluster > - No replication/redundancy -- 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

16 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-167) Implement generic dependency annotation handling

by Ales Justin (JIRA)

Implement generic dependency annotation handling ------------------------------------------------ Key: JBMICROCONT-167 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-167 Project: JBoss MicroContainer Issue Type: Feature Request Components: Dependency Reporter: Ales Justin Assigned To: Ales Justin Handle dependency annotations in Decribe and Instantiate (factory generated beans) states. Add appropriate dependency / install items. Handling should be generic - easily able to add / handle new dependency annotations. -- 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

16 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-1235) Fix JBCACHE-1165 on 1.4.X branch

by Brian Stansberry (JIRA)

Fix JBCACHE-1165 on 1.4.X branch -------------------------------- Key: JBCACHE-1235 URL: http://jira.jboss.com/jira/browse/JBCACHE-1235 Project: JBoss Cache Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Manik Surtani Fix on 1.4.X branch was reverted in SP8 as it was causing problems. Need to reexamine. -- 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

16 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-5070) Extending container configurations without changing the name is not supported in the new MetaData

by Adrian Brock (JIRA)

Extending container configurations without changing the name is not supported in the new MetaData ------------------------------------------------------------------------------------------------- Key: JBAS-5070 URL: http://jira.jboss.com/jira/browse/JBAS-5070 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Reporter: Adrian Brock Assigned To: Alexey Loubyansky Fix For: JBossAS-5.0.0.CR1 The new metadata doesn't support overridding a container configuration like the old code did. e.g. This changes the "Standard Stateless SessionBean" for this ejb deployment without changing the name. jboss.xml <container-configurations> <container-configuration> <container-name>Standard Stateless SessionBean</container-name> <depends>test:name=Test</depends> </container-configuration> </container-configurations> -- 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

16 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-5072) Fix null pointer exception when getting keys, values, or entry's in the ConcurrentHashmap

by Jay Howell (JIRA)

Fix null pointer exception when getting keys, values, or entry's in the ConcurrentHashmap ----------------------------------------------------------------------------------------- Key: JBAS-5072 URL: http://jira.jboss.com/jira/browse/JBAS-5072 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-4.2.2.GA Reporter: Jay Howell Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA Fixed null problem for JBAS-4698. The previous fix fixed the problem by using iteration instead of values(), but it also allowed nulls to be put into the array, which throws a null pointer exception. This is just further refinement of the JBAS-4698 bug. -- 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

16 years, 5 months

2
8
0 / 0

[JBoss JIRA] Created: (JBAS-3460) Allow per-webapp configuration of useJK, snapshotMode and snapshotInterval

by Brian Stansberry (JIRA)

Allow per-webapp configuration of useJK, snapshotMode and snapshotInterval -------------------------------------------------------------------------- Key: JBAS-3460 URL: http://jira.jboss.com/jira/browse/JBAS-3460 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.1.CR1 The Tomcat SAR's useJK, snapshotMode and snapshotInterval attributes all drive the creation of valves that are deployed per web-app. Therefore the properties could also be changed per web-app. Need to add them to jboss-web.xml. -- 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

16 years, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (JBAS-4961) Default for JBossCacheManager useJK is whether jvmRoute is set

by Brian Stansberry (JIRA)

Default for JBossCacheManager useJK is whether jvmRoute is set -------------------------------------------------------------- Key: JBAS-4961 URL: http://jira.jboss.com/jira/browse/JBAS-4961 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.0.Beta3 Having to configure "useJK" for the JBossWeb service is redundant, since Engine.jvmRoute is null by default. Treat having Engine.jvmRoute set as meaning JBossCacheManager should add the JvmRouteValve. Allow override via JBossWebMetaData (jboss-web.xml). -- 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

16 years, 5 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBAS-2870) Separate the HA aspect from the invoker proxy

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2870?page=all ] Brian Stansberry updated JBAS-2870: ----------------------------------- Fix Version/s: JBossAS-5.0.0.CR1 (was: JBossAS-5.0.0.Beta3) Affects: [Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration] (was: [Compatibility/Configuration, Documentation (Ref Guide, User Guide, etc.)]) > Separate the HA aspect from the invoker proxy > --------------------------------------------- > > Key: JBAS-2870 > URL: http://jira.jboss.com/jira/browse/JBAS-2870 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Fix For: JBossAS-5.0.0.CR1 > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Comment from Scott Stark (http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3926369#3926369) > HA proxy invokers like JRMPInvokerProxyHA should not exist. The only difference between an ha proxy and regular proxy would be an interceptor that selected from the available targets and set the invocation proxy such that the common Invoker proxy was told the transport proxy to use. Even an unclustered proxy could have a recover/ha sematic like blocking until the server is availble with this configuration. HA is an aspect that should not be embedded in the transport specific proxy. -- 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

16 years, 5 months

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 December 2007