Helen Borrie wrote:

>
> Relying on JS to step in and clarify...but, as I understand, the superserver version doesn't scale well and you get a "see-saw" effect as bunches of threads get swapped back and forth between the CPUs. If InterServer isn't threaded, then my shot in the dark could very well be astray. The problem is with SS on any platform and it doesn't exist with Classic, AFAIK.
>

Ok I am using Classic ONLY.

>
> >b) Does "IB problems on SMP" mean that Interclient/Interserver on a machine not running the database itself
> >could be affected?
>
> I haven't heard that the problem affects clients and don't know why it would. I don't understand what you mean by "InterServer on a machine not running the database itself". Are you saying that you are running the server on one machine and physically storing the database on another? Pardon my ignorance about InterServer - so far I've assumed it's a Java version of IBServer that would be subject to the same physical restrictions but I could be way off mark on that.
>

Machine A
Interclient java protion used by connectionpool
Java programs(web apps) using the connections
Interserver responding to requests made by interclient on same machine
Request from interclient are requesting a database not on local machine so interserver connects remote server

Machine B
IB 6.01 Classic


I am running interclient java portion connecting to a local interserver on machine A.
Interserver on machine A connects to the actual Interbase server on machine B which is on another subnet
via portforwarding. I don't think portforwarding is the problem since putting machine on same subnet
produce the same result.

>
> >c) How do I set the affinity?
>
> There's a freeware utility for Windows, written by (I think) Martijn Tonies. http://www.ibobjects.com/ib_affinity.zip
>

And with linux ...........?

>
> YES. The etiology is ..well... very similar to what you described but the dropouts in this case were random and affected active and idle connections indiscriminately. Hope that it is configuration problem because identifying and eliminating faults in the network is hell, especially if you bought a bad batch of something, where some might be OK and some might be bad.
>

Thanks!
//OLAS

>
> Cheers,
> Helen
>
> All for Open and Open for All
> InterBase Developer Initiative · http://www.interbase2000.org
> _______________________________________________________
>
>
> To unsubscribe from this group, send an email to:
> IB-Java-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/