[JBoss JIRA] (WFLY-1914) Application client container doesn't start
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-1914?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-1914:
-----------------------------------------------
Aleksandar Kostadinov <akostadi(a)redhat.com> made a comment on [bug 999465|https://bugzilla.redhat.com/show_bug.cgi?id=999465]
We still see the issue with 6.2.0 ER3.1.. just saying
> Application client container doesn't start
> ------------------------------------------
>
> Key: WFLY-1914
> URL: https://issues.jboss.org/browse/WFLY-1914
> Project: WildFly
> Issue Type: Bug
> Components: Application Client
> Affects Versions: 8.0.0.Alpha4
> Reporter: jaikiran pai
> Assignee: jaikiran pai
> Fix For: 8.0.0.Beta1
>
>
> Application client container fails to start with the following exception:
> {code}
> 16:23:40,742 INFO [org.jboss.as.jacorb] (MSC service thread 1-7) JBAS016328: CORBA Naming Service started
> 16:23:40,744 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
> ("subsystem" => "naming"),
> ("service" => "remote-naming")
> ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.naming.remote is missing [jboss.remoting.endpoint.subsystem]"]}
> 16:23:40,779 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.remoting.endpoint.subsystem (missing) dependents: [service jboss.naming.remote]
> 16:23:40,782 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.0.0.Beta1-SNAPSHOT "WildFly" started (with errors) in 1471ms - Started 99 of 103 services (1 services failed or missing dependencies, 9 services are lazy, passive or on-demand)
> {code}
> when started using the following command:
> {code}
> JBOSS_HOME/bin/appclient.sh /foo/bar/some.jar
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] (WFLY-2093) No any log generated after changing periodic-rotating-file-handler to size-rotating-file-handler
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2093?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2093:
-----------------------------------------------
Ondrej Lukas <olukas(a)redhat.com> made a comment on [bug 1008806|https://bugzilla.redhat.com/show_bug.cgi?id=1008806]
I tried to reproduce it according your steps, but it always works fine for me. It logs WARN message but it writes another logs which looks right as usual. Is there any other needed configuration please? I can't verify it for that reason.
> No any log generated after changing periodic-rotating-file-handler to size-rotating-file-handler
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-2093
> URL: https://issues.jboss.org/browse/WFLY-2093
> Project: WildFly
> Issue Type: Bug
> Components: Logging
> Reporter: Xiaohui Wu
> Assignee: James Perkins
>
> There is no any log in the server.log after changing periodic-rotating-file-handler to size-rotating-file-handler.
> The reproduce steps:
> 1. remove the part periodic-rotating-file-handler in standalone.xml
> <periodic-rotating-file-handler name="FILE">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss.SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="server.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="true"/>
> </periodic-rotating-file-handler>
> 2. add one size-rotating-file-handler
> <size-rotating-file-handler name="FILE" autoflush="true">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p (%c) [%t] %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="server.log"/>
> <rotate-size value="500k"/>
> <max-backup-index value="15"/>
> <append value="true"/>
> </size-rotating-file-handler>
> 3. start the jboss server, then you will see there is a warning in the server.log and no any further logs in the server.log.
> 13:23:28,205 WARN [org.jboss.as.logging] (Controller Boot Thread) JBAS011511: Replacing handler 'FILE' during add operation. Either the handler type or the module name differs from the initial configuration.
> The possible fix:
> https://issues.jboss.org/browse/WFLY-178 the code change is in https://github.com/wildfly/wildfly/pull/4137
> and the bugzilla is in EAP6.1.0:
> https://bugzilla.redhat.com/show_bug.cgi?id=918103
> But this issue still exists in 6.1.1
> Best Regards,
> Vicky
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] (WFLY-553) Allow for alternative access control providers to be plugged into management.
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-553?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse updated WFLY-553:
----------------------------------
Summary: Allow for alternative access control providers to be plugged into management. (was: Implementation of a more complex ACL scheme for domain management)
Just changing the title of this issue as the next step is to formalise support for plugging in different providers, at this stage there is not an identified need for us to actually provide alternative providers ourselves.
> Allow for alternative access control providers to be plugged into management.
> -----------------------------------------------------------------------------
>
> Key: WFLY-553
> URL: https://issues.jboss.org/browse/WFLY-553
> Project: WildFly
> Issue Type: Feature Request
> Components: Domain Management, Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Labels: Authorization, Realm_Management
> Fix For: 9.0.0.CR1
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months