Skip to content
This repository has been archived by the owner on Oct 30, 2018. It is now read-only.

ImageUtil appears not to release http connections #33

Open
dkit opened this issue Nov 19, 2011 · 1 comment
Open

ImageUtil appears not to release http connections #33

dkit opened this issue Nov 19, 2011 · 1 comment

Comments

@dkit
Copy link

dkit commented Nov 19, 2011

After a while my log becomes full of these messages and it just hangs this didn't appear to be an issue in the previous version :
INFO com.gravity.goose.images.ImageUtils - org.apache.http.conn.ConnectionPoolTimeoutException: Timeout waiting for connection
....

at com.gravity.goose.images.ImageUtils$.fetchEntity(ImageUtils.scala:267)
at com.gravity.goose.images.ImageUtils$.storeImageToLocalFile(ImageUtils.scala:172)
at com.gravity.goose.images.UpgradedImageIExtractor.getLocallyStoredImage(UpgradedImageIExtractor.scala:465)
at com.gravity.goose.images.UpgradedImageIExtractor$$anonfun$com$gravity$goose$images$UpgradedImageIExtractor$$findImagesThatPassByteSizeTest$1.apply(UpgradedImageIExtractor.scala:348)
at com.gravity.goose.images.UpgradedImageIExtractor$$anonfun$com$gravity$goose$images$UpgradedImageIExtractor$$findImagesThatPassByteSizeTest$1.apply(UpgradedImageIExtractor.scala:341)
at scala.collection.Iterator$class.foreach(Iterator.scala:652)

However I was calling ImageExtractor directly and now I'm using com.gravity.goose.Goose.extractContent and it appears to be calling UpgradedImageExtractor ....

com.gravity.goose.images.UpgradedImageIExtractor.com$gravity$goose$images$UpgradedImageIExtractor$$findImagesThatPassByteSizeTest(UpgradedImageIExtractor.scala:341)

@dkit dkit closed this as completed Nov 22, 2011
@dkit dkit reopened this Nov 26, 2011
@dkit
Copy link
Author

dkit commented Nov 26, 2011

It's still happening. I tried increasing the number of max connections but it didn't help. After some checking I found that Scala should be closing these requests automatically. Any ideas on why this is happening?

Note: The StandardImageExtractor also causes this error. I have to downgrade to two versions ago to get rid of this error ...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant