Kaa Project : ERROR o.s.web.context.ContextLoader and other error - server

I follow the steps from
https://kaaproject.github.io/kaa/docs/v0.10.0/Administration-guide/System-installation/Single-node-installation/
The last command is
$ cat /var/log/kaa/* | grep ERROR
and the error occur
2560-07-13 16:20:00,333 [main] ERROR o.s.web.context.ContextLoader - Context initialization failed
2560-07-13 16:25:59,019 [main] ERROR o.s.web.context.ContextLoader - Context initialization failed
2560-07-13 16:37:41,610 [main] ERROR o.s.web.context.ContextLoader - Context initialization failed
2560-07-13 17:01:49,474 [main] ERROR o.s.web.context.ContextLoader - Context initialization failed
2560-07-13 18:26:42,078 [main] ERROR o.s.web.context.ContextLoader - Context initialization failed
2560-07-13 18:27:31,562 [main] ERROR o.s.web.context.ContextLoader - Context initialization failed
2560-07-13 19:04:39,818 [qtp1591550320-71] ERROR org.spring4gwt.server.RpcHelper - Unexpected exception occured while invoking service method - createKaaAdmin
2560-07-14 10:26:03,480 [main] ERROR o.k.k.s.n.s.i.KaaNodeInitializationService - Failed to connect to Zookeeper within 5 minutes. Kaa Node Server will be stopped.
I reinstalled all again but it doesn't work. The last error, I already started Zookeeper but the error still occurs.

Related

Failing to start up HazelCast on AWS ECS

I'm trying to start up Hazelcast on AWS ECS. I have gone through the tutorial and have enabled all the permissions on the task role i.e decribeTasks, lisTasks etc. I have have a very simple configuration file
hazelcast:
cluster-name: hs-dcom-hazelcast
network:
join:
multicast:
enabled: false
aws:
enabled: true
interfaces:
enabled: true
interfaces:
- 10.106.*.*
However when the container tries to start it throws the following error
2023-01-23T14:47:16.975Z INFO 835 --- [ main] com.hazelcast.instance.impl.Node : [10.106.139.69]:5701 [hs-dcom-hazelcast] [5.0-BETA-1] Shutting down node engine...
7467 2023-01-23T14:47:17.004Z INFO 835 --- [ main] c.hazelcast.instance.impl.NodeExtension : [10.106.139.69]:5701 [hs-dcom-hazelcast] [5.0-BETA-1] Destroying node NodeExtension.
7468 2023-01-23T14:47:17.004Z INFO 835 --- [ main] com.hazelcast.instance.impl.Node : [10.106.139.69]:5701 [hs-dcom-hazelcast] [5.0-BETA-1] Hazelcast Shutdown is completed in 35 ms.
! 7469 2023-01-23T14:47:17.006Z WARN 835 --- [ main] o.s.w.c.s.GenericWebApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'hazelcastInstance' defined in class path resource [org/springframework/boot/autoconfigure/hazelcast/HazelcastServerConfiguration$HazelcastServerConfigFileConfiguration.class]: Failed to instantiate [com.hazelcast.core.HazelcastInstance]: Factory method 'hazelcastInstance' threw exception with message: Failure executing: POST at: https://ecs.eu-west-1.amazonaws.com. Message: {"__type":"InvalidParameterException","message":"Identifier is for 570169269855. Your accountId is 531465454359"}. HTTP Error Code: 400
7470 2023-01-23T14:47:17.021Z INFO 835 --- [ main] .s.b.a.l.ConditionEvaluationReportLogger :
7471
7472 Error starting ApplicationContext. To display the condition evaluation report re-run your application with 'debug' enabled.
7473 2023-01-23T14:47:17.052Z ERROR 835 --- [ main] o.s.boot.SpringApplication : Application run failed
7474
7475 org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'hazelcastInstance' defined in class path resource [org/springframework/boot/autoconfigure/hazelcast/HazelcastServerConfiguration$HazelcastServerConfigFileConfiguration.class]: Failed to instantiate [com.hazelcast.core.HazelcastInstance]: Factory method 'hazelcastInstance' threw exception with message: Failure executing: POST at: https://ecs.eu-west-1.amazonaws.com. Message: {"__type":"InvalidParameterException","message":"Identifier is for 570169269855. Your accountId is 531465454359"}. HTTP Error Code: 400
7476 at org.springframework.beans.factory.support.ConstructorResolver.instantiate(ConstructorResolver.java:657) ~[spring-beans-6.0.3.jar:6.0.3]
7477 at
I have tried looking on the forum, however can't seem to find anyone that has had this issue before.

occurred error while use zkcopy copy data from zookeeper

1、using zkcopy and run cmd as following:
java -jar target/zkcopy.jar --source xxxx:2181/clickhouse --target xxxx:2181/clickhouse
2、cmd output as following:
2021-09-07 21:47:33,542 [main] INFO com.github.ksprojects.ZkCopy - using 10 concurrent workers to copy data
2021-09-07 21:47:33,542 [main] INFO com.github.ksprojects.ZkCopy - delete nodes = true
2021-09-07 21:47:33,542 [main] INFO com.github.ksprojects.ZkCopy - ignore ephemeral nodes = true
2021-09-07 21:47:33,543 [main] INFO com.github.ksprojects.zkcopy.reader.Reader - Reading /clickhouse from 10.201.226.32:2181
2021-09-07 21:47:34,590 [main] INFO com.github.ksprojects.zkcopy.reader.Reader - Processing, total=12417, processed=3142
2021-09-07 21:47:35,655 [main] INFO com.github.ksprojects.zkcopy.reader.Reader - Processing, total=12417, processed=6059
2021-09-07 21:47:36,655 [main] INFO com.github.ksprojects.zkcopy.reader.Reader - Processing, total=12417, processed=9172
2021-09-07 21:47:37,655 [main] INFO com.github.ksprojects.zkcopy.reader.Reader - Processing, total=12497, processed=12497
2021-09-07 21:47:37,657 [main] INFO com.github.ksprojects.zkcopy.reader.Reader - Completed.
2021-09-07 21:47:37,687 [main] INFO com.github.ksprojects.zkcopy.writer.Writer - Writing data...
2021-09-07 21:47:38,338 [main] INFO com.github.ksprojects.zkcopy.writer.Writer - Committing transaction
2021-09-07 21:47:38,954 [main] INFO com.github.ksprojects.zkcopy.writer.Writer - Committing transaction
Exception in thread "main" picocli.CommandLine$ExecutionException: Error while calling command (com.github.ksprojects.ZkCopy#7960847b): java.lang.RuntimeException: org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss
at picocli.CommandLine.execute(CommandLine.java:458)
at picocli.CommandLine.access$300(CommandLine.java:134)
at picocli.CommandLine$RunLast.handleParseResult(CommandLine.java:538)
at picocli.CommandLine.parseWithHandlers(CommandLine.java:656)
at picocli.CommandLine.call(CommandLine.java:883)
at picocli.CommandLine.call(CommandLine.java:834)
at com.github.ksprojects.ZkCopy.main(ZkCopy.java:69)
Caused by: java.lang.RuntimeException: org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss
at com.github.ksprojects.zkcopy.writer.AutoCommitTransactionWrapper.maybeCommitTransaction(AutoCommitTransactionWrapper.java:74)
at com.github.ksprojects.zkcopy.writer.AutoCommitTransactionWrapper.create(AutoCommitTransactionWrapper.java:39)
at com.github.ksprojects.zkcopy.writer.Writer.upsertNode(Writer.java:147)
at com.github.ksprojects.zkcopy.writer.Writer.update(Writer.java:96)
at com.github.ksprojects.zkcopy.writer.Writer.update(Writer.java:104)
at com.github.ksprojects.zkcopy.writer.Writer.update(Writer.java:104)
at com.github.ksprojects.zkcopy.writer.Writer.update(Writer.java:104)
at com.github.ksprojects.zkcopy.writer.Writer.update(Writer.java:104)
at com.github.ksprojects.zkcopy.writer.Writer.update(Writer.java:104)
at com.github.ksprojects.zkcopy.writer.Writer.write(Writer.java:65)
at com.github.ksprojects.ZkCopy.call(ZkCopy.java:86)
at com.github.ksprojects.ZkCopy.call(ZkCopy.java:14)
at picocli.CommandLine.execute(CommandLine.java:456)

Error while initializing actor system wavesplatform com.protonail.leveldb.jna.LevelDBException

I want to fork the waves blockchain in which I wanted to change the coin. I first change the name of coin in waves node
link : https://github.com/wavesplatform/Waves/blob/version-1.2.x/node/src/main/scala/com/wavesplatform/transaction/assets/exchange/AssetPair.scala
according to the link I deployed on windows and I got this error.
ERROR: 18:28:45,568 ERROR [main] c.w.actor.RootActorSystem$ - Error while initializing actor system wavesplatform com.protonail.leveldb.jna.LevelDBException: IO error: /root/.local/share/waves-testnet/data: Invalid argument
(note : full error is given below)
software details:
openjdk11
ubuntu 18.04LTS
I am deploying in windows through ubuntu 18.04LTS by following steps for installing in windows and installing deb file.
link for installing: https://docs.waves.tech/en/waves-node/how-to-install-a-node/on-windows
command: java -jar node/target/waves-all-1.2.15-DIRTY.jar node/target/classes/application.conf
I got error while initializing it with wavesplatform.
root#WJLP-1220:/mnt/c/Users/swatim/Desktop/wavesProject/Waves/node/target# java -jar waves-all-1.2.15-DIRTY.jar classes/application.conf
2021-01-04 18:28:44,524 INFO [main] c.w.Application$ - Starting...
2021-01-04 18:28:45,082 INFO [ctor.default-dispatcher-4] a.event.slf4j.Slf4jLogger - Slf4jLogger started 2021-01-04 18:28:45,193 INFO [main] c.w.Application$ - Waves v1.2.15-DIRTY Blockchain Id: T
2021-01-04 18:28:45,271 INFO [main] c.w.d.LevelDBFactory$ - Loaded com.wavesplatform.database.jna.LevelDBJNADBFactory with com.wavesplatform.database.jna.LevelDBJNADBFactory#72ba28ee
2021-01-04 18:28:45,568 ERROR [main] c.w.actor.RootActorSystem$ - Error while initializing actor system wavesplatform com.protonail.leveldb.jna.LevelDBException: IO error: /root/.local/share/waves-testnet/data: Invalid argument
at com.protonail.leveldb.jna.LevelDBNative.checkError(LevelDBNative.java:295)
at com.protonail.leveldb.jna.LevelDB.(LevelDB.java:16) at com.wavesplatform.database.jna.LevelDBJNADBFactory.openJnaDatabase(LevelDBJNADBFactory.scala:11)
at com.wavesplatform.database.jna.LevelDBJNADBFactory.open(LevelDBJNADBFactory.scala:15)
at com.wavesplatform.database.package$.openDB(package.scala:51)
at com.wavesplatform.Application.(Application.scala:69)
at com.wavesplatform.Application$.$anonfun$startNode$4(Application.scala:558)
at com.wavesplatform.Application$.$anonfun$startNode$4$adapted(Application.scala:555)
at com.wavesplatform.actor.RootActorSystem$.start(RootActorSystem.scala:25)
at com.wavesplatform.Application$.startNode(Application.scala:555)
at com.wavesplatform.Application$.main(Application.scala:524)
at com.wavesplatform.Application.main(Application.scala)

UnresolvedAdressException milo

Im trying to connect from an basic Milo-Client (ReadSample), but getting UnresolvedAdressException. Both Client and Server are in an remote Network and I only got Access to the Client. I'm pretty sure its not a Firewall since I can Connect with other Clients (Prosys OPC UA Client) and i can see that the ip is resolved to an Host-Name in the Logs:
Server is opc.tcp://192.168.115.40:49580 aka opc.tcp://Extern-Mess-Rec:49580 (tried both in UaTcpStackClient.getEndpoints(url).get();)
13:24:51.530 [main] DEBUG
io.netty.util.internal.logging.InternalLoggerFactory - Using SLF4J as
the default logging framework 13:24:51.546 [main] DEBUG
io.netty.channel.MultithreadEventLoopGroup -
-Dio.netty.eventLoopThreads: 8 13:24:51.561 [main] DEBUG io.netty.util.internal.PlatformDependent0 - java.nio.Buffer.address:
available 13:24:51.561 [main] DEBUG
io.netty.util.internal.PlatformDependent0 - sun.misc.Unsafe.theUnsafe:
available 13:24:51.561 [main] DEBUG
io.netty.util.internal.PlatformDependent0 -
sun.misc.Unsafe.copyMemory: available 13:24:51.561 [main] DEBUG
io.netty.util.internal.PlatformDependent0 - java.nio.Bits.unaligned:
true 13:24:51.561 [main] DEBUG
io.netty.util.internal.PlatformDependent - Platform: Windows
13:24:51.561 [main] DEBUG io.netty.util.internal.PlatformDependent -
Java version: 8 13:24:51.561 [main] DEBUG
io.netty.util.internal.PlatformDependent - -Dio.netty.noUnsafe: false
13:24:51.561 [main] DEBUG io.netty.util.internal.PlatformDependent -
sun.misc.Unsafe: available 13:24:51.561 [main] DEBUG
io.netty.util.internal.PlatformDependent - -Dio.netty.noJavassist:
false 13:24:51.686 [main] DEBUG
io.netty.util.internal.PlatformDependent - Javassist: available
13:24:51.686 [main] DEBUG io.netty.util.internal.PlatformDependent -
-Dio.netty.tmpdir: C:\Users\SOFTWA~1\AppData\Local\Temp\3 (java.io.tmpdir) 13:24:51.686 [main] DEBUG
io.netty.util.internal.PlatformDependent - -Dio.netty.bitMode: 64
(sun.arch.data.model) 13:24:51.686 [main] DEBUG
io.netty.util.internal.PlatformDependent - -Dio.netty.noPreferDirect:
false 13:24:51.718 [main] DEBUG io.netty.channel.nio.NioEventLoop -
-Dio.netty.noKeySetOptimization: false 13:24:51.718 [main] DEBUG io.netty.channel.nio.NioEventLoop -
-Dio.netty.selectorAutoRebuildThreshold: 512 13:24:51.858 [main] DEBUG io.netty.util.ResourceLeakDetector - -Dio.netty.leakDetection.level:
simple 13:24:51.858 [main] DEBUG io.netty.util.ResourceLeakDetector -
-Dio.netty.leakDetection.maxRecords: 4 13:24:52.264 [main] DEBUG io.netty.buffer.PooledByteBufAllocator -
-Dio.netty.allocator.numHeapArenas: 8 13:24:52.264 [main] DEBUG io.netty.buffer.PooledByteBufAllocator -
-Dio.netty.allocator.numDirectArenas: 8 13:24:52.264 [main] DEBUG io.netty.buffer.PooledByteBufAllocator -
-Dio.netty.allocator.pageSize: 8192 13:24:52.264 [main] DEBUG io.netty.buffer.PooledByteBufAllocator -
-Dio.netty.allocator.maxOrder: 11 13:24:52.264 [main] DEBUG io.netty.buffer.PooledByteBufAllocator -
-Dio.netty.allocator.chunkSize: 16777216 13:24:52.264 [main] DEBUG io.netty.buffer.PooledByteBufAllocator -
-Dio.netty.allocator.tinyCacheSize: 512 13:24:52.264 [main] DEBUG io.netty.buffer.PooledByteBufAllocator -
-Dio.netty.allocator.smallCacheSize: 256 13:24:52.264 [main] DEBUG io.netty.buffer.PooledByteBufAllocator -
-Dio.netty.allocator.normalCacheSize: 64 13:24:52.264 [main] DEBUG io.netty.buffer.PooledByteBufAllocator -
-Dio.netty.allocator.maxCachedBufferCapacity: 32768 13:24:52.264 [main] DEBUG io.netty.buffer.PooledByteBufAllocator -
-Dio.netty.allocator.cacheTrimInterval: 8192 13:24:52.296 [main] DEBUG io.netty.util.internal.ThreadLocalRandom -
-Dio.netty.initialSeedUniquifier: 0x35f32988e43eab85 (took 10 ms) 13:24:52.327 [main] DEBUG io.netty.buffer.ByteBufUtil -
-Dio.netty.allocator.type: unpooled 13:24:52.327 [main] DEBUG io.netty.buffer.ByteBufUtil - -Dio.netty.threadLocalDirectBufferSize:
65536 13:24:52.327 [main] DEBUG io.netty.buffer.ByteBufUtil -
-Dio.netty.maxThreadLocalCharBufferSize: 16384 13:24:52.358 [ua-netty-event-loop-0] DEBUG
io.netty.util.internal.JavassistTypeParameterMatcherGenerator -
Generated:
io.netty.util.internal.matchers.org.eclipse.milo.opcua.stack.client.handlers.UaRequestFutureMatcher 13:24:52.389 [ua-netty-event-loop-0] DEBUG
io.netty.buffer.AbstractByteBuf -
-Dio.netty.buffer.bytebuf.checkAccessible: true 13:24:52.858 [ua-netty-event-loop-0] DEBUG io.netty.util.Recycler -
-Dio.netty.recycler.maxCapacity.default: 262144 13:24:52.890 [ua-netty-event-loop-0] DEBUG
org.eclipse.milo.opcua.stack.client.handlers.UaTcpClientAcknowledgeHandler
- Sent Hello message on channel=[id: 0xa0ec7fec, L:/130.83.225.169:58872 - R:/192.168.115.40:49580]. 13:24:52.905
[ua-netty-event-loop-0] DEBUG
org.eclipse.milo.opcua.stack.client.handlers.UaTcpClientAcknowledgeHandler
- Received Acknowledge message on channel=[id: 0xa0ec7fec, L:/130.83.225.169:58872 - R:/192.168.115.40:49580]. 13:24:52.921
[ua-netty-event-loop-0] DEBUG
org.eclipse.milo.opcua.stack.client.handlers.UaTcpClientMessageHandler
- OpenSecureChannel timeout scheduled for +5s 13:24:52.967 [ua-netty-event-loop-0] DEBUG
org.eclipse.milo.opcua.stack.client.handlers.UaTcpClientMessageHandler
- OpenSecureChannel timeout canceled 13:24:52.967 [ua-shared-pool-0] DEBUG
org.eclipse.milo.opcua.stack.client.handlers.UaTcpClientMessageHandler
- Sent OpenSecureChannelRequest (Issue, id=0, currentToken=-1, previousToken=-1). 13:24:52.999 [ua-shared-pool-1] DEBUG
org.eclipse.milo.opcua.stack.client.handlers.UaTcpClientMessageHandler
- Received OpenSecureChannelResponse. 13:24:52.999 [ua-shared-pool-1] DEBUG
org.eclipse.milo.opcua.stack.client.handlers.UaTcpClientMessageHandler
- SecureChannel id=1140, currentTokenId=1, previousTokenId=-1, lifetime=3600000ms, createdAt=DateTime{utcTime=131384570808248472,
javaDate=Fri May 05 13:24:40 CEST 2017} 13:24:52.999
[ua-netty-event-loop-0] DEBUG
org.eclipse.milo.opcua.stack.client.handlers.UaTcpClientMessageHandler
- 0 message(s) queued before handshake completed; sending now. 13:24:52.999 [ForkJoinPool.commonPool-worker-1] DEBUG
org.eclipse.milo.opcua.stack.client.ClientChannelManager - Channel
bootstrap succeeded: localAddress=/130.83.225.169:58872,
remoteAddress=/192.168.115.40:49580 13:24:53.061
[ForkJoinPool.commonPool-worker-1] DEBUG
org.eclipse.milo.opcua.stack.client.ClientChannelManager - Sending
CloseSecureChannelRequest... 13:24:53.061 [main] INFO
org.eclipse.milo.examples.client.ClientExampleRunner - Using endpoint:
opc.tcp://Extern-Mess-Rec:49580 [None] 13:24:53.077
[ua-netty-event-loop-0] DEBUG
org.eclipse.milo.opcua.stack.client.ClientChannelManager -
channelInactive(), disconnect complete 13:24:53.077
[ua-netty-event-loop-0] DEBUG
org.eclipse.milo.opcua.stack.client.ClientChannelManager - disconnect
complete, state set to Idle 13:24:53.124 [main] DEBUG
org.eclipse.milo.opcua.sdk.client.OpcUaClient - Added
ServiceFaultListener:
org.eclipse.milo.opcua.sdk.client.ClientSessionManager$$Lambda$1049/664457955#58134517
13:24:53.171 [main] DEBUG
org.eclipse.milo.opcua.sdk.client.OpcUaClient - Added
SessionActivityListener:
org.eclipse.milo.opcua.sdk.client.subscriptions.OpcUaSubscriptionManager$1#2d2e5f00
13:24:55.592 [ForkJoinPool.commonPool-worker-1] DEBUG
org.eclipse.milo.opcua.stack.client.ClientChannelManager - Channel
bootstrap failed: null java.nio.channels.UnresolvedAddressException:
null
at sun.nio.ch.Net.checkAddress(Net.java:101)
at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:622)
at io.netty.channel.socket.nio.NioSocketChannel.doConnect(NioSocketChannel.java:209)
at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.connect(AbstractNioChannel.java:207)
at io.netty.channel.DefaultChannelPipeline$HeadContext.connect(DefaultChannelPipeline.java:1279)
at io.netty.channel.AbstractChannelHandlerContext.invokeConnect(AbstractChannelHandlerContext.java:453)
at io.netty.channel.AbstractChannelHandlerContext.connect(AbstractChannelHandlerContext.java:439)
at io.netty.channel.ChannelDuplexHandler.connect(ChannelDuplexHandler.java:50)
at io.netty.channel.AbstractChannelHandlerContext.invokeConnect(AbstractChannelHandlerContext.java:453)
at io.netty.channel.AbstractChannelHandlerContext.connect(AbstractChannelHandlerContext.java:439)
at io.netty.channel.AbstractChannelHandlerContext.connect(AbstractChannelHandlerContext.java:421)
at io.netty.channel.DefaultChannelPipeline.connect(DefaultChannelPipeline.java:1024)
at io.netty.channel.AbstractChannel.connect(AbstractChannel.java:203)
at io.netty.bootstrap.Bootstrap$2.run(Bootstrap.java:167)
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:358)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:374)
at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
at java.lang.Thread.run(Thread.java:745) 13:24:55.608 [main] ERROR org.eclipse.milo.examples.client.ClientExampleRunner - Error
running client example: java.nio.channels.UnresolvedAddressException
java.util.concurrent.ExecutionException:
java.nio.channels.UnresolvedAddressException
at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895)
at org.eclipse.milo.examples.client.ReadExample.run(ReadExample.java:43)
at org.eclipse.milo.examples.client.ClientExampleRunner.run(ClientExampleRunner.java:106)
at org.eclipse.milo.examples.client.ReadExample.main(ReadExample.java:35)
Caused by: java.nio.channels.UnresolvedAddressException: null
at sun.nio.ch.Net.checkAddress(Net.java:101)
at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:622)
at io.netty.channel.socket.nio.NioSocketChannel.doConnect(NioSocketChannel.java:209)
at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.connect(AbstractNioChannel.java:207)
at io.netty.channel.DefaultChannelPipeline$HeadContext.connect(DefaultChannelPipeline.java:1279)
at io.netty.channel.AbstractChannelHandlerContext.invokeConnect(AbstractChannelHandlerContext.java:453)
at io.netty.channel.AbstractChannelHandlerContext.connect(AbstractChannelHandlerContext.java:439)
at io.netty.channel.ChannelDuplexHandler.connect(ChannelDuplexHandler.java:50)
at io.netty.channel.AbstractChannelHandlerContext.invokeConnect(AbstractChannelHandlerContext.java:453)
at io.netty.channel.AbstractChannelHandlerContext.connect(AbstractChannelHandlerContext.java:439)
at io.netty.channel.AbstractChannelHandlerContext.connect(AbstractChannelHandlerContext.java:421)
at io.netty.channel.DefaultChannelPipeline.connect(DefaultChannelPipeline.java:1024)
at io.netty.channel.AbstractChannel.connect(AbstractChannel.java:203)
at io.netty.bootstrap.Bootstrap$2.run(Bootstrap.java:167)
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:358)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:374)
at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
at java.lang.Thread.run(Thread.java:745)
The server you're getting endpoints from is probably returning "Extern-Mess-Rec" as its hostname, which you can't resolve.
See this answer for how to deal with that scenario.

eclipse console suddenly showing INFO

I'm using a apache HttpClient and I've started seeing some INFO output on the eclipse console:
0 [main] INFO org.apache.commons.httpclient.HttpMethodDirector - I/O exception (java.net.ConnectException) caught when processing request: Connection refused: connect
3 [main] INFO org.apache.commons.httpclient.HttpMethodDirector - Retrying request
3861 [pool-1-thread-25] INFO org.apache.commons.httpclient.HttpMethodDirector - I/O exception (java.net.ConnectException) caught when processing request: Connection refused: connect
3861 [pool-1-thread-25] INFO org.apache.commons.httpclient.HttpMethodDirector - Retrying request
3913 [pool-1-thread-16] INFO org.apache.commons.httpclient.HttpMethodBase - Response content length is not known
To my knowledge, nothing has changed. How can I get rid of it?
It's probably your logging library. HttpClient likely depends on commons-logging, which automatically picks up a logging implementation in your classpath (either java.util.logging or log4j) which by default writes on the console.