Spawning a Java process

hey,
I have no idea if this is possible, but i have my fingers
crossed.
So what i want to do is create an instance of a java object
that extracts some data from a database and then emails it to a
specified email address.
I want CF to create the java object, set all the variables
and then finish. Ie i don't want CF to wait for the extraction to
complete.
Is there anyway that i can do this? I'm thinking no, but its
worth asking.
Cheers Bec.

> ...an instance of a java object that extracts some data
from a database
> and then emails it to a specified email address.
<cfcomponent>
<cfquery>
</cfquery>
<cfmail>
</cfmail>
</cfcomponent>

Similar Messages

Spawn a java process using runtime.exec() method

Hi,
This is my first post in this forum. I have a small problem. I am trying to spawn a java process using Runtime.getRuntime().exec() method in Solaris. However, there is no result in this check the follwoing program.
/* Program Starts here */
import java.io.*;
public class Test {
public static void main(String args[]) {
String cmd[] = {"java", "-version"};
Runtime runtime = Runtime.getRuntime();
try{
Process proc = runtime.exec(cmd);
}catch(Exception ioException){
ioException.printStackTrace();
/* Program ends here */
There is neither any exception nor any result.
The result I am expecting is it should print the following:
java version "1.4.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92)
Java HotSpot(TM) Client VM (build 1.4.0-b92, mixed mode)
Please help me out in this regard
Thanks in advance
Chotu.

Yes your right. It is proc.getInputStream() or proc.getErrorStream(). That is what I get for trying to use my memory instead of looking it up. Though hopefully the OP would have seen the return type of the other methods and figured it out.

Spawning another java process after System.exit(0);

Hi everyone
I have an application that Im trying to test. Unfortunately one of these tests requires me to spawn another java process after a System.exit(0); has executed. Since this exits the VM its proving very difficult. Does anyone know of a way to restart the VM after the System.exit has run?
Thanks

Hi everyone
I have an application that Im trying to test.
Unfortunately one of these tests requires me to spawn
another java process after a System.exit(0); has
executed. Since this exits the VM its proving very
difficult. Does anyone know of a way to restart the VM
after the System.exit has run?Exactly what do you want to do?
If the application is supposed to only have one exit point then add a security manager and disallow all the other exit points. Then you can use Runtime.exec() to start the second application just before the real exit point.
However note that if there are other calls to System.exit in the application then it is very likely that this will cause some unexpected failures in terms of security exceptions.
You could also use Runtime.addShutdownHook() which would run your second app. The hook would be called as the application exits.
You might want to consider what happens if someone just kills the application (say with 'kill -9' or the windows task manager.) In either of those cases there is nothing that you can do in java to make that second application run.
You might also want to consider why you are doing this in the first place. As suggested a script solution is probably a better solution.

Spawning another sub-process

All
A quick workflow question: How do I spawn another child/sub-process from another process of the same item type ?
Imagine this scenario:
ItemType : ABC
Process : EFG
Start --> Function A ---> Process HIJ ---> Function C ---> End
Process : HIJ
Start --> Function D ---> Notify X ---[Timeout]--> Notify Y ---> Re-assign
One of the options/buttons within the Notify Y will be to start another process EFG of item type ABC.
Do I simply drag and drop the Process EFG process icon into the diagram of Process HIJ and link it as an outcome of Notify Y ?
Or is there another way of doing it ?
Any helps is appreciated ?
Thanks
Regards

Hi everyone
I have an application that Im trying to test.
Unfortunately one of these tests requires me to spawn
another java process after a System.exit(0); has
executed. Since this exits the VM its proving very
difficult. Does anyone know of a way to restart the VM
after the System.exit has run?Exactly what do you want to do?
If the application is supposed to only have one exit point then add a security manager and disallow all the other exit points. Then you can use Runtime.exec() to start the second application just before the real exit point.
However note that if there are other calls to System.exit in the application then it is very likely that this will cause some unexpected failures in terms of security exceptions.
You could also use Runtime.addShutdownHook() which would run your second app. The hook would be called as the application exits.
You might want to consider what happens if someone just kills the application (say with 'kill -9' or the windows task manager.) In either of those cases there is nothing that you can do in java to make that second application run.
You might also want to consider why you are doing this in the first place. As suggested a script solution is probably a better solution.

Tracing Java Processes that spawns child process

I hope I'm posting this in the correct group. If not, please let me know where to direct this question:
In our 12.1.3 Applications, we installed a plugin called 'Org Chart' by Applaud Solutions. It is a flash component that graphically displays the employee hierarchy of an organizations and is accessed via responsibility. This tool also has a feature to 'export' the chart as a Microsoft Word or PowerPoint to the users desktop. When this occurs, a 'java' process is kicked off on the applications server to process this request. Now, here's the issue: The performance of this export is terrible! It takes roughly about 2-3 minutes to complete, and sometimes never completes. Here is the java process that gets kicked off for one user which i figured out how to run manually:
[applprod1@aspapp012 ~]$ java -jar OpenOfficeGenerator.jar /u01/applprod1/PROD1/apps/apps_st/appl/xxas/1.0.1/out/orgchart-f78b7a67-a379-4f7d-9dcf-5f13b22e03e4.xml /tmp/ed.pptx docx NameandTitle letter Y normal
When I kick this off, I'm able to get the linux PID :
9056
22523 24779 62 16:21 pts/0
00:00:06 java -jar OpenOfficeGenerator.jar /u01/applprod1/PROD1/apps/apps_st/appl/xxas/1.0.1/out/orgchart-f78b7a67-a379-4f7d-9dcf-5f13b22e03e4.xml /tmp/ed.pptx docx NameandTitle letter Y normal
Then, I run an 'strace -f -p 22523' and notice these timeout issues from child processes that is spawns:
[pid 22524] read(3, "\n", 1)
= 1
[pid 22524] _llseek(3, 18642588, [18642588], SEEK_SET) = 0
[pid 22524] read(3, "\0", 1)
= 1
[pid 22524] _llseek(3, 18642589, [18642589], SEEK_SET) = 0
[pid 22536] <... futex resumed> )
= -1 ETIMEDOUT (Connection timed out)
[pid 22524] read(3, <unfinished ...>
[pid 22536] futex(0x972b728, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 22536] gettimeofday({1384208528, 131781}, NULL) = 0
[pid 22536] clock_gettime(CLOCK_MONOTONIC, {33657710, 707532536}) = 0
[pid 22536] gettimeofday({1384208528, 131844}, NULL) = 0
[pid 22536] clock_gettime(CLOCK_REALTIME, {1384208528, 131892000}) = 0
[pid 22536] futex(0x965d2bc, FUTEX_WAIT_PRIVATE, 1, {0, 49952000} <unfinished ...>
My question is does anyone know how i can determine what is causing these timeouts? It seems the java process spawns off child processes and this is where the timeouts are occurring. Upon further investigation the child processes are throwing the following errors as well:
futex(0x905f1b4, FUTEX_WAIT_PRIVATE, 67, NULL) = 0
futex(0x905ed28, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x906345c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x9063458, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0x905f1b4, FUTEX_WAIT_PRIVATE, 69, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x905ed28, FUTEX_WAKE_PRIVATE, 1) = 0
However, I am unable to determine the cause of the timeout and resource issue. Any ideas or help is greatly appreciated! thanks.

I would suggest you consult "Applaud Solutions" for this issue.
Thanks,
Hussein

SunOS 5.10 spawns multiple PID's for same java process

On SunOS 5.10 I see same java process having multiple PID's. ps -ef lists out the same java process running from same path with multiple PID's. What can be the reason for this?
Please let me know if you need some more information.....
Edited by: sayanb on Jan 5, 2010 9:29 AM

Hi Chris,
Thank you for this update.
Again this seems to be a known issue on SunOS 10.Also I will try to take the stack strace for the specific java process.
http://forums.sun.com/thread.jspa?forumID=546&threadID=5297465
http://groups.google.com/group/bojug/browse_thread/thread/19d722275c4384b8
Basically the issue seems to be with one of the fork system calls which confuses with active and actual threads running.The above link speaks about the same , faced by similar users.
Any updates will be appreciated.Meanwhile will try to get the stack trace.
Regards
Sayan

Does different Java processes spawn different JVMs running on a server ?

Hi,
I have 2 applications running on AIX server, one is weblogic server and the other one is inhouse developed Java application. I have set the heap sizes for both the applications and when I do
ps ax | grep JavaI get
/usr/java14/bin/java -Xms2048m -Xmx2048m (weblogic)
/usr/java14/jre/bin/java -Xmx320m -Dvert.log.prefix (inhouse Java)I was wondering if these two processes have their own JVM or as they are running on the same server they share the same JVM. I read in some Java related article that even though there are multiple Java processes, they share the same JVM when run on a single server.
So from the above Java processes is it true that the total Java heap size is 2048+320=2368M and is used by only one JVM?
I appreciate if anyone who can answer or direct me to some resources which might give me some answers.
Thanks,
kraziabtu

No, you have two totally independent JVM's. As with many O/S's AIX (and I'm so sorry for you on that :) will only load a single copy of things like read only data segments, shared libraries and some other things but the processes are separate.
Your first process is allowed to grow to a maximum of 2GB and your second one is set at 320 MB. Again, as there are two of them they are not related.
Need Java help? Want to help people who do? Sit down with a cup of Java at the hotjoe forums.
Sure they're new - come get them started!

JDK 1.6 on Solaris. Multiple java processes and thread freezes

Hi, we've come across a really weird behavior on the Solaris JVM, reported by a customer of ours.
Our server application consists of multiple threads. Normally we see them all running within a single Java process, and all is fine.
At some point in time, and only on Solaris 10, it seems that the main Java process starts a second Java process. This is not our code trying to execute some other application/command. It's the JVM itself forking a new copy of itself. I assumed this was because of some JVM behaviour on Solaris that uses multiple processes if the number of threads is > 128. However at the time of spawn there are less than 90 threads running.
In any case, once this second process starts, some of the threads of the application (incidentally, they're the first threads created by the application at startup, in the first threadgroup) stop working. Our application dumps a list of all threads in the system every ten minutes, and even when they're not working, the threads are still there. Our logs also show that when the second process starts, these threads were not in the running state. They had just completed their operations and were sleeping in their thread pool, in a wait() call. Once the second process starts, jobs for these threads just queue up, and the wait() does not return, even after another thread has done a notify() to inform them of the new jobs.
Even more interesting, when the customer manually kills -9 the second process, without doing anything in our application, all threads that were 'frozen' start working again, immediately. This (and the fact that this never happens on other OSes) makes us think that this is some sort of problem (or misconfiguration) specific to the Solaris JVM, and not our application.
The customer initially reported this with JDK 1.5.0_12 , we told them to upgrade to the latest JDK 1.6 update 6, but the problem remains. There are no special JVM switches (apart from -Xms32m -Xmx256m) used. We're really at a dead end here in diagnosing this problem, as it clearly seems to be outside our app. Any suggestion?

Actually, we've discovered that that's not really what was going on. I still believe there's a bug in the JVM, but the fork was happening because our Java code tries to exec a command line tool once a minute. After hours of this, we get a rogue child process with this stack (which is where we are forking this command line tool once a minute):
JVM version is 1.5.0_08-b03
Thread t@38: (state = IN_NATIVE)
- java.lang.UNIXProcess.forkAndExec(byte[], byte[], int, byte[], int, byte[], boolean, java.io.FileDescriptor, java.io.FileDescriptor, java.io.FileDescriptor) @bci=168980456 (Interpreted frame)
- java.lang.UNIXProcess.forkAndExec(byte[], byte[], int, byte[], int, byte[], boolean, java.io.FileDescriptor, java.io.FileDescriptor, java.io.FileDescriptor) @bci=0 (Interpreted frame)
- java.lang.UNIXProcess.<init>(byte[], byte[], int, byte[], int, byte[], boolean) @bci=62, line=53 (Interpreted frame)
- java.lang.ProcessImpl.start(java.lang.String[], java.util.Map, java.lang.String, boolean) @bci=182, line=65 (Interpreted frame)
- java.lang.ProcessBuilder.start() @bci=112, line=451 (Interpreted frame)
- java.lang.Runtime.exec(java.lang.String[], java.lang.String[], java.io.File) @bci=16, line=591 (Interpreted frame)
- java.lang.Runtime.exec(java.lang.String, java.lang.String[], java.io.File) @bci=69, line=429 (Interpreted frame)
- java.lang.Runtime.exec(java.lang.String) @bci=4, line=326 (Interpreted frame)
- java.lang.Thread.run() @bci=11, line=595 (Interpreted frame)There are also several dozen other threads all with the same stack:
Thread t@32: (state = BLOCKED)
Error occurred during stack walking:
sun.jvm.hotspot.debugger.DebuggerException: can't map thread id to thread handle!
     at sun.jvm.hotspot.debugger.proc.ProcDebuggerLocal.getThreadIntegerRegisterSet0(Native Method)
     at sun.jvm.hotspot.debugger.proc.ProcDebuggerLocal.getThreadIntegerRegisterSet(ProcDebuggerLocal.java:364)
     at sun.jvm.hotspot.debugger.proc.sparc.ProcSPARCThread.getContext(ProcSPARCThread.java:35)
     at sun.jvm.hotspot.runtime.solaris_sparc.SolarisSPARCJavaThreadPDAccess.getCurrentFrameGuess(SolarisSPARCJavaThreadPDAccess.java:108)
     at sun.jvm.hotspot.runtime.JavaThread.getCurrentFrameGuess(JavaThread.java:252)
     at sun.jvm.hotspot.runtime.JavaThread.getLastJavaVFrameDbg(JavaThread.java:211)
     at sun.jvm.hotspot.tools.StackTrace.run(StackTrace.java:50)
     at sun.jvm.hotspot.tools.JStack.run(JStack.java:41)
     at sun.jvm.hotspot.tools.Tool.start(Tool.java:204)
     at sun.jvm.hotspot.tools.JStack.main(JStack.java:58)I'm pretty sure this is because the fork part of the UnixProcess.forkAndExec is using the Solaris fork1 system call, and thus all the Java context thinks all those threads exist, whereas the actual threads don't exist in that process.
It seems to me that something is broken in UnixProcess.forkAndExec in native code; it did the fork, but not the exec, and this exec thread just sits there forever. And of course, it's still holding all the file descriptors of the original process, which means that if we decide to restart our process, we can't reopen our sockets for listening or whatever else we want to do.
There is another possibility, which I can't completely rule out: this child process just happened to be the one that was fork'd when the parent process called Runtime.halt(), which is how the Java process exits. We decided to exit halfway through a Runtime.exec(), and got this child process stuck. But I don't think that's what happens... from what I understand that we collected, we see this same child process created at some point in time, and it doesn't go away.
Yes, I realize that my JVM is very old, but I cannot find any bug fixes in the release notes that claim to fix something like this. And since this only happens once every day or two, I'm reluctant to just throw a new JVM at this--although I'm sure I will shortly.
Has anyone else seen anything like this?

Java processes

Dear all,
I am using Oracle 10.2.0.3 on Linux.
When I do ps -ef on the server I see a lot of java process spawned. There are so jobs or anything running which executes any java processes. Then why is it so.
Please help.
Regards
SL

Try not making any threads. Just do a single Thread.sleep in main. Then count how many java processes there are. If your OS implements threads as lightweight processes, there will be several. One will be your main thread and the others will be those of the VM.

JVM spawning mysterious child process of itself using Runtime.exec()

Hello, I'm not sure if this is how this is supposed to work but I have a java application that monitors legacy c programs and after a period of time (its intermittent), I'll see a duplicate jvm process running the same classpath, classname as a child of the java application monitor. This behaviour can be reproduced with the following simple class running on either solaris 9 or 10 using 1.6.0_03-b05:
public class Monitor {
Process procss;
public Monitor() {
try {
Runtime runtime = Runtime.getRuntime();
for (int i = 0; i < 10000; i++) {
System.out.println("execing command ls -l.");
procss = runtime.exec("ls -l");
procss.waitFor();
catch (Exception e) {
e.printStackTrace();
public static void main(String[] args) {
new Monitor();
Using java -classpath ./ Monitor to run it. While this is running, at intermittent times doing a ps -ef you will see a duplicate jvm running whose parent process is the one that was started on the command line. Ie:
UID PID PPID etc
user 17434 10706 .... java -classpath ./ Monitor (the one I put running)
user 27771 17434 .....java -classpath ./ Monitor (intermittently started)
in another window I'll run the following shell script that will output the processes when a duplicate java process gets started as they don't seem to run very long (on my production system they will occasionally get hung up until I manually kill them):
#!/usr/bin/ksh
while ((1 == 1))
do
ps -ef | grep "Monitor" | grep -v grep > /tmp/test.out
VAL=`cat /tmp/test.out | wc -l`
if (($VAL != 1))
then
echo "Duplicate java process started"
cat /tmp/test.out
fi
done
It takes roughly 30 seconds before I start to see duplicate jvms starting to run. The concern is that is the new jvm instance running the Monitor class? Eventually on my production system the real application will have a child or 2 linger indefinetly, and threads will be deadlocked. Once I kill these child java processes, everything is back to normal. This doesn't seem to occur with the above java class but will show the duplicate child jvm's start to run after a bit.

This is true for Solaris and Linux. Sun's implementation does a fork. A lot of people who have very large memory java applications wish there was a way to create a process from Java that doesn't involve copying the parent process. As far as I know your stuck.
A workaround: Use jms, rmi, sockets, or files to communicate with a low memory footprint java application whose sole purpose is to spawn child processes.

Long time to start on Java process dispatcher

Hi ,
I am trying to Install Solution Manager. When I attempt to start my sap system, the Java process dispatcher of instance/stage SM1 (solution manager) takes too much time and finally doesn't start showing this intallation error.
ERROR 2008-09-24 11:01:11.314
CJS-30151 Java process dispatcher of instance SM1/DVEBMGS00 [ABAP: ACTIVE, Java: (dispatcher: UNKNOWN, server0: RUNNING)] did not start after 2:00 minutes. Giving up.
ERROR 2008-09-24 11:01:11.502
FCO-00011 The step startJava with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_StartJava|ind|ind|ind|ind|5|0|startJava was executed with status ERROR .
Can anyone please let me know what is missing in this procedure? Any idea?
tkanks in advance.

Hi Matias,
What are the parameters you set for your dispatcher?
Regards
Val

All Java Processes crash on RH Linux 7.3 / 6.3 without any comment

We have the following Problem on two Machines. We installed j2sdk1.4.0 first, then jdk-1.3.1_04 (Because of other Problems with 1.4.0).
Now all running java Processes crash after up to two hours without any comment, any error file. Looks like they were killed by the 'kill' Command. The running java Processes are different Programs, that do very different things.
The OS on the two machines are RH Linux 7.3 and 6.3 - normal installation without any essential changes.
I would be very happy, if someone have an idea, how to solve this Problem. If you need additional Information, ask for.
Holger

... if someone have an idea, how to solve this Problem.Seems like I remember seeing a problem like that.
It turned out that indeed it was the 'kill' command. Another process was running, looking for the app, and killing it when it found it.
We spend quite a bit of time trying to figure out why our app was 'crashing' before deciding to look elsewhere (when we discovered the other process.)

How do I stop Java processes from appearing on the dock?

I have a Java application that has a fairly extensive build process using ant. It builds fine on OSX, but constantly annoys me. There are a large number of unit tests that run using JUnit, and each test starts in a new Java process. The problem is that when each process starts (and there are about 100 during the course of the build), a new Java icon appears on the dock and stays until the process finishes. First of all, that slows down the build (since it has to do all that graphics work to keep changing the appearance of the dock). Secondly, every time a new process starts, it takes away the keyboard focus from whatever I'm currently working on. I either have to click in the window I want again, or else wait for the process to finish.
On Windows, this is handled with an alternative version of the JVM called "javaw.exe" that does not get a foreground window. However, I see no "javaw" in the Java directory on OSX. Is there some option to start Java with that will stop this dock updating? Note that there are times when I want the dock to be updated (when I'm running a "normal" Java app).

Even when the Guest Account / Access is disabled, the login option / and lock screen, still have a guest login.
This is because in Preferences/ Security & Privacy/General the bottom item is turned on.
Turn on: Disable restarting to Safari when screen is locked

How to restart a java process in Oracle AS 10g

Hi
In Oracle AS 10g, the java process consumes 50% cpu resource due to the report invoked by a user. Now I need to restart the java back ground process?, please reply me with the syntax or with examples.
ps -eaf
CPU PROCESS
50% /ORACLE_HOME/jdk/jre/bin/java -server -cp /report/oracle
Thanks in advance
Bala

The copy method being using is unsupported, hence the target Portal would be in an unsupported state.
This is unsupported as per the following note:
Note 333867.1 - Portal Export and Import Utility Supportability Scenarios :
Copy operations after an object is renamed:
Exporting and importing a page group, then renaming the page group on the target system (to create a copy) and repeating the export and import operation.
OR:
Exporting and importing a page group, then renaming the same in source or target and repeating the export and import operation.
Not supported.
Please do not rename objects if you plan to perform export and import operations.
Note: The display name can be changed, but internal name change is considered a renaming operation.
In 10.1.4, renaming is supported, but renaming page group and pages with the intention of copying them is not supported..."

Java process - high CPU usage

Hi,
I'm describing a high CPU scenario which gets triggered randomly ( I'm not able to replicate it on my lab setup).
There are around 120 threads which are running in my java process. The jvm is running on a high traffic (through put) site, where there are a lot of async events coming to the java process.( around 220 events per 60 seconds ). The java process works fine in this scenario, the normal CPU consumption hovers around 1.5 % to 2.0 %.
But, at times, I've seen CPU to be as high as 43 %, and it stays at that value for hours altogther. In those situations, I usually do a failover to standby java process. I tried debugging the issue to see which java thread could be causing the issue, but, I could not come to a conclusion or replicate the situation in lab environment.
Here are the details of the execution environment
java -version
java version "1.4.2_11"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_11-b06)
Java HotSpot(TM) Client VM (build 1.4.2_11-b06, mixed mode)
prstat during high CPU
PID USERNAME THR PRI NICE SIZE RES STATE TIME CPU COMMAND
10485 root 120 10 0 570M 381M cpu1 268:10 43.64% java
prstat -Lm -p output
PID USERNAME USR SYS TRP TFL DFL LCK SLP LAT VCX ICX SCL SIG PROCESS/LWPID
10485 root 53 0.5 0.2 0.0 0.0 30 0.2 16 69 1K 118 0 java/2
10485 root 31 0.0 0.1 0.0 0.0 53 0.2 16 23 778 93 0 java/26
10485 root 0.4 0.0 0.0 0.0 0.0 99 0.0 0.1 10 16 106 0 java/12
10485 root 0.1 0.0 0.0 0.0 0.0 100 0.0 0.0 3 2 7 0 java/15
10485 root 0.1 0.0 0.0 0.0 0.0 97 0.0 2.4 120 3 128 0 java/41
10485 root 0.1 0.0 0.0 0.0 0.0 97 0.0 2.5 120 4 131 0 java/410
Some more points about the last prstat -Lm output.
java/2 is "VM Thread" ( responsible for GC). "VM Thread" is having a NORMAL priority ( 5 )
java/26 is a "Worker" thread, with priority MINIMUM ( 1 ).
Could you suggest what could be issue, and what other information I could collect to find out the issue. Its difficult to profile the process because the problem scenario is difficult to ascertain and the process is running on a production setup.
Any help is appreciated.
Thanks
Sanjay

Hi,
Thanks for your response. Both, the production setup and lab setup have have 2 physical CPUs.
Actually, there are two java threads ( machine is solaris 10) one is "VM Thread" and other is my applications worker thread. (there are 10 of them with priority 1). If you look at the top two lwps in the prstat -Lm , both are showing high value of ICX.
I'm still not able to drill down to my code level. (Worker thread is waiting on a queue to de-queue server request). Could you give some hint to move foward?
rgds
Sanjay

Spawning a Java process

Similar Messages

Maybe you are looking for