java:comp/env isn't available for SessionSynchronization callbacks
------------------------------------------------------------------
Key: JBAS-6553
URL: https://jira.jboss.org/jira/browse/JBAS-6553
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB2
Reporter: Carlo de Wolf
Assignee: Alexey Loubyansky
Priority: Critical
Fix For: JBossAS-5.1.0.CR1
--
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
Remove org.jboss.test.ejb3.servlet.unit.HttpUtils
-------------------------------------------------
Key: JBAS-6556
URL: https://jira.jboss.org/jira/browse/JBAS-6556
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Test Suite
Reporter: Carlo de Wolf
Assignee: Carlo de Wolf
Priority: Critical
Fix For: JBossAS-5.1.0.Beta1, JBossAS-6.0.0.Alpha1
org.jboss.test.ejb3.servlet.unit.HttpUtils is an old fork of org.jboss.test.util.web.HttpUtils which has localhost hardcoded.
Remote it in favour of the second class.
--
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
Reenable Tomcat SSL tests
-------------------------
Key: JBAS-6940
URL: https://jira.jboss.org/jira/browse/JBAS-6940
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Test Suite, Web (Tomcat) service
Reporter: Anil Saldhana
Assignee: Anil Saldhana
Priority: Critical
Fix For: JBossAS-5.1.0.GA, JBossAS-6.0.0.Alpha1
I feel very miserable that this target has been commented out for close to 3 years now.
http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/trunk/testsuite/build....
I had a need to test something and found that this target was commented out. Things had broken down, functionalitywise.
I have it working and will re-enable. :)
--
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
boot.log should print command line options ($JAVA_OPTS) by default
------------------------------------------------------------------
Key: JBAS-5240
URL: http://jira.jboss.com/jira/browse/JBAS-5240
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Other
Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Priority: Minor
To help remote support, AS should by default log command line options
within boot.log as explained in " Logging command line options in boot.log"
section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging
Thoughts?
--
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
Upgrade to JBossXACML 2.0.3.CR1
-------------------------------
Key: JBAS-6565
URL: https://jira.jboss.org/jira/browse/JBAS-6565
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Security
Reporter: Anil Saldhana
Assignee: Anil Saldhana
Fix For: JBossAS-6.0.0.Alpha1
Currently, jboss-sunxacml.jar is packaged inside jbossxacml.jar.
Hence the dependencies org.jboss.security:jboss-xacml and org.jboss.security:jboss-sunxacml need to be consolidated into org.jboss.security:jbossxacml as part of this upgrade.
--
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 JBoss Security 2.0.2.SP7
--------------------------------
Key: JBAS-6566
URL: https://jira.jboss.org/jira/browse/JBAS-6566
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Security
Reporter: Anil Saldhana
Assignee: Stefan Guilhen
Fix For: JBossAS-6.0.0.Alpha1
--
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
VFS cache should handle main context roots better
-------------------------------------------------
Key: JBAS-6373
URL: https://jira.jboss.org/jira/browse/JBAS-6373
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: VFS
Affects Versions: JBossAS-5.0.0.GA
Reporter: Ales Justin
Assignee: Ales Justin
Currently we use timed VFS cache,
which results in plague of temp jar files once the cache expires.
We should control the main VFS contexts better.
--
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
Define initial persistent format of the profile repository
----------------------------------------------------------
Key: JBAS-3768
URL: http://jira.jboss.com/jira/browse/JBAS-3768
Project: JBoss Application Server
Issue Type: Sub-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.Beta
We need to define the initial profile repository format with consideration of future migrations, jsr88, admin tools.
--
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
DataSourceDeploymentMetaData doesnt create property "isSameRMOverrideValue"
---------------------------------------------------------------------------
Key: JBAS-6848
URL: https://jira.jboss.org/jira/browse/JBAS-6848
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.1.GA
Reporter: seboonet
Assignee: Ales Justin
Priority: Blocker
org.jboss.resource.metadata.mcf.DataSourceDeploymentMetaData.getManagedConnectionFactoryProperties() should create Property named "isSameRMOverrideValue".
The absence of this property results in an illegal work of XAManagedConnectionFactory and running 2PC protocol.
--
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