December 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-5084) Add the transaction active check to the jms resource adapter

by Adrian Brock (JIRA)

Add the transaction active check to the jms resource adapter ------------------------------------------------------------ Key: JBAS-5084 URL: http://jira.jboss.com/jira/browse/JBAS-5084 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.2.2.GA Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA Add the new transaction active to the jdbc resource adapter. -- 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, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-5080) Need to check transaction status on SQL operations

by Adrian Brock (JIRA)

Need to check transaction status on SQL operations -------------------------------------------------- Key: JBAS-5080 URL: http://jira.jboss.com/jira/browse/JBAS-5080 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.2.2.GA Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA In 4.2.x the transaction timeout rollsback the transaction rather than marking it rollback only. This means that for the local transaction datasource the connection has effectively moved onto the next transaction. Actual code: Connection c = datasource.getConnection(); // tx timeout here Statement s = createStatement(); s.executeUpdate(); // should not work Actual Code executed in 4.0.x Connection c = pool.getConnection(); // tx timeout here transaction.setRollbackOnly(); Statement s = createStatement(); s.executeUpdate(); tx.rollback(); // Rollsback the update Actual Code executed in 4.2.x Connection c = pool.getConnection(); // tx timeout here transaction.rollback(); Statement s = createStatement(); s.executeUpdate(); // happens "in the next local transaction" -- 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, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-5082) Add a transaction status interface for the connection manager and implement it in TxConnectionManager

by Adrian Brock (JIRA)

Add a transaction status interface for the connection manager and implement it in TxConnectionManager ------------------------------------------------------------------------------------------------------ Key: JBAS-5082 URL: http://jira.jboss.com/jira/browse/JBAS-5082 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.2.2.GA Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA The ConnectionManager needs a transaction status interface such that resource adapters can check the active status of the transaction assoication. This should be similar to the TransactionTimeoutConfiguration where only the TxConnectionManager implements it. If the transaction is not active then an exception should be thrown. The resource adapters (jdbc and jms) need to add a check for transation active to their checkState methods). -- 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, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-479) Wizard for autopopulating a decision table

by Michael Neale (JIRA)

Wizard for autopopulating a decision table ------------------------------------------ Key: JBRULES-479 URL: http://jira.jboss.com/jira/browse/JBRULES-479 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Decision tables Reporter: Michael Neale Assigned To: Mark Proctor Priority: Minor This could be done quite easily by a contributor. Have a wizard (in the IDE) which takes information regarding the facts to be used, fields, actions (and the number of each) and generates a decision table based on that info capture (ie populates it). -- 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, 10 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, 10 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, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBREM-753) Assure version compatibility with earlier versions of Remoting

by Ron Sigal (JIRA)

Assure version compatibility with earlier versions of Remoting -------------------------------------------------------------- Key: JBREM-753 URL: http://jira.jboss.com/jira/browse/JBREM-753 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.4.0.CR1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Priority: Critical Fix For: 2.4.0.CR1 (Pinto) Each version of Remoting must be API and wire compatible with earlier versions, at least as far back as 1.4.3.GA, which is used in JBossAS 4.0.4.GA and 4.0.5.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

16 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBREM-703) allow for total configuration of socket via socket invoker

by Tom Elrod (JIRA)

allow for total configuration of socket via socket invoker ---------------------------------------------------------- Key: JBREM-703 URL: http://jira.jboss.com/jira/browse/JBREM-703 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Components: transport Affects Versions: 2.2.0.Alpha7 Reporter: Tom Elrod Assigned To: Tom Elrod Priority: Minor Fix For: 2.2.0.Beta2 (Bluto) Currently remoting does not expose all the configuration properties for a socket for the socket invokers. Should just allow configuration of everything allowed by the jdk api for a socket to be allowed via remtoing (i.e. sendBufferSize and receiveBufferSize) -- 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, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (JBREM-739) Fix java serialization leak.

by Ron Sigal (JIRA)

Fix java serialization leak. ---------------------------- Key: JBREM-739 URL: http://jira.jboss.com/jira/browse/JBREM-739 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.0.SP2 Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.SP2 Bug was reported in JBAS-4359. -- 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, 10 months

1
6
0 / 0

[JBoss JIRA] Created: (JBREM-809) Verify that the behavior of the HTTPUnMarshaller re stripping CR and LF characters is correct

by Tom Fennelly (JIRA)

Verify that the behavior of the HTTPUnMarshaller re stripping CR and LF characters is correct --------------------------------------------------------------------------------------------- Key: JBREM-809 URL: http://jira.jboss.com/jira/browse/JBREM-809 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: marshall Affects Versions: 2.2.2.GA Reporter: Tom Fennelly Assigned To: Trustin Lee At the moment, the HTTPUnMarshaller uses a BufferedReader to read a HTTP char stream. This causes it to modify the message payload by removing the CR and LF characters. This causes a problem for us on the ESB because it means that signature checks fail on signed SOAP messages since the sig was generated from the message containing the CR and LF chars. It's even worse than that... it actually corrupts the signature within the message because the canonical form of the sig contains CRLF chars. We got around this in the ESB (in the short term) by setting our own modified version of the HTTPUnMarshaller - one that doesn't use a BufferedReader. -- 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, 10 months

2
11
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2007