[esb-issues] [JBoss JIRA] Commented: (JBESB-1573) boot.log is truncated upon ESB Server startup

Mon Mar 3 10:40:07 EST 2008

    [ http://jira.jboss.com/jira/browse/JBESB-1573?page=comments#action_12401104 ] 

Kevin Conner commented on JBESB-1573:
-------------------------------------

Hiya Daniel.

The default log4j configuration is found in the AS run.jar archive.  This is used until the logging system can be properly configured.

The inclusion of the log4j.jar in the scoped context will, all most certainly, be the culprit.  Please remove the jar file but do not remove the scoping.

Kev

> boot.log is truncated upon ESB Server startup
> ---------------------------------------------
>
>                 Key: JBESB-1573
>                 URL: http://jira.jboss.com/jira/browse/JBESB-1573
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Rosetta
>    Affects Versions: 4.2.1 CP1
>            Reporter: Daniel Bevenius
>         Assigned To: Daniel Bevenius
>            Priority: Critical
>
> boot.log is truncated upon startup of the ESBServer. I've tracked this down to the soapui-client.sar. By "unscoping" it the boot.log is no longer be truncated. Why this is happening I'm not sure...I'll continue to investigate but though I create this Jira in case someone else has any ideas. 
> This might also be the cause of an issue that we are currently seeing. Our ESB suddenly starts to log to boot.log at the DEBUG level. This has caused our file system to fill up and actually stop the servers from handling more requests. 
> I think I remember something about the soapui-client.sar being scoped because of some versions conflict, but I can rememeber which it was...jbossws maybe?
> I just tested to unscope soapui-client.sar and removed: 
> jbossesb-rosetta.jar
> milyn*,
> lib/log4j.jar
> lib/commons-logging.jar
> I then ran the web service producer quickstart without any trouble. Is this sufficient to verify that soapui-client.sar can now run unscoped with 4_2_1_GA_CP.
> Any thoughs on this would be much appriciated.
> Thanks,
> Daniel

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira