[tjhoman]

I have a set of web services that are available within our application. These web services have been in the application and working for a couple of years. Recently, I upgraded to MyEclipse 5.1 from 4.1 and ever since have been unable to execute my web services. I get the following error in the JBoss server. From what I can determine it appears to be a jar file conflict. However, I am not certain what I need to do to eliminate the conflict. I am running with JBoss 4.0.2, JDK1.5_08. One of my colleagues refuses to move off of 4.1 because we can’t get this resolved. I have read other posts that indicate this could be a conflict between log4j versions as well but I have tried to use the recommended version of log4j and that doesn’t seem to make a difference. The project deployment includes all of the jar files within the ear file, so I am a little confused on how it could be a jar conflict but that seems to be the common denominator in all that we have tried. Has anyone else had issues like this with MyEclipse 5.1?

17:37:52,191 WARN [EngineConfigurationFactoryFinder] Factory org.apache.axis.configuration.EngineConfigurationFactoryServlet Ignored: missing required method: public static EngineConfigurationFactory newFactory(Object).
17:37:52,191 WARN [EngineConfigurationFactoryFinder] Factory org.apache.axis.configuration.EngineConfigurationFactoryDefault Ignored: missing required method: public static EngineConfigurationFactory newFactory(Object).
17:37:52,191 ERROR [EngineConfigurationFactoryFinder] Unable to locate a valid EngineConfigurationFactory
17:37:52,191 INFO [STDOUT] java.lang.NullPointerException
17:37:52,191 INFO [STDOUT] at org.apache.axis.client.Service.getEngineConfiguration(Service.java:803)
17:37:52,191 INFO [STDOUT] at org.apache.axis.client.Service.getAxisClient(Service.java:104)
17:37:52,206 INFO [STDOUT] at org.apache.axis.client.Service.<init>(Service.java:113)
17:37:52,206 INFO [STDOUT] at com.lightspeed.gateway.operations.utility.UtilityIntfServiceLocator.<init>(UtilityIntfServiceLocator.java:12)
17:37:52,206 INFO [STDOUT] at com.lightspeed.xml.gateway.servlets.LsgTestServlet.doPost(LsgTestServlet.java:165)
17:37:52,206 INFO [STDOUT] at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
17:37:52,206 INFO [STDOUT] at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
17:37:52,206 INFO [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
17:37:52,206 INFO [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
17:37:52,206 INFO [STDOUT] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
17:37:52,206 INFO [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
17:37:52,206 INFO [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
17:37:52,206 INFO [STDOUT] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
17:37:52,206 INFO [STDOUT] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
17:37:52,206 INFO [STDOUT] at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)
17:37:52,206 INFO [STDOUT] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:153)
17:37:52,206 INFO [STDOUT] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
17:37:52,206 INFO [STDOUT] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
17:37:52,206 INFO [STDOUT] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
17:37:52,206 INFO [STDOUT] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
17:37:52,206 INFO [STDOUT] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
17:37:52,206 INFO [STDOUT] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
17:37:52,206 INFO [STDOUT] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
17:37:52,206 INFO [STDOUT] at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
17:37:52,206 INFO [STDOUT] at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
17:37:52,206 INFO [STDOUT] at java.lang.Thread.run(Thread.java:595)

[tjhoman]

Some further testing today determined that it was related to property settings on the MyEclipse project. The Axis jar file was needed by a web application as well as the web services server within the ear file. The jar file was being deployed at the ear level for use by all components of the ear. However, MyEclipse was also including the jar file into the WEB-INF/lib directory for the WAR file for the web application. This caused the web application to load one instance and the server to load a different instance causing the compatibility error.

I corrected this by changing the properties of the web application project and setting the MyEclipse/Web/Deployment value for Library Deployment Policies. I turned off the Use workbench default settings and also turned off the Jars on Web Project build path.

[Author]

Posts