[JDEV] Jabber server on HPUX

[Brennan, James]

Hi Rick,

Yes - that's exactly what I experienced!

Although, as you say, pth compiles fine, it's actually
the get/set/swapcontext() methods that it uses.

I found that pth just stopped 'switching' to other threads,
grinds to a halt, takes up 100%cpu and doesn't get to spawn
the other jabber process.

I traced it down to get/set/swapcontext() in the pth.
You can force pth to use sigsetjmp/siglongjump instead
and the way you do this is with the ./configure switches
that I describe in my email at the end.

james

Logica Mobile Networks,
Dublin, Ireland.

-----Original Message-----
From: Rick Hickerson [mailto:richard_hickerson at agilent.com]
Sent: Wednesday, November 28, 2001 7:51 PM
To: jdev at jabber.org
Subject: Re: [JDEV] Jabber server on HPUX


I get it compiled OK with pth-1.4.0, and can execute:
./jabberd/jabberd -D -h <my.fully.qualified.hostname>

But there everything stops. `top` shows jabberd as using 100% of one of the
CPUs, and any attempt to connect to port 5222 is refused.  

When running in the foreground, one message comes to the console:
Wed Nov 28 13:32:59 2001  mio.c:568 MIO is starting up

It doesn't respond to <ctrl>-c.  I have to login another session and `kill
-9`
to shut it down.

Rick

"Brennan, James" wrote:
> 
> I think this is the same problem that I had.
> The problem is the pth component which jabber uses.
> This is the thread component part.
> 
> You will find this component in the directory:
> jabberd/pth-1.3.7  (I use pth-1.4.0 but this should not matter)
> 
> You need to enter this directory and run configure with
> the following flags:
> 
> ./configure --with-mctx-mth=sjlj --with-mctx-dsp=sjlj --with-mctx-stk=sas
> 
> You then need to build the pth component.
> Just run make in the pth-1.3.7 directory.
> 
> Then go back out to the jabber directory and make the system.
> 
> Get in touch with me if this doesn't make sense or work.
> 
> james

This e-mail and any attachment is for authorised use by the intended recipient(s) only.  It may contain proprietary material, confidential information and/or be subject to legal privilege.  It should not be copied, disclosed to, retained or used by, any other party.  If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender.  Thank you.