Bug 1151221 - After adding Partition Manager through CLI incorrect process-state is shown
Summary: After adding Partition Manager through CLI incorrect process-state is shown
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: PicketLink
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: EAP 6.4.0
Assignee: Pedro Igor
QA Contact: FIlip Bogyai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-09 19:55 UTC by FIlip Bogyai
Modified: 2016-03-17 08:36 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-10-15 16:04:29 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker EAP6-182 0 Major Ready for QA Transition PicketLink subsystems from tech preview to production support 2016-01-04 10:02:50 UTC
Red Hat Issue Tracker WFLY-3978 0 Major Resolved PicketLink Subsystem EAP 6.4 Issues 2016-03-17 08:36:17 UTC

Description FIlip Bogyai 2014-10-09 19:55:03 UTC 
When partition manager is added through CLI using batch, the output shows:

"process-state: reload-required"

although partition manager is successfully started. The process-state message: "reload-required" should not be shown.
Comment 1 JBoss JIRA Server 2014-10-14 13:01:28 UTC 
Kabir Khan <kabir.khan> updated the status of jira EAP6-182 to Resolved
Comment 2 JBoss JIRA Server 2014-10-14 13:26:54 UTC 
Kabir Khan <kabir.khan> updated the status of jira EAP6-182 to Reopened
Comment 3 Pedro Igor 2014-10-15 16:03:51 UTC 
To achieve what you want you first need to add the following header to your operation:

{allow-resource-service-restart=true}

If you are running in batch mode, try this:

run-batch --headers={allow-resource-service-restart=true}

This header instructs the server to do a restart of the service and not a reload.
Comment 4 JBoss JIRA Server 2014-10-17 18:38:41 UTC 
Kabir Khan <kabir.khan> updated the status of jira EAP6-182 to Resolved
Comment 5 JBoss JIRA Server 2014-10-22 09:08:13 UTC 
Ondrej Lukas <olukas> updated the status of jira EAP6-182 to Reopened
Comment 6 JBoss JIRA Server 2014-11-05 07:05:41 UTC 
Rostislav Svoboda <rsvoboda> updated the status of jira EAP6-182 to Resolved
Comment 7 JBoss JIRA Server 2016-03-17 08:36:18 UTC 
Pedro Igor <pigor.craveiro> updated the status of jira WFLY-3978 to Resolved
Note You need to log in before you can comment on or make changes to this bug.