{"action":"opened","issue":{"url":"https://api.github.com/repos/gbif/ipt/issues/1221","labels_url":"https://api.github.com/repos/gbif/ipt/issues/1221/labels{/name}","comments_url":"https://api.github.com/repos/gbif/ipt/issues/1221/comments","events_url":"https://api.github.com/repos/gbif/ipt/issues/1221/events","html_url":"https://github.com/gbif/ipt/issues/1221","id":112473853,"number":1221,"title":"Issues publishing by direct db connection after java issue","user":{"login":"bbrunet","id":12201328,"avatar_url":"https://avatars.githubusercontent.com/u/12201328?v=3","gravatar_id":"","url":"https://api.github.com/users/bbrunet","html_url":"https://github.com/bbrunet","followers_url":"https://api.github.com/users/bbrunet/followers","following_url":"https://api.github.com/users/bbrunet/following{/other_user}","gists_url":"https://api.github.com/users/bbrunet/gists{/gist_id}","starred_url":"https://api.github.com/users/bbrunet/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bbrunet/subscriptions","organizations_url":"https://api.github.com/users/bbrunet/orgs","repos_url":"https://api.github.com/users/bbrunet/repos","events_url":"https://api.github.com/users/bbrunet/events{/privacy}","received_events_url":"https://api.github.com/users/bbrunet/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-10-20T22:32:10Z","updated_at":"2015-10-20T22:32:10Z","closed_at":null,"body":"Sometime last month our system admin deleted the java version on our webserver that our IPT (v2.2) was configured with. This caused four of our resources to fail during automated monthly publishing beginning Oct. 1 with an error that reads along the lines of \"...Error writing data file for mapping Darwin Core Archive...\". Two of these failed publications occurred prior to upgrading the IPT to version 2.3.1 at the beginning of the month and two occurred afterwards (I hadn't noticed the issue until after upgrading), a version which incidentally also had inherent bugs associated with publishing via direct connection, so I subsequently upgraded to version 2.3.2. This caused the error message for the affected resources to change to a \"...Java heap space...\" issue which lead us to the assumed root of the problem (that the Java version was deleted).\r\n\r\nNow that we have re-established the path to the Java version that we're using for the IPT, I've been able to publish the two remaining resources without issue, but a problem still persists for the four affected resources. I looked at the resources in the iptdata directory (from a backup of the iptdata dir prior to upgrading to v2.3.1) and it appears that the failed attempts at publishing resulted in the current dwc-a version being deleted to make room for the new version (we don't have archival mode turned on), so even though the IPT returned back to the current version after the two failed publications prior to upgrading, those current dwc archive are no longer available. Also, contrary to the write error message noted above, the archive for the pending version was still saved. Despite this, subsequent attempts to publish also continue to fail. \r\n\r\nThere is slightly different handling of the dwc archives for the two resources that failed after upgrading to v.2.3.1, namely that the iptdata/resource directories for the two resources now have dwc-a archives for both the current and pending versions, but when attempting to publish manually nothing happens following the \"Are you sure?\" window.\r\n\r\nI've also noticed that the current version and pending versions on the manage resources pages for the affected resources are not present in the version history on each of these resources' home pages. The two resources that failed prior to upgrading to v.2.3.1 indicate on their home pages that the most recent versions are actually two versions prior to the current versions indicated on their manage resource pages (eg. 1.3 versus 1.5, respectively). Similarily, the two resources that failed after upgrading to v2.3.1 also have discrepancies between the version history and the current version, except that the difference is only a single version (eg. 1.4 versus 1.5). The unaffected resources show all published versions as expected. \r\n\r\nIn summary, now that the Java issue has been resolved, and confirmation that fixing this has restored successful publishing of the two unaffected resources, I am still unable to publish the four affected resources.\r\n\r\nAny help resolving this/these issues would be greatly appreciated! \r\n\r\nThanks,\r\nBryan Brunet\r\nUniversity of Alberta Museums"}}