https://issues.apache.org/bugzilla/show_bug.cgi?id=53345
--- Comment #2 from Mallikarjun Channappagoudar
<mallikarjun.channappagou...@bcbsma.com> ---
(In reply to comment #1)
> Hello,
>
> can you provide more information?
>
> Could you for example look how the log statement looks like:
> om.bcbsma.adapter.util.TPS837_D_Utils.getTransformed837DXmls(TPS837_D_Utils.
> java:119)
>
> Is it a String? How big is it?
>
> Also can you probably show us your configuration?
>
> Thanks!
Surprisingly the line of code at TPS837_D_Utils.java:119 is not a debug
statement, but for some reason the error stack has the following lines.
at org.apache.log4j.Category.forcedLog(Category.java:391)
at org.apache.log4j.Category.debug(Category.java:260)
at
com.bcbsma.adapter.util.TPS837_D_Utils.getTransformed837DXmls(TPS837_D_Utils.java:119)
But there are other instances where the line of code is actually a logger.debug
statement and have caused OutOfMemory errors.
This has happened for small as well as large strings.
The configuration and env info is as follows.
The OS is Linux 2.6.18-164.el5 x86_64 GNU/Linux.
The application is deployed on WAS ND 7.0 with SCA Feature pack 1.0.1
I tried to attach the native_stderr.log file to the bug but may be due to file
size it was not getting attached.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
