Bug 971265 - Duplicate message when threaddump application
Duplicate message when threaddump application
Status: CLOSED CURRENTRELEASE
Product: OpenShift Online
Classification: Red Hat
Component: Master (Show other bugs)
2.x
Unspecified Unspecified
medium Severity low
: ---
: ---
Assigned To: Dan McPherson
libra bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-06-06 03:10 EDT by Wei Sun
Modified: 2015-05-14 20:54 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-08-07 18:54:28 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Wei Sun 2013-06-06 03:10:12 EDT
Description of problem:
Thread dump the app via RESTAPI,but it returns duplicate messages:
The thread dump file will be available via: rhc tail eapt -f /tmp/jbosseap.log -o '-n 250'

Version-Release number of selected component (if applicable):
devenv_3324

How reproducible:
Always

Steps to Reproduce:
1.Create jboss/ruby app
2.Thread dump the app via RESTAPI
3.

Actual results:
<messages>
    <message>
      <severity>info</severity>
      <text>Success
The thread dump file will be available via: rhc tail eapt -f /tmp/jbosseap.log -o '-n 250'</text>
      <exit-code nil="true"></exit-code>
      <field nil="true"></field>
    </message>
    <message>
      <severity>result</severity>
      <text>Success
The thread dump file will be available via: rhc tail eapt -f /tmp/jbosseap.log -o '-n 250'
</text>
      <exit-code nil="true"></exit-code>
      <field nil="true"></field>
    </message>
  </messages>


Expected results:
Don't have duplicate messages

Additional info:
Comment 1 Dan McPherson 2013-07-23 15:09:39 EDT
https://github.com/openshift/origin-server/pull/3145
Comment 3 Wei Sun 2013-07-24 02:23:15 EDT
Verified on devenv_3545

Result:
 <messages>
    <message>
      <severity>info</severity>
      <text></text>
      <exit-code>0</exit-code>
      <field nil="true"></field>
    </message>
    <message>
      <severity>result</severity>
      <text>Success
The thread dump file will be available via: rhc tail eapt -f /tmp/jbosseap.log -o '-n 250'
</text>
      <exit-code>0</exit-code>
      <field nil="true"></field>
    </message>
  </messages>

Note You need to log in before you can comment on or make changes to this bug.