Hello,

I start a Server.exe and a Client.exe which run on the same computer. 
Sometimes the server quits without message, but there are a 
xppfatal.log. It happens only sometimes and random.
I tested the server.exe and the client.exe on a second computer where 
happens the same.
Did anybody have an idea why this happens? I have added two xppfatal.log.

Christin




1.--- xppfatal.log -------------------------------------
FATAL ERROR LOG
Error within the error handling!
SYS Thread-ID: 1136
Module: EXE
Error Codes: EH: 1005 Sub: 0(0) OS: 0 XPP: 15
Call Stack of Thread 1 (1648):
MAIN(134)
Call Stack of Thread 2 (1176):
__CHECKSCROLLSTATE(96)
Call Stack of Thread 3 (1136):
@USRCOM@I@SEND(219)
@GRUPPE@I@LESEN(361)
@ZYLINDER@I@READ(260)
COMZYK(19)
Call Stack of Thread 4 (1108):
COMSL(45)
Call Stack of Thread 5 (1076):
STANDARDEH(139)
(B)ERRORSYS@0000(52)
WDISPBEGIN(1254)
WSELECT(486)
@MYSERVERTASK@I@EXECUTE(266)
Call Stack of Thread 6 (1044):
@SERVERTHREAD@I@EXECUTE(73)
Call Stack of Thread 7 (904):
@CLIENTTASK@I@EXECUTE(157)
Call Stack of Thread 8 (844):
STANDARDEH(139)
(B)ERRORSYS@0000(52)
@CLIENTTASK@I@EXECUTE(154)
Call Stack of Thread 9 (796):
STANDARDEH(139)
(B)ERRORSYS@0000(52)
@CLIENTTASK@I@EXECUTE(154)
Call Stack of Thread 11 (700):
STANDARDEH(136)
(B)ERRORSYS@0000(52)
@CLIENTTASK@I@EXECUTE(154)
Call Stack of Thread 12 (664):
STANDARDEH(139)
(B)ERRORSYS@0000(52)
@CLIENTTASK@I@EXECUTE(154)
File: C:\BVG_DGS\Server\SERVER.EXE
TimeStamp: 20060816 11:52
End of FATAL ERROR LOG.


2.--- xppfatal.log -------------------------------------
FATAL ERROR LOG
Not recoverable Error!
SYS Thread-ID: 1076
Module: MOM
Error Codes: EH: 1005 Sub: 0(0) OS: 0 XPP: 15
Call Stack of Thread 1 (1648):
MAIN(134)
Call Stack of Thread 2 (1176):
__CHECKSCROLLSTATE(96)
Call Stack of Thread 3 (1136):
@USRCOM@I@SEND(183)
@GRUPPE@I@LESEN(361)
@RADKRAFT@I@READ(150)
COMZYK(19)
Call Stack of Thread 4 (1108):
COMSL(59)
Call Stack of Thread 5 (1076):
ERRORMESSAGE(263)
STANDARDEH(109)
(B)ERRORSYS@0000(52)
WDISPBEGIN(1254)
WSELECT(486)
@MYSERVERTASK@I@EXECUTE(266)
Call Stack of Thread 6 (1044):
@SERVERTHREAD@I@EXECUTE(73)
Call Stack of Thread 7 (904):
@CLIENTTASK@I@EXECUTE(157)
Call Stack of Thread 8 (848):
@CLIENTTASK@I@EXECUTE(157)
Call Stack of Thread 9 (796):
@CLIENTTASK@I@EXECUTE(157)
Call Stack of Thread 10 (748):
@CLIENTTASK@I@EXECUTE(157)
File: C:\BVG_DGS\Server\SERVER.EXE
TimeStamp: 20060818 11:00
End of FATAL ERROR LOG.
-----------------------------------------

Christin,


> Hello,
> 
> I start a Server.exe and a Client.exe which run on the same computer. 
> Sometimes the server quits without message, but there are a 
> xppfatal.log. It happens only sometimes and random.
> I tested the server.exe and the client.exe on a second computer where 
> happens the same.
> Did anybody have an idea why this happens? I have added two xppfatal.log.

> FATAL ERROR LOG
> Error within the error handling!
> SYS Thread-ID: 1136

Look for a thread witha sysid of 1136.

Here it is...
> Call Stack of Thread 3 (1136):
> @USRCOM@I@SEND(219)
> @GRUPPE@I@LESEN(361)
> @ZYLINDER@I@READ(260)
> COMZYK(19)

I'm not sure what that line of code does, but I suspect that your socket,
pipe or whatever is broken.

Regards,

Phil Ide

-----------------------------------------------------------------
xbHCL (http://www.xbHCL.com)     Xbase++ HTML command layer
PBIH  (http://www.pbih.eu)       Polar Bear International Hosting
-----------------------------------------------------------------
Xbase++ FAQ, Libraries and Sources:
http://www.idep.org.uk/xbase

Why are there interstate highways in Hawaii?

hi,

> 1.--- xppfatal.log -------------------------------------
> FATAL ERROR LOG
> Error within the error handling!
> SYS Thread-ID: 1136
> Module: EXE
> Error Codes: EH: 1005 Sub: 0(0) OS: 0 XPP: 15

EXE     = Expression Executer
          * XppFatal Message: "Error within the error handling!"
            - Error Codes: "EH: 5"/"Sub: -1073741819(c0000005)"/"XPP: 41"
            - Error Codes: "EH: 1005"/"XPP: 15"

> Call Stack of Thread 1 (1648):
> MAIN(134)
> Call Stack of Thread 2 (1176):
> __CHECKSCROLLSTATE(96)
> Call Stack of Thread 3 (1136):

Error in Thread 3 Line 1136

 > 2.--- xppfatal.log -------------------------------------
> FATAL ERROR LOG
> Not recoverable Error!
> SYS Thread-ID: 1076
> Module: MOM
> Error Codes: EH: 1005 Sub: 0(0) OS: 0 XPP: 15

MOM     = Memory Object Manager
          * XppFatal Message: (none)
            - Error Codes: "EH: 1003"/"XPP: 0"

> Call Stack of Thread 5 (1076):

Error in Thread 5 Line 1076

while both have Error XPP : 15

15     XPP_ERR_MEMORY_FULL  Not enough memory or swapping space available.

it seems to be a Memory (or roghts) Problem

greetings by OHR
Jimmy

Jimmy,
the number 1136 is not a line number but the Thread-ID!!
As you can see at the beginning of the log there is a line saying that there 
was an error within the error handling in the SYS Thread-ID: 1136!
Later on you will find thread number three (which has the thread-ID 1136 and 
therefore is the culprit) indicating the error within line 219: 
@USRCOM@I@SEND(219)
The same goes with the second log.

Regards,
Martin

______________________________

Deutschsprachiges Xbase-Forum:
http://www.xbaseforum.de/
______________________________

hi,

> the number 1136 is not a line number but the Thread-ID!!
> As you can see at the beginning of the log there is a line saying that
there
> was an error within the error handling in the SYS Thread-ID: 1136!
> Later on you will find thread number three (which has the thread-ID 1136
and
> therefore is the culprit) indicating the error within line 219:
> @USRCOM@I@SEND(219)
> The same goes with the second log.

yes shure you are right, it is the line after Thread-ID .

greetings by OHR
Jimmy

Hello,

I find the problem. It seems to be a memory problem.
I start the server.exe and the client.exe again. I used the tool 
"ProcessExplorer" and I see that the server increases the memory
used every time the client request a record. I tested it on a Computer 
with windows XP.
The same procedure I testet on windows 2000 and there is no memory 
problem. The memory remain constant.
Did anybody have an idea why the memory increase on windows xp and not 
on windows 2000. Is there a difference in memory usage?

Christin

Christin Paulick,

> I find the problem. It seems to be a memory problem.
> I start the server.exe and the client.exe again. I used the tool 
> "ProcessExplorer" and I see that the server increases the memory
> used every time the client request a record. I tested it on a Computer 
> with windows XP.
> The same procedure I testet on windows 2000 and there is no memory 
> problem. The memory remain constant.
> Did anybody have an idea why the memory increase on windows xp and not 
> on windows 2000. Is there a difference in memory usage?

I don't know, but as Xbase++ reuses thread numbers once the threads are 
released, your app seems to keep the threads alive some way. Yoy might want 
to look into this and perhaps find the reason why your memory increases.
Link in memwatch. It's a beautiful tool.

Peter

Now I know why the memory increase. I have one client and one server. 
The client establish two connections to the server. Over the first 
connection I demand information continuously and over the second 
connection I demand information rarely.
The memory allways increases when no data are transmitted over the 
second connection. As soon as data were transmitted then the memory 
decrease.

Peter Alderliesten schrieb:
> Christin Paulick,
> 
> 
>>I find the problem. It seems to be a memory problem.
>>I start the server.exe and the client.exe again. I used the tool 
>>"ProcessExplorer" and I see that the server increases the memory
>>used every time the client request a record. I tested it on a Computer 
>>with windows XP.
>>The same procedure I testet on windows 2000 and there is no memory 
>>problem. The memory remain constant.
>>Did anybody have an idea why the memory increase on windows xp and not 
>>on windows 2000. Is there a difference in memory usage?
> 
> 
> I don't know, but as Xbase++ reuses thread numbers once the threads are 
> released, your app seems to keep the threads alive some way. Yoy might want 
> to look into this and perhaps find the reason why your memory increases.
> Link in memwatch. It's a beautiful tool.
> 
> Peter