[#JRA-14183] Terrible error reporting when establishing trusted connections

JIRA

Terrible error reporting when establishing trusted connections

Created: 25/Dec/07 07:43 PM Updated: 09/Jan/08 10:54 PM

Component/s:

Backend / Domain Model

Affects Version/s:

3.12.1

Fix Version/s:

3.12.2

Time Tracking:

Not Specified

File Attachments:

None

Image Attachments:

1. trusted_doesnotsupport.png
(15 kB)

2. trustederror.png
(38 kB)

Participants:	Anton Mazkovoi [Atlassian], Jed Wesley-Smith [Atlassian], Jeff Turner [Atlassian] and Unai Rodriguez
Since last comment:	34 weeks, 2 days ago
Resolution Date:	09/Jan/08 10:34 PM
Labels:

Description

« Hide

As a test, I set up JIRA 3.12.1 and Confluence 2.7, and attempted to tell JIRA to trust Confluence. This is the error I got:

For the purposes of this bug, i don't care why it isn't working. I care that:

The error message presented to the user is completely unhelpful.
There is absolutely nothing in the logs.

JIRA code is swallowing a NPE, which ought to be a hanging offense.

If I try the http URL instead of https, I get an equally uninformative message:

It's Confluence 2.7 which does indeed support the Trusted Application protocol. Again, a complete lack of information necessary to aid further debugging.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 26/Dec/07 04:25 PM

Michael,

Can you have a look at what the actual errors are? We can then try to see if it is possible to find out if it is possible to come up with better error messages.

[ Permlink | « Hide ]

Unai Rodriguez added a comment - 03/Jan/08 03:46 AM

We are experiencing the same problem. Is there any estimates on when this is going to get resolved?

Thank you,
unai

[ Permlink | « Hide ]

Jeff Turner [Atlassian] added a comment - 06/Jan/08 10:49 PM

Unai,

Please create an issue at https://support.atlassian.com, attaching logs and letting us know as much detail about your configuration as possible. This bug (~~JRA-14183~~) only addresses the error reporting, not the particular underlying errors.

Cheers,
Jeff

[ Permlink | « Hide ]

Unai Rodriguez added a comment - 07/Jan/08 03:53 AM

Sure, I will. Thanks Jeff.

[ Permlink | « Hide ]

Jed Wesley-Smith [Atlassian] added a comment - 09/Jan/08 10:34 PM

We now log these with a full stack trace of the causal exception.

There is not a lot that we can do about the utility of the NullPointerException message inside java.security.* however...

We also updated Seraph to better log unsuccessful trusted application requests.

[ Permlink | « Hide ]

Jeff Turner [Atlassian] added a comment - 09/Jan/08 10:54 PM

Great, thanks.