[jboss-jira] [JBoss JIRA] (WFCORE-855) Intermittent Disconnection from CLI After Reload in domain mode
RH Bugzilla Integration (JIRA)
issues at jboss.org
Wed Aug 26 02:36:42 EDT 2015
[ https://issues.jboss.org/browse/WFCORE-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13101815#comment-13101815 ]
RH Bugzilla Integration commented on WFCORE-855:
------------------------------------------------
Carlo de Wolf <cdewolf at redhat.com> changed the Status of [bug 1249031|https://bugzilla.redhat.com/show_bug.cgi?id=1249031] from POST to MODIFIED
> Intermittent Disconnection from CLI After Reload in domain mode
> ---------------------------------------------------------------
>
> Key: WFCORE-855
> URL: https://issues.jboss.org/browse/WFCORE-855
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 2.0.0.Alpha12
> Reporter: Joe Wertz
> Assignee: Joe Wertz
> Fix For: 2.0.0.Alpha13
>
> Original Estimate: 3 minutes
> Time Spent: 3 hours
> Remaining Estimate: 0 minutes
>
> Description of problem:
> CLI scripts for management of managed domain
> Version-Release number of selected component (if applicable):
> 6.4.3.CP.CR1
> How reproducible:
> Always
> Steps to Reproduce:
> Use CLI script:
> :read-attribute(name=process-type)
> reload --host=master
> :read-attribute(name=process-type)
> or commands option for script
> Actual results:
> 6.4.3
> ./jboss-cli.sh -c commands=':read-attribute(name=process-type), reload --host=master, :read-attribute(name=process-type)'
> {
> "outcome" => "success",
> "result" => "Domain Controller"
> }
> Failed to establish connection in 6025ms
> Expected results:
> 6.3.3
> ./jboss-cli.sh -c commands=':read-attribute(name=process-type), reload --host=master, :read-attribute(name=process-type)'
> {
> "outcome" => "success",
> "result" => "Domain Controller"
> }
> {
> "outcome" => "success",
> "result" => "Domain Controller"
> }
> Additional info:
> - Follow up to https://bugzilla.redhat.com/show_bug.cgi?id=1232933
> - using --timeout doesn't workaround the problem
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
More information about the jboss-jira
mailing list