Forum Discussion
rohitgkk
14 years agoContributor
!!! FINALLY FIXED THIS ISSUE !!!
Yes, One thing I understood that we should not add any of the cglib jars to the SoapUI lib directory because of this we are facing this issue. If you add cglib jars to the SoapUI lib directory and try to invoke the testrunner.sh then it will point to tcp://localhost:7222
Justification:: If you check any of the SoapUI Linux version Installation files then you will find that there are no cglib jars in SoapUI lib directory and you will find cglib jars only in hermesJMS lib folder.
If we remove all the cglib jars from the SoapUI lib directory and try to run testrunner then you will get the error like the JMS sessions are not found.
SOLUTION:: Remove all the cglibs*.jar files from the SoapUI lib directory and add asm-2.1.jar (This jar will be present in hermesJMS/lib directory just copy to SoapUI/lib directory) this will fix the issue.
Yes, One thing I understood that we should not add any of the cglib jars to the SoapUI lib directory because of this we are facing this issue. If you add cglib jars to the SoapUI lib directory and try to invoke the testrunner.sh then it will point to tcp://localhost:7222
Justification:: If you check any of the SoapUI Linux version Installation files then you will find that there are no cglib jars in SoapUI lib directory and you will find cglib jars only in hermesJMS lib folder.
If we remove all the cglib jars from the SoapUI lib directory and try to run testrunner then you will get the error like the JMS sessions are not found.
SOLUTION:: Remove all the cglibs*.jar files from the SoapUI lib directory and add asm-2.1.jar (This jar will be present in hermesJMS/lib directory just copy to SoapUI/lib directory) this will fix the issue.
Related Content
- 8 years ago
- 9 years ago
- 10 years ago
Recent Discussions
- 18 days ago