Issue Details (XML | Word | Printable)

Key: JRA-14513
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Brad Baker [Atlassian]
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JIRA

JIRA Soap Service log footprint needs improving - Invoked Method would be handy

Created: 24/Feb/08 07:52 PM   Updated: 24/Feb/08 09:22 PM
Component/s: Remote API (SOAP & XML-RPC)
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Participants: Brad Baker [Atlassian]
Since last comment: 33 weeks ago
Labels: support_improvement


 Description  « Hide
Currently when a SOAP request comes into JIRA it lands on the AXIS servlet.

/jira/rpc/soap/jirasoapservice-v2

This is because its a POST and not a GET.

What this means is that it hard to tell what "service method" was being invoked.

From a support point of view, you cant tell what "SOAP method" is taking a long time compared to some other SOAP method or how often one method versus another is being invoked.

JIRA needs a better way to display this information.

Perhaps a second log could be added for SOAP requests. Perhaps a setting to cause this to go to the main log could be added.

We would at least need the "method" being invoked, so support can better work out what is going on



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.