Crash with AStreams.InitializePrefix, success with AStreams.Initialize

[jo1234]

Hi,

I have a problem to get my asynchstream initialized.

My app connects nicely to a windows server when I use:

AStreams.[COLOR="Red"]Initialize[/COLOR](ClientSocket.InputStream, ClientSocket.OutputStream, "AStreamsIn")

However, I get a crash when I use:

AStreams.[COLOR="Red"]InitializePrefix[/COLOR](ClientSocket.InputStream, False, ClientSocket.OutputStream, "AStreamsIn")

Error: java.lang.ArrayIndexOutOfBondsException: Offset out of bonds: -1

Sub Process_Globals
    Dim ClientSocket As Socket      
    Dim AStreams As AsyncStreams
End Sub 

Sub cmdConnect_Click
    If Not(ClientSocket.IsInitialized) Then
       ClientSocket.Initialize("ClientSocket")
    End If
    ClientSocket.Connect(sIP, iPort, 2000)
End Sub

Sub ClientSocket_Connected (Successful As Boolean)
    If Successful Then
          AStreams.InitializePrefix(ClientSocket.InputStream, False, ClientSocket.OutputStream, "AStreamsIn")
    Else
        ClientSocket.Close 
    End If
End Sub

What am I doing wrong?

Thanks,
Johannes

 

[agraham]

Nothing. Read the AsyncStreams tutorial. Your server does not understand prefix mode.

 

[jo1234]

No, the server is not the issue (the server is my VB6 program, which sends the prefix).

The problem is that the app crashes when it hits the line:

AStreams.InitializePrefix(ClientSocket.InputStream, False, ClientSocket.OutputStream, "AStreamsIn")

Error: java.lang.ArrayIndexOutOfBondsException: Offset out of bonds: -1

Why?

thanks,
Johannes

PS: And yes, I did study the AsyncStreams tutorial

 

[agraham]

No idea! You are not giving enough information to even hazard a guess.

 

[jo1234]

This code below is sufficient to reproduce the error. Of course, you would need the responding server, but as said, the server registers the connection request by the app. And there is no data exchange between the two, because the app crashes when initializing the stream.

Moreover: If I change AStreams.InitializePrefix to AStreams.Initialize everything runs smoothly.

Note that AStreamsIn_Error is NOT triggered.
The app crashes fatally when executing the line

AStreams.InitializePrefix(ClientSocket.InputStream, False, ClientSocket.OutputStream, "AStreamsIn")

Complete code:

Sub Process_Globals
    Dim ClientSocket As Socket      
    Dim AStreams As AsyncStreams
    Dim buffer() As Byte
End Sub 

Sub Globals
   Dim cmdConnect As Button
End Sub

Sub Activity_Create(FirstTime As Boolean)
   Activity.LoadLayout ("main")
End Sub

Sub cmdConnect_Click
   If Not(ClientSocket.IsInitialized) Then
       ClientSocket.Initialize("ClientSocket")
    End If
    ClientSocket.Connect("192.168.1.3", 7610, 2000)
End Sub

Sub ClientSocket_Connected (Successful As Boolean)
    If Successful Then
          AStreams.InitializePrefix(ClientSocket.InputStream, False, ClientSocket.OutputStream, "AStreamsIn")
   Else
      ClientSocket.Close 
      End If
End Sub

Sub AStreamsIn_Error
   Msgbox (LastException.Message , "")
End Sub

 

[myriaddev]

idea

Note that when connected with your server using:
AStreams.Initialize, see if your server is sending/receiving
the correct byte order of size. Does your server
know when it is connected via AStreams.Initialize
or AStreams.InitializePrefix thus sends size or not ?
Hope this helps,
Jerry

 

[agraham]

That's a very odd error considering what Initialize actually does. Look in the unfiltered logs for the exception details. That will give the line number within AsyncStreams where it is happening.

 

[Michael eldred]

Program crashes in ASYNC prefix mode

I am having the exact same issue...

when initializing in normal mode I can communicate no problem,

when I switch to prefix mode the program crashes "An unexpected error has caused the forced closure of the program" type message..

I have programmed a microcontroller/bluetooth combo to send the required prefix.. I never recieve any data before it crashes

 

[Erel]

You should check the unfiltered logs for the exact error message. The problem is probably related to your prefix implementation in the other side. Maybe the byte order (endianess) is different?