Error after deploying channels

[tGitm]

Hello! 👋
I have basic database reader as source and file writer as destination. In summary tab data types are set to:

Database and everything works fine, but when i deploy a channel I get an error (I am using Java 16):
[2021-09-16 02:48:20,850] ERROR (org.quartz.core.ErrorLogger:2361): Job (d7444f3c-249a-4e4f-b3b2-1862ac874cbc.PollConnectord7444f3c-249a-4e4f-b3b2-1862ac874cbc threw an exception. org.quartz.SchedulerException: Job threw an unhandled exception. [See nested exception: java.lang.IllegalAccessError: class com.mirth.connect.connectors.jdbc.DatabaseReceiverQuery (in unnamed module @0x2ca26d77) cannot access class com.sun.rowset.CachedRowSetImpl (in module java.sql.rowset) because module java.sql.rowset does not export com.sun.rowset to unnamed module @0x2ca26d77] at org.quartz.core.JobRunShell.run(JobRunShell.java:224) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557)Caused by: java.lang.IllegalAccessError: class com.mirth.connect.connectors.jdbc.DatabaseReceiverQuery (in unnamed module @0x2ca26d77) cannot access class com.sun.rowset.CachedRowSetImpl (in module java.sql.rowset) because module java.sql.rowset does not export com.sun.rowset to unnamed module @0x2ca26d77 at com.mirth.connect.connectors.jdbc.DatabaseReceiverQuery.poll(DatabaseReceiverQuery.java:195) at com.mirth.connect.connectors.jdbc.DatabaseReceiver.poll(DatabaseReceiver.java:134) at com.mirth.connect.donkey.server.channel.PollConnectorJob.execute(PollConnectorJob.java:49) at org.quartz.core.JobRunShell.run(JobRunShell.java:213) ... 1 more

I tried to change my access to permit (#4602) in .vmoptions of mcservice and mcserver, but it didn't helped.
What else can I do? 😞

Thanks for your help! 💯

[pacmano1]

I think most folks are just not using v16 java

[tGitm]

Right now I'm downgrading to Java 13.

[tGitm]

It helped, thanks!

[tonygermano]

Did you restart your mirth server after changing the .vmoptions file? Those options only take effect on startup.

[tonygermano]

Also, once issue #4602 is resolved, you'll want to make sure to remove that from your vmoptions and not let it carry over to your new mirth version.

[tGitm]

Yes I did. Ok I'll clear them after resolving my issue :)