登录/注册
    我的位置：首页 › 大数据分析-亿信BI › BI-问题求助 › 服务器tomcat进程偶尔会自己死掉

    服务器tomcat进程偶尔会自己死掉

    复制链接 | 收藏本帖
    5233
    4

    Carson 小试身手Lv3

    发表于2018-11-6 12:02

    悬赏200

    已解决

    楼主
    linux云服务器操作系统，BI 和I都部署在同一个tomcat下面，tomcat其中可以正常访问。但是偶尔会存在tomcat进程莫名其妙的死掉问题，造成无法访问。
    查看了下logs日志，出现最多的错误是：
    Nov 04, 2018 4:35:08 AM org.apache.jk.common.MsgAjp processHeader
    SEVERE: BAD packet signature 18245
    Nov 04, 2018 4:35:08 AM org.apache.jk.common.ChannelSocket processConnection
    SEVERE: Error, processing connection
    java.lang.IndexOutOfBoundsException
            at java.io.BufferedInputStream.read(BufferedInputStream.java:327)
            at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:621)
            at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:578)
            at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:686)
            at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
            at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
            at java.lang.Thread.run(Thread.java:745)

    Nov 04, 2018 4:35:08 AM org.apache.jk.common.MsgAjp processHeader
    SEVERE: BAD packet signature 0
    Nov 04, 2018 4:35:28 AM org.apache.jk.common.ChannelSocket receive
    WARNING: can't read body, waited #84
    Nov 04, 2018 4:35:28 AM org.apache.jk.common.ChannelSocket processConnection
    WARNING: Closing ajp connection -1
    Nov 04, 2018 5:40:05 AM org.apache.jk.common.MsgAjp processHeader
    SEVERE: BAD packet signature 18245
    Nov 04, 2018 5:40:05 AM org.apache.jk.common.ChannelSocket processConnection
    SEVERE: Error, processing connection
    java.lang.IndexOutOfBoundsException
            at java.io.BufferedInputStream.read(BufferedInputStream.java:327)
            at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:621)
            at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:578)
            at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:686)
            at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
            at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
            at java.lang.Thread.run(Thread.java:745)

    Nov 04, 2018 5:40:05 AM org.apache.jk.common.MsgAjp processHeader
    SEVERE: BAD packet signature 18245
    Nov 04, 2018 5:40:05 AM org.apache.jk.common.ChannelSocket processConnection
    SEVERE: Error, processing connection
    java.lang.IndexOutOfBoundsException
            at java.io.BufferedInputStream.read(BufferedInputStream.java:327)
            at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:621)
            at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:578)
            at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:686)
            at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
            at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
            at java.lang.Thread.run(Thread.java:745)

    Nov 04, 2018 5:40:05 AM org.apache.jk.common.MsgAjp processHeader
    SEVERE: BAD packet signature 1284
    Nov 04, 2018 5:40:05 AM org.apache.jk.common.HandlerRequest invoke
    SEVERE: Error decoding request
    java.lang.ArrayIndexOutOfBoundsException: -1
            at org.apache.jk.common.HandlerRequest.decodeRequest(HandlerRequest.java:388)
            at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:261)
            at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
            at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
            at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
            at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
            at java.lang.Thread.run(Thread.java:745)

    Nov 04, 2018 5:40:05 AM org.apache.jk.common.ChannelSocket processConnection
    WARNING: processCallbacks status 2
    Nov 04, 2018 5:40:05 AM org.apache.jk.common.MsgAjp processHeader
    SEVERE: BAD packet signature 3338
    Nov 04, 2018 5:40:10 AM org.apache.jk.common.ChannelSocket receive
    WARNING: can't read body, waited #3338
    Nov 04, 2018 5:40:10 AM org.apache.jk.common.ChannelSocket processConnection
    WARNING: Closing ajp connection -1
    Nov 04, 2018 5:40:10 AM org.apache.jk.common.MsgAjp processHeader
    SEVERE: BAD packet signature 20304
    Nov 04, 2018 5:40:10 AM org.apache.jk.common.ChannelSocket processConnection
    SEVERE: Error, processing connection
    java.lang.IndexOutOfBoundsException
            at java.io.BufferedInputStream.read(BufferedInputStream.java:327)
            at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:621)
            at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:578)
            at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:686)
            at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
            at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
            at java.lang.Thread.run(Thread.java:745)

    Nov 04, 2018 5:40:10 AM org.apache.jk.common.MsgAjp processHeader
    SEVERE: BAD packet signature 20304
    Nov 04, 2018 5:40:10 AM org.apache.jk.common.ChannelSocket processConnection
    SEVERE: Error, processing connection
    java.lang.IndexOutOfBoundsException
            at java.io.BufferedInputStream.read(BufferedInputStream.java:327)
            at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:621)
            at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:578)
            at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:686)
            at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
            at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
            at java.lang.Thread.run(Thread.java:745)

    Nov 04, 2018 5:40:10 AM org.apache.jk.common.MsgAjp processHeader
    SEVERE: BAD packet signature 32768
    Nov 04, 2018 5:40:10 AM org.apache.jk.common.HandlerRequest invoke
    INFO: Unknown message 114
    Nov 04, 2018 5:40:10 AM org.apache.jk.common.MsgAjp processHeader
    SEVERE: BAD packet signature 18245
    Nov 04, 2018 5:40:10 AM org.apache.jk.common.ChannelSocket processConnection
    SEVERE: Error, processing connection
    java.lang.IndexOutOfBoundsException
            at java.io.BufferedInputStream.read(BufferedInputStream.java:327)
            at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:621)
            at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:578)
            at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:686)
            at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
            at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
            at java.lang.Thread.run(Thread.java:745)

    Nov 04, 2018 5:40:10 AM org.apache.jk.common.MsgAjp processHeader
    SEVERE: BAD packet signature 18245
    Nov 04, 2018 5:40:10 AM org.apache.jk.common.ChannelSocket processConnection
    SEVERE: Error, processing connection
    java.lang.IndexOutOfBoundsException
            at java.io.BufferedInputStream.read(BufferedInputStream.java:327)
            at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:621)
            at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:578)
            at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:686)
            at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
            at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
            at java.lang.Thread.run(Thread.java:745)

    最近看过此主题的会员

    esen_4TU4L1BV1N

    esen_4Y7CUM9LAB

    ssssssss

    最佳答案

    wut

    发表于2018-11-6 12:02

    丨

    只看该作者

    丨

    取消 关注该作者的回复

    Carson 发表于 2018-11-6 14:19
    端口是开放着的，之前访是正常的，只是偶尔会出现进程死掉的情况。进程死掉了，当就是访问不到了，判断进程 ...

    从您的报错日志上看，是端口不正确的错误。您从tomcat这块能不能突破下，搞个啥子监控来监控tomcat，实时抓取日志做分析把
    QQ空间 微信
    4个回答

    只看楼主

    wut 数据老手Lv5

    发表于2018-11-6 13:58

    丨

    只看该作者

    丨

    取消 关注该作者的回复

    沙发

    从报错的信息判断是访问的端口错误，请问您之前可以正常访问吗？然后是如果判断tomcat进程死掉的呢。前台有什么报错吗

    回复

    Carson 小试身手Lv3

    发表于2018-11-6 14:19

    丨

    只看该作者

    丨

    取消 关注该作者的回复

    板凳

    端口是开放着的，之前访是正常的，只是偶尔会出现进程死掉的情况。进程死掉了，当就是访问不到了，判断进程死掉  ps -ef| grep tomcat

    回复

    wut 数据老手Lv5

    发表于2018-11-6 12:02

    丨

    只看该作者

    丨

    取消 关注该作者的回复

    地板

    Carson 发表于 2018-11-6 14:19
    端口是开放着的，之前访是正常的，只是偶尔会出现进程死掉的情况。进程死掉了，当就是访问不到了，判断进程 ...

    从您的报错日志上看，是端口不正确的错误。您从tomcat这块能不能突破下，搞个啥子监控来监控tomcat，实时抓取日志做分析把

    回复

    Carson 小试身手Lv3

    发表于2018-11-6 15:22

    丨

    只看该作者

    丨

    取消 关注该作者的回复

    5#

    wut 发表于 2018-11-6 15:00
    从您的报错日志上看，是端口不正确的错误。您从tomcat这块能不能突破下，搞个啥子监控来监控tomcat，实时 ...

    即便是端口存在端口不正确也不会造成进程死掉吧。这种进程直接死掉的你们之前又遇到过没，可以给分享几个出现这种情况的解决案例吗？

    回复

    登录后可回答问题，请登录或注册

    有问题，来提问！
    我要发帖
    热门推荐
    热门视频
    热门产品推荐
    快速回复 返回顶部 返回列表

    小时

    全天响应

    分钟

    快速处理问题

    工程师强势助力

    明星产品
    一站式数据分析平台-亿信ABI
    智能数据治理平台-睿治
    解决方案
    大数据治理方案
    数据标准化及质量管控方案
    主数据管理方案
    数据资产盘点方案
    联系合作

    400咨询：400-0011-866

    技术支持QQ：400-0011-866(工作日9:00-18:00)

    产品建议邮箱yixin@esensoft.com

    关注我们

    扫TA学习更多干货

    一对一专家交流

    版权所有© 2006-2024 北京亿信华辰软件有限责任公司 京ICP备07017321号 京公网安备11010802016281号