Move log services deployer into earlier bootstrap phase
-------------------------------------------------------
Key: JBAS-7683
URL: https://jira.jboss.org/jira/browse/JBAS-7683
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Logging
Reporter: David Lloyd
Assignee: David Lloyd
Fix For: JBossAS-6.0.0.M3
--
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
Try to profile which unguarded log.debug statements are expensive
-----------------------------------------------------------------
Key: JBAS-7693
URL: https://jira.jboss.org/jira/browse/JBAS-7693
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Brian Stansberry
Fix For: JBossAS-6.0.0.M3
See if there is a way other than manual inspection to identify non-spammy log.debug() statements that are expensive.
--
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
AOP does not properly implement latest logging SPI
--------------------------------------------------
Key: JBAS-7437
URL: https://jira.jboss.org/jira/browse/JBAS-7437
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: AOP
Reporter: David Lloyd
Assignee: Kabir Khan
Fix For: JBossAS-6.0.0.M1
AOP can't instantiate the SystemOutLoggerPlugin because it does not implement the 2.2.0 logging SPI. This can result in errors like this:
Failed to initalize plugin: org.jboss.aop.util.logging.SystemOutLoggerPlugin@6719dc16, cause: java.lang.AbstractMethodError
in certain cases.
--
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
Track component updates - 6.0.0.M2
----------------------------------
Key: JBAS-7501
URL: https://jira.jboss.org/jira/browse/JBAS-7501
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Brian Stansberry
Assignee: Jason T. Greene
Priority: Critical
Fix For: JBossAS-6.0.0.M3
--
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
Upgrade MyFaces to 1.2.7
------------------------
Key: JBAS-7529
URL: https://jira.jboss.org/jira/browse/JBAS-7529
Project: JBoss Application Server
Issue Type: Component Upgrade
Security Level: Public (Everyone can see)
Reporter: Brian Stansberry
Assignee: Stan Silvert
Fix For: JBossAS-6.0.0.M2
Decide whether trunk should move to 1.2.7, which is the myfaces version in M1. JBAS-7408 implies it will stay at the 1.1.3 currently in trunk. (I have no opinion either way; am just being thorough about creating JIRAs to resolve all trunk vs. M1 discrepancies).
--
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
Generalize naming factory and remoting lookup
---------------------------------------------
Key: JBAS-4070
URL: http://jira.jboss.com/jira/browse/JBAS-4070
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-5.0.0.Beta2
Reporter: Scott M Stark
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
Issue with JBoss5DeploymentScope and VFS3
-----------------------------------------
Key: JBAS-7783
URL: https://jira.jboss.org/jira/browse/JBAS-7783
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB3
Affects Versions: JBossAS-6.0.0.M3
Reporter: John Bailey
Assignee: John Bailey
Fix For: JBossAS-6.0.0.M3
VFS3 changes the semantics of VirtualFile.getPathName to no longer return a path relative to another root. This caused a failure in JBoss5DeploymentScope as it was assuming the path would be relative.
--
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
Dist Zip file base directory should match name of the zip file
--------------------------------------------------------------
Key: JBAS-7754
URL: https://jira.jboss.org/jira/browse/JBAS-7754
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Paul Gier
Assignee: Paul Gier
Fix For: JBossAS-6.0.0.M3
In the M2 build there is a difference between the name of the base directory inside the zip file, and the name of the zip file itself. This is due to the zip file being renamed before being uploaded to sourceforge for milestone releases.
--
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
TCP can cause memory usage when connecting to a non-JGroups service
-------------------------------------------------------------------
Key: JGRP-1119
URL: https://jira.jboss.org/jira/browse/JGRP-1119
Project: JGroups
Issue Type: Bug
Affects Versions: 2.4.7
Reporter: Dennis Reed
Assignee: Bela Ban
JGroups does not verify that it is connecting to a JGroups service before using the data returned.
If it connects to another service (for example if another service is found in TCPPING's scan), it reads the first four bytes, uses it as the size of a buffer, and blocks until it fills the buffer with data (or the server kills the connection).
The symptoms are the same as JGRP-1116.
--
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
Virtual deployment repositories
-------------------------------
Key: JBPROFILE-2
URL: https://jira.jboss.org/jira/browse/JBPROFILE-2
Project: JBoss Profile Service
Issue Type: Task
Reporter: Emanuel Muckenhuber
Assignee: Emanuel Muckenhuber
Fix For: 1.0.0.Alpha1
Add a notion of virtual deployments and virtual repositories. This is an enhancement to current deployment repositories where deployment are only based on a single virtual file.
--
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