Bug 1191720 - JCA Resource Adapter creation error is "Unknown Error"
Summary: JCA Resource Adapter creation error is "Unknown Error"
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Console - UX
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.4.2
Assignee: Romain Pelisse
QA Contact: Pavel Jelinek
eap-docs
URL:
Whiteboard:
Depends On:
Blocks: 1219165 1222380
TreeView+ depends on / blocked
 
Reported: 2015-02-11 19:59 UTC by anestico
Modified: 2017-01-17 10:13 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-17 10:13:04 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description anestico 2015-02-11 19:59:03 UTC 
Description of problem:
When creating a bad JCA Resource Adapter, the error message shown is "Unknown Error"

Version-Release number of selected component (if applicable):
EAP 6.4.0-ER2

How reproducible:
Always

Steps to Reproduce:
1. Go to Configuration -> Connector -> Resource Adapters
2. Click "Add"
3. Enter Name="anyString", Module="anyString", any option for TX; leave Archive blank.
4. Click "Save"

Actual results:
Error message is "Unknown Error"
Clicking "Messages" shows "Unexpected HTTP Response: 500" and better details

Expected results:
A better message, perhaps "Unexpected HTTP Response: 500", should be displayed.

Additional info:
Comment 1 Matt Carrano 2015-02-11 22:34:38 UTC 
Agree that there should be a better error message.  Not sure if this is just a bug or if the solution requires better error reporting from the backend.
Comment 3 Romain Pelisse 2015-04-01 02:23:41 UTC 
Here is a fix proposal for the upstream project (hal-core):

https://github.com/hal/core/pull/26
Comment 5 Harald Pehl 2015-04-01 12:01:19 UTC 
Merged in master: https://github.com/hal/core/pull/26
Comment 12 Pavel Jelinek 2015-06-19 11:33:13 UTC 
Verified for EAP 6.4.2.CP.CR1.
Comment 14 Petr Penicka 2017-01-17 10:13:04 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.
Note You need to log in before you can comment on or make changes to this bug.