[JBoss JIRA] (WFWIP-151) HTTP Verb OPTIONS requires to have Accept header defined, response should provide some guidance about this
by Rostislav Svoboda (Jira)
[ https://issues.jboss.org/browse/WFWIP-151?page=com.atlassian.jira.plugin.... ]
Rostislav Svoboda updated WFWIP-151:
------------------------------------
Description:
HTTP Verb OPTIONS requires to have Accept header defined
{code}
$ curl -X OPTIONS http://127.0.0.1:10090/metrics/vendor
No exporter found for method OPTIONS and media type
{code}
I have to specify json mediatype
{code}
curl -X OPTIONS -H "Accept: application/json" http://127.0.0.1:10090/metrics/vendor
{code}
I was expecting that I get -the json response or at least more- helpful message.
OpenLiberty returns
{code}
Error 406: CWMMC0000I: The accept header format */* is incorrect.
{code}
which at least points user to define proper header
Update:
Spec requires header to be defined, so WF could be a bit more helpful in the response message
{code}
The implementation must return a 406 response code if the request’s HTTP Accept header
for an OPTIONS request does not match application/json.
{code}
was:
HTTP Verb OPTIONS requires to have Accept header defined
{code}
$ curl -X OPTIONS http://127.0.0.1:10090/metrics/vendor
No exporter found for method OPTIONS and media type
{code}
I have to specify json mediatype
{code}
curl -X OPTIONS -H "Accept: application/json" http://127.0.0.1:10090/metrics/vendor
{code}
I was expecting that I get -the json response or at least more- helpful message.
OpenLiberty returns {{Error 406: CWMMC0000I: The accept header format */* is incorrect.}} which at least points user to define proper header
Update: Spec requires header to be defined, so WF could be a bit more helpful in the response message
{code}
The implementation must return a 406 response code if the request’s HTTP Accept header
for an OPTIONS request does not match application/json.
{code}
> HTTP Verb OPTIONS requires to have Accept header defined, response should provide some guidance about this
> ----------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-151
> URL: https://issues.jboss.org/browse/WFWIP-151
> Project: WildFly WIP
> Issue Type: Bug
> Components: MP Metrics
> Reporter: Rostislav Svoboda
> Assignee: Jeff Mesnil
> Priority: Major
>
> HTTP Verb OPTIONS requires to have Accept header defined
> {code}
> $ curl -X OPTIONS http://127.0.0.1:10090/metrics/vendor
> No exporter found for method OPTIONS and media type
> {code}
> I have to specify json mediatype
> {code}
> curl -X OPTIONS -H "Accept: application/json" http://127.0.0.1:10090/metrics/vendor
> {code}
> I was expecting that I get -the json response or at least more- helpful message.
> OpenLiberty returns
> {code}
> Error 406: CWMMC0000I: The accept header format */* is incorrect.
> {code}
> which at least points user to define proper header
> Update:
> Spec requires header to be defined, so WF could be a bit more helpful in the response message
> {code}
> The implementation must return a 406 response code if the request’s HTTP Accept header
> for an OPTIONS request does not match application/json.
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFWIP-151) HTTP Verb OPTIONS requires to have Accept header defined
by Rostislav Svoboda (Jira)
[ https://issues.jboss.org/browse/WFWIP-151?page=com.atlassian.jira.plugin.... ]
Rostislav Svoboda updated WFWIP-151:
------------------------------------
Description:
HTTP Verb OPTIONS requires to have Accept header defined
{code}
$ curl -X OPTIONS http://127.0.0.1:10090/metrics/vendor
No exporter found for method OPTIONS and media type
{code}
I have to specify json mediatype
{code}
curl -X OPTIONS -H "Accept: application/json" http://127.0.0.1:10090/metrics/vendor
{code}
I was expecting that I get -the json response or at least more- helpful message.
OpenLiberty returns {{Error 406: CWMMC0000I: The accept header format */* is incorrect.}} which at least points user to define proper header
Update: Spec requires header to be defined, so WF could be a bit more helpful in the response message
{code}
The implementation must return a 406 response code if the request’s HTTP Accept header
for an OPTIONS request does not match application/json.
{code}
was:
HTTP Verb OPTIONS requires to have Accept header defined
{code}
$ curl -X OPTIONS http://127.0.0.1:10090/metrics/vendor
No exporter found for method OPTIONS and media type
{code}
I have to specify json mediatype
{code}
curl -X OPTIONS -H "Accept: application/json" http://127.0.0.1:10090/metrics/vendor
{code}
I was expecting that I get the json response or at least more helpful message.
OpenLiberty returns {{Error 406: CWMMC0000I: The accept header format */* is incorrect.}} which at least points user to define proper header
> HTTP Verb OPTIONS requires to have Accept header defined
> --------------------------------------------------------
>
> Key: WFWIP-151
> URL: https://issues.jboss.org/browse/WFWIP-151
> Project: WildFly WIP
> Issue Type: Bug
> Components: MP Metrics
> Reporter: Rostislav Svoboda
> Assignee: Jeff Mesnil
> Priority: Major
>
> HTTP Verb OPTIONS requires to have Accept header defined
> {code}
> $ curl -X OPTIONS http://127.0.0.1:10090/metrics/vendor
> No exporter found for method OPTIONS and media type
> {code}
> I have to specify json mediatype
> {code}
> curl -X OPTIONS -H "Accept: application/json" http://127.0.0.1:10090/metrics/vendor
> {code}
> I was expecting that I get -the json response or at least more- helpful message.
> OpenLiberty returns {{Error 406: CWMMC0000I: The accept header format */* is incorrect.}} which at least points user to define proper header
> Update: Spec requires header to be defined, so WF could be a bit more helpful in the response message
> {code}
> The implementation must return a 406 response code if the request’s HTTP Accept header
> for an OPTIONS request does not match application/json.
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFWIP-151) HTTP Verb OPTIONS requires to have Accept header defined, response should provide some guidance about this
by Rostislav Svoboda (Jira)
[ https://issues.jboss.org/browse/WFWIP-151?page=com.atlassian.jira.plugin.... ]
Rostislav Svoboda updated WFWIP-151:
------------------------------------
Summary: HTTP Verb OPTIONS requires to have Accept header defined, response should provide some guidance about this (was: HTTP Verb OPTIONS requires to have Accept header defined)
> HTTP Verb OPTIONS requires to have Accept header defined, response should provide some guidance about this
> ----------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-151
> URL: https://issues.jboss.org/browse/WFWIP-151
> Project: WildFly WIP
> Issue Type: Bug
> Components: MP Metrics
> Reporter: Rostislav Svoboda
> Assignee: Jeff Mesnil
> Priority: Major
>
> HTTP Verb OPTIONS requires to have Accept header defined
> {code}
> $ curl -X OPTIONS http://127.0.0.1:10090/metrics/vendor
> No exporter found for method OPTIONS and media type
> {code}
> I have to specify json mediatype
> {code}
> curl -X OPTIONS -H "Accept: application/json" http://127.0.0.1:10090/metrics/vendor
> {code}
> I was expecting that I get -the json response or at least more- helpful message.
> OpenLiberty returns {{Error 406: CWMMC0000I: The accept header format */* is incorrect.}} which at least points user to define proper header
> Update: Spec requires header to be defined, so WF could be a bit more helpful in the response message
> {code}
> The implementation must return a 406 response code if the request’s HTTP Accept header
> for an OPTIONS request does not match application/json.
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-10919) INFO message Initialized tracer=JaegerTracer is too verbose
by Juraci Paixão Kröhling (Jira)
[ https://issues.jboss.org/browse/WFLY-10919?page=com.atlassian.jira.plugin... ]
Juraci Paixão Kröhling commented on WFLY-10919:
-----------------------------------------------
I had a discussion about this with upstream at the time our QE reported that this was an issue, and their reasoning is that:
> bootstrap can be verbose because it allows for easy checks on what the actual configuration of the tracer is on production
I tend to agree with that, especially considering the usual consumers of the library but I can also understand that WildFly should be restrictive on what's logged during bootstrap, as quite a few things are happening.
Given that, I believe the best (only?) solution is indeed to set the logger to record messages with a minimal level of WARN for the `io.jaegertracing.Configuration` class.
For reference, here are a couple of GitHub resources on this:
https://github.com/jaegertracing/jaeger-client-java/pull/531
https://github.com/jaegertracing/jaeger-client-java/issues/79
> INFO message Initialized tracer=JaegerTracer is too verbose
> -----------------------------------------------------------
>
> Key: WFLY-10919
> URL: https://issues.jboss.org/browse/WFLY-10919
> Project: WildFly
> Issue Type: Bug
> Components: MP OpenTracing
> Affects Versions: 14.0.0.Beta2
> Reporter: Jan Stourac
> Assignee: Juraci Paixão Kröhling
> Priority: Major
>
> Following log message is logged during the deploy operation of a deployment:
> {code}
> 10:52:11,703 INFO [io.jaegertracing.Configuration] (ServerService Thread Pool -- 72) Initialized tracer=JaegerTracer(version=Java-0.30.6, serviceName=helloworld-rs.war, reporter=RemoteReporter(sender=UdpSender(), closeEnqueueTimeout=1000), sampler=RemoteControlledSampler(maxOperations=2000, manager=HttpSamplingManager(hostPort=localhost:5778), sampler=ProbabilisticSampler(tags={sampler.type=probabilistic, sampler.param=0.001})), tags={hostname=dhcp-10-40-5-80.brq.redhat.com, jaeger.version=Java-0.30.6, ip=10.40.5.80}, zipkinSharedRpcSpan=false, expandExceptionLogs=false)
> {code}
> This information is too verbose for INFO level. I propose to do one of following:
> # Remove this log message from INFO level - note that very similar message is also logged on DEBUG level:
> {code}
> 10:52:11,714 DEBUG [org.wildfly.microprofile.opentracing.smallrye] (ServerService Thread Pool -- 72) WFLYTRAC0001: Tracer initialized: JaegerTracer(version=Java-0.30.6, serviceName=helloworld-rs.war, reporter=RemoteReporter(sender=UdpSender(), closeEnqueueTimeout=1000), sampler=RemoteControlledSampler(maxOperations=2000, manager=HttpSamplingManager(hostPort=localhost:5778), sampler=ProbabilisticSampler(tags={sampler.type=probabilistic, sampler.param=0.001})), tags={hostname=dhcp-10-40-5-80.brq.redhat.com, jaeger.version=Java-0.30.6, ip=10.40.5.80}, zipkinSharedRpcSpan=false, expandExceptionLogs=false)
> {code}
> # Simplify the log message on INFO level to something simple, like:
> {code}
> 10:52:11,703 INFO [io.jaegertracing.Configuration] (ServerService Thread Pool -- 72) Initialized tracer for service helloworld-rs.war
> {code}
> This issue is a followup of a WFLY-10904.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFWIP-151) HTTP Verb OPTIONS requires to have Accept header defined
by Rostislav Svoboda (Jira)
Rostislav Svoboda created WFWIP-151:
---------------------------------------
Summary: HTTP Verb OPTIONS requires to have Accept header defined
Key: WFWIP-151
URL: https://issues.jboss.org/browse/WFWIP-151
Project: WildFly WIP
Issue Type: Bug
Components: MP Metrics
Reporter: Rostislav Svoboda
Assignee: Jeff Mesnil
HTTP Verb OPTIONS requires to have Accept header defined
{code}
$ curl -X OPTIONS http://127.0.0.1:10090/metrics/vendor
No exporter found for method OPTIONS and media type
{code}
I have to specify json mediatype
{code}
curl -X OPTIONS -H "Accept: application/json" http://127.0.0.1:10090/metrics/vendor
{code}
I was expecting that I get the json response or at least more helpful message.
OpenLiberty returns {{Error 406: CWMMC0000I: The accept header format */* is incorrect.}} which at least points user to define proper header
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFCORE-4224) -secmgr and SECMGR=true env property doesn't work for domain.ps1 script
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFCORE-4224?page=com.atlassian.jira.plugi... ]
James Perkins moved WFLY-10504 to WFCORE-4224:
----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-4224 (was: WFLY-10504)
Component/s: Scripts
(was: Scripts)
> -secmgr and SECMGR=true env property doesn't work for domain.ps1 script
> -----------------------------------------------------------------------
>
> Key: WFCORE-4224
> URL: https://issues.jboss.org/browse/WFCORE-4224
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Reporter: Marek Kopecký
> Assignee: James Perkins
> Priority: Critical
>
> -secmgr and SECMGR=true env property doesn't work for domain.ps1 script
> Steps to reproduce:
> # start powershell
> # .\domain.bat "-secmgr"
> # WMIC PROCESS get Commandline | findstr java
> # check that "-secmgr" property is present in PC or HC
> # exit domain.bat
> # .\domain.ps1 "-secmgr"
> # WMIC PROCESS get Commandline | findstr java
> # check that "-secmgr" property is *not* present in PC or HC
> Secmgr can't be enabled also by $env:SECMGR = "true"
> This issue is not about java-opts, but it is related with WFCORE-3830
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-10919) INFO message Initialized tracer=JaegerTracer is too verbose
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-10919?page=com.atlassian.jira.plugin... ]
James Perkins commented on WFLY-10919:
--------------------------------------
Hi [~juraci.costa], yes if needed I can help there. There are also {{logging.properties}} files that need to be updated too. That said I think if we're going to use level {{INFO}} we may as well not include the configured logger and wait until the logging is reduced, if that is the plain, in jaeger. I do still feel those should be debug messages, but that fix would be required in the upstream project.
> INFO message Initialized tracer=JaegerTracer is too verbose
> -----------------------------------------------------------
>
> Key: WFLY-10919
> URL: https://issues.jboss.org/browse/WFLY-10919
> Project: WildFly
> Issue Type: Bug
> Components: MP OpenTracing
> Affects Versions: 14.0.0.Beta2
> Reporter: Jan Stourac
> Assignee: Juraci Paixão Kröhling
> Priority: Major
>
> Following log message is logged during the deploy operation of a deployment:
> {code}
> 10:52:11,703 INFO [io.jaegertracing.Configuration] (ServerService Thread Pool -- 72) Initialized tracer=JaegerTracer(version=Java-0.30.6, serviceName=helloworld-rs.war, reporter=RemoteReporter(sender=UdpSender(), closeEnqueueTimeout=1000), sampler=RemoteControlledSampler(maxOperations=2000, manager=HttpSamplingManager(hostPort=localhost:5778), sampler=ProbabilisticSampler(tags={sampler.type=probabilistic, sampler.param=0.001})), tags={hostname=dhcp-10-40-5-80.brq.redhat.com, jaeger.version=Java-0.30.6, ip=10.40.5.80}, zipkinSharedRpcSpan=false, expandExceptionLogs=false)
> {code}
> This information is too verbose for INFO level. I propose to do one of following:
> # Remove this log message from INFO level - note that very similar message is also logged on DEBUG level:
> {code}
> 10:52:11,714 DEBUG [org.wildfly.microprofile.opentracing.smallrye] (ServerService Thread Pool -- 72) WFLYTRAC0001: Tracer initialized: JaegerTracer(version=Java-0.30.6, serviceName=helloworld-rs.war, reporter=RemoteReporter(sender=UdpSender(), closeEnqueueTimeout=1000), sampler=RemoteControlledSampler(maxOperations=2000, manager=HttpSamplingManager(hostPort=localhost:5778), sampler=ProbabilisticSampler(tags={sampler.type=probabilistic, sampler.param=0.001})), tags={hostname=dhcp-10-40-5-80.brq.redhat.com, jaeger.version=Java-0.30.6, ip=10.40.5.80}, zipkinSharedRpcSpan=false, expandExceptionLogs=false)
> {code}
> # Simplify the log message on INFO level to something simple, like:
> {code}
> 10:52:11,703 INFO [io.jaegertracing.Configuration] (ServerService Thread Pool -- 72) Initialized tracer for service helloworld-rs.war
> {code}
> This issue is a followup of a WFLY-10904.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-11339) ServiceRef*TestCases fail with security manager
by Martin Choma (Jira)
Martin Choma created WFLY-11339:
-----------------------------------
Summary: ServiceRef*TestCases fail with security manager
Key: WFLY-11339
URL: https://issues.jboss.org/browse/WFLY-11339
Project: WildFly
Issue Type: Bug
Components: Test Suite
Affects Versions: 14.0.0.Final
Reporter: Martin Choma
Summary: ServiceRef*TestCases fail with security manager
* ServiceRefEarTestCase
* ServiceRefSevletTestCase
* ServiceRefTestCase
Having in common root exception like this
{noformat}
Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.io.FilePermission" "/store/repository/org/jboss/ws/cxf/jbossws-cxf-factories/5.2.4.Final/jbossws-cxf-factories-5.2.4.Final.jar" "read")" in code source "(vfs:/content/ws-serviceref-example.ear/ws-serviceref-example-servlet-client.war/WEB-INF/classes <no signer certificates>)" of "ModuleClassLoader for Module "deployment.ws-serviceref-example.ear.ws-serviceref-example-servlet-client.war" from Service Module Loader")
{noformat}
[1] https://ci.wildfly.org/viewLog.html?buildId=128138&buildTypeId=WF_MasterS...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFWIP-127) Subsystem jgroups exposes 180 metrics, no way to expose subset of metrics
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFWIP-127?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil updated WFWIP-127:
------------------------------
Summary: Subsystem jgroups exposes 180 metrics, no way to expose subset of metrics (was: Subsystem jgroups exposes 354 metrics, no way to expose subset of metrics)
> Subsystem jgroups exposes 180 metrics, no way to expose subset of metrics
> -------------------------------------------------------------------------
>
> Key: WFWIP-127
> URL: https://issues.jboss.org/browse/WFWIP-127
> Project: WildFly WIP
> Issue Type: Bug
> Components: MP Metrics
> Reporter: Rostislav Svoboda
> Assignee: Jeff Mesnil
> Priority: Critical
>
> Subsystem jgroups exposes 354 metrics
> There is no way to expose subset of metrics for subsystem
> standalone.xml
> {code}
> curl http://localhost:10090/metrics 2>/dev/null | grep -v TYPE | grep -v HELP | wc -l
> 109
> curl http://localhost:10090/metrics 2>/dev/null | grep -v TYPE | grep -v HELP | grep subsystem | cut -d_ -f 3 | sort | uniq -c
> 7 batch
> 1 datasources
> 7 ejb3
> 6 io
> 8 jca
> 1 request
> 11 transactions
> 12 undertow
> {code}
> standalone-full-ha.xml
> {code}
> curl http://localhost:10090/metrics 2>/dev/null | grep -v TYPE | grep -v HELP | wc -l
> 497
> curl http://localhost:10090/metrics 2>/dev/null | grep -v TYPE | grep -v HELP | grep subsystem | cut -d_ -f 3 | sort | uniq -c
> 7 batch
> 1 datasources
> 7 ejb3
> 6 io
> 8 jca
> 354 jgroups
> 10 messaging
> 1 request
> 11 transactions
> 18 undertow
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months