[JBoss JIRA] (WFLY-1970) Make mod_cluster status configurable
by Radoslav Husar (JIRA)
Radoslav Husar created WFLY-1970:
------------------------------------
Summary: Make mod_cluster status configurable
Key: WFLY-1970
URL: https://issues.jboss.org/browse/WFLY-1970
Project: WildFly
Issue Type: Feature Request
Components: Clustering
Affects Versions: 8.0.0.Alpha4
Reporter: Radoslav Husar
Assignee: Radoslav Husar
Fix For: 8.0.0.Beta1
There is a TODO in UndertowEventHandlerAdapter.start(StartContext)
--
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
10 years, 7 months
[JBoss JIRA] (WFLY-1721) Access log support
by Yoshimasa Tanabe (JIRA)
[ https://issues.jboss.org/browse/WFLY-1721?page=com.atlassian.jira.plugin.... ]
Yoshimasa Tanabe edited comment on WFLY-1721 at 8/29/13 11:07 AM:
------------------------------------------------------------------
OK, It works!
{code}
[standalone@localhost:9990 /] /subsystem=undertow/server=default-server/host=default-host/setting=access-log:write-attribute(name=directory,value="$WILDFLY_HOME/standalone/log")
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
// restart WildFly
$ wget localhost:8080
$ ls $WILDFLY_HOME/standalone/log
access_log..log server.log server.log.2013-08-28
$ cat access_log..log
127.0.0.1 29/Aug/2013:14:39:31 +0000 "GET / HTTP/1.0" 200 2417
{code}
Thank you for you reply!
was (Author: emag):
OK, It works!
{code}
[standalone@localhost:9990 /] /subsystem=undertow/server=default-server/host=default-host/setting=access-log:write-attribute(name=directory,value="$WILDFLY_HOME/standalone/log")
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
// restart WildFly
$ wget localhost:8080
$ ls
access_log..log server.log server.log.2013-08-28
$ cat access_log..log
127.0.0.1 29/Aug/2013:14:39:31 +0000 "GET / HTTP/1.0" 200 2417
{code}
Thank you for you reply!
> Access log support
> ------------------
>
> Key: WFLY-1721
> URL: https://issues.jboss.org/browse/WFLY-1721
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Alpha3
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
> Fix For: 8.0.0.Beta1
>
>
> We need to expose access log configuration trough management.
--
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
10 years, 7 months
[JBoss JIRA] (WFLY-1721) Access log support
by Yoshimasa Tanabe (JIRA)
[ https://issues.jboss.org/browse/WFLY-1721?page=com.atlassian.jira.plugin.... ]
Yoshimasa Tanabe commented on WFLY-1721:
----------------------------------------
OK, It works!
{code}
[standalone@localhost:9990 /] /subsystem=undertow/server=default-server/host=default-host/setting=access-log:write-attribute(name=directory,value="$WILDFLY_HOME/standalone/log")
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
// restart WildFly
$ wget localhost:8080
$ ls
access_log..log server.log server.log.2013-08-28
$ cat access_log..log
127.0.0.1 29/Aug/2013:14:39:31 +0000 "GET / HTTP/1.0" 200 2417
{code}
Thank you for you reply!
> Access log support
> ------------------
>
> Key: WFLY-1721
> URL: https://issues.jboss.org/browse/WFLY-1721
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Alpha3
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
> Fix For: 8.0.0.Beta1
>
>
> We need to expose access log configuration trough management.
--
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
10 years, 7 months
[JBoss JIRA] (WFLY-1969) PicketLink: java.lang.LinkageError during loading javax.xml.crypto.dsig.XMLSignContext
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/WFLY-1969?page=com.atlassian.jira.plugin.... ]
Alessio Soldano reassigned WFLY-1969:
-------------------------------------
Assignee: Alessio Soldano (was: Derek Horton)
> PicketLink: java.lang.LinkageError during loading javax.xml.crypto.dsig.XMLSignContext
> --------------------------------------------------------------------------------------
>
> Key: WFLY-1969
> URL: https://issues.jboss.org/browse/WFLY-1969
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 8.0.0.Alpha4
> Reporter: Alessio Soldano
> Assignee: Alessio Soldano
> Fix For: 8.0.0.Beta1
>
>
> A linkage error javax.xml.crypto.dsig.XMLSignContext is thrown when a XMLSignatureFactory is first resolved by PicketLink (instead of the WS subsystem) on WFLY.
> This should be fixed by tuning the module dependencies in org.picketlink module, either by modifying the relative order of org.apache.santuario.xmlsec and javax.api modules, or -better by setting an exclude block as follows:
> {noformat}
> ...
> <module name="org.apache.santuario.xmlsec">
> <imports>
> <exclude path="javax/*"/>
> </imports>
> </module>
> ...
> {noformat}
--
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
10 years, 7 months