Forum Discussion
Sachin_Sawe__Pr
15 years agoContributor
Robert,
I figured this one out. Basically there is a bug underlying soapui monitor with http tunnel functionality. This bug is such that if there is anything wrong with http keystore or truststore then it throws error on console but does not actually start the monitor. It however shows you the monitor in UI so user feels monitor has started but actually it has not. That is why I was getting Connection refused because the monitor was not at all running on port 8081. Please note this bug for future references so you guys can fix it.
I do have another follow up questions as I progressed further on this. But I shall create a separate topic for that
Thanks,
Sachin
I figured this one out. Basically there is a bug underlying soapui monitor with http tunnel functionality. This bug is such that if there is anything wrong with http keystore or truststore then it throws error on console but does not actually start the monitor. It however shows you the monitor in UI so user feels monitor has started but actually it has not. That is why I was getting Connection refused because the monitor was not at all running on port 8081. Please note this bug for future references so you guys can fix it.
I do have another follow up questions as I progressed further on this. But I shall create a separate topic for that
Thanks,
Sachin
Related Content
- 5 years agopaulvinders
- 5 years agormnrdi
- 9 years agogiovanni
Recent Discussions
- 4 days agominhng