Tomcat error in web_server_module_log.txt

[FossilFM]

Hi

We have just installed FileMaker Server Advanced in our XServe and everything seems to be working accordingly with the exception of an error in the server module log of FileMaker Server Advanced,

We always get an error of

Error reading reply from tomcat. Tomcat is down or network problems.

[Mon Dec 06 16:45:30 2004] [jk_ajp_common.c (1187)]: ERROR: Receiving from tomcat failed, recoverable operation. err=0

[Mon Dec 06 16:45:30 2004] [jk_ajp_common.c (1198)]: Error connecting to tomcat. Tomcat is probably not started or is listenning on the wrong port. Failed errno = 61

[Mon Dec 06 16:45:30 2004]wpc 17.212.20.79 0.000378

[Mon Dec 06 16:45:31 2004] [jk_ajp_common.c (1198)]: Error connecting to tomcat. Tomcat is probably not started or is listenning on the wrong port. Failed errno = 61

Is this in regards to a port being blocked or Tomcat not running? Everything is installed with default settings; we haven't made any changes to OS X Server or FileMaker Server Advacned. The only change we made is that we have XSLT publising disabled and XML publishing enabled.

If this is in regards to port settings, does anyone know of a good reference online regarding setting up ports on a XServe.

Any advice would be appreciated.

Thanks.

[Martin Brändle]

According to the FMSA Web Publishing Installation Guide, p. 15, the following ports are used:

FileMaker Proprietary Networking: 5003

Apache Jakarta Protocol 16016, 16018

Tomcat Control: 16010

FileMaker Internal: 16008, 16012

HTTP: 16014

[Bergare]

Has someone found a statisfying solution to this problem? In my case, when traffic is a bit higher, it looks like it's the cause for the server to run bezerk, making 'java' eventually use 95% of the processor power.

Any suggestion would be greatly appreciated!

thanks,

B.

[FossilFM]

Occassionally this causes FileMaker Server Advanced to disconnect from FileMaker Server and eventually stop responding at all to any request from the website.

I still haven't found a solution this problem and at the moment we are keeping a close eye on our machines and sending out request to the machine to make sure that we are still up and running.

Thanks.

[infiniteg]

Check out my post under the subject: "cannot add Filemaker Web Publishing Engine" in the "FileMaker Server Advance" forum. I found the same error messages as you in my log files after having trouble adding the web publishing engine. I haven't resolved the problem yet.

[jeffer]

There is an quite easy solution for this problem. The Java 1.4.2 updates makes the jboss and tomcat services unable to start up. This is due to a startup parameter is a plist file. Just change this and your filemaker server works again!

Check this document from tha apple till database:

http://docs.info.apple.com/article.html?artnum=107814

greetz,

Jeffer

[infiniteg]

I'm running Windows 2000 Server. I don't have a plist file.

[gillian]

We had exactly the same problem on a W2K server - we had not installed Java, once installed the problem was resolved... it should be noted that the setting given under the following thread was also applied.

http://www.fmforums.com/threads/showflat.php?Cat=0&Number=139727&an=0&page=1#139727