November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBASM-25) Always set jboss.server.log.threshold=DEBUG when starting server test configurations

by Shelly McGowan (JIRA)

Always set jboss.server.log.threshold=DEBUG when starting server test configurations ------------------------------------------------------------------------------------ Key: JBASM-25 URL: https://jira.jboss.org/jira/browse/JBASM-25 Project: JBoss AS Server Manager Issue Type: Feature Request Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 1.0.1.GA so it does not have to be configured individually. Reference: https://jira.jboss.org/jira/browse/JBAS-6205?focusedCommentId=12438665#ac... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JASSIST-68) Remove limitation on public constructors

by Erik Putrycz (JIRA)

Remove limitation on public constructors ---------------------------------------- Key: JASSIST-68 URL: https://jira.jboss.org/jira/browse/JASSIST-68 Project: Javassist Issue Type: Feature Request Affects Versions: 3.8.1.GA Reporter: Erik Putrycz Assignee: Shigeru Chiba Currently when extending a class with javassist, it is required that the superclass has a public constructor. However, in some cases, this is not a necessary constraint. For instance when extending a class and generating a factory with Javassist, it is better to hide the constructor to prevent users to bypass the factory, and this is not possible currently. This would involve a minor change in inheritAllConstructors() in class CtNewClass -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JASSIST-32) Add method debugWriteFile(String directoryName) to CtClass

by Martin Burger (JIRA)

Add method debugWriteFile(String directoryName) to CtClass ---------------------------------------------------------- Key: JASSIST-32 URL: http://jira.jboss.com/jira/browse/JASSIST-32 Project: Javassist Issue Type: Feature Request Reporter: Martin Burger Assigned To: Shigeru Chiba Priority: Minor Attachments: patch.txt Class CtClass provides method debugWriteFile(). A method debugWriteFile(String directoryName) that calls writeFile(directoryName) would be helpful. -- 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

15 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAOP-648) Pointcut call(* *->@java.lang.Deprecated(..)) does not work

by Flavia Rainone (JIRA)

Pointcut call(* *->@java.lang.Deprecated(..)) does not work ----------------------------------------------------------- Key: JBAOP-648 URL: https://jira.jboss.org/jira/browse/JBAOP-648 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.5.6.GA Reporter: Flavia Rainone The pointcut is not triggering advices on the call of such joinpoints. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-5941) NullPointerException in ClusteredSession

by Radoslav Husar (JIRA)

NullPointerException in ClusteredSession ---------------------------------------- Key: JBAS-5941 URL: https://jira.jboss.org/jira/browse/JBAS-5941 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-5.0.0.CR2 Environment: perf01 Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: JBossAS-5.0.0.GA During SOAK (failover, session replication, passivation disabled) testing, after 90 minutes JBoss logs: [JBoss] 11:24:29,329 ERROR [CoyoteAdapter] An exception or error occurred in the container during the request processing [JBoss] java.lang.NullPointerException [JBoss] at org.jboss.web.tomcat.service.session.ClusteredSession.update(ClusteredSession.java:1097) [JBoss] at org.jboss.web.tomcat.service.session.SessionBasedClusteredSession.update(SessionBasedClusteredSession.java:154) [JBoss] at org.jboss.web.tomcat.service.session.distributedcache.impl.jbc.JBossCacheService.loadSession(JBossCacheService.java:344) [JBoss] at org.jboss.web.tomcat.service.session.JBossCacheManager.loadSession(JBossCacheManager.java:1432) [JBoss] at org.jboss.web.tomcat.service.session.JBossCacheManager.findSession(JBossCacheManager.java:491) [JBoss] at org.apache.catalina.connector.Request.isRequestedSessionIdValid(Request.java:2160) [JBoss] at org.apache.catalina.connector.CoyoteAdapter.parseSessionCookiesId(CoyoteAdapter.java:626) [JBoss] at org.apache.catalina.connector.CoyoteAdapter.postParseRequest(CoyoteAdapter.java:551) [JBoss] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:322) [JBoss] at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437) [JBoss] at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:384) [JBoss] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) [JBoss] at java.lang.Thread.run(Thread.java:619) Hudson build: http://hudson.qa.jboss.com/hudson/job/as5-soak/44/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
13
0 / 0

[JBoss JIRA] Created: (JBAS-6038) Examine use of SessionReplicationContext start/finishCacheActivity

by Brian Stansberry (JIRA)

Examine use of SessionReplicationContext start/finishCacheActivity ------------------------------------------------------------------ Key: JBAS-6038 URL: https://jira.jboss.org/jira/browse/JBAS-6038 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.1.CR1 I don't believe the calls to SessionReplicationContext.startCacheActivity and finishCacheActivity are necessary any longer; confirm this and remove if so. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1564) add other configurations to hudson+create hudson tasks

by Radoslav Husar (JIRA)

add other configurations to hudson+create hudson tasks ------------------------------------------------------ Key: EJBTHREE-1564 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1564 Project: EJB 3.0 Issue Type: Sub-task Reporter: Radoslav Husar Assignee: Radoslav Husar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTEST-8) add a stop task option to silently ignore shutdown errors

by Aleksandar Kostadinov (JIRA)

add a stop task option to silently ignore shutdown errors --------------------------------------------------------- Key: JBTEST-8 URL: https://jira.jboss.org/jira/browse/JBTEST-8 Project: JBoss Test Issue Type: Feature Request Affects Versions: 1.1.2.GA Reporter: Aleksandar Kostadinov Assignee: Shelly McGowan Fix For: 1.1.3.GA It could be useful to have a stop task option to silently ignore shutdown errors. For example when we know we screwed up a server config with some test and want server manager to kill its process and not complain anyhow. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1230) Client failover support if one node of a cluster is cleanly shut down.

by Phillip Thurmond (JIRA)

Client failover support if one node of a cluster is cleanly shut down. ---------------------------------------------------------------------- Key: JBMESSAGING-1230 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1230 Project: JBoss Messaging Issue Type: Feature Request Reporter: Phillip Thurmond Assigned To: Tim Fox Fix For: 1.4.0.SP3.CP01 If one node of a cluster fails in someway, the client will attempt to failover transparently. However, if one node is shutdown cleanly, the client will not automatically failover to another node in the cluster. This functionality would be very useful for "rolling upgrades" where a portion of the cluster is left up while the other nodes are being updated. -- 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

15 years, 9 months

3
11
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-213) check and warn if system time on joining node if off

by Radoslav Husar (JIRA)

check and warn if system time on joining node if off ---------------------------------------------------- Key: JBCLUSTER-213 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-213 Project: JBoss Clustering Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Radoslav Husar Assignee: Brian Stansberry Priority: Minor When new node joins the cluster, It can simply exchange time with other nodes. If the time is off by significant number of seconds, it would warn the administrator to synchronize the time on cluster machines. Since some services depend on having time synchronized, this could help users to find this problem quickly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
8
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2008