Re: Communications Endpoint Closed i JAVA SDK

dcbb · ‎Jun 22, 2016

Hi

I got error, can you please tell me How to solve this problem, when i ran the Java SDK it was showing error like this

12:37:05.724 [main] DEBUG i.n.u.i.l.InternalLoggerFactory - Using SLF4J as the default logging framework

12:37:05.724 [main] DEBUG i.n.c.MultithreadEventLoopGroup - -Dio.netty.eventLoopThreads: 8

12:37:05.740 [main] DEBUG i.n.util.internal.PlatformDependent0 - java.nio.Buffer.address: available

12:37:05.740 [main] DEBUG i.n.util.internal.PlatformDependent0 - sun.misc.Unsafe.theUnsafe: available

12:37:05.740 [main] DEBUG i.n.util.internal.PlatformDependent0 - sun.misc.Unsafe.copyMemory: available

12:37:05.740 [main] DEBUG i.n.util.internal.PlatformDependent0 - java.nio.Bits.unaligned: true

12:37:05.740 [main] DEBUG i.n.util.internal.PlatformDependent - Platform: Windows

12:37:05.740 [main] DEBUG i.n.util.internal.PlatformDependent - Java version: 7

12:37:05.740 [main] DEBUG i.n.util.internal.PlatformDependent - -Dio.netty.noUnsafe: false

12:37:05.740 [main] DEBUG i.n.util.internal.PlatformDependent - sun.misc.Unsafe: available

12:37:05.740 [main] DEBUG i.n.util.internal.PlatformDependent - -Dio.netty.noJavassist: false

12:37:05.740 [main] DEBUG i.n.util.internal.PlatformDependent - Javassist: unavailable

12:37:05.740 [main] DEBUG i.n.util.internal.PlatformDependent - You don't have Javassist in your class path or you don't have enough permission to load dynamically generated classes. Please check the configuration for better performance.

12:37:05.740 [main] DEBUG i.n.util.internal.PlatformDependent - -Dio.netty.tmpdir: C:\Users\524708\AppData\Local\Temp (java.io.tmpdir)

12:37:05.740 [main] DEBUG i.n.util.internal.PlatformDependent - -Dio.netty.bitMode: 64 (sun.arch.data.model)

12:37:05.740 [main] DEBUG i.n.util.internal.PlatformDependent - -Dio.netty.noPreferDirect: false

12:37:05.755 [main] DEBUG io.netty.channel.nio.NioEventLoop - -Dio.netty.noKeySetOptimization: false

12:37:05.755 [main] DEBUG io.netty.channel.nio.NioEventLoop - -Dio.netty.selectorAutoRebuildThreshold: 512

12:37:05.771 [main] DEBUG i.n.buffer.PooledByteBufAllocator - -Dio.netty.allocator.numHeapArenas: 8

12:37:05.771 [main] DEBUG i.n.buffer.PooledByteBufAllocator - -Dio.netty.allocator.numDirectArenas: 8

12:37:05.771 [main] DEBUG i.n.buffer.PooledByteBufAllocator - -Dio.netty.allocator.pageSize: 8192

12:37:05.771 [main] DEBUG i.n.buffer.PooledByteBufAllocator - -Dio.netty.allocator.maxOrder: 11

12:37:05.771 [main] DEBUG i.n.buffer.PooledByteBufAllocator - -Dio.netty.allocator.chunkSize: 16777216

12:37:05.771 [main] DEBUG i.n.buffer.PooledByteBufAllocator - -Dio.netty.allocator.tinyCacheSize: 512

12:37:05.771 [main] DEBUG i.n.buffer.PooledByteBufAllocator - -Dio.netty.allocator.smallCacheSize: 256

12:37:05.771 [main] DEBUG i.n.buffer.PooledByteBufAllocator - -Dio.netty.allocator.normalCacheSize: 64

12:37:05.771 [main] DEBUG i.n.buffer.PooledByteBufAllocator - -Dio.netty.allocator.maxCachedBufferCapacity: 32768

12:37:05.771 [main] DEBUG i.n.buffer.PooledByteBufAllocator - -Dio.netty.allocator.cacheTrimInterval: 8192

12:37:05.771 [main] INFO c.t.c.c.p.ClientMessageProcessor - Created new ClientMessageProcessor [minPoolSize: 4, maxPoolSize: 10, maxThreadLife: 10000, maxQueueSize: 1000]

12:37:05.787 [main] DEBUG c.t.c.c.e.m.ConnectivityMonitorTask - Initializing CommunicationEndpoint Connection Monitor...

12:37:05.849 [Client-EndpointMonitor-1] DEBUG c.t.c.c.e.m.ConnectivityMonitorTask - Resetting duty cycle

12:37:05.849 [Client-EndpointMonitor-1] DEBUG c.t.c.c.e.m.ConnectivityMonitorTask - Entering duty cycle ON

12:37:05.849 [Client-EndpointMonitor-1] INFO c.t.c.c.e.m.ConnectivityMonitorTask - Endpoint not connected [name: SteamSensorGateway, id: 0]. Attempting [re]connect...

12:37:05.849 [Client-EndpointMonitor-1] DEBUG c.t.c.c.e.ClientCommunicationEndpoint - Clearing endpoint authentication data [id: 0]

12:37:05.849 [Client-EndpointMonitor-1] INFO c.t.c.c.e.ClientCommunicationEndpoint - Needed to refill connections on client endpoint [id: 0] : [active: 0, max: 1]

12:37:05.958 [Client-EndpointMonitor-1] DEBUG i.n.util.internal.ThreadLocalRandom - -Dio.netty.initialSeedUniquifier: 0x43ed3595d8f82968 (took 8 ms)

12:37:05.974 [Client-EndpointMonitor-1] DEBUG io.netty.buffer.ByteBufUtil - -Dio.netty.allocator.type: unpooled

12:37:05.974 [Client-EndpointMonitor-1] DEBUG io.netty.buffer.ByteBufUtil - -Dio.netty.threadLocalDirectBufferSize: 65536

12:37:05.989 [NettyClient-NIO-1] DEBUG c.t.c.c.c.n.NettyClientConnectionFactory - initializing a secure websocket connection [ignore ssl errors: true]

12:37:06.223 [NettyClient-NIO-1] DEBUG io.netty.util.ResourceLeakDetector - -Dio.netty.leakDetectionLevel: simple

12:37:06.457 [NettyClient-NIO-1] DEBUG io.netty.util.Recycler - -Dio.netty.recycler.maxCapacity.default: 262144

12:37:06.457 [NettyClient-NIO-1] DEBUG c.t.c.c.c.n.ThingworxClientConnectionHandler - WebSocket Channel is connected [is open: true]

12:37:06.473 [NettyClient-NIO-1] DEBUG i.n.h.c.h.w.WebSocketClientHandshaker13 - WebSocket version 13 client handshake key: LEVUCD63fTo1R6jRTGK+uw==, expected response: 5vPutxkMO+yRK2zRXwuzpocwDkE=

12:37:06.691 [NettyClient-NIO-1] INFO c.t.c.c.c.n.NettyClientConnectionFactory - TRUST-ALL X509TrustManager.checkServerTrusted called [issuer: CN=DigiCert SHA2 High Assurance Server CA, OU=www.digicert.com, O=DigiCert Inc, C=US, subject: CN=*.portal.ptc.io, O=PTC Inc., L=Needham, ST=MA, C=US, authType: ECDHE_RSA]

12:37:06.691 [NettyClient-NIO-1] INFO c.t.c.c.c.n.NettyClientConnectionFactory - TRUST-ALL X509TrustManager.getAcceptedIssuers called

12:37:06.958 [NettyClient-NIO-1] DEBUG io.netty.handler.ssl.SslHandler - [id: 0xad494e38, /10.251.71.7:51887 => pp-20160303165712179.portal.ptc.io/52.5.87.101:443] HANDSHAKEN: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA

12:37:07.176 [NettyClient-NIO-1] DEBUG c.t.c.c.c.n.ThingworxClientConnectionHandler - [ClientHandler: 2055812419] Client websocket handshake is complete

12:37:07.192 [Client-EndpointMonitor-1] INFO c.t.c.c.e.ClientCommunicationEndpoint - Preparing new Connection Authentication Request: DispatchingClientEndpoint [id: 0, isConnected: false, open connections: 0, max connections: 1]

12:37:07.192 [Client-EndpointMonitor-1] DEBUG c.t.c.c.e.CommunicationEndpoint - Sending connection authentication message, waiting for response [sync key: 1, message: AuthRequestMessage [requestId: 1, endpointId: -1, sessionId: -1, method: AUTHREQUEST]]

12:37:07.192 [NettyClient-NIO-1] DEBUG i.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=2 length=60

12:37:07.410 [NettyClient-NIO-1] DEBUG i.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=2

12:37:07.410 [NettyClient-NIO-1] DEBUG i.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=17

12:37:07.426 [NettyClient-NIO-1] DEBUG c.t.c.c.e.DispatchingClientEndpoint - RESPONSE received [endpoint id: 0, duration: 234] ResponseMessage [requestId: 1, endpointId: 1488, sessionId: 1488, code: STATUS_SUCCESS, multipart: false, packet #: 0, total packets: 0]

12:37:07.426 [Client-EndpointMonitor-1] INFO c.t.c.c.e.ClientCommunicationEndpoint - Authentication Request was SUCCESSFUL [tworx session id: 1488, connection group id: 1488]

12:37:07.426 [Client-EndpointMonitor-1] DEBUG c.t.c.c.e.CommunicationEndpoint - [Endpoint id: 0, connection id: 0-0] added Connection

12:37:07.426 [Client-EndpointMonitor-1] INFO c.t.c.c.e.ClientCommunicationEndpoint - Successfully reconnected client endpoint [id: 0] : [active: 1, max: 1]

12:37:07.426 [Client-EndpointMonitor-1] INFO c.t.c.client.ConnectedThingClient - Communications Endpoint Opened

12:37:07.426 [Client-EndpointMonitor-1] DEBUG c.t.c.c.e.CommunicationEndpoint - Sending synchronous message, waiting for response [sync key: 2, message: BindRequestMessage [requestId: 2, method: BINDREQUEST, names: [*SN00010, *SN00011, *SN00012, *SN00013, *SN00014, *SN00015, *SN00016, *SN00017, *SN00018, *SN00019, SteamSensorGateway, SteamSensorGateway]]]

12:37:07.426 [NettyClient-NIO-1] DEBUG i.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=2 length=176

12:37:07.644 [NettyClient-NIO-1] INFO c.t.c.c.c.n.NettyClientConnection - [websocket id: 0-0] Closing underlying websocket channel

12:37:07.644 [NettyClient-NIO-1] INFO c.t.c.c.c.n.NettyClientConnection - [websocket id: 0-0] Unregistering NettyClientConnection from ClientEndpoint

12:37:07.644 [NettyClient-NIO-1] DEBUG c.t.c.c.e.CommunicationEndpoint - [Endpoint id: 0, connection id: 0-0] removed Connection

12:37:07.644 [NettyClient-NIO-1] INFO c.t.c.c.e.CommunicationEndpoint - All Connections are closed [endpoint id: 0]

12:37:07.644 [NettyClient-NIO-1] INFO c.t.c.client.ConnectedThingClient - Communications Endpoint Closed

supandey · ‎Jun 22, 2016

can you pinpoint the error?

dcbb · ‎Jun 23, 2016

12:37:07.644 [NettyClient-NIO-1] INFO c.t.c.client.ConnectedThingClient - Communications Endpoint Closed

ibanham · ‎Jun 22, 2016

Hi

Is there anything in the Platform logs? If possible put the communication log on "trace" and try connecting your SDK application again.

Regards

Ian

dcbb · ‎Jun 23, 2016

12:37:07.644 [NettyClient-NIO-1] INFO c.t.c.client.ConnectedThingClient - Communications Endpoint Closed

dcbb · ‎Jun 23, 2016

Hi

I Have doubt the problem in composer i mean WS communication subsystem there all the size of seconds

ibanham · ‎Jun 23, 2016

The logs on the platform sometimes give reasons as to why the connection was closed. There's no guarantee it'll point to a solution but it's worth checking....

dcbb · ‎Jun 23, 2016

if u want my code i will send u

ibanham · ‎Jun 23, 2016

Not at this time, the steam sensor code is pretty robust. I'm guessing there's a small configuration issue somewhere, the challenge is to find out where....

In composer, go to the Monitoring menu, then communication log. In the Settings tab, set the level for this log to trace. Return to the Viewer tab and then start your Edge application, you should get details of what is happening on the server side when the Edge application tries to connect.

dcbb · ‎Jun 23, 2016

Now i saw in local server,ok fine it worked in local server fine but i have 443 URL there problem occurred

dcbb · ‎Jun 23, 2016

you know idea on dashboard

i have troubled lot because it is overlapping the gadgets in dashboard, i mean change one position to onther position . that is not good.my thing is not change position. if u have idea please tell me....

mhollenbach · ‎Jun 23, 2016

Out of curiosity, do you leave the Java SDK running after the INFO message or does it completely kill the application from proceeding any further? Once the websocket closes it should attempt a reconnect once property updates need to be pushed again.

Meghan