Maybe that log statement comes from a class that you don't have the source of? Like a call to a method from a jar library?
On 6/30/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hi, > > I have a really strange problem and hope you'll be able to help me. I > have a class named OpenHR (compiled with JDK1.3) using Log4J v1.2.8. > My problem is that everything's going right and, suddenly, Log4J lost > the context of the caller : > > 2005-06-29 11:34:50,917 (OpenHR.java:871) DEBUG - getFromSAP--> Execute the > function in SAP > 2005-06-29 11:34:50,980 (?:?) DEBUG - getFromSAP--> String from table DATA: > blablabla > > Problem : (OpenHR.java:871) ==> (?:?) > > Is it a known behaviour and, if yes, do you know why it occurs > suddenly ? > If not, could it be linked to the jvm memory management (stack > management i guess) ? > Is there any limitation of the string length of the message sent to > log4j ? > > Any help is welcome. > > Regards, > Thomas de Bodt. > > > > = = = = = = = = = = = = = = = = = = = = = = = = = > Fortis Bank disclaimer : > http://www.fortisbank.be/legal/disclaimer.htm > > Fortis Bank privacy policy : > http://www.fortisbank.be/legal/privacy_policy.htm > = = = = = = = = = = = = = = = = = = = = = = = = = > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Javier Gonzalez Nicolini --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
