Orion在与Apache Tomcat 7一起运行时遇到问题 [英] Orion has issues running alongside Apache Tomcat 7

查看:134
本文介绍了Orion在与Apache Tomcat 7一起运行时遇到问题的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我已经在服务器上安装了Orion 0.24,并在其中安装了ProtonCEP GE(已部署4x WAR文件)的Apache Tomcat 7.

I've installed Orion 0.24 on a server, alongside with Apache Tomcat 7, where I deployed ProtonCEP GE (4x WAR files deployed).

问题在于,Orion仅以替代方式将收到的请求(不依赖于请求)的一半保留,例如:

The issue is that Orion unswers only to half of the requests it gets (independent of request) in an alternate fashion, like so:

$ curl http://localhost:1026/version -H "Content-Type: application/json"
<orion>
  <version>0.24.0</version>
  <uptime>0 d, 0 h, 8 m, 39 s</uptime>
  <git_hash>ed11a3307c7050857ef398ee3e4cd04042a0cc01</git_hash>
  <compile_time>Mon Sep 14 17:52:44 CEST 2015</compile_time>
  <compiled_by>fermin</compiled_by>
  <compiled_in>centollo</compiled_in>
</orion>
$ curl http://localhost:1026/version -H "Content-Type: application/json"
curl: (52) Empty reply from server
$ curl http://localhost:1026/version -H "Content-Type: application/json"
<orion>
  <version>0.24.0</version>
  <uptime>0 d, 0 h, 8 m, 42 s</uptime>
  <git_hash>ed11a3307c7050857ef398ee3e4cd04042a0cc01</git_hash>
  <compile_time>Mon Sep 14 17:52:44 CEST 2015</compile_time>
  <compiled_by>fermin</compiled_by>
  <compiled_in>centollo</compiled_in>
</orion>
$ curl http://localhost:1026/version -H "Content-Type: application/json"
curl: (52) Empty reply from server

如果我停止Tomcat,则通过运行CATALINA_HOME/bin/shutdown.sh脚本,Orion可以正常工作.如果Tomcat正在运行,那么Orion的行为将与描述的一样.

If I stop Tomcat, by running CATALINA_HOME/bin/shutdown.sh script, Orion works fine. If Tomcat is running, Orion behaves as described.

这是在CentOS 6.7上的全新安装中发生的.这两个GE都有依赖关系,因此还安装了MongoDB 2.6.11和Java jdk 8.

This is happening in a fresh install on CentOS 6.7. Both GEs have dependencies, so MongoDB 2.6.11 and Java jdk 8 where also installed.

其他另一个

This same behaviour seemed to have happened to someone else, as asked in another post, but with no mentioned relation to Tomcat then. The solution provided there (to add the option '-ipv4' to the orion's starter command) doesn't solve the issue in this case.

我希望这是一个简单的问题.

I hope it's a simple issue.

如果需要更多信息,请告诉我.

If more information is needed, please let me know.

谢谢

推荐答案

我很抱歉忘记提到偶然的机会,我们最终切换到了具有更多RAM内存的VM,问题就此消失了. 故障VM上的内存很短,但似乎并不重要.此外,唯一的服务失败是Orion,没有其他过程出现故障,这增加了诊断问题的难度.

I apologize for forgeting to mention that, by chance, we ended up switching to a VM with more RAM memory and the issue went away. The memory on the faulty VM was short but didn't seem critical. Also, the only service failing was Orion and no other process was malfunctioning, which contributed to the difficulty in diagnosing the issue.

不再对有故障的VM进行任何测试,并且Orion和CEP/Tomcat在新VM以及其他进程上都可以正常工作.

No more tests were conducted on the faulty VM and Orion and CEP/Tomcat are working fine on the new VM, alongside other processes.

故障VM的运行速度为0.6 GB.新的VM运行在3.75 GB

The faulty VM was running at 0.6 GB. The new VM runs at 3.75 GB

谢谢

这篇关于Orion在与Apache Tomcat 7一起运行时遇到问题的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆