#176 DS console should timeout when mismatched port and protocol combination is chosen
Closed: wontfix None Opened 8 years ago by rmeggins.

https://bugzilla.redhat.com/show_bug.cgi?id=758983

Description of problem:
While doing MMR+SSL configuration from DS console, I was just trying with below
settings for MMR agreement and the DS console hanged completely.
I tried it many times and It behaves the same.

For the settings, please check the screen shot in attachment Image.
For the console log, please check the attachment.

batch move to milestone future

set default ticket origin to Community

Added initial screened field value.

The formatting looks off starting at line 443.

I think the timeouts should be much shorter - probably 5 seconds for each.

I think the timeouts should be configurable, but I'm not sure how to do that, so I guess we can punt that for another ticket.

Replying to [comment:11 rmeggins]:

The formatting looks off starting at line 443.

The formatting in this file is a complete disaster! There is not a single method that is consistent. I'll just redo that entire method.

I think the timeouts should be much shorter - probably 5 seconds for each.

And I was thinking they might be too short :) I'll gladly reduce them.

I think the timeouts should be configurable, but I'm not sure how to do that, so I guess we can punt that for another ticket.

Okay.

New patch attached.

git merge ticket176
Updating 8dd0505..fea27bc
Fast-forward
src/com/netscape/admin/dirserv/DSUtil.java | 58 +++++++++++++++++++++++-----------------

git push origin master
To ssh://git.fedorahosted.org/git/389/ds-console.git
8dd0505..fea27bc master -> master

commit fea27bc7a2a07d50b22ac26de6eabc055fa4b973
Author: Mark Reynolds mreynolds@redhat.com
Date: Thu Aug 28 17:14:11 2014 -0400

Metadata Update from @rmeggins:
- Issue assigned to mreynolds
- Issue set to the milestone: 389-admin,console 1.1.36

3 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/176

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)

7 days ago

Login to comment on this ticket.

Metadata