Home Forums Support Cant get Android example to work

  • This topic has 3 replies, 2 voices, and was last updated 8 years ago by Anonymous.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #4135
    Anonymous
    Inactive

    Dear All,

    Need some help with setting up the most basic example of the chat example locally, I run the Android example and set it as server and also run the ExamplesConsole.exe in which I choose the first option “Basic – Message Send”, when I try to send some text to the correct IP address as the Android stated it is listening to I dont get to see the text message in the Android application:
    Screen

    however when I close the ExamplesConsole.exe the Android application writes the following message:
    Android

    so the connection has been made earlier but the text was not shown?

    Please help me with this..

    Thank you all in advance!
    Best,
    R.

    #4136
    Anonymous
    Inactive

    Heya R,

    Are you using some kind of emulator for android? If so it is common that many of them are quite buggy when using network connections. Also ensure that all firewalls have been disabled at both end of the connection, or atleast that they allow the required ports through. You could also try enabling logging on the consoleexample to see what is happening when you try to send a message.

    Kind regards,
    Marc

    #4140
    Anonymous
    Inactive

    Hi Marc,

    Thank you for your reply.

    The following is the log output for a test between an Android Galaxy device and a PC running the Console example, in this test I’ve sent a message from the Android device to the PC, the log created but no message arrived:

    13.44.17.142 [9 - Info] - Added incoming packetHandler for 'Message' packetType.
    13.44.17.344 [9 - Info] - Created new connection listener (TCP-E).
    13.44.17.345 [9 - Info] - Created new connection listener (TCP-E).
    13.44.17.345 [9 - Info] - Created new connection listener (TCP-E).
    13.44.17.346 [9 - Info] - Created new connection listener (TCP-E).
    13.44.17.346 [9 - Info] - Created new connection listener (TCP-E).
    13.44.17.365 [9 - Info] - Listener started (TCP-E - 10.0.0.40:63135).
    13.44.17.371 [9 - Info] - Listener started (TCP-E - 192.168.56.1:63136).
    13.44.17.373 [9 - Info] - Listener started (TCP-E - 10.71.34.1:63137).
    13.44.17.375 [9 - Info] - Listener started (TCP-E - [::1]:63138).
    13.44.17.377 [9 - Info] - Listener started (TCP-E - 127.0.0.1:63139).
    Listening for TCP messages on:
    10.0.0.40:63135
    192.168.56.1:63136
    10.71.34.1:63137
    ::1:63138
    127.0.0.1:63139
    
    Please enter your message and press enter (Type 'exit' to quit):
    13.49.16.980 [11 - Info] - New incoming TCP connection from [TCP-E-U] 10.0.0.40:63135 -> 10.0.0.3:50474
    13.49.17.35 [15 - Trace] - RetrieveConnection by remoteEndPoint='10.0.0.3:50474', localEndPoint='10.0.0.40:63135', conne
    ctionType='TCP' and ApplicationLayerProtocolStatus='Enabled'. No matching connections found.
    13.49.17.36 [15 - Trace] - Creating new TCPConnection to connectionInfo='[TCP-E-U] 10.0.0.40:63135 -> 10.0.0.3:50474'. C
    onnection will be established.
    13.49.17.54 [15 - Info] - Appended connection specific packet handlers from listener '[TCP-E] Listening - 10.0.0.40:6313
    5' to connection '[TCP-E-U] 10.0.0.40:63135 -> 10.0.0.3:50474'.
    13.49.17.61 [15 - Trace] - Checking for existing connection by remoteEndPoint='10.0.0.3:50474', localEndPoint='10.0.0.40
    :63135', connectionType='TCP' and ApplicationLayerProtocolStatus='Enabled'.
    13.49.17.62 [15 - Trace] - RetrieveConnection by remoteEndPoint='10.0.0.3:50474', localEndPoint='10.0.0.40:63135', conne
    ctionType='TCP' and ApplicationLayerProtocolStatus='Enabled'. No matching connections found.
    13.49.17.87 [15 - Trace] - Adding connection reference by endPoint. Connection='[TCP-E-U] 10.0.0.40:63135 -> 10.0.0.3:50
    474'.
    13.49.17.89 [15 - Trace] - RetrieveConnection by remoteEndPoint='10.0.0.3:50474', localEndPoint='10.0.0.40:63135', conne
    ctionType='TCP' and ApplicationLayerProtocolStatus='Undefined'. No matching connections found.
    13.49.17.94 [15 - Trace] - RetrieveConnection by remoteEndPoint='10.0.0.3:50474', localEndPoint='10.0.0.40:63135', conne
    ctionType='TCP' and ApplicationLayerProtocolStatus='Undefined'. No matching connections found.
    13.49.17.97 [15 - Trace] - Completed adding connection reference by endPoint. Connection='[TCP-E-U] 10.0.0.40:63135 -> 1
    0.0.0.3:50474'.
    13.49.17.101 [15 - Trace] - Establishing new connection with [TCP-E-I] 10.0.0.40:63135 -> 10.0.0.3:50474
    13.49.17.110 [15 - Trace] - Updating connection reference by endPoint. Connection='[TCP-E-I] 10.0.0.40:63135 -> 10.0.0.3
    :50474'. Provided newRemoteEndPoint of 10.0.0.3:50474. Provided newLocalEndPoint of 10.0.0.40:63135.
    13.49.17.114 [15 - Trace] - Checking for existing connection by remoteEndPoint='10.0.0.3:50474', localEndPoint='10.0.0.4
    0:63135', connectionType='TCP' and ApplicationLayerProtocolStatus='Enabled'.
    13.49.17.116 [15 - Trace] - RetrieveConnection by remoteEndPoint='10.0.0.3:50474', localEndPoint='10.0.0.40:63135', conn
    ectionType='TCP' and ApplicationLayerProtocolStatus='Enabled'. 1 matching connections found.
    13.49.17.117 [15 - Trace] - Listening for incoming data from [TCP-E-I] 10.0.0.40:63135 -> 10.0.0.3:50474
    13.49.17.127 [15 - Debug] - Waiting for client connnectionInfo from [TCP-E-I] 10.0.0.40:63135 -> 10.0.0.3:50474
    13.49.17.377 [11 - Trace] -  ... 68 bytes added to packetBuilder for [TCP-E-I] 10.0.0.40:63135 -> 10.0.0.3:50474. Cached
     0 bytes, expecting 0 bytes.
    13.49.17.380 [11 - Trace] -  ... added 68 bytes to packetBuilder.
    13.49.17.398 [11 - Trace] -  ... checking for completed packet with 68 bytes read.
    13.49.17.399 [11 - Trace] -      ... deserializing header using 68 bytes, 68 bytes cached.
    13.49.17.440 [11 - Trace] -      ... more data required for complete packet payload. Expecting 119 total packet bytes.
    13.49.17.445 [11 - Trace] -  ... reusing byte[512] from packetBuilder which contains 68 existing bytes.
    13.49.17.859 [11 - Trace] -  ... 119 bytes added to packetBuilder for [TCP-E-I] 10.0.0.40:63135 -> 10.0.0.3:50474. Cache
    d 0 bytes, expecting 119 bytes.
    13.49.17.860 [11 - Trace] -  ... added 119 bytes to packetBuilder.
    13.49.17.861 [11 - Trace] -  ... checking for completed packet with 119 bytes read.
    13.49.17.862 [11 - Trace] -      ... deserializing header using 68 bytes, 119 bytes cached.
    13.49.17.871 [11 - Debug] - Received packet of type 'ConnectionSetup' from [TCP-E-I] 10.0.0.40:63135 -> 10.0.0.3:50474,
    containing 68 header bytes and 51 payload bytes.
    13.49.17.874 [11 - Trace] -  ... handling packet type 'ConnectionSetup' inline. Loop index - 0. pSeq#-5.
    13.49.17.886 [11 - Trace] - Handling a ConnectionSetup packet from [TCP-E-I] 10.0.0.40:63135 -> 10.0.0.3:50474 with a pr
    iority of AboveNormal.
    13.49.17.896 [11 - Trace] - RetrieveConnection by remoteEndPoint='10.0.0.3:50474', localEndPoint='10.0.0.40:63135', conn
    ectionType='TCP' and ApplicationLayerProtocolStatus='Enabled'. 1 matching connections found.
    13.49.17.897 [11 - Trace] - Updating connection reference by endPoint. Connection='[TCP-E-I] 10.0.0.40:63135 -> 10.0.0.3
    :50474'. Provided newRemoteEndPoint of 10.0.0.3:50474. Provided newLocalEndPoint of 10.0.0.40:63135.
    13.49.17.930 [11 - Trace] -  ... created packet of type ConnectionSetup. PacketObject data size is 52 bytes
    13.49.17.941 [11 - Trace] - Entering packet send of 'ConnectionSetup' packetType to [TCP-E-I] 10.0.0.40:63135 -> 10.0.0.
    3:50474 (7eb5SAG4N0ehimVnfFEb4w)
    13.49.17.951 [11 - Debug] - Sending a packet of type 'ConnectionSetup' to [TCP-E-I] 10.0.0.40:63135 -> 10.0.0.3:50474 (7
    eb5SAG4N0ehimVnfFEb4w) containing 68 header bytes and 52 payload bytes. Allowing 1000.0 ms/KB for send.
    13.49.17.977 [11 - Trace] -  ... 0.117KB sent at average of 5.208KB/s. Current:102.52 ms/KB, Connection Avg:110.93 ms/KB
    .
    13.49.17.978 [11 - Trace] - Completed packet send of 'ConnectionSetup' packetType to [TCP-E-I] 10.0.0.40:63135 -> 10.0.0
    .3:50474 (7eb5SAG4N0ehimVnfFEb4w)
    13.49.17.979 [11 - Trace] - Triggering handlers for packet of type 'ConnectionSetup' from [TCP-E-I] 10.0.0.40:63135 -> 1
    0.0.0.3:50474 (7eb5SAG4N0ehimVnfFEb4w)
    13.49.17.982 [11 - Trace] - Removing 119 bytes from incoming packet builder from connection with [TCP-E-E] 10.0.0.40:631
    35 -> 10.0.0.3:50474 (7eb5SAG4N0ehimVnfFEb4w).
    13.49.17.987 [15 - Trace] - Adding connection reference by identifier. Connection=[TCP-E-E] 10.0.0.40:63135 -> 10.0.0.3:
    50474 (7eb5SAG4N0ehimVnfFEb4w).
    13.49.17.988 [15 - Trace] - Checking for existing connection by remoteEndPoint='10.0.0.3:50474', localEndPoint='10.0.0.4
    0:63135', connectionType='TCP' and ApplicationLayerProtocolStatus='Enabled'.
    13.49.17.989 [15 - Trace] - RetrieveConnection by remoteEndPoint='10.0.0.3:50474', localEndPoint='10.0.0.40:63135', conn
    ectionType='TCP' and ApplicationLayerProtocolStatus='Enabled'. 1 matching connections found.
    13.49.17.990 [11 - Trace] -  ... removed 119 bytes from packetBuilder.
    13.49.17.997 [15 - Trace] -  ... connection successfully established with [TCP-E-E] 10.0.0.40:63135 -> 10.0.0.3:50474 (7
    eb5SAG4N0ehimVnfFEb4w)
    13.49.18.6 [21 - Debug] - Connection keep alive polling thread has started.
    13.49.18.400 [14 - Trace] -  ... 64 bytes added to packetBuilder for [TCP-E-E] 10.0.0.40:63135 -> 10.0.0.3:50474 (7eb5SA
    G4N0ehimVnfFEb4w). Cached 0 bytes, expecting 0 bytes.
    13.49.18.401 [14 - Trace] -  ... added 64 bytes to packetBuilder.
    13.49.18.403 [14 - Trace] -  ... checking for completed packet with 64 bytes read.
    13.49.18.404 [14 - Trace] -      ... deserializing header using 64 bytes, 64 bytes cached.
    13.49.18.407 [14 - Trace] -      ... more data required for complete packet payload. Expecting 120 total packet bytes.
    13.49.18.409 [14 - Trace] -  ... reusing byte[512] from packetBuilder which contains 64 existing bytes.
    13.49.18.416 [18 - Trace] -  ... 120 bytes added to packetBuilder for [TCP-E-E] 10.0.0.40:63135 -> 10.0.0.3:50474 (7eb5S
    AG4N0ehimVnfFEb4w). Cached 0 bytes, expecting 120 bytes.
    13.49.18.417 [18 - Trace] -  ... added 120 bytes to packetBuilder.
    13.49.18.418 [18 - Trace] -  ... checking for completed packet with 120 bytes read.
    13.49.18.420 [18 - Trace] -      ... deserializing header using 64 bytes, 120 bytes cached.
    13.49.18.421 [18 - Debug] - Received packet of type 'ChatMessage' from [TCP-E-E] 10.0.0.40:63135 -> 10.0.0.3:50474 (7eb5
    SAG4N0ehimVnfFEb4w), containing 64 header bytes and 56 payload bytes.
    13.49.18.429 [22 - Trace] - Handling a ChatMessage packet from [TCP-E-E] 10.0.0.40:63135 -> 10.0.0.3:50474 (7eb5SAG4N0eh
    imVnfFEb4w) with a priority of Normal.
    13.49.18.430 [18 - Trace] -  ... added completed ChatMessage packet to thread pool (Q:0, T:1, I:0) with priority Normal.
     Selected threadId=22. Loop index=0. pSeq#-6.
    13.49.18.435 [18 - Trace] - Removing 120 bytes from incoming packet builder from connection with [TCP-E-E] 10.0.0.40:631
    35 -> 10.0.0.3:50474 (7eb5SAG4N0ehimVnfFEb4w).
    13.49.18.438 [18 - Trace] -  ... removed 120 bytes from packetBuilder.
    13.49.18.430 [22 - Trace] - Triggering handlers for packet of type 'ChatMessage' from [TCP-E-E] 10.0.0.40:63135 -> 10.0.
    0.3:50474 (7eb5SAG4N0ehimVnfFEb4w)

    Many thanks in advance!

    #4141
    Anonymous
    Inactive

    According to the logs, everything appears to be working correctly. The last line refers to the packet handler that should write the message to the console – Triggering handlers for packet of type ‘ChatMessage’.

    The problem has to be something basic in your setup, i.e. something that is causing the messages to not be printed to the expected console window, or you are breakpointing in the code and not allowing the packet handlers to run.

    Sorry I can’t provide anything more specific but according to the logs everything looks good. Perhaps try two console applications first to ensure that works before adding the complication of a mobile device.

    Please let me know how you get on.

    Marc

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.