November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-826) RegionManager region map should be ConcurrentReaderHashMap

by Brian Stansberry (JIRA)

RegionManager region map should be ConcurrentReaderHashMap ---------------------------------------------------------- Key: JBCACHE-826 URL: http://jira.jboss.com/jira/browse/JBCACHE-826 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: 2.0.0.GA The regionMap in o.j.c.eviction.RegionManager is a Collections.synchronizedMap. This should be a ConcurrentReaderHashMap. If eviction is used, for every call the EvictionInterceptor makes a call that ends up doing a lookup in this map, so the synchronization becomes a choke point. I already made this change in HEAD along with some refactoring work on eviction configuration. -- 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

19 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAOP-314) Modify JoinPointInfo hierarchy so that we can call resolveAnnotation/resolveClassAnnotation on the underlying advisor

by Kabir Khan (JIRA)

Modify JoinPointInfo hierarchy so that we can call resolveAnnotation/resolveClassAnnotation on the underlying advisor --------------------------------------------------------------------------------------------------------------------- Key: JBAOP-314 URL: http://jira.jboss.com/jira/browse/JBAOP-314 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Flavia Rainone Fix For: 2.0.0.alpha3 This is so that we can use annotation overrides from before/after/throwing advices similar to how it is being done from invocations. See the org.jboss.test.aop.regression.jbaop248annotationoverride for an example of how it is done for invocations/around advice -- 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

19 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-3537) Add a startup switch to configure a multicast port

by Brian Stansberry (JIRA)

Add a startup switch to configure a multicast port -------------------------------------------------- Key: JBAS-3537 URL: http://jira.jboss.com/jira/browse/JBAS-3537 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 Proper cluster isolation with UDP requires use of a different cluster name, different multicast address and different multicast port. (See http://wiki.jboss.org/wiki/Wiki.jsp?page=PromiscuousTraffic for why the latter is important.) The -g and -u switches allow easy configuration of the cluster name and multicast address. But, configuring the port that way wasn't practical, as an AS instance may have many different JChannels. With the JGroups multiplexer, a switch is a possibility, as by default there will only be one JChannel per server instance. (If a user wanted to use more than one JChannel, they would need to manually configure the second one to use a different port.) -- 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

19 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-363) GossipRouter classpath error message is misleading

by Jerry Gauthier (JIRA)

GossipRouter classpath error message is misleading -------------------------------------------------- Key: JGRP-363 URL: http://jira.jboss.com/jira/browse/JGRP-363 Project: JGroups Issue Type: Bug Affects Versions: 2.4 Reporter: Jerry Gauthier Assigned To: Bela Ban Priority: Minor If you start the GossipRouter without concurrent.jar on the classpath, a NoClassDefFoundError exception will occur. However this information is hidden by GossipRouter error handing and the user is presented with the cryptic message: "failed reading the magic number mapping file." I think there are severl ways to improve this situation. 1) Update the GossipRouter example in the JGroups documentation to show what jars need to be on the classpath. 2) Modify the GossipRouter or ClassConfigurator to reveal the underlying problem. Note that this error occurs when you start the GossipRouter per the doc without adding concurrent.jar to the classpath. -- 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

19 years, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-3550) JBAS 4.0.4GA Test suite Error on Java 1.5 - org.jboss.test.classloader.test.CircularityUnitTestCase (testRecursiveLoadMT)

by Vivek Lakshmanan (JIRA)

JBAS 4.0.4GA Test suite Error on Java 1.5 - org.jboss.test.classloader.test.CircularityUnitTestCase (testRecursiveLoadMT) ------------------------------------------------------------------------------------------------------------------------- Key: JBAS-3550 URL: http://jira.jboss.com/jira/browse/JBAS-3550 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-4.0.4.GA Environment: Sun 1.5.0_08, Java VM Version 1.5.0_08-b03 OS: Linux RHEL 4 U3 2.6.9-34.EL Arch: i386 Reporter: Vivek Lakshmanan The above test case seems to produce an error frequently on Sun 1.5 JVM. From a cursory search through JIRA, it seems this could be related to JIRA issue JBAS-760. The stacktrace produced in the test reports follows: javax.management.MBeanException at org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:180) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:163) 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.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:266) 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.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179) 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.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:819) at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:420) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) at sun.rmi.transport.Transport$1.run(Transport.java:153) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:149) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.Exception: Thread1 failed to load HARMIServerImpl_Stub, class=null at org.jboss.test.classloader.circularity.test.RecursiveCCETests.testRecursiveLoadMT(RecursiveCCETests.java:99) at org.jboss.test.classloader.circularity.Starter.testRecursiveLoadMT(Starter.java:154) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) ... 40 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

19 years, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-3548) RMIAdaptorUnitTestCase testMBeanInfoMarshalling failures

by Matt Wringe (JIRA)

RMIAdaptorUnitTestCase testMBeanInfoMarshalling failures -------------------------------------------------------- Key: JBAS-3548 URL: http://jira.jboss.com/jira/browse/JBAS-3548 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-4.0.4.GA Environment: Sun 1.5.0_08 JVM RHEL 4, Linux Kernel 2.6.9 Reporter: Matt Wringe The org.jboss.test.jmx.test.RMIAdaptorUnitTestCase testMBeanInfoMarshalling test fails on the Sun 1.5.0 JVM. >From the test report: "Failed to get MBeanInfo for bean named: jboss.deployment:type=DeploymentScanner,flavor=URL junit.framework.AssertionFailedError: Failed to get MBeanInfo for bean named: jboss.deployment:type=DeploymentScanner,flavor=URL at org.jboss.test.jmx.test.RMIAdaptorUnitTestCase.testMBeanInfoMarshalling(RMIAdaptorUnitTestCase.java:72)" -- 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

19 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-705) Provide monitoring for standalone applications

by Ryan Campbell (JIRA)

Provide monitoring for standalone applications ---------------------------------------------- Key: JBPM-705 URL: http://jira.jboss.com/jira/browse/JBPM-705 Project: JBoss jBPM Issue Type: Feature Request Reporter: Ryan Campbell Assigned To: Tom Baeyens Fix For: jBPM 3.2 Provide jmx interfaces for monitor processes not in a webapp. Or can you point the monitoring webapp at a jBPM datastore? -- 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

19 years, 4 months

3
8
0 / 0

[JBoss JIRA] Created: (JBPM-742) Reimplement JbpmThreadsServlet as a ServletContextListener

by Alejandro Guizar (JIRA)

Reimplement JbpmThreadsServlet as a ServletContextListener ---------------------------------------------------------- Key: JBPM-742 URL: http://jira.jboss.com/jira/browse/JBPM-742 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Affects Versions: jBPM 3.1.1 Reporter: Alejandro Guizar ServletContextListeners are a viable alternative to servlets for management of the jBPM scheduler/command threads. From the Servlet 2.4 spec, section 10.2: >>> Servlet event listeners support event notifications for state changes in the ServletContext, HttpSession and ServletRequest objects. Servlet context listeners are used to **manage resources** or state held at a JVM level for the application. <<< Their intent definitely seems to match our purposes. Further below: >>> There may be multiple listener classes listening to each event type. <<< We could have separate listeners for the scheduler and command executor so that applications may remove either of them in case the related service is not used. Section 10.2.2 provides an example. When the application starts up, the listener creates a connection to the database and stores it in the servlet context. Servlets access the connection from the context as needed. When the application shuts down, the listener closes the connection. Our listener could start the thread and store it in the servlet context, then stop it using the mechanisms provided by JBPM-741. -- 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

19 years, 4 months

4
12
0 / 0

[JBoss JIRA] Created: (JBTM-145) Check PropertyManager raises warning if file not found (or format wrong)

by Mark Little (JIRA)

Check PropertyManager raises warning if file not found (or format wrong) ------------------------------------------------------------------------ Key: JBTM-145 URL: http://jira.jboss.com/jira/browse/JBTM-145 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Little Assigned To: Mark Little Priority: Minor -- 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

19 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBTM-159) Installation script for integrating JBossTransactions/Arjuna TM into JBossAS

by William DeCoste (JIRA)

Installation script for integrating JBossTransactions/Arjuna TM into JBossAS ---------------------------------------------------------------------------- Key: JBTM-159 URL: http://jira.jboss.com/jira/browse/JBTM-159 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: William DeCoste Assigned To: Mark Little requested by Intuit -- 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

19 years, 4 months

2
1
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 November 2006