April 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAOP-539) Need Javassist release

by Kabir Khan (JIRA)

Need Javassist release ---------------------- Key: JBAOP-539 URL: http://jira.jboss.com/jira/browse/JBAOP-539 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.GA javassist.util.proxy.RuntimeSupport was calling secure methods -- 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, 3 months

2
7
0 / 0

[JBoss JIRA] Created: (JBAOP-540) Modify DuplicateTestCase to extend AOPTestWithSetup

by Kabir Khan (JIRA)

Modify DuplicateTestCase to extend AOPTestWithSetup --------------------------------------------------- Key: JBAOP-540 URL: http://jira.jboss.com/jira/browse/JBAOP-540 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.GA It currently runs without security enabled -- 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, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-5468) when the shutdown of the server is complete, some ports still been used (timing issue)

by Jehudi Castro (JIRA)

when the shutdown of the server is complete, some ports still been used (timing issue) -------------------------------------------------------------------------------------- Key: JBAS-5468 URL: http://jira.jboss.com/jira/browse/JBAS-5468 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Environment: Red Hat Application Stack V.1.3 Reporter: Jehudi Castro Priority: Minor After the shutdown got the confirmation: 11:11:08,795 INFO [Server] Shutdown complete Shutdown complete Halting VM Then try to start the server again: [root@dhcp78-191 ~]# service jbossas start Starting jbossas: [FAILED] Port 8080 is busy, is there a Tomcat running? after a few seconds works fine -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBEE-1) Release the JavaEE 5.0.0.CR1 aggregate

by Dimitris Andreadis (JIRA)

Release the JavaEE 5.0.0.CR1 aggregate -------------------------------------- Key: JBEE-1 URL: http://jira.jboss.com/jira/browse/JBEE-1 Project: JBoss JavaEE APIs Issue Type: Release Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: 5.0.0.CR1 -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-953) CLONE [JBREM-945] - Allow ServerThread to keep running after SocketTImeoutException

by Ron Sigal (JIRA)

CLONE [JBREM-945] - Allow ServerThread to keep running after SocketTImeoutException ----------------------------------------------------------------------------------- Key: JBREM-953 URL: http://jira.jboss.com/jira/browse/JBREM-953 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.2.2.SP4 Reporter: Ron Sigal Assigned To: Ron Sigal Priority: Minor Fix For: 2.2.2.SP7 Currently, org.jboss.remoting.transport.socket.ServerThread will close its socket and return itself to the threadpool in the event of a SocketTimeoutException. However, it could simply continue trying to read the next invocation. The javadoc for java.net.Socket.setSoTimeout() states: Enable/disable SO_TIMEOUT with the specified timeout, in milliseconds. With this option set to a non-zero timeout, a read() call on the InputStream associated with this Socket will block for only this amount of time. If the timeout expires, a java.net.SocketTimeoutException is raised, though the Socket is still valid. If the timeout is due to transitory circumstances, then it would be much more efficient to allow the ServerThread to continue, rather than forcing the client to start over with a new socket. -- 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, 3 months

1
6
0 / 0

[JBoss JIRA] Created: (JBREM-951) CLONE [JBREM-942] - A deadlock encountered on ConnectionValidator

by Ron Sigal (JIRA)

CLONE [JBREM-942] - A deadlock encountered on ConnectionValidator ------------------------------------------------------------------ Key: JBREM-951 URL: http://jira.jboss.com/jira/browse/JBREM-951 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: transport Affects Versions: 2.2.2.SP5 Environment: JBoss-EAP-4.2, JBossMessaging-1.4.0-SP3, JBossRemoting-2.2.2-SP5 Reporter: Tyronne Wickramarathne Assigned To: Ron Sigal Priority: Critical Fix For: 2.2.2.SP7 This deadlock occurred on JBREM when a JBossMessaging Bridge was set and consuming messages. here's the StackTrace : Found one Java-level deadlock: ============================= "Thread-278": waiting to lock monitor 0x08128544 (object 0xce8b25e0, a java.lang.Object), which is held by "Timer-4" "Timer-4": waiting to lock monitor 0x08129160 (object 0xce89f508, a java.util.ArrayList), which is held by "Thread-278" Java stack information for the threads listed above: =================================================== "Thread-278": at org.jboss.remoting.ConnectionValidator.doStop(ConnectionValidator.java:526) - waiting to lock <0xce8b25e0> (a java.lang.Object) at org.jboss.remoting.ConnectionValidator.stop(ConnectionValidator.java:252) at org.jboss.remoting.ConnectionValidator.removeConnectionListener(ConnectionValidator.java:344) - locked <0xce89f508> (a java.util.ArrayList) at org.jboss.remoting.Client.removeConnectionListener(Client.java:398) at org.jboss.jms.client.remoting.JMSRemotingConnection.removeConnectionListener(JMSRemotingConnection.java:493) - locked <0xce8b18c8> (a org.jboss.jms.client.remoting.JMSRemotingConnection) at org.jboss.jms.client.container.ConnectionAspect.handleClose(ConnectionAspect.java:184) at sun.reflect.GeneratedMethodAccessor134.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121) at org.jboss.jms.client.delegate.ClientConnectionDelegate$close_N4742752445160157748.invokeNext(ClientConnectionDelegate$close_N4742752445160157748.java) at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) at org.jboss.jms.client.delegate.ClientConnectionDelegate$close_N4742752445160157748.invokeNext(ClientConnectionDelegate$close_N4742752445160157748.java) at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) at org.jboss.jms.client.delegate.ClientConnectionDelegate$close_N4742752445160157748.invokeNext(ClientConnectionDelegate$close_N4742752445160157748.java) at org.jboss.jms.client.delegate.ClientConnectionDelegate.close(ClientConnectionDelegate.java) at org.jboss.jms.client.JBossConnection.close(JBossConnection.java:132) at org.jboss.jms.server.bridge.Bridge.cleanup(Bridge.java:1098) at org.jboss.jms.server.bridge.Bridge.access$1100(Bridge.java:66) at org.jboss.jms.server.bridge.Bridge$FailureHandler.run(Bridge.java:1496) at java.lang.Thread.run(Thread.java:619) "Timer-4": at org.jboss.remoting.ConnectionValidator.notifyListeners(ConnectionValidator.java:553) - waiting to lock <0xce89f508> (a java.util.ArrayList) at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:286) - locked <0xce8b25e0> (a java.lang.Object) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) Found 1 deadlock. -- 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, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1970) FastURLDecoder / enhance error message

by Antoine Herzog (JIRA)

FastURLDecoder / enhance error message --------------------------------------- Key: JBPORTAL-1970 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1970 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: Common-1.0 Environment: JBP 2.6.4 Reporter: Antoine Herzog Priority: Minor Fix For: Common-1.0.1 small thing : in FastURLDecoder class at line : 329 line is : throw new MalformedInputException("Cannot decode char " + c); Adding some "[" and "]." would be better : throw new MalformedInputException("Cannot decode char [" + c + "]."); usual error case is a blank space in the url... and then the message MAY be confusing (nothing is shown). it will help when someone have this kind of error on bad char in the url. thanks, -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1296) Create ejb3/security submodule

by Anil Saldhana (JIRA)

Create ejb3/security submodule ------------------------------ Key: EJBTHREE-1296 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1296 Project: EJB 3.0 Issue Type: Task Components: Security Affects Versions: AS 5.0.0.Beta4 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: AS 5.0.0.CR1 All the security code should go in here such that the core classes should have one liners rather than security specific code. -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1048) EJB3 JACC migration to Unified MetaModel

by Anil Saldhana (JIRA)

EJB3 JACC migration to Unified MetaModel ---------------------------------------- Key: EJBTHREE-1048 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1048 Project: EJB 3.0 Issue Type: Task Components: Security Reporter: Anil Saldhana EJB2/Web world is aligned with the JaccPolicy service bean in the JBoss MC in AS5. EJB3 JACC layer is not aligned with this. Once the EJB3 metamodel is aligned with the unified meta model, EJB3 JACC layer can get aligned with the top level JaccPolicy concept. JBAS-4506 is the issue for the unification of metadata. -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5362) Move JCA specific login modules into the security project

by Anil Saldhana (JIRA)

Move JCA specific login modules into the security project --------------------------------------------------------- Key: JBAS-5362 URL: http://jira.jboss.com/jira/browse/JBAS-5362 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JCA service, Security Affects Versions: JBossAS-5.0.0.Beta4 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.CR1 -- 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, 3 months

2
2
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 April 2008