June 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-5592) Container leaks java:comp/TransactionSynchronizationRegistry binding

by Brian Stansberry (JIRA)

Container leaks java:comp/TransactionSynchronizationRegistry binding -------------------------------------------------------------------- Key: JBAS-5592 URL: http://jira.jboss.com/jira/browse/JBAS-5592 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-5.0.0.Beta4 Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 Container.setupEnvironment() adds a binding for java:comp/TransactionSynchronizationRegistry but teardownEnvironment() doesn't clear it. Result is redeploy fails: 2008-06-05 12:25:13,048 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (RMI TCP Connection(20)-127.0.0.1) Error installing to Start: name=jboss.j2ee:jndiName=nextgen_TxSession,service=EJB state=Create mode=Manual requiredState=Installed javax.naming.NameAlreadyBoundException at org.jnp.server.NamingServer.bind(NamingServer.java:144) at org.jnp.interfaces.NamingContext.bind(NamingContext.java:593) at org.jnp.interfaces.NamingContext.bind(NamingContext.java:554) at org.jboss.ejb.Container.setupEnvironment(Container.java:1155) at org.jboss.ejb.Container.startService(Container.java:900) at org.jboss.ejb.SessionContainer.startService(SessionContainer.java:396) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:376) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:322) -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBMAN-14) Change APPLICATION_CLUSTERED to APPLICATION_TRANSIENT

by Scott M Stark (JIRA)

Change APPLICATION_CLUSTERED to APPLICATION_TRANSIENT ----------------------------------------------------- Key: JBMAN-14 URL: http://jira.jboss.com/jira/browse/JBMAN-14 Project: JBoss Managed Issue Type: Feature Request Reporter: Scott M Stark Assigned To: Scott M Stark The clustering notion turned out to be confused. Instead we'll add a transient application notion that can be used by services that want to dynamically add unversioned deployments to a profile. /** The phase of deployment */ public enum DeploymentPhase { /** A deployment loaded during the server bootstrap phase */ BOOTSTRAP, /** An mc/service deployment for a Deployer to be loaded after the BOOTSTRAP phase */ DEPLOYER, /** Any deployment content to be loaded after the DEPLOYER phase */ APPLICATION, /** Any unversioned deployment content to be loaded after the APPLICATION phase */ APPLICATION_TRANSIENT }; This rollsback the JBMAN-13 feature request. -- 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, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-4999) org.jboss.test.cts.test.MDBUnitTestCase

by Shelly McGowan (JIRA)

org.jboss.test.cts.test.MDBUnitTestCase --------------------------------------- Key: JBAS-4999 URL: http://jira.jboss.com/jira/browse/JBAS-4999 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Shelly McGowan Assigned To: Shelly McGowan -- 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, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-5575) SRPPrincipal.equals() throws ClassCastException

by Marcus Moyses (JIRA)

SRPPrincipal.equals() throws ClassCastException ----------------------------------------------- Key: JBAS-5575 URL: http://jira.jboss.com/jira/browse/JBAS-5575 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA Reporter: Marcus Moyses Assigned To: Marcus Moyses Fix For: JBossAS-5.0.0.CR1 The equals method is incorrectly implemented and may cause a ClassCastException to be thrown when objects in a Collection are being compared. -- 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, 1 month

1
4
0 / 0

[JBoss JIRA] Created: (JBBUILD-474) Require maven 2.0.9 for app server build

by Paul Gier (JIRA)

Require maven 2.0.9 for app server build ---------------------------------------- Key: JBBUILD-474 URL: http://jira.jboss.com/jira/browse/JBBUILD-474 Project: JBoss Build System Issue Type: Task Components: Maven Reporter: Paul Gier Assigned To: Paul Gier Fix For: Maven Build - Maint 2008 Require maven 2.0.9 for app server build -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Updated: (JBAS-3051) change jmx console title to display the name of the jboss server configuration with the machine name

by Clive Saldanha (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3051?page=all ] Clive Saldanha updated JBAS-3051: --------------------------------- Attachment: config_in_header.patch > change jmx console title to display the name of the jboss server configuration with the machine name > ---------------------------------------------------------------------------------------------------- > > Key: JBAS-3051 > URL: http://jira.jboss.com/jira/browse/JBAS-3051 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JMX/Web Console > Reporter: Jim Moran > Assigned To: Clive Saldanha > Priority: Trivial > Attachments: config_in_header.patch > > > When running multiple instances of JBoss on one machine the jmx console's title does not distinguish which instance it is for. > It would be easier to distinguish which instance a jmx console was for if the title contained the server config name as well as the machine name. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-3051) change jmx console title to display the name of the jboss server configuration with the machine name

by Clive Saldanha (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3051?page=all ] Clive Saldanha reassigned JBAS-3051: ------------------------------------ Assignee: Clive Saldanha > change jmx console title to display the name of the jboss server configuration with the machine name > ---------------------------------------------------------------------------------------------------- > > Key: JBAS-3051 > URL: http://jira.jboss.com/jira/browse/JBAS-3051 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JMX/Web Console > Reporter: Jim Moran > Assigned To: Clive Saldanha > Priority: Trivial > > When running multiple instances of JBoss on one machine the jmx console's title does not distinguish which instance it is for. > It would be easier to distinguish which instance a jmx console was for if the title contained the server config name as well as the machine name. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4621) error deploying admin-consoles in deploy is a link

by davide pasinato (JIRA)

error deploying admin-consoles in deploy is a link -------------------------------------------------- Key: JBAS-4621 URL: http://jira.jboss.com/jira/browse/JBAS-4621 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Console Affects Versions: JBossAS-4.2.1.GA Environment: linux RH-4 Sun jdk 1.5 jboss 4.2.1 server: all with jbossws-2.0.1 Reporter: davide pasinato Assigned To: Darran Lofthouse Priority: Minor I have a cluster of two jboss 4.2.1 servers. They run on the same machine. For this reason the server B links the directories deploy and lib of the server A when I start server A everything run smoothly. When I start server B I get an exception deploying the administration consoles. Looks like the directory management doesnt like symbolic links. This is the exception I get on server B (the root directory of server B is /var/opt/jboss/stress1b): org.jboss.deployment.DeploymentException: Exception setting attribute javax.management.Attribute@e5f0d2 on mbean jboss.admin:service=DeploymentFileRepository; - nested throwable: (java.lang.IllegalArgumentException: child './deploy/management' should be a child of parent '/var/opt/jboss/stress1b') at org.jboss.system.ServiceConfigurator.setAttribute(ServiceConfigurator.java:698) at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:332) at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:460) at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171) at org.jboss.system.ServiceController.install(ServiceController.java:226) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.install(Unknown Source) at org.jboss.deployment.SARDeployer.create(SARDeployer.java:249) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:508) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.IllegalArgumentException: child './deploy/management' should be a child of parent '/var/opt/jboss/stress1b' at org.jboss.console.manager.DeploymentFileRepository.getFile(DeploymentFileRepository.java:151) at org.jboss.console.manager.DeploymentFileRepository.setBaseDir(DeploymentFileRepository.java:124) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.AttributeDispatcher.invoke(AttributeDispatcher.java:136) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.interceptor.ModelMBeanAttributeInterceptor.invoke(ModelMBeanAttributeInterceptor.java:103) at org.jboss.mx.interceptor.PersistenceInterceptor.invoke(PersistenceInterceptor.java:76) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.setAttribute(AbstractMBeanInvoker.java:461) at org.jboss.mx.server.MBeanServerImpl.setAttribute(MBeanServerImpl.java:608) at org.jboss.system.ServiceConfigurator.setAttribute(ServiceConfigurator.java:694) ... 84 more -- 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, 1 month

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-5163) listThreadDump should print thread dumps in the same format as kill -3

by Galder Zamarreno (JIRA)

listThreadDump should print thread dumps in the same format as kill -3 ---------------------------------------------------------------------- Key: JBAS-5163 URL: http://jira.jboss.com/jira/browse/JBAS-5163 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX, Management services, System service Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA Reporter: Galder Zamarreno Assigned To: Galder Zamarreno There're 4 ways to generate a thread dump. I have taken the output from the same run with different methods: 1.- kill -3. Can be parsed by tools like https://tda.dev.java.net/ (simply, one of the most useful tools I've found out there!). Example: "JBossLifeThread" prio=1 tid=0x0a690cc0 nid=0x1741 in Object.wait() [0x867f2000..0x867f30b0] at java.lang.Object.wait(Native Method) - waiting on <0x9247e200> (a java.lang.Object) at java.lang.Object.wait(Object.java:474) at org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940) - locked <0x9247e200> (a java.lang.Object) 2.- JMX via org.jboss.system.server.ServerInfo.listThreadDump(). Here's some output: Thread: JBossLifeThread : priority:5, demon:false, threadId:58, threadState:WAITING, lockName:java.l ang.Object@10cff6b java.lang.Object.wait(Native Method) java.lang.Object.wait(Object.java:474) org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940) Lock name is different to lock monitor achieved via kill -3. Doesn't looks like it prints previously locked monitors. Cannot be parsed by TDA tools because it's in JBoss specific format. 3.- Thread.getAllStackTraces(). Haven't tested the output from this. What would this print? Couldn't find an MBean that uses/parses the output from this, but I suspect it's the same as method 2, specially since http://jira.jboss.com/jira/browse/JBAS-1448 has already been fixed. 4.- JConsole Threads view: Code: Name: JBossLifeThread State: WAITING on java.lang.Object@10cff6b Total blocked: 0 Total waited: 1 Stack trace: java.lang.Object.wait(Native Method) java.lang.Object.wait(Object.java:474) org.jboss.system.server.ServerImpl$LifeThread.run(ServerImpl.java:940) Seems to print same info as JBoss' ServerInfo. Bottom line: we should try generating thread dumps that look like kill -3 output to make them more readable than in their current format and to benefit from existing tools that can parse standard kill -3 format. -- 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, 1 month

2
33
0 / 0

[JBoss JIRA] Created: (JBAS-5448) Upgrade jboss-ha-client to 1.1.0.GA

by Brian Stansberry (JIRA)

Upgrade jboss-ha-client to 1.1.0.GA ----------------------------------- Key: JBAS-5448 URL: http://jira.jboss.com/jira/browse/JBAS-5448 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 We've moved stuff from the AS aspects module into it; need to release and upgrade once dependencies jboss-remoting-aspects and jboss-aop are GA. -- 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, 1 month

2
4
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 June 2008