| Author |
Jaguar.log growing beyond set limit
|
|
|
| Hi!
In our production EAServer environment the Jaguar.log file
grows beyond the limit we have set. It is not truncated.
We have this setting,
com.sybase.jaguar.server.logfilesize=5000000.
Now we have to restart the EAServer when the Jaguar.log is
around 10 Mbyte, just to truncate the Jaguar.log.
We have never seen this problem before in any environment.
Thankful for tips
//Jonas
| |
| Sandip Ghayal 2005-11-29, 1:24 pm |
| Is log file located on remote machine ?
Thanks,
Sandip
Jonas wrote:
> Hi!
>
> In our production EAServer environment the Jaguar.log file
> grows beyond the limit we have set. It is not truncated.
> We have this setting,
> com.sybase.jaguar.server.logfilesize=5000000.
>
> Now we have to restart the EAServer when the Jaguar.log is
> around 10 Mbyte, just to truncate the Jaguar.log.
>
> We have never seen this problem before in any environment.
>
> Thankful for tips
> //Jonas
| |
| Alexander Pire 2005-11-30, 3:24 am |
| Sorry my friend but com.sybase.jaguar.server.logfilesize have been obsoleted
since EAServer 5.0 (check the programming guide Documentation), you have to
use Log Profile properties.
Alexander Pire
PowerObjects
www.powerobjects.com
612.339.3355
**IT Solutions - Outside the Box**
"Sandip Ghayal" <sghayal@sybase.com> wrote in message
news:438ca154$1@foru
ms-1-dub...[color=darkred]
> Is log file located on remote machine ?
>
> Thanks,
>
> Sandip
>
> Jonas wrote:
| |
|
| The log file is locally on that machine.
The EAServer is 4.1.1.
We done now a big cleaning in the code so it log only errors...
So now in a couple of days we will se if the log is growing below the size.
/Remus
"Alexander Pire" < alexander@powerobjec
ts.com> wrote in message
news:438d1b53$1@foru
ms-1-dub...
> Sorry my friend but com.sybase.jaguar.server.logfilesize have been
obsoleted
> since EAServer 5.0 (check the programming guide Documentation), you have
to
> use Log Profile properties.
>
> Alexander Pire
> PowerObjects
> www.powerobjects.com
> 612.339.3355
> **IT Solutions - Outside the Box**
>
> "Sandip Ghayal" <sghayal@sybase.com> wrote in message
> news:438ca154$1@foru
ms-1-dub...
>
>
| |
| Jonathan Baker [Sybase] 2005-11-30, 11:24 am |
| One word: log4j.
Jonathan
Remus wrote:
> The log file is locally on that machine.
> The EAServer is 4.1.1.
> We done now a big cleaning in the code so it log only errors...
> So now in a couple of days we will se if the log is growing below the size.
>
> /Remus
>
> "Alexander Pire" < alexander@powerobjec
ts.com> wrote in message
> news:438d1b53$1@foru
ms-1-dub...
> obsoleted
> to
>
>
| |
|
| This is one of our main reason for uppgrading to 5.3 :)
/Remus
"Jonathan Baker [Sybase]" < last_name_first_init
ial@sybase.com> wrote in
message news:438de1d8@forums
-1-dub...[color=darkred]
> One word: log4j.
>
>
>
> Jonathan
>
>
> Remus wrote:
size.[color=darkred]
have[color=darkred]
| |
| Jonathan Baker [Sybase] 2005-12-01, 8:25 pm |
| Log4J works fine in EAServer 4.x. It is an application library, and is
pretty much independent of the application server.
The only difference is that EAServer itself starts to use log4j for it's
own messages in EAS 5.0. Notice that I said "starts" - because not all
messages end up on the new logging system.
Jonathan
Remus wrote:
> This is one of our main reason for uppgrading to 5.3 :)
>
> /Remus
>
> "Jonathan Baker [Sybase]" < last_name_first_init
ial@sybase.com> wrote in
> message news:438de1d8@forums
-1-dub...
> size.
> have
>
>
|
|
|
|