seong - 2015-03-13

Hello,

I wish to mention and request the following;

I discovered that J-Interop creates temporary files in windows; 'temp' folder. These temporary files are logs which contains server connection information logs that are disabled to be shown on console by: JISystem.setInBuiltLogHandler(false).

For example:

Recieved ALTER_CTX_RESP
Feb 12, 2015 10:34:16 AM rpc.DefaultConnection processOutgoing
INFO:
Sending REQUEST
Feb 12, 2015 10:34:16 AM rpc.DefaultConnection processIncoming
INFO:
Recieved RESPONSE
^Cb 12, 2015 10:34:16 AM rpc.DefaultConnection processOutgoing

Each log file is 600 -900 mb which is huge. (I run the app for a long period of time and cannot have the program eating up 50-60 gb disk space.)

Is there any way to prevent J-interop from creating these files?

Can I also request;

After using the method; JISystem.setInBuiltLogHandler(false).

I tend to get the following errors after 4 hours running.

java.util.logging.FileHandler.openFiles(Unknown Source)
java.util.logging.FileHandler.<init>(Unknown Source)
org.jinterop.dcom.common.JISystem.setInBuiltLogHandler(Unknown Source)
...........
java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
java.util.concurrent.FutureTask.run(Unknown Source)
java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
java.lang.Thread.run(Unknown Source)

Although this does not have a major effect on the entire program, I am yet curious to know what the error is relating to and how to solve this?

Is J-interop not thread safe?

I very much appreciate and would like to thank you in advance for your time and responses.

Kindest regards

Seong