Priyadarshan, Ashok
2007-07-25 14:15:40 UTC
Hello:
I need to improve performance with Log4j with Open JMS.
I am using the standard log4j JMS appender publishing to a Que.
Are there any options to to add to OpenJMS and or Log4j to improve
performace.
Thanks
-----Original Message-----
From: openjms-developer-***@lists.sourceforge.net
[mailto:openjms-developer-***@lists.sourceforge.net] On Behalf Of
openjms-developer-***@lists.sourceforge.net
Sent: Tuesday, July 17, 2007 3:09 PM
To: openjms-***@lists.sourceforge.net
Subject: openjms-developer Digest, Vol 11, Issue 2
Send openjms-developer mailing list submissions to
openjms-***@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/openjms-developer
or, via email, send a message with subject or body 'help' to
openjms-developer-***@lists.sourceforge.net
You can reach the person managing the list at
openjms-developer-***@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of openjms-developer digest..."
Today's Topics:
1. [ openjms-Bugs-1751688 ] Transaction in progress causes
server unresponsive on topic (SourceForge.net)
----------------------------------------------------------------------
Message: 1
Date: Wed, 11 Jul 2007 00:53:56 -0700
From: "SourceForge.net" <***@sourceforge.net>
Subject: [openjms-developer] [ openjms-Bugs-1751688 ] Transaction in
progress causes server unresponsive on topic
To: ***@sourceforge.net
Message-ID: <E1I8X1I-0003TV-***@sc8-sf-web23.sourceforge.net>
Content-Type: text/plain; charset="UTF-8"
Bugs item #1751688, was opened at 2007-07-11 09:53
Message generated for change (Tracker Item Submitted) made by Item
Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1751688&gro
up_id=54559
Please note that this message will contain a full copy of the comment
thread,
including the initial issue submission, for this request,
not just the latest update.
Category: server
Group: v0.7.7-beta-1
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Peter De Leuze (stardust)
Assigned to: Nobody/Anonymous (nobody)
Summary: Transaction in progress causes server unresponsive on topic
Initial Comment:
There is a problem that occurs frequently but randomly, but I cannot
reproduce it.
This is the scenario:
1) two jms clients connect to the same server, both on a different topic
A and B.
Everything works fine.
2) two/more additional clients are started and connect to those topics.
3) at one point, "somewhere" a transaction error is caused, and causes
all connected clients to the same topic to receive jms messages: the
clients send it to server topic, but no messages are propagated.
Other connected clients on other topics work fine !
In the serverlog the following logstate is printed:
--------------
2007-07-11 09:29:10,234 ERROR [Scheduler-Worker-5] - Transaction in
progress, allocated at
java.lang.Exception
at java.lang.Throwable.<init>(Throwable.java:181)
at java.lang.Exception.<init>(Exception.java:29)
at
org.exolab.jms.persistence.DatabaseService$State.<init>(DatabaseService.
java:321)
at
org.exolab.jms.persistence.DatabaseService.begin(DatabaseService.java:15
2)
at
org.exolab.jms.server.SessionConsumer.send(SessionConsumer.java:550)
at
org.exolab.jms.server.SessionConsumer.dispatch(SessionConsumer.java:498)
at
org.exolab.jms.server.SessionConsumer.access$000(SessionConsumer.java:78
)
at
org.exolab.jms.server.SessionConsumer$1.run(SessionConsumer.java:155)
at org.exolab.jms.scheduler.SerialTask.run(SerialTask.java:164)
at
org.exolab.jms.common.threads.ThreadPool$NotifyingRunnable.run(ThreadPoo
l.java:211)
at
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown
Source)
at java.lang.Thread.run(Thread.java:595)
2007-07-11 09:29:10,315 ERROR [Scheduler-Worker-5] - Failed to release
unsent message
org.exolab.jms.persistence.PersistenceException: Transaction already in
progress
at java.lang.Throwable.<init>(Throwable.java:196)
at java.lang.Exception.<init>(Exception.java:41)
at
org.exolab.jms.service.ServiceException.<init>(ServiceException.java:101
)
at
org.exolab.jms.service.ServiceException.<init>(ServiceException.java:80)
at
org.exolab.jms.persistence.PersistenceException.<init>(PersistenceExcept
ion.java:71)
at
org.exolab.jms.persistence.DatabaseService.begin(DatabaseService.java:15
9)
at
org.exolab.jms.server.SessionConsumer.send(SessionConsumer.java:594)
at
org.exolab.jms.server.SessionConsumer.dispatch(SessionConsumer.java:498)
at
org.exolab.jms.server.SessionConsumer.access$000(SessionConsumer.java:78
)
at
org.exolab.jms.server.SessionConsumer$1.run(SessionConsumer.java:155)
at org.exolab.jms.scheduler.SerialTask.run(SerialTask.java:164)
at
org.exolab.jms.common.threads.ThreadPool$NotifyingRunnable.run(ThreadPoo
l.java:211)
at
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown
Source)
at java.lang.Thread.run(Thread.java:595)
--------------------
4)When new clients connect/disconnect, this does not change the
unresponsiveness on the "faulty" topic.
Only when the first connected client disconnects, then suddenly the
server becomes again responsive on that topic !!!
So, it seems that this transaction error causes the whole topic to be
blocked, until the faulty client disconnects.
I think it is better that it may never occur that a server just stops
(partially) working because of a client error... The topic should stay
responsive.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1751688&gro
up_id=54559
------------------------------
------------------------------------------------------------------------
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
------------------------------
_______________________________________________
openjms-developer mailing list
openjms-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openjms-developer
End of openjms-developer Digest, Vol 11, Issue 2
************************************************
I need to improve performance with Log4j with Open JMS.
I am using the standard log4j JMS appender publishing to a Que.
Are there any options to to add to OpenJMS and or Log4j to improve
performace.
Thanks
-----Original Message-----
From: openjms-developer-***@lists.sourceforge.net
[mailto:openjms-developer-***@lists.sourceforge.net] On Behalf Of
openjms-developer-***@lists.sourceforge.net
Sent: Tuesday, July 17, 2007 3:09 PM
To: openjms-***@lists.sourceforge.net
Subject: openjms-developer Digest, Vol 11, Issue 2
Send openjms-developer mailing list submissions to
openjms-***@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/openjms-developer
or, via email, send a message with subject or body 'help' to
openjms-developer-***@lists.sourceforge.net
You can reach the person managing the list at
openjms-developer-***@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of openjms-developer digest..."
Today's Topics:
1. [ openjms-Bugs-1751688 ] Transaction in progress causes
server unresponsive on topic (SourceForge.net)
----------------------------------------------------------------------
Message: 1
Date: Wed, 11 Jul 2007 00:53:56 -0700
From: "SourceForge.net" <***@sourceforge.net>
Subject: [openjms-developer] [ openjms-Bugs-1751688 ] Transaction in
progress causes server unresponsive on topic
To: ***@sourceforge.net
Message-ID: <E1I8X1I-0003TV-***@sc8-sf-web23.sourceforge.net>
Content-Type: text/plain; charset="UTF-8"
Bugs item #1751688, was opened at 2007-07-11 09:53
Message generated for change (Tracker Item Submitted) made by Item
Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1751688&gro
up_id=54559
Please note that this message will contain a full copy of the comment
thread,
including the initial issue submission, for this request,
not just the latest update.
Category: server
Group: v0.7.7-beta-1
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Peter De Leuze (stardust)
Assigned to: Nobody/Anonymous (nobody)
Summary: Transaction in progress causes server unresponsive on topic
Initial Comment:
There is a problem that occurs frequently but randomly, but I cannot
reproduce it.
This is the scenario:
1) two jms clients connect to the same server, both on a different topic
A and B.
Everything works fine.
2) two/more additional clients are started and connect to those topics.
3) at one point, "somewhere" a transaction error is caused, and causes
all connected clients to the same topic to receive jms messages: the
clients send it to server topic, but no messages are propagated.
Other connected clients on other topics work fine !
In the serverlog the following logstate is printed:
--------------
2007-07-11 09:29:10,234 ERROR [Scheduler-Worker-5] - Transaction in
progress, allocated at
java.lang.Exception
at java.lang.Throwable.<init>(Throwable.java:181)
at java.lang.Exception.<init>(Exception.java:29)
at
org.exolab.jms.persistence.DatabaseService$State.<init>(DatabaseService.
java:321)
at
org.exolab.jms.persistence.DatabaseService.begin(DatabaseService.java:15
2)
at
org.exolab.jms.server.SessionConsumer.send(SessionConsumer.java:550)
at
org.exolab.jms.server.SessionConsumer.dispatch(SessionConsumer.java:498)
at
org.exolab.jms.server.SessionConsumer.access$000(SessionConsumer.java:78
)
at
org.exolab.jms.server.SessionConsumer$1.run(SessionConsumer.java:155)
at org.exolab.jms.scheduler.SerialTask.run(SerialTask.java:164)
at
org.exolab.jms.common.threads.ThreadPool$NotifyingRunnable.run(ThreadPoo
l.java:211)
at
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown
Source)
at java.lang.Thread.run(Thread.java:595)
2007-07-11 09:29:10,315 ERROR [Scheduler-Worker-5] - Failed to release
unsent message
org.exolab.jms.persistence.PersistenceException: Transaction already in
progress
at java.lang.Throwable.<init>(Throwable.java:196)
at java.lang.Exception.<init>(Exception.java:41)
at
org.exolab.jms.service.ServiceException.<init>(ServiceException.java:101
)
at
org.exolab.jms.service.ServiceException.<init>(ServiceException.java:80)
at
org.exolab.jms.persistence.PersistenceException.<init>(PersistenceExcept
ion.java:71)
at
org.exolab.jms.persistence.DatabaseService.begin(DatabaseService.java:15
9)
at
org.exolab.jms.server.SessionConsumer.send(SessionConsumer.java:594)
at
org.exolab.jms.server.SessionConsumer.dispatch(SessionConsumer.java:498)
at
org.exolab.jms.server.SessionConsumer.access$000(SessionConsumer.java:78
)
at
org.exolab.jms.server.SessionConsumer$1.run(SessionConsumer.java:155)
at org.exolab.jms.scheduler.SerialTask.run(SerialTask.java:164)
at
org.exolab.jms.common.threads.ThreadPool$NotifyingRunnable.run(ThreadPoo
l.java:211)
at
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown
Source)
at java.lang.Thread.run(Thread.java:595)
--------------------
4)When new clients connect/disconnect, this does not change the
unresponsiveness on the "faulty" topic.
Only when the first connected client disconnects, then suddenly the
server becomes again responsive on that topic !!!
So, it seems that this transaction error causes the whole topic to be
blocked, until the faulty client disconnects.
I think it is better that it may never occur that a server just stops
(partially) working because of a client error... The topic should stay
responsive.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1751688&gro
up_id=54559
------------------------------
------------------------------------------------------------------------
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
------------------------------
_______________________________________________
openjms-developer mailing list
openjms-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openjms-developer
End of openjms-developer Digest, Vol 11, Issue 2
************************************************