topic SVN commit failed - Connection reset by peer: socket write error in Talend Studio

SVN commit failed - Connection reset by peer: socket write error

stephaneB1 — Thu, 17 Oct 2013 12:36:41 GMT

Hello
With the studio of the product Talend Enterprise Data Integration release 5.1.2, I encounter some issues during the transactions with the SVN server (Apache 2.2.21/SVN) through a VPN. The issue is that the studio can't syncrhonize with the SVN, and the modifications are lost. When the studio is connected to the SVN server through the LAN, I don't encounter this issue
In the logs of the studio, I get the following message :
!ENTRY svn 4 1 2013-10-15 09:41:28.532
!MESSAGE
!STACK 0
org.talend.commons.exception.PersistenceException: org.tigris.subversion.javahl.ClientException: svn: Commit failed (details follow):
svn: Connection reset by peer: socket write error
svn: PUT request failed on '/svn_talend_repository/projecttalend/!svn/wrk/dc790ebb-4101-0010-a860-e134a21cddae/trunk/documentations/generated/jobs/t05_Output/Gap_L2Backup/createReportDiffWithL2BackupToolClientNW_1.0.item'
at org.talend.repository.svnprovider.SvnEclipseHandler.commit(SvnEclipseHandler.java:367)
at org.talend.repository.svnprovider.SvnCommitAbstractStrategy.commit(SvnCommitAbstractStrategy.java:141)
at org.talend.repository.svnprovider.SvnRepositoryFactory$2.run(SvnRepositoryFactory.java:444)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: org.tigris.subversion.javahl.ClientException: svn: Commit failed (details follow):
svn: Connection reset by peer: socket write error
svn: PUT request failed on '/svn_talend_repository/projecttalend/!svn/wrk/dc790ebb-4101-0010-a860-e134a21cddae/trunk/documentations/generated/jobs/t05_Output/Gap_L2Backup/createReportDiffWithL2BackupToolClientNW_1.0.item'
at org.tigris.subversion.javahl.JavaHLObjectFactory.throwException(JavaHLObjectFactory.java:778)
at org.tmatesoft.svn.core.javahl.SVNClientImpl.throwException(SVNClientImpl.java:1850)
at org.tmatesoft.svn.core.javahl.SVNClientImpl.commit(SVNClientImpl.java:667)
at org.talend.repository.svnprovider.SvnHandler.internalCommit(SvnHandler.java:185)
at org.talend.repository.svnprovider.SvnHandler.commit(SvnHandler.java:176)
at org.talend.repository.svnprovider.SvnEclipseHandler.commit(SvnEclipseHandler.java:350)
... 3 more
Caused by: org.tmatesoft.svn.core.SVNException: svn: Commit failed (details follow):
svn: Connection reset by peer: socket write error
svn: PUT request failed on '/svn_talend_repository/projecttalend/!svn/wrk/dc790ebb-4101-0010-a860-e134a21cddae/trunk/documentations/generated/jobs/t05_Output/Gap_L2Backup/createReportDiffWithL2BackupToolClientNW_1.0.item'
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
at org.tmatesoft.svn.core.wc.SVNCommitClient.doCommit(SVNCommitClient.java:899)
at org.tmatesoft.svn.core.wc.SVNCommitClient.doCommit(SVNCommitClient.java:828)
at org.tmatesoft.svn.core.javahl.SVNClientImpl.commit(SVNClientImpl.java:665)
... 6 more
On the SVN server, I get the following error :
Could not get next bucket brigade
I encounter this issue especially when the project is large (more than 100 jobs) and when the whole documentation has been generated.
I would like to know if someone has already encountered the same issues, an if there's a fix or a workaround.
I have already sent this issue to the official support, but I don't yet receive any solution.
Regards

Re: SVN commit failed - Connection reset by peer: socket write error

Anonymous — Thu, 17 Oct 2013 13:02:59 GMT

Hi Stephane,
I'm using the Studio connect to SVN through the VPN connection (check point) and I never have such problem while writing the Talend jobs.
- Can you see the TAC interface working through the VPN connection?
- Does your SVN server can communicate with your VPN? and the network has been tested? Do you have any firewall installed around SVN, VPN?
Kind regards,
Xin

Re: SVN commit failed - Connection reset by peer: socket write error

stephaneB1 — Thu, 17 Oct 2013 13:16:27 GMT

Hi Xin
Here are my replies :
- Can you see the TAC interface working through the VPN connection?
> Yes, I'm using the same VPN for the connection to the TAC, and I don't encounter any issue.
- Does your SVN server can communicate with your VPN? and the network has been tested? Do you have any firewall installed around SVN, VPN?
> Yes the connection between the studio and the SVN server is fully operational, and I think there are some firewalls.
This issue doesn't happen in a small project. It seems that this issue happens when they are several transactions with the SVN server, and I think that a timeout expires on the studio and the connection with the SVN is broken.
Regards

Re: SVN commit failed - Connection reset by peer: socket write error

Anonymous — Fri, 18 Oct 2013 09:01:00 GMT

The connection seems OK from VPN to SVN for you, so the network issue is out of our scope now.
As you said: "I encounter this issue especially when the project is large (more than 100 jobs) and when the whole documentation has been generated." Which interested me is, how much space the documention is taking? and if the auto-documentation is really needed in your project?

Re: SVN commit failed - Connection reset by peer: socket write error

stephaneB1 — Mon, 21 Oct 2013 13:27:11 GMT

Hi Xin
I think that the behaviour of the studio is not correct in case of large projects and with a SVN server reachable through a VPN. I think that the studio cuts the SVN transactions too earlier. If you are interested, I can provide some tcpdump traces in a private message.
The documentation is taking around 45Mbytes, and the auto-documentation option (Automatic update of corresponding documentation of job/joblet) is disabled in the preferences of the studio.
Regards

Re: SVN commit failed - Connection reset by peer: socket write error

Anonymous — Tue, 27 Oct 2015 12:42:25 GMT

Hi All,
while using the talend 5.2.3 version subscribed version, changes to the jobs are reflected in the SVN.
whereas changes performed to routines(custom code) are not getting updated to the SVN.
unable to figure out the error.SVN commit is failed.
modifications are lost. SVN & Studio are not getting synchronized.