• Post Reply Bookmark Topic Watch Topic
  • New Topic

InvalidAlgorithmParameterException  RSS feed

 
rahulJ james
Ranch Hand
Posts: 123
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am working on an old application with the following configuration. JRE 1.5_6 and Tomcat 5.5. I have to use this because the production environment has the same.

I ran this application 2 years back and it was working good .. I had to fix something in this application and had to set up everything now.. I did, when I started hitting the database, it throws the issue with the prime size.. I remember I posed the same topic few years back. The solution was to reinstall JRE. I did that today assuming the cacerts file under security folder would have been corrupted as I imported a certificate.. Can someone advise..

 
Brian Burress
Ranch Hand
Posts: 131
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have not run into this issue, but I have "re-configured" a Sun JRE to have the IBM security providers to run an app under Tomcat instead of Websphere so I'll throw in my 2 cents based on that experience.

Are you running with the exact same JRE in your dev environment as in Prod? By exact, I mean having made the same configuration changes to the security certificates, etc if any?

Did you install the JRE on your dev environment? If so, is it possible for you to use a copy of the production JRE instead? If not possible to copy the full JRE, what about the security policy files/certs, etc?

Also, take a look at this information Websphere DB2 While it concerns Websphere/DB2, because it has a similar exception I am wondering if you maybe need and don't have the correct ibm security provider jar available in the app or to tomcat.
 
rahulJ james
Ranch Hand
Posts: 123
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Brian.. In the prod, I have j2re1.5.0_05 wherein, In my dev, I have j2re1.5.0_06 which I think will not be a big difference.
I followed your suggestion and copied the security files from production to dev and tried.. I get the same error and also the beginning of the log says something like

 
Brian Burress
Ranch Hand
Posts: 131
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Not sure what sort of research you have done - I would encourage you to do some googling on the error your are getting. While the solutions may not pan out, there are a number of hits on the string "Security mechanism not supported. ERRORCODE=-4214, SQLSTATE=28000" such as this one which the solution was as simple as the wrong server name. T

IBM Solution

The same link also offers this link with some information that may be useful Security under DB2 Driver

 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!