Mirth 4.1.1: No Webstart after Upgrade from 3.8./Mirth Service is Working #6017

ErikW1503 · 2023-12-09T13:11:28Z

ErikW1503
Dec 9, 2023

Hi Folks,
After updating from 3.8 to 4.4.1, the Webadmin no longer starts. Neither via 8080 nor 8443. The installation ran without errors. Java_home and java-version are both correct. The service itself works fine, but logging in via MCAL is not possible. 127.0.0.1:8080 cannot be opened.

JAVA_HOME=C:\Program Files\ojdkbuild\jdk-12.0.2
openjdk version "12.0.2" 2019-07-16
OpenJDK Runtime Environment (build 12.0.2+10)
OpenJDK 64-Bit Server VM (build 12.0.2+10, mixed mode, sharing)

MCAL shows: Unable to retrieve payload from HTTP request. URI: http://localhost:8080/webstart

Do you need any further information/do you have any ideas?

Thank you

Answered by ErikW1503

Dec 10, 2023

"Lastly, do you have any custom jars in any mirth directory? If yes, move those somewhere else."

This was the final clue. I had old .jar files in server-lib\database based on an very old installation an connect to mssql (2018). (mssql-jdbc-7.4.1.jre11) I just renamed the server-lib folder, did a update install, copied the sqljdbc42.jar back to that folder (do not know if necessary) and finally my server runs.
Now, i can troubleshoot if anything else fails, but the webserver is running.

View full answer

pacmano1 · 2023-12-09T14:43:33Z

pacmano1
Dec 9, 2023
Collaborator

Use the secure port, the default is 8443. https://yourip:8443/.

Also, you should be using the Mirth Admin Launcher tool, there is a separate installer for that.

0 replies

ErikW1503 · 2023-12-09T16:30:13Z

ErikW1503
Dec 9, 2023
Author

I have already tried that. The MCAL also requires a capable web server. If I can't access these ports through the browser, the MCAL won't be able to either. Netstat also didn't show port 8080 or 8443. Even a reinstall didn't solve the issue.

2 replies

pacmano1 Dec 9, 2023
Collaborator

I misread your first post... serves me right for reading it on the phone, lol.

What does mirth.log say?

On a fresh start the only thing it should have is something like:

INFO  2023-12-08 15:58:52.109 [Main Server Thread] com.mirth.connect.server.Mirth: Mirth Connect 4.4.2 (Built on October 23, 2023) server successfully started.
INFO  2023-12-08 15:58:52.116 [Main Server Thread] com.mirth.connect.server.Mirth: This product was developed by NextGen Healthcare (https://www.nextgen.com) and its contributors (c)2005-2023.
INFO  2023-12-08 15:58:52.116 [Main Server Thread] com.mirth.connect.server.Mirth: Running OpenJDK 64-Bit Server VM 1.8.0_362 on Linux (5.15.116-1-pve, amd64), mysql, with charset US-ASCII.
INFO  2023-12-08 15:58:52.117 [Main Server Thread] com.mirth.connect.server.Mirth: Web server running at http://192.168.66.121:8080/ and https://192.168.66.121:8443/

You said the service is working fine, what does that mean exactly? That Windows shows the service as running?

Here is a video of 4.4.2 insstalled with Amazon Coretto on windows 10: https://www.youtube.com/watch?v=r2QLOet6LEA, just as a reference point, not idenitcal to your set up but it just "works".

tonygermano Dec 10, 2023
Collaborator

Definitely check the mirth log. If netstat is showing nothing listening on 8080 or 8443, then either your service is not working or you've changed the default ports.

ErikW1503 · 2023-12-10T07:52:39Z

ErikW1503
Dec 10, 2023
Author

OK good Idea. But I have no Idea what to do.
WARN 2023-12-10 08:49:09.412 [Main Server Thread] com.mirth.connect.server.Mirth: Could not start web server.
javax.servlet.ServletException: com.mirth.connect.server.servlets.SwaggerServlet-4a408af5==com.mirth.connect.server.servlets.SwaggerServlet@d57634c9{jsp=null,order=2,inst=true,async=true,src=EMBEDDED:null,STARTED}
at org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:650) ~[jetty-servlet-9.4.44.v20210927.jar:9.4.44.v20210927]
at org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:415) ~[jetty-servlet-9.4.44.v20210927.jar:9.4.44.v20210927]
at org.eclipse.jetty.servlet.ServletHandler.lambda$initialize$0(ServletHandler.java:731) ~[jetty-servlet-9.4.44.v20210927.jar:9.4.44.v20210927]
at java.util.stream.SortedOps$SizedRefSortingSink.end(SortedOps.java:357) ~[?:?]
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:485) ~[?:?]
at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474) ~[?:?]
at java.util.stream.StreamSpliterators$WrappingSpliterator.forEachRemaining(StreamSpliterators.java:312) ~[?:?]
at java.util.stream.Streams$ConcatSpliterator.forEachRemaining(Streams.java:735) ~[?:?]
at java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:658) ~[?:?]
at org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:755) ~[jetty-servlet-9.4.44.v20210927.jar:9.4.44.v20210927]
at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:379) ~[jetty-servlet-9.4.44.v20210927.jar:9.4.44.v20210927]
at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:910) ~[jetty-server-9.4.44.v20210927.jar:9.4.44.v20210927]
at org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:288) ~[jetty-servlet-9.4.44.v20210927.jar:9.4.44.v20210927]
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73) ~[jetty-util-9.4.44.v20210927.jar:9.4.44.v20210927]
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169) ~[jetty-util-9.4.44.v20210927.jar:9.4.44.v20210927]
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110) ~[jetty-util-9.4.44.v20210927.jar:9.4.44.v20210927]
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97) ~[jetty-server-9.4.44.v20210927.jar:9.4.44.v20210927]
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73) ~[jetty-util-9.4.44.v20210927.jar:9.4.44.v20210927]
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169) ~[jetty-util-9.4.44.v20210927.jar:9.4.44.v20210927]
at org.eclipse.jetty.server.Server.start(Server.java:423) ~[jetty-server-9.4.44.v20210927.jar:9.4.44.v20210927]
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110) ~[jetty-util-9.4.44.v20210927.jar:9.4.44.v20210927]
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97) ~[jetty-server-9.4.44.v20210927.jar:9.4.44.v20210927]
at org.eclipse.jetty.server.Server.doStart(Server.java:387) ~[jetty-server-9.4.44.v20210927.jar:9.4.44.v20210927]
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73) ~[jetty-util-9.4.44.v20210927.jar:9.4.44.v20210927]
at com.mirth.connect.server.MirthWebServer.startup(MirthWebServer.java:380) ~[mirth-server.jar:?]
at com.mirth.connect.server.Mirth.startWebServer(Mirth.java:473) ~[mirth-server.jar:?]
at com.mirth.connect.server.Mirth.startup(Mirth.java:351) ~[mirth-server.jar:?]
at com.mirth.connect.server.Mirth.run(Mirth.java:168) ~[mirth-server.jar:?]
Caused by: java.lang.SecurityException: class "com.fasterxml.jackson.databind.ser.std.ToStringSerializerBase"'s signer information does not match signer information of other classes in the same package
at java.lang.ClassLoader.checkCerts(ClassLoader.java:1150) ~[?:?]
at java.lang.ClassLoader.preDefineClass(ClassLoader.java:905) ~[?:?]
at java.lang.ClassLoader.defineClass(ClassLoader.java:1014) ~[?:?]
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:151) ~[?:?]
at java.net.URLClassLoader.defineClass(URLClassLoader.java:515) ~[?:?]
at java.net.URLClassLoader$1.run(URLClassLoader.java:423) ~[?:?]
at java.net.URLClassLoader$1.run(URLClassLoader.java:417) ~[?:?]
at java.security.AccessController.doPrivileged(AccessController.java:689) ~[?:?]
at java.net.URLClassLoader.findClass(URLClassLoader.java:416) ~[?:?]
at java.lang.ClassLoader.loadClass(ClassLoader.java:588) ~[?:?]
at java.lang.ClassLoader.loadClass(ClassLoader.java:521) ~[?:?]
at java.lang.ClassLoader.defineClass1(Native Method) ~[?:?]
at java.lang.ClassLoader.defineClass(ClassLoader.java:1016) ~[?:?]
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:151) ~[?:?]
at java.net.URLClassLoader.defineClass(URLClassLoader.java:515) ~[?:?]
at java.net.URLClassLoader$1.run(URLClassLoader.java:423) ~[?:?]
at java.net.URLClassLoader$1.run(URLClassLoader.java:417) ~[?:?]
at java.security.AccessController.doPrivileged(AccessController.java:689) ~[?:?]
at java.net.URLClassLoader.findClass(URLClassLoader.java:416) ~[?:?]
at java.lang.ClassLoader.loadClass(ClassLoader.java:588) ~[?:?]
at java.lang.ClassLoader.loadClass(ClassLoader.java:521) ~[?:?]
at io.swagger.v3.core.util.ObjectMapperFactory.create(ObjectMapperFactory.java:99) ~[swagger-core-2.0.10.jar:2.0.10]
at io.swagger.v3.core.util.ObjectMapperFactory.createJson(ObjectMapperFactory.java:63) ~[swagger-core-2.0.10.jar:2.0.10]
at io.swagger.v3.core.util.Json.mapper(Json.java:13) ~[swagger-core-2.0.10.jar:2.0.10]
at io.swagger.v3.jaxrs2.Reader.read(Reader.java:366) ~[swagger-jaxrs2-2.0.10.jar:2.0.10]
at io.swagger.v3.jaxrs2.Reader.read(Reader.java:169) ~[swagger-jaxrs2-2.0.10.jar:2.0.10]
at io.swagger.v3.jaxrs2.Reader.read(Reader.java:196) ~[swagger-jaxrs2-2.0.10.jar:2.0.10]
at io.swagger.v3.oas.integration.GenericOpenApiContext.read(GenericOpenApiContext.java:470) ~[swagger-integration-2.0.10.jar:2.0.10]
at com.mirth.connect.server.servlets.SwaggerServlet.init(SwaggerServlet.java:77) ~[mirth-server.jar:?]
at org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:632) ~[jetty-servlet-9.4.44.v20210927.jar:9.4.44.v20210927]

1 reply

pacmano1 Dec 10, 2023
Collaborator

Looks like some sort of classpath/library problem with swagger related Jackson library stuff. If it were me, I would fire up a clean new machine and do a fresh install of a LTS java version and mirth. Probably the fastest "fix".

But you could strip all java on your current machine and reinstall a LTS release.

Lastly, do you have any custom jars in any mirth directory? If yes, move those somewhere else.

ErikW1503 · 2023-12-10T16:55:01Z

ErikW1503
Dec 10, 2023
Author

"Lastly, do you have any custom jars in any mirth directory? If yes, move those somewhere else."

This was the final clue. I had old .jar files in server-lib\database based on an very old installation an connect to mssql (2018). (mssql-jdbc-7.4.1.jre11) I just renamed the server-lib folder, did a update install, copied the sqljdbc42.jar back to that folder (do not know if necessary) and finally my server runs.
Now, i can troubleshoot if anything else fails, but the webserver is running.

1 reply

pacmano1 Dec 10, 2023
Collaborator

I don't think you need any extra ms jdbc jars in recent releases of Mirth, they are already bundled. But I defer to your troubleshooting.

ErikW1503 · 2023-12-10T17:21:00Z

ErikW1503
Dec 10, 2023
Author

Thank you for your clue.I copied it because i found this file in our "backup" installation. Just to be sure.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Mirth 4.1.1: No Webstart after Upgrade from 3.8./Mirth Service is Working #6017

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 5 comments 4 replies

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

Select a reply

Mirth 4.1.1: No Webstart after Upgrade from 3.8./Mirth Service is Working #6017

ErikW1503 Dec 9, 2023

Replies: 5 comments · 4 replies

pacmano1 Dec 9, 2023 Collaborator

ErikW1503 Dec 9, 2023 Author

pacmano1 Dec 9, 2023 Collaborator

tonygermano Dec 10, 2023 Collaborator

ErikW1503 Dec 10, 2023 Author

pacmano1 Dec 10, 2023 Collaborator

ErikW1503 Dec 10, 2023 Author

pacmano1 Dec 10, 2023 Collaborator

ErikW1503 Dec 10, 2023 Author

ErikW1503
Dec 9, 2023

Replies: 5 comments 4 replies

pacmano1
Dec 9, 2023
Collaborator

ErikW1503
Dec 9, 2023
Author

pacmano1 Dec 9, 2023
Collaborator

tonygermano Dec 10, 2023
Collaborator

ErikW1503
Dec 10, 2023
Author

pacmano1 Dec 10, 2023
Collaborator

ErikW1503
Dec 10, 2023
Author

pacmano1 Dec 10, 2023
Collaborator

ErikW1503
Dec 10, 2023
Author