You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Darren Scott (JIRA)" <ji...@apache.org> on 2008/03/11 12:38:46 UTC

[jira] Commented: (OFBIZ-1409) Entity synchronization not working because of RMI failure

    [ https://issues.apache.org/jira/browse/OFBIZ-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577403#action_12577403 ] 

Darren Scott commented on OFBIZ-1409:
-------------------------------------

Hi,

First off, a quick intro as I'm new, I've been working on an Ofbiz deployment for my company for the last few months. We have an incumbent semi-ERP system in place already, and we are planning to use Ofbiz primarily for the e-commerce side, with a view to replacing the rest of the system sometime in the future. 

I've had to make several source code changes to allow Ofbiz to cooperate with our systes in place, and also to fit other more generic requirements, plus some bugfixes, which I think are worth sharing with the community. I have a way to go yet, but I'm slowly getting to grips with the codebase, although I've been working with Opentaps so far and so need to migrate the either release 4.0 or trunk to start making proper contributions to the current source tree.

Anyway, this is one of the issues I have looked at, but I am in the process of documenting my changes now so won't give a full appraisal here and now, but as a pointer to anybody else having the problem:

I found three steps were needed to get the RMI SSL sockets working - 

1) generate your own certificate (obviously); 

2) turn OFF client authentication in rmi.containers (and/or ofbiz.containers, cant recall which but thats something that needs sorting) - I spent many days trying to get the client authentication working and turning if off is the only way I managed to avoid "bad certificate" messages; 

3) set the trust store explicitly on the command line "java -Djavax.net.ssl.trustStore=framework/base/config/ofbiztrust.jks -jar ofbiz.jar" - if you do a quick search of the codebase you'll see that there is *no* reference to the ofbiz.trustStore property anywhere, which is why no trusted certificates are found.

I'll try to get a more specific report on the problem in soon, and perhaps we can find a way to re-enable needsClientAuth.

> Entity synchronization not working because of RMI failure
> ---------------------------------------------------------
>
>                 Key: OFBIZ-1409
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-1409
>             Project: OFBiz
>          Issue Type: Bug
>          Components: framework
>    Affects Versions: Release Branch 4.0
>         Environment: Java VM 1.5 or 1.4
>            Reporter: Hans Bakker
>             Fix For: Release Branch 4.0
>
>
> The entity synchronization gives the eror below, The latest OFBiz version from trunk works fine and orders are pushed upstream.
> We tried to run this version with java 1.5 or 1.4, copied the
> certificates all with the same problematic result.
> thanks in advance for your help.
> ---- exception report
> ----------------------------------------------------------
> Service [remoteStoreEntitySyncDataRmi] threw an unexpected
> exception/error
> Exception: org.ofbiz.service.GenericServiceException
> Message: RMI Invocation Error (error during JRMP connection
> establishment; nested exception is: 
>         javax.net.ssl.SSLHandshakeException:
> sun.security.validator.ValidatorException: No trusted certificate found)
> ---- stack trace
> ---------------------------------------------------------------
> org.ofbiz.service.GenericServiceException: RMI Invocation Error (error
> during JRMP connection establishment; nested exception is: 
>         javax.net.ssl.SSLHandshakeException:
> sun.security.validator.ValidatorException: No trusted certificate found)
> org.ofbiz.service.rmi.RmiServiceEngine.run(RmiServiceEngine.java:66)
> org.ofbiz.service.rmi.RmiServiceEngine.runSync(RmiServiceEngine.java:41)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.