Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to push entire sites #16481

Open
bryanboza opened this issue Apr 26, 2019 · 5 comments

Comments

@bryanboza
Copy link
Contributor

commented Apr 26, 2019

Describe the bug

We have problems trying to push an entire site, After configuring the push environment I'm able to push individual pages, and assets, also check for conflicts with the integrity checker, after trying with the site, we have a connection problems

Steps to reproduce the behavior:

  1. Login
  2. Create a copy of the demo site
  3. Try to push this copy
  4. Check your logs

Here the log: https://gist.github.com/bryanboza/489cf865238318141e871a00fa502d38

FYI: Tested multiple times and get the same error

Expected behavior

We need to be able to push sites without problems

Desktop (please complete the following information):

Tested on master // Postgres // FF

@fabrizzio-dotCMS

This comment has been minimized.

Copy link
Contributor

commented Apr 26, 2019

Per Bryan request, I tried this exercise with my local copy of master and it is easily reproducible.

The Error I'm getting :

14:28:16.525 ERROR pusher.PushPublisher - An error occurred for the endpoint bf-endpoint with address 127.0.0.1:8086. Error: Already connected
com.dotcms.repackage.javax.ws.rs.ProcessingException: Already connected

@jgambarios jgambarios added Needs QA and removed Needs QA labels Apr 30, 2019

@jgambarios jgambarios added this to the Cody Current milestone Apr 30, 2019

jgambarios added a commit that referenced this issue May 17, 2019

@jgambarios

This comment has been minimized.

Copy link
Contributor

commented May 17, 2019

PR: #16593

jgambarios added a commit that referenced this issue May 20, 2019

jgambarios added a commit that referenced this issue May 20, 2019

jgambarios added a commit that referenced this issue May 20, 2019

jgambarios added a commit that referenced this issue May 20, 2019

jgambarios added a commit that referenced this issue May 20, 2019

#16481 closing streams in order to avoid Too many files open error (#…
…16593)

* #16481 closing streams in order to avoid Too many files open error

* #16481

* #16481

* #16481 Adding cache to the metadata container file content

* Revert "#16481 Adding cache to the metadata container file content"

This reverts commit b2d003c
@jgambarios

This comment has been minimized.

Copy link
Contributor

commented May 20, 2019

Further improvements will be handle in #16597

@bryanboza bryanboza added this to CODY in QA May 28, 2019

jgambarios added a commit that referenced this issue May 30, 2019

#16481 closing streams in order to avoid Too many files open error (#…
…16593)

* #16481 closing streams in order to avoid Too many files open error

* #16481

* #16481

* #16481 Adding cache to the metadata container file content

* Revert "#16481 Adding cache to the metadata container file content"

This reverts commit b2d003c

(cherry picked from commit 8275a58)
@bryanboza

This comment has been minimized.

Copy link
Contributor Author

commented May 31, 2019

Fixed, tested in the release branch, testing with the last java_version and works as expected

@bryanboza

This comment has been minimized.

Copy link
Contributor Author

commented Jun 19, 2019

Fixed, tested on master // Postgres // FF

@bryanboza bryanboza added Passed QA and removed Needs QA labels Jun 19, 2019

@bryanboza bryanboza moved this from CODY to Done in QA Jun 19, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.