[GitHub] [camel-k] oscerd commented on issue #2684: Unable to access MongoDB

2021-10-12 Thread GitBox


oscerd commented on issue #2684:
URL: https://github.com/apache/camel-k/issues/2684#issuecomment-940724995


   By the way your kamelet error seems to be related to knative not to mongodb
   
org.apache.camel.ResolveEndpointFailedException: Failed to resolve 
endpoint: 
knative://channel/isgattchannel?apiVersion=messaging.knative.dev%2Fv1=Channel
 due to: Cannot load Knative configuration from file or env variable


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [camel-k] oscerd commented on issue #2684: Unable to access MongoDB

2021-10-12 Thread GitBox


oscerd commented on issue #2684:
URL: https://github.com/apache/camel-k/issues/2684#issuecomment-940717695


   I tried again and cannot reproduce on the kamelets side.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [camel-k] oscerd commented on issue #2684: Unable to access MongoDB

2021-10-11 Thread GitBox


oscerd commented on issue #2684:
URL: https://github.com/apache/camel-k/issues/2684#issuecomment-940355641


   Kamelets are working. They have been tested for 1.6 by the way I'll try to 
reproduce. On minikube at least i don't see this 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [camel-k] oscerd commented on issue #2684: Unable to access MongoDB

2021-10-08 Thread GitBox


oscerd commented on issue #2684:
URL: https://github.com/apache/camel-k/issues/2684#issuecomment-939082189


   My test was using this
   
   
https://github.com/apache/camel-performance-tests/tree/main/profiling/kafka-mongo
   
   Which it is using Kamelets in the route definition.
   
   Btw I'll try to test on minikube to check


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [camel-k] oscerd commented on issue #2684: Unable to access MongoDB

2021-10-08 Thread GitBox


oscerd commented on issue #2684:
URL: https://github.com/apache/camel-k/issues/2684#issuecomment-939059619


   With the kamelets, you'll get some complaints before the correct connection 
will be done
   
   ```
   2021-10-08 19:08:39,308 WARN  [io.qua.net.run.NettyRecorder] (Thread-0) 
Netty DefaultChannelId initialization (with io.netty.machineId system property 
set to 6b:d5:f4:43:a6:d8:c4:47) took more than a second
   2021-10-08 19:08:41,106 INFO  [org.mon.dri.cluster] (main) Cluster created 
with settings {hosts=[127.0.0.1:27017], mode=SINGLE, 
requiredClusterType=UNKNOWN, serverSelectionTimeout='3 ms'}
   2021-10-08 19:08:42,019 INFO  [org.mon.dri.cluster] (main) Cluster created 
with settings {hosts=[127.0.0.1:27017], mode=SINGLE, 
requiredClusterType=UNKNOWN, serverSelectionTimeout='3 ms'}
   2021-10-08 19:08:42,710 INFO  [org.mon.dri.cluster] 
(cluster-ClusterId{value='61609738311ec2632f641801', 
description='null'}-127.0.0.1:27017) Exception in monitor thread while 
connecting to server 127.0.0.1:27017: com.mongodb.MongoSocketOpenException: 
Exception opening socket
at 
com.mongodb.internal.connection.SocketStream.open(SocketStream.java:70)
at 
com.mongodb.internal.connection.InternalStreamConnection.open(InternalStreamConnection.java:165)
at 
com.mongodb.internal.connection.DefaultServerMonitor$ServerMonitorRunnable.lookupServerDescription(DefaultServerMonitor.java:195)
at 
com.mongodb.internal.connection.DefaultServerMonitor$ServerMonitorRunnable.run(DefaultServerMonitor.java:151)
at java.base/java.lang.Thread.run(Thread.java:829)
   Caused by: java.net.ConnectException: Connection refused (Connection refused)
at java.base/java.net.PlainSocketImpl.socketConnect(Native Method)
at 
java.base/java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:399)
at 
java.base/java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:242)
at 
java.base/java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:224)
at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.base/java.net.Socket.connect(Socket.java:609)
at 
com.mongodb.internal.connection.SocketStreamHelper.initialize(SocketStreamHelper.java:107)
at 
com.mongodb.internal.connection.SocketStream.initializeSocket(SocketStream.java:79)
at 
com.mongodb.internal.connection.SocketStream.open(SocketStream.java:65)
... 4 more
   
   2021-10-08 19:08:43,009 INFO  [org.mon.dri.cluster] 
(cluster-ClusterId{value='6160973a311ec2632f641802', 
description='null'}-127.0.0.1:27017) Exception in monitor thread while 
connecting to server 127.0.0.1:27017: com.mongodb.MongoSocketOpenException: 
Exception opening socket
at 
com.mongodb.internal.connection.AsynchronousSocketChannelStream$OpenCompletionHandler.failed(AsynchronousSocketChannelStream.java:124)
at java.base/sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:129)
at 
java.base/sun.nio.ch.UnixAsynchronousSocketChannelImpl.finishConnect(UnixAsynchronousSocketChannelImpl.java:283)
at 
java.base/sun.nio.ch.UnixAsynchronousSocketChannelImpl.finish(UnixAsynchronousSocketChannelImpl.java:198)
at 
java.base/sun.nio.ch.UnixAsynchronousSocketChannelImpl.onEvent(UnixAsynchronousSocketChannelImpl.java:213)
at 
java.base/sun.nio.ch.EPollPort$EventHandlerTask.run(EPollPort.java:306)
at 
java.base/sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112)
at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
   Caused by: java.net.ConnectException: Connection refused
at 
java.base/sun.nio.ch.UnixAsynchronousSocketChannelImpl.checkConnect(Native 
Method)
at 
java.base/sun.nio.ch.UnixAsynchronousSocketChannelImpl.finishConnect(UnixAsynchronousSocketChannelImpl.java:252)
... 7 more
   ```
   
   But after that you'll get the correct connection, this is something related 
to underlined quarkus extension
   
   ```
   2021-10-08 19:08:54,308 INFO  [org.apa.cam.imp.eng.AbstractCamelContext] 
(main) StreamCaching is enabled on CamelContext: camel-k-runtime-examples-yaml
   2021-10-08 19:08:54,609 INFO  [org.mon.dri.cluster] (main) Cluster created 
with settings {hosts=[172.17.0.3:27017], mode=SINGLE, 
requiredClusterType=UNKNOWN, serverSelectionTimeout='3 ms'}
   2021-10-08 19:08:54,907 INFO  [org.apa.cam.com.mon.MongoDbEndpoint] (main) 
Initialising MongoDb endpoint: 
local-mongodb-1://test?collection=log=false=test=172.17.0.3=insert=xx=mongoadmin
   2021-10-08 19:08:55,415 INFO  [org.mon.dri.cluster] (main) Cluster 
description not yet available. Waiting for 3 ms before timing out
   2021-10-08 

[GitHub] [camel-k] oscerd commented on issue #2684: Unable to access MongoDB

2021-10-08 Thread GitBox


oscerd commented on issue #2684:
URL: https://github.com/apache/camel-k/issues/2684#issuecomment-939044358


   Well this seems weird. I tested the sink and source Kamelets multiple times 
and never faced this


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org