Skip to content

Upgrading Mirth Connect to 4.5.0 #6156

Answered by ab-mg-23
elemle asked this question in Q&A
Discussion options

You must be logged in to vote

How are you applying the upgrade? There have been reports when using the installer sometimes older JARs of dependencies get left behind post install and it causes classpath issues amongst other oddities. Jetty was upgraded between 4.4.2 (Jetty 9.4.44) and 4.5.0 (Jetty 9.4.53). Starting in jetty 9.4.47 PathMapping.getMatch(String) was deprecated and throws an UnsupportedException so my suspicion is there's a mix of Jetty JARs still in server-lib after your uprgade.

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@elemle
Comment options

@elemle
Comment options

Answer selected by elemle
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants