Forum Discussion

dojcsak's avatar
dojcsak
11 years ago

Error generating Analytics session ID on Linux

I'm using Open Source SoapUI 5.1.2 with JUnit.

I faced to the next issue:

18:13:19,336 INFO  [JettyMockEngine] Started mockService [Mock Response] on port [6666] at path [/webservice]
18:13:19,343 WARN  [AnalyticsManager] Error generating Analytics session ID - returning empty String
java.lang.NullPointerException
 at com.eviware.soapui.analytics.AnalyticsManager.makeUserId(AnalyticsManager.java:118)
 at com.eviware.soapui.analytics.AnalyticsManager.<init>(AnalyticsManager.java:30)
 at com.eviware.soapui.analytics.AnalyticsManager.getInstance(AnalyticsManager.java:35)
 at com.eviware.soapui.analytics.Analytics.getAnalyticsManager(Analytics.java:16)
 at com.eviware.soapui.analytics.Analytics.trackAction(Analytics.java:24)
 at com.eviware.soapui.impl.wsdl.mock.WsdlMockRunner.start(WsdlMockRunner.java:210)
 at com.eviware.soapui.impl.wsdl.mock.WsdlMockRunner.<init>(WsdlMockRunner.java:71)
 at com.eviware.soapui.impl.support.AbstractMockService.start(AbstractMockService.java:249)
 at com.eviware.soapui.impl.wsdl.teststeps.WsdlMockResponseTestStep.internalRun(WsdlMockResponseTestStep.java:389)
 at com.eviware.soapui.impl.wsdl.teststeps.WsdlMockResponseTestStep.run(WsdlMockResponseTestStep.java:354)
 at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.runTestStep(AbstractTestCaseRunner.java:213)
 at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.runCurrentTestStep(WsdlTestCaseRunner.java:47)
 at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:139)
 at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:47)
 at com.eviware.soapui.impl.wsdl.support.AbstractTestRunner.run(AbstractTestRunner.java:129)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 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:745)


It looks like a bug.

1 Reply

  • nsalomatin's avatar
    nsalomatin
    Occasional Contributor
    11 years ago
    I get this problem when I didn`t updated puTTy session ID and started soapUI pro 5.1.2.
    I also didn`t close soapUI and turn-off PC.