[Vortex] Problem when calling vortex_connection_close

[Robert M. Münch]

On Mon, 28 Apr 2008 15:28:20 +0200, Francis Brosnan Blazquez  
<francis at aspl.es> wrote:

> ..it's odd; looks like a format problem rather a pointer issue because
> the printf format %d do not produce ??? (or at least it's first time I
> see it)...

Hi, sorry the ??? was just a placeholder from my side. Here is a snippet  
of the log-output. Does this help? I don't understand the number of  
"connection=" and "channel=" because I expected the output to show the  
vortex IDs.

[1880] we still didn't sent replies for connection=3208816  
channel=3208768, block until all replies are sent (RPY 268465751 != MSG  
268702552)
[1880] called vortex_cond_timedwait from :3208776
[1880] SignalObjectAndWait finished, because:  
´>´>´>0@tÔL[èö0ƒÄéÃvortex-thread
[1880] finished vortex_cond_timedwait (result: 3208788) from @ö0:268465751
[1880] we still didn't sent replies for connection=3208816  
channel=3208768, block until all replies are sent (RPY 268465751 != MSG  
268702552)
[1880] called vortex_cond_timedwait from :3208776
[1880] SignalObjectAndWait finished, because:  
´>´>´>0@tÔL[èö0ƒÄéÃvortex-thread
[1880] finished vortex_cond_timedwait (result: 3208788) from @ö0:268465751
[1880] we still didn't sent replies for connection=3208816  
channel=3208768, block until all replies are sent (RPY 268465751 != MSG  
268702552)
[1880] called vortex_cond_timedwait from :3208776
[1880] SignalObjectAndWait finished, because:  
´>´>´>0@tÔL[èö0ƒÄéÃvortex-thread
[1880] finished vortex_cond_timedwait (result: 3208788) from @ö0:268465751
[1880] we still didn't sent replies for connection=3208816  
channel=3208768, block until all replies are sent (RPY 268465751 != MSG  
268702552)
[1880] called vortex_cond_timedwait from :3208776

> Fix the format problem or check channel status just before calling to
> vortex_connection_close.

I will add a loop to check all channels.

> If you don't want to wait on close you can also use
> vortex_connection_shutdown avoiding to get locked if a channel have
> pending replies.

I just tried this but I still get the debug output above and my client  
hangs... That's really strange. Robert