InvalidAlgorithmParameterException

[rahulJ james]

Can anyone suggest why do I get this exception.

I was working on the dev region, I have to format my system. I installed the jdk 1.5 version and I need to import the cacerts file using keytool.. After doing all this, I started getting this exception. Can anyone advise..

The exception says

    
java.security.InvalidAlgorithmParameterException:Prime size must be multiple of 64, and can only range from 512 to 1024 (inclusive)
	at com.sun.crypto.provider.DHKeyPairGenerator.initialize(DashoA12275)
	at java.security.KeyPairGenerator$Delegate.initialize(Unknown Source)
	at java.security.KeyPairGenerator.initialize(Unknown Source)
	at com.ibm.db2.jcc.b.ic.<init>(ic.java:75)
	at com.ibm.db2.jcc.t4.b.Mc(b.java:2334)
	at com.ibm.db2.jcc.t4.b.a(b.java:1266)
	at com.ibm.db2.jcc.t4.b.b(b.java:1255)
	at com.ibm.db2.jcc.t4.b.s(b.java:1020)
	at com.ibm.db2.jcc.t4.b.c(b.java:632)
	at com.ibm.db2.jcc.t4.b.b(b.java:618)
	at com.ibm.db2.jcc.t4.b.a(b.java:360)
	at com.ibm.db2.jcc.t4.b.<init>(b.java:298)
	at com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:193)
	at org.apache.tomcat.dbcp.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38)
	at org.apache.tomcat.dbcp.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:294)
	at org.apache.tomcat.dbcp.dbcp.BasicD

[Roberto Perillo]

Howdy, RahulJ!

Champ, can you please post the code that generates the algorithm?

Also, it looks like there is something wrong with this Prime size... according to the exception, you have to make sure it is multiple of 64 and it is within 512 and 1024.

[rahulJ james]

I did not write the code for this..I don't know where to check this either.. PLease advice

[rahulJ james]

When I meant I did noty write the code, the team did not have anything specific for this. It was working good and suddenly after I formatted teh system, I am getting this error

[Michael Angstadt]

rahulJ james wrote:I installed the jdk 1.5 version and I need to import the cacerts file using keytool..

Where are you importing the cacerts file? What was the keytool command that you ran? It looks like maybe the cacerts file got corrupted or something.

[rahulJ james]

I executed this from the c:\jre1.5\lib\security where I found the cacerts file.
Should I reinstall the jdk and try this again.

[Michael Angstadt]

rahulJ james wrote:I executed this from the c:\jre1.5\lib\security where I found the cacerts file.
Should I reinstall the jdk and try this again.

Yes, but what command did you execute? If you corrupted the cacerts file, then reinstalling the JDK should fix the problem.

[rahulJ james]

This is the command I used to import the new cert.

 
keytool -import -keystore cacerts -file newcert.txt

I will try to reinstall the JDK and try this again,

[Michael Angstadt]

The fact that your cert's filename has a ".txt" extension is strange...if it's letting you import a text file, it might be corrupting cacerts. Always make a backup of cacerts before modifying it. That way, you won't have to reinstall the JDK if something goes wrong.

Also, one minor note: The "-import" parameter is deprecated in more recent versions of the JDK. You should use "-importcert" instead (but "-import" still works).

[rahulJ james]

I got the new certnew.cer file and I imported and yet again the same result. Can it be because of something else as this error pops up from the database connectivity.

   
java.security.InvalidAlgorithmParameterException: Prime size must be multiple of 64, and can only range from 512 to 1024 (inclusive)
	at com.sun.crypto.provider.DHKeyPairGenerator.initialize(DashoA12275)
	at java.security.KeyPairGenerator$Delegate.initialize(Unknown Source)
	at java.security.KeyPairGenerator.initialize(Unknown Source)
	at com.ibm.db2.jcc.b.ic.<init>(ic.java:75)
	at com.ibm.db2.jcc.t4.b.Mc(b.java:2334)
	at com.ibm.db2.jcc.t4.b.a(b.java:1266)
	at com.ibm.db2.jcc.t4.b.b(b.java:1255)
	at com.ibm.db2.jcc.t4.b.s(b.java:1020)
	at com.ibm.db2.jcc.t4.b.c(b.java:632)
	at com.ibm.db2.jcc.t4.b.b(b.java:618)
	at com.ibm.db2.jcc.t4.b.a(b.java:360)
	at com.ibm.db2.jcc.t4.b.<init>(b.java:298)
	at com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:193)
	at org.apache.tomcat.dbcp.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38)
	at org.apache.tomcat.dbcp.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:294)
	at org.apache.tomcat.dbcp.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:1247)
	at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1221)
	at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
	at com.qwest.dao.ColaDAO.getConnection(ColaDAO.java:37)                  ->>>>> This is where I try to hit teh database
	at com.qwest.dao.UserDAO.getUserDetails(UserDAO.java:127)
	at com.qwest.action.ColaLoginAction.loginUser(ColaLoginAction.java:44)   ->>>>> This is the login action
 

[Michael Angstadt]

Do you get this error when importing the cert or connecting to the database?

What happens when you don't import the cert? Do you still get the same exception?

[rahulJ james]

Even If I don't import the certification, I get this exception.

[Michael Angstadt]

Since it's throwing this exception when you are connecting to the database, maybe the JDBC driver is out of date or not compatible with the version of the database.

[rahulJ james]

I wrote a standalone program to analyze this issue. basically I am trying to connect to DB2.

 
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.util.ArrayList;
import java.util.Date;
import java.util.Properties;

import javax.activation.DataSource;
import com.ibm.db2.jcc.DB2BaseDataSource;
import com.ibm.db2.jcc.DB2Connection;

public class MyDAO {
	public static String strDriver = "com.ibm.db2.jcc.DB2Driver";
	
	public static void main(String args[]) {
		Connection objConnection = null;
		
		try {
			System.out.println(new Date());
			Class.forName(strDriver);
			//objConnection = DriverManager.getConnection("jdbc:db2://suomt764.qintra.com:50000/DBJR","XXXXX","xxxxx");
			Properties properties = new Properties();
			properties.setProperty("securityMechanism", Integer.toString(com.ibm.db2.jcc.DB2BaseDataSource.ENCRYPTED_USER_AND_PASSWORD_SECURITY));
			properties.setProperty("user","XXXXX");
			properties.setProperty("password","xxxxx");
			objConnection = DriverManager.getConnection("jdbc:db2://suomt764.qintra.com:50000/DBJR", properties);

		} catch (ClassNotFoundException e) {
			e.printStackTrace();
		} catch (SQLException sqle) {
			sqle.printStackTrace();
		}
		System.out.println(new Date());
	}
}
   

After executing this I get the following error

 
Fri May 28 12:42:47 IST 2010
com.ibm.db2.jcc.b.SqlException: [jcc][1071][10611][3.50.152] Caught java.security.InvalidAlgorithmParameterException while initializing EncryptionManager.  See attached Throwable for details. ERRORCODE=-4223, SQLSTATE=null
	at com.ibm.db2.jcc.b.wc.a(wc.java:55)
	at com.ibm.db2.jcc.b.wc.a(wc.java:84)
	at com.ibm.db2.jcc.b.ic.<init>(ic.java:87)
	at com.ibm.db2.jcc.t4.b.Mc(b.java:2334)
	at com.ibm.db2.jcc.t4.b.v(b.java:1097)
	at com.ibm.db2.jcc.t4.b.c(b.java:648)
	at com.ibm.db2.jcc.t4.b.b(b.java:618)
	at com.ibm.db2.jcc.t4.b.a(b.java:360)
	at com.ibm.db2.jcc.t4.b.<init>(b.java:298)
	at com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:193)
	at java.sql.DriverManager.getConnection(Unknown Source)
	at java.sql.DriverManager.getConnection(Unknown Source)
	at ColaDAO.main(ColaDAO.java:29)
Caused by: java.security.InvalidAlgorithmParameterException: Prime size must be multiple of 64, and can only range from 512 to 1024 (inclusive)
	at com.sun.crypto.provider.DHKeyPairGenerator.initialize(DashoA12275)
	at java.security.KeyPairGenerator$Delegate.initialize(Unknown Source)
	at java.security.KeyPairGenerator.initialize(Unknown Source)
	at com.ibm.db2.jcc.b.ic.<init>(ic.java:75)
	... 10 more
Fri May 28 12:42:48 IST 2010