Skip to content
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

ClassNotFoundException: org.glassfish.jaxb.runtime.v2.ContextFactory #4161

Open
2 tasks done
uSlashVlad opened this issue Oct 28, 2024 · 1 comment
Open
2 tasks done

Comments

@uSlashVlad
Copy link

uSlashVlad commented Oct 28, 2024

Issue Description: Dynmap crashes on start when S3 storage type is used

  • Dynmap Version: v3.7-SNAPSHOT-948
  • Server Version: 1.21.1-128-master@d348cb8 (2024-10-21T16:23:24Z)
  • Pastebin of Configuration.txt: https://pastebin.com/HKRi3e3g
  • Pastebin of crashlogs: https://pastebin.com/p0rMJAfA
  • Steps to Replicate: Setup with Paper 1.21.1, dynmap 3.7-SNAPSHOT-948, AWS S3 bucket (with custom endpoint), restart the server
  • I have looked at all other issues and this is not a duplicate
  • I have been able to replicate this

Bucket is active and aws tool can read-write there with specified credentials (in config I masked with asterisk)

@stewi1014
Copy link

stewi1014 commented Oct 28, 2024

I would recommend trying to revert #4030, it seems a few problems for AWS's s3 were introduced with it.

files have extra null characters appended, and I've also experienced #4129 (comment) which I've since found out has incurred a cost of 30USD from AWS because Dynmap silently ran up the monthly API call limit and then a fee for excess API calls in under a day. An impressive number, so be careful.

Try reverting #4030, and see how it goes. I'm currently looking into the idea of replacing the s3 library in use and making a PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants