Skip to content
This repository has been archived by the owner on Jul 2, 2020. It is now read-only.

Accessing Swagger UI causes crash #1

Closed
bravetarget opened this issue Sep 14, 2018 · 2 comments
Closed

Accessing Swagger UI causes crash #1

bravetarget opened this issue Sep 14, 2018 · 2 comments
Labels
bug Something isn't working

Comments

@bravetarget
Copy link

This might be a bug more suited for wavesplatform/Waves but I've only experienced this behavior while running this docker image...

Describe the bug
Navigating to the root API endpoint from a browser (which redirects to Waves REST API Swagger UI) will cause the node to crash.

To Reproduce
Steps to reproduce the behavior:

  1. Run docker image with REST API fully enabled
  2. From a browser navigate to the root of the API (i.e. localhost:6869)
  3. It should redirect to Swagger UI, then crash the node
  4. See error

Expected behavior
Swagger UI works as intended, or give an option to completely disable the serving of this feature.

Error Log

Uncaught error from thread [wavesplatform-akka.actor.default-dispatcher-7]: javax/xml/bind/annotation/XmlRootElement, shutting down JVM since 'akka.jvm-exit-on-fatal-error' is enabled for for ActorSystem[wavesplatform]
java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlRootElement
	at io.swagger.jackson.ModelResolver.resolve(ModelResolver.java:270)
	at io.swagger.jackson.ModelResolver.resolve(ModelResolver.java:185)
	at io.swagger.scala.converter.SwaggerScalaModelConverter.resolve(SwaggerScalaModelConverter.scala:86)

Additional context
Attempted on local docker daemon and remote kubernetes cluster, same result...
However, I have not tested the most recent version of Waves Node to determine if this bug is isolated to this image.

Possible quick solution to introduce stability is to disable akka.jvm-exit-on-fatal-error

KardanovIR added a commit to KardanovIR/waves-node that referenced this issue Sep 24, 2018
@KardanovIR
Copy link
Contributor

@bravetarget thank you for your report! This issue should be fixed with 409298d. Can you check it again, please?

@KardanovIR KardanovIR added the bug Something isn't working label Sep 24, 2018
@bravetarget
Copy link
Author

@KardanovIR my pleasure. full usage test shows 409298d resolved this issue, nice work! 👍

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants