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

Regression reading catalog from URI between 0.12.4 & 0.13.1 #13

Closed
cmarchand opened this Issue Jul 4, 2018 · 9 comments

Comments

Projects
None yet
3 participants
@cmarchand
Copy link

cmarchand commented Jul 4, 2018

Hello,

we load catalog from a custom URL, cp:/catalog.xml, with a URLStreamHandler that implements the protocol as looking in classpath.

With xmlresolver 0.12.4, this was working correctly, but with 0.13.1, we get a java.net.ConnectionException :

org.xmlresolver.Catalog - I/O exception reading cp:/catalog.xml: java.net.ConnectException: Connection timed out

I think I'm going to have problems to get the whole exception stack trace.

Maybe a multiple use of the same InputSource ?

Best,
Christophe

@ndw

This comment has been minimized.

Copy link
Owner

ndw commented Jul 6, 2018

I don't know off the top of my head. That doesn't sound like the obvious culprit though. Same version of Java?

@ndw

This comment has been minimized.

Copy link
Owner

ndw commented Jul 7, 2018

Hi Christophe,

Can you try with 0.14.0, released today, (it's an experimental release, so I'm not suggesting you put it in production without testing!) and see if the problem has gone away?

I don't expect that it will have, but I did tinker with a some of the http stuff and I updated the httpclient library.

If it's still happening, I think I'm going to need a reproducible test case...

@AxelCourt

This comment has been minimized.

Copy link

AxelCourt commented Jul 9, 2018

Hello,

Thanks for the release and the time spent working on it.
Unfortunately it did not do the trick for us, we are getting the same java.net.ConnectException. :(

We are working on providing you with a test case (but it could be tricky since we are encountering this error in a Spring XD environment).
We will get back to you soon!

Thanks again,
Axel

@ndw

This comment has been minimized.

Copy link
Owner

ndw commented Jul 9, 2018

Ok. I've glanced through a diff between 0.12.4 and 0.13.1. There are a bunch of changes, of course, but nothing stands out as a likely culprit. Curiously, ResourceConnection where the actual I/O gets done, is unchanged. I also reviewed all the commit messages between 0.12.4 and now. Again, nothing stands out.

Can you try 0.12.5 for me?

@AxelCourt

This comment has been minimized.

Copy link

AxelCourt commented Jul 9, 2018

Hi,

I ran the program with version 0.12.5 and it seems to work as expected.
We will try and investigate a bit more to see if we find anything else suspicious and come back to you with a test case.

Thanks,
Axel

@ndw

This comment has been minimized.

Copy link
Owner

ndw commented Jul 9, 2018

Interesting. I'll help in any way I can, just let me know.

@ndw

This comment has been minimized.

Copy link
Owner

ndw commented Feb 14, 2019

Any progress on this? If not, I'm tempted to close this as "not reproducible"

@cmarchand

This comment has been minimized.

Copy link
Author

cmarchand commented Feb 14, 2019

Close it as "Not reproductible"'.
If we have again the problem, we will re-open it.

Thanks,
Christophe

@ndw

This comment has been minimized.

Copy link
Owner

ndw commented Feb 14, 2019

Thanks, Christophe!

@ndw ndw closed this Feb 14, 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.