another query on PHIN MS 3.0
Bruce Riddle
For more than a month I have been trying to get PHIN MS 3.0 up and running. PhinMS 2.8.03 has worked for what seems like years. I’ve been in touch with PHIN MS tech support they have been unable to replicate the error. I am running in Server 2012 and SQL 2012.
Here is the error message:
Timer-0|02/26|09:06:31|---- DatabaseSession: The end of the configuration file ------
|
Error: Initial SessionFactory creation failed.java.lang.NoClassDefFoundError: javax/transaction/Synchronization
Timer-0|02/26|09:06:31|RegistrationTask: java.lang.NullPointerException|
Timer-0|02/26|09:06:31|-------- RegistrationTask completed.
--------------|
Initializing Console Servlet ...
here is PHINMS_HOME: C:/PHINMS3.0/
here is PHINMS_HOME: C:/PHINMS3.0/
location is:C:\PHINMS3.0/config/sender/foldermap.xml
here is PHINMS_HOME: C:/PHINMS3.0/
Thread-11|02/26|09:34:30|Error creating connection pool for dbid: NHSCR_DB|
Thread-11|02/26|09:34:30||
Thread-11|
02/26|09:34:30|Error getting connection from connection pool|
Thread-11|02/26|09:34:30|Connection is null|
Thread-11|
02/26|09:34:30|Database connections are down or not valid. Suspending polling for 30 minutes|
here is PHINMS_HOME: C:/PHINMS3.0/
The ‘Error creating connection pool for dbid: NHSCR_DB’ appears in many logs.
I have tried to follow the 64 bit discussion. I found an error in a log that said that the said the TomCat Native Library was 32 bit and needed to be 64 bit. I replaced this file ‘tcnative-1.dll’ with the 64 bit version along with a second file and the error message disappeared.
The Wrapper Log contains this error:
INFO | jvm 1 | 2018/02/26 09:04:23 | WARNING - Unable to load the Wrapper's native library 'wrapper.dll'.
INFO | jvm 1 | 2018/02/26 09:04:23 | The file is located on the path at the following location but
INFO | jvm 1 | 2018/02/26 09:04:23 | could not be loaded:
INFO | jvm 1 | 2018/02/26 09:04:23 | C:\PHINMS3.0\bin\dbtools\hsqldb\.\wrapper.dll
INFO | jvm 1 | 2018/02/26 09:04:23 | Please verify that the file is readable by the current user
INFO | jvm 1 | 2018/02/26 09:04:23 | and that the file has not been corrupted in any way.
INFO | jvm 1 | 2018/02/26 09:04:23 | One common cause of this problem is running a 32-bit version
INFO | jvm 1 | 2018/02/26 09:04:23 | of the Wrapper with a 64-bit version of Java, or vica versa.
INFO | jvm 1 | 2018/02/26 09:04:23 | This is a 64-bit JVM.
INFO | jvm 1 | 2018/02/26 09:04:23 | Reported cause:
INFO | jvm 1 | 2018/02/26 09:04:23 | C:\PHINMS3.0\bin\dbtools\hsqldb\wrapper.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform
INFO | jvm 1 | 2018/02/26 09:04:23 | System signals will not be handled correctly.
PHINMS Tech support says I do not have to replace the Wrapper (actually 4 files) with the 64 bit version but that strikes me as incorrect. All the DLLs have to be of the same bit version.
Any opinions or ideas?
Thanks.
Bruce
Lowe, Phillip (DOH)
Not a direct parallel but we had problems recently where an additional driver was added to PHINMS and what was working stopped. The added driver was a 32 bit version of sqljdbc. Java found it in the LIB folder and tried to load it with the rest of the 64 bit pieces and the error it caused prevented the working 64 bit version from working. I am not a JAVA person but I am quite uneasy at the idea of mixing 32 and 64 bit pieces.
Phill Lowe – 360 236-4261
--
---
You received this message because you are subscribed to the Google Groups "PHINMS User Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
phinms+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Schneider, Edward (MNIT)
The Java library we are using to supply the apparently missing Synchronization.class is javax.transaction_1.1.0.jar. We put it in the appserver\lib folder. (Actually we do this in Linux, but the directory location is analogous.) There are later versions of this JAR on the Web, but I am unprepared to specify which of them should be accessed for purposes of obtaining the needed Windows JAR file.
I doubt that putting in that JAR addresses your larger issue, however. It's certainly the case that PHINMS v. 3.0 runs as a 64-bit application (or several of them). Still, I had no difficulty installing PHINMS 3.0 on
a Windows 2012 R2 host, and getting it to start, from the CDC's distributed package. Admittedly I was using it with the HSQLDB default there. Which leads to the next point: You should check whether you are using the correct driver for SQL Server 2012 with
the PHINMS 3.0 installation. (In our case, for PHINMS v. 2.9 with SQL Server 2016, it was
sqljdbc41.jar, which we put into appserver\webapps\receiver\WEB-INF\lib. I believe that was tied to PHINMS's use of Java 7, in addition to the version of SQL Server. But you'll need to check the Microsoft support pages for the compatibility
matrix for your chosen version of SQL Server.)
Minnesota IT Services | Partnering with Minnesota Department of Health
625 North Robert St.
P.O. Box 64975
St. Paul, MN 55164-0975
O: 651-201-4047
Information Technology for Minnesota Government | mn.gov/mnit
Sent: Friday, March 2, 2018 10:46:53 AM
For more than a month I have been trying to get PHIN MS 3.0 up and running. PhinMS 2.8.03 has worked for what seems like years. I’ve been in touch with PHIN MS tech support they have been unable to replicate the error. I am running in Server 2012 and SQL 2012.
Schneider, Edward (MNIT)
And, by the way, the relevant connection strings for using the SQL Server JDBC's with PHINMS are the following (in the TransportDB configuration setup):
JDBC driver - com.microsoft.sqlserver.jdbc.SQLServerDriver
Database URL - jdbc:sqlserver://mdh-sql.health.state.mn.us:1433;DatabaseName=<your DB name here>
Minnesota IT Services | Partnering with Minnesota Department of Health
625 North Robert St.
P.O. Box 64975
St. Paul, MN 55164-0975
O: 651-201-4047
Information Technology for Minnesota Government | mn.gov/mnit
Sent: Friday, March 2, 2018 11:47
To: phi...@googlegroups.com
Subject: Re: another query on PHIN MS 3.0
Schneider, Edward (MNIT)
Let me correct that Database URL in my last post (it wouldn't be accessible to the web as shown, anyway):
JDBC driver - com.microsoft.sqlserver.jdbc.SQLServerDriver
Database URL - jdbc:sqlserver://<your hostname or IP address here>:1433;DatabaseName=<your DB name here>
Minnesota IT Services | Partnering with Minnesota Department of Health
625 North Robert St.
P.O. Box 64975
St. Paul, MN 55164-0975
O: 651-201-4047
Information Technology for Minnesota Government | mn.gov/mnit
Sent: Friday, March 2, 2018 12:11:18 PM
Preacher Man
Phill is spot on here. The 32 vs. 64 bit issue rears its ugly head at the JVM/OS interface (found in the DLL parts on MS OS). But it can also appear in JAR files if they expect to call different parts of the DLL interface, even though the JAVA byte code is platform agnostic (the old "compile once, run anywhere" brag).
It looks to me like there are really two problems here. Others have pointed out the need for a synchronization piece for MS SQL I believe. I'll leave that one for those with experience with that dB.
But the curious thing about your question for me is the reference to the "wrapper" for the HSQLDB service. I just checked mine an it is indeed 32 bit in PHINMS 3.0. If you want to get it to work, I think all you would
have to do is modify wrapper.conf and change wrapper.java.command to point to a 32 bit JVM, then (re) start the service. I have successfully run the PHINMS 3.0 HSQL db using a 32 bit 1.6x JVM on my ancient XP box from the command line (where the wrapper
is not needed).
Alternatively, get the 64 bit versions of wrapper and install it. Either way it runs independent of PHINMS under its own copy of a JVM, so there should be no 32 vs 64 bit issue between the two processes.
Also I'll note that the wrapper service install BAT script does look for a 64 bit wrapper... it just doesn't find it.
Let us know how things work out.
Tom
Sent: Friday, March 2, 2018 10:58 AM
To: phi...@googlegroups.com
Subject: RE: another query on PHIN MS 3.0
---
You received this message because you are subscribed to the Google Groups "PHINMS User Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to phinms+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.