[#APIMANAGER-2243] Message tracing does not function

advertisement
[APIMANAGER-2243] Message tracing does not function properly Created:
29/Apr/14 Updated: 02/May/14 Resolved: 30/Apr/14
Status:
Project:
Component/s:
Affects
Version/s:
Fix Version/s:
Resolved
WSO2 API Manager
gateway
1.7.0
Type:
Reporter:
Resolution:
Labels:
Remaining
Estimate:
Time Spent:
Original
Estimate:
Environment:
Bug
Asanthi Kulasinghe
Cannot Reproduce
None
Not Specified
1.7.0
Priority:
Assignee:
Votes:
Highest
sanjeewa malalgoda
0
Not Specified
Not Specified
Operating System :Ubuntu 13.04
Java Version : 1.7.0
WSO2 API_Manager version : 1.7.0 (20th April pack)
WSO ELB version : 2.1.0
Setup : Cluster set up
DB - MySQL
Major
Severity:
Moderate
Estimated
Complexity:
Test cases added: Yes
Description
Message tracing feature does not function properly.
Issue 1:
Transaction ID is missing in the Gateway log for message tracing when an API is invoked.
TID: [0] [AM] [2014-04-29 13:26:17,766] DEBUG
{org.wso2.carbon.apimgt.gateway.handlers.ext.APIManagerExtensionHandler} - Inbound API
call from client to gateway: appName=aaaaaaaaa , userName=apimanager@apimanager.com ,
userAgent=Synapse-PT-HttpComponents-NIO , requestURI=/t/apimanager.com/aa1/1.0.0 ,
requestTime=Tue Apr 29 13:26:17 IST 2014 , clientIP=10.100.5.40
{org.wso2.carbon.apimgt.gateway.handlers.ext.APIManagerExtensionHandler}
TID: [0] [AM] [2014-04-29 13:26:17,776] DEBUG
{org.wso2.carbon.apimgt.gateway.handlers.ext.APIManagerExtensionHandler} - Outbound
API call from gateway to client: appName=aaaaaaaaa ,
userName=apimanager@apimanager.com , requestURI=/t/apimanager.com/aa1/1.0.0 ,
requestTime=Tue Apr 29 13:26:17 IST 2014 , EndPointURL=null
{org.wso2.carbon.apimgt.gateway.handlers.ext.APIManagerExtensionHandler}
Issue 2 (intermittent):
In and Out events related to 'getAllURITemplates' operation of 'APIKeyValidationService' are
not published on the Cassandra server.
Comments
Comment by sanjeewa malalgoda [ 29/Apr/14 ]
Please enable message tracing capability for each tenant and try this scenario. Then you will see
following message.
[2014-04-29 17:04:06,405] DEBUG - APIManagerExtensionHandler Inbound API call from
client to gateway: appName=DefaultApplication , userName=ttt@ttt.ttt ,
transactionId=11603076149214452342659 , userAgent=curl/7.32.0 ,
requestURI=/t/ttt.ttt/vvv/1.0.0 , requestTime=Tue Apr 29 17:04:06 IST 2014 ,
clientIP=10.100.1.65
[2014-04-29 17:04:06,415] DEBUG - APIManagerExtensionHandler Outbound API call from
gateway to client: appName=DefaultApplication , userName=ttt@ttt.ttt ,
transactionId=11603076149214452342659 , requestURI=/t/ttt.ttt/vvv/1.0.0 , requestTime=Tue
Apr 29 17:04:06 IST 2014 , EndPointURL=null
Thanks,
sanjeewa.
Comment by sanjeewa malalgoda [ 30/Apr/14 ]
Resolving issue after testing with 28th pack. Please verify and close jira.
Thanks,
sanjeewa.
Comment by Asanthi Kulasinghe [ 01/May/14 ]
Issue 1 is not reproducible when tenant specific message tracing is enabled.
Issue 2 is still reproducible.
Generated at Sun Mar 06 11:09:38 IST 2016 using JIRA 6.0.1#6096sha1:e4a48bd73c6b8a4d99c824976ce5808b4c85857d.
Download