Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-3472

gwt-console-server component cannot talk to Guvnor if guvnor.connect.timeout and guvnor.read.timeout properties are not set

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • jBPM 5.3
    • jBPM 5.2
    • Console
    • None

    Description

      Description of problem:
      In org.jbpm.integration.console.shared.GuvnorConnectionUtils these properties
      default to "" (empty string) and later they are parsed as integer values so a
      NumberFormatException occurs.

      This was pretty cumbersome to debug, because only exception message is logged:
      2011-12-14 16:32:28,783 ERROR
      [org.jbpm.integration.console.shared.GuvnorConnectionUtils]
      (http-127.0.0.1-8080-4) Error retriving packages from guvnor: For input string:
      ""

      When fixing this please look at the rest of the code and try to make sure that
      if serious exception occurs that can't be recovered from, it is logged with the
      stack trace, too, not only its message, which might be confusing.

      Version-Release number of selected component (if applicable):
      BRMS-5.3.0.DEV5

      How reproducible:

      Steps to Reproduce:
      1. make sure guvnor.connect.timeout and guvnor.read.timeout properties are not
      set in gwt-console-server.war/WEB-INF/classes/jbpm.console.properties (which is
      default in the tested build)
      2. open Process Overview in the BPM console
      3. no processes show up, error message is logged in server log

      Actual results:

      Expected results:
      guvnor.connect.timeout and guvnor.read.timeout should default to a value that
      makes sense, so the properties can be omitted in the properties file

      Attachments

        Activity

          People

            rhn-support-tsurdilo Tihomir Surdilovic (Inactive)
            rhn-support-tsurdilo Tihomir Surdilovic (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: