Loading...

XML

Word

Printable

Type: Bug
Resolution: Duplicate
Priority: Major
Fix Version/s: None
Affects Version/s: 7.0.0.ER6
Component/s: mod_cluster
Labels:
None

CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Target Release:

7.1.0.GA
Git Pull Request:
https://github.com/jbossas/jboss-eap7/pull/490

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

Missing info which services failed to start on server startup

E.g. when I change in mod_cluster subsystem connector reference to invalid one (/subsystem=modcluster/mod-cluster-config=configuration:write-attribute(name=connector, value=invalid), the server fails to start several services without explaining which ones. This is user unfriendly as it creates hard effort to find out what is actually wrong. There should be at least pointed out which services failed to start.

clones

WFLY-6512 Missing explanation which services failed to start

Closed

duplicates

JBEAP-223 mod_cluster subsystem remains silent if connector set to undefined connector

Verified

is cloned by

JBEAP-3600 Missing explanation which services failed to start

Closed

relates to

JBEAP-5311 (7.1.0) Improve readability of missing dependency logs

Verified

Assignee:: Fedor Gavrilov (Inactive)

Reporter:: Bartosz Baranowski

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2016/07/20 6:18 AM

Updated:: 2017/03/07 4:43 PM

Resolved:: 2017/03/07 4:43 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates