UOJ log and lock files are generated why?

I found these files in our web server that use UniObjects for JAVA: uojlog_0.log.0, uojlog_0.log.0.lck, uojlog_1.log.0, uojlog_1.log.0.lck and on and on. Since I am using UOJ version 5.111.2 if that helps. BTW the files are always empty.

------------------------------
Doug Averch (Owner)
U2logic, Inc.
daverch@u2logic.com
303-946-5226 (cell & text)
------------------------------

New empty log files are generated by new UOJ 5.2.1 client that implements new logging feature. We asked our UOJ engineer to remove them by default in the future release. Thanks for point this out Doug.

------------------------------
Paul Chang
Principal Technical Support Engineer
Rocket Software
------------------------------

New empty log files are generated by new UOJ 5.2.1 client that implements new logging feature. We asked our UOJ engineer to remove them by default in the future release. Thanks for point this out Doug.

------------------------------
Paul Chang
Principal Technical Support Engineer
Rocket Software
------------------------------

Hi Paul,

I am not sure deleting this feature is good, unless you mean "turning off logging by default".

I think if you could define:
UniJava.setLogDebugLevel(Level.OFF); as the default, which would not create the empty (uojlog_0.log.0 & uojlog_0.log.0.lck files)  and continue to allow options as documented in the UOJ manual:

The log debug level, which can be set to one of the following: ALL, FINEST, FINER, FINE, CONFIG, INFO, WARNING, SEVERE, and
OFF. If not specified, the default setting is WARNING.

thanks

------------------------------
Nik Kesic
LKQ
------------------------------

Hi Paul,

I am not sure deleting this feature is good, unless you mean "turning off logging by default".

I think if you could define:
UniJava.setLogDebugLevel(Level.OFF); as the default, which would not create the empty (uojlog_0.log.0 & uojlog_0.log.0.lck files)  and continue to allow options as documented in the UOJ manual:

The log debug level, which can be set to one of the following: ALL, FINEST, FINER, FINE, CONFIG, INFO, WARNING, SEVERE, and
OFF. If not specified, the default setting is WARNING.

thanks

------------------------------
Nik Kesic
LKQ
------------------------------

Hey Nic:

Your code generates an error because you have not told us where to get the Java Level library. I had ten chooses but I am not sure what the debug-level variable should be.
UniJava.setLogDebugLevel(Level.OFF);

------------------------------
Doug Averch (Owner)
www.u2logic.com
daverch@u2logic.com
------------------------------

Hey Nic:

Your code generates an error because you have not told us where to get the Java Level library. I had ten chooses but I am not sure what the debug-level variable should be.
UniJava.setLogDebugLevel(Level.OFF);

------------------------------
Doug Averch (Owner)
www.u2logic.com
daverch@u2logic.com
------------------------------

Hello Doug,

You are right.

This should help:

import java.util.logging.Level;
Just a note, when i set 'Level' to ALL(UniJava.setLogDebugLevel(Level.ALL);), I got 45KB of logs for a simple Subroutine call. When 'Level' was set to OFF(UniJava.setLogDebugLevel(Level.OFF);), I got zero bytes in the log file.  I believe OFF is the default, and should not allow the log files to be created or left behind in the first place. But I think there is more to the story, which I am sure Paul can comment on because of the momentary existence of.lck file.

cheers

------------------------------
Nik Kesic
LKQ
------------------------------

Hello Doug,

You are right.

This should help:

import java.util.logging.Level;
Just a note, when i set 'Level' to ALL(UniJava.setLogDebugLevel(Level.ALL);), I got 45KB of logs for a simple Subroutine call. When 'Level' was set to OFF(UniJava.setLogDebugLevel(Level.OFF);), I got zero bytes in the log file.  I believe OFF is the default, and should not allow the log files to be created or left behind in the first place. But I think there is more to the story, which I am sure Paul can comment on because of the momentary existence of.lck file.

cheers

------------------------------
Nik Kesic
LKQ
------------------------------

On new UOJ 5.2.1 client, it implement new Java logging feature that can define new options in the uoj.properties file. The default logging option is set to WARNING. It might generate a new uojlog_0.log.0 file with empty byte. On some secure system, it won't be allowed to create new file that might break the application. We suggest to update new UOJ driver without generating new empty file by default. You still can set the logging option in the uoj.properties file or UOJ application.

------------------------------
Paul Chang
Principal Technical Support Engineer
Rocket Software
------------------------------

On new UOJ 5.2.1 client, it implement new Java logging feature that can define new options in the uoj.properties file. The default logging option is set to WARNING. It might generate a new uojlog_0.log.0 file with empty byte. On some secure system, it won't be allowed to create new file that might break the application. We suggest to update new UOJ driver without generating new empty file by default. You still can set the logging option in the uoj.properties file or UOJ application.

------------------------------
Paul Chang
Principal Technical Support Engineer
Rocket Software
------------------------------

Hello Paul 

I a fairly complex scenario , where should I place uoj.properties ?

is there any jvm property i can pass to tell the location of uoj.properties ? 

we have failed to find the place for it , so we can utrrn off the creation of the log and lck files that are messing with our logs a lot 

thanks in advance 

------------------------------
David Lopez
Director of Software Strategy
Quiter Servicios Informaticos SL
Santander ES
------------------------------