PING > Benoît (ServerSocket)

[nospam.nospam.nospam]

Benoît,

I'd like to ask you take a look at something, please. I've been tearing
my hair out over this problem for weeks, but now that I've finally
nailed it, I can't reproduce it. I encountered this problem a few weeks
back in the ServerSocket component; my code had been working great for
weeks then suddenly it stopped dead, for no reason that I could explain
except a reboot (one day it worked, the next it didn't). I even went to
the trouble of a format and clean install, and still had the problem
(Ubuntu 9.04 x86 and 9.10 x64).

To cut a short story long, to find out what the problem was, I created a
project from the ServerSocket example in 2.17 (I was using 2.16 last
time this happened, and it was the same with the much earlier version
supplied with Ubuntu 9.04).

I then stripped the example down to get rid of all the buttons and other
adornments on the screen: The code attached in A1.tar.gz worked; it is
the stripped-down ServerSocket example I was using as a benchmark
against my own code.

Next, I stripped absolutely everything out of my no longer working code
and manually edited it, one change at a time, line for line, to make it
match precisely what is in A1.tar.gz, which works. When I say precisely
I mean I even changed the variable names to match, and every single
newline was replicated as well. I ran my code at each change, and each
time either:

1) PUBLIC SUB Socket_Read() failed to fire

Or

2) WRITE #Client, "200 Get lost! Leave me alone!\r\n", Len("200 Get
lost! Leave me alone!\r\n") in procedure PUBLIC SUB Socket_Ready()
failed to reach the client.

It has to be one of those two, I can't say which one, but I can say that
PUBLIC SUB Socket_Ready was firing <-- It was firing. Anyway I got down
to the very last change I could possibly make so that my own code
matched the working, modified example ServerSocket code exactly. That
change was this:

The working code
================

PUBLIC SUB Form_Open()

  Server.Type = Net.Internet
  Server.Port = 5001
  Server.Listen(1)

END

The not working code
====================

PUBLIC SUB Form_Open()

  Server.Port = 5001
  Server.Type = Net.Internet
  Server.Listen(1)

END

As soon as I ran my code after swapping the Server.Port and Server.Type
lines, I swear, it worked. So I reversed the change and it still
worked :(

So I created a new project, added a ServerSocket control named Server,
pasted in the not working code prior to the line swap, and it worked as
well :(

Ok, either I am going nuts or my Gambas has made a liar out of me.
Perhaps I am crazy and ought to be locked up in a rubber room with a
straight-jacket on?

Is there any possible way that setting Server.Port before Server.Type
could cause ServerSocket to behave oddly? Could an Ubuntu update
overwrite something that ServerSocket uses and thereby cause
ServerSocket to stop working suddenly --> if and only if Server.Port is
set before Server.Type? Am I really insane? Inquiring minds that don't
want to be labelled "MAD!!!" want to know.

Truly, I cannot now reproduce this problem after that line swap. The
code continues to work, no matter what inhumane atrocities I commit upon
it.

I am so frustrated by this problem that if you tell me that I am indeed
insane I will probably believe you.





------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Gambas-user mailing list
Gambas-user@...
https://lists.sourceforge.net/lists/listinfo/gambas-user

> Benoît,
>
> I'd like to ask you take a look at something, please. I've been tearing
> my hair out over this problem for weeks, but now that I've finally
> nailed it, I can't reproduce it. I encountered this problem a few weeks
> back in the ServerSocket component; my code had been working great for
> weeks then suddenly it stopped dead, for no reason that I could explain
> except a reboot (one day it worked, the next it didn't). I even went to
> the trouble of a format and clean install, and still had the problem
> (Ubuntu 9.04 x86 and 9.10 x64).
>
> To cut a short story long, to find out what the problem was, I created a
> project from the ServerSocket example in 2.17 (I was using 2.16 last
> time this happened, and it was the same with the much earlier version
> supplied with Ubuntu 9.04).
>
> I then stripped the example down to get rid of all the buttons and other
> adornments on the screen: The code attached in A1.tar.gz worked; it is
> the stripped-down ServerSocket example I was using as a benchmark
> against my own code.
>
> Next, I stripped absolutely everything out of my no longer working code
> and manually edited it, one change at a time, line for line, to make it
> match precisely what is in A1.tar.gz, which works. When I say precisely
> I mean I even changed the variable names to match, and every single
> newline was replicated as well. I ran my code at each change, and each
> time either:
>
> 1) PUBLIC SUB Socket_Read() failed to fire
>
> Or
>
> 2) WRITE #Client, "200 Get lost! Leave me alone!\r\n", Len("200 Get
> lost! Leave me alone!\r\n") in procedure PUBLIC SUB Socket_Ready()
> failed to reach the client.
>
> It has to be one of those two, I can't say which one, but I can say that
> PUBLIC SUB Socket_Ready was firing <-- It was firing. Anyway I got down
> to the very last change I could possibly make so that my own code
> matched the working, modified example ServerSocket code exactly. That
> change was this:
>
> The working code
> ================
>
> PUBLIC SUB Form_Open()
>
>   Server.Type = Net.Internet
>   Server.Port = 5001
>   Server.Listen(1)
>
> END
>
> The not working code
> ====================
>
> PUBLIC SUB Form_Open()
>
>   Server.Port = 5001
>   Server.Type = Net.Internet
>   Server.Listen(1)
>
> END
>
> As soon as I ran my code after swapping the Server.Port and Server.Type
> lines, I swear, it worked. So I reversed the change and it still
> worked :(
>
> So I created a new project, added a ServerSocket control named Server,
> pasted in the not working code prior to the line swap, and it worked as
> well :(
>
> Ok, either I am going nuts or my Gambas has made a liar out of me.
> Perhaps I am crazy and ought to be locked up in a rubber room with a
> straight-jacket on?
>
> Is there any possible way that setting Server.Port before Server.Type
> could cause ServerSocket to behave oddly? Could an Ubuntu update
> overwrite something that ServerSocket uses and thereby cause
> ServerSocket to stop working suddenly --> if and only if Server.Port is
> set before Server.Type? Am I really insane? Inquiring minds that don't
> want to be labelled "MAD!!!" want to know.
>
> Truly, I cannot now reproduce this problem after that line swap. The
> code continues to work, no matter what inhumane atrocities I commit upon
> it.
>
> I am so frustrated by this problem that if you tell me that I am indeed
> insane I will probably believe you.
>

I'm sorry, but setting the Port and Type property does nothing except storing
the integer values in memory. These properties are used when you call
Listen().

I'm not completely sure this is a Gambas problem, as in your previous mail you
said that, when your program suddenly stopped working, the ServerSocket
example stopped working too. And that rebooting changed nothing: the only way
for Gambas to do that after a reboot is killing your network card!

If only you have noticed the full "broken pipe" error message... :-s. If you
have the problem again, please note it carefully!

Regards,

--
Benoît Minisini

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Gambas-user mailing list
Gambas-user@...
https://lists.sourceforge.net/lists/listinfo/gambas-user

[nospam.nospam.nospam]

On Thu, 2009-11-05 at 10:53 +0100, Benoît Minisini wrote:

> > Benoît,
> >
> > I'd like to ask you take a look at something, please. I've been tearing
> > my hair out over this problem for weeks, but now that I've finally
> > nailed it, I can't reproduce it. I encountered this problem a few weeks
> > back in the ServerSocket component; my code had been working great for
> > weeks then suddenly it stopped dead, for no reason that I could explain
> > except a reboot (one day it worked, the next it didn't). I even went to
> > the trouble of a format and clean install, and still had the problem
> > (Ubuntu 9.04 x86 and 9.10 x64).
> >
> > To cut a short story long, to find out what the problem was, I created a
> > project from the ServerSocket example in 2.17 (I was using 2.16 last
> > time this happened, and it was the same with the much earlier version
> > supplied with Ubuntu 9.04).
> >
> > I then stripped the example down to get rid of all the buttons and other
> > adornments on the screen: The code attached in A1.tar.gz worked; it is
> > the stripped-down ServerSocket example I was using as a benchmark
> > against my own code.
> >
> > Next, I stripped absolutely everything out of my no longer working code
> > and manually edited it, one change at a time, line for line, to make it
> > match precisely what is in A1.tar.gz, which works. When I say precisely
> > I mean I even changed the variable names to match, and every single
> > newline was replicated as well. I ran my code at each change, and each
> > time either:
> >
> > 1) PUBLIC SUB Socket_Read() failed to fire
> >
> > Or
> >
> > 2) WRITE #Client, "200 Get lost! Leave me alone!\r\n", Len("200 Get
> > lost! Leave me alone!\r\n") in procedure PUBLIC SUB Socket_Ready()
> > failed to reach the client.
> >
> > It has to be one of those two, I can't say which one, but I can say that
> > PUBLIC SUB Socket_Ready was firing <-- It was firing. Anyway I got down
> > to the very last change I could possibly make so that my own code
> > matched the working, modified example ServerSocket code exactly. That
> > change was this:
> >
> > The working code
> > ================
> >
> > PUBLIC SUB Form_Open()
> >
> >   Server.Type = Net.Internet
> >   Server.Port = 5001
> >   Server.Listen(1)
> >
> > END
> >
> > The not working code
> > ====================
> >
> > PUBLIC SUB Form_Open()
> >
> >   Server.Port = 5001
> >   Server.Type = Net.Internet
> >   Server.Listen(1)
> >
> > END
> >
> > As soon as I ran my code after swapping the Server.Port and Server.Type
> > lines, I swear, it worked. So I reversed the change and it still
> > worked :(
> >
> > So I created a new project, added a ServerSocket control named Server,
> > pasted in the not working code prior to the line swap, and it worked as
> > well :(
> >
> > Ok, either I am going nuts or my Gambas has made a liar out of me.
> > Perhaps I am crazy and ought to be locked up in a rubber room with a
> > straight-jacket on?
> >
> > Is there any possible way that setting Server.Port before Server.Type
> > could cause ServerSocket to behave oddly? Could an Ubuntu update
> > overwrite something that ServerSocket uses and thereby cause
> > ServerSocket to stop working suddenly --> if and only if Server.Port is
> > set before Server.Type? Am I really insane? Inquiring minds that don't
> > want to be labelled "MAD!!!" want to know.
> >
> > Truly, I cannot now reproduce this problem after that line swap. The
> > code continues to work, no matter what inhumane atrocities I commit upon
> > it.
> >
> > I am so frustrated by this problem that if you tell me that I am indeed
> > insane I will probably believe you.
> >
>
> I'm sorry, but setting the Port and Type property does nothing except storing
> the integer values in memory. These properties are used when you call
> Listen().
>
> I'm not completely sure this is a Gambas problem, as in your previous mail you
> said that, when your program suddenly stopped working, the ServerSocket
> example stopped working too. And that rebooting changed nothing: the only way
> for Gambas to do that after a reboot is killing your network card!
>
> If only you have noticed the full "broken pipe" error message... :-s. If you
> have the problem again, please note it carefully!

Ok, so I'm crazy.

The broken pipe error is irrelevant because I am using a different
machine and still have the same issue.

> the ServerSocket example stopped working too

Yes, it did.

I'll keep my eye on the problem. I want to be able to say, "I TOLD YOU
SO!!!"

Mind you, it doesn't exactly instil confidence in me to bother getting
the application finished.


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Gambas-user mailing list
Gambas-user@...
https://lists.sourceforge.net/lists/listinfo/gambas-user

> On Thu, 2009-11-05 at 10:53 +0100, Benoît Minisini wrote:
> > > Benoît,
> > >
> > > I'd like to ask you take a look at something, please. I've been tearing
> > > my hair out over this problem for weeks, but now that I've finally
> > > nailed it, I can't reproduce it. I encountered this problem a few weeks
> > > back in the ServerSocket component; my code had been working great for
> > > weeks then suddenly it stopped dead, for no reason that I could explain
> > > except a reboot (one day it worked, the next it didn't). I even went to
> > > the trouble of a format and clean install, and still had the problem
> > > (Ubuntu 9.04 x86 and 9.10 x64).
> > >
> > > To cut a short story long, to find out what the problem was, I created
> > > a project from the ServerSocket example in 2.17 (I was using 2.16 last
> > > time this happened, and it was the same with the much earlier version
> > > supplied with Ubuntu 9.04).
> > >
> > > I then stripped the example down to get rid of all the buttons and
> > > other adornments on the screen: The code attached in A1.tar.gz worked;
> > > it is the stripped-down ServerSocket example I was using as a benchmark
> > > against my own code.
> > >
> > > Next, I stripped absolutely everything out of my no longer working code
> > > and manually edited it, one change at a time, line for line, to make it
> > > match precisely what is in A1.tar.gz, which works. When I say precisely
> > > I mean I even changed the variable names to match, and every single
> > > newline was replicated as well. I ran my code at each change, and each
> > > time either:
> > >
> > > 1) PUBLIC SUB Socket_Read() failed to fire
> > >
> > > Or
> > >
> > > 2) WRITE #Client, "200 Get lost! Leave me alone!\r\n", Len("200 Get
> > > lost! Leave me alone!\r\n") in procedure PUBLIC SUB Socket_Ready()
> > > failed to reach the client.
> > >
> > > It has to be one of those two, I can't say which one, but I can say
> > > that PUBLIC SUB Socket_Ready was firing <-- It was firing. Anyway I got
> > > down to the very last change I could possibly make so that my own code
> > > matched the working, modified example ServerSocket code exactly. That
> > > change was this:
> > >
> > > The working code
> > > ================
> > >
> > > PUBLIC SUB Form_Open()
> > >
> > >   Server.Type = Net.Internet
> > >   Server.Port = 5001
> > >   Server.Listen(1)
> > >
> > > END
> > >
> > > The not working code
> > > ====================
> > >
> > > PUBLIC SUB Form_Open()
> > >
> > >   Server.Port = 5001
> > >   Server.Type = Net.Internet
> > >   Server.Listen(1)
> > >
> > > END
> > >
> > > As soon as I ran my code after swapping the Server.Port and Server.Type
> > > lines, I swear, it worked. So I reversed the change and it still
> > > worked :(
> > >
> > > So I created a new project, added a ServerSocket control named Server,
> > > pasted in the not working code prior to the line swap, and it worked as
> > > well :(
> > >
> > > Ok, either I am going nuts or my Gambas has made a liar out of me.
> > > Perhaps I am crazy and ought to be locked up in a rubber room with a
> > > straight-jacket on?
> > >
> > > Is there any possible way that setting Server.Port before Server.Type
> > > could cause ServerSocket to behave oddly? Could an Ubuntu update
> > > overwrite something that ServerSocket uses and thereby cause
> > > ServerSocket to stop working suddenly --> if and only if Server.Port is
> > > set before Server.Type? Am I really insane? Inquiring minds that don't
> > > want to be labelled "MAD!!!" want to know.
> > >
> > > Truly, I cannot now reproduce this problem after that line swap. The
> > > code continues to work, no matter what inhumane atrocities I commit
> > > upon it.
> > >
> > > I am so frustrated by this problem that if you tell me that I am indeed
> > > insane I will probably believe you.
> >
> > I'm sorry, but setting the Port and Type property does nothing except
> > storing the integer values in memory. These properties are used when you
> > call Listen().
> >
> > I'm not completely sure this is a Gambas problem, as in your previous
> > mail you said that, when your program suddenly stopped working, the
> > ServerSocket example stopped working too. And that rebooting changed
> > nothing: the only way for Gambas to do that after a reboot is killing
> > your network card!
> >
> > If only you have noticed the full "broken pipe" error message... :-s. If
> > you have the problem again, please note it carefully!
>
> Ok, so I'm crazy.
>

No. I don't think so. :-)

But if rebooting your Linux server does not make the application work again, I
can't really suspect Gambas, as it does not save anything on the hard disk,
especially the network component.

Did you test the connection with telnet, or any other non-Gambas program? Did
you test another socket server application not made in Gambas?

The only possibility I see would be a memory corruption in the network
component - it is possible, I didn't write it :-). By reading the source code
of the Listen() method, I didn't see anything that could lead to that. But I
will check again.

A way to see these kinds of error is running Gambas inside valgrind:

$ cd /path/to/my/application/project
$ valgrind --tool=memcheck --num-callers=40 --track-origins=yes gbx2
...

And tell me all the messages reported by valgrind during the life of the
application.


> The broken pipe error is irrelevant because I am using a different
> machine and still have the same issue.
>

I thought you were talking about an error message from your gambas
application.

> > the ServerSocket example stopped working too
>
> Yes, it did.
>
> I'll keep my eye on the problem. I want to be able to say, "I TOLD YOU
> SO!!!"
>
> Mind you, it doesn't exactly instil confidence in me to bother getting
> the application finished.
>

If the information you gave are all exact (rebooting changed nothing, suddenly
everything works again), the problem should come from something outside of the
operating system.

Regards,

--
Benoît Minisini

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Gambas-user mailing list
Gambas-user@...
https://lists.sourceforge.net/lists/listinfo/gambas-user

[Jean-Yves F. Barbier-2]

Benoît Minisini a écrit :
...

> But if rebooting your Linux server does not make the application work again, I
> can't really suspect Gambas, as it does not save anything on the hard disk,
> especially the network component.
>
> Did you test the connection with telnet, or any other non-Gambas program? Did
> you test another socket server application not made in Gambas?
>
> The only possibility I see would be a memory corruption in the network
> component - it is possible, I didn't write it :-). By reading the source code
> of the Listen() method, I didn't see anything that could lead to that. But I
> will check again.

May be a RAM is corrupted, running a full memtest86+ could reveal that
(well @ least 2 tests: while physically swapping RAMs between tests in order
to completely test low addresses of the 1st one)

--
Must be getting close to town -- we're hitting more people.

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Gambas-user mailing list
Gambas-user@...
https://lists.sourceforge.net/lists/listinfo/gambas-user

[nospam.nospam.nospam]

On Thu, 2009-11-05 at 11:54 +0100, Benoît Minisini wrote:

> Did you test the connection with telnet, or any other non-Gambas program? Did
> you test another socket server application not made in Gambas?

No. I don't have one.

> The only possibility I see would be a memory corruption in the network
> component - it is possible, I didn't write it :-). By reading the source code
> of the Listen() method, I didn't see anything that could lead to that. But I
> will check again.

That's all I'm asking :)

> A way to see these kinds of error is running Gambas inside valgrind:
>
> $ cd /path/to/my/application/project
> $ valgrind --tool=memcheck --num-callers=40 --track-origins=yes gbx2
> ...
>
> And tell me all the messages reported by valgrind during the life of the
> application.
>
>
> > The broken pipe error is irrelevant because I am using a different
> > machine and still have the same issue.
> >
>
> I thought you were talking about an error message from your gambas
> application.

The message was in Gambas. A Windows server rebooted. However since then
I have changed machines (both the server machine and the workstation)
and had the same problem with PUBLIC SUB Socket_Read() or WRITE #Client
in PUBLIC SUB Socket_Ready()... until I swapped those two lines of code
around.

> > > the ServerSocket example stopped working too
> >
> > Yes, it did.
> >
> > I'll keep my eye on the problem. I want to be able to say, "I TOLD YOU
> > SO!!!"
> >
> > Mind you, it doesn't exactly instil confidence in me to bother getting
> > the application finished.
> >
>
> If the information you gave are all exact (rebooting changed nothing, suddenly
> everything works again), the problem should come from something outside of the
> operating system.

It wasn't working until I the instant I swapped those two lines then,
VOILA! It suddenly worked and refused to let me repeat the problem.

Anyway, all I wanted was for you to take a look and you've offered to do
that so I'm happy. If it happens again I'll let you know if I discover
anything.

Thanks, your help is appreciated.

> Regards,
>




------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Gambas-user mailing list
Gambas-user@...
https://lists.sourceforge.net/lists/listinfo/gambas-user

[nospam.nospam.nospam]

On Thu, 2009-11-05 at 14:45 +0100, Jean-Yves F. Barbier wrote:

> Benoît Minisini a écrit :
> ...
> > But if rebooting your Linux server does not make the application work again, I
> > can't really suspect Gambas, as it does not save anything on the hard disk,
> > especially the network component.
> >
> > Did you test the connection with telnet, or any other non-Gambas program? Did
> > you test another socket server application not made in Gambas?
> >
> > The only possibility I see would be a memory corruption in the network
> > component - it is possible, I didn't write it :-). By reading the source code
> > of the Listen() method, I didn't see anything that could lead to that. But I
> > will check again.
>
> May be a RAM is corrupted, running a full memtest86+ could reveal that
> (well @ least 2 tests: while physically swapping RAMs between tests in order
> to completely test low addresses of the 1st one)

Gawd! I've got 8Gig to test. I'll take the advice, just to make sure but
the problem has happened on two machines with the very same symptoms.
Thanks.


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Gambas-user mailing list
Gambas-user@...
https://lists.sourceforge.net/lists/listinfo/gambas-user

[Ron Klinkien]

Kad Mann wrote:

> On Thu, 2009-11-05 at 14:45 +0100, Jean-Yves F. Barbier wrote:
>  
>> Benoît Minisini a écrit :
>> ...
>>    
>>> But if rebooting your Linux server does not make the application work again, I
>>> can't really suspect Gambas, as it does not save anything on the hard disk,
>>> especially the network component.
>>>
>>> Did you test the connection with telnet, or any other non-Gambas program? Did
>>> you test another socket server application not made in Gambas?
>>>
>>> The only possibility I see would be a memory corruption in the network
>>> component - it is possible, I didn't write it :-). By reading the source code
>>> of the Listen() method, I didn't see anything that could lead to that. But I
>>> will check again.
>>>      
>> May be a RAM is corrupted, running a full memtest86+ could reveal that
>> (well @ least 2 tests: while physically swapping RAMs between tests in order
>> to completely test low addresses of the 1st one)
>>    
>
> Gawd! I've got 8Gig to test. I'll take the advice, just to make sure but
> the problem has happened on two machines with the very same symptoms.
> Thanks.
>
>  

Just thinking out loud maybe it helps.

You talked about a Windows machine at one end, maybe also check its
firewall and antivirus settings, if any.
I know for example Kaspersky 2010 sits between all the network
connections you have, maybe some strange pattern is seen as evil, and
the connection gets cut off in the middle. Check logs.

If you transfer lots of (other) network data, make sure your
switches/pcs/routers's network interfaces etc. are in the correct mode,
full duplex/duplex, lots of equipment doesn't negotiate mode correctly,
resulting in one device in half- and the switch in full duplex for
example, it seems to work, but not 100%... you get network errors, and
strange behavior.

I couldn't see if you are running on 64 Bits Linux, I have had many
occasions of problems at the startup of my project, some times my
project started 30 times in a row without any problem and the 31th time
bingo! It made me nuts back then... It had to do with memory space
Gambas was loaded in, if it was in 64Bit memory space, it was unstable.  
(those bugs are fixed by Benoit so don't worry)
Just to illustrate that sometimes you oversee something obvious at
first, and you point at the wrong code just because you don't know where
to look.

My 2 cents.

Regards,
Ron_2nd.

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Gambas-user mailing list
Gambas-user@...
https://lists.sourceforge.net/lists/listinfo/gambas-user

[Jean-Yves F. Barbier-2]

Ron a écrit :

> Kad Mann wrote:
>> On Thu, 2009-11-05 at 14:45 +0100, Jean-Yves F. Barbier wrote:
>>  
>>> Benoît Minisini a écrit :
>>> ...
>>>    
>>>> But if rebooting your Linux server does not make the application work again, I
>>>> can't really suspect Gambas, as it does not save anything on the hard disk,
>>>> especially the network component.
>>>>
>>>> Did you test the connection with telnet, or any other non-Gambas program? Did
>>>> you test another socket server application not made in Gambas?
>>>>
>>>> The only possibility I see would be a memory corruption in the network
>>>> component - it is possible, I didn't write it :-). By reading the source code
>>>> of the Listen() method, I didn't see anything that could lead to that. But I
>>>> will check again.
>>>>      
>>> May be a RAM is corrupted, running a full memtest86+ could reveal that
>>> (well @ least 2 tests: while physically swapping RAMs between tests in order
>>> to completely test low addresses of the 1st one)
>>>    
>> Gawd! I've got 8Gig to test. I'll take the advice, just to make sure but
>> the problem has happened on two machines with the very same symptoms.
>> Thanks.
>>
>>  
> Just thinking out loud maybe it helps.
>
> You talked about a Windows machine at one end, maybe also check its
> firewall and antivirus settings, if any.
> I know for example Kaspersky 2010 sits between all the network
> connections you have, maybe some strange pattern is seen as evil, and
> the connection gets cut off in the middle. Check logs.

Yeah, absolutely right.

Moreover, back in 2001, norton antivirus clobbered the network (10Mb)
down from 780KB/s to 140KB/s even after uninstallation (!)

--
I'd love to kiss you, but I just washed my hair.
                -- Bette Davis, "Cabin in the Cotton"

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Gambas-user mailing list
Gambas-user@...
https://lists.sourceforge.net/lists/listinfo/gambas-user

[nospam.nospam.nospam]

On Fri, 2009-11-06 at 08:37 +0100, Ron wrote:

> Kad Mann wrote:
> > On Thu, 2009-11-05 at 14:45 +0100, Jean-Yves F. Barbier wrote:
> >  
> >> Benoît Minisini a écrit :
> >> ...
> >>    
> >>> But if rebooting your Linux server does not make the application work again, I
> >>> can't really suspect Gambas, as it does not save anything on the hard disk,
> >>> especially the network component.
> >>>
> >>> Did you test the connection with telnet, or any other non-Gambas program? Did
> >>> you test another socket server application not made in Gambas?
> >>>
> >>> The only possibility I see would be a memory corruption in the network
> >>> component - it is possible, I didn't write it :-). By reading the source code
> >>> of the Listen() method, I didn't see anything that could lead to that. But I
> >>> will check again.
> >>>      
> >> May be a RAM is corrupted, running a full memtest86+ could reveal that
> >> (well @ least 2 tests: while physically swapping RAMs between tests in order
> >> to completely test low addresses of the 1st one)
> >>    
> >
> > Gawd! I've got 8Gig to test. I'll take the advice, just to make sure but
> > the problem has happened on two machines with the very same symptoms.
> > Thanks.
> >
> >  
> Just thinking out loud maybe it helps.
>
> You talked about a Windows machine at one end, maybe also check its
> firewall and antivirus settings, if any.
> I know for example Kaspersky 2010 sits between all the network
> connections you have, maybe some strange pattern is seen as evil, and
> the connection gets cut off in the middle. Check logs.

I have the problem on linux and linux alone. Windows has nothing to do
with it.

> If you transfer lots of (other) network data, make sure your
> switches/pcs/routers's network interfaces etc. are in the correct mode,
> full duplex/duplex,

Well, that'll be a great help if I have only wireless. Nevertheless my
network is wired but the network is not the culprit either.

>  lots of equipment doesn't negotiate mode correctly,
> resulting in one device in half- and the switch in full duplex for
> example, it seems to work, but not 100%... you get network errors, and
> strange behavior.

Also nothing to do with it. The problem occurred first when a Windows
server was involved, however it has also happened since on a standalone
linux talking to itself on localhost. The second time I posted about the
problem I didn't mention Windows because Windows has been completely
eliminated from the equation.

> I couldn't see if you are running on 64 Bits Linux, I have had many
> occasions of problems at the startup of my project, some times my
> project started 30 times in a row without any problem and the 31th time
> bingo! It made me nuts back then... It had to do with memory space
> Gambas was loaded in, if it was in 64Bit memory space, it was unstable.  
> (those bugs are fixed by Benoit so don't worry)

It has happened on both x86 and x64, and I am using x64 right now.

> Just to illustrate that sometimes you oversee something obvious at
> first, and you point at the wrong code just because you don't know where
> to look.

Yes, true but I do know where not to look.

> My 2 cents.
>
> Regards,
> Ron_2nd.
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Gambas-user mailing list
> Gambas-user@...
> https://lists.sourceforge.net/lists/listinfo/gambas-user

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Gambas-user mailing list
Gambas-user@...
https://lists.sourceforge.net/lists/listinfo/gambas-user

[Jean-Yves F. Barbier-2]

Kad Mann a écrit :
...
>
> I have the problem on linux and linux alone. Windows has nothing to do
> with it.

windows might be disturbing the force...
...

> Also nothing to do with it. The problem occurred first when a Windows
> server was involved, however it has also happened since on a standalone
> linux talking to itself on localhost. The second time I posted about the

this points the code, as Benoît suggest, not the network

--

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Gambas-user mailing list
Gambas-user@...
https://lists.sourceforge.net/lists/listinfo/gambas-user

[Emil Tchekov-2]

-----Ursprüngliche Nachricht-----
Von: Jean-Yves F. Barbier [mailto:12ukwn@...]
Gesendet: Freitag, 6. November 2009 09:13
An: mailing list for gambas users
Betreff: Re: [Gambas-user]PING > Benoît (ServerSocket)


>Kad Mann a écrit :
>...
>>
>> I have the problem on linux and linux alone. Windows has nothing to do
>> with it.

>windows might be disturbing the force...


I do not want to start an new discussion about Windows, BUT

it is a FORCE disturbance... M$ went for year$ on the Dark $ide of the Force$...

As example - just check on FileZilla issues when talking with M$ FTP -> due to incorrect implementation of FTP protocol, after a break, the severs starts the transfer from the very beginning - results in corupted files (>100% filelength issue)...


So why should we expect any difference, it is always the same - as we say in Germany - M$ is "cooking his own soup" ...



best regards


Emil



------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Gambas-user mailing list
Gambas-user@...
https://lists.sourceforge.net/lists/listinfo/gambas-user

[Ron Klinkien]

Kad Mann wrote:

> On Fri, 2009-11-06 at 08:37 +0100, Ron wrote:
>  
>> Kad Mann wrote:
>>    
>>> On Thu, 2009-11-05 at 14:45 +0100, Jean-Yves F. Barbier wrote:
>>>  
>>>      
>>>> Benoît Minisini a écrit :
>>>> ...
>>>>    
>>>>        
>>>>> But if rebooting your Linux server does not make the application work again, I
>>>>> can't really suspect Gambas, as it does not save anything on the hard disk,
>>>>> especially the network component.
>>>>>
>>>>> Did you test the connection with telnet, or any other non-Gambas program? Did
>>>>> you test another socket server application not made in Gambas?
>>>>>
>>>>> The only possibility I see would be a memory corruption in the network
>>>>> component - it is possible, I didn't write it :-). By reading the source code
>>>>> of the Listen() method, I didn't see anything that could lead to that. But I
>>>>> will check again.
>>>>>      
>>>>>          
>>>> May be a RAM is corrupted, running a full memtest86+ could reveal that
>>>> (well @ least 2 tests: while physically swapping RAMs between tests in order
>>>> to completely test low addresses of the 1st one)
>>>>    
>>>>        
>>> Gawd! I've got 8Gig to test. I'll take the advice, just to make sure but
>>> the problem has happened on two machines with the very same symptoms.
>>> Thanks.
>>>
>>>  
>>>      
>> Just thinking out loud maybe it helps.
>>
>> You talked about a Windows machine at one end, maybe also check its
>> firewall and antivirus settings, if any.
>> I know for example Kaspersky 2010 sits between all the network
>> connections you have, maybe some strange pattern is seen as evil, and
>> the connection gets cut off in the middle. Check logs.
>>    
>
> I have the problem on linux and linux alone. Windows has nothing to do
> with it.
>
>  
>> If you transfer lots of (other) network data, make sure your
>> switches/pcs/routers's network interfaces etc. are in the correct mode,
>> full duplex/duplex,
>>    
>
> Well, that'll be a great help if I have only wireless. Nevertheless my
> network is wired but the network is not the culprit either.
>
>  
>>  lots of equipment doesn't negotiate mode correctly,
>> resulting in one device in half- and the switch in full duplex for
>> example, it seems to work, but not 100%... you get network errors, and
>> strange behavior.
>>    
>
> Also nothing to do with it. The problem occurred first when a Windows
> server was involved, however it has also happened since on a standalone
> linux talking to itself on localhost. The second time I posted about the
> problem I didn't mention Windows because Windows has been completely
> eliminated from the equation.
>
>  
>> I couldn't see if you are running on 64 Bits Linux, I have had many
>> occasions of problems at the startup of my project, some times my
>> project started 30 times in a row without any problem and the 31th time
>> bingo! It made me nuts back then... It had to do with memory space
>> Gambas was loaded in, if it was in 64Bit memory space, it was unstable.  
>> (those bugs are fixed by Benoit so don't worry)
>>    
>
> It has happened on both x86 and x64, and I am using x64 right now.
>
>  
>> Just to illustrate that sometimes you oversee something obvious at
>> first, and you point at the wrong code just because you don't know where
>> to look.
>>    
>
> Yes, true but I do know where not to look.
>
>  
>>    

Ok fair enough ...
Overlooked the linux-localhost part, so you're right we cannot point at
Bill.

Did you try to run valgrind tool already like Benoit suggested?
It has proven to be very helpful to catch bugs...
I had to run it several times in the past and although the output can be
massive it's worth the try.

Regards,
Ron_2nd.


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Gambas-user mailing list
Gambas-user@...
https://lists.sourceforge.net/lists/listinfo/gambas-user

[nospam.nospam.nospam]

On Fri, 2009-11-06 at 09:20 +0100, Ron wrote:

> Ok fair enough ...
> Overlooked the linux-localhost part, so you're right we cannot point at
> Bill.

lol

> Did you try to run valgrind tool already like Benoit suggested?

Not just yet. I've almost maxed out my bandwidth and still have a week
to go before it rolls over so I'm taking the downloading easy. I've made
a note to check it out.

> It has proven to be very helpful to catch bugs...
> I had to run it several times in the past and although the output can be
> massive it's worth the try.

Thanks, appreciated.


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Gambas-user mailing list
Gambas-user@...
https://lists.sourceforge.net/lists/listinfo/gambas-user