April 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBLOGGING-42) Include version information in stack traces

by Randall Hauch (JIRA)

Include version information in stack traces ------------------------------------------- Key: JBLOGGING-42 URL: https://jira.jboss.org/jira/browse/JBLOGGING-42 Project: JBoss Logging Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Randall Hauch Assignee: David Lloyd Priority: Minor Including JAR and version information for each class in a stack trace provides a lot of useful information. For example (taken from the LogBack documentation): 14:28:48.835 [btpool0-7] INFO c.q.l.demo.prime.PrimeAction - 99 is not a valid value java.lang.Exception: 99 is invalid at ch.qos.logback.demo.prime.PrimeAction.execute(PrimeAction.java:28) [classes/:na] at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) [struts-1.2.9.jar:1.2.9] at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) [struts-1.2.9.jar:1.2.9] at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432) [struts-1.2.9.jar:1.2.9] at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) [servlet-api-2.5-6.1.12.jar:6.1.12] at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502) [jetty-6.1.12.jar:6.1.12] at ch.qos.logback.demo.UserServletFilter.doFilter(UserServletFilter.java:44) [classes/:na] at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1115) [jetty-6.1.12.jar:6.1.12] at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:361) [jetty-6.1.12.jar:6.1.12] at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417) [jetty-6.1.12.jar:6.1.12] at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) [jetty-6.1.12.jar:6.1.12] -- 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

16 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-6292) Documentation should include transitioning from AS 4.2 to AS 5.0

by Bruce Link (JIRA)

Documentation should include transitioning from AS 4.2 to AS 5.0 ---------------------------------------------------------------- Key: JBAS-6292 URL: https://jira.jboss.org/jira/browse/JBAS-6292 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Docs/Installation and Getting Started Guide Affects Versions: JBossAS-5.0.0.GA Environment: Not applicable Reporter: Bruce Link Assignee: Samson Kittoli The installation and getting started guide should have a chapter on transitioning applications from JBoss AS 4.2 to JBoss AS 5.0. Examples discussed might be changes in build class path and configuration documents. For example, when using EJB3, the persistence.xml seems to need to specify a JBoss schema. The release notes is vague in this area. -- 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

16 years, 3 months

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-7750) Update JBoss LogManager to 1.2.0

by David Lloyd (JIRA)

Update JBoss LogManager to 1.2.0 -------------------------------- Key: JBAS-7750 URL: https://jira.jboss.org/jira/browse/JBAS-7750 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Logging Reporter: David Lloyd Assignee: David Lloyd Fix For: JBossAS-6.0.0.M3 Some performance and memory usage improvements, plus a few new & improved features. -- 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

16 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7898) Upgrade JBoss Logging to 3.0.0.Beta2

by David Lloyd (JIRA)

Upgrade JBoss Logging to 3.0.0.Beta2 ------------------------------------ Key: JBAS-7898 URL: https://jira.jboss.org/jira/browse/JBAS-7898 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

16 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-261) Possible concurrency problem: Replicated version id

by Rajesh Chauhan (JIRA)

Possible concurrency problem: Replicated version id --------------------------------------------------- Key: JBCLUSTER-261 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-261 Project: JBoss Clustering Issue Type: Bug Security Level: Public (Everyone can see) Environment: Linux Reporter: Rajesh Chauhan Assignee: Brian Stansberry Hi, I have configured cluster and http session replciation on Jboss but I am getting error called "20:55:12,936 INFO [CacheListener] Possible concurrency problem: Replicated version id 16 matches in-memory version for session 5k130hmp77e26ryJiOddhQ**". I dont know this error is related to session replciation, even I dont know session replciation is working fine or not. As I have checked and it seems failover and session replication is working but I am not sure. Please help me to fix this issue. Hardware Architecture. 1. Cisco Load Balancer 2. Jboss App server(4.2.2) , 1 instace each on 2 server Help will be highly appreciated -- 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

16 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-7896) Remove old LoggingMonitor

by David Lloyd (JIRA)

Remove old LoggingMonitor ------------------------- Key: JBAS-7896 URL: https://jira.jboss.org/jira/browse/JBAS-7896 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Other 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

16 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2470) No/confusing info available on use of "Event Wait" Flow node

by Edward Staub (JIRA)

No/confusing info available on use of "Event Wait" Flow node ------------------------------------------------------------ Key: JBRULES-2470 URL: https://jira.jboss.org/jira/browse/JBRULES-2470 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-docs-flow, drools-eclipse (flow) Affects Versions: 5.1.0.M1, 5.0.1.FINAL Reporter: Edward Staub Assignee: Mark Proctor Use of "Event Wait" (a node type exposed in the Eclipse IDE) is undocumented. In particular, the content of "constraint" is confusing at best. The IDE (in 5.0 - I haven't checked 5.1) has a Java/MVEL pulldown in the constraint editor, but the one example I can find, "ClinicalPathwayX.rf", has a constraint that reads <constraint type="rule" dialect="mvel" >Diagnose( )</constraint> which suggests that it's a rule pattern ("mvel" to the contrary). The compiler blows up with no clues if an expression like "foo==true" is put in the constraint. If imports are entered in the constraint editor, they are discarded. This means that use of the WorkflowProcessInstance, and hence use of process variables, is not accessible as doc'ed in the "Constraints" section of the docs. Apologies in advance if any of this is just noobiness. If anyone wants to post workarounds for all of this, great! If not, I'll cross-post on the user forum in a few days. -- 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

16 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-7830) Remove the "jboss.jmx:type=adaptor, name=Invoker, protocol=http, service=proxyFactory" object from jmx-invoker-service.xml

by David Lloyd (JIRA)

Remove the "jboss.jmx:type=adaptor,name=Invoker,protocol=http,service=proxyFactory" object from jmx-invoker-service.xml ----------------------------------------------------------------------------------------------------------------------- Key: JBAS-7830 URL: https://jira.jboss.org/jira/browse/JBAS-7830 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JMX Reporter: David Lloyd Fix For: JBossAS-6.0.0.M3 ...in server/src/etc/conf/web/jmx-invoker-service.xml to be exact -- 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

16 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-7891) Fix the NPE in EJB3DeploymentDeployer introduced in EJB3.1 singleton implementation which causes testcase failures

by jaikiran pai (JIRA)

Fix the NPE in EJB3DeploymentDeployer introduced in EJB3.1 singleton implementation which causes testcase failures -------------------------------------------------------------------------------------------------------------------- Key: JBAS-7891 URL: https://jira.jboss.org/jira/browse/JBAS-7891 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Reporter: jaikiran pai Assignee: jaikiran pai Fix For: JBossAS-6.0.0.M3 2010-04-05 03:07:48,034 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (RMI TCP Connection(4)-127.0.0.1) Error installing to PostClassLoader: name=vfs:///qa/services/hudson/hudson_workspace/workspace/JBoss-AS-6.0.x/JBossAS_6_0/testsuite/output/lib/log4j113-ejb.jar state=ClassLoader mode=Manual requiredState=PostClassLoader: org.jboss.deployers.spi.DeploymentException: Error during deploy: vfs:///qa/services/hudson/hudson_workspace/workspace/JBoss-AS-6.0.x/JBossAS_6_0/testsuite/output/lib/log4j113-ejb.jar at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:185) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1857) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1575) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1516) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:377) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2042) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1081) at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1320) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1244) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1137) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:937) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:652) at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:2008) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1101) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:370) 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:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:271) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:670) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1426) at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1264) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1359) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788) at sun.reflect.GeneratedMethodAccessor289.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305) at sun.rmi.transport.Transport$1.run(Transport.java:159) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:155) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.NullPointerException at org.jboss.ejb3.singleton.deployer.EJB3DeploymentDeployer.deploy(EJB3DeploymentDeployer.java:88) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) ... 42 more -- 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

16 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-7892) Fix the INFO level logging in HornetQ deployers

by jaikiran pai (JIRA)

Fix the INFO level logging in HornetQ deployers ----------------------------------------------- Key: JBAS-7892 URL: https://jira.jboss.org/jira/browse/JBAS-7892 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JMS (HornetQ) Reporter: jaikiran pai Assignee: jaikiran pai Fix For: JBossAS-6.0.0.M3 On server startup HornetQ deployers log this at INFO level: 16:17:57,602 INFO [HornetQConfigParserDeployer] Main Config = org.hornetq.core.config.impl.ConfigurationImpl@1962ecd 16:17:57,659 INFO [HornetQJMSParserDeployer] Config = org.hornetq.jms.server.config.impl.JMSConfigurationImpl@fd0e71 Not much useful at INFO level. -- 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

16 years, 3 months

1
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 2010