[jBPM] New message: "Re: Strategy for assigning subprocess execution ID"
by Sasa Mitrovic
User development,
A new message was posted in the thread "Strategy for assigning subprocess execution ID":
http://community.jboss.org/message/530095#530095
Author : Sasa Mitrovic
Profile : http://community.jboss.org/people/letstalk
Message:
--------------------------------------------------------------
Hi Al, I've tried getId() first but it didn't work for my case where subprocess reached timer activity. In this case processInstance.getParent().getId() returns the parent execution which is the execution of the subprocess and it is in the inactive-scope state. This execution, in turn, returns null for parent execution id which is strange, isn't it?
Besides, that's only a part of the problem, my goal is to have all child execution reference the original order id and your second suggestion might just do the trick. I'll try that, thanks a lot!
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/530095#530095
16 years, 1 month
[Performance Tuning] New message: "HTTP threads waiting on JIOEndpoint$Worker.await"
by Jason Smith
User development,
A new message was posted in the thread "HTTP threads waiting on JIOEndpoint$Worker.await":
http://community.jboss.org/message/530090#530090
Author : Jason Smith
Profile : http://community.jboss.org/people/jsmith085
Message:
--------------------------------------------------------------
*I am doing some load testing using a http playback tool and simulating 150 users, with 40 second think times between transactions. I'm on Red Hat Enterprise 5.2 on Wintel, on VMWare !*
*My load test response times have become worse and worse as I've added the last 50 or so users and I'm curious about the following.*
*A thread dump of one of our running JBoss AS 5.1 app server shows large numbers of our HTTP connector threads WAITING as follows:*
*Thread: http-0.0.0.0-8180-1* : priority:5, demon:true, threadId:129, threadState:WAITING
> *- waiting on <0x1d30afa> (a org.apache.tomcat.util.net.JIoEndpoint$Worker)
> java.lang.Object.wait(Native Method)
> java.lang.Object.wait(Object.java:485)
> org.apache.tomcat.util.net.JIoEndpoint$Worker.await(JIoEndpoint.java:416)
> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:442)
> java.lang.Thread.run(Thread.java:619)
> *
* *
*Is this normal/expected? *
*In a different post elsewhere I saw what appeared to be the code for the await method of the JIOEndpoint$Worker class and it appeared to be trying to obtain a socket. This led to other post talking about file descriptors (lack thereof) potentially being an issue....how can I definitely confirm if they are an issue?*
*If threads waiting in this method is not normal then what other causes could account for it?*
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/530090#530090
16 years, 1 month
[JBoss Messaging] New message: "Error configuring DLQ and ExpiryQueue for distributed destination"
by Steve Joy
User development,
A new message was posted in the thread "Error configuring DLQ and ExpiryQueue for distributed destination":
http://community.jboss.org/message/530089#530089
Author : Steve Joy
Profile : http://community.jboss.org/people/skr989
Message:
--------------------------------------------------------------
Can somebody help me with the DLQ and ExpiryQueue for distributed destinations? I tried with the below myqueue-service.xml.
<?xml version="1.0" encoding="UTF-8"?>
<!--
Messaging Destinations deployment descriptor.
$Id: destinations-service.xml 85945 2009-03-16 19:45:12Z mailto:dimitris@jboss.org $
-->
<server>
<mbean code="org.jboss.jms.server.destination.QueueService"
name="jboss.messaging.destination:service=Queue,name=myErrorQueue"
xmbean-dd="xmdesc/Queue-xmbean.xml">
<depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
<depends>jboss.messaging:service=PostOffice</depends>
<attribute name="Clustered">true</attribute>
</mbean>
<mbean code="org.jboss.jms.server.destination.QueueService"
name="jboss.messaging.destination:service=Queue,name=myExpiryQueue"
xmbean-dd="xmdesc/Queue-xmbean.xml">
<depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
<depends>jboss.messaging:service=PostOffice</depends>
<attribute name="Clustered">true</attribute>
</mbean>
<mbean code="org.jboss.jms.server.destination.QueueService"
name="jboss.messaging.destination:service=Queue,name=testDistributedQueue"
xmbean-dd="xmdesc/Queue-xmbean.xml">
<depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
<depends>jboss.messaging:service=PostOffice</depends>
<attribute name="Clustered">true</attribute>
<attribute name="DLQ">jboss.messaging.destination:service=Queue,name=myErrorQueue</attribute>
<attribute name="ExpiryQueue">jboss.messaging.destination:service=Queue,name=myExpiryQueue</attribute>
</mbean>
</server>
When I start node1 of the Cluster, it starts fine. But when I start node2, I get the below error.
DEPLOYMENTS IN ERROR:
Deployment "jboss.messaging.destination:name=myExpiryQueue,service=Queue" is in error due to the following reason(s): java.lang.IllegalArgumentException: Queue myExpiryQueue is already deployed as clustered = false so cannot redeploy as clustered=true . You must delete the destination first before redeploying
Deployment "jboss.messaging.destination:name=myErrorQueue,service=Queue" is in error due to the following reason(s): java.lang.IllegalArgumentException: Queue myErrorQueue is already deployed as clustered = false so cannot redeploy as clustered=true . You must delete the destination first before redeploying
Any help on this is highly appreciated.
Thanks,
Steve
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/530089#530089
16 years, 1 month
[Performance Tuning] New message: "Re: Tuning the MaxThreadPool"
by Jason Smith
User development,
A new message was posted in the thread "Tuning the MaxThreadPool":
http://community.jboss.org/message/530088#530088
Author : Jason Smith
Profile : http://community.jboss.org/people/jsmith085
Message:
--------------------------------------------------------------
OK. Thanks. Peter. You've answered what I think I was really trying to get clear in my head. I thought that the two pools,
1. the HTTP connector thread pool (governed by the MinThreads and MaxThreads parms on the connector in the server.xml in the ../default/jbossweb folder), and
2. the JBoss system thread pool (governed by the MaximumPoolSize attribute of the jboss.system:service=ThreadPool mbean definition defined in the jboss-service.xml file in the ../default/conf folder)
were related. Reason being, I came across the JBoss Tuning tips at:
http://www.mastertheboss.com/en/jboss-application-server/113-jboss-perfor...
and there was a comment relating to the HTTP conenctory thread settings that said:
"if you increase the maxThreads count you need to raise your JBoss Thread pool accordingly". I though that the thread pool being refered to here was the JBoss System Threads pool and in my mind this created a dependency between the two.
I guess the other question I'm asking is:
What are all the JBoss thread pools that come into play in order to support the needs of the variety of mainstream applications today (assuming its safe to frame the question this way!).
The ones I've learnt about so far are:
1.JBoss System Threads, attribute "MaximumPoolSize", defined in mBean name="jboss.system:service=ThreadPool" of $+server_root+/conf/jboss-service.xml
2.HTTP1.1 Connector Thread Pool, attribute "MaxThreads", defined in the <Server><Service><Connector> section of $+server_root+/deploy/jbossweb.sar/server.xml
What other pools are there? For each pool that comes to mind, what is the:
thread pool name
defined how/where?
what type of processing/tasks it limits/controls ?
relationship with other pools?
Any and all comments welcome.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/530088#530088
16 years, 1 month