New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RestException when trying to trigger a mocked rest service #648
Comments
I ended up restarting from scratch with a new project, re-creating my mocks from scratch. Maybe the problem was caused by the fact that I first created the project with Castle Mock 1.63, had some issues there (a NPE in the same class when triggering my mock server), exported it, started a new Cast Mock Docker instace with 1.65 and imported it there. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I get a HTTP 500 error when trying to call a mocked rest service. I'm using Castlemock 1.6.5 and started it via docker
In the docker logs I only have the following
Looking at the code the root cause exception is not re thrown but just logged, however I'm unable to find the logfile.
Any idea what could potentially causing this? And if not what can I do to get the log output?
The interesting thing is that the request/response log accessible via the web ui shows the correct response as configured for the mocked method
Castle Mock
docker run -d -p 8080:8080 castlemock/castlemock
The text was updated successfully, but these errors were encountered: