March 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBAS-3352) Provide better validation of the redelivery parameters on JBossMQ queues and topics

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3352?page=comments#action_12401222 ] Adrian Brock commented on JBAS-3352: ------------------------------------ Questions go in the forums (where you will find it already answered). > Provide better validation of the redelivery parameters on JBossMQ queues and topics > ----------------------------------------------------------------------------------- > > Key: JBAS-3352 > URL: http://jira.jboss.com/jira/browse/JBAS-3352 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMS service > Affects Versions: JBossAS-4.0.4.GA > Reporter: Adrian Brock > Assigned To: Dimitris Andreadis > Fix For: JBossAS-4.2.0.CR1 > > > The JBossMQ Queues and Topics have parameters for redelivery delay and limit. > Both accept any value. There should be validation that errors attempts to use negative values. -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3352) Provide better validation of the redelivery parameters on JBossMQ queues and topics

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3352?page=all ] Adrian Brock updated JBAS-3352: ------------------------------- Comment: was deleted > Provide better validation of the redelivery parameters on JBossMQ queues and topics > ----------------------------------------------------------------------------------- > > Key: JBAS-3352 > URL: http://jira.jboss.com/jira/browse/JBAS-3352 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMS service > Affects Versions: JBossAS-4.0.4.GA > Reporter: Adrian Brock > Assigned To: Dimitris Andreadis > Fix For: JBossAS-4.2.0.CR1 > > > The JBossMQ Queues and Topics have parameters for redelivery delay and limit. > Both accept any value. There should be validation that errors attempts to use negative values. -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3352) Provide better validation of the redelivery parameters on JBossMQ queues and topics

by Jaroslaw Kijanowski (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3352?page=comments#action_12401220 ] Jaroslaw Kijanowski commented on JBAS-3352: ------------------------------------------- The redelivery limit is set to -1 by default. Why is this value not allowed to be set via the jmx-console? > Provide better validation of the redelivery parameters on JBossMQ queues and topics > ----------------------------------------------------------------------------------- > > Key: JBAS-3352 > URL: http://jira.jboss.com/jira/browse/JBAS-3352 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMS service > Affects Versions: JBossAS-4.0.4.GA > Reporter: Adrian Brock > Assigned To: Dimitris Andreadis > Fix For: JBossAS-4.2.0.CR1 > > > The JBossMQ Queues and Topics have parameters for redelivery delay and limit. > Both accept any value. There should be validation that errors attempts to use negative values. -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBREFLECT-19) Move the DependencyBuilder to the kernel project

by Adrian Brock (JIRA)

Move the DependencyBuilder to the kernel project ------------------------------------------------ Key: JBREFLECT-19 URL: http://jira.jboss.com/jira/browse/JBREFLECT-19 Project: JBoss Reflection Issue Type: Task Components: Config Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossReflection.2.0.0.CR1 The DependencyBuilder should really be in the kernel project. It will be moved to there and the AOP callback updated according. -- 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

16 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-248) Include the DependencyBuilder in the kernel project

by Adrian Brock (JIRA)

Include the DependencyBuilder in the kernel project --------------------------------------------------- Key: JBMICROCONT-248 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-248 Project: JBoss MicroContainer Issue Type: Task Components: Dependency Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossMC-2.0.0.CR1 Move the DependencyBuilder from the reflection project and update aop-mc-int accordingly. -- 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

16 years, 2 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBCACHE-70) Make JBossCache an XAResource

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-70?page=all ] Manik Surtani updated JBCACHE-70: --------------------------------- JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131825#4131825 Complexity: High > Make JBossCache an XAResource > ----------------------------- > > Key: JBCACHE-70 > URL: http://jira.jboss.com/jira/browse/JBCACHE-70 > Project: JBoss Cache > Issue Type: Feature Request > Reporter: Bela Ban > Assigned To: Manik Surtani > Fix For: 3.2.0 > > -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-1295) implement JBossCache as an XA resource, rather than standard JTA Synchronizations

by Mircea Markus (JIRA)

implement JBossCache as an XA resource, rather than standard JTA Synchronizations --------------------------------------------------------------------------------- Key: JBCACHE-1295 URL: http://jira.jboss.com/jira/browse/JBCACHE-1295 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mircea Markus Assigned To: Manik Surtani this is a quirk in that we actually finish committing state to the cache in afterCompletion() which is actually incorrect - but since this involves replication informing remote caches to commit their state as well, we can only be sure of this success in afterCompletion(). -- 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

16 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1229) Allow names for queues and topics to contain slashes

by Martin Landua (JIRA)

Allow names for queues and topics to contain slashes ---------------------------------------------------- Key: JBMESSAGING-1229 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1229 Project: JBoss Messaging Issue Type: Feature Request Components: JMS Destination Manager Affects Versions: 1.4.0.SP3 Environment: JBoss Messaging 1.4.0.SP3 on JBoss AS 4.2.2.GA Reporter: Martin Landua Assigned To: Tim Fox Priority: Minor When defining a queue or topic, the JNDI name is automatically derived from the queue/topic's name. It is often convenient for JNDI names to contain slashes to form a queue/topic hierarchy. However, the JMX-name of a queue/topic must not contain slashes because in this case the automatic registration in JNDI fails due to missing parent contexts. Please consider the enclosed patch that would fix this problem. The patch renders everything backward compatible. Index: D:/JBossIDE/workspace_jb42/jboss-messaging-1.4.0.SP3a/src/main/org/jboss/jms/server/DestinationJNDIMapper.java =================================================================== --- D:/JBossIDE/workspace_jb42/jboss-messaging-1.4.0.SP3a/src/main/org/jboss/jms/server/DestinationJNDIMapper.java (revision 3658) +++ D:/JBossIDE/workspace_jb42/jboss-messaging-1.4.0.SP3a/src/main/org/jboss/jms/server/DestinationJNDIMapper.java (working copy) @@ -99,20 +99,18 @@ jndiNameInContext = destination.getName(); jndiName = parentContext + "/" + jndiNameInContext; } - else - { - // TODO more solid parsing + test cases - int sepIndex = jndiName.lastIndexOf('/'); - if (sepIndex == -1) - { - parentContext = ""; - } - else - { - parentContext = jndiName.substring(0, sepIndex); - } - jndiNameInContext = jndiName.substring(sepIndex + 1); - } + + // TODO more solid parsing + test cases + int sepIndex = jndiName.lastIndexOf('/'); + if (sepIndex == -1) + { + parentContext = ""; + } + else + { + parentContext = jndiName.substring(0, sepIndex); + } + jndiNameInContext = jndiName.substring(sepIndex + 1); destination.setJndiName(jndiName); -- 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

16 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1210) Simple messaging test unable to drive CPU utilization better than 20%

by P Duffy (JIRA)

Simple messaging test unable to drive CPU utilization better than 20% --------------------------------------------------------------------- Key: JBMESSAGING-1210 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1210 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.3.0.GA Environment: EAP 4.2 running JBoss Messaging 1.3. Solaris 10 running on Sun T2000 server. Note that T2000 is able to run 32 threads concurrently. We routinely run various tests to confirm AS is fully utilizing available CPU. Reporter: P Duffy Assigned To: Tim Fox After several months, we have been unable to resolve a JBM performance issue. Recent JBoss consultant visit has not helped. We narrowed down our performance test to the following: - several instances of a multi threaded test client sending a simple ObjectMessage into a single AS instance. - a single MDB is deployed in the AS instance. This MDB consumes the message and throws it away (does nothing with it). When this test is run, the AS instance indicates messages are backing up in the Q, yet the clients are unable to drive the CPU past 20% utilization. We've tried the following tuning adjustments: (1) maxSession Annotation on MDB: @ActivationConfigProperty(propertyName = "maxSession", propertyValue = "300") (2) maxSize in server/default/deploy/ejb3-interceptors-aop.xml, on Message Driven Bean: @org.jboss.annotation.ejb.PoolClass (value=org.jboss.ejb3.StrictMaxPool.class, maxSize=300, timeout=10000) (3) maxPoolSize and numAcceptThreads in server/default/deploy/jboss-messaging.sar/remoting-service.xml <attribute name="maxPoolSize" isParam="true">300</attribute> <attribute name="numAcceptThreads" isParam="true">50</attribute> (4) maxPoolSize in ThreadPool in /server/default/conf/jboss-service.xml <attribute name="MaximumPoolSize">800</attribute> Specific documentation re: JBM performance tuning is utterly lacking. We have tried to piece together various shreds of configuration from support cases, consultant comments, etc. to no avail. We need SPECIFIC direction from JBoss re: how to properly configure messaging to fully utilize available CPU. Else identify underlying bugs and resolve same. P.S. We have performed some examination of the JBM 1.3 code. With the huge caveat that we are not expert re: JBM internals, we have identified one location at which 100+ threads appear to be waiting on a single threaded synchronization point. See below. -----Original Message----- From: Mickael Graham (mickaelg) Sent: Monday, December 17, 2007 5:21 PM To: Nick Culpepper (nculpepp) Subject: Re: Thread dump for MDBEcho test Yes. Heaps of threads are blocked on this: at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServe rInvocationHandler.java:105) - waiting to lock <0xfffffffeb17129b8> (a java.lang.Class) This is where the performance problem is. Looking at the JBoss messaging code: public Object invoke(InvocationRequest invocation) throws Throwable { if (trace) { log.trace("invoking " + invocation); } synchronized (JMSServerInvocationHandler.class) { if (closed) { throw new MessagingJMSException("Cannot handle invocation since messaging server is not active (it is either starting up or shutting down)"); } RequestSupport request = (RequestSupport)invocation.getParameter(); if (request instanceof ConnectionFactoryCreateConnectionDelegateRequest) { //Create connection request ConnectionFactoryCreateConnectionDelegateRequest cReq = (ConnectionFactoryCreateConnectionDelegateRequest)request; String remotingSessionId = cReq.getRemotingSessionID(); ServerInvokerCallbackHandler callbackHandler = null; synchronized(callbackHandlers) { callbackHandler = (ServerInvokerCallbackHandler)callbackHandlers.get(remotingSessionId); } if (callbackHandler != null) { log.debug("found calllback handler for remoting session " + Util.guidToString(remotingSessionId)); cReq.setCallbackHandler(callbackHandler); } else { throw new IllegalStateException("Cannot find callback handler " + "for session id " + remotingSessionId); } } return request.serverInvoke(); } } Basically this is for delivering I believe and that looks single threaded. Perhaps once its delivered, it will not be single threaded. -- 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

16 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1211) Investigate Paging on cluster

by Clebert Suconic (JIRA)

Investigate Paging on cluster ----------------------------- Key: JBMESSAGING-1211 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1211 Project: JBoss Messaging Issue Type: Task Reporter: Clebert Suconic Assigned To: Tim Fox -- 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

16 years, 2 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2008