Bug 594864 - Determine impact of JCA changes to admin-console
Determine impact of JCA changes to admin-console
Product: RHQ Project
Classification: Other
Component: Plugins (Show other bugs)
All Linux
medium Severity medium (vote)
: ---
: ---
Assigned To: Ian Springer
Mike Foley
Depends On:
Blocks: 577978
  Show dependency treegraph
Reported: 2010-05-21 15:53 EDT by Shelly McGowan
Modified: 2013-08-05 20:37 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-02-26 17:18:16 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Shelly McGowan 2010-05-21 15:53:47 EDT
Description of problem:
Make sure console for EAP 5.1 accommodates recent JCA changes seen in:

Additional info:
Filing for tracking as more information is needed on the above-referenced changes to determine the impact to admin-console
Comment 1 Ian Springer 2010-05-21 17:41:42 EDT
In git commit fd9f8cd10e12584a6e3650036b65692ff27ba6b2 (bugfixes branch), I changed the def for the use-try-lock prop in the jboss-as-5 lugin descriptor to:

    <c:simple-property name="use-try-lock" type="long" required="false">
            Any configured timeout, in seconds, for internal locks on the resource adapter objects. A value of 0
            means no timeout. The default is 60.

I'm unsure whether I should also change the type of the prop from "long" to "integer". If I do make that change, I'll need to make sure the prop still works with AS 5.1 and EAP 5.0 too.
Comment 2 Corey Welton 2010-09-24 08:36:19 EDT
Ian, can this be closed out?

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