I've done as you say. I don't have an exception, but the same log I have posted with also the line of the code:
....
INFO [ApplicationServerThread] (DataSourceJDBC.java:524) - field=image1 col=23 value=image.jpg type=8
......
INFO [ApplicationServerThread] (DataSource.java:514) - uh! empty fileHolder
If you want I can do other tests.
Regards
Viviana
At 14.21 25/09/2003 +0100, you wrote:
Hi Viviana,
so the bug seems to be into the new event classes ... anyway try to:
1)
configure log4j with the statements below; the conversionPattern preferences
should print the line number of the dbforms source where the exception occurs..
2)
send to the m.list the full exception's stacktrace, so we could have a better
idea of the program flow...
---
## log4j example:
log4j.category.org.dbforms=INFO, stdout
# stdout Appender
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
# Pattern to output the caller's file name and line number.
log4j.appender.stdout.layout.ConversionPattern=%5p [%t] (%F:%L) - %m%n
---
Regards,
Luca
