Unable to start Message Processor on 16.05 Private Cloud setup

We tried starting the Message Processor on 16.05 Private Cloud setup as follows:

#apigee-service edge-message-processor start 

and got the following output:

apigee-configutil: edge-message-processor: # OK 
apigee-service: edge-message-processor: Not running (NO_LOCKFILE) 
apigee-service: edge-message-processor: status=2, continuing 
apigee-service: edge-message-processor: OK 
apigee-service: edge-message-processor: edge-message-processor is running

But when I checked the status with # apigee-all status command and noticed that Message Processor was not started.

"edge-message-processor: Not running (DEAD)”.
Solved Solved
0 1 570
1 ACCEPTED SOLUTION

  • Checked the startupruntimeerrors.log. Did not see any errors.
  • Checked the system.log and found the following exception
2016-06-14 05:10:45,463  main ERROR KERNEL - MicroKernel.deployAll() : MicroKernel.deployAll() : Error in deploying the deployment : ComponentConfigurationService
com.apigee.kernel.exceptions.spi.UncheckedException: Starting of Service HTTPTransport failed unexpectedly
	at com.apigee.kernel.service.deployment.ServiceDeployer.getUncheckedException(ServiceDeployer.java:192) ~[microkernel-1.0.0.jar:na]
	at com.apigee.kernel.service.deployment.ServiceDeployer.startService(ServiceDeployer.java:176) ~[microkernel-1.0.0.jar:na]
	at com.apigee.kernel.service.deployment.ServiceDeployer.deploy(ServiceDeployer.java:70) ~[microkernel-1.0.0.jar:na]
	at com.apigee.kernel.service.deployment.ServiceDeployer.deployDependantServices(ServiceDeployer.java:356) ~[microkernel-1.0.0.jar:na]
	at com.apigee.kernel.service.deployment.ServiceDeployer.deploy(ServiceDeployer.java:76) ~[microkernel-1.0.0.jar:na]
	at com.apigee.kernel.MicroKernel.deployAll(MicroKernel.java:178) [microkernel-1.0.0.jar:na]
	at com.apigee.kernel.MicroKernel.start(MicroKernel.java:139) [microkernel-1.0.0.jar:na]
	at com.apigee.kernel.MicroKernel.start(MicroKernel.java:135) [microkernel-1.0.0.jar:na]
	at com.apigee.kernel.MicroKernel.main(MicroKernel.java:84) [microkernel-1.0.0.jar:na]
Caused by: java.lang.IllegalArgumentException: No enum constant com.apigee.protocol.http.HTTPProxy.Type.
	at java.lang.Enum.valueOf(Enum.java:238) ~[na:1.8.0_91]
	at com.apigee.protocol.http.HTTPProxy$Type.valueOf(HTTPProxy.java:20) ~[http-1.0.0.jar:na]
	at com.apigee.protocol.http.HTTPTransport.configure(HTTPTransport.java:331) ~[http-1.0.0.jar:na]
	at com.apigee.protocol.http.HTTPTransport.start(HTTPTransport.java:103) ~[http-1.0.0.jar:na]
	at com.apigee.kernel.service.deployment.ServiceDeployer.startService(ServiceDeployer.java:167) ~[microkernel-1.0.0.jar:na]
	... 7 common frames omitted
  • Looking further into the code and found that we get this error while we are trying to read the property "HTTPClient.proxy.type" from the properties file.
  • Checked the /<inst_root>/apigee/customer/application/message-processor.properties and found that the following properties were set:
  • conf/http.properties+HTTPClient.proxy.host=api.somehost.com
    conf/http.properties+HTTPClient.proxy.port=8080 
    conf/http.properties+HTTPClient.use.tunneling=false
    
  • This indicated that the exception was caused because of the missing property HTTPClient.proxy.type
  • Updated the /<inst_root>/apigee/customer/application/message-processor.properties to include this property “HTTPProxy.Type.proxy” as follows:
  • conf/http.properties+HTTPClient.proxy.type=HTTPS
    conf/http.properties+HTTPClient.proxy.host=api.somehost.com
    conf/http.properties+HTTPClient.proxy.port=8080
    conf/http.properties+HTTPClient.use.tunneling=false
    
  • Saved the file and started the message-processor.
  • This resolved the issue.

    Note: The valid values for HTTPClient.proxy.type are HTTP, HTTPS

    View solution in original post

    1 REPLY 1

    • Checked the startupruntimeerrors.log. Did not see any errors.
    • Checked the system.log and found the following exception
    2016-06-14 05:10:45,463  main ERROR KERNEL - MicroKernel.deployAll() : MicroKernel.deployAll() : Error in deploying the deployment : ComponentConfigurationService
    com.apigee.kernel.exceptions.spi.UncheckedException: Starting of Service HTTPTransport failed unexpectedly
    	at com.apigee.kernel.service.deployment.ServiceDeployer.getUncheckedException(ServiceDeployer.java:192) ~[microkernel-1.0.0.jar:na]
    	at com.apigee.kernel.service.deployment.ServiceDeployer.startService(ServiceDeployer.java:176) ~[microkernel-1.0.0.jar:na]
    	at com.apigee.kernel.service.deployment.ServiceDeployer.deploy(ServiceDeployer.java:70) ~[microkernel-1.0.0.jar:na]
    	at com.apigee.kernel.service.deployment.ServiceDeployer.deployDependantServices(ServiceDeployer.java:356) ~[microkernel-1.0.0.jar:na]
    	at com.apigee.kernel.service.deployment.ServiceDeployer.deploy(ServiceDeployer.java:76) ~[microkernel-1.0.0.jar:na]
    	at com.apigee.kernel.MicroKernel.deployAll(MicroKernel.java:178) [microkernel-1.0.0.jar:na]
    	at com.apigee.kernel.MicroKernel.start(MicroKernel.java:139) [microkernel-1.0.0.jar:na]
    	at com.apigee.kernel.MicroKernel.start(MicroKernel.java:135) [microkernel-1.0.0.jar:na]
    	at com.apigee.kernel.MicroKernel.main(MicroKernel.java:84) [microkernel-1.0.0.jar:na]
    Caused by: java.lang.IllegalArgumentException: No enum constant com.apigee.protocol.http.HTTPProxy.Type.
    	at java.lang.Enum.valueOf(Enum.java:238) ~[na:1.8.0_91]
    	at com.apigee.protocol.http.HTTPProxy$Type.valueOf(HTTPProxy.java:20) ~[http-1.0.0.jar:na]
    	at com.apigee.protocol.http.HTTPTransport.configure(HTTPTransport.java:331) ~[http-1.0.0.jar:na]
    	at com.apigee.protocol.http.HTTPTransport.start(HTTPTransport.java:103) ~[http-1.0.0.jar:na]
    	at com.apigee.kernel.service.deployment.ServiceDeployer.startService(ServiceDeployer.java:167) ~[microkernel-1.0.0.jar:na]
    	... 7 common frames omitted
    
  • Looking further into the code and found that we get this error while we are trying to read the property "HTTPClient.proxy.type" from the properties file.
  • Checked the /<inst_root>/apigee/customer/application/message-processor.properties and found that the following properties were set:
  • conf/http.properties+HTTPClient.proxy.host=api.somehost.com
    conf/http.properties+HTTPClient.proxy.port=8080 
    conf/http.properties+HTTPClient.use.tunneling=false
    
  • This indicated that the exception was caused because of the missing property HTTPClient.proxy.type
  • Updated the /<inst_root>/apigee/customer/application/message-processor.properties to include this property “HTTPProxy.Type.proxy” as follows:
  • conf/http.properties+HTTPClient.proxy.type=HTTPS
    conf/http.properties+HTTPClient.proxy.host=api.somehost.com
    conf/http.properties+HTTPClient.proxy.port=8080
    conf/http.properties+HTTPClient.use.tunneling=false
    
  • Saved the file and started the message-processor.
  • This resolved the issue.

    Note: The valid values for HTTPClient.proxy.type are HTTP, HTTPS