[jira] [Commented] (CAMEL-11511) Camel bean binding issues
[ https://issues.apache.org/jira/browse/CAMEL-11511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074088#comment-16074088 ] ASF GitHub Bot commented on CAMEL-11511: GitHub user aldettinger opened a pull request: https://github.com/apache/camel/pull/1804 CAMEL-11511: Proposal to enhance the `BeanInfo` introspection in 2 cases Proposal to enhance the `BeanInfo` introspection in 2 cases: - A package private class implementing a 2 hop interface method - A public class implementing an interface method by an override from a package private class More info in [CAMEL-11511](https://issues.apache.org/jira/browse/CAMEL-11511). You can merge this pull request into a Git repository by running: $ git pull https://github.com/aldettinger/camel master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1804.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1804 commit 723a375e3a7f9c96659c30b5ae9504a4e1eabdbe Author: aldettingerDate: 2017-07-04T20:14:35Z Corrected issues in BeanInfo introspection commit 491f011f89dc7feccc282cfb5009956bbaf8d290 Author: aldettinger Date: 2017-06-29T16:26:48Z Implemented 2 tests showing issues in BeanInfo > Camel bean binding issues > - > > Key: CAMEL-11511 > URL: https://issues.apache.org/jira/browse/CAMEL-11511 > Project: Camel > Issue Type: Bug >Reporter: Alex Dettinger >Priority: Minor > > Tests below show 2 issues in the bean binding: > {code:java} > public class PrivatePackageClassBeanInfoTest extends CamelTestSupport { > @EndpointInject(uri = "mock:result") > protected MockEndpoint mockResult; > public static interface IA { > public String method(); > } > public static interface IB extends IA { > public String method1(); > } > class C implements IB { > @Override > public String method() { > return "C.method() has been called"; > } > @Override > public String method1() { > return "C.method1() has been called"; > } > } > public static interface IBC { > public String method(); > } > class D { > public String method() { > return "D.method() has been called"; > } > } > public class E extends D implements IBC { > } > @Test > public void getInterfaceMethodsMessUpWithMultipleLevelOfInterface() > throws InterruptedException { > mockResult.expectedBodiesReceived("C.method() has been called"); > template.sendBodyAndProperty("direct:test", "", "myObject", new C()); > mockResult.assertIsSatisfied(); > } > @Test > public void interfaceMethodImplementedByPackagePrivateUpperClassFails() > throws InterruptedException { > System.out.println(Modifier.isPublic(E.class.getModifiers())); > mockResult.expectedBodiesReceived("D.method() has been called"); > template.sendBodyAndProperty("direct:test", "", "myObject", new E()); > mockResult.assertIsSatisfied(); > } > @Override > public RouteBuilder createRouteBuilder() { > return new RouteBuilder() { > @Override > public void configure() throws Exception { > > from("direct:test").setBody(simple("${exchangeProperty.myObject.method}")).to(mockResult); > } > }; > } > } > {code} > Below messages are logged: > {noformat} > logged:org.apache.camel.language.bean.RuntimeBeanExpressionException: Failed > to invoke method: method on null due to: > org.apache.camel.RuntimeExchangeException: IllegalAccessException occurred > invoking method: public java.lang.String > PrivatePackageClassBeanInfoTest$D.method() using arguments: [] on the > exchange: Exchange[] > {noformat} > {noformat} > org.apache.camel.language.bean.RuntimeBeanExpressionException: Failed to > invoke method: method on null due to: > org.apache.camel.RuntimeExchangeException: IllegalAccessException occurred > invoking method: public java.lang.String > PrivatePackageClassBeanInfoTest$C.method() using arguments: [] on the > exchange: Exchange[] > {noformat} -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11511) Camel bean binding issues
Alex Dettinger created CAMEL-11511: -- Summary: Camel bean binding issues Key: CAMEL-11511 URL: https://issues.apache.org/jira/browse/CAMEL-11511 Project: Camel Issue Type: Bug Reporter: Alex Dettinger Priority: Minor Tests below show 2 issues in the bean binding: {code:java} public class PrivatePackageClassBeanInfoTest extends CamelTestSupport { @EndpointInject(uri = "mock:result") protected MockEndpoint mockResult; public static interface IA { public String method(); } public static interface IB extends IA { public String method1(); } class C implements IB { @Override public String method() { return "C.method() has been called"; } @Override public String method1() { return "C.method1() has been called"; } } public static interface IBC { public String method(); } class D { public String method() { return "D.method() has been called"; } } public class E extends D implements IBC { } @Test public void getInterfaceMethodsMessUpWithMultipleLevelOfInterface() throws InterruptedException { mockResult.expectedBodiesReceived("C.method() has been called"); template.sendBodyAndProperty("direct:test", "", "myObject", new C()); mockResult.assertIsSatisfied(); } @Test public void interfaceMethodImplementedByPackagePrivateUpperClassFails() throws InterruptedException { System.out.println(Modifier.isPublic(E.class.getModifiers())); mockResult.expectedBodiesReceived("D.method() has been called"); template.sendBodyAndProperty("direct:test", "", "myObject", new E()); mockResult.assertIsSatisfied(); } @Override public RouteBuilder createRouteBuilder() { return new RouteBuilder() { @Override public void configure() throws Exception { from("direct:test").setBody(simple("${exchangeProperty.myObject.method}")).to(mockResult); } }; } } {code} Below messages are logged: {noformat} logged:org.apache.camel.language.bean.RuntimeBeanExpressionException: Failed to invoke method: method on null due to: org.apache.camel.RuntimeExchangeException: IllegalAccessException occurred invoking method: public java.lang.String PrivatePackageClassBeanInfoTest$D.method() using arguments: [] on the exchange: Exchange[] {noformat} {noformat} org.apache.camel.language.bean.RuntimeBeanExpressionException: Failed to invoke method: method on null due to: org.apache.camel.RuntimeExchangeException: IllegalAccessException occurred invoking method: public java.lang.String PrivatePackageClassBeanInfoTest$C.method() using arguments: [] on the exchange: Exchange[] {noformat} -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11482) SSLContextParameters settings are not properly copied to SslContextFactory
[ https://issues.apache.org/jira/browse/CAMEL-11482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073965#comment-16073965 ] Roman Vottner commented on CAMEL-11482: --- Just a quick headsup on this issue. I've started to work on a fix (https://github.com/RovoMe/camel/commit/952175559110babf0ee7224f8045c1270dad5aa7) though I'm not sure if the code has to support Java 7 (or even 6). Also, there are probably a couple other settings that aren't copied to the SslContextFactory which I have not yet included either. What should be the strategy on these? Continue work on that issue and copy over all settings or leave them to those who need them and ask them to provide a fix/PR? Will also check how to setup unit-tests therefore, though as the method is private I guess I have to test it within createConnector(Server, JettyHttpEndpoint) and/or createHttpClient(JettyHttpEndpoint, Integer, SSLContextParameters) which use the updated method. > SSLContextParameters settings are not properly copied to SslContextFactory > -- > > Key: CAMEL-11482 > URL: https://issues.apache.org/jira/browse/CAMEL-11482 > Project: Camel > Issue Type: Bug > Components: camel-jetty >Affects Versions: 2.19.0, 2.19.1 > Environment: Max OS X, Java 8 Update 131 > Ubuntu 14.04 LTS, Java 8 Update 111 > Camel 2.19.0 > Jetty9 9.4.5v20170502 and 9.3.14.v20161028 >Reporter: Roman Vottner > Fix For: 2.19.2, 2.20.0 > > > Jetty 9.3+ excludes unsecure ciphers which end on either MD5, SHA or SHA1 by > default now. This will however remove all ciphers that are used by either > TLSv1 or TLSv1.1 and thus no ciphers remain in order to agree on a cipher for > TLSv1 or TLSv1.1 connection attempts. (Further reading: > https://github.com/eclipse/jetty.project/issues/860) > The Jetty 9 SSL configuration documentation > (https://www.eclipse.org/jetty/documentation/9.3.x/configuring-ssl.html) > states that this exclusion cipher suites can be customized by providing an > own exclusion list. On specifying SSLContextParameters like below however > will not correctly propagate this exclution cipher suites to the > SslContextFactory of Jetty and thus use the default setting which prevents > TLSv1 and TLSv1.1 connections. > {code:title=SSLContextParameters Spring Config|borderStyle=solid} > @Bean(name = "sslContextParameters") > public SSLContextParameters sslContextParameters() { > String keyStore = env.getProperty("ssl.keyStore.resource"); > URL keyStoreUrl = this.getClass().getResource(keyStore); > // http://camel.apache.org/jetty.html > KeyStoreParameters ksp = new KeyStoreParameters(); > ksp.setResource(keyStoreUrl.getPath()); > ksp.setPassword(env.getProperty("ssl.keyStore.password")); > KeyManagersParameters kmp = new KeyManagersParameters(); > kmp.setKeyStore(ksp); > kmp.setKeyPassword(env.getProperty("ssl.key.password")); > SSLContextParameters scp = new SSLContextParameters(); > scp.setKeyManagers(kmp); > // Jetty 9.3+ support only TLSv1.2 by default hence clients not > supporting this protocol will fail > List supportedSslProtocols = Arrays.asList("TLSv1", "TLSv1.1", > "TLSv1.2"); > SecureSocketProtocolsParameters protocolsParameters = new > SecureSocketProtocolsParameters(); > protocolsParameters.setSecureSocketProtocol(supportedSslProtocols); > scp.setSecureSocketProtocols(protocolsParameters); > // TLS 1.0 / 1.1 have been disabled by jetty 9.3 > // this is a first attempt to re-enable them > // see > // - > https://www.eclipse.org/jetty/documentation/9.3.x/configuring-ssl.html > // - https://github.com/eclipse/jetty.project/issues/860 > // - http://camel.apache.org/camel-configuration-utilities.html > FilterParameters cipherParameters = new FilterParameters(); > cipherParameters.getInclude().add(".*"); > cipherParameters.getExclude().add("^.*_(MD5|SHA1)$"); > scp.setCipherSuitesFilter(cipherParameters); > return scp; > } > {code} > A workaround is to use a custom JettyHttpComponent9 implementation that sets > the excludedCipherSuites manually like depicted below: > {code:title=Workaround|borderStyle=solid} > /** >* A custom jetty http component which explicitly sets the > excludedCipherSuites during creation of >* the jetty connector. >* >* Why? It seems camel does not push included/excluded cipherSuites from > {@link >* SSLContextParameters} to the {@link SslContextFactory} nor does push > explicitly listed cipher >* suites (i.e. like TLS_RSA_WITH_AES_256_CBC_SHA) to the Jetty > SSL context factory. >*/ > public static class HackedJettyHttpComponent extends JettyHttpComponent9 { > @Override > protected AbstractConnector
[jira] [Commented] (CAMEL-11321) Can CamelContext startup faster
[ https://issues.apache.org/jira/browse/CAMEL-11321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073674#comment-16073674 ] Claus Ibsen commented on CAMEL-11321: - By using a warm-up of the LRUCache then we can cut those 150-200 millis startup, when for example running Camel in Spring-Boot or elsewhere. With Spring-Boot there is plenty of Spring Boot stuff to execute that can happen concurrently while Camel is warming up. > Can CamelContext startup faster > --- > > Key: CAMEL-11321 > URL: https://issues.apache.org/jira/browse/CAMEL-11321 > Project: Camel > Issue Type: Improvement > Components: camel-core, camel-spring-boot >Reporter: Claus Ibsen > Fix For: Future > > > [~lb] have some thoughts on if we can make CamelContext startup faster, > especially when using Spring Boot. Spring Boot itself is not so fast, but > should be faster in 2.x. > For example we could consider camel-core to not do any classpath scanning for > components that are provided OOTB in camel-core, eg if using "log" endpoint, > then only check the spring registry if any custom bean of that, and if not, > then we know "log" is from camel-core and then we know its class name already > and dont need to scan the classpath. > We could take that one step further for the entire Camel release and have a > plugin that generate/keep java source file up to date from camel-core, which > has complete mapping of all component-name=component-class. > We can also do some profiling and see if there is some hot-spots. There is > also the revised work that Zoran does in starting Camel on spring / > spring-boot. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11509) Cannot set content type with parameters without specifying charset
[ https://issues.apache.org/jira/browse/CAMEL-11509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073639#comment-16073639 ] Steffen F. commented on CAMEL-11509: See also https://issues.apache.org/jira/browse/CAMEL-7886 Maybe we can now use only use {{parse}} instead without any checks. > Cannot set content type with parameters without specifying charset > -- > > Key: CAMEL-11509 > URL: https://issues.apache.org/jira/browse/CAMEL-11509 > Project: Camel > Issue Type: Bug > Components: camel-http4 >Affects Versions: 2.19.0, 2.19.1 >Reporter: Steffen F. > Fix For: 2.19.2, 2.20.0 > > > When setting a content type that does not contain a charset parameter, for > example this: > {noformat} > .setHeader("Content-Type", constant("application/json;odata=verbose")) > {noformat} > the route will fail with the following exception: > {noformat} > java.lang.IllegalArgumentException: MIME type may not contain reserved > characters > at org.apache.http.util.Args.check(Args.java:36) > at org.apache.http.entity.ContentType.create(ContentType.java:206) > at org.apache.http.entity.ContentType.create(ContentType.java:218) > at > org.apache.camel.component.http4.HttpProducer.createRequestEntity(HttpProducer.java:511) > {noformat} > although this is clearly a valid content type according to the RFC: > https://tools.ietf.org/html/rfc2045#section-5.1 > This only affects version 2.19+, because in version 4.4.6 of the > httpcomponents-core library, they changed the behavior of {{create}} to check > the mime type for semicolons, which it previously didn't. If we, however, > also use a charset parameter, you will call the {{parse}} method instead: > {noformat} > if (contentTypeString != null) { > if (contentTypeString.indexOf("charset") > 0) { > contentType = ContentType.parse(contentTypeString); > } else { > contentType = ContentType.create(contentTypeString); > } > } > {noformat} > There can be all kind of different parameters, though. Instead of checking > for charset, it should rather check for the existence of a semicolon. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11509) Cannot set content type with parameters without specifying charset
[ https://issues.apache.org/jira/browse/CAMEL-11509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073634#comment-16073634 ] Steffen F. commented on CAMEL-11509: No idea what to do really, because there seems to be a workaround for something (according to the comments): {noformat} //Check the contentType is valid or not, If not it throws an exception. //When ContentType.parse parse method parse "multipart/form-data;boundary=---j2radvtrk", //it removes "boundary" from Content-Type; I have to use contentType.create method. if (contentTypeString != null) { // using ContentType.parser for charset if (contentTypeString.indexOf("charset") > 0) { contentType = ContentType.parse(contentTypeString); } else { contentType = ContentType.create(contentTypeString); } } {noformat} which, then again, shouldn't work anymore, because {{ContentType.create}} will now throw an exception for any content type containing a semicolon. > Cannot set content type with parameters without specifying charset > -- > > Key: CAMEL-11509 > URL: https://issues.apache.org/jira/browse/CAMEL-11509 > Project: Camel > Issue Type: Bug > Components: camel-http4 >Affects Versions: 2.19.0, 2.19.1 >Reporter: Steffen F. > Fix For: 2.19.2, 2.20.0 > > > When setting a content type that does not contain a charset parameter, for > example this: > {noformat} > .setHeader("Content-Type", constant("application/json;odata=verbose")) > {noformat} > the route will fail with the following exception: > {noformat} > java.lang.IllegalArgumentException: MIME type may not contain reserved > characters > at org.apache.http.util.Args.check(Args.java:36) > at org.apache.http.entity.ContentType.create(ContentType.java:206) > at org.apache.http.entity.ContentType.create(ContentType.java:218) > at > org.apache.camel.component.http4.HttpProducer.createRequestEntity(HttpProducer.java:511) > {noformat} > although this is clearly a valid content type according to the RFC: > https://tools.ietf.org/html/rfc2045#section-5.1 > This only affects version 2.19+, because in version 4.4.6 of the > httpcomponents-core library, they changed the behavior of {{create}} to check > the mime type for semicolons, which it previously didn't. If we, however, > also use a charset parameter, you will call the {{parse}} method instead: > {noformat} > if (contentTypeString != null) { > if (contentTypeString.indexOf("charset") > 0) { > contentType = ContentType.parse(contentTypeString); > } else { > contentType = ContentType.create(contentTypeString); > } > } > {noformat} > There can be all kind of different parameters, though. Instead of checking > for charset, it should rather check for the existence of a semicolon. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11510) The consumer endpoint for Twitter component timeline/user doesn't poll the tweets even if the type is set to polling and delay attribute doesn't work
[ https://issues.apache.org/jira/browse/CAMEL-11510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073599#comment-16073599 ] Chirag Anand commented on CAMEL-11510: -- Also tried using the version 2.19.0, didn't work. Can you help me out here? > The consumer endpoint for Twitter component timeline/user doesn't poll the > tweets even if the type is set to polling and delay attribute doesn't work > - > > Key: CAMEL-11510 > URL: https://issues.apache.org/jira/browse/CAMEL-11510 > Project: Camel > Issue Type: Bug > Components: camel-twitter >Affects Versions: 2.16.2 > Environment: Any machine >Reporter: Chirag Anand >Priority: Minor > > When we try to get the tweets from timeline of a user using the consumer > endpoint timeline/user of the Twitter component. It only gets first set of > Tweets 20 tweets at max and later doesn't poll for the rest of them even > though the type is given as polling. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11321) Can CamelContext startup faster
[ https://issues.apache.org/jira/browse/CAMEL-11321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073577#comment-16073577 ] Claus Ibsen commented on CAMEL-11321: - As Caffeine cache takes 150-200 millis to startup etc we can try to have some LRUCacheFactory which initializes this in the background while Camel startup. We can look at where we use LRUCache and limit this to only when really needed so there are maybe some parts during startup that dont need that and can just use a regular bounded Map or something. > Can CamelContext startup faster > --- > > Key: CAMEL-11321 > URL: https://issues.apache.org/jira/browse/CAMEL-11321 > Project: Camel > Issue Type: Improvement > Components: camel-core, camel-spring-boot >Reporter: Claus Ibsen > Fix For: Future > > > [~lb] have some thoughts on if we can make CamelContext startup faster, > especially when using Spring Boot. Spring Boot itself is not so fast, but > should be faster in 2.x. > For example we could consider camel-core to not do any classpath scanning for > components that are provided OOTB in camel-core, eg if using "log" endpoint, > then only check the spring registry if any custom bean of that, and if not, > then we know "log" is from camel-core and then we know its class name already > and dont need to scan the classpath. > We could take that one step further for the entire Camel release and have a > plugin that generate/keep java source file up to date from camel-core, which > has complete mapping of all component-name=component-class. > We can also do some profiling and see if there is some hot-spots. There is > also the revised work that Zoran does in starting Camel on spring / > spring-boot. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11510) The consumer endpoint for Twitter component timeline/user doesn't poll the tweets even if the type is set to polling and delay attribute doesn't work
[ https://issues.apache.org/jira/browse/CAMEL-11510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073558#comment-16073558 ] Chirag Anand commented on CAMEL-11510: -- I did try with 2.18.1 too. It doesn't work either. > The consumer endpoint for Twitter component timeline/user doesn't poll the > tweets even if the type is set to polling and delay attribute doesn't work > - > > Key: CAMEL-11510 > URL: https://issues.apache.org/jira/browse/CAMEL-11510 > Project: Camel > Issue Type: Bug > Components: camel-twitter >Affects Versions: 2.16.2 > Environment: Any machine >Reporter: Chirag Anand >Priority: Minor > > When we try to get the tweets from timeline of a user using the consumer > endpoint timeline/user of the Twitter component. It only gets first set of > Tweets 20 tweets at max and later doesn't poll for the rest of them even > though the type is given as polling. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11509) Cannot set content type with parameters without specifying charset
[ https://issues.apache.org/jira/browse/CAMEL-11509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-11509: Fix Version/s: 2.20.0 2.19.2 > Cannot set content type with parameters without specifying charset > -- > > Key: CAMEL-11509 > URL: https://issues.apache.org/jira/browse/CAMEL-11509 > Project: Camel > Issue Type: Bug > Components: camel-http4 >Affects Versions: 2.19.0, 2.19.1 >Reporter: Steffen F. > Fix For: 2.19.2, 2.20.0 > > > When setting a content type that does not contain a charset parameter, for > example this: > {noformat} > .setHeader("Content-Type", constant("application/json;odata=verbose")) > {noformat} > the route will fail with the following exception: > {noformat} > java.lang.IllegalArgumentException: MIME type may not contain reserved > characters > at org.apache.http.util.Args.check(Args.java:36) > at org.apache.http.entity.ContentType.create(ContentType.java:206) > at org.apache.http.entity.ContentType.create(ContentType.java:218) > at > org.apache.camel.component.http4.HttpProducer.createRequestEntity(HttpProducer.java:511) > {noformat} > although this is clearly a valid content type according to the RFC: > https://tools.ietf.org/html/rfc2045#section-5.1 > This only affects version 2.19+, because in version 4.4.6 of the > httpcomponents-core library, they changed the behavior of {{create}} to check > the mime type for semicolons, which it previously didn't. If we, however, > also use a charset parameter, you will call the {{parse}} method instead: > {noformat} > if (contentTypeString != null) { > if (contentTypeString.indexOf("charset") > 0) { > contentType = ContentType.parse(contentTypeString); > } else { > contentType = ContentType.create(contentTypeString); > } > } > {noformat} > There can be all kind of different parameters, though. Instead of checking > for charset, it should rather check for the existence of a semicolon. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11510) The consumer endpoint for Twitter component timeline/user doesn't poll the tweets even if the type is set to polling and delay attribute doesn't work
[ https://issues.apache.org/jira/browse/CAMEL-11510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-11510: Fix Version/s: (was: 2.16.2) > The consumer endpoint for Twitter component timeline/user doesn't poll the > tweets even if the type is set to polling and delay attribute doesn't work > - > > Key: CAMEL-11510 > URL: https://issues.apache.org/jira/browse/CAMEL-11510 > Project: Camel > Issue Type: Bug > Components: camel-twitter >Affects Versions: 2.16.2 > Environment: Any machine >Reporter: Chirag Anand >Priority: Minor > > When we try to get the tweets from timeline of a user using the consumer > endpoint timeline/user of the Twitter component. It only gets first set of > Tweets 20 tweets at max and later doesn't poll for the rest of them even > though the type is given as polling. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11509) Cannot set content type with parameters without specifying charset
[ https://issues.apache.org/jira/browse/CAMEL-11509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073553#comment-16073553 ] Claus Ibsen commented on CAMEL-11509: - You are welcome to provide a patch or better as a github PR with a fix http://camel.apache.org/contributing > Cannot set content type with parameters without specifying charset > -- > > Key: CAMEL-11509 > URL: https://issues.apache.org/jira/browse/CAMEL-11509 > Project: Camel > Issue Type: Bug > Components: camel-http4 >Affects Versions: 2.19.0, 2.19.1 >Reporter: Steffen F. > > When setting a content type that does not contain a charset parameter, for > example this: > {noformat} > .setHeader("Content-Type", constant("application/json;odata=verbose")) > {noformat} > the route will fail with the following exception: > {noformat} > java.lang.IllegalArgumentException: MIME type may not contain reserved > characters > at org.apache.http.util.Args.check(Args.java:36) > at org.apache.http.entity.ContentType.create(ContentType.java:206) > at org.apache.http.entity.ContentType.create(ContentType.java:218) > at > org.apache.camel.component.http4.HttpProducer.createRequestEntity(HttpProducer.java:511) > {noformat} > although this is clearly a valid content type according to the RFC: > https://tools.ietf.org/html/rfc2045#section-5.1 > This only affects version 2.19+, because in version 4.4.6 of the > httpcomponents-core library, they changed the behavior of {{create}} to check > the mime type for semicolons, which it previously didn't. If we, however, > also use a charset parameter, you will call the {{parse}} method instead: > {noformat} > if (contentTypeString != null) { > if (contentTypeString.indexOf("charset") > 0) { > contentType = ContentType.parse(contentTypeString); > } else { > contentType = ContentType.create(contentTypeString); > } > } > {noformat} > There can be all kind of different parameters, though. Instead of checking > for charset, it should rather check for the existence of a semicolon. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11510) The consumer endpoint for Twitter component timeline/user doesn't poll the tweets even if the type is set to polling and delay attribute doesn't work
[ https://issues.apache.org/jira/browse/CAMEL-11510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-11510: Priority: Minor (was: Major) > The consumer endpoint for Twitter component timeline/user doesn't poll the > tweets even if the type is set to polling and delay attribute doesn't work > - > > Key: CAMEL-11510 > URL: https://issues.apache.org/jira/browse/CAMEL-11510 > Project: Camel > Issue Type: Bug > Components: camel-twitter >Affects Versions: 2.16.2 > Environment: Any machine >Reporter: Chirag Anand >Priority: Minor > > When we try to get the tweets from timeline of a user using the consumer > endpoint timeline/user of the Twitter component. It only gets first set of > Tweets 20 tweets at max and later doesn't poll for the rest of them even > though the type is given as polling. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11510) The consumer endpoint for Twitter component timeline/user doesn't poll the tweets even if the type is set to polling and delay attribute doesn't work
[ https://issues.apache.org/jira/browse/CAMEL-11510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073551#comment-16073551 ] Claus Ibsen commented on CAMEL-11510: - Try with newer version of Camel as 2.16.x is EOL > The consumer endpoint for Twitter component timeline/user doesn't poll the > tweets even if the type is set to polling and delay attribute doesn't work > - > > Key: CAMEL-11510 > URL: https://issues.apache.org/jira/browse/CAMEL-11510 > Project: Camel > Issue Type: Bug > Components: camel-twitter >Affects Versions: 2.16.2 > Environment: Any machine >Reporter: Chirag Anand > Fix For: 2.16.2 > > > When we try to get the tweets from timeline of a user using the consumer > endpoint timeline/user of the Twitter component. It only gets first set of > Tweets 20 tweets at max and later doesn't poll for the rest of them even > though the type is given as polling. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11510) The consumer endpoint for Twitter component timeline/user doesn't poll the tweets even if the type is set to polling and delay attribute doesn't work
Chirag Anand created CAMEL-11510: Summary: The consumer endpoint for Twitter component timeline/user doesn't poll the tweets even if the type is set to polling and delay attribute doesn't work Key: CAMEL-11510 URL: https://issues.apache.org/jira/browse/CAMEL-11510 Project: Camel Issue Type: Bug Components: camel-twitter Affects Versions: 2.16.2 Environment: Any machine Reporter: Chirag Anand Fix For: 2.16.2 When we try to get the tweets from timeline of a user using the consumer endpoint timeline/user of the Twitter component. It only gets first set of Tweets 20 tweets at max and later doesn't poll for the rest of them even though the type is given as polling. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11509) Cannot set content type with parameters without specifying charset
Steffen F. created CAMEL-11509: -- Summary: Cannot set content type with parameters without specifying charset Key: CAMEL-11509 URL: https://issues.apache.org/jira/browse/CAMEL-11509 Project: Camel Issue Type: Bug Components: camel-http4 Affects Versions: 2.19.1, 2.19.0 Reporter: Steffen F. When setting a content type that does not contain a charset parameter, for example this: {noformat} .setHeader("Content-Type", constant("application/json;odata=verbose")) {noformat} the route will fail with the following exception: {noformat} java.lang.IllegalArgumentException: MIME type may not contain reserved characters at org.apache.http.util.Args.check(Args.java:36) at org.apache.http.entity.ContentType.create(ContentType.java:206) at org.apache.http.entity.ContentType.create(ContentType.java:218) at org.apache.camel.component.http4.HttpProducer.createRequestEntity(HttpProducer.java:511) {noformat} although this is clearly a valid content type according to the RFC: https://tools.ietf.org/html/rfc2045#section-5.1 This only affects version 2.19+, because in version 4.4.6 of the httpcomponents-core library, they changed the behavior of {{create}} to check the mime type for semicolons, which it previously didn't. If we, however, also use a charset parameter, you will call the {{parse}} method instead: {noformat} if (contentTypeString != null) { if (contentTypeString.indexOf("charset") > 0) { contentType = ContentType.parse(contentTypeString); } else { contentType = ContentType.create(contentTypeString); } } {noformat} There can be all kind of different parameters, though. Instead of checking for charset, it should rather check for the existence of a semicolon. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11321) Can CamelContext startup faster
[ https://issues.apache.org/jira/browse/CAMEL-11321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073529#comment-16073529 ] Claus Ibsen commented on CAMEL-11321: - camel-spring-boot in the auto configuration creates a ProducerTemplate and ConsumerTemplate bean which may not be in-use / needed. We can look at optimising to only create them on demand, or to lazy init the bean on use etc, as its startup time cost a bit with the caffine cache > Can CamelContext startup faster > --- > > Key: CAMEL-11321 > URL: https://issues.apache.org/jira/browse/CAMEL-11321 > Project: Camel > Issue Type: Improvement > Components: camel-core, camel-spring-boot >Reporter: Claus Ibsen > Fix For: Future > > > [~lb] have some thoughts on if we can make CamelContext startup faster, > especially when using Spring Boot. Spring Boot itself is not so fast, but > should be faster in 2.x. > For example we could consider camel-core to not do any classpath scanning for > components that are provided OOTB in camel-core, eg if using "log" endpoint, > then only check the spring registry if any custom bean of that, and if not, > then we know "log" is from camel-core and then we know its class name already > and dont need to scan the classpath. > We could take that one step further for the entire Camel release and have a > plugin that generate/keep java source file up to date from camel-core, which > has complete mapping of all component-name=component-class. > We can also do some profiling and see if there is some hot-spots. There is > also the revised work that Zoran does in starting Camel on spring / > spring-boot. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (CAMEL-11508) Why "from" xml element does not support custom attributes in spring xml?
[ https://issues.apache.org/jira/browse/CAMEL-11508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-11508. - Resolution: Not A Problem Assignee: Claus Ibsen They are not used for etc but for EIPs such as splitter ,aggregator etc that has attributes with boolean, int types where you want to use property placeholders and then need to use the prop placeholder trick. The from is just an uri as string type where you can use placeholders already. > Why "from" xml element does not support custom attributes in spring xml? > > > Key: CAMEL-11508 > URL: https://issues.apache.org/jira/browse/CAMEL-11508 > Project: Camel > Issue Type: Improvement > Components: camel-spring >Affects Versions: 2.19.1 >Reporter: Artem St >Assignee: Claus Ibsen > Labels: easyfix > > Hello, > The definition of "from" element in camel-spring.xsd does not allow to use a > custom attributes, because of there is no declared anyAttribute element. > My opinion is that "from" element should allow to create user specific > attributes same as "to" element (which has a namespace="##other" processContents="skip"/> > in the definition) > There is my route: > > uri="localmq://queueStart" /> > > > And Camel gives me exception on that route: > org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line > 47 in XML document from file [C:\Projects\server\main.xml] is invalid; nested > exception is org.xml.sax.SAXParseException; lineNumber: 47; columnNumber: 83; > cvc-complex-type.3.2.2: Attribute 'yuo:custom-attr' is not allowed to appear > in element 'from'. > at > org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:399) > at > org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336) > at > org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304) > at > org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181) > at > org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:217) > at > org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188) > at > org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:252) > at > org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:127) > at > org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:93) > at > org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:129) > at > org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:613) > at > org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:514) > > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:748) > Caused by: org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute > 'yuo:custom-attr' is not allowed to appear in element 'from'. > at > org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown > Source) > at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source) > at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) > at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) > at > org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown > Source) > at > org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source) > at > org.apache.xerces.impl.xs.XMLSchemaValidator.processAttributes(Unknown Source) > at > org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown > Source) > at org.apache.xerces.impl.xs.XMLSchemaValidator.emptyElement(Unknown > Source) > at > org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown > Source) > at >
[jira] [Updated] (CAMEL-11508) Why "from" xml element does not support custom attributes in spring xml?
[ https://issues.apache.org/jira/browse/CAMEL-11508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem St updated CAMEL-11508: - Description: Hello, The definition of "from" element in camel-spring.xsd does not allow to use a custom attributes, because of there is no declared anyAttribute element. My opinion is that "from" element should allow to create user specific attributes same as "to" element (which has a in the definition) There is my route: And Camel gives me exception on that route: org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 47 in XML document from file [C:\Projects\server\main.xml] is invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 47; columnNumber: 83; cvc-complex-type.3.2.2: Attribute 'yuo:custom-attr' is not allowed to appear in element 'from'. at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:399) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:217) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:252) at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:127) at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:93) at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:129) at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:613) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:514) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748) Caused by: org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'yuo:custom-attr' is not allowed to appear in element 'from'. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.processAttributes(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.emptyElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:76) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadDocument(XmlBeanDefinitionReader.java:429) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:391) was: Hello, The definition of "from" element in camel-spring.xsd does not allow to use a custom attributes, because of
[jira] [Created] (CAMEL-11508) Why "from" xml element does not support custom attributes in spring xml?
Artem St created CAMEL-11508: Summary: Why "from" xml element does not support custom attributes in spring xml? Key: CAMEL-11508 URL: https://issues.apache.org/jira/browse/CAMEL-11508 Project: Camel Issue Type: Improvement Components: camel-spring Affects Versions: 2.19.1 Reporter: Artem St Hello, The definition of "from" element in camel-spring.xsd does not allow to use a custom attributes, because of there is no declared anyAttribute element. There is my route: And Camel gives me exception on that route: org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 47 in XML document from file [C:\Projects\server\main.xml] is invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 47; columnNumber: 83; cvc-complex-type.3.2.2: Attribute 'yuo:custom-attr' is not allowed to appear in element 'from'. at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:399) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:217) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:252) at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:127) at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:93) at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:129) at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:613) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:514) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748) Caused by: org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'yuo:custom-attr' is not allowed to appear in element 'from'. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.processAttributes(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.emptyElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:76) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadDocument(XmlBeanDefinitionReader.java:429) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:391) My opinion is that "from" element should allow to
[jira] [Resolved] (CAMEL-11506) MavenVersionManager blocks on unavailable URL
[ https://issues.apache.org/jira/browse/CAMEL-11506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-11506. - Resolution: Fixed > MavenVersionManager blocks on unavailable URL > - > > Key: CAMEL-11506 > URL: https://issues.apache.org/jira/browse/CAMEL-11506 > Project: Camel > Issue Type: Improvement > Components: tooling >Affects Versions: 2.19.0 >Reporter: Lars Heinemann >Assignee: Claus Ibsen > Fix For: 2.19.2, 2.20.0 > > > If I try to load the catalog of a not existing Camel version using the > MavenVersionManager then the call to load does not return. > Below is the appropriate stack of the thread which is never returning. > {noformat} > "main" #1 prio=6 os_prio=0 tid=0x7f6ea800b000 nid=0x12da runnable > [0x7f6eb2013000] >java.lang.Thread.State: RUNNABLE > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:171) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.read(InputRecord.java:503) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983) > - locked <0x0007b0be7870> (a java.lang.Object) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:940) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > - locked <0x0007b0be8668> (a sun.security.ssl.AppInputStream) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > - locked <0x000773a4de60> (a java.io.BufferedInputStream) > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:735) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:678) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1569) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) > at > sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338) > at > org.apache.ivy.util.url.BasicURLHandler.checkStatusCode(BasicURLHandler.java:131) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:73) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:54) > at > org.apache.ivy.plugins.repository.url.URLResource.init(URLResource.java:68) > at > org.apache.ivy.plugins.repository.url.URLResource.exists(URLResource.java:84) > at > org.apache.ivy.plugins.resolver.RepositoryResolver.findResourceUsingPattern(RepositoryResolver.java:97) > at > org.apache.ivy.plugins.resolver.AbstractPatternsBasedResolver.findResourceUsingPatterns(AbstractPatternsBasedResolver.java:97) > at > org.apache.ivy.plugins.resolver.IBiblioResolver.findArtifactRef(IBiblioResolver.java:125) > at > org.apache.ivy.plugins.resolver.BasicResolver.getArtifactRef(BasicResolver.java:1034) > at > org.apache.ivy.plugins.resolver.BasicResolver.findFirstArtifactRef(BasicResolver.java:971) > at > org.apache.ivy.plugins.resolver.BasicResolver.getDependency(BasicResolver.java:243) > at > org.apache.ivy.plugins.resolver.IBiblioResolver.getDependency(IBiblioResolver.java:506) > at > org.apache.ivy.plugins.resolver.ChainResolver.getDependency(ChainResolver.java:104) > at org.apache.ivy.core.resolve.IvyNode.loadData(IvyNode.java:170) > at org.apache.ivy.core.resolve.VisitNode.loadData(VisitNode.java:292) > at > org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:718) > at > org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:803) > at > org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:726) > at > org.apache.ivy.core.resolve.ResolveEngine.getDependencies(ResolveEngine.java:599) > at > org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:236) > at org.apache.ivy.Ivy.resolve(Ivy.java:523) > at org.apache.ivy.Ivy$resolve$0.call(Unknown Source) > at groovy.grape.GrapeIvy.getDependencies(GrapeIvy.groovy:410) > at
[jira] [Comment Edited] (CAMEL-11506) MavenVersionManager blocks on unavailable URL
[ https://issues.apache.org/jira/browse/CAMEL-11506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073347#comment-16073347 ] Claus Ibsen edited comment on CAMEL-11506 at 7/4/17 8:53 AM: - Okay pushed some code fixes to master and 2.19.x branch that uses http client 3.1 with a default timeout of 1 millis. You can configure the timeout value on the MavenVersionManager with the setter was (Author: davsclaus): Okay pushed some code fixes to master and 2.19.x branch that uses http client 3.1 with a default timeout of 1 millis. > MavenVersionManager blocks on unavailable URL > - > > Key: CAMEL-11506 > URL: https://issues.apache.org/jira/browse/CAMEL-11506 > Project: Camel > Issue Type: Improvement > Components: tooling >Affects Versions: 2.19.0 >Reporter: Lars Heinemann >Assignee: Claus Ibsen > Fix For: 2.19.2, 2.20.0 > > > If I try to load the catalog of a not existing Camel version using the > MavenVersionManager then the call to load does not return. > Below is the appropriate stack of the thread which is never returning. > {noformat} > "main" #1 prio=6 os_prio=0 tid=0x7f6ea800b000 nid=0x12da runnable > [0x7f6eb2013000] >java.lang.Thread.State: RUNNABLE > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:171) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.read(InputRecord.java:503) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983) > - locked <0x0007b0be7870> (a java.lang.Object) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:940) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > - locked <0x0007b0be8668> (a sun.security.ssl.AppInputStream) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > - locked <0x000773a4de60> (a java.io.BufferedInputStream) > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:735) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:678) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1569) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) > at > sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338) > at > org.apache.ivy.util.url.BasicURLHandler.checkStatusCode(BasicURLHandler.java:131) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:73) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:54) > at > org.apache.ivy.plugins.repository.url.URLResource.init(URLResource.java:68) > at > org.apache.ivy.plugins.repository.url.URLResource.exists(URLResource.java:84) > at > org.apache.ivy.plugins.resolver.RepositoryResolver.findResourceUsingPattern(RepositoryResolver.java:97) > at > org.apache.ivy.plugins.resolver.AbstractPatternsBasedResolver.findResourceUsingPatterns(AbstractPatternsBasedResolver.java:97) > at > org.apache.ivy.plugins.resolver.IBiblioResolver.findArtifactRef(IBiblioResolver.java:125) > at > org.apache.ivy.plugins.resolver.BasicResolver.getArtifactRef(BasicResolver.java:1034) > at > org.apache.ivy.plugins.resolver.BasicResolver.findFirstArtifactRef(BasicResolver.java:971) > at > org.apache.ivy.plugins.resolver.BasicResolver.getDependency(BasicResolver.java:243) > at > org.apache.ivy.plugins.resolver.IBiblioResolver.getDependency(IBiblioResolver.java:506) > at > org.apache.ivy.plugins.resolver.ChainResolver.getDependency(ChainResolver.java:104) > at org.apache.ivy.core.resolve.IvyNode.loadData(IvyNode.java:170) > at org.apache.ivy.core.resolve.VisitNode.loadData(VisitNode.java:292) > at > org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:718) > at > org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:803) > at >
[jira] [Commented] (CAMEL-11506) MavenVersionManager blocks on unavailable URL
[ https://issues.apache.org/jira/browse/CAMEL-11506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073347#comment-16073347 ] Claus Ibsen commented on CAMEL-11506: - Okay pushed some code fixes to master and 2.19.x branch that uses http client 3.1 with a default timeout of 1 millis. > MavenVersionManager blocks on unavailable URL > - > > Key: CAMEL-11506 > URL: https://issues.apache.org/jira/browse/CAMEL-11506 > Project: Camel > Issue Type: Improvement > Components: tooling >Affects Versions: 2.19.0 >Reporter: Lars Heinemann >Assignee: Claus Ibsen > Fix For: 2.19.2, 2.20.0 > > > If I try to load the catalog of a not existing Camel version using the > MavenVersionManager then the call to load does not return. > Below is the appropriate stack of the thread which is never returning. > {noformat} > "main" #1 prio=6 os_prio=0 tid=0x7f6ea800b000 nid=0x12da runnable > [0x7f6eb2013000] >java.lang.Thread.State: RUNNABLE > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:171) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.read(InputRecord.java:503) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983) > - locked <0x0007b0be7870> (a java.lang.Object) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:940) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > - locked <0x0007b0be8668> (a sun.security.ssl.AppInputStream) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > - locked <0x000773a4de60> (a java.io.BufferedInputStream) > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:735) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:678) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1569) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) > at > sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338) > at > org.apache.ivy.util.url.BasicURLHandler.checkStatusCode(BasicURLHandler.java:131) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:73) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:54) > at > org.apache.ivy.plugins.repository.url.URLResource.init(URLResource.java:68) > at > org.apache.ivy.plugins.repository.url.URLResource.exists(URLResource.java:84) > at > org.apache.ivy.plugins.resolver.RepositoryResolver.findResourceUsingPattern(RepositoryResolver.java:97) > at > org.apache.ivy.plugins.resolver.AbstractPatternsBasedResolver.findResourceUsingPatterns(AbstractPatternsBasedResolver.java:97) > at > org.apache.ivy.plugins.resolver.IBiblioResolver.findArtifactRef(IBiblioResolver.java:125) > at > org.apache.ivy.plugins.resolver.BasicResolver.getArtifactRef(BasicResolver.java:1034) > at > org.apache.ivy.plugins.resolver.BasicResolver.findFirstArtifactRef(BasicResolver.java:971) > at > org.apache.ivy.plugins.resolver.BasicResolver.getDependency(BasicResolver.java:243) > at > org.apache.ivy.plugins.resolver.IBiblioResolver.getDependency(IBiblioResolver.java:506) > at > org.apache.ivy.plugins.resolver.ChainResolver.getDependency(ChainResolver.java:104) > at org.apache.ivy.core.resolve.IvyNode.loadData(IvyNode.java:170) > at org.apache.ivy.core.resolve.VisitNode.loadData(VisitNode.java:292) > at > org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:718) > at > org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:803) > at > org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:726) > at > org.apache.ivy.core.resolve.ResolveEngine.getDependencies(ResolveEngine.java:599) > at > org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:236) > at org.apache.ivy.Ivy.resolve(Ivy.java:523) >
[jira] [Assigned] (CAMEL-11506) MavenVersionManager blocks on unavailable URL
[ https://issues.apache.org/jira/browse/CAMEL-11506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-11506: --- Assignee: Claus Ibsen > MavenVersionManager blocks on unavailable URL > - > > Key: CAMEL-11506 > URL: https://issues.apache.org/jira/browse/CAMEL-11506 > Project: Camel > Issue Type: Improvement > Components: tooling >Affects Versions: 2.19.0 >Reporter: Lars Heinemann >Assignee: Claus Ibsen > Fix For: 2.19.2, 2.20.0 > > > If I try to load the catalog of a not existing Camel version using the > MavenVersionManager then the call to load does not return. > Below is the appropriate stack of the thread which is never returning. > {noformat} > "main" #1 prio=6 os_prio=0 tid=0x7f6ea800b000 nid=0x12da runnable > [0x7f6eb2013000] >java.lang.Thread.State: RUNNABLE > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:171) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.read(InputRecord.java:503) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983) > - locked <0x0007b0be7870> (a java.lang.Object) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:940) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > - locked <0x0007b0be8668> (a sun.security.ssl.AppInputStream) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > - locked <0x000773a4de60> (a java.io.BufferedInputStream) > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:735) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:678) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1569) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) > at > sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338) > at > org.apache.ivy.util.url.BasicURLHandler.checkStatusCode(BasicURLHandler.java:131) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:73) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:54) > at > org.apache.ivy.plugins.repository.url.URLResource.init(URLResource.java:68) > at > org.apache.ivy.plugins.repository.url.URLResource.exists(URLResource.java:84) > at > org.apache.ivy.plugins.resolver.RepositoryResolver.findResourceUsingPattern(RepositoryResolver.java:97) > at > org.apache.ivy.plugins.resolver.AbstractPatternsBasedResolver.findResourceUsingPatterns(AbstractPatternsBasedResolver.java:97) > at > org.apache.ivy.plugins.resolver.IBiblioResolver.findArtifactRef(IBiblioResolver.java:125) > at > org.apache.ivy.plugins.resolver.BasicResolver.getArtifactRef(BasicResolver.java:1034) > at > org.apache.ivy.plugins.resolver.BasicResolver.findFirstArtifactRef(BasicResolver.java:971) > at > org.apache.ivy.plugins.resolver.BasicResolver.getDependency(BasicResolver.java:243) > at > org.apache.ivy.plugins.resolver.IBiblioResolver.getDependency(IBiblioResolver.java:506) > at > org.apache.ivy.plugins.resolver.ChainResolver.getDependency(ChainResolver.java:104) > at org.apache.ivy.core.resolve.IvyNode.loadData(IvyNode.java:170) > at org.apache.ivy.core.resolve.VisitNode.loadData(VisitNode.java:292) > at > org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:718) > at > org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:803) > at > org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:726) > at > org.apache.ivy.core.resolve.ResolveEngine.getDependencies(ResolveEngine.java:599) > at > org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:236) > at org.apache.ivy.Ivy.resolve(Ivy.java:523) > at org.apache.ivy.Ivy$resolve$0.call(Unknown Source) > at groovy.grape.GrapeIvy.getDependencies(GrapeIvy.groovy:410) >
[jira] [Updated] (CAMEL-11506) MavenVersionManager blocks on unavailable URL
[ https://issues.apache.org/jira/browse/CAMEL-11506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-11506: Fix Version/s: 2.20.0 2.19.2 > MavenVersionManager blocks on unavailable URL > - > > Key: CAMEL-11506 > URL: https://issues.apache.org/jira/browse/CAMEL-11506 > Project: Camel > Issue Type: Improvement > Components: tooling >Affects Versions: 2.19.0 >Reporter: Lars Heinemann >Assignee: Claus Ibsen > Fix For: 2.19.2, 2.20.0 > > > If I try to load the catalog of a not existing Camel version using the > MavenVersionManager then the call to load does not return. > Below is the appropriate stack of the thread which is never returning. > {noformat} > "main" #1 prio=6 os_prio=0 tid=0x7f6ea800b000 nid=0x12da runnable > [0x7f6eb2013000] >java.lang.Thread.State: RUNNABLE > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:171) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.read(InputRecord.java:503) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983) > - locked <0x0007b0be7870> (a java.lang.Object) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:940) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > - locked <0x0007b0be8668> (a sun.security.ssl.AppInputStream) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > - locked <0x000773a4de60> (a java.io.BufferedInputStream) > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:735) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:678) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1569) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) > at > sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338) > at > org.apache.ivy.util.url.BasicURLHandler.checkStatusCode(BasicURLHandler.java:131) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:73) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:54) > at > org.apache.ivy.plugins.repository.url.URLResource.init(URLResource.java:68) > at > org.apache.ivy.plugins.repository.url.URLResource.exists(URLResource.java:84) > at > org.apache.ivy.plugins.resolver.RepositoryResolver.findResourceUsingPattern(RepositoryResolver.java:97) > at > org.apache.ivy.plugins.resolver.AbstractPatternsBasedResolver.findResourceUsingPatterns(AbstractPatternsBasedResolver.java:97) > at > org.apache.ivy.plugins.resolver.IBiblioResolver.findArtifactRef(IBiblioResolver.java:125) > at > org.apache.ivy.plugins.resolver.BasicResolver.getArtifactRef(BasicResolver.java:1034) > at > org.apache.ivy.plugins.resolver.BasicResolver.findFirstArtifactRef(BasicResolver.java:971) > at > org.apache.ivy.plugins.resolver.BasicResolver.getDependency(BasicResolver.java:243) > at > org.apache.ivy.plugins.resolver.IBiblioResolver.getDependency(IBiblioResolver.java:506) > at > org.apache.ivy.plugins.resolver.ChainResolver.getDependency(ChainResolver.java:104) > at org.apache.ivy.core.resolve.IvyNode.loadData(IvyNode.java:170) > at org.apache.ivy.core.resolve.VisitNode.loadData(VisitNode.java:292) > at > org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:718) > at > org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:803) > at > org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:726) > at > org.apache.ivy.core.resolve.ResolveEngine.getDependencies(ResolveEngine.java:599) > at > org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:236) > at org.apache.ivy.Ivy.resolve(Ivy.java:523) > at org.apache.ivy.Ivy$resolve$0.call(Unknown Source) > at
[jira] [Commented] (CAMEL-11506) MavenVersionManager blocks on unavailable URL
[ https://issues.apache.org/jira/browse/CAMEL-11506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073320#comment-16073320 ] Claus Ibsen commented on CAMEL-11506: - Okay I am trying to make it use the http-client instead for http/https download which seems to have some kind of timeout support. > MavenVersionManager blocks on unavailable URL > - > > Key: CAMEL-11506 > URL: https://issues.apache.org/jira/browse/CAMEL-11506 > Project: Camel > Issue Type: Improvement > Components: tooling >Affects Versions: 2.19.0 >Reporter: Lars Heinemann > > If I try to load the catalog of a not existing Camel version using the > MavenVersionManager then the call to load does not return. > Below is the appropriate stack of the thread which is never returning. > {noformat} > "main" #1 prio=6 os_prio=0 tid=0x7f6ea800b000 nid=0x12da runnable > [0x7f6eb2013000] >java.lang.Thread.State: RUNNABLE > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:171) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.read(InputRecord.java:503) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983) > - locked <0x0007b0be7870> (a java.lang.Object) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:940) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > - locked <0x0007b0be8668> (a sun.security.ssl.AppInputStream) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > - locked <0x000773a4de60> (a java.io.BufferedInputStream) > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:735) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:678) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1569) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) > at > sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338) > at > org.apache.ivy.util.url.BasicURLHandler.checkStatusCode(BasicURLHandler.java:131) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:73) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:54) > at > org.apache.ivy.plugins.repository.url.URLResource.init(URLResource.java:68) > at > org.apache.ivy.plugins.repository.url.URLResource.exists(URLResource.java:84) > at > org.apache.ivy.plugins.resolver.RepositoryResolver.findResourceUsingPattern(RepositoryResolver.java:97) > at > org.apache.ivy.plugins.resolver.AbstractPatternsBasedResolver.findResourceUsingPatterns(AbstractPatternsBasedResolver.java:97) > at > org.apache.ivy.plugins.resolver.IBiblioResolver.findArtifactRef(IBiblioResolver.java:125) > at > org.apache.ivy.plugins.resolver.BasicResolver.getArtifactRef(BasicResolver.java:1034) > at > org.apache.ivy.plugins.resolver.BasicResolver.findFirstArtifactRef(BasicResolver.java:971) > at > org.apache.ivy.plugins.resolver.BasicResolver.getDependency(BasicResolver.java:243) > at > org.apache.ivy.plugins.resolver.IBiblioResolver.getDependency(IBiblioResolver.java:506) > at > org.apache.ivy.plugins.resolver.ChainResolver.getDependency(ChainResolver.java:104) > at org.apache.ivy.core.resolve.IvyNode.loadData(IvyNode.java:170) > at org.apache.ivy.core.resolve.VisitNode.loadData(VisitNode.java:292) > at > org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:718) > at > org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:803) > at > org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:726) > at > org.apache.ivy.core.resolve.ResolveEngine.getDependencies(ResolveEngine.java:599) > at > org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:236) > at org.apache.ivy.Ivy.resolve(Ivy.java:523) > at org.apache.ivy.Ivy$resolve$0.call(Unknown Source) >
[jira] [Commented] (CAMEL-11506) MavenVersionManager blocks on unavailable URL
[ https://issues.apache.org/jira/browse/CAMEL-11506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073274#comment-16073274 ] Claus Ibsen commented on CAMEL-11506: - Ah Apache Ivy allows to use the older http client 3.1 instead of the JDK, so we can try to add it to the classpath {code} /** * This method is used to get appropriate http downloader dependening on Jakarta Commons * HttpClient availability in classpath, or simply use jdk url handling in other cases. * * @return most accurate http downloader */ public static URLHandler getHttp() { try { Class.forName("org.apache.commons.httpclient.HttpClient"); // temporary fix for IVY-880: only use HttpClientHandler when // http-client-3.x is available Class.forName("org.apache.commons.httpclient.params.HttpClientParams"); Class handler = Class.forName("org.apache.ivy.util.url.HttpClientHandler"); Message.verbose("jakarta commons httpclient detected: using it for http downloading"); return (URLHandler) handler.newInstance(); } catch (ClassNotFoundException e) { Message.verbose("jakarta commons httpclient not found: using jdk url handling"); return new BasicURLHandler(); } catch (NoClassDefFoundError e) { Message.verbose("error occurred while loading jakarta commons httpclient: " + e.getMessage()); Message.verbose("Using jdk url handling instead."); return new BasicURLHandler(); } catch (InstantiationException e) { Message.verbose("couldn't instantiate HttpClientHandler: using jdk url handling"); return new BasicURLHandler(); } catch (IllegalAccessException e) { Message.verbose("couldn't instantiate HttpClientHandler: using jdk url handling"); return new BasicURLHandler(); } } {code} > MavenVersionManager blocks on unavailable URL > - > > Key: CAMEL-11506 > URL: https://issues.apache.org/jira/browse/CAMEL-11506 > Project: Camel > Issue Type: Improvement > Components: tooling >Affects Versions: 2.19.0 >Reporter: Lars Heinemann > > If I try to load the catalog of a not existing Camel version using the > MavenVersionManager then the call to load does not return. > Below is the appropriate stack of the thread which is never returning. > {noformat} > "main" #1 prio=6 os_prio=0 tid=0x7f6ea800b000 nid=0x12da runnable > [0x7f6eb2013000] >java.lang.Thread.State: RUNNABLE > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:171) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.read(InputRecord.java:503) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983) > - locked <0x0007b0be7870> (a java.lang.Object) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:940) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > - locked <0x0007b0be8668> (a sun.security.ssl.AppInputStream) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > - locked <0x000773a4de60> (a java.io.BufferedInputStream) > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:735) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:678) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1569) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) > at > sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338) > at > org.apache.ivy.util.url.BasicURLHandler.checkStatusCode(BasicURLHandler.java:131) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:73) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:54) > at > org.apache.ivy.plugins.repository.url.URLResource.init(URLResource.java:68) > at >
[jira] [Commented] (CAMEL-11506) MavenVersionManager blocks on unavailable URL
[ https://issues.apache.org/jira/browse/CAMEL-11506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073273#comment-16073273 ] Claus Ibsen commented on CAMEL-11506: - What JDK version do you use, maybe try to upgrade, as you end up using the HTTP client from the JDK (according to stacktrace) and it may be better in newer version. > MavenVersionManager blocks on unavailable URL > - > > Key: CAMEL-11506 > URL: https://issues.apache.org/jira/browse/CAMEL-11506 > Project: Camel > Issue Type: Improvement > Components: tooling >Affects Versions: 2.19.0 >Reporter: Lars Heinemann > > If I try to load the catalog of a not existing Camel version using the > MavenVersionManager then the call to load does not return. > Below is the appropriate stack of the thread which is never returning. > {noformat} > "main" #1 prio=6 os_prio=0 tid=0x7f6ea800b000 nid=0x12da runnable > [0x7f6eb2013000] >java.lang.Thread.State: RUNNABLE > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:171) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.read(InputRecord.java:503) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983) > - locked <0x0007b0be7870> (a java.lang.Object) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:940) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > - locked <0x0007b0be8668> (a sun.security.ssl.AppInputStream) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > - locked <0x000773a4de60> (a java.io.BufferedInputStream) > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:735) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:678) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1569) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) > at > sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338) > at > org.apache.ivy.util.url.BasicURLHandler.checkStatusCode(BasicURLHandler.java:131) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:73) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:54) > at > org.apache.ivy.plugins.repository.url.URLResource.init(URLResource.java:68) > at > org.apache.ivy.plugins.repository.url.URLResource.exists(URLResource.java:84) > at > org.apache.ivy.plugins.resolver.RepositoryResolver.findResourceUsingPattern(RepositoryResolver.java:97) > at > org.apache.ivy.plugins.resolver.AbstractPatternsBasedResolver.findResourceUsingPatterns(AbstractPatternsBasedResolver.java:97) > at > org.apache.ivy.plugins.resolver.IBiblioResolver.findArtifactRef(IBiblioResolver.java:125) > at > org.apache.ivy.plugins.resolver.BasicResolver.getArtifactRef(BasicResolver.java:1034) > at > org.apache.ivy.plugins.resolver.BasicResolver.findFirstArtifactRef(BasicResolver.java:971) > at > org.apache.ivy.plugins.resolver.BasicResolver.getDependency(BasicResolver.java:243) > at > org.apache.ivy.plugins.resolver.IBiblioResolver.getDependency(IBiblioResolver.java:506) > at > org.apache.ivy.plugins.resolver.ChainResolver.getDependency(ChainResolver.java:104) > at org.apache.ivy.core.resolve.IvyNode.loadData(IvyNode.java:170) > at org.apache.ivy.core.resolve.VisitNode.loadData(VisitNode.java:292) > at > org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:718) > at > org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:803) > at > org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:726) > at > org.apache.ivy.core.resolve.ResolveEngine.getDependencies(ResolveEngine.java:599) > at > org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:236) > at org.apache.ivy.Ivy.resolve(Ivy.java:523) > at
[jira] [Commented] (CAMEL-11506) MavenVersionManager blocks on unavailable URL
[ https://issues.apache.org/jira/browse/CAMEL-11506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073259#comment-16073259 ] Lars Heinemann commented on CAMEL-11506: I already tried starting the CI job with params {noformat} -Dsun.net.client.defaultConnectTimeout=3 -Dsun.net.client.defaultReadTimeout=3 {noformat} but that seemed to have no effect. > MavenVersionManager blocks on unavailable URL > - > > Key: CAMEL-11506 > URL: https://issues.apache.org/jira/browse/CAMEL-11506 > Project: Camel > Issue Type: Improvement > Components: tooling >Affects Versions: 2.19.0 >Reporter: Lars Heinemann > > If I try to load the catalog of a not existing Camel version using the > MavenVersionManager then the call to load does not return. > Below is the appropriate stack of the thread which is never returning. > {noformat} > "main" #1 prio=6 os_prio=0 tid=0x7f6ea800b000 nid=0x12da runnable > [0x7f6eb2013000] >java.lang.Thread.State: RUNNABLE > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:171) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.read(InputRecord.java:503) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983) > - locked <0x0007b0be7870> (a java.lang.Object) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:940) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > - locked <0x0007b0be8668> (a sun.security.ssl.AppInputStream) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > - locked <0x000773a4de60> (a java.io.BufferedInputStream) > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:735) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:678) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1569) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) > at > sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338) > at > org.apache.ivy.util.url.BasicURLHandler.checkStatusCode(BasicURLHandler.java:131) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:73) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:54) > at > org.apache.ivy.plugins.repository.url.URLResource.init(URLResource.java:68) > at > org.apache.ivy.plugins.repository.url.URLResource.exists(URLResource.java:84) > at > org.apache.ivy.plugins.resolver.RepositoryResolver.findResourceUsingPattern(RepositoryResolver.java:97) > at > org.apache.ivy.plugins.resolver.AbstractPatternsBasedResolver.findResourceUsingPatterns(AbstractPatternsBasedResolver.java:97) > at > org.apache.ivy.plugins.resolver.IBiblioResolver.findArtifactRef(IBiblioResolver.java:125) > at > org.apache.ivy.plugins.resolver.BasicResolver.getArtifactRef(BasicResolver.java:1034) > at > org.apache.ivy.plugins.resolver.BasicResolver.findFirstArtifactRef(BasicResolver.java:971) > at > org.apache.ivy.plugins.resolver.BasicResolver.getDependency(BasicResolver.java:243) > at > org.apache.ivy.plugins.resolver.IBiblioResolver.getDependency(IBiblioResolver.java:506) > at > org.apache.ivy.plugins.resolver.ChainResolver.getDependency(ChainResolver.java:104) > at org.apache.ivy.core.resolve.IvyNode.loadData(IvyNode.java:170) > at org.apache.ivy.core.resolve.VisitNode.loadData(VisitNode.java:292) > at > org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:718) > at > org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:803) > at > org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:726) > at > org.apache.ivy.core.resolve.ResolveEngine.getDependencies(ResolveEngine.java:599) > at > org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:236) > at org.apache.ivy.Ivy.resolve(Ivy.java:523)
[jira] [Commented] (CAMEL-11506) MavenVersionManager blocks on unavailable URL
[ https://issues.apache.org/jira/browse/CAMEL-11506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073254#comment-16073254 ] Zoran Regvart commented on CAMEL-11506: --- [~lhein] Can setting {{sun.net.client.defaultConnectTimeout}} (a Java system property) help in your case? See [Java networking properties|https://docs.oracle.com/javase/8/docs/technotes/guides/net/properties.html]. Do note that you can set it only once and on startup (see [JDK-6245589|https://bugs.openjdk.java.net/browse/JDK-6245589]). Might work as a temporary workaround. > MavenVersionManager blocks on unavailable URL > - > > Key: CAMEL-11506 > URL: https://issues.apache.org/jira/browse/CAMEL-11506 > Project: Camel > Issue Type: Improvement > Components: tooling >Affects Versions: 2.19.0 >Reporter: Lars Heinemann > > If I try to load the catalog of a not existing Camel version using the > MavenVersionManager then the call to load does not return. > Below is the appropriate stack of the thread which is never returning. > {noformat} > "main" #1 prio=6 os_prio=0 tid=0x7f6ea800b000 nid=0x12da runnable > [0x7f6eb2013000] >java.lang.Thread.State: RUNNABLE > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:171) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.read(InputRecord.java:503) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983) > - locked <0x0007b0be7870> (a java.lang.Object) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:940) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > - locked <0x0007b0be8668> (a sun.security.ssl.AppInputStream) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > - locked <0x000773a4de60> (a java.io.BufferedInputStream) > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:735) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:678) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1569) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) > at > sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338) > at > org.apache.ivy.util.url.BasicURLHandler.checkStatusCode(BasicURLHandler.java:131) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:73) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:54) > at > org.apache.ivy.plugins.repository.url.URLResource.init(URLResource.java:68) > at > org.apache.ivy.plugins.repository.url.URLResource.exists(URLResource.java:84) > at > org.apache.ivy.plugins.resolver.RepositoryResolver.findResourceUsingPattern(RepositoryResolver.java:97) > at > org.apache.ivy.plugins.resolver.AbstractPatternsBasedResolver.findResourceUsingPatterns(AbstractPatternsBasedResolver.java:97) > at > org.apache.ivy.plugins.resolver.IBiblioResolver.findArtifactRef(IBiblioResolver.java:125) > at > org.apache.ivy.plugins.resolver.BasicResolver.getArtifactRef(BasicResolver.java:1034) > at > org.apache.ivy.plugins.resolver.BasicResolver.findFirstArtifactRef(BasicResolver.java:971) > at > org.apache.ivy.plugins.resolver.BasicResolver.getDependency(BasicResolver.java:243) > at > org.apache.ivy.plugins.resolver.IBiblioResolver.getDependency(IBiblioResolver.java:506) > at > org.apache.ivy.plugins.resolver.ChainResolver.getDependency(ChainResolver.java:104) > at org.apache.ivy.core.resolve.IvyNode.loadData(IvyNode.java:170) > at org.apache.ivy.core.resolve.VisitNode.loadData(VisitNode.java:292) > at > org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:718) > at > org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:803) > at > org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:726) > at >
[jira] [Updated] (CAMEL-11506) MavenVersionManager blocks on unavailable URL
[ https://issues.apache.org/jira/browse/CAMEL-11506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Heinemann updated CAMEL-11506: --- Affects Version/s: (was: 2.19.1) 2.19.0 > MavenVersionManager blocks on unavailable URL > - > > Key: CAMEL-11506 > URL: https://issues.apache.org/jira/browse/CAMEL-11506 > Project: Camel > Issue Type: Improvement > Components: tooling >Affects Versions: 2.19.0 >Reporter: Lars Heinemann > > If I try to load the catalog of a not existing Camel version using the > MavenVersionManager then the call to load does not return. > Below is the appropriate stack of the thread which is never returning. > {noformat} > "main" #1 prio=6 os_prio=0 tid=0x7f6ea800b000 nid=0x12da runnable > [0x7f6eb2013000] >java.lang.Thread.State: RUNNABLE > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:171) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.read(InputRecord.java:503) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983) > - locked <0x0007b0be7870> (a java.lang.Object) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:940) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > - locked <0x0007b0be8668> (a sun.security.ssl.AppInputStream) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > - locked <0x000773a4de60> (a java.io.BufferedInputStream) > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:735) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:678) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1569) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) > at > sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338) > at > org.apache.ivy.util.url.BasicURLHandler.checkStatusCode(BasicURLHandler.java:131) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:73) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:54) > at > org.apache.ivy.plugins.repository.url.URLResource.init(URLResource.java:68) > at > org.apache.ivy.plugins.repository.url.URLResource.exists(URLResource.java:84) > at > org.apache.ivy.plugins.resolver.RepositoryResolver.findResourceUsingPattern(RepositoryResolver.java:97) > at > org.apache.ivy.plugins.resolver.AbstractPatternsBasedResolver.findResourceUsingPatterns(AbstractPatternsBasedResolver.java:97) > at > org.apache.ivy.plugins.resolver.IBiblioResolver.findArtifactRef(IBiblioResolver.java:125) > at > org.apache.ivy.plugins.resolver.BasicResolver.getArtifactRef(BasicResolver.java:1034) > at > org.apache.ivy.plugins.resolver.BasicResolver.findFirstArtifactRef(BasicResolver.java:971) > at > org.apache.ivy.plugins.resolver.BasicResolver.getDependency(BasicResolver.java:243) > at > org.apache.ivy.plugins.resolver.IBiblioResolver.getDependency(IBiblioResolver.java:506) > at > org.apache.ivy.plugins.resolver.ChainResolver.getDependency(ChainResolver.java:104) > at org.apache.ivy.core.resolve.IvyNode.loadData(IvyNode.java:170) > at org.apache.ivy.core.resolve.VisitNode.loadData(VisitNode.java:292) > at > org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:718) > at > org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:803) > at > org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:726) > at > org.apache.ivy.core.resolve.ResolveEngine.getDependencies(ResolveEngine.java:599) > at > org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:236) > at org.apache.ivy.Ivy.resolve(Ivy.java:523) > at org.apache.ivy.Ivy$resolve$0.call(Unknown Source) > at groovy.grape.GrapeIvy.getDependencies(GrapeIvy.groovy:410) > at
[jira] [Commented] (CAMEL-11506) MavenVersionManager blocks on unavailable URL
[ https://issues.apache.org/jira/browse/CAMEL-11506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073236#comment-16073236 ] Lars Heinemann commented on CAMEL-11506: corrected the affected version to 2.19.0 which is the one I used. > MavenVersionManager blocks on unavailable URL > - > > Key: CAMEL-11506 > URL: https://issues.apache.org/jira/browse/CAMEL-11506 > Project: Camel > Issue Type: Improvement > Components: tooling >Affects Versions: 2.19.0 >Reporter: Lars Heinemann > > If I try to load the catalog of a not existing Camel version using the > MavenVersionManager then the call to load does not return. > Below is the appropriate stack of the thread which is never returning. > {noformat} > "main" #1 prio=6 os_prio=0 tid=0x7f6ea800b000 nid=0x12da runnable > [0x7f6eb2013000] >java.lang.Thread.State: RUNNABLE > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:171) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.read(InputRecord.java:503) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983) > - locked <0x0007b0be7870> (a java.lang.Object) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:940) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > - locked <0x0007b0be8668> (a sun.security.ssl.AppInputStream) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > - locked <0x000773a4de60> (a java.io.BufferedInputStream) > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:735) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:678) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1569) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) > at > sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338) > at > org.apache.ivy.util.url.BasicURLHandler.checkStatusCode(BasicURLHandler.java:131) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:73) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:54) > at > org.apache.ivy.plugins.repository.url.URLResource.init(URLResource.java:68) > at > org.apache.ivy.plugins.repository.url.URLResource.exists(URLResource.java:84) > at > org.apache.ivy.plugins.resolver.RepositoryResolver.findResourceUsingPattern(RepositoryResolver.java:97) > at > org.apache.ivy.plugins.resolver.AbstractPatternsBasedResolver.findResourceUsingPatterns(AbstractPatternsBasedResolver.java:97) > at > org.apache.ivy.plugins.resolver.IBiblioResolver.findArtifactRef(IBiblioResolver.java:125) > at > org.apache.ivy.plugins.resolver.BasicResolver.getArtifactRef(BasicResolver.java:1034) > at > org.apache.ivy.plugins.resolver.BasicResolver.findFirstArtifactRef(BasicResolver.java:971) > at > org.apache.ivy.plugins.resolver.BasicResolver.getDependency(BasicResolver.java:243) > at > org.apache.ivy.plugins.resolver.IBiblioResolver.getDependency(IBiblioResolver.java:506) > at > org.apache.ivy.plugins.resolver.ChainResolver.getDependency(ChainResolver.java:104) > at org.apache.ivy.core.resolve.IvyNode.loadData(IvyNode.java:170) > at org.apache.ivy.core.resolve.VisitNode.loadData(VisitNode.java:292) > at > org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:718) > at > org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:803) > at > org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:726) > at > org.apache.ivy.core.resolve.ResolveEngine.getDependencies(ResolveEngine.java:599) > at > org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:236) > at org.apache.ivy.Ivy.resolve(Ivy.java:523) > at org.apache.ivy.Ivy$resolve$0.call(Unknown Source) > at
[jira] [Commented] (CAMEL-11506) MavenVersionManager blocks on unavailable URL
[ https://issues.apache.org/jira/browse/CAMEL-11506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073234#comment-16073234 ] Claus Ibsen commented on CAMEL-11506: - Its Apache Ivy that would need to support timeout which it does not https://issues.apache.org/jira/browse/IVY-735 > MavenVersionManager blocks on unavailable URL > - > > Key: CAMEL-11506 > URL: https://issues.apache.org/jira/browse/CAMEL-11506 > Project: Camel > Issue Type: Improvement > Components: tooling >Affects Versions: 2.19.1 >Reporter: Lars Heinemann > > If I try to load the catalog of a not existing Camel version using the > MavenVersionManager then the call to load does not return. > Below is the appropriate stack of the thread which is never returning. > {noformat} > "main" #1 prio=6 os_prio=0 tid=0x7f6ea800b000 nid=0x12da runnable > [0x7f6eb2013000] >java.lang.Thread.State: RUNNABLE > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:171) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.read(InputRecord.java:503) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983) > - locked <0x0007b0be7870> (a java.lang.Object) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:940) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > - locked <0x0007b0be8668> (a sun.security.ssl.AppInputStream) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > - locked <0x000773a4de60> (a java.io.BufferedInputStream) > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:735) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:678) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1569) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) > at > sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338) > at > org.apache.ivy.util.url.BasicURLHandler.checkStatusCode(BasicURLHandler.java:131) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:73) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:54) > at > org.apache.ivy.plugins.repository.url.URLResource.init(URLResource.java:68) > at > org.apache.ivy.plugins.repository.url.URLResource.exists(URLResource.java:84) > at > org.apache.ivy.plugins.resolver.RepositoryResolver.findResourceUsingPattern(RepositoryResolver.java:97) > at > org.apache.ivy.plugins.resolver.AbstractPatternsBasedResolver.findResourceUsingPatterns(AbstractPatternsBasedResolver.java:97) > at > org.apache.ivy.plugins.resolver.IBiblioResolver.findArtifactRef(IBiblioResolver.java:125) > at > org.apache.ivy.plugins.resolver.BasicResolver.getArtifactRef(BasicResolver.java:1034) > at > org.apache.ivy.plugins.resolver.BasicResolver.findFirstArtifactRef(BasicResolver.java:971) > at > org.apache.ivy.plugins.resolver.BasicResolver.getDependency(BasicResolver.java:243) > at > org.apache.ivy.plugins.resolver.IBiblioResolver.getDependency(IBiblioResolver.java:506) > at > org.apache.ivy.plugins.resolver.ChainResolver.getDependency(ChainResolver.java:104) > at org.apache.ivy.core.resolve.IvyNode.loadData(IvyNode.java:170) > at org.apache.ivy.core.resolve.VisitNode.loadData(VisitNode.java:292) > at > org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:718) > at > org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:803) > at > org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:726) > at > org.apache.ivy.core.resolve.ResolveEngine.getDependencies(ResolveEngine.java:599) > at > org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:236) > at org.apache.ivy.Ivy.resolve(Ivy.java:523) > at org.apache.ivy.Ivy$resolve$0.call(Unknown Source) > at
[jira] [Commented] (CAMEL-11487) Support resources load through custom defined protocols by registering custom UrlHandlers
[ https://issues.apache.org/jira/browse/CAMEL-11487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073232#comment-16073232 ] ASF GitHub Bot commented on CAMEL-11487: Github user valdar closed the pull request at: https://github.com/apache/camel/pull/1799 > Support resources load through custom defined protocols by registering custom > UrlHandlers > - > > Key: CAMEL-11487 > URL: https://issues.apache.org/jira/browse/CAMEL-11487 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Andrea Tarocchi >Assignee: Claus Ibsen > Fix For: 2.20.0 > > > Modifing {{resolveResourceAsUrl}} and {{resolveResourceAsInputStream}} in > {{ResourceHelper}} class to support custom defined protocols. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11506) MavenVersionManager blocks on unavailable URL
[ https://issues.apache.org/jira/browse/CAMEL-11506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-11506: Priority: Major (was: Critical) > MavenVersionManager blocks on unavailable URL > - > > Key: CAMEL-11506 > URL: https://issues.apache.org/jira/browse/CAMEL-11506 > Project: Camel > Issue Type: Improvement > Components: tooling >Affects Versions: 2.19.1 >Reporter: Lars Heinemann > > If I try to load the catalog of a not existing Camel version using the > MavenVersionManager then the call to load does not return. > Below is the appropriate stack of the thread which is never returning. > {noformat} > "main" #1 prio=6 os_prio=0 tid=0x7f6ea800b000 nid=0x12da runnable > [0x7f6eb2013000] >java.lang.Thread.State: RUNNABLE > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:171) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.read(InputRecord.java:503) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983) > - locked <0x0007b0be7870> (a java.lang.Object) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:940) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > - locked <0x0007b0be8668> (a sun.security.ssl.AppInputStream) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > - locked <0x000773a4de60> (a java.io.BufferedInputStream) > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:735) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:678) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1569) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) > at > sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338) > at > org.apache.ivy.util.url.BasicURLHandler.checkStatusCode(BasicURLHandler.java:131) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:73) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:54) > at > org.apache.ivy.plugins.repository.url.URLResource.init(URLResource.java:68) > at > org.apache.ivy.plugins.repository.url.URLResource.exists(URLResource.java:84) > at > org.apache.ivy.plugins.resolver.RepositoryResolver.findResourceUsingPattern(RepositoryResolver.java:97) > at > org.apache.ivy.plugins.resolver.AbstractPatternsBasedResolver.findResourceUsingPatterns(AbstractPatternsBasedResolver.java:97) > at > org.apache.ivy.plugins.resolver.IBiblioResolver.findArtifactRef(IBiblioResolver.java:125) > at > org.apache.ivy.plugins.resolver.BasicResolver.getArtifactRef(BasicResolver.java:1034) > at > org.apache.ivy.plugins.resolver.BasicResolver.findFirstArtifactRef(BasicResolver.java:971) > at > org.apache.ivy.plugins.resolver.BasicResolver.getDependency(BasicResolver.java:243) > at > org.apache.ivy.plugins.resolver.IBiblioResolver.getDependency(IBiblioResolver.java:506) > at > org.apache.ivy.plugins.resolver.ChainResolver.getDependency(ChainResolver.java:104) > at org.apache.ivy.core.resolve.IvyNode.loadData(IvyNode.java:170) > at org.apache.ivy.core.resolve.VisitNode.loadData(VisitNode.java:292) > at > org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:718) > at > org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:803) > at > org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:726) > at > org.apache.ivy.core.resolve.ResolveEngine.getDependencies(ResolveEngine.java:599) > at > org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:236) > at org.apache.ivy.Ivy.resolve(Ivy.java:523) > at org.apache.ivy.Ivy$resolve$0.call(Unknown Source) > at groovy.grape.GrapeIvy.getDependencies(GrapeIvy.groovy:410) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >
[jira] [Updated] (CAMEL-11506) MavenVersionManager blocks on unavailable URL
[ https://issues.apache.org/jira/browse/CAMEL-11506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-11506: Issue Type: Improvement (was: Bug) > MavenVersionManager blocks on unavailable URL > - > > Key: CAMEL-11506 > URL: https://issues.apache.org/jira/browse/CAMEL-11506 > Project: Camel > Issue Type: Improvement > Components: tooling >Affects Versions: 2.19.1 >Reporter: Lars Heinemann >Priority: Critical > > If I try to load the catalog of a not existing Camel version using the > MavenVersionManager then the call to load does not return. > Below is the appropriate stack of the thread which is never returning. > {noformat} > "main" #1 prio=6 os_prio=0 tid=0x7f6ea800b000 nid=0x12da runnable > [0x7f6eb2013000] >java.lang.Thread.State: RUNNABLE > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:171) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.read(InputRecord.java:503) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983) > - locked <0x0007b0be7870> (a java.lang.Object) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:940) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > - locked <0x0007b0be8668> (a sun.security.ssl.AppInputStream) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > - locked <0x000773a4de60> (a java.io.BufferedInputStream) > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:735) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:678) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1569) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) > at > sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338) > at > org.apache.ivy.util.url.BasicURLHandler.checkStatusCode(BasicURLHandler.java:131) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:73) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:54) > at > org.apache.ivy.plugins.repository.url.URLResource.init(URLResource.java:68) > at > org.apache.ivy.plugins.repository.url.URLResource.exists(URLResource.java:84) > at > org.apache.ivy.plugins.resolver.RepositoryResolver.findResourceUsingPattern(RepositoryResolver.java:97) > at > org.apache.ivy.plugins.resolver.AbstractPatternsBasedResolver.findResourceUsingPatterns(AbstractPatternsBasedResolver.java:97) > at > org.apache.ivy.plugins.resolver.IBiblioResolver.findArtifactRef(IBiblioResolver.java:125) > at > org.apache.ivy.plugins.resolver.BasicResolver.getArtifactRef(BasicResolver.java:1034) > at > org.apache.ivy.plugins.resolver.BasicResolver.findFirstArtifactRef(BasicResolver.java:971) > at > org.apache.ivy.plugins.resolver.BasicResolver.getDependency(BasicResolver.java:243) > at > org.apache.ivy.plugins.resolver.IBiblioResolver.getDependency(IBiblioResolver.java:506) > at > org.apache.ivy.plugins.resolver.ChainResolver.getDependency(ChainResolver.java:104) > at org.apache.ivy.core.resolve.IvyNode.loadData(IvyNode.java:170) > at org.apache.ivy.core.resolve.VisitNode.loadData(VisitNode.java:292) > at > org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:718) > at > org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:803) > at > org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:726) > at > org.apache.ivy.core.resolve.ResolveEngine.getDependencies(ResolveEngine.java:599) > at > org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:236) > at org.apache.ivy.Ivy.resolve(Ivy.java:523) > at org.apache.ivy.Ivy$resolve$0.call(Unknown Source) > at groovy.grape.GrapeIvy.getDependencies(GrapeIvy.groovy:410) > at
[jira] [Commented] (CAMEL-11506) MavenVersionManager blocks on unavailable URL
[ https://issues.apache.org/jira/browse/CAMEL-11506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073227#comment-16073227 ] Claus Ibsen commented on CAMEL-11506: - Its maybe something on your end etc. as trying to load an unknown version here, just don't do that, and it exit after a short while. Also your stacktrace does not fit with Camel 2.19.1 as MavenVersionManager.java:91 is the follow code line {code} param.put("classLoader", classLoader); {code} > MavenVersionManager blocks on unavailable URL > - > > Key: CAMEL-11506 > URL: https://issues.apache.org/jira/browse/CAMEL-11506 > Project: Camel > Issue Type: Bug > Components: tooling >Affects Versions: 2.19.1 >Reporter: Lars Heinemann >Priority: Critical > > If I try to load the catalog of a not existing Camel version using the > MavenVersionManager then the call to load does not return. > Below is the appropriate stack of the thread which is never returning. > {noformat} > "main" #1 prio=6 os_prio=0 tid=0x7f6ea800b000 nid=0x12da runnable > [0x7f6eb2013000] >java.lang.Thread.State: RUNNABLE > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:171) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.read(InputRecord.java:503) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983) > - locked <0x0007b0be7870> (a java.lang.Object) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:940) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > - locked <0x0007b0be8668> (a sun.security.ssl.AppInputStream) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > - locked <0x000773a4de60> (a java.io.BufferedInputStream) > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:735) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:678) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1569) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474) > - locked <0x000773a4baa0> (a > sun.net.www.protocol.https.DelegateHttpsURLConnection) > at > java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) > at > sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338) > at > org.apache.ivy.util.url.BasicURLHandler.checkStatusCode(BasicURLHandler.java:131) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:73) > at > org.apache.ivy.util.url.BasicURLHandler.getURLInfo(BasicURLHandler.java:54) > at > org.apache.ivy.plugins.repository.url.URLResource.init(URLResource.java:68) > at > org.apache.ivy.plugins.repository.url.URLResource.exists(URLResource.java:84) > at > org.apache.ivy.plugins.resolver.RepositoryResolver.findResourceUsingPattern(RepositoryResolver.java:97) > at > org.apache.ivy.plugins.resolver.AbstractPatternsBasedResolver.findResourceUsingPatterns(AbstractPatternsBasedResolver.java:97) > at > org.apache.ivy.plugins.resolver.IBiblioResolver.findArtifactRef(IBiblioResolver.java:125) > at > org.apache.ivy.plugins.resolver.BasicResolver.getArtifactRef(BasicResolver.java:1034) > at > org.apache.ivy.plugins.resolver.BasicResolver.findFirstArtifactRef(BasicResolver.java:971) > at > org.apache.ivy.plugins.resolver.BasicResolver.getDependency(BasicResolver.java:243) > at > org.apache.ivy.plugins.resolver.IBiblioResolver.getDependency(IBiblioResolver.java:506) > at > org.apache.ivy.plugins.resolver.ChainResolver.getDependency(ChainResolver.java:104) > at org.apache.ivy.core.resolve.IvyNode.loadData(IvyNode.java:170) > at org.apache.ivy.core.resolve.VisitNode.loadData(VisitNode.java:292) > at > org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:718) > at > org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:803) > at > org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:726) > at > org.apache.ivy.core.resolve.ResolveEngine.getDependencies(ResolveEngine.java:599) >
[jira] [Resolved] (CAMEL-11487) Support resources load through custom defined protocols by registering custom UrlHandlers
[ https://issues.apache.org/jira/browse/CAMEL-11487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-11487. - Resolution: Fixed Assignee: Claus Ibsen Thanks for the PR > Support resources load through custom defined protocols by registering custom > UrlHandlers > - > > Key: CAMEL-11487 > URL: https://issues.apache.org/jira/browse/CAMEL-11487 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Andrea Tarocchi >Assignee: Claus Ibsen > Fix For: 2.20.0 > > > Modifing {{resolveResourceAsUrl}} and {{resolveResourceAsInputStream}} in > {{ResourceHelper}} class to support custom defined protocols. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (CAMEL-11507) camel-servicenow : add an header to indicate the answer data type
[ https://issues.apache.org/jira/browse/CAMEL-11507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli resolved CAMEL-11507. - Resolution: Fixed > camel-servicenow : add an header to indicate the answer data type > - > > Key: CAMEL-11507 > URL: https://issues.apache.org/jira/browse/CAMEL-11507 > Project: Camel > Issue Type: Improvement > Components: camel-servicenow >Reporter: Luca Burgazzoli >Assignee: Luca Burgazzoli >Priority: Minor > Fix For: 2.19.2, 2.20.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)