{"id":521,"date":"2017-04-07T11:50:18","date_gmt":"2017-04-07T09:50:18","guid":{"rendered":"http:\/\/www.ume.li\/blog\/?p=521"},"modified":"2017-04-07T11:51:54","modified_gmt":"2017-04-07T09:51:54","slug":"orient-me-95","status":"publish","type":"post","link":"https:\/\/www.ume.li\/blog\/2017\/04\/07\/orient-me-95\/","title":{"rendered":"Orient Me – 95%"},"content":{"rendered":"

The installation process for the orient me part in connections was interessting.
\nThe installer sets up its own IBM CFC (Spectrum Conductor for Containers) environment complete with docker and kubernetes. I went through all the config steps and soon had access to the new orient me page.
\nTesting the page I sometimes got an error message “Der Activity Stream konnte nicht geladen werden. Zeitlimit f\u00fcr die Anforderung ist abgelaufen.”<\/p>\n

Checking back on the CFC Dashboard<\/p>\n

\"\"<\/a><\/p>\n

 <\/p>\n

Checking the applications, the retrievalservice does not want to start. The restart count is currently beyond 450….<\/p>\n

Setting up a second environment this time only 1 worker node with the same result.<\/p>\n

 <\/p>\n

 <\/p>\n

After struggling with the new docker environment, I got the logs (kubectl logs<\/em> is your friend)<\/p>\n

There is a nasty error message.
\n
\nException in thread \"main\" java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
\nat org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:62)
\nat java.lang.Thread.run(Unknown Source)
\nCaused by: java.lang.reflect.InvocationTargetException
\nat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
\nat sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
\nat sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
\nat java.lang.reflect.Method.invoke(Unknown Source)
\nat org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:54)
\n... 1 more
\nCaused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'retrievalControllerImpl': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.ibm.orientme.micros.retrievalservice.service.IStackingService com.ibm.orientme.micros.retrievalservice.controller.RetrievalControllerImpl.stackingService; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'stackingServiceImpl' defined in URL [jar:file:\/opt\/ibm\/toscana\/retrievalservice\/retrieval-service\/build\/libs\/retrieval-service-20170327_131255-standalone.jar!\/com\/ibm\/orientme\/micros\/retrievalservice\/service\/impl\/StackingServiceImpl.class]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.ibm.orientme.micros.retrievalservice.service.impl.StackingServiceImpl]: Constructor threw exception; nested exception is org.apache.solr.common.SolrException: Cannot connect to cluster at zookeeper1:2181,zookeeper2:2181,zookeeper3:2181: cluster not found\/not ready ....
\n<\/code><\/p>\n

Unfortunatly the zookeper app is green….<\/p>\n","protected":false},"excerpt":{"rendered":"

The installation process for the orient me part in connections was interessting. The installer sets up its own IBM CFC<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[23],"tags":[],"class_list":["post-521","post","type-post","status-publish","format-standard","hentry","category-connections"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t