POS Sync Issue

[bhakti]

Hello all,

I am truing to setup POS Sync.
When i try to sync data over intranet it works perfectly fine.
But when i try to sync it over internet it gives connection refused to host.

I have loaded the respective data too.
Settings : on client :

1.bat file :

"%JAVA_HOME%\bin\java" -Duser.language=en_IN -Xms512M -Xmx1024M -XX:MaxPermSize=512m -Djava.rmi.server.hostname=127.0.0.1 -Djavax.net.ssl.keyStore=framework/base/config/tomcat.ks -Djavax.net.ssl.keyStorePassword=thinkhigh -jar ofbiz.jar -pos

2. service engine file :
<service-location name="entity-sync-rmi" location="rmi://www.mydomainName:1099/RMIDispatcher"/>

server .bat file :
"%JAVA_HOME%\bin\java" -Duser.language=en_IN -Xms512M -Xmx1024M -XX:MaxPermSize=512m -Djava.rmi.server.hostname=10.0.0.7  -jar ofbiz.jar

Created a certificate and keystore file for myDomain and imported it into server.
Passing the same file on startup to client.
Disabled the firewall.

I think its a certificate error. Has anyone got the same issue?

Error Message :

Exception calling remote pull and report EntitySync service with name: remotePullAndReportEntitySyncDataRmi; org.ofbiz.service.GenericServiceException: RMI Invocation Error (Connection refused to host: 10.0.1.7; nested exception is:
        java.net.ConnectException: Connection timed out: connect)
Exception: org.ofbiz.service.GenericServiceException
Message: RMI Invocation Error (Connection refused to host: 10.0.1.7; nested exception is:
        java.net.ConnectException: Connection timed out: connect)
---- cause ---------------------------------------------------------------------
Exception: java.rmi.ConnectException
Message: Connection refused to host: 10.0.1.7; nested exception is:
        java.net.ConnectException: Connection timed out: connect
---- cause ---------------------------------------------------------------------
Exception: java.net.ConnectException
Message: Connection timed out: connect
---- stack trace ---------------------------------------------------------------
java.net.ConnectException: Connection timed out: connect
java.net.PlainSocketImpl.socketConnect(Native Method)
java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
java.net.Socket.connect(Socket.java:529)
com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:570)
com.sun.net.ssl.internal.ssl.SSLSocketImpl.<init>(SSLSocketImpl.java:371)
com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl.createSocket(SSLSocketFactoryImpl.java:71)
org.ofbiz.service.rmi.socket.ssl.SSLClientSocketFactory.createSocket(SSLClientSocketFactory.java:44)
sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595)
sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198)
sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184)
sun.rmi.server.UnicastRef.invoke(UnicastRef.java:110)
org.ofbiz.service.rmi.RemoteDispatcherImpl_Stub.runSync(Unknown Source)
org.ofbiz.service.rmi.RmiServiceEngine.run(RmiServiceEngine.java:66)
org.ofbiz.service.rmi.RmiServiceEngine.runSync(RmiServiceEngine.java:42)
org.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:390)
org.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:225)
org.ofbiz.service.GenericDispatcher.runSync(GenericDispatcher.java:163)
org.ofbiz.entityext.synchronization.EntitySyncServices.runPullEntitySync(EntitySyncServices.java:303)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
org.ofbiz.service.engine.StandardJavaEngine.serviceInvoker(StandardJavaEngine.java:100)
org.ofbiz.service.engine.StandardJavaEngine.runSync(StandardJavaEngine.java:57)
org.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:390)
org.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:225)
org.ofbiz.service.GenericDispatcher.runSync(GenericDispatcher.java:163)
org.ofbiz.service.job.GenericServiceJob.exec(GenericServiceJob.java:71)
org.ofbiz.service.job.JobInvoker.run(JobInvoker.java:242)
java.lang.Thread.run(Thread.java:662)


Thanks.

[monica ford]

Hi, POS is no more part of OfBIZ13 , which is really bad. you can use trunk.
Monika

[Jacques Le Roux]

Yes, we are discussing about putting it back, with other components, in the release R13.07 branch at least. I also believe it was not a wise decision.
But it needs now to be well thought (exchanges on the dev ML) in order to get the best consensus between users needs, our (dev team) real maintenance
possibilities, our priorities and preferences and the real use of these components, WIP...

Jacques


Le 22/11/2014 03:50, monica ford a écrit :
> Hi, POS is no more part of OfBIZ13 , which is really bad. you can use trunk.
> Monika
>
>
>
> --
> View this message in context: http://ofbiz.135035.n4.nabble.com/POS-Sync-Issue-tp4655795p4658736.html
> Sent from the OFBiz - User mailing list archive at Nabble.com.
>

[mandeepmavi]

Hi Jacques,
Yes we need it back. even me spent lots of time to fix this pos. i was also depressed. even me was think to quit from Ofbiz.

Thanks for update.

[Jacques Le Roux]

HI Mandeep,



Le 25/11/2014 06:05, mandeepmavi a écrit :
> Hi Jacques,
> Yes we need it back. even me spent lots of time to fix this pos.
What do you mean exactly by "to fix this pos". To adapt it to your needs or did you fix some out of the box issues? If it's OOTB issues, did you
contribute them?
> i was also
> depressed. even me was think to quit from Ofbiz.
I'm sorry to hear that, be sure we will do our best and the POS will be part of it.

Jacques
>
> Thanks for update.
>
>
>
> --
> View this message in context: http://ofbiz.135035.n4.nabble.com/POS-Sync-Issue-tp4655795p4658908.html
> Sent from the OFBiz - User mailing list archive at Nabble.com.
>

[Pierre Smits]

Maybe Mandeep is trying to bring across that we fix releases in such a way
that (prospect) users don't have to go through hoops to get apps working
when downloading the stuff they want to work with.

Barriers don't help when adopting.

Pierre Smits

*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com

On Tue, Nov 25, 2014 at 9:01 AM, Jacques Le Roux <
[hidden email]> wrote:

> HI Mandeep,
>
>
>
> Le 25/11/2014 06:05, mandeepmavi a écrit :
>
>> Hi Jacques,
>> Yes we need it back. even me spent lots of time to fix this pos.
>>
> What do you mean exactly by "to fix this pos". To adapt it to your needs
> or did you fix some out of the box issues? If it's OOTB issues, did you
> contribute them?
>
>> i was also
>> depressed. even me was think to quit from Ofbiz.
>>
> I'm sorry to hear that, be sure we will do our best and the POS will be
> part of it.
>
> Jacques
>
>
>> Thanks for update.
>>
>>
>>
>> --
>> View this message in context: http://ofbiz.135035.n4.nabble.
>> com/POS-Sync-Issue-tp4655795p4658908.html
>> Sent from the OFBiz - User mailing list archive at Nabble.com.
>>
>>

[mandeepmavi]

Hi Jacques,
It was for my needs. With your help i was able to use this with different printers. even more I was able to document my experience.
Well i make it in row and share.

Mavi