Answered

Error Exception EclipseLink-4002 when running process with Bizagi JEE Plugin

Dear all,

When running the vacation leave request process with Bizagi JEE-plugin I get an error when I run the process in Develpment mode.

Error Bizagi JEE: Bizagi version could not be published. Check server log for details. - Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.5.0.v201130507-3faac2b): org.eclipse.persistence.exceptions.DatabaseException

Does anyone knows what is causing this error ?

regards

Danny

Comments (8)

photo
1

I solved the problem: happens to be the TCP/IP Port not enabled for the MS SQL server

photo
1

Dear all,

Had to reinstall sql server and bizagi on my computer.

And after creating the vacation request project again I am getting the error .

But no whatever I try I am not able to solve it .

Attached the console.log file

can anyone help me out ?

regards

Danny

photo
photo
1

Dear all,

Seems to have something to do with

JDK-6521495 : Lift 1024-bit long prime restriction on Diffie-Hellman

but how to solve it - when I had sql server 2014 running I did not have the problem.

photo
1

Dear all,

I am making some progress - I followed some of the steps in

http://stackoverflow.com/questions/6851461/java-why-does-ssl-handshake-give-could-not-generate-dh-keypair-exception

Especially where they talk about the BouncyCastle's JCE provider.

Since I noticed that the bouncycastle jar files were already in the jboss eap:

C:\BizagiJEE\10.7.0.2082\jboss-eap-6.2\modules\system\layers\base\org\bouncycastle\main\

I only changed the settings in java.security

security.provider.10=sun.security.provider.Sun

security.provider.2=sun.security.rsa.SunRsaSign

security.provider.3=com.sun.net.ssl.internal.ssl.Provider

security.provider.4=com.sun.crypto.provider.SunJCE

security.provider.5=sun.security.jgss.SunProvider

security.provider.6=com.sun.security.sasl.Provider

security.provider.7=org.jcp.xml.dsig.internal.dom.XMLDSigRI

security.provider.8=sun.security.smartcardio.SunPCSC

security.provider.9=sun.security.mscapi.SunMSCAPI

security.provider.1=org.bouncycastle.jce.provider.BouncyCastleProvider

Now when I start publishing the process the error does not appear. But it takes a long time and finally Bizagi comes with the message "index was outside the bounds of the arrary".

Clearly I am out of luck to get Bizagi working on sql server 2012. But removing and going back to sql server 2014 is not an option since I am running other programs that require 2012.

regards

Danny

photo
1

Alright looking in the server.log file reveals the problem persists:

so the bouncycastle stuff is not working although it looked promising.

So I wonder whether there is someone out there who encountered the same problem and managed to solve it .

Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "java.lang.RuntimeException: Could not generate DH keypair".

at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1352)

at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1533)

at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:1042)

at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:817)

at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:700)

at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:842)

at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:260)

... 92 more

Caused by: javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair

at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:190) [jsse.jar:1.6]

at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1747) [jsse.jar:1.6]

at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1708) [jsse.jar:1.6]

at com.sun.net.ssl.internal.ssl.SSLSocketImpl.handleException(SSLSocketImpl.java:1691) [jsse.jar:1.6]

at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1222) [jsse.jar:1.6]

at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1199) [jsse.jar:1.6]

at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1483)

... 97 more

Caused by: java.lang.RuntimeException: Could not generate DH keypair

at com.sun.net.ssl.internal.ssl.DHCrypt.<init>(DHCrypt.java:114) [jsse.jar:1.6]

at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverKeyExchange(ClientHandshaker.java:559) [jsse.jar:1.6]

at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:186) [jsse.jar:1.6]

at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:593) [jsse.jar:1.6]

at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:529) [jsse.jar:1.6]

at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:943) [jsse.jar:1.6]

at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1188) [jsse.jar:1.6]

at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1215) [jsse.jar:1.6]

... 99 more

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(DashoA13*..) [sunjce_provider.jar:1.6]

at java.security.KeyPairGenerator$Delegate.initialize(KeyPairGenerator.java:627) [rt.jar:1.6.0_45]

at com.sun.net.ssl.internal.ssl.DHCrypt.<init>(DHCrypt.java:107) [jsse.jar:1.6]

... 106 more

photo
1

here is my server.log

photo
1

Hi Danny,

I was facing the same error. I observed that this happened after my Windows get updated with some security updates. I rolled back all the recent windows updates and the problem got solved.

photo
1

Dear Chetan,

Thank you to share the solution. Regards

photo