![]() Unfortunately both of them are very unstable, and CloudWatch indicates high CPU while the usage pattern is very low. This past weekend I started a couple of AWS EC2 micro instances using ami-161e787f. The contents of /usr/share/solr/ also looks ls -lĭrwxr-xr-x 5 tomcat tomcat 4096 May 13 13:11 confĭrwxr-xr-x 2 tomcat tomcat 4096 May 13 13:20 dataĭrwxr-xr-x 2 tomcat tomcat 4096 May 13 13:21 lib The /opt/bitnami/apache-tomcat/conf/Catalina/localhost/solr.xml looks like this. : Īt $Sync.innerGet(FutureTask.java:252)Īt .get(FutureTask.java:111)Īt .ployDescriptors(HostConfig.java:579)Īt .ployApps(HostConfig.java:475)Īt .HostConfig.start(HostConfig.java:1402)Īt .HostConfig.lifecycleEvent(HostConfig.java:318)Īt .LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)Īt .LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)Īt .tStateInternal(LifecycleBase.java:402)Īt .tState(LifecycleBase.java:347) SEVERE: Error waiting for multi-thread deployment of context descriptors to complete SEVERE: Error deploying configuration descriptor /opt/bitnami/apache-tomcat/conf/Catalina/localhost/solr.xmlĪt .ployDescriptor(HostConfig.java:625)Īt .HostConfig$n(HostConfig.java:1637)Īt $RunnableAdapter.call(Executors.java:471)Īt $Sync.innerRun(FutureTask.java:334)Īt .run(FutureTask.java:166)Īt .runWorker(ThreadPoolExecutor.java:1145)Īt $n(ThreadPoolExecutor.java:615)ħ:01:52 AM .HostConfig deployDescriptors INFO: Deploying configuration descriptor /opt/bitnami/apache-tomcat/conf/Catalina/localhost/solr.xmlħ:01:52 AM .HostConfig deployDescriptor ![]() ![]() INFO: Starting Servlet Engine: Apache Tomcat/7.0.39ħ:01:51 AM .HostConfig deployDescriptor Here is the Catalina logħ:01:51 AM .StandardEngine startInternal I am using bitnami tomcat7 AMI to create an instance in aws. ![]()
0 Comments
Leave a Reply. |