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.

Similar Messages

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.)

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.

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

Server Socket Threading

My program does a couple of things, one of the thing it does is it runs a ServerSocket in the background.
The problem is that when I run the my Server class, I can't do anything else since the ServerSocket is stuck in an infinite loop waiting for a new request.
See this:
My Driver
    public static void main(String [] args) {
            new Server();
            new SomethingElse();
    }Server's snippet of code that establishes a connection between a client and server.
     while (true)
                  try
                        Socket clientSocket = serverSocket.accept();
                   catch (IOException e)
                        System.out.println("Could not accept requests.");
                        System.exit(-1);
              }So I can never reach SomethingElse() in the driver since Server is stuck in an infinite loop.
I have tried to implement the ServerSocket as a thread, but the serverSocket throws an IOException (which makes sense since a ServerSocket should not have multiple versions of itself running at a same time unless they are on separate ports).
So how would take care of this?
Edited by: sharpdust on Dec 5, 2008 1:12 PM

How about something like this?
public static void main(String [] args) {
            new Thread(new Server()).start();
            new SomethingElse();
public class Server implements Runnable {
     public void run() {
          while (true)
                  try
                        Socket clientSocket = serverSocket.accept();
                   catch (IOException e)
                        System.out.println("Could not accept requests.");
                        System.exit(-1);
}

Oracle Application Server 10g thread stuck issue.

We are having,
Oracle Application Server 10g [10.1.3.1 + 10.1.3.4patch] along with Oracle Http Server 2.0
Now there is a issue of thread stuck [some application threads taking longer times] due to which the application server is unable to respond and sometimes it reinits the oc4j instance.
=> Is there any setting to increase the Thread Stuck Time in OAS.
=> Is there any setting to stop the auto reinit of oc4j instance.
=> Does the auto re init of oc4j get logged in opmn.log as well as in service.log.
It will be really helpful if any advice on the same.
Thanks in advance...
ManojC

Look in httpd.conf file anything that is like thread in there you will find a simple description of the Directives.
Greetings.

Can a server handle threads?

I have a server that
a) recieves data
b) updates a database
c) sends data to clients
I tried putting the database update into a separate
thread :
Runnable task = new Runnable() {
public void run() {
//i have a print statement here
//which is not reached
//database update in here
so now the server recieves data and sends it to the clients
but it never updates the database.
Are there any issues that you are aware of with starting threads on
a server?
thanks,
zeke

Thanks for responding.
Here is some more detail...
static class TaskRunner {
 private final static int TIME_TO_WAIT = 60000;
 private Queue q = new Queue();
 class MonitorThread extends Thread {
 private Thread t;
 private boolean go;
 private boolean timeout;
 MonitorThread(String name, Thread t) {
 super(name + " monitor");
 this.t = t;
 this.start();
 public void run() {
 while (true) {
 // wait for tick off
 synchronized(this) {
 go = false;
 while (go == false) {
 try {
 wait();
 catch (InterruptedException ex)
 //ignore
 // get out of this wait either in timeou
t or reset
 try {
 wait(TIME_TO_WAIT);
 catch (InterruptedException ex) {}
 if (timeout == true) {
 CoreUtil.beep();
 printDebugMessage("***** " + t.g
etName() + " timeout " + TIME_TO_WAIT + "ms !!!!!!!!");
 synchronized void begin() {
 go = true;
 notify();
 class TaskRunnerThread extends Thread {
 private MonitorThread monitor;
 TaskRunnerThread(String name, boolean monitorOn) {
 super(name);
 if (monitorOn) {
 this.monitor = new MonitorThread(name, t
his);
 yield();
 CoreUtil.setPriority(this, Thread.MIN_PRIORITY +
2);
 CoreUtil.setDaemon(this, true);
 this.start();
 * Get a message from the queue, block if there is no mes
sage.
 * @return the message.
 public void run() {
 while (true) {
 if (monitor != null) {
 monitor.reset();
 Runnable task;
 synchronized(TaskRunner.this) {
 while (q.isEmpty()) {
 try {
 TaskRunner.this.
wait();
 catch (InterruptedExcept
ion e) { }
 task = (Runnable) q.pop();
 // a null task signal for exit
 if (task == null) {
 return;
 if (monitor != null) {
 monitor.begin();
 try {
 task.run();
 catch (Exception ex) {
 printDebugMessage("Exception in
runnerTask: " + ex);
 ex.printStackTrace();
 task = null; // null out so we don
't hold reference here
 // create a TaskRunner object with the specified number of work
threads
 TaskRunner(String name, int n) {
 this(name, n, false);
 // create a TaskRunner object with the specified number of work
threads
 TaskRunner(String name, int n, boolean monitorOn) {
 // create a pool of RunnerThread so in case one is block
ed
 // we are not block totally. It's a very bad sign if an
y
 // of these thread a block for a long time
 for (int i = 0 ; i < n ; i++) {
 new TaskRunnerThread(name + " " + i, monitorOn);
 * Execute the subribe command
 * @param m the messsage
 synchronized void execute(Runnable task) {
 q.push(task);
 notify();
 public static void runTask(Runnable task) {
 printDebugMessage("in runTask "+task);
 if(taskRunner == null)
 taskRunner = new TaskRunner("CoreUtil.TaskRunner Thread", 3);
 taskRunner.execute(task);
 public static void close(){
 taskRunner = null;
//then i call this
runTask(new Runnable() {
 public void run() {
 //update database
});do you see any reason why the thread wouldn't start?

SQL Server - Mult threading

Hi ,
We have requirement to execute a SQL Server 2008 R2 , stored procedure for 200 different input values ( 200 times calling the same procedure) . All these calculations can be executed independently. Currently, we
are executing the same procedure for 200 different values SEQUENTIALLY. I feel this can be converted as parallel process / muti threaded , where i can initiate the execution of stored procedures for multiple values at the same time, so that i can reduce the
total execution time.
In SQL Server is there any possibility of handling this scenario ( parallel process / multi threading) . Please suggest.
Thank you

Hello,
Its a web application and the request is initiated from web page ... and the user is exepecting a quick responce .. The procedure has to do lot of calcualtion based on the supplied parameters..
There isn't much you can do except for tune the stored procedures or have an intermediate result set ready through something such as a indexed view. If there are multiple simultaneous queries on the same connections then I would look at the middleware tier
if you're using one.
SQL Server automatically decides (which can be influenced in several different ways) how to run the query. SQL Server itself is vastly multi-threaded and not every query benefits from parallelism. I feel as though you'd have more luck either tuning the stored
procedures.
Sean Gallardy | Blog |
Twitter

Weblogic server + stuck threads

Hi All,
We have java application deployed on weblogic server 10.1.3.4 which is integrated with BPEL (SOA Oracle 11g). The application creates a task through BPEL. We have configured StuckThread Max Time to 600 secs. Now after certain time (5-7 days) the servers goes into warning state due to stuck threads and finally it gets crashed
We noticed the OOM error in jrockit dump, could any one help me here as how to avoid this? your help is very much appreciated, thanks

Regarding
Sample of your Weblogic logs showing the java.lang.OutOfMemoryError along with Stack Trace if available
Please find below
[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <532776f80ba738ab:-48a8d4c8:133068f0cee:-8000-00000000000001a5> <1322080967160> <BEA-080003> <RuntimeException thrown by rmi server: javax.management.remote.rmi.RMIConnectionImpl.invoke(Ljavax.management.ObjectName;Ljava.lang.String;Ljava.rmi.MarshalledObject;[Ljava.lang.String;Ljavax.security.auth.Subject;)
javax.management.RuntimeErrorException: java.lang.OutOfMemoryError: allocLargeObjectOrArray: [B, size 1335312.
javax.management.RuntimeErrorException: java.lang.OutOfMemoryError: allocLargeObjectOrArray: [B, size 1335312
 at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrow(DefaultMBeanServerInterceptor.java:858)
 at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrowMaybeMBeanException(DefaultMBeanServerInterceptor.java:869)
 at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:838)
 at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
 at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449)
 at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:447)
 at weblogic.management.mbeanservers.internal.JMXContextInterceptor.invoke(JMXContextInterceptor.java:263)
 at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449)
 at weblogic.management.mbeanservers.internal.SecurityInterceptor.invoke(SecurityInterceptor.java:444)
 at weblogic.management.jmx.mbeanserver.WLSMBeanServer.invoke(WLSMBeanServer.java:323)
 at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$11.run(JMXConnectorSubjectForwarder.java:661)
 at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder.invoke(JMXConnectorSubjectForwarder.java:654)
 at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788)
 at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
 at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:668)
 at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Caused By: java.lang.OutOfMemoryError: allocLargeObjectOrArray: [B, size 1335312
 at java.util.Arrays.copyOf(Arrays.java:2786)
 at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94)
 at java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStream.java:1847)
at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94)
 at java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStream.java:1847)
 at java.io.ObjectOutputStream$BlockDataOutputStream.flush(ObjectOutputStream.java:1792)
 at java.io.ObjectOutputStream.flush(ObjectOutputStream.java:699)
 at java.io.ObjectOutputStream.close(ObjectOutputStream.java:720)
 at oracle.dms.jmx.app.ServerAggreMBeanImpl.getTableGroupInBytes(ServerAggreMBeanImpl.java:328)
 at oracle.dms.jmx.app.ServerAggreMBeanWrapper.invokeOperation(ServerAggreMBeanWrapper.java:71)
 at oracle.dms.jmx.app.AggreMBeanWrapper.invoke(AggreMBeanWrapper.java:167)
 at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
 at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
 at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449)
 at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:447)
 at weblogic.management.mbeanservers.internal.JMXContextInterceptor.invoke(JMXContextInterceptor.java:263)
 at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449)
 at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:447)
 at weblogic.management.mbeanservers.internal.SecurityInterceptor.invoke(SecurityInterceptor.java:444)
 at weblogic.management.jmx.mbeanserver.WLSMBeanServer.invoke(WLSMBeanServer.java:323)
 at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$11$1.run(JMXConnectorSubjectForwarder.java:663)
 at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$11.run(JMXConnectorSubjectForwarder.java:661)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
 at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder.invoke(JMXConnectorSubjectForwarder.java:654)
 at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1427)
 at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
 at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1265)
 at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1367)
 at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788)
 at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
 at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
 at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
 at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
 at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)

Tcp server single thread per user?

Hi all,
I am working on a spam filter, which is implemented as an IMAP proxy server (web worker). Currently, I use TcpListener to listen for clients, and when one connects, I spin off a thread which listens to them and pushes their requests to the IMAP server. I
also create a thread that listens to the IMAP server and pushes responses down to the client.
I have some concerns about the performance of this when we have hundreds or thousands of connections. Do you think I should be concerned about the number of threads? If so, does anyone have some alternate suggestions for handling the requests?
Thanks,
Erik

Hi,
Based on my understanding, if use web/worker role as the server, we could use some metrics to see whether the web/worker role reach to the limitation, and use auto scale feature to scale up our cloud service in order to service for more clients, refer
to
http://azure.microsoft.com/en-us/documentation/articles/cloud-services-how-to-scale/ for more details.
Best Regards,
Jambor
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Server count thread count

our server has 4 cpus(double kernel), 8GB memory
windows 2003 64bit
we use netweaver 7.0 with sp6
how much server node
and how much threadcount for 'applicationthreadmanager' or 'threadmanager'(MIN MAX Thread count)
will increase performance ?
regard

Hey
The amount of 'applicationthreadmanager' or 'threadmanager'
is depended on two things:
1. The system you are using, for example XI, BI and etc.
2. The load on the system.
In general, the J2EE comes with default,
and if you are not having performance issues,
than you should keep this parameter without any change.
If you are having performance problems,
like describes in the following links, you should change the configuration:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_mid/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d393530393231%7d
Example for XI configuration:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_xi/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d393337313539%7d
How to configure number of concurrent processes in XI?
Example for Portal configuration:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_jas/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d383236333931%7d
Here is an a link to the configure procedure:
http://help.sap.com/saphelp_nw04/helpdata/en/47/9a3e759e2141a7b03e4f37e6c14074/frameset.htm

Help Needed with Unresponsive Server

Hi,
I have a server at a remote location which is fairly unresponsive. It responds to ping but not much else. I need to restart the server but a psshutdown has done very little.
I have tried a number of tools but I get RPC Server Unavailable or WMI service unavailable.
Are there any tools out there that can reboot the server without the use of RPC or WMI?
We have had a numbe of domain controllers falling over of late due to running out of memory and I believe this could be down to a number of agents we rolled out and a memory leak. Is there a remote processor tool out there I can use to view this? I have
tried a few but agan they tend to use RPC and WMI.
Your help with this is much appreciated.

They can probably help you over here with IDRAC setup.
http://en.community.dell.com/support-forums/servers/
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Is Flash Media Server is Thread Safe?

Hello,
I am trying to develop a game in flex, using flash media server 4.5. As its a multiplayer game, the server side code, should be multi threaded.
Please let me know, is the "Flash Media Server 4.5" has Thread Safety mechanism. Please provide me any link( or guide me) to have detail decription regarding this.
Thanks in advance.

Hi,
I am not sure if this exactly will help you but you can use SharedObject class to store data shared by different clients. With this you can also achieve synchronization. Below link has the details about SharedObject class:
http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/net/SharedObject. html
Also, following link has an example which shows how to synchronize users and store data using SharedObject:
http://help.adobe.com/en_US/FlashMediaServer/3.5_Deving/WS5b3ccc516d4fbf351e63e3d11a0773d3 7a-7fff.html

WL Server Stuck Thread on Network Read

I am experiencing an issue with the Weblogic deployment at my organisation.
Firstly an introduction; My Application works by receiving a Web Service (SOAP) Request from a client, the Web Service request is then processed and a internal message packet is generated and sent to a C++ Application ( which is listening on a particular port). The C++ application then processes the information, and returns the response to the web service Layer, which then process the Web Service request back to the calling client.
Currently we are having a situation where some packets are sent to the C++ application as expected. But then we are having situations where some packets NEVER reach the C++ side and the calling client time outs the entire request ( configured timeout is set for 180 seconds) and on the WebLogic Layer we have noticed a significant amount of Stuck ( and Hogging ) Threads. It should be noted that even after a stuck thread is recorded some requests are still being processed normally.
A deeper investigation into the Weblogic Thread dump shows the Weblogic thread is stuck at:
_at sun/nio/ch/IOUtil.read(Ljava/io/FileDescriptor;Ljava/nio/ByteBuffer;JLsun/nio/ch/NativeDispatcher;Ljava/lang/Object;)I(IOUtil.java)[inlined]_+
_at sun/nio/ch/SocketChannelImpl.read(SocketChannelImpl.java:236)[optimized]_+
+_^-- Holding lock: java/lang/Object@0x1a27db60[thin lock]_+
_at com/reso/number/service/comm/SoaSocket.receive(SoaSocket.java:128)[optimized]_+
_at com/reso/number/service/event/OTEvent.submitEvent(TEvent.java:219)[optimized]_+
_at com/reso/number/service/event/SIMQueryEvent.process(QQEvent.java:368)[optimized]_+
It seems that a write is sent to the C++ Application and the thread is 'WAITING' for the response.
Now, the problem is that due to the Infrastructure in place and architectural setup ( We are using Solaris Zone for Node deployment and we have the WebLogic AS on the same node/zone as the C++ application) we are unable to do a network trace to determine whether WebLogic actually sends the request.
Now my questions: i) Are there any known ways to trace the networks packets sent by Java ( maybe via the JVM) ii) Could Garbage collection cause the symptoms being observed? iii)Any recommended ways to resolve this kind of problem?
Thanks for all the help.

Increasing the Stuck Thread Max Time will not help. " Stuck Thread Max Time" tells us, after how much amount of time the thread should mark as stuck. Because by default it is 600 sec, any thread which takes more than 600sec for execution will mark as stuck. If you mention 700 sec, after 700sec the thread is marked as stuck. Even though the thread is marked stuck it still process.
Here we need to find why the thread is stuck at
]", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
Thread-15 "[STUCK] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, in native, suspended, priority=1, DAEMON> {
sun.nio.ch.SocketDispatcher.read1(SocketDispatcher.java:???)
sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:46)
sun.nio.ch.IOUtil.read(IOUtil.java:228)
sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:159)
^-- Holding lock: java.lang.Object@16a47a8b[thin lock]
weblogic.socket.NIOSocketMuxer$NIOInputStream.read(NIOSocketMuxer.java:505)
weblogic.servlet.internal.PostInputStream.read(PostInputStream.java:156)
weblogic.servlet.internal.ServletInputStreamImpl.read(ServletInputStreamImpl.java:228)
weblogic.servlet.internal.ServletRequestImpl$RequestParameters.mergePostParams(ServletRequestImpl.java:2062)
You may have to increase the buffer size at sun.nio.

HELP -- Slow and sometime unresponsive CF Server

From 2 weeks to date we are having problems with our CF Server. Especifically in one site but affect all the CF webserver. The problem is that the CF server is very slow and unresponsive some times and suddenly is normal again. Sometimes the server take a lot of time to load the index.cfm of the site in some sesion but the rarerly is that at the sametime other users load very fast the index. I don't know why. I debbuged and where it take a lot of time to load is in the application.cfm and is where the session is create. We have othe web apps in our intranet where have session too, they don´t take a lot of time of load the index (index and application.cfm).
Any recomendations?
regards!
This is the last snapshot of unresponsive server
Snapshot generated on : Fri Aug 19 12:13:27 CDT 2011      Caused by : Unresponsive Server Alert
Profiling : Enabled
Memory Tracking : Enabled
8 or more threads are busy for more than 60 seconds.
*Total Running requests - 12
*Total Queued requests - 2
Template Running requests - 7
Template Queued requests - 0
Flash Remoting Running requests - 0
Flash Remoting Queued requests - 0
CFC method Running requests - 0
CFC method Queued requests - 0
Web Service Running requests - 5
Web Service Queued requests - 2
JVM Memory Stats
Free Memory : 208656768 bytes
Used Memory : 214836864 bytes
Server Scope Memory Used - 3192 bytes
   [Variable Type : Variable Name : Size]
   STRUCT : COLDFUSION : 2992 bytes
   STRUCT : OS : 200 bytes
Application Scope Memory Used - 264 bytes
[Application Name : Memory Used]
    : 0 bytes
      [Variable Type : Variable Name : Size]
      C:\ColdFusion8\wwwroot\WEB-INF\cfc-skeletons : coldfusion.xml.rpc.CFCServlet.outputdir : 128 bytes
      C:\ColdFusion8\wwwroot\WEB-INF\cfclasses : coldfusion.compiler.outputDir : 120 bytes
       : applicationname : 40 bytes
   cfadmin : 56 bytes
      [Variable Type : Variable Name : Size]
      cfadmin : applicationname : 56 bytes
   MiComimsa : 56 bytes
      [Variable Type : Variable Name : Size]
      xxx : emailpersonarh : 80 bytes
      Portal_Prestacion : datasourcemicomimsa : 72 bytes
      MiComimsa : applicationname : 56 bytes
   Calidad : 56 bytes
      [Variable Type : Variable Name : Size]
      Calidad : applicationname : 56 bytes
   MailCheck : 56 bytes
      [Variable Type : Variable Name : Size]
      MailCheck : applicationname : 56 bytes
   bv : 40 bytes
      [Variable Type : Variable Name : Size]
      bv : applicationname : 40 bytes
Session Scope Memory Used - 18960 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620834_53879880 : MiComimsa : 976 bytes
      [Variable Type : Variable Name : Size]
      STRUCT : auth : 592 bytes
      STRUCT : usuario : 152 bytes
      ARRAY : perfiles : 152 bytes
      CFID=620834&CFTOKEN=53879880 : urltoken : 96 bytes
      MICOMIMSA_620834_53879880 : sessionid : 88 bytes
      53879880 : cftoken : 56 bytes
      620834 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620827_80747367 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620827&CFTOKEN=80747367 : urltoken : 96 bytes
      MICOMIMSA_620827_80747367 : sessionid : 88 bytes
      80747367 : cftoken : 56 bytes
      620827 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620803_58559093 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620803&CFTOKEN=58559093 : urltoken : 96 bytes
      MICOMIMSA_620803_58559093 : sessionid : 88 bytes
      58559093 : cftoken : 56 bytes
      620803 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620824_83583802 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620824&CFTOKEN=83583802 : urltoken : 96 bytes
      MICOMIMSA_620824_83583802 : sessionid : 88 bytes
      83583802 : cftoken : 56 bytes
      620824 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620800_30123461 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620800&CFTOKEN=30123461 : urltoken : 96 bytes
      MICOMIMSA_620800_30123461 : sessionid : 88 bytes
      30123461 : cftoken : 56 bytes
      620800 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620823_54237891 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620823&CFTOKEN=54237891 : urltoken : 96 bytes
      MICOMIMSA_620823_54237891 : sessionid : 88 bytes
      54237891 : cftoken : 56 bytes
      620823 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620813_39640746 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620813&CFTOKEN=39640746 : urltoken : 96 bytes
      MICOMIMSA_620813_39640746 : sessionid : 88 bytes
      39640746 : cftoken : 56 bytes
      620813 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620819_21112367 : MiComimsa : 1040 bytes
      [Variable Type : Variable Name : Size]
      STRUCT : auth : 656 bytes
      STRUCT : usuario : 152 bytes
      ARRAY : perfiles : 152 bytes
      CFID=620819&CFTOKEN=21112367 : urltoken : 96 bytes
      MICOMIMSA_620819_21112367 : sessionid : 88 bytes
      21112367 : cftoken : 56 bytes
      620819 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620197_32596268 : MiComimsa : 984 bytes
      [Variable Type : Variable Name : Size]
      STRUCT : auth : 600 bytes
      STRUCT : usuario : 152 bytes
      ARRAY : perfiles : 152 bytes
      CFID=620197&CFTOKEN=32596268 : urltoken : 96 bytes
      MICOMIMSA_620197_32596268 : sessionid : 88 bytes
      32596268 : cftoken : 56 bytes
      620197 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620836_27586780 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620836&CFTOKEN=27586780 : urltoken : 96 bytes
      MICOMIMSA_620836_27586780 : sessionid : 88 bytes
      27586780 : cftoken : 56 bytes
      620836 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620793_10115109 : MiComimsa : 632 bytes
      [Variable Type : Variable Name : Size]
      STRUCT : auth : 616 bytes
      STRUCT : usuario : 152 bytes
      ARRAY : perfiles : 152 bytes
      CFID=620793&CFTOKEN=10115109 : urltoken : 96 bytes
      MICOMIMSA_620793_10115109 : sessionid : 88 bytes
      10115109 : cftoken : 56 bytes
      620793 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620815_85048906 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620815&CFTOKEN=85048906 : urltoken : 96 bytes
      MICOMIMSA_620815_85048906 : sessionid : 88 bytes
      85048906 : cftoken : 56 bytes
      620815 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620814_69065671 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620814&CFTOKEN=69065671 : urltoken : 96 bytes
      MICOMIMSA_620814_69065671 : sessionid : 88 bytes
      69065671 : cftoken : 56 bytes
      620814 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620311_98418593 : MiComimsa : 984 bytes
      [Variable Type : Variable Name : Size]
      STRUCT : auth : 600 bytes
      STRUCT : usuario : 152 bytes
      ARRAY : perfiles : 152 bytes
      CFID=620311&CFTOKEN=98418593 : urltoken : 96 bytes
      MICOMIMSA_620311_98418593 : sessionid : 88 bytes
      98418593 : cftoken : 56 bytes
      620311 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620840_57833497 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620840&CFTOKEN=57833497 : urltoken : 96 bytes
      MICOMIMSA_620840_57833497 : sessionid : 88 bytes
      57833497 : cftoken : 56 bytes
      620840 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620801_48226812 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620801&CFTOKEN=48226812 : urltoken : 96 bytes
      MICOMIMSA_620801_48226812 : sessionid : 88 bytes
      48226812 : cftoken : 56 bytes
      620801 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620831_82072476 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620831&CFTOKEN=82072476 : urltoken : 96 bytes
      MICOMIMSA_620831_82072476 : sessionid : 88 bytes
      82072476 : cftoken : 56 bytes
      620831 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620807_99373155 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620807&CFTOKEN=99373155 : urltoken : 96 bytes
      MICOMIMSA_620807_99373155 : sessionid : 88 bytes
      99373155 : cftoken : 56 bytes
      620807 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620805_76851467 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620805&CFTOKEN=76851467 : urltoken : 96 bytes
      MICOMIMSA_620805_76851467 : sessionid : 88 bytes
      76851467 : cftoken : 56 bytes
      620805 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   Calidad_620760_76846444 : Calidad : 624 bytes
      [Variable Type : Variable Name : Size]
      STRUCT : auth : 296 bytes
      CFID=620760&CFTOKEN=76846444 : urltoken : 96 bytes
      CALIDAD_620760_76846444 : sessionid : 88 bytes
      76846444 : cftoken : 56 bytes
      620760 : cfid : 48 bytes
      on : winpopup : 40 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620830_50140928 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620830&CFTOKEN=50140928 : urltoken : 96 bytes
      MICOMIMSA_620830_50140928 : sessionid : 88 bytes
      50140928 : cftoken : 56 bytes
      620830 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620810_94946605 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620810&CFTOKEN=94946605 : urltoken : 96 bytes
      MICOMIMSA_620810_94946605 : sessionid : 88 bytes
      94946605 : cftoken : 56 bytes
      620810 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620806_87405821 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620806&CFTOKEN=87405821 : urltoken : 96 bytes
      MICOMIMSA_620806_87405821 : sessionid : 88 bytes
      87405821 : cftoken : 56 bytes
      620806 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620822_90511878 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620822&CFTOKEN=90511878 : urltoken : 96 bytes
      MICOMIMSA_620822_90511878 : sessionid : 88 bytes
      90511878 : cftoken : 56 bytes
      620822 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620804_93123588 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620804&CFTOKEN=93123588 : urltoken : 96 bytes
      MICOMIMSA_620804_93123588 : sessionid : 88 bytes
      93123588 : cftoken : 56 bytes
      620804 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620764_18211345 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620764&CFTOKEN=18211345 : urltoken : 96 bytes
      MICOMIMSA_620764_18211345 : sessionid : 88 bytes
      18211345 : cftoken : 56 bytes
      620764 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   bv_620833_58599060 : bv : 504 bytes
      [Variable Type : Variable Name : Size]
      STRUCT : auth : 232 bytes
      CFID=620833&CFTOKEN=58599060 : urltoken : 96 bytes
      BV_620833_58599060 : sessionid : 72 bytes
      58599060 : cftoken : 56 bytes
      620833 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620818_16094570 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620818&CFTOKEN=16094570 : urltoken : 96 bytes
      MICOMIMSA_620818_16094570 : sessionid : 88 bytes
      16094570 : cftoken : 56 bytes
      620818 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620811_50303269 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620811&CFTOKEN=50303269 : urltoken : 96 bytes
      MICOMIMSA_620811_50303269 : sessionid : 88 bytes
      50303269 : cftoken : 56 bytes
      620811 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620817_68843193 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620817&CFTOKEN=68843193 : urltoken : 96 bytes
      MICOMIMSA_620817_68843193 : sessionid : 88 bytes
      68843193 : cftoken : 56 bytes
      620817 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620835_82909315 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620835&CFTOKEN=82909315 : urltoken : 96 bytes
      MICOMIMSA_620835_82909315 : sessionid : 88 bytes
      82909315 : cftoken : 56 bytes
      620835 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620837_48954912 : MiComimsa : 1008 bytes
      [Variable Type : Variable Name : Size]
      STRUCT : auth : 624 bytes
      STRUCT : usuario : 152 bytes
      ARRAY : perfiles : 152 bytes
      CFID=620837&CFTOKEN=48954912 : urltoken : 96 bytes
      MICOMIMSA_620837_48954912 : sessionid : 88 bytes
      48954912 : cftoken : 56 bytes
      620837 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620826_45755482 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620826&CFTOKEN=45755482 : urltoken : 96 bytes
      MICOMIMSA_620826_45755482 : sessionid : 88 bytes
      45755482 : cftoken : 56 bytes
      620826 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620795_28314251 : MiComimsa : 1136 bytes
      [Variable Type : Variable Name : Size]
      STRUCT : auth : 592 bytes
      ARRAY : perfiles : 352 bytes
      STRUCT : usuario : 200 bytes
      CFID=620795&CFTOKEN=28314251 : urltoken : 96 bytes
      MICOMIMSA_620795_28314251 : sessionid : 88 bytes
      28314251 : cftoken : 56 bytes
      620795 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620829_95927183 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620829&CFTOKEN=95927183 : urltoken : 96 bytes
      MICOMIMSA_620829_95927183 : sessionid : 88 bytes
      95927183 : cftoken : 56 bytes
      620829 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620820_39067055 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620820&CFTOKEN=39067055 : urltoken : 96 bytes
      MICOMIMSA_620820_39067055 : sessionid : 88 bytes
      39067055 : cftoken : 56 bytes
      620820 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620839_71524632 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620839&CFTOKEN=71524632 : urltoken : 96 bytes
      MICOMIMSA_620839_71524632 : sessionid : 88 bytes
      71524632 : cftoken : 56 bytes
      620839 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620809_48255137 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620809&CFTOKEN=48255137 : urltoken : 96 bytes
      MICOMIMSA_620809_48255137 : sessionid : 88 bytes
      48255137 : cftoken : 56 bytes
      620809 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620802_32861440 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620802&CFTOKEN=32861440 : urltoken : 96 bytes
      MICOMIMSA_620802_32861440 : sessionid : 88 bytes
      32861440 : cftoken : 56 bytes
      620802 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620808_87629440 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620808&CFTOKEN=87629440 : urltoken : 96 bytes
      MICOMIMSA_620808_87629440 : sessionid : 88 bytes
      87629440 : cftoken : 56 bytes
      620808 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620838_28711131 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620838&CFTOKEN=28711131 : urltoken : 96 bytes
      MICOMIMSA_620838_28711131 : sessionid : 88 bytes
      28711131 : cftoken : 56 bytes
      620838 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620828_92134794 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620828&CFTOKEN=92134794 : urltoken : 96 bytes
      MICOMIMSA_620828_92134794 : sessionid : 88 bytes
      92134794 : cftoken : 56 bytes
      620828 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620825_76366611 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620825&CFTOKEN=76366611 : urltoken : 96 bytes
      MICOMIMSA_620825_76366611 : sessionid : 88 bytes
      76366611 : cftoken : 56 bytes
      620825 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620821_75994248 : MiComimsa : 992 bytes
      [Variable Type : Variable Name : Size]
      STRUCT : auth : 608 bytes
      STRUCT : usuario : 152 bytes
      ARRAY : perfiles : 152 bytes
      CFID=620821&CFTOKEN=75994248 : urltoken : 96 bytes
      MICOMIMSA_620821_75994248 : sessionid : 88 bytes
      75994248 : cftoken : 56 bytes
      620821 : cfid : 48 bytes
   [Session Id : Application Name :Session Size]
   MiComimsa_620816_44610515 : MiComimsa : 288 bytes
      [Variable Type : Variable Name : Size]
      CFID=620816&CFTOKEN=44610515 : urltoken : 96 bytes
      MICOMIMSA_620816_44610515 : sessionid : 88 bytes
      44610515 : cftoken : 56 bytes
      620816 : cfid : 48 bytes
Throttle Stats [Throttle Queue Size : Throttle Memory Used]
            0 : 0.0 megabytes
Query Cache Stats -
[Hit Ratio : Size : Count]
   0.0 : 0 bytes : 0
Cached Queries -
[Query Name : DSN : Size : TIme Executed : Time Taken : Line No : Function Name : Template Path]
DB Pool Stats -
[DSN :Open Conn Count : Total Conn Count : Max Con Count : Avg Open Conn Count : Avg Total Conn Count]
   extensiones : 0 : 0 : Unlimited : 0 : 0
   curriculumtest : 0 : 0 : Unlimited : 0 : 0
   Test_MiComimsa : 0 : 0 : Unlimited : 0 : 0
   SATDSN : 0 : 0 : Unlimited : 0 : 0
   arrendamiento : 0 : 0 : Unlimited : 0 : 0
   carlog : 0 : 0 : Unlimited : 0 : 0
   laboratorios : 0 : 0 : Unlimited : 0 : 0
   iso9000 : 0 : 0 : Unlimited : 0 : 0
   sca : 0 : 0 : Unlimited : 0 : 0
   cfcodeexplorer : 0 : 0 : Unlimited : 0 : 0
   CMIDocumentos : 5 : 6 : Unlimited : 0 : 2
   firmadocs : 0 : 0 : Unlimited : 0 : 0
   CurriculumsPITT : 0 : 0 : Unlimited : 0 : 0
   PORTALPLANEACION : 0 : 0 : Unlimited : 0 : 0
   PortalRH : 0 : 6 : Unlimited : 0 : 4
   FoodMart 2000 : 0 : 0 : Unlimited : 0 : 0
   sig_contabilidad : 0 : 1 : Unlimited : 0 : 0
   Bitacora_AJ : 0 : 0 : Unlimited : 0 : 0
   cfdocexamples : 0 : 0 : Unlimited : 0 : 0
   pnt : 0 : 0 : Unlimited : 0 : 0
   encuestaPITT : 0 : 0 : Unlimited : 0 : 0
   AgendaPresidencial : 0 : 0 : Unlimited : 0 : 0
   CodigoConducta-quiz : 0 : 0 : Unlimited : 0 : 0
   vinculacion : 0 : 0 : Unlimited : 0 : 0
   Dir2 : 0 : 0 : Unlimited : 0 : 0
   SIG_Test : 0 : 0 : Unlimited : 0 : 0
   filemanager-gat : 0 : 0 : Unlimited : 0 : 0
   filiacion : 0 : 0 : Unlimited : 0 : 0
   BSC : 0 : 0 : Unlimited : 0 : 0
   noticias : 0 : 0 : Unlimited : 0 : 0
   sigel : 0 : 0 : Unlimited : 0 : 0
   SIID_test : 0 : 0 : Unlimited : 0 : 0
   dimm : 0 : 0 : Unlimited : 0 : 0
   Portal_auditores : 0 : 0 : Unlimited : 0 : 0
   Xtreme Sample Database : 0 : 0 : Unlimited : 0 : 0
   testisocmi : 0 : 0 : Unlimited : 0 : 0
   bit2 : 0 : 0 : Unlimited : 0 : 0
   DocumentosFEA : 0 : 1 : Unlimited : 0 : 0
   cmm : 0 : 0 : Unlimited : 0 : 0
   ra_sig : 0 : 2 : Unlimited : 0 : 1
   cfbookclub : 0 : 0 : Unlimited : 0 : 0
   foros_GPC : 0 : 0 : Unlimited : 0 : 0
   ows : 0 : 0 : Unlimited : 0 : 0
   guiasimple : 0 : 0 : Unlimited : 0 : 0
   BSC_SQ : 0 : 0 : Unlimited : 0 : 0
   dst : 0 : 0 : Unlimited : 0 : 0
   cfusionlog : 0 : 0 : Unlimited : 0 : 0
   MobileDashboard : 0 : 0 : Unlimited : 0 : 0
   RA_Intra : 0 : 2 : Unlimited : 0 : 1
   cfartgallery : 0 : 0 : Unlimited : 0 : 0
   inventarios : 0 : 0 : Unlimited : 0 : 0
   indicadores : 0 : 0 : Unlimited : 0 : 0
   ForosDTT : 0 : 0 : Unlimited : 0 : 0
   scdwalmi : 0 : 2 : Unlimited : 0 : 1
   ForosSoldadura : 0 : 0 : Unlimited : 0 : 0
   LocalServer : 0 : 0 : Unlimited : 0 : 0
   curriculum : 0 : 1 : Unlimited : 0 : 0
   ForosClasificados : 0 : 0 : Unlimited : 0 : 0
   foros_PlanEstrategica : 0 : 0 : Unlimited : 0 : 0
   bv : 0 : 1 : Unlimited : 0 : 0
   ssdog : 0 : 0 : Unlimited : 0 : 0
   Bitacora_SGIyD : 0 : 0 : Unlimited : 0 : 0
   SIG : 0 : 1 : Unlimited : 0 : 0
   satisfaccioncte : 0 : 0 : Unlimited : 0 : 0
   IMD : 0 : 0 : Unlimited : 0 : 0
   capacitacion : 0 : 0 : Unlimited : 0 : 0
   vpnet : 0 : 0 : Unlimited : 0 : 0
   portal_prestacion : 0 : 2 : Unlimited : 0 : 2
   server : 0 : 4 : Unlimited : 0 : 3
   capacitacion_foros : 0 : 0 : Unlimited : 0 : 0
   indica2 : 0 : 0 : Unlimited : 0 : 0
   votacion : 0 : 0 : Unlimited : 0 : 0
Thread jrpp-331 request type - TEMPLATE REQUEST
*Template Path - E:\inetpub\wwwroot\CMIMobileServices\CMIMobileSigner\POSTListenerTest.cfm
*Request Parameters - {BBP=[Ljava.lang.String;@14bb595, tID=[Ljava.lang.String;@17e541f, action=[Ljava.lang.String;@c4ce59, fContent=[Ljava.lang.String;@c75e7c, eLink=[Ljava.lang.String;@10c33ce, recipient=[Ljava.lang.String;@1d36a4}
*Request Method - POST
*Client IP address - 172.16.0.36
*Thread elapsed time - 86263 milliseconds
*Application Name -
*request/local/variables scope variables
      [Scope Type: Type : Name : Size]
      -APPLICATION : SIMPLE : FILECONTENT : 189120 bytes
      -APPLICATION : SIMPLE : PAGENAME : 88 bytes
      -APPLICATION : SIMPLE : KEY : 56 bytes
      -APPLICATION : SIMPLE : RESPONSE : 40 bytes
*CF stack -
E:\inetpub\wwwroot\CMIMobileServices\CMIMobileSigner\POSTListenerTest.cfm
at E:\inetpub\wwwroot\CMIMobileServices\CMIMobileSigner\POSTListenerTest.cfm
*Currently executing queries -
Thread jrpp-310 request type - TEMPLATE REQUEST
*Template Path - E:\inetpub\wwwroot\CMIMobileServices\CMIMobileSigner\POSTListenerTest.cfm
*Request Parameters - {BBP=[Ljava.lang.String;@1bf8ca4, tID=[Ljava.lang.String;@aa82a7, action=[Ljava.lang.String;@67d8a6, fContent=[Ljava.lang.String;@1c0abbc, eLink=[Ljava.lang.String;@4ae55d, recipient=[Ljava.lang.String;@11865d9}
*Request Method - POST
*Client IP address - 172.16.0.36
*Thread elapsed time - 37611 milliseconds
*Application Name -
*request/local/variables scope variables
      [Scope Type: Type : Name : Size]
      -APPLICATION : SIMPLE : FILECONTENT : 190216 bytes
      -APPLICATION : SIMPLE : PAGENAME : 88 bytes
      -APPLICATION : SIMPLE : KEY : 56 bytes
      -APPLICATION : SIMPLE : RESPONSE : 40 bytes
*CF stack -
E:\inetpub\wwwroot\CMIMobileServices\CMIMobileSigner\POSTListenerTest.cfm
at E:\inetpub\wwwroot\CMIMobileServices\CMIMobileSigner\POSTListenerTest.cfm
*Currently executing queries -
Thread jrpp-319 request type - TEMPLATE REQUEST
*Template Path - E:\inetpub\wwwroot\CMIMobileServices\CMIMobileSigner\POSTListenerTest.cfm
*Request Parameters - {BBP=[Ljava.lang.String;@c6bd69, tID=[Ljava.lang.String;@1bd4b5b, action=[Ljava.lang.String;@9e7eba, fContent=[Ljava.lang.String;@191eddc, eLink=[Ljava.lang.String;@1971194, recipient=[Ljava.lang.String;@1031bbf}
*Request Method - POST
*Client IP address - 172.16.0.36
*Thread elapsed time - 95001 milliseconds
*Application Name -
*request/local/variables scope variables
      [Scope Type: Type : Name : Size]
      -APPLICATION : SIMPLE : FILECONTENT : 167208 bytes
      -APPLICATION : SIMPLE : PAGENAME : 88 bytes
      -APPLICATION : SIMPLE : KEY : 56 bytes
      -APPLICATION : SIMPLE : RESPONSE : 40 bytes
*CF stack -
E:\inetpub\wwwroot\CMIMobileServices\CMIMobileSigner\POSTListenerTest.cfm
at E:\inetpub\wwwroot\CMIMobileServices\CMIMobileSigner\POSTListenerTest.cfm
*Currently executing queries -
Thread jrpp-336 request type - TEMPLATE REQUEST
*Template Path - E:\inetpub\wwwroot\CMIMobileServices\CMIMobileSigner\POSTListenerTest.cfm
*Request Parameters - {BBP=[Ljava.lang.String;@187f846, tID=[Ljava.lang.String;@1bcf4de, action=[Ljava.lang.String;@703f9d, fContent=[Ljava.lang.String;@160808b, eLink=[Ljava.lang.String;@9760da, recipient=[Ljava.lang.String;@57ab64}
*Request Method - POST
*Client IP address - 172.16.0.36
*Thread elapsed time - 76250 milliseconds
*Application Name -
*request/local/variables scope variables
      [Scope Type: Type : Name : Size]
      -APPLICATION : SIMPLE : FILECONTENT : 185608 bytes
      -APPLICATION : SIMPLE : PAGENAME : 88 bytes
      -APPLICATION : SIMPLE : KEY : 56 bytes
      -APPLICATION : SIMPLE : RESPONSE : 40 bytes
*CF stack -
E:\inetpub\wwwroot\CMIMobileServices\CMIMobileSigner\POSTListenerTest.cfm
at E:\inetpub\wwwroot\CMIMobileServices\CMIMobileSigner\POSTListenerTest.cfm
*Currently executing queries -
Thread jrpp-314 request type - TEMPLATE REQUEST
*Template Path - E:\inetpub\wwwroot\CMIMobileServices\CMIMobileSigner\POSTListenerTest.cfm
*Request Parameters - {BBP=[Ljava.lang.String;@10d867a, tID=[Ljava.lang.String;@f7b83a, action=[Ljava.lang.String;@1601471, fContent=[Ljava.lang.String;@de17d5, eLink=[Ljava.lang.String;@eeb6ef, recipient=[Ljava.lang.String;@2c338c}
*Request Method - POST
*Client IP address - 172.16.0.36
*Thread elapsed time - 50289 milliseconds
*Application Name -
*request/local/variables scope variables
      [Scope Type: Type : Name : Size]
      -APPLICATION : SIMPLE : FILECONTENT : 218808 bytes
      -APPLICATION : SIMPLE : PAGENAME : 88 bytes
      -APPLICATION : SIMPLE : KEY : 56 bytes
      -APPLICATION : SIMPLE : RESPONSE : 40 bytes
*CF stack -
E:\inetpub\wwwroot\CMIMobileServices\CMIMobileSigner\POSTListenerTest.cfm
at E:\inetpub\wwwroot\CMIMobileServices\CMIMobileSigner\POSTListenerTest.cfm
*Currently executing queries -
Thread jrpp-315 request type - TEMPLATE REQUEST
*Template Path - E:\inetpub\wwwroot\CMIMobileServices\CMIMobileSigner\POSTListenerTest.cfm
*Request Parameters - {BBP=[Ljava.lang.String;@d029df, tID=[Ljava.lang.String;@6d004d, action=[Ljava.lang.String;@2ee14d, fContent=[Ljava.lang.String;@1c98759, eLink=[Ljava.lang.String;@1d50f08, recipient=[Ljava.lang.String;@ce0137}
*Request Method - POST
*Client IP address - 172.16.0.36
*Thread elapsed time - 65402 milliseconds
*Application Name -
*request/local/variables scope variables
      [Scope Type: Type : Name : Size]
      -APPLICATION : SIMPLE : FILECONTENT : 182016 bytes
      -APPLICATION : SIMPLE : PAGENAME : 88 bytes
      -APPLICATION : SIMPLE : KEY : 56 bytes
      -APPLICATION : SIMPLE : RESPONSE : 40 bytes
*CF stack -
E:\inetpub\wwwroot\CMIMobileServices\CMIMobileSigner\POSTListenerTest.cfm
at E:\inetpub\wwwroot\CMIMobileServices\CMIMobileSigner\POSTListenerTest.cfm
*Currently executing queries -
Thread jrpp-317 request type - WEB SERVICE REQUEST
*Template Path - C:\ColdFusion8\wwwroot\Webservices\wsCF\wsMobileSigner.cfc uploadSignedDocument
*Request Parameters - {}
*Request Method - POST
*Client IP address - 172.16.0.3
*Thread elapsed time - 15092 milliseconds
*Application Name -
*request/local/variables scope variables
      [Scope Type: Type : Name : Size]
      -APPLICATION : CFC : THIS : 1728 bytes
      -APPLICATION : CFC : THIS : 1728 bytes
      -APPLICATION : CFC : THIS : 1728 bytes
      -APPLICATION : CFC : OAPPROVALFLOWMGR : 1728 bytes
      -APPLICATION : CFC : OAPPROVALFLOW : 1000 bytes
      -APPLICATION : CFC : THIS : 1000 bytes
      -APPLICATION : CFC : OOBJECT : 1000 bytes
      -APPLICATION : CFC : THIS : 1000 bytes
      -APPLICATION : CFC : THIS : 1000 bytes
      -APPLICATION : CFC : THIS : 832 bytes
      -APPLICATION : CFC : THIS : 832 bytes
      -APPLICATION : CFC : ODOCUMENTMANAGER : 832 bytes
      -APPLICATION : CFC : THIS : 832 bytes
      -APPLICATION : CFC : THIS : 832 bytes
      -APPLICATION : CFC : THIS : 832 bytes
      -APPLICATION : CFC : THIS : 832 bytes
      -APPLICATION : CFC : THIS : 744 bytes
      -APPLICATION : CFC : PARAMETERS : 744 bytes
      -APPLICATION : CFC : THIS : 744 bytes
      -APPLICATION : CFC : THIS : 744 bytes
      -APPLICATION : STRUCT : ENTRIES : 744 bytes
      -APPLICATION : CFC : OPARAMS : 744 bytes
      -APPLICATION : CFC : THIS : 728 bytes
      -APPLICATION : CFC : OAPPROVALFLOWGTW : 728 bytes
      -APPLICATION : CFC : THIS : 728 bytes
      -APPLICATION : CFC : THIS : 728 bytes
      -APPLICATION : CFC : THIS : 728 bytes
      -APPLICATION : CFC : THIS : 696 bytes
      -APPLICATION : CFC : THIS : 696 bytes
      -APPLICATION : CFC : OSIGNATUREMGR : 696 bytes
      -APPLICATION : CFC : THIS : 696 bytes
      -APPLICATION : CFC : THIS : 680 bytes
      -APPLICATION : CFC : THIS : 680 bytes
      -APPLICATION : CFC : THIS : 680 bytes
      -APPLICATION : CFC : OEMAILLINKDAO : 680 bytes
      -APPLICATION : CFC : THIS : 536 bytes
      -APPLICATION : CFC : THIS : 536 bytes
      -APPLICATION : CFC : THIS : 536 bytes
      -APPLICATION : CFC : THIS : 536 bytes
      -APPLICATION : CFC : THIS : 536 bytes
      -APPLICATION : CFC : THIS : 536 bytes
      -APPLICATION : CFC : THIS : 536 bytes
      -APPLICATION : CFC : THIS : 536 bytes
      -APPLICATION : CFC : THIS : 536 bytes
      -APPLICATION : CFC : OEMAILLINK : 536 bytes
      -APPLICATION : CFC : THIS : 536 bytes
      -APPLICATION : CFC : THIS : 536 bytes
      -APPLICATION : STRUCT : SIGNATURESTRUCT : 408 bytes
      -APPLICATION : STRUCT : LASTSIGNATURE : 408 bytes
      -APPLICATION : STRUCT : lastSignature : 408 bytes
      -APPLICATION : STRUCT : RETURNVALUE : 408 bytes
      -APPLICATION : QUERY : QRYRESULT : 392 bytes
      -APPLICATION : QUERY : QRYREAD : 392 bytes
      -APPLICATION : SIMPLE : lastSignature : 384 bytes
      -APPLICATION : SIMPLE : LASTSIGNATURE : 384 bytes
      -APPLICATION : CFC : THIS : 384 bytes
      -APPLICATION : QUERY : QRYREAD : 344 bytes
      -APPLICATION : QUERY : RESULT : 344 bytes
      -APPLICATION : CFC : THIS : 296 bytes
      -APPLICATION : CFC : OSOLICITUDFACTORY : 296 bytes
      -APPLICATION : CFC : THIS : 296 bytes
      -APPLICATION : SIMPLE : DOCPATH : 248 bytes
      -APPLICATION : CFC : THIS : 232 bytes
      -APPLICATION : CFC : LOGGER : 232 bytes
      -APPLICATION : SIMPLE : MAILPATH : 232 bytes
      -APPLICATION : CFC : THIS : 232 bytes
      -APPLICATION : CFC : LOGGER : 232 bytes
      -APPLICATION : CFC : THIS : 232 bytes
      -APPLICATION : CFC : THIS : 232 bytes
      -APPLICATION : CFC : THIS : 232 bytes
      -APPLICATION : CFC : OSOLICITUD : 232 bytes
      -APPLICATION : CFC : THIS : 232 bytes
      -APPLICATION : CFC : THIS : 232 bytes
      -APPLICATION : CFC : LOGGER : 232 bytes
      -APPLICATION : CFC : LOGGER : 232 bytes
      -APPLICATION : CFC : LOGGER : 232 bytes
      -APPLICATION : CFC : LOGGER : 232 bytes
      -APPLICATION : CFC : LOGGER : 232 bytes
      -APPLICATION : CFC : LOGGER : 232 bytes
      -APPLICATION : CFC : THIS : 232 bytes
      -APPLICATION : CFC : LOGGER : 232 bytes
      -APPLICATION : CFC : LOGGER : 232 bytes
      -APPLICATION : CFC : THIS : 232 bytes
      -APPLICATION : CFC : OOBJECT : 232 bytes
      -APPLICATION : SIMPLE : PATRON : 184 bytes
      -APPLICATION : SIMPLE : PATH : 176 bytes
      -APPLICATION : SIMPLE : TRACKID : 112 bytes
      -APPLICATION : ARRAY : MATCH : 96 bytes
      -APPLICATION : SIMPLE : TRACKID : 96 bytes
      -APPLICATION : SIMPLE : FILEPATH : 88 bytes
      -APPLICATION : SIMPLE : FILEPATH : 88 bytes
      -APPLICATION : SIMPLE : mailTo : 80 bytes
      -APPLICATION : SIMPLE : BACKUPFILENAME : 72 bytes
      -APPLICATION : SIMPLE : LOGFILE : 72 bytes
      -APPLICATION : SIMPLE : LOGFILE : 72 bytes
      -APPLICATION : SIMPLE : HOST : 72 bytes
      -APPLICATION : SIMPLE : FILEPATH : 64 bytes
      -APPLICATION : SIMPLE : FILENAME : 64 bytes
      -APPLICATION : SIMPLE : DSN : 64 bytes
      -APPLICATION : SIMPLE : PATH : 64 bytes
      -APPLICATION : SIMPLE : DSN : 64 bytes
      -APPLICATION : SIMPLE : BBPIN : 56 bytes
      -APPLICATION : SIMPLE : HASHALGORITHM : 56 bytes
      -APPLICATION : SIMPLE : RELATIVEPATH : 48 bytes
      -APPLICATION : SIMPLE : action : 48 bytes
      -APPLICATION : SIMPLE : IdSolicitud : 48 bytes
      -APPLICATION : SIMPLE : FOLIO : 48 bytes
      -APPLICATION : SIMPLE : LOGGING : 48 bytes
      -APPLICATION : SIMPLE : LOGGING : 48 bytes
      -APPLICATION : SIMPLE : APP : 48 bytes
      -APPLICATION : SIMPLE : ID : 48 bytes
      -APPLICATION : SIMPLE : ID : 48 bytes
      -APPLICATION : SIMPLE : folio : 48 bytes
      -APPLICATION : SIMPLE : FOLIO : 48 bytes
      -APPLICATION : SIMPLE : FILENAME : 48 bytes
      -APPLICATION : SIMPLE : EXTENSION : 48 bytes
      -APPLICATION : SIMPLE : PATCHVERSION : 40 bytes
      -APPLICATION : SIMPLE : MAILPATH : 40 bytes
      -APPLICATION : SIMPLE : OAPPROVALFLOWGTW : 40 bytes
      -APPLICATION : SIMPLE : DSN : 40 bytes
      -APPLICATION : SIMPLE : QRYREAD : 40 bytes
      -APPLICATION : SIMPLE : FOLIO : 40 bytes
      -APPLICATION : SIMPLE : MINORVERSION : 40 bytes
      -APPLICATION : SIMPLE : OSOLICITUD : 40 bytes
      -APPLICATION : SIMPLE : OWEBSERVICE : 40 bytes
      -APPLICATION : SIMPLE : SIGNERSANDSIGNATURES : 40 bytes
      -APPLICATION : SIMPLE : IdApp : 40 bytes
      -APPLICATION : SIMPLE : DECODED : 40 bytes
      -APPLICATION : SIMPLE : BACKUPFILENAME : 40 bytes
      -APPLICATION : SIMPLE : HASHALGORITHM : 40 bytes
      -APPLICATION : SIMPLE : EXTENSION : 40 bytes
      -APPLICATION : SIMPLE : FOLIO : 40 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 40 bytes
      -APPLICATION : SIMPLE : ID : 40 bytes
      -APPLICATION : SIMPLE : PATH : 40 bytes
      -APPLICATION : SIMPLE : ID : 40 bytes
      -APPLICATION : SIMPLE : ENTRIES : 40 bytes
      -APPLICATION : SIMPLE : OAPPROVALFLOW : 40 bytes
      -APPLICATION : SIMPLE : OERRORHANDLER : 40 bytes
      -APPLICATION : SIMPLE : XMLFROMQRY : 40 bytes
      -APPLICATION : SIMPLE : SUPPORT : 40 bytes
      -APPLICATION : SIMPLE : SECUENCIA : 40 bytes
      -APPLICATION : SIMPLE : ACTIVO : 40 bytes
      -APPLICATION : SIMPLE : MAJORVERSION : 40 bytes
      -APPLICATION : SIMPLE : IDAPP : 40 bytes
      -APPLICATION : SIMPLE : FOLIO : 40 bytes
      -APPLICATION : SIMPLE : TITLE : 40 bytes
      -APPLICATION : SIMPLE : RESULT : 40 bytes
      -APPLICATION : SIMPLE : OUPLOADREQUEST : 40 bytes
      -APPLICATION : SIMPLE : LOGGER : 40 bytes
      -APPLICATION : SIMPLE : IDAPP : 40 bytes
      -APPLICATION : SIMPLE : OPKCS7 : 40 bytes
      -APPLICATION : SIMPLE : FILENAME : 40 bytes
      -APPLICATION : SIMPLE : FECHA : 40 bytes
      -APPLICATION : SIMPLE : DOCPATH : 40 bytes
      -APPLICATION : SIMPLE : PARAMETERS : 40 bytes
      -APPLICATION : SIMPLE : RESULT : 40 bytes
      -APPLICATION : SIMPLE : OMULTISIGNERMANAGER : 40 bytes
      -APPLICATION : SIMPLE : APP : 40 bytes
      -APPLICATION : SIMPLE : FILENAME : 40 bytes
      -APPLICATION : SIMPLE : timestamp : 24 bytes
      -APPLICATION : SIMPLE : MAXDATE : 24 bytes
      -APPLICATION : SIMPLE : ExecutionTime : 16 bytes
      -APPLICATION : SIMPLE : IdEmpleado : 16 bytes
      -APPLICATION : SIMPLE : IIDX : 16 bytes
      -APPLICATION : STRUCT : CFSTOREDPROC : 16 bytes
      -APPLICATION : SIMPLE : CFQUERY.EXECUTIONTIME : 16 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : SIMPLE : FECHA : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : LASTSIGNATURE : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : SIMPLE : FECHA : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
*CF stack -
C:\ColdFusion8\CustomTags\com\comimsa\blackberry\feamobile\model\ThirdPartyApprovalFlow.cf c execute()
at C:\ColdFusion8\CustomTags\com\comimsa\blackberry\feamobile\ApprovalFlowManager.cfc start() : 56
at C:\ColdFusion8\CustomTags\com\comimsa\feaframework\DocumentManager.cfc existsLocalFile() : 79
at C:\ColdFusion8\CustomTags\com\comimsa\feaframework\DocumentManager.cfc existsFile() : 111
at C:\ColdFusion8\CustomTags\com\comimsa\blackberry\feamobile\model\EmailLink.cfc isAuthentic() : 52
at C:\ColdFusion8\wwwroot\Webservices\wsCF\wsMobileSigner.cfc uploadSignedDocument() : 40
*Currently executing queries -
Thread jrpp-333 request type - WEB SERVICE REQUEST
*Template Path - C:\ColdFusion8\wwwroot\Webservices\wsCF\wsMobileSigner.cfc uploadSignedDocument
*Request Parameters - {}
*Request Method - POST
*Client IP address - 172.16.0.3
*Thread elapsed time - 87170 milliseconds
*Application Name -
*request/local/variables scope variables
      [Scope Type: Type : Name : Size]
      -APPLICATION : CFC : THIS : 1776 bytes
      -APPLICATION : CFC : THIS : 1776 bytes
      -APPLICATION : CFC : THIS : 1776 bytes
      -APPLICATION : CFC : OAPPROVALFLOWMGR : 1776 bytes
      -APPLICATION : CFC : OAPPROVALFLOW : 1024 bytes
      -APPLICATION : CFC : THIS : 1024 bytes
      -APPLICATION : CFC : OOBJECT : 1024 bytes
      -APPLICATION : CFC : THIS : 1024 bytes
      -APPLICATION : CFC : THIS : 1024 bytes
      -APPLICATION : CFC : THIS : 840 bytes
      -APPLICATION : CFC : THIS : 840 bytes
      -APPLICATION : CFC : ODOCUMENTMANAGER : 840 bytes
      -APPLICATION : CFC : THIS : 840 bytes
      -APPLICATION : CFC : THIS : 840 bytes
      -APPLICATION : CFC : THIS : 840 bytes
      -APPLICATION : CFC : THIS : 840 bytes
      -APPLICATION : CFC : THIS : 760 bytes
      -APPLICATION : CFC : PARAMETERS : 760 bytes
      -APPLICATION : CFC : THIS : 760 bytes
      -APPLICATION : CFC : THIS : 760 bytes
      -APPLICATION : STRUCT : ENTRIES : 760 bytes
      -APPLICATION : CFC : OPARAMS : 760 bytes
      -APPLICATION : CFC : THIS : 752 bytes
      -APPLICATION : CFC : OAPPROVALFLOWGTW : 752 bytes
      -APPLICATION : CFC : THIS : 752 bytes
      -APPLICATION : CFC : THIS : 752 bytes
      -APPLICATION : CFC : THIS : 752 bytes
      -APPLICATION : CFC : THIS : 704 bytes
      -APPLICATION : CFC : THIS : 704 bytes
      -APPLICATION : CFC : OSIGNATUREMGR : 704 bytes
      -APPLICATION : CFC : THIS : 704 bytes
      -APPLICATION : CFC : THIS : 696 bytes
      -APPLICATION : CFC : THIS : 696 bytes
      -APPLICATION : CFC : THIS : 696 bytes
      -APPLICATION : CFC : OEMAILLINKDAO : 696 bytes
      -APPLICATION : CFC : THIS : 560 bytes
      -APPLICATION : CFC : THIS : 560 bytes
      -APPLICATION : CFC : THIS : 560 bytes
      -APPLICATION : CFC : THIS : 560 bytes
      -APPLICATION : CFC : THIS : 560 bytes
      -APPLICATION : CFC : THIS : 560 bytes
      -APPLICATION : CFC : THIS : 560 bytes
      -APPLICATION : CFC : THIS : 560 bytes
      -APPLICATION : CFC : THIS : 560 bytes
      -APPLICATION : CFC : OEMAILLINK : 560 bytes
      -APPLICATION : CFC : THIS : 560 bytes
      -APPLICATION : CFC : THIS : 560 bytes
      -APPLICATION : QUERY : QRYRESULT : 408 bytes
      -APPLICATION : STRUCT : SIGNATURESTRUCT : 408 bytes
      -APPLICATION : STRUCT : LASTSIGNATURE : 408 bytes
      -APPLICATION : STRUCT : lastSignature : 408 bytes
      -APPLICATION : STRUCT : RETURNVALUE : 408 bytes
      -APPLICATION : QUERY : QRYREAD : 408 bytes
      -APPLICATION : SIMPLE : lastSignature : 384 bytes
      -APPLICATION : SIMPLE : LASTSIGNATURE : 384 bytes
      -APPLICATION : CFC : THIS : 384 bytes
      -APPLICATION : QUERY : QRYREAD : 352 bytes
      -APPLICATION : QUERY : RESULT : 352 bytes
      -APPLICATION : CFC : THIS : 304 bytes
      -APPLICATION : CFC : OSOLICITUDFACTORY : 304 bytes
      -APPLICATION : CFC : THIS : 304 bytes
      -APPLICATION : CFC : THIS : 256 bytes
      -APPLICATION : CFC : THIS : 256 bytes
      -APPLICATION : CFC : THIS : 256 bytes
      -APPLICATION : CFC : OSOLICITUD : 256 bytes
      -APPLICATION : CFC : THIS : 256 bytes
      -APPLICATION : CFC : THIS : 256 bytes
      -APPLICATION : CFC : OOBJECT : 256 bytes
      -APPLICATION : SIMPLE : DOCPATH : 248 bytes
      -APPLICATION : CFC : LOGGER : 232 bytes
      -APPLICATION : SIMPLE : MAILPATH : 232 bytes
      -APPLICATION : CFC : THIS : 232 bytes
      -APPLICATION : CFC : LOGGER : 232 bytes
      -APPLICATION : CFC : THIS : 232 bytes
      -APPLICATION : CFC : THIS : 232 bytes
      -APPLICATION : CFC : THIS : 232 bytes
      -APPLICATION : CFC : LOGGER : 232 bytes
      -APPLICATION : CFC : LOGGER : 232 bytes
      -APPLICATION : CFC : LOGGER : 232 bytes
      -APPLICATION : CFC : LOGGER : 232 bytes
      -APPLICATION : CFC : LOGGER : 232 bytes
      -APPLICATION : CFC : LOGGER : 232 bytes
      -APPLICATION : CFC : LOGGER : 232 bytes
      -APPLICATION : CFC : LOGGER : 232 bytes
      -APPLICATION : SIMPLE : PATRON : 184 bytes
      -APPLICATION : SIMPLE : PATH : 176 bytes
      -APPLICATION : SIMPLE : TRACKID : 112 bytes
      -APPLICATION : ARRAY : MATCH : 104 bytes
      -APPLICATION : SIMPLE : TRACKID : 104 bytes
      -APPLICATION : SIMPLE : FILEPATH : 88 bytes
      -APPLICATION : SIMPLE : FILEPATH : 88 bytes
      -APPLICATION : SIMPLE : BACKUPFILENAME : 80 bytes
      -APPLICATION : SIMPLE : mailTo : 80 bytes
      -APPLICATION : SIMPLE : FILENAME : 72 bytes
      -APPLICATION : SIMPLE : LOGFILE : 72 bytes
      -APPLICATION : SIMPLE : LOGFILE : 72 bytes
      -APPLICATION : SIMPLE : HOST : 72 bytes
      -APPLICATION : SIMPLE : FILEPATH : 64 bytes
      -APPLICATION : SIMPLE : DSN : 64 bytes
      -APPLICATION : SIMPLE : PATH : 64 bytes
      -APPLICATION : SIMPLE : DSN : 64 bytes
      -APPLICATION : SIMPLE : IdSolicitud : 56 bytes
      -APPLICATION : SIMPLE : FOLIO : 56 bytes
      -APPLICATION : SIMPLE : BBPIN : 56 bytes
      -APPLICATION : SIMPLE : ID : 56 bytes
      -APPLICATION : SIMPLE : folio : 56 bytes
      -APPLICATION : SIMPLE : HASHALGORITHM : 56 bytes
      -APPLICATION : SIMPLE : FOLIO : 56 bytes
      -APPLICATION : SIMPLE : FILENAME : 56 bytes
      -APPLICATION : SIMPLE : RELATIVEPATH : 48 bytes
      -APPLICATION : SIMPLE : action : 48 bytes
      -APPLICATION : SIMPLE : LOGGING : 48 bytes
      -APPLICATION : SIMPLE : LOGGING : 48 bytes
      -APPLICATION : SIMPLE : APP : 48 bytes
      -APPLICATION : SIMPLE : ID : 48 bytes
      -APPLICATION : SIMPLE : EXTENSION : 48 bytes
      -APPLICATION : SIMPLE : PATCHVERSION : 40 bytes
      -APPLICATION : SIMPLE : MAILPATH : 40 bytes
      -APPLICATION : SIMPLE : OAPPROVALFLOWGTW : 40 bytes
      -APPLICATION : SIMPLE : DSN : 40 bytes
      -APPLICATION : SIMPLE : QRYREAD : 40 bytes
      -APPLICATION : SIMPLE : FOLIO : 40 bytes
      -APPLICATION : SIMPLE : MINORVERSION : 40 bytes
      -APPLICATION : SIMPLE : OSOLICITUD : 40 bytes
      -APPLICATION : SIMPLE : OWEBSERVICE : 40 bytes
      -APPLICATION : SIMPLE : SIGNERSANDSIGNATURES : 40 bytes
      -APPLICATION : SIMPLE : IdApp : 40 bytes
      -APPLICATION : SIMPLE : DECODED : 40 bytes
      -APPLICATION : SIMPLE : BACKUPFILENAME : 40 bytes
      -APPLICATION : SIMPLE : HASHALGORITHM : 40 bytes
      -APPLICATION : SIMPLE : EXTENSION : 40 bytes
      -APPLICATION : SIMPLE : FOLIO : 40 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 40 bytes
      -APPLICATION : SIMPLE : ID : 40 bytes
      -APPLICATION : SIMPLE : PATH : 40 bytes
      -APPLICATION : SIMPLE : ID : 40 bytes
      -APPLICATION : SIMPLE : ENTRIES : 40 bytes
      -APPLICATION : SIMPLE : OAPPROVALFLOW : 40 bytes
      -APPLICATION : SIMPLE : OERRORHANDLER : 40 bytes
      -APPLICATION : SIMPLE : XMLFROMQRY : 40 bytes
      -APPLICATION : SIMPLE : SUPPORT : 40 bytes
      -APPLICATION : SIMPLE : SECUENCIA : 40 bytes
      -APPLICATION : SIMPLE : ACTIVO : 40 bytes
      -APPLICATION : SIMPLE : MAJORVERSION : 40 bytes
      -APPLICATION : SIMPLE : IDAPP : 40 bytes
      -APPLICATION : SIMPLE : FOLIO : 40 bytes
      -APPLICATION : SIMPLE : TITLE : 40 bytes
      -APPLICATION : SIMPLE : RESULT : 40 bytes
      -APPLICATION : SIMPLE : OUPLOADREQUEST : 40 bytes
      -APPLICATION : SIMPLE : LOGGER : 40 bytes
      -APPLICATION : SIMPLE : IDAPP : 40 bytes
      -APPLICATION : SIMPLE : OPKCS7 : 40 bytes
      -APPLICATION : SIMPLE : FILENAME : 40 bytes
      -APPLICATION : SIMPLE : FECHA : 40 bytes
      -APPLICATION : SIMPLE : DOCPATH : 40 bytes
      -APPLICATION : SIMPLE : PARAMETERS : 40 bytes
      -APPLICATION : SIMPLE : RESULT : 40 bytes
      -APPLICATION : SIMPLE : OMULTISIGNERMANAGER : 40 bytes
      -APPLICATION : SIMPLE : APP : 40 bytes
      -APPLICATION : SIMPLE : FILENAME : 40 bytes
      -APPLICATION : SIMPLE : timestamp : 24 bytes
      -APPLICATION : SIMPLE : MAXDATE : 24 bytes
      -APPLICATION : SIMPLE : ExecutionTime : 16 bytes
      -APPLICATION : SIMPLE : IdEmpleado : 16 bytes
      -APPLICATION : SIMPLE : IIDX : 16 bytes
      -APPLICATION : STRUCT : CFSTOREDPROC : 16 bytes
      -APPLICATION : SIMPLE : CFQUERY.EXECUTIONTIME : 16 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APPLICATION : STRUCT : ARGUMENTS : 0 bytes
      -APP

On the Win 08 r2 64 bit CF8 32 bit server I was able to install both jdk-6u27-windows-i586.exe and jdk-6u27-windows-x64.exe concurrently.
This worked:
# VM configuration
#java.home=C:/ColdFusion8/runtime/jre
java.home=C:/Java32/jdk1.6.0_27/jre
#java.home=C:/Program Files/Java/jdk1.6.0_27/jre
In part - CFadmin > Server Settings > Settings Summary
Server Details
Server Product ColdFusion
Version 8,0,0,176276
Edition Standard
Operating System Windows Server 2008 R2
OS Version 6.1
JVM Details
Java Version 1.6.0_27
Java Vendor Sun Microsystems Inc.
Java Vendor URL http://java.sun.com/
Java Home C:\Java32\jdk1.6.0_27\jre
User Home C:\
User Dir C:\ColdFusion8\runtime\bin
Java VM Specification Version 1.0
Java VM Specification Vendor Sun Microsystems Inc.
Java VM Specification Name Java Virtual Machine Specification
Java VM Version 20.2-b06
Java VM Vendor Sun Microsystems Inc.
Java VM Name Java HotSpot(TM) Server VM
Java Specification Version 1.6
This failed:
# VM configuration
#java.home=C:/ColdFusion8/runtime/jre
#java.home=C:/Java32/jdk1.6.0_27/jre
java.home=C:/Program Files/Java/jdk1.6.0_27/jre
Where CF8\runtime\logs\OUT log reports:
Error loading: C:/Program Files/Java/jdk1.6.0_27/jre\bin\server\jvm.dll
Error loading: C:/Program Files/Java/jdk1.6.0_27/jre\bin\server\jvm.dll
I thought CF8 32 bit would struggle with a 64 bit Java. Only had a short time window to try this so did not do any further experiments with trying to make the 64 bit Java function with CF8 like moving or swapping other DLL files around.
Not sure that helps you much since you said the 32 bit JDK did not install. I suppose I have replicated what you found that CF8 got the same startup problem you saw with 64 bit JDK.
What else can I suggest? In my case the particular site was working well CF8 with 1.6.0_04 JVM. The JVM had some tuned values applied to the minimum and maximum memory heap and non-heap values as well as garbage collector had core switch applied so it was working multi-threaded. I guess for me it will be interesting to note if any problems arise since I have left the site running 1.6.0_27 32 bit JDK (aka free upgrade).
Regards, Carl.

Unresponsive server/jrun threads

Similar Messages

Maybe you are looking for