Uploaded image for project: 'Gazelle Security Suite'
  1. Gazelle Security Suite
  2. GSS-393

When SyslogCollector receive a message, JBoss server is crashing.

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 5.3.0
    • Fix Version/s: 5.3.1
    • Component/s: None
    • Labels:
      None
    • Account:
      Innovation 2016 (INNOVATION2016)

      Description

      When sending a message to the SyslogCollector on TCP port, the JBoss does not answer anymore after.

      It seems it raise a problem with the persistence layer and disturbs other applications on the same application server. (see attached file gss-stacketrace.txt)

      This issue was not detected during development due to an isolated dev environment (only one user at a time with no other applications on the JBoss server).

      Regarding SyslogCollector source code, this JAR manage by itself its database connection using gov.nist.syslog.util.DBUtil.java. It might mix with JPA persistence layer (or hibernate) and cause problems.

      A solution may be to remove this DBUtil class and use instead hibernate and JPA.

        Attachments

          Activity

            People

            • Assignee:
              ceoche Cédric EOCHE-DUVAL
              Reporter:
              ceoche Cédric EOCHE-DUVAL
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 1 week Original Estimate - 1 week
                1w
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 2 weeks, 6 hours
                2w 6h

                  Potential Duplicates