On Monday 25 February 2002 15:12, Guillaume Laforge wrote: >. . . > Before adding some class creating some PDF with FOP, everything works > perfectly. Tomcat is configured on port 8080, but that's not the > problem, and no other program is using this port. The simple fact of > adding fop.jar in WEB-INF/lib of my webapp causes this problem. And > as soon as I remove fop.jar, everything works fine again, like > before! Weird, isnt it ?
Weird it is - the stack trace that you sent clearly shows the problem happening when the HttpConnector class tries to open a ServerSocket, and it is hard to imagine what this has to do with FOP.jar. Maybe, just maybe, having FOP.jar in the classpath causes wrong versions of some classes to be loaded instead of the right versions, in which case you might want to make sure fop.jar is loaded last in the classpath. Maybe renaming it to zzz-fop.jar will do if the tomcat script sorts jar files by name when building the classpath. You might also want to set tomcat's log level to the most detailed and try to follow exactly what's happening during initialization (or running diff on two logs, one with and one without FOP.jar). -Bertrand
