[GitHub] [camel-k-runtime] makandre commented on issue #513: Thread blocked calling knative REST

2020-10-20 Thread GitBox
makandre commented on issue #513: URL: https://github.com/apache/camel-k-runtime/issues/513#issuecomment-712781736 Right. This is an automated message from the Apache Git Service. To respond to the message, please log on to

[GitHub] [camel-k-runtime] makandre commented on issue #513: Thread blocked calling knative REST

2020-10-20 Thread GitBox
makandre commented on issue #513: URL: https://github.com/apache/camel-k-runtime/issues/513#issuecomment-712775942 Yes, I used the `vertxoption` method before camel-k 1.2 (when it wasn't using Quarkus). I just defined the method as suggested above in the same `RouteBuilder` as my route

[GitHub] [camel-k-runtime] makandre commented on issue #513: Thread blocked calling knative REST

2020-10-15 Thread GitBox
makandre commented on issue #513: URL: https://github.com/apache/camel-k-runtime/issues/513#issuecomment-709382069 Thank you, that worked. This is an automated message from the Apache Git Service. To respond to the message,

[GitHub] [camel-k-runtime] makandre commented on issue #513: Thread blocked calling knative REST

2020-10-15 Thread GitBox
makandre commented on issue #513: URL: https://github.com/apache/camel-k-runtime/issues/513#issuecomment-709370058 I might be setting this wrong I got: ``` Error configuring property: camel.component.quarkus.vertx.max-event-loop-execute-time because cannot find component with

[GitHub] [camel-k-runtime] makandre commented on issue #513: Thread blocked calling knative REST

2020-10-15 Thread GitBox
makandre commented on issue #513: URL: https://github.com/apache/camel-k-runtime/issues/513#issuecomment-709325223 I don't quite follow. The class where I've placed that `vertxOptions` method does extend `RouteBuilder`

[GitHub] [camel-k-runtime] makandre commented on issue #513: Thread blocked calling knative REST

2020-10-15 Thread GitBox
makandre commented on issue #513: URL: https://github.com/apache/camel-k-runtime/issues/513#issuecomment-709267983 Hi @lburgazzoli, I just updated to camel-k 1.2, and the above workaround you gave me stopped working; my change of the timeout doesn't take affect and it's always uses the

[GitHub] [camel-k-runtime] makandre commented on issue #513: Thread blocked calling knative REST

2020-09-30 Thread GitBox
makandre commented on issue #513: URL: https://github.com/apache/camel-k-runtime/issues/513#issuecomment-701341244 How do I check that? I didn't configure specifically for quarkus, so I assume I'm using default. This is an

[GitHub] [camel-k-runtime] makandre commented on issue #513: Thread blocked calling knative REST

2020-09-30 Thread GitBox
makandre commented on issue #513: URL: https://github.com/apache/camel-k-runtime/issues/513#issuecomment-701328927 Sure, my route is acting as a proxy to another knative service ``` restConfiguration().setHost("a knative .svc.cluster.local host") rest("/results")