October 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

18 years, 7 months

2
1
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

18 years, 7 months

1
2
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

18 years, 7 months

3
7
0 / 0

[JBoss JIRA] Created: (JBAS-3818) Application Client Container capabilities may be useful

by Mike Khlu (JIRA)

Application Client Container capabilities may be useful ------------------------------------------------------- Key: JBAS-3818 URL: http://jira.jboss.com/jira/browse/JBAS-3818 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: EJB3, Other Reporter: Mike Khlu Assigned To: Bill Burke Now we have pretty nice @EJB annotation within there no the ugly JNDI-client code required. please look at http://java.sun.com/j2ee/1.4/docs/relnotes/cliref/hman1m/appclient.1m.html and "Creating a Reference to an Enterprise Bean Instance" chapter on J2ee 5 Sun's tutorial. I think that would be great to have application client container's possibilities in the best app server (aka JBoss)!!! sorry, my english isn't glance -- 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

18 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4707) Convert ClientDeployer to a AbstractVFSParsingDeployer subclass

by Scott M Stark (JIRA)

Convert ClientDeployer to a AbstractVFSParsingDeployer subclass --------------------------------------------------------------- Key: JBAS-4707 URL: http://jira.jboss.com/jira/browse/JBAS-4707 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Deployment services Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.Beta3 The org.jboss.deployment.ClientDeployer needs to be a AbstractVFSParsingDeployer that outputs ClientMetaData -- 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

18 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1030) Implement EE 8.2.1 section 2 functionality

by Carlo de Wolf (JIRA)

Implement EE 8.2.1 section 2 functionality ------------------------------------------ Key: EJBTHREE-1030 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1030 Project: EJB 3.0 Issue Type: Sub-task Reporter: Carlo de Wolf Fix For: EJB 3.0 RC11 - FD -- 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

18 years, 7 months

1
4
0 / 0

[JBoss JIRA] Created: (JBAS-4424) WebAuthentication:Generate a SSOID

by Anil Saldhana (JIRA)

WebAuthentication:Generate a SSOID ---------------------------------- Key: JBAS-4424 URL: http://jira.jboss.com/jira/browse/JBAS-4424 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Security, Web (Tomcat) service Affects Versions: JBossAS-4.2.0.GA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-4.2.1.CR1 http://wiki.jboss.org/wiki/Wiki.jsp?page=WebAuthentication The feature needs to implement the sso stuff if it is desired by the user. At the least, ssoid needs to be generated and set on the session. The ssoid generation logic exists in AuthenticatorBase. -- 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

18 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-1168) Sometimes aquired locks are not released

by Jacek Halat (JIRA)

Sometimes aquired locks are not released ---------------------------------------- Key: JBCACHE-1168 URL: http://jira.jboss.com/jira/browse/JBCACHE-1168 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: PojoCache Affects Versions: 1.4.1.SP4 Environment: Windows XP, jrockit90_150_06 Solaris 10 Reporter: Jacek Halat Assigned To: Jason T. Greene Attachments: TransactionStormTest.java Sometimes under heavy load acquired locks are not released - node is locked forever. Only what can we do is stop/start cache. Main loop: while (true) { for (int x = 0; x < 2; x++) { WorkThread t = new WorkThread(x == 1); threads.add(t); t.start(); } for (WorkThread separateThread : threads) { separateThread.join(); if (separateThread.getException() != null) { //separateThread.getException().getMessage(); } } int locksNum = getNumberOfLocksHeld(); // System.out.println("Locks="+locksNum); // checkpoint if (cache.getNumberOfLocksHeld()>0){ System.out.println("ERROR, locks="+locksNum); doDomethingOnCache(1); } assertEquals(0, locksNum); } Exception - after //checkpoint line numberOfLocks is grater than 0! JUnit is provided to this issue, but this error is nondeterministic - sometimes fails after 5 seconds and another time after 20 minutes. -- 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

18 years, 7 months

3
13
0 / 0

[JBoss JIRA] Created: (JBCACHE-1183) Acquired WL lock could be not released after async transaction rolback

by Jacek Halat (JIRA)

Acquired WL lock could be not released after async transaction rolback ---------------------------------------------------------------------- Key: JBCACHE-1183 URL: http://jira.jboss.com/jira/browse/JBCACHE-1183 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Environment: WindowsXP, jdk150_06 Reporter: Jacek Halat Assigned To: Manik Surtani In some cases on weblogic (and other servers where transaction manager with async transaction rollback after timeout is used) acquired WL can be not released. Only way to release lock is stop/start cche again. -- 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

18 years, 7 months

2
9
0 / 0

[JBoss JIRA] Created: (EJBTHREE-748) The implementation of equals() in org.jboss.ejb3.ProxyUtils.handleCallLocally() throws a NPE when being passed a null argument.

by Nicolas Bielza (JIRA)

The implementation of equals() in org.jboss.ejb3.ProxyUtils.handleCallLocally() throws a NPE when being passed a null argument. ------------------------------------------------------------------------------------------------------------------------------- Key: EJBTHREE-748 URL: http://jira.jboss.com/jira/browse/EJBTHREE-748 Project: EJB 3.0 Issue Type: Bug Environment: Embedded EJB3 container Reporter: Nicolas Bielza When looking up an entity bean, we get a proxy which implements equals() in a broken way: Here's an example: // Proxy NPE test: InitialContext ctx = new InitialContext(); Manager m = (Manager)ctx.lookup("ManagerAction/local"); try { if(m != null) { m.equals(null); } System.err.println("What bug ???"); } catch(NullPointerException e) { System.err.println("ProxyUtils NPE bug detected."); e.printStackTrace(); } And the output: ProxyUtils NPE bug detected. java.lang.NullPointerException at org.jboss.ejb3.ProxyUtils.handleCallLocally(ProxyUtils.java:156) at org.jboss.ejb3.ProxyUtils.handleCallLocally(ProxyUtils.java:137) at org.jboss.ejb3.stateful.StatefulLocalProxy.invoke(StatefulLocalProxy.java:92) at $Proxy34.equals(Unknown Source) at com.alligacom.nett.NetTransferAdminInterface.<init>(NetTransferAdminInterface.java:49) at com.alligacom.nett.NetTransferAdminInterface.main(NetTransferAdminI nterface.java:87) The incriminated line (156) in ProxyUtils is: return new Boolean(ih.toString().equals(args[0].toString())); and should be: return new Boolean(args[0] == null ? false : ih.toString().equals(args[0].toString())); -- 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

18 years, 7 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 October 2007