the multi-release: true can make the jar behave differently on different versions of java

I really would double check the jar that is running matches the jar you have locally, like if (I haven't used beanstalk) beanstalk has the concept of staging a new version before switching to it, could you have staged a version of the jar without deploying it

yeah I'll try that once more

grasping at straws, but do you think it could be due to the case difference in the meta-inf directory name?

yes, but I would expect there to be another manifest under META-INF

are you on osx and inspecting the jar contents by unzipping?

Ah, actually on windows, looking inside with emacs, but yeah there is an identical manifest in the capitalized directory

Identical contents

?

yes exactly the same

Try repackaging the jar, unzip remove the lower case meta inf, and zip it all back up

giving that a shot now

My current guess is something about the case change is still messing things up, maybe however you are inspect file contents is also tripping over it

The case thing is so weird

It must stem from this

https://issues.apache.org/jira/browse/MJAR-73?attachmentOrder=desc

One of your dependencies may be badly packaged

No dice. Gonna give up for tonight, but thanks for the help

@jjttjj Check the app logs first! Yesterday, I was troubleshooting a very similar issue for somebody on another slack team and it was indeed because of a mismatch between build JDK version (13) and beanstalk java version (8). I know you menteiond it's running fine elsewhere but the logs should definitely give you the answer.

FWIW I install Clojure tools and run stuff in Beanstalk directly from source. Wrote a post here https://clojureverse.org/t/running-a-clojure-application-on-aws-elastic-beanstalk-with-clojure-cli-tools/4161