JRUN thread number

Hello,
I was looking for logs and the field "threadId".
I've found that "JRPP-X" is for JRUN thread and the X is a
number.
My X increases, about +200 per day for 60k connections... So
I'm wondering if it means that there are memory/thread leak or
something like that...
Thanks,
Y.

Your threads will fall down to the minhandler count on a
server that is idle or lightly used. So, threads will go away. In
short, the thread ID incrementing does not show any negative
behavior by itself.

Similar Messages

Maximum number of running JRun threads - where to set?

Hi,
I have been looking to increase the maximum number of JRun threads on CF8 Standard on Linux. However, changing jrun.xml (<attribute name="activeHandlerThreads">100</attribute> in the JRunProxyService section) did nothing after restarting CF and Apache and I have not been able to find it anywhere in the Administrator. Anybody have any ideas or have I missed something really obvious?
CF administrator does not list the value anywhere apart from the settings summary.
Thanks
Meint

Ok, I changed the WebService setting and it now shows the new value in CF Administrator. However, it does have me wondering if this is possibly a bug in CF Administrator? Does it always show the JRun threads against the internal web server, even if you are using an external web server like Apache? Reason for asking is that the relevant sections against the JrunProxyService section clearly state that this is for an external web server and the WebService section states it is for the internal web swerver? Bit confused now but have got it working as expected. Is there another way of finding out the JRun thread value other than the CF Administrator?
Regards
Meint

JRun Thread Pool Issue

I'm running CF 9.0.1 on Ubuntu on an "Medium" Amazon EC2 instance. CF has been crashing intermittently (several times per day). At such times, running top gets me this (or something similar):
PID
USER
PR
NI
VIRT
RES
SHR
S
%CPU
%MEM
TIME+COMMAND
15855
wwwrun
20
0
1762m
730m
20m
S
99.3
19.4
13:22.96 coldfusion9
So, it's obviously consuming most of the server resources. The following error has been showing up in my cfserver.log in the leadup to each crash:
java.lang.RuntimeException: Request timed out waiting for an available thread to run. You may want to consider increasing the number of active threads in the thread pool.
If I run /opt/coldfusion9/bin/coldfusion status, I get:
Pg/Sec DB/Sec CP/Sec Reqs Reqs Reqs AvgQ   AvgReq AvgDB Bytes Bytes
Now Hi Now Hi Now Hi Q'ed Run'g TO'ed Time   Time   Time   In/Sec Out/Sec
0   0   0   0   -1 -1 150   25    0     0      -1352560      0      0
In the administrator, under Server Settings > Request Tuning, the setting for Maximum number of simultaneous Template requests is 25. So this makes sense so far. I could just increase the thread pool to cover these sort of load spikes. I could make it 200. (Which I did just now as a test.)
However, there's also this file /opt/coldfusion9/runtime/servers/coldfusion/SERVER-INF/jrun.xml. And some of the settings in there appear to conflict. For example, it reads:
<service class="jrunx.scheduler.SchedulerService" name="SchedulerService">
<attribute name="bindToJNDI">true</attribute>
<attribute name="activeHandlerThreads">25</attribute>
<attribute name="maxHandlerThreads">1000</attribute>
<attribute name="minHandlerThreads">20</attribute>
<attribute name="threadWaitTimeout">180</attribute>
<attribute name="timeout">600</attribute>
</service>
Which a) has fewer active threads (what does this mean?), and b) has a max threads that exceed the simultaneous request limit set in the admin. So, I'm not sure. Are these independent configs that need to be made to match manually? Or is the jrun.xml file supposed to be written by the CF Admin when changes are made there? Hmm. But maybe this is different because presumably the CF Scheduler should only use a subset of all available threads, right...so we'd always have some threads for real live users. We also have this in there:
<service class="jrun.servlet.http.WebService" name="WebService">
<attribute name="port">8500</attribute>
<attribute name="interface">*</attribute>
<attribute name="deactivated">true</attribute>
<attribute name="activeHandlerThreads">200</attribute>
<attribute name="minHandlerThreads">1</attribute>
<attribute name="maxHandlerThreads">1000</attribute>
<attribute name="mapCheck">0</attribute>
<attribute name="threadWaitTimeout">300</attribute>
<attribute name="backlog">500</attribute>
<attribute name="timeout">300</attribute>
</service>
This appears to have changed when I changed the CF Admin setting...maybe...but it's the activeHandlerThreads that matches my new maximum simulataneous requests setting...rather than the maxHandlerThreads, which again exceeds it. Finally, we have this:
<service class="jrun.servlet.jrpp.JRunProxyService" name="ProxyService">
<attribute name="activeHandlerThreads">200</attribute>
<attribute name="minHandlerThreads">1</attribute>
<attribute name="maxHandlerThreads">1000</attribute>
<attribute name="mapCheck">0</attribute>
<attribute name="threadWaitTimeout">300</attribute>
<attribute name="backlog">500</attribute>
<attribute name="deactivated">false</attribute>
<attribute name="interface">*</attribute>
<attribute name="port">51800</attribute>
<attribute name="timeout">300</attribute>
<attribute name="cacheRealPath">true</attribute>
</service>
So, I'm not certain which (if any) of these I should change and what exactly the relationship is between maximum requests and maximum threads. Also, since several of these list the maxHandlerThreads as 1000, I'm wondering if I should just set the maximum simultaneous requests to 1000. There must be some upper limit that depends on available server resources...but I'm not sure what it is and I don't really want to play around with it since it's a production environment.
I'm not sure if it pertains to this issue at all, but when I run a ps aux | grep coldfusion I get the following:
wwwrun   15853 0.0 0.0   8704   760 pts/1
S
20:22   0:00 /opt/coldfusion9/runtime/bin/coldfusion9 -jar jrun.jar -autorestart -start coldfusion
wwwrun   15855 5.4 18.2 1678552 701932 pts/1
Sl
20:22   1:38 /opt/coldfusion9/runtime/bin/coldfusion9 -jar jrun.jar -start coldfusion
There are always these two and never more than these two processes. So there does not appear to be a one-to-one relationship between processes and threads. I recall from an MX 6.1 install I maintained for many years that additional CF processes were visible in the process list. It seemed to me at the time like I had a process for each thread...so either I was wrong or something is quite different in version 9 since it's reporting 25 running requests and only showing these two processes. If a single process can have multiple threads in the background, then I'm given to wonder why I have two processes instead of one...just curious.
So, anyway, I've been experimenting while composing this post. As noted above I adjusted the maximum simulataneous requests up to 200. I was hoping this would solve my problem, but CF just crashed again (rather it slogged down and requests started timing out...so effectively "crashed"). This time, top looked similar (still consuming more than 99% of the CPU), but CF status looked different:
Pg/Sec DB/Sec CP/Sec Reqs Reqs Reqs AvgQ   AvgReq AvgDB Bytes Bytes
Now Hi Now Hi Now Hi Q'ed Run'g TO'ed Time   Time   Time   In/Sec Out/Sec
0   0   0   0   -1 -1 0     150   0     0      0      0      0      0
Obviously, since I'd increased the maximum simultaneous requests, it was allowing more requests to run simultaneously...but it was still maxing out the server resources.
Further experiments (after restarting CF) showed me that the server became unusably slogged after about 30-35 "Reqs Run'g", with all additional requests headed for an inevitible timeout:
Pg/Sec DB/Sec CP/Sec Reqs Reqs Reqs AvgQ   AvgReq AvgDB Bytes Bytes
Now Hi Now Hi Now Hi Q'ed Run'g TO'ed Time   Time   Time   In/Sec Out/Sec
0   0   0   0   -1 -1 0     33    0     0      -492   0      0      0
So, it's clear that increasing the maximum simultaneous requests has not helped. I guess what it comes down to is this: What is it having such a hard time with? Where are these spikes coming from? Bursts of traffic? On what pages? What requests are running at any given time? I guess I simply need more information to continue troubleshooting. If there are long-running requests, or other issues, I'm not seeing it in the logs (although I do have that option checked in the admin). I need to know which requests exactly are those responsible for these spikes. Any help would be much appreciated. Thanks.
~Day

I really appreciate your help. However, I haven't been able to find the JRun Thread settings you describe above.
Under Request Tuning, I see:
Server Settings > Request Tuning
Request Limits
Maximum number of simultaneous Template requests
Restricts the number of simultaneously processed requests. Use this setting to increase overall system performance for heavy load applications. Requests beyond the specified limit are queued. On Standard Edition, you must restart ColdFusion to enable this setting.
Maximum number of simultaneous Flash Remoting requests
The number of Flash Remoting requests that can be processed concurrently.
Maximum number of simultaneous Web Service requests
The number of Web Service requests that can be processed concurrently.
Maximum number of simultaneous CFC function requests
The number of ColdFusion Component methods that can be processed concurrently via HTTP. This does not affect invocation of CFC methods from within CFML, only methods requested via an HTTP request.
Tag Limit Settings
Maximum number of simultaneous Report threads
The maximum number of ColdFusion reports that can be processed concurrently.
Maximum number of threads available for CFTHREAD
The maximum number of threads created by CFTHREAD that will be run concurrently. Threads created by CFTHREAD in excess of this are queued. On Standard Edition, the maximum limit is 10.
And under Java and JVM, I see:
Server Settings > Java and JVM
    Java and JVM settings control the way ColdFusion starts the Java Virtual Machine when it starts. You can control settings like what classpaths are used and how memory is allocated as well as add custom command line arguments. Changing these settings requires restarting ColdFusion. If you enter an incorrect setting, ColdFusion may not restart properly.
   Backups of the jvm.config file are created when you hit the submit button. You can use this backup to restore from a critical change.
   Java Virtual Machine Path
Specifies the location of the Java Virtual Machine.
   Minimum JVM Heap Size (MB)         Maximum JVM Heap Size (MB)
   The Memory Size settings determine the amount of memory that the JVM can use for programs and data.
   ColdFusion Class Path
Specifies any additional class paths for the JVM, with multiple directories separated by commas.
   JVM Arguments
-server -Dsun.io.useCanonCaches=false -XX:MaxPermSize=192m -XX:+UseParallelGC -Xbatch -Dcoldfusion.rootDir={application.home}/../ -Dcoldfusion.libPath={application.home}/../lib
Specifies any specific JVM initialization options, separated by spaces.
I did go take a look at FusionReactor and found it's not free (which would be fine, of course, if it would actually help). It looks like there's a fully functional demo, which is cool...but I've haven't been able to get it to install yet, so we'll see.
Thanks again!
~Day
(By the way, I've cross-posted this inquiry on StackOverflow. So if you're able to help me arrive at a solution you might want to answer there as well.)

Thread number limitation on Sun One Web Server 6.1 on Solaris 9

Hi.
I am testing my servlet on Web Server 6.1 on Solaris 9 (SPARC). I am logging start of HTTPServlet.doPost() method and end of it, by calling GenericServlet.log() method for perfomance check.
When I request more than two request(it takes long time) simultaneously from browser, my servlet logs like:
doPost start
doPost start
doPost end
doPost start
doPost end
doPost start
:that is ,two requests is processed concurrent by threads, and another requests waiting, and after each running thread ends, waiting request is processed one by one.
I think there is some limitation of thread or connections, so I checked magnus.conf. But RqThrottle is set to 128. And I cannot find any thread number settings.
My magnus.conf is as follows.
# The NetsiteRoot, ServerName, and ServerID directives are DEPRECATED.
# They will not be supported in future releases of the Web Server.
NetsiteRoot /export/home0/SUNWwbsvr
ServerName test03
ServerID https-test03
RqThrottle 128
DNS off
Security off
PidLog /export/home0/SUNWwbsvr/https-test03/logs/pid
User webservd
StackSize 131072
TempDir /tmp/https-test03-8ac62f09
UseNativePoll off
PostThreadsEarly on
KernelThreads off
Init fn=flex-init access="$accesslog" format.access="%Ses->client.ip% - %Req->vars.auth-user% [%SYSDATE%] \"%Req->reqpb.clf-request%\" %Req->srvhdrs.clf-status% %Req->srvhdrs.content-length%"
Init fn="load-modules" shlib="/export/home0/SUNWwbsvr/bin/https/lib/libj2eeplugin.so" shlib_flags="(global|now)"Why web server do not process more than two requests concurrent? Which server configuration should I check?
Thanks in advance.

I don't think I ever ran into that kind of a limit. Does the servlet use database connections (maybe the connection pool is empty) or other critical sections / large synchronized blocks?
Try a minimal servlet that takes a while to execute:
    doGet(...)
        log("sleep starting " + Thread.currentThread().getName());
        try {
            Thread.sleep(30000);
        } catch (Exception e) { }
        log("sleep done " + Thread.currentThread().getName());
        response.getOutputStream().println("good morning");

OpenMP thread number

Hello,
I add OpenMP directives in my code, do "setenv OMP_NUM_THREADS 4", then run the code. When the code is running, I use "top" utility to look at this running job. One column "THR" in the "top" screen shows "6" for this job. I only set to use at most 4 threads, why are there "6" threads? I then tested different thread numbers, when I set thread number to 1,2,3,4, respectively, the running process actually uses 3,4,5,6 threads respectively. So, even if I want it to run serially by set 1 thread, it still create 3 threads.
If I compile the real serial code which has no OpenMP directives at all, the code would run as a real serial code, "top" indicates only 1 thread is created.
This kind of behavior is not expected, anything wrong with SUN compiler or parallel run time system? I am using Studio8 compiler on 4-processor SUN fire V880 system.
Anybody has similar experience?
Thanks for any input or comments.
Jeff

It's likely that you're running on Solaris 8 or older, and not
using the 1-to-1 libthread. (/usr/lib/lwp on Solaris 8)
That threads library creates extra threads for "internal" use,
like catching signals.
The OMP variable controls how many threads the OMP library
creates, not how many will be in the process.
The extra threads don't normally run code except during special
cases like signal processing.
On newer versions of Solaris you can use "prstat -L" to get a top-like
display showing all active LWP's. This would be a good tool to see
how many threads are actually doing work at once in your OpenMP program.
--chris

Thread number per connection crash 4.16

We are using a program in a loop, we add 500 entry in 2 minutes. If the
thread number per connection is set to 5 or 10, the Netscape Directory
Server 4.16 got disorderly shutdown and dump a core. If we set this as 1,
the server works fine.
Could you please tell me what is the problem? Is this version not reliable?
Thanks,
Peter

Peter Pan wrote:
We are using a program in a loop, we add 500 entry in 2 minutes. If the
thread number per connection is set to 5 or 10, the Netscape Directory
Server 4.16 got disorderly shutdown and dump a core. If we set this as 1,
the server works fine.
Could you please tell me what is the problem? Is this version not reliable?What does it say in your error log? Is the number of threads per connection times the number of connections greater than the
threadnumber? Are you sure you have tuned your kernel parameters to allow a large number of threads per process and per kernel?
>
>
Thanks,
Peter

Thread number limit

Hi !
Is there a thread number limit in a JVM ?
Thanks
Ludovic

The OS limits the number of threads which can be run without significant overhead.
This is 100 - 1000 depending on the OS.

Log4J - Unable to get Thread number in log4j

Hi
Please post me the log4j config file used in Sun One Application server 7.0. I am unable to retrive the thread number in logs using my existing log config file.
existing log line sample :
Aug 01 17:48:52 DEBUG [service-j2ee]
Thanks in advance.
Vishnu Deevi

Hi Sadasivam,
Could you explain me how did you resolved this.
BR
Raju

How to change the thread number for user account

I remember that for each user account, we can limit the maximum thread number it can create for a user process. But how to change this number?
Thanks,
Iris

Hi ,
I do not think that there is a way to control the number of "threads per user".
Are you referring to "thread id" ? Please elaborate on your requirement.
You may want to take a look at the complete list of process sizing tunables
at:
http://docs.sun.com/ab2/coll.707.1/SOLTUNEPARAMREF/@Ab2PageView/idmatch(CHAPTER2-4)?Ab2Lang=C&Ab2Enc=iso-8859-1#CHAPTER2-4
The link can also be accessed as:
http://docs.sun.com
Collection Titles
Solaris Tunable Parameters Collection
Solaris Tunable Parameters Reference Manual HTH
Gopinath.
Developer Technical Support
Sun Microsystems Inc

J2ee Hanging and thread number growing

Hello all,
Nearly every day our XI system hangs. The Abap stack works
normally, but the Java stack no longer allows any connections (http,
visual admin).
After the "WaitingTaskCount" KPI reaches its threshold (RZ20 - Kernel->Application Threads Pool -> WaitingTasksCount), the j2ee engine is hanging. We noticed a very high number of thread (442). When we telnet on the
J2ee engine on port 50008, we jump from the dispatcher to the server and we execute a garbage collector, the j2ee engine is available again but
it hangs again 2 hours after.
Regards,
Vincent

Nadim,
Please check SAP Note 764417 - Information for troubleshooting of the SAP J2EE
Engine 6.40.
It is very useful to have a full thread dump if the J2EE Engine is running with high
CPU consumption, or an Out of Memory error. See SAP Note 710154 - How to
create a thread dump for J2EE Engine 6.30. I think SAP recommend that you create the thread dump once the J2EE Engine is running properly and once when an error occurs.
---Satish

Set execution thread number

I am running WLS6.1SP1, and in the tab configuration/tunning, I did not see a place
that let me set the number of execution threads, does any body know where to set
it ?
thanks
zhou

I found this on weblogic.developer.interest.performance just minutes after my last post:
1. Click on "Servers" folder in tree to expand it to where you can see the server you want to work with (if necessary).
2. Right-mouse click of the server you want to work with. This will display a track pop-up menu. Select the "View Execute Queues" menu option.
3. Click the link for the "default" execute queue in the HTML table that is displayed. Afterwards, you should see the screen you are accustomed to using to adjust the execute threads count.
4. Change the value in the field next to the "Thread Count" label and click the "Apply" button.
I don't know why I didn't think of that...
Dave
On Mon, 03 Jun 2002 19:08:16 GMT, [email protected] (David W. Archer) wrote:
I think it's missing from the GUI. It's in config.xml as:
<Server ...>
<ExecuteQueue Name="default" ThreadCount="50"/>
/Server>
On 11 Apr 2002 12:43:04 -0800, "x zhou" <[email protected]> wrote:
I am running WLS6.1SP1, and in the tab configuration/tunning, I did not see a place
that let me set the number of execution threads, does any body know where to set
it ?
thanks
zhou

Unresponsive server/jrun threads

Running CF9 on Solaris 10 with the oracle webserver7
Our Jrun process is hanging several times a day with the unresponsive server message. I've got monitoring and tracing turned on and also getting stack dumps.
Here's a section of the log:
07/08 00:05:42 Information [scheduler-2] - Alert: Unresponsive server state dete
cted. 10 or more threads have been busy for over 60000 milliseconds
07/08 00:05:45 metrics Web threads (busy/total/delay/idle/listen): 19/20/0/0/1 R
equests(delay/drop/handle): 0/0/0 Sessions: 0 Total Memory=438016 Free=138098
07/08 00:05:45 Information [scheduler-2] - Mail: 'ColdFusion: Unresponsive Serve
r Alert active at Sun, 8 Jul 2012 00:05:42' From:'cf9@web2...' To:'...' was successfully sent using smtp...
07/08 00:05:45 Information [scheduler-2] - Alert: unresponsiveserveralert: Email
notification sent.
07/08 00:05:45 Information [scheduler-2] - Aborting request null handled by thre
ad jrpp-7 CFML stack:   Java stack:   java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:485)      at coldfusion.util.AbstractCache.
fetch(AbstractCache.java:46)      at coldfusion.util.SoftCache.get_statsOff(Soft
For some reason we now have busy threads. But not all the time. It's intermittent. All Data Sources appear to be responding as they should and I see no hardware issues(disks going bad or interfaces going flaky).
Here's what my threads look like when the server goes unresponsive:
07/10 14:28:26(busy/total/delay/idle/listen):0/3/0/2/1
07/10 14:28:46(busy/total/delay/idle/listen):0/3/0/2/1
07/10 14:29:06(busy/total/delay/idle/listen):0/3/0/2/1
07/10 14:29:26(busy/total/delay/idle/listen):0/3/0/2/1
07/10 14:29:46(busy/total/delay/idle/listen):0/3/0/2/1
07/10 14:30:06(busy/total/delay/idle/listen):0/3/0/2/1
07/10 14:30:26(busy/total/delay/idle/listen):0/3/0/2/1
07/10 14:30:46(busy/total/delay/idle/listen):0/3/0/2/1
07/10 14:31:06(busy/total/delay/idle/listen):0/3/0/2/1
07/10 14:31:26(busy/total/delay/idle/listen):4/5/0/0/1
07/10 14:31:46(busy/total/delay/idle/listen):11/12/0/0/1
07/10 14:32:06(busy/total/delay/idle/listen):13/14/0/0/1
07/10 14:32:26(busy/total/delay/idle/listen):19/20/0/0/1
07/10 14:32:46(busy/total/delay/idle/listen):25/26/0/0/1
07/10 14:33:06(busy/total/delay/idle/listen):6/33/0/15/12
07/10 14:33:26(busy/total/delay/idle/listen):1/33/0/1/31
07/10 14:33:46(busy/total/delay/idle/listen):0/33/0/2/31
07/10 14:34:06(busy/total/delay/idle/listen):0/33/0/2/31
07/10 14:34:26(busy/total/delay/idle/listen):0/33/0/2/31
07/10 14:34:46(busy/total/delay/idle/listen):0/33/0/2/31
07/10 14:35:06(busy/total/delay/idle/listen):0/33/0/2/31
07/10 14:35:26(busy/total/delay/idle/listen):0/33/0/2/31
Any ideas on how to resolve this issue would be greatly appreciated.

Running CF9 on Solaris 10 with the oracle webserver7
Our Jrun process is hanging several times a day with the unresponsive server message. I've got monitoring and tracing turned on and also getting stack dumps.
Here's a section of the log:
07/08 00:05:42 Information [scheduler-2] - Alert: Unresponsive server state dete
cted. 10 or more threads have been busy for over 60000 milliseconds
07/08 00:05:45 metrics Web threads (busy/total/delay/idle/listen): 19/20/0/0/1 R
equests(delay/drop/handle): 0/0/0 Sessions: 0 Total Memory=438016 Free=138098
07/08 00:05:45 Information [scheduler-2] - Mail: 'ColdFusion: Unresponsive Serve
r Alert active at Sun, 8 Jul 2012 00:05:42' From:'cf9@web2...' To:'...' was successfully sent using smtp...
07/08 00:05:45 Information [scheduler-2] - Alert: unresponsiveserveralert: Email
notification sent.
07/08 00:05:45 Information [scheduler-2] - Aborting request null handled by thre
ad jrpp-7 CFML stack:   Java stack:   java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:485)      at coldfusion.util.AbstractCache.
fetch(AbstractCache.java:46)      at coldfusion.util.SoftCache.get_statsOff(Soft
For some reason we now have busy threads. But not all the time. It's intermittent. All Data Sources appear to be responding as they should and I see no hardware issues(disks going bad or interfaces going flaky).
Here's what my threads look like when the server goes unresponsive:
07/10 14:28:26(busy/total/delay/idle/listen):0/3/0/2/1
07/10 14:28:46(busy/total/delay/idle/listen):0/3/0/2/1
07/10 14:29:06(busy/total/delay/idle/listen):0/3/0/2/1
07/10 14:29:26(busy/total/delay/idle/listen):0/3/0/2/1
07/10 14:29:46(busy/total/delay/idle/listen):0/3/0/2/1
07/10 14:30:06(busy/total/delay/idle/listen):0/3/0/2/1
07/10 14:30:26(busy/total/delay/idle/listen):0/3/0/2/1
07/10 14:30:46(busy/total/delay/idle/listen):0/3/0/2/1
07/10 14:31:06(busy/total/delay/idle/listen):0/3/0/2/1
07/10 14:31:26(busy/total/delay/idle/listen):4/5/0/0/1
07/10 14:31:46(busy/total/delay/idle/listen):11/12/0/0/1
07/10 14:32:06(busy/total/delay/idle/listen):13/14/0/0/1
07/10 14:32:26(busy/total/delay/idle/listen):19/20/0/0/1
07/10 14:32:46(busy/total/delay/idle/listen):25/26/0/0/1
07/10 14:33:06(busy/total/delay/idle/listen):6/33/0/15/12
07/10 14:33:26(busy/total/delay/idle/listen):1/33/0/1/31
07/10 14:33:46(busy/total/delay/idle/listen):0/33/0/2/31
07/10 14:34:06(busy/total/delay/idle/listen):0/33/0/2/31
07/10 14:34:26(busy/total/delay/idle/listen):0/33/0/2/31
07/10 14:34:46(busy/total/delay/idle/listen):0/33/0/2/31
07/10 14:35:06(busy/total/delay/idle/listen):0/33/0/2/31
07/10 14:35:26(busy/total/delay/idle/listen):0/33/0/2/31
Any ideas on how to resolve this issue would be greatly appreciated.

Find sequence and thread number of Oracle 10g Database

Hallo!I am a newbie Oracle DBA studying for OCP.I am trying various methods of performing flashback of the database.
Out of these options there is one that uses the sequence and thread numbers of the database as below
RMAN> FLASHBACK DATABASE
2> TO SEQUENCE=223 THREAD=1;
How can I find out current sequence and thread numbers of the db to enable me implement such a flashback strategy?
Thanks.

Current sequence# is the one with status = CURRENT
SELECT group#, thread#, sequence#, status FROM v$log;Lukasz

Tuning the good number of thread with Work Manager?

Hi,
I search some best practice or experience return on the max thread number on a weblogic managed server
I try to explain: with WLS 8.1 and execute queue it was hard to tune the good number of thread but possible (with some processor and for an application we find that after 30 concurrent thread, there's lower performance because of switch on processeur, for others it was 45 for example)
Now i can see sometimes more than 500 thread on one JVM and it seem to be very much for me!!
we face some problem of response time in PRODUCTION, i can see sometimes more than 100 Stuck thread on a resource, so i think it's the reason of bad response time. But with Work Manager, it increase the number of thread to accept others request and the CPU stay at acceptable level (less than 50%) because the stuckthread are do nothing (waiting for resource)
So i don't understand the good tuning to apply since WorkManager...ok it isn't normal to have a lot of stuck thread but if there's no matter about the max number of thread, is it useful to stop and restart managed server?
do you think we can have have bad performance if there's a lot of thread?
thank you for your experience return. If you have no idea just tell me how much thread you can see on your managed server in Production.

up, up...
we have always the same probleme in production: 50 stuck thread on each JVM since 15 days....
the manages serveurs are in warning but don't seem to be disturb cause the work manager add more threads dynamicaly.
Anyone have idea if this situation is a probleme for response time on other request ?
reboot managed solve this situation but i would like to understand the consequence of this situation.
thanks a lot for your experience.

Jrun crash

hi all
i manage a server with cf8.
my customer decided to move server to a cloud.
from that moment, i lost my sleep...
one or twice a day jRun gets the error
"JRun closed connection".
this is a little report of situation... any help is very appreciated... :-)
== SERVER SPECS ==
virtual machine on wmware cloud
with Linux CentOS, 32 bit
4 core CPU
3 GB Ram
1,5 GB Ram dedicated for JRun
JVM use 20% of allocated memory.
80.000 pages a day
== JRUN ==
Maximum number of simultaneous Template requests: 25
Maximum JVM Heap Size (MB): 1524
i activate jRun log. this is a optimal situation:
THREADS: Listen=22 Idle=60 Running=1 Delayed/Waiting=0
Time Delayed=0 Dropped=0 Completed=62 Time To Complete=11253 Total=83
THREADS: Listen=23 Idle=86 Running=1 Delayed/Waiting=0
Time Delayed=0 Dropped=0 Completed=134 Time To Complete=30495 Total=110
THREADS: Listen=22 Idle=77 Running=1 Delayed/Waiting=0
Time Delayed=0 Dropped=0 Completed=106 Time To Complete=19309 Total=100
before crash, the situation is similar... :-(
== DB ==
db (postgres 9.1) is in local lan on other virtual server,
no particulary data to provide.
== DURING THE CRASH... ==
this is the situation just before crash cf crash (from fusionreactor)
http://i.imgur.com/VwXts.png
http://i.imgur.com/ezzuV.png
there are no reasons for this situation.
no overload on cpu, no overload on ram.
in screenshot, over the first 3/4 page in list, other pages
are normally generated in 1/4 of second.
from this reports a see a strage "time question"...
== "TIME QUESTION"... ==
on this server happen at least two strage events...
- 1 -
in fusionreactor report, such as in seefusion report, such as in cf log,
i see a very strange long long long request.
this request taken 4,398 secs, 1h and 22m to complete. (ALWAYS 1h 22m!!!).
this happens randomly, in normal situation this page are generated
in few millisecons. moreover, the end-time of this tasks is IN THE FUTURE!
time of machine is updated regularly via ntp.
can this happen because of the virtual machine?
12/19 12:20:55 Warning [jrpp-871] - Thread: jrpp-871, template:
/jackets/audio.cfm, completed in 4,398 secs
12/19 12:23:00 Warning [jrpp-1068] - Thread: jrpp-1068, template:
/articoli/index.cfm, completed in 4,398 secs
12/19 13:00:05 Warning [jrpp-1126] - Thread: jrpp-1126, template:
/articoli/index.cfm, completed in 4,398 secs
12/19 13:23:10 Warning [jrpp-1292] - Thread: jrpp-1292, template:
/home/index.cfm, completed in 4,398 secs
- 2 -
second strange event, is the frequently timeout of cfloop, cfoutout,
cffile tags... but is not "real" timeout.
when i meet up with the error, there is no waiting time that should
generate the timeout error.
evidently cf with this error, want to say me such other,
but i don't know what... :-/
you have some idea?
i add "var" scope to cfc in my code...
== APACHE PROCESS ==
i activeted a simple log for apache connections.
sometimes, just before the crash the apache load
is bit overload..
H: apache process - C: connections on 80 port.
-- optimal situation --
H:79 C:195
H:108 C:255
H:85 C:264
H:81 C:163
H:77 C:198
H:88 C:402
H:82 C:243
H:82 C:196
-- just before crash --
H:68 C:63
H:81 C:81
H:143 C:130
H:156 C:152
H:163 C:169
H:163 C:163
-- just before crash --
H:178 C:186
H:178 C:170
H:178 C:187
H:178 C:176
H:178 C:188
H:178 C:215
== CFSERVER.LOG ==
from cfserver.log i get
12/18 18:48:36 error Error in getRealPathFromConn
12/18 21:51:00 error Error in getRealPathFromConn
12/18 21:51:00 error Error in getRealPathFromConn
12/18 21:51:03 error Error in getRealPathFromConn
12/18 21:51:03 error Error in getRealPathFromConn
but i do not think this is an important matter...
===
have you got some ideas for this strage case?
links, documents... any idea is welcome!
many thanks
Roberto

for future...
the "strange" timeouts are caused by a linux kernel bug...
http://archives.postgresql.org/pgsql-general/2011-07/msg00300.php

JRUN thread number

Similar Messages

Maybe you are looking for