[JBoss JIRA] (RTGOV-243) RTGov quickstart in SOA-P not reporting SLA violations
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-243?page=com.atlassian.jira.plugin.... ]
Gary Brown closed RTGOV-243.
----------------------------
> RTGov quickstart in SOA-P not reporting SLA violations
> ------------------------------------------------------
>
> Key: RTGOV-243
> URL: https://issues.jboss.org/browse/RTGOV-243
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Affects Versions: 1.0.0.Final
> Environment: SOA-P 6.0.0.ER1 installed to JBoss EAP 6.1 GA
> Reporter: Stefan Bunciak
> Assignee: Gary Brown
>
> After sending SOAP message to OrderService:
> {code}
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:switchyard-quickstart-demo:orders:1.0">
> <soapenv:Header/>
> <soapenv:Body>
> <urn:submitOrder>
> <order>
> <orderId>XYZ-126-C</orderId>
> <itemId>JAM</itemId>
> <quantity>135</quantity>
> <customer>Fred</customer>
> </order>
> </urn:submitOrder>
> </soapenv:Body>
> </soapenv:Envelope>
> {code}
> takes >500ms and should trigger SLA violation (according to rule "check for SLA violations" in SLAViolation.drl) but no WARN log present in server.log neither in gadget-web.
--
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
11 years, 4 months
[JBoss JIRA] (RTGOV-243) RTGov quickstart in SOA-P not reporting SLA violations
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-243?page=com.atlassian.jira.plugin.... ]
Gary Brown resolved RTGOV-243.
------------------------------
Resolution: Rejected
> RTGov quickstart in SOA-P not reporting SLA violations
> ------------------------------------------------------
>
> Key: RTGOV-243
> URL: https://issues.jboss.org/browse/RTGOV-243
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Affects Versions: 1.0.0.Final
> Environment: SOA-P 6.0.0.ER1 installed to JBoss EAP 6.1 GA
> Reporter: Stefan Bunciak
> Assignee: Gary Brown
>
> After sending SOAP message to OrderService:
> {code}
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:switchyard-quickstart-demo:orders:1.0">
> <soapenv:Header/>
> <soapenv:Body>
> <urn:submitOrder>
> <order>
> <orderId>XYZ-126-C</orderId>
> <itemId>JAM</itemId>
> <quantity>135</quantity>
> <customer>Fred</customer>
> </order>
> </urn:submitOrder>
> </soapenv:Body>
> </soapenv:Envelope>
> {code}
> takes >500ms and should trigger SLA violation (according to rule "check for SLA violations" in SLAViolation.drl) but no WARN log present in server.log neither in gadget-web.
--
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
11 years, 4 months
[JBoss JIRA] (RTGOV-243) RTGov quickstart in SOA-P not reporting SLA violations
by Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/RTGOV-243?page=com.atlassian.jira.plugin.... ]
Stefan Bunciak commented on RTGOV-243:
--------------------------------------
The property collectionEnabled was set to false (by default), after setting to true SLAs has been reported as expected. Thank you, can close this issue.
> RTGov quickstart in SOA-P not reporting SLA violations
> ------------------------------------------------------
>
> Key: RTGOV-243
> URL: https://issues.jboss.org/browse/RTGOV-243
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Affects Versions: 1.0.0.Final
> Environment: SOA-P 6.0.0.ER1 installed to JBoss EAP 6.1 GA
> Reporter: Stefan Bunciak
> Assignee: Gary Brown
>
> After sending SOAP message to OrderService:
> {code}
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:switchyard-quickstart-demo:orders:1.0">
> <soapenv:Header/>
> <soapenv:Body>
> <urn:submitOrder>
> <order>
> <orderId>XYZ-126-C</orderId>
> <itemId>JAM</itemId>
> <quantity>135</quantity>
> <customer>Fred</customer>
> </order>
> </urn:submitOrder>
> </soapenv:Body>
> </soapenv:Envelope>
> {code}
> takes >500ms and should trigger SLA violation (according to rule "check for SLA violations" in SLAViolation.drl) but no WARN log present in server.log neither in gadget-web.
--
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
11 years, 4 months
[JBoss JIRA] (RTGOV-243) RTGov quickstart in SOA-P not reporting SLA violations
by Stefan Bunciak (JIRA)
Stefan Bunciak created RTGOV-243:
------------------------------------
Summary: RTGov quickstart in SOA-P not reporting SLA violations
Key: RTGOV-243
URL: https://issues.jboss.org/browse/RTGOV-243
Project: RTGov (Run Time Governance)
Issue Type: Bug
Affects Versions: 1.0.0.Final
Environment: SOA-P 6.0.0.ER1 installed to JBoss EAP 6.1 GA
Reporter: Stefan Bunciak
Assignee: Gary Brown
After sending SOAP message to OrderService:
{code}
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:switchyard-quickstart-demo:orders:1.0">
<soapenv:Header/>
<soapenv:Body>
<urn:submitOrder>
<order>
<orderId>XYZ-126-C</orderId>
<itemId>JAM</itemId>
<quantity>135</quantity>
<customer>Fred</customer>
</order>
</urn:submitOrder>
</soapenv:Body>
</soapenv:Envelope>
{code}
takes >500ms and should trigger SLA violation (according to rule "check for SLA violations" in SLAViolation.drl) but no WARN log present in server.log neither in gadget-web.
--
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
11 years, 4 months