WSO2 API管理器和Google Analytics（分析）

Question

I've configured my API Manager to enable google analytics, and am receiving the following error in API Manager:

2013-10-10 13:31:12,869 [-] [HttpServerWorker-1] ERROR APIMgtGoogleAnalyticsTrackingHandler String index out of range: -1 java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(String.java:1911) at org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler.trackPageView(APIMgtGoogleAnalyticsTrackingHandler.java:69) at org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler.handleRequest(APIMgtGoogleAnalyticsTrackingHandler.java:49) at org.apache.synapse.rest.API.process(API.java:252) at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RESTRequestHandler.java:76) at org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:63) at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:191) at org.apache.synapse.core.axis2.SynapseMessageReceiver.receive(SynapseMessageReceiver.java:83) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172) at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:455) at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:275) at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722)

Any ideas what I could be doing wrong?

My API Manager configuration is very simple:

<GoogleAnalyticsTracking>
   <Enabled>true</Enabled>
   <TrackingID>UA-TrackingId-1</TrackingID>
</GoogleAnalyticsTracking>

Answer 1

We haven't come across this issue in APIM with google analytics. But we have fixed the possible code block. You can try with latest APIM 1.5.0