Unable to use Proctor Pipet out of the box

43 views
Skip to first unread message

mpari...@homeaway.com

unread,
Feb 15, 2017, 10:19:30 AM2/15/17
to indeedeng-proctor-users
I am trying to use Proctor Pipet (https://github.com/indeedeng/proctor-pipet) to evaluate for an internal project but it just wont work out-of-the-box when trying to run the examples. Two of us are experiencing the same problem. 

I follow the README file step by step. All works well until I need to run the command to start the service. 

The command is "java -jar proctor-pipet-deploy/target/dependency/webapp-runner.jar proctor-pipet-deploy/target/*.war" 

The service just wont start, here is the full out put until the first exception stack trace: 

Feb 15, 2017 8:06:13 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-nio-8080"]
Feb 15, 2017 8:06:13 AM org.apache.tomcat.util.net.NioSelectorPool getSharedSelector
INFO: Using a shared selector for servlet write/read
Feb 15, 2017 8:06:13 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Tomcat
Feb 15, 2017 8:06:13 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.34
Feb 15, 2017 8:06:13 AM org.apache.catalina.loader.WebappClassLoader validateJarFile
INFO: validateJarFile(/Users/mparigiani/Projects/ha/proctor-pipet/proctor-pipet/target/tomcat.8080/work/Tomcat/localhost/_/WEB-INF/lib/tomcat-el-api-7.0.8.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/el/Expression.class
Feb 15, 2017 8:06:13 AM org.apache.catalina.loader.WebappClassLoader validateJarFile
INFO: validateJarFile(/Users/mparigiani/Projects/ha/proctor-pipet/proctor-pipet/target/tomcat.8080/work/Tomcat/localhost/_/WEB-INF/lib/tomcat-servlet-api-7.0.8.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
Feb 15, 2017 8:06:13 AM org.apache.catalina.startup.ContextConfig getDefaultWebXmlFragment
INFO: No global web.xml found
Feb 15, 2017 8:06:17 AM org.apache.catalina.core.ApplicationContext log
INFO: Spring WebApplicationInitializers detected on classpath: [com.indeed.proctor.pipet.deploy.AppInit@2c9a8def]
log4j:WARN No appenders could be found for logger (com.indeed.proctor.pipet.deploy.AppInit).
log4j:WARN Please initialize the log4j system properly.
Feb 15, 2017 8:06:17 AM org.apache.catalina.core.ApplicationContext log
INFO: Initializing Spring FrameworkServlet 'dispatcher'
Feb 15, 2017 8:06:18 AM org.apache.catalina.core.ApplicationContext log
SEVERE: StandardWrapper.Throwable
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'restController' defined in URL [jar:file:/Users/mparigiani/Projects/ha/proctor-pipet/proctor-pipet/target/tomcat.8080/work/Tomcat/localhost/_/WEB-INF/lib/proctor-pipet-core-0.0.1-SNAPSHOT.jar!/com/indeed/proctor/pipet/core/web/RestController.class]: Unsatisfied dependency expressed through constructor argument with index 1 of type [com.indeed.proctor.common.AbstractProctorLoader]: Error creating bean with name 'proctorLoader' defined in class path resource [com/indeed/proctor/pipet/core/config/CoreConfig.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.indeed.proctor.common.AbstractProctorLoader]: Factory method 'proctorLoader' threw exception; nested exception is java.lang.NoClassDefFoundError: com/indeed/util/core/ReleaseVersion; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'proctorLoader' defined in class path resource [com/indeed/proctor/pipet/core/config/CoreConfig.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.indeed.proctor.common.AbstractProctorLoader]: Factory method 'proctorLoader' threw exception; nested exception is java.lang.NoClassDefFoundError: com/indeed/util/core/ReleaseVersion
at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:749)
at...


Any help would be greatly appreciated. 

mpari...@homeaway.com

unread,
Feb 21, 2017, 7:20:30 AM2/21/17
to indeedeng-proctor-users
UPDATE 

It seems as if the problem was being caused by the util-core dependency in the proctor-pipet-core pom.xml. This is currently set to use 1.0.0 where the ReleaseVersion class is not there (hence the NoClassDefFoundError). It needs to be bumped up to 1.0.12 and everything works now. 


The change would be in the pom.xml for the core project. The <properties> definitions. The <util.version> line, that needs to be changed from 1.0.0 to 1.0.12. 


This change should be committed to proctor-pipet code base. 

Jack Humphrey

unread,
Feb 21, 2017, 4:13:29 PM2/21/17
to indeedeng-proctor-users
Thank you for the report and the resolution note.

I have updated to latest versions of util and proctor: cecc7dd14a3ba1aadb600ecd9afe71b4a2563922

Jack
Reply all
Reply to author
Forward
0 new messages