Bug 1080333 - Changing IOR settings should require restart of jacorb subsystem
Summary: Changing IOR settings should require restart of jacorb subsystem
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: IIOP
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: DR11
: EAP 6.4.0
Assignee: Stefan Guilhen
QA Contact: Jan Martiska
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-25 07:50 UTC by Jan Martiska
Modified: 2023-09-14 02:05 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker EAP6-188 0 Major Closed IOR Settings for Corba Relays 2018-08-09 08:07:52 UTC
Red Hat Issue Tracker WFLY-4093 0 Major Closed Changing IOR settings should require restart of jacorb subsystem 2018-08-09 08:07:52 UTC

Description Jan Martiska 2014-03-25 07:50:49 UTC
Description of problem:
When using management operations to change IOR settings, the settings don't get reflected in the IORSecConfigMetaDataService until a server reload. The management operations should mark that the jacorb subsystem needs to be restarted.

Version-Release number of selected component (if applicable):
6.3.0.DR6 (not officially built yet, I built it from sources, 6.x branch, commit d9d37b2)

Steps to Reproduce:
1. start EAP with the default standalone-full.xml
2. /subsystem=jacorb/ior-settings=default:add
3. /subsystem=jacorb/ior-settings=default/setting=transport-config:add(confidentiality=required){allow-resource-service-restart=true}
4. obtain IORSecConfigMetaDataService (service name: jboss.jacorb.ior-security-config) from MSC and read its value

Actual results:
the value (IORSecurityConfigMetaData) is null

Expected results:
the value (IORSecurityConfigMetaData) should exist and contain the requested configuration

Comment 4 Jan Martiska 2014-11-26 10:00:57 UTC
Verified in EAP 6.4.0.DR11.

Comment 5 JBoss JIRA Server 2015-04-28 15:09:02 UTC
John Doyle <jdoyle> updated the status of jira EAP6-188 to Closed

Comment 6 Red Hat Bugzilla 2023-09-14 02:05:28 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


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