AnsweredAssumed Answered

Administrator "fmsadmin" no longer responding; connection closed

Question asked by user13578 on Sep 3, 2009
Latest reply on Feb 21, 2011 by TSGal


Administrator "fmsadmin" no longer responding; connection closed

Description of the issue

  FileMaker Product(s) involved:FileMaker Server 10.1 Operating System(s) involved:PC + II7 + Java 6..7 Detailed description of the issue:In the past two weeks, the server continues to experience an error in communication approximately one hour after restart concerning the connection of the fmsadmin. This prevents the use of the port 16000 for reaching the server administration screen on the local host. Many tickets are found in this filemaker forum database which are related but all issues seem to have differing causes, implying different issues such as a backup routine is running concurrently or a java version upgrade to 10/11 when only support 7 or a FMSv9 certificate s/w update. Plus, many people seem to resort to a re-install of a FMS but in my case we cannot re-install at this stage with production run 6 days a week. I've isolated this one instance by cross-relating the event.log with the java catalina log to find an exact point of failure. 2009-09-03 02:02:46.460 +0100    Information    518     FMS10    Administrator connected: "fmsadmin" (). 2009-09-03 03:09:42.528 +0100    Warning    628     FMS10    Administrator "fmsadmin" no longer responding; connection closed.   03-Sep-2009 03:09:50 org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor processChildrenSEVERE: Exception invoking periodic operation:java.lang.OutOfMemoryError: Java heap space    at Method)    at Source)    at org.apache.catalina.startup.HostConfig.deployApps(    at org.apache.catalina.startup.HostConfig.check(    at org.apache.catalina.startup.HostConfig.lifecycleEvent(    at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(    at org.apache.catalina.core.ContainerBase.backgroundProcess(    at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(    at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(    at org.apache.catalina.core.ContainerBase$    at Source) Exact steps to reproduce the issue:1.  Restart FM2.  Load databases within successfully all within 20 minutes3.  Some one hour later find the error with catalina and the mis-commuication No users at 2am, no xslt publishing, no web publishing Expected Result:fmsadmin remains connected and the server admin console is able to workActual Result:So, no server admin console nor the 16000 port works Exact text of any error message(s) that appeared:See above for catalina messageAny additional configuration information/troubleshooting that is relevant to the issue:1.  All users have access, xslt publishing works, xml publishing works,2.  I have no problem accessing these files via Instant Web Publishing