AnsweredAssumed Answered

FileMaker 12 Web Publishing Engine (Tomcat) Does Not Work with Java 7 Update 55

Question asked by scott777 on May 16, 2014
Latest reply on May 19, 2014 by disabled_ntaylor


FileMaker 12 Web Publishing Engine (Tomcat) Does Not Work with Java 7 Update 55


FileMaker Server


12.0v5 Windows

Operating system version

Windows Server 2008 R2 SP 1  (ALL Versions affected)

Description of the issue

The Web Publishing Engine is using org.jacorb.orb.ORBSingleton from the jacorb.jar file on start-up.  Java 7 Update 55 has introduced an acknowledged bug with Oracle where this class is erroneously loaded by the system class loader. t

The bug can be found here:

Steps to reproduce the problem

Upgrade Java on the server to Update 55

Expected result

Web Publishing Engine should come up normally

Actual result

Web Publishing engines fails to come up properly.   After upgrading Java, the server is re-booted.  When logging into FMS Admin Console the status area shows Web Server = Enabled with a green check mark, the Database Server shows Enabled with a green check mark,  but the Web Publishing Engine has a red exclamation mark.  The web publishing engine is not up and running because when attempting the run the  PHP web test page it doesn't load.   This test worked prior to the Java Upgrade to 55.

Exact text of any error message(s) that appear

The FileMaker server log has the following entry but the Tomcat catalina.log below has the more pertinent error I believe.

FileMaker Server Log

Publishing Engine Access Error 0 - - "/fmi/conf/config.wpc" 401 0

In the tomcat catalina.log

org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet JWPC threw exception
org.omg.CORBA.INITIALIZE: can't instantiate default ORB implementation org.jacorb.orb.ORBSingleton vmcid: 0x0 minor code: 0 completed: No
at org.omg.CORBA.ORB.create_impl_with_systemclassloader(Unknown Source)
at org.omg.CORBA.ORB.init(Unknown Source)
at com.filemaker.jwpc.fmwp.idl.RequestParamHelper.type(
at com.filemaker.jwpc.fmwp.idl.RequestParamHelper.insert(
at com.filemaker.jwpc.fmwp.WPEConnector.sendRecordCommand(
at com.filemaker.jwpc.xml.request.XMLRequest.performRequest(
at com.filemaker.jwpc.XMLCGIBase.processRequest(
at com.filemaker.jwpc.XMLCGIBase.doPost(
at javax.servlet.http.HttpServlet.service(
at javax.servlet.http.HttpServlet.service(
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
at org.apache.catalina.core.ApplicationFilterChain.doFilter(
at com.filemaker.jwpc.http.JWPCFilter.doFilter(
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
at org.apache.catalina.core.ApplicationFilterChain.doFilter(
at org.apache.catalina.core.StandardWrapperValve.invoke(
at org.apache.catalina.core.StandardContextValve.invoke(
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(
at org.apache.catalina.core.StandardHostValve.invoke(
at com.filemaker.tomcat.FMErrorReportValve.invoke(Unknown Source)
at org.apache.catalina.core.StandardEngineValve.invoke(
at org.apache.catalina.connector.CoyoteAdapter.service(
at org.apache.jk.server.JkCoyoteHandler.invoke(
at org.apache.jk.common.HandlerRequest.invoke(
at org.apache.jk.common.ChannelSocket.invoke(
at org.apache.jk.common.ChannelSocket.processConnection(
at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(
at org.apache.tomcat.util.threads.ThreadPool$
at Source)
Caused by: java.lang.ClassNotFoundException: org.jacorb.orb.ORBSingleton
at$ Source)
at$ Source)
at Method)
at Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
... 29 more


Unfortunately, the workaround that other people are doing which is to put the jar file in the \jre\lib\ext directory does not work for the web publishing tomcat engine with FileMaker.  It leads to more errors.

The only workaround seems to be going back to Java 7 Update 51