November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-6207) update jts install for new lib layout

by Jonathan Halliday (JIRA)

update jts install for new lib layout ------------------------------------- Key: JBAS-6207 URL: https://jira.jboss.org/jira/browse/JBAS-6207 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Transaction Manager (Arjuna) Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: JBossAS-5.0.0.GA Changes to the AS lib dir layout have invalidated the install instructions for JTA->JTS upgrades. Additionally, there is now a greater degree of automation available for this process. Update the install instructions accordingly. -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-385) GenericBeanFactory missing privileged blocks

by Anil Saldhana (JIRA)

GenericBeanFactory missing privileged blocks -------------------------------------------- Key: JBMICROCONT-385 URL: https://jira.jboss.org/jira/browse/JBMICROCONT-385 Project: JBoss Microcontainer Issue Type: Bug Components: Kernel Affects Versions: JBossMC.2.0.0.CR5 Reporter: Anil Saldhana Assignee: Ales Justin Fix For: JBossMC-2.2.0.GA ====================== 10:30:49,885 ERROR [STDERR] access: access denied (java.lang.RuntimePermission getClassLoader) 10:30:49,885 ERROR [STDERR] java.lang.Exception: Stack trace 10:30:49,886 ERROR [STDERR] at java.lang.Thread.dumpStack(Thread.java:1158) 10:30:49,886 ERROR [STDERR] at java.security.AccessControlContext.checkPermission(AccessControlContext.java:253) 10:30:49,886 ERROR [STDERR] at java.security.AccessController.checkPermission(AccessController.java:427) 10:30:49,886 ERROR [STDERR] at java.lang.SecurityManager.checkPermission(SecurityManager.java:532) 10:30:49,886 ERROR [STDERR] at java.lang.Thread.getContextClassLoader(Thread.java:1276) 10:30:49,886 ERROR [STDERR] at org.jboss.kernel.plugins.config.Configurator.getClassLoader(Configurator.java:658) 10:30:49,886 ERROR [STDERR] at org.jboss.beans.metadata.plugins.factory.GenericBeanFactory.createBean(GenericBeanFactory.java:84) 10:30:49,886 ERROR [STDERR] at org.jboss.aop.microcontainer.beans.DelegatingBeanAspectFactory.doCreate(DelegatingBeanAspectFactory.java:132) 10:30:49,886 ERROR [STDERR] at org.jboss.aop.microcontainer.beans.DelegatingBeanAspectFactory.createPerInstance(DelegatingBeanAspectFactory.java:99) 10:30:49,886 ERROR [STDERR] at org.jboss.aop.InstanceAdvisorDelegate.initializeAspects(InstanceAdvisorDelegate.java:95) 10:30:49,886 ERROR [STDERR] at org.jboss.aop.InstanceAdvisorDelegate.initialize(InstanceAdvisorDelegate.java:71) 10:30:49,886 ERROR [STDERR] at org.jboss.ejb3.interceptors.container.ManagedObjectAdvisor.getInstanceAdvisorDelegate(ManagedObjectAdvisor.java:211) 10:30:49,886 ERROR [STDERR] at org.jboss.ejb3.interceptors.container.ManagedObjectAdvisor.getPerInstanceJoinpointAspect(ManagedObjectAdvisor.java:288) ..... 10:30:49,888 ERROR [STDERR] access: domain that failed ProtectionDomain (vfsmemory://3j001-zc92f-fnj1ohos-1-fnj1ou2b-6/ <no signer certificates>) null <no principals> java.security.Permissions@14f94672 ( (java.net.SocketPermission * connect,resolve) (javax.management.MBeanPermission org.jboss.mx.modelmbean.XMBean#*[JMImplementation:type=MBeanRegistry] *) (javax.management.MBeanPermission org.jboss.security.plugins.JaasSecurityManagerService#*[jboss.sec -- 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, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (JBVFS-81) Make FileSystemContext lazy load root

by Ales Justin (JIRA)

Make FileSystemContext lazy load root ------------------------------------- Key: JBVFS-81 URL: https://jira.jboss.org/jira/browse/JBVFS-81 Project: JBoss VFS Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR5 Reporter: Ales Justin Assignee: Ales Justin Fix For: 2.0.0.GA FileSystemContext should lazy load root. So VFSUtils enable/disable options can take effect. -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-6178) JBoss-AS-5.0.x-CompatibilityMatrix Failures

by Shelly McGowan (JIRA)

JBoss-AS-5.0.x-CompatibilityMatrix Failures ------------------------------------------- Key: JBAS-6178 URL: https://jira.jboss.org/jira/browse/JBAS-6178 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Shelly McGowan -- 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, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-6193) JBossCacheManager leaks ReplicationStatistics.TimeStatistic

by Brian Stansberry (JIRA)

JBossCacheManager leaks ReplicationStatistics.TimeStatistic ----------------------------------------------------------- Key: JBAS-6193 URL: https://jira.jboss.org/jira/browse/JBAS-6193 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Affects Versions: JBossAS-5.0.0.CR2 Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-5.0.0.GA If a clustered session has failed over and then the original copy has been passivated, if a remote invalidation message comes in the ReplicationStatistics.TimeStatistic associated with the session isn't removed. This is a slow memory leak. -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBBOOT-3) Change groupId to avoid collision with AS "bootstraP" module

by Andrew Lee Rubinger (JIRA)

Change groupId to avoid collision with AS "bootstraP" module ------------------------------------------------------------ Key: JBBOOT-3 URL: https://jira.jboss.org/jira/browse/JBBOOT-3 Project: JBoss Bootstrap Issue Type: Task Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: 0.1.0 AS "bootstrap" module has POM defining: org.jboss.jbossas:jboss-as-bootstrap ...so the componentized project needs a separate namespace, "org.jboss.bootstrap" -- 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, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-132) DefaultManagedObjectCreator should pass in the attachment name as the MO name

by Scott M Stark (JIRA)

DefaultManagedObjectCreator should pass in the attachment name as the MO name ----------------------------------------------------------------------------- Key: JBDEPLOY-132 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-132 Project: JBoss Deployers Issue Type: Bug Components: deployer Affects Versions: JBDEPLOY-2.0.0.CR5 Reporter: Scott M Stark Assignee: Scott M Stark Fix For: JBDEPLOY-2.0.0.GA The DefaultManagedObjectCreator is currently obtaining the attachment names for a deployment, and then creating the ManagedObjects for them, passing in just the instance, but not the name. This can lead to duplicate attachments in the case of an interface being used as the attachment name as is the case for KernelDeployment. The problem is that the default ManagedObject name is taken from the attachment.getClass().getName(), but this would never be the interface name. -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBBOOT-2) Apply changes from AS "bootstrap" module to Bootstrap Project

by Andrew Lee Rubinger (JIRA)

Apply changes from AS "bootstrap" module to Bootstrap Project ------------------------------------------------------------- Key: JBBOOT-2 URL: https://jira.jboss.org/jira/browse/JBBOOT-2 Project: JBoss Bootstrap Issue Type: Task Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: 0.1.0 Changes have been made into the AS "bootstrap" module since it was broken out into its own project in r80819. As the project is still an (unusued) fork, reconcile with current revision: 81177. -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-6205) Make server.log logging level configurable via system property

by Brian Stansberry (JIRA)

Make server.log logging level configurable via system property -------------------------------------------------------------- Key: JBAS-6205 URL: https://jira.jboss.org/jira/browse/JBAS-6205 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Logging Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-5.0.0.GA Add <param name="Threshold" value="${jboss.server.log.level}"/> to the FILE appender config in jboss-log4j.xml. Log4j performs a system property substitution (see org.apache.log4j.xml.DomConfigurator.subst()). It doesn't seem to support our default value syntax, e.g. {jboss.server.log.level:DEBUG}, but starting the AS w/o setting the system property results in DEBUG logging. If we want a default other than DEBUG (or don't like counting on log4j to use DEBUG if the property isn't set), we can check the system property in Log4jService and set it if not set. -- 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, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1454) Libaio Native Layer would crash on close if it failed opening a file

by Clebert Suconic (JIRA)

Libaio Native Layer would crash on close if it failed opening a file -------------------------------------------------------------------- Key: JBMESSAGING-1454 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1454 Project: JBoss Messaging Issue Type: Bug Affects Versions: 2.0.0 Alpha Reporter: Clebert Suconic Assignee: Clebert Suconic Fix For: 2.0.0 Beta -- 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, 7 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2008