search

rbeckman-nextgen / test-mc

test-migration
1 stars 0 forks source link

Error after start Mirth Connect Administrator #1310

Closed rbeckman-nextgen closed 5 years ago

rbeckman-nextgen commented 5 years ago

Starting Mirth Admin the following error is displayed in log:

INFO 2012-06-08 10:51:54,249 [Thread-1] com.mirth.connect.server.Mirth: Mirth Connect 2.2.1.5861 (Built on February 28, 2012) server successfully started.

I use version 2.2.1.5861 64bit on Windows 2008 server.

INFO 2012-06-08 10:51:54,249 [Thread-1] com.mirth.connect.server.Mirth: This product was developed by Mirth Corporation (http://www.mirthcorp.com) and its contributors (c)2005-2012. INFO 2012-06-08 10:51:54,249 [Thread-1] com.mirth.connect.server.Mirth: Running Java HotSpot(TM) 64-Bit Server VM 1.6.0_31 on Windows Server 2008 R2 (6.1, amd64), derby, with charset windows-1252. ERROR 2012-06-08 10:52:41,753 [qtp4435274-54] Server: org.eclipse.jetty.io.nio.SelectorManager$SelectSet @6b482747: ERROR 2012-06-08 10:52:41,753 [qtp4435274-54] Server: org.eclipse.jetty.io.nio.SelectorManager$SelectSet @6b482747 id=0 ERROR 2012-06-08 10:52:41,753 [qtp4435274-54] Server: +- org.eclipse.jetty.io.nio.SelectorManager$SelectSet .doSelect(SelectorManager.java:539) ERROR 2012-06-08 10:52:41,753 [qtp4435274-54] Server: +- sun.nio.ch.WindowsSelectorImpl@404fe94c keys=2 ERROR 2012-06-08 10:52:41,753 [qtp4435274-54] Server: +- SCEP@170684272java.nio.channels.SocketChannel[connected local=/127.0.0.1:8080 remote=/127.0.0.1:57738][o=true d=false,io=1,w=true,rb=false,wb=false] 1 1 ERROR 2012-06-08 10:52:41,753 [qtp4435274-54] Server: +- SCEP@69248303java.nio.channels.SocketChannel[closed][o=false d=false,io=1,w=true,rb=false,wb=false] - - ERROR 2012-06-08 10:52:41,753 [qtp4435274-54] Server:

Imported Issue. Original Details: Reporter: mdehoog Created: 2012-06-16T02:54:40.000-0700

rbeckman-nextgen commented 5 years ago

Detected the same error same serverconfig & mirthversion using a sql2008 backend

there seems no degradation in functionality

Imported Comment. Original Details: Author: freddydeyucca Created: 2012-08-23T23:28:57.000-0700

rbeckman-nextgen commented 5 years ago

Issue occurs mainly on Windows Server 2008 R2 (and e.g. Sun Java JDK 6 update 33)

Can be solved by uninstalling all versions of Sun Java JRE/JDK and afterwards installation of Sun Java JDK 7 Update 17

Imported Comment. Original Details: Author: nicovn Created: 2013-03-18T03:02:21.000-0700

rbeckman-nextgen commented 5 years ago

This seems to be a problem with specific versions of Java that has since been resolved.

Imported Comment. Original Details: Author: jacobb Created: 2013-03-21T13:27:17.000-0700