To use Naming Service...or not to use Naming Service?

That is my question.

I want to use clustering and load balancing on my jag servers, so I'm not
sure if I need to do this or if the connection object handles this "behind
the scenes".

In PB does the connection object use the nameservice to do this for you, or
do you have to use the JaguarORB.Resolve_Initial_References(), and narrow
everything down to the component to take advantage of this?  What is "the
best way" to instantiate Jag components in PB if you want clustering,
fail-over, and load balancing?

Thanks for any help.

Erik T.

0 Erik 6/25/2001 2:51:47 PM

The connection object will use the name service. I would say you only need
to use jaguarORB if you want to create the component on a given server in
the cluster. That is you want the component created on server 'A'.

--
Dean Jones TeamSybase
PowerTeam, Inc.
www.powerobjects.com
WebReport - Move your reports to the web!
Come visit our booth at TechWave
EAServer Seminar http://www.powerobjects.com/seminar


"Erik Toft"  wrote in message
news:HhnNRkY$AHA.194@forums.sybase.com...
> That is my question.
>
> I want to use clustering and load balancing on my jag servers, so I'm not
> sure if I need to do this or if the connection object handles this "behind
> the scenes".
>
> In PB does the connection object use the nameservice to do this for you,
or
> do you have to use the JaguarORB.Resolve_Initial_References(), and narrow
> everything down to the component to take advantage of this?  What is "the
> best way" to instantiate Jag components in PB if you want clustering,
> fail-over, and load balancing?
>
> Thanks for any help.
>
> Erik T.
>
>

0 Dean 6/25/2001 3:03:47 PM

Just initialise the conenction object with your name servers before
calling connectToServer().

The location string should be a semi-colon separated list of server
locations (e.g. "iiop://A:9000;iiop://B:9000")

All you need to do then is call connection.createinstance() from the PB
client.

A.

Erik Toft wrote:
> 
> That is my question.
> 
> I want to use clustering and load balancing on my jag servers, so I'm not
> sure if I need to do this or if the connection object handles this "behind
> the scenes".
> 
> In PB does the connection object use the nameservice to do this for you, or
> do you have to use the JaguarORB.Resolve_Initial_References(), and narrow
> everything down to the component to take advantage of this?  What is "the
> best way" to instantiate Jag components in PB if you want clustering,
> fail-over, and load balancing?
> 
> Thanks for any help.
> 
> Erik T.

-- 
__________________________

Adam Simmonds [TeamSybase]
System Architect
ITS FLEXSIS PROJECT
The University of Sydney
Phone:  +61 2 9351 5174
Mobile: +61 403 341 474
Fax:    +61 2 9351 7711

0 Adam 6/25/2001 3:14:22 PM

Thanks to both Dean and Adam.

I just wanted to be sure...I am re-writing a desktop application from java
(PowerJ) to PB.  So, since you have to use the Naming facilities when using
Java, I did not know if the same held for PB.

BTW the PB version of the app. took much less time to write, is much more
stable, and much faster than the PowerJ equivalent.  We thought the java
DataWindow was going to be great...our experience proved us wrong.  We have
ongoing memory leak problems...and we are pretty sure that we have narrowed
it down to the DW.  We have opened issues, and updated to the latest
software to no avail.  Moving back to PB on the client was our only
recourse...and a welcome one for me...long live PB!

Please NOTE that the java DataStore seems to be OK, and we are continuing
with our existing java Jaguar components.  We have good results with PB on
the client, and java on the server.  To the folks who want PB and Jaguar,
but want Linux for the Jaguar server, you may want to look into this
solution.  I am going to re-post this info for folks not interested in this
thread, but may like to know this.

Erik T.

"Erik Toft"  wrote in message
news:HhnNRkY$AHA.194@forums.sybase.com...
> That is my question.
>
> I want to use clustering and load balancing on my jag servers, so I'm not
> sure if I need to do this or if the connection object handles this "behind
> the scenes".
>
> In PB does the connection object use the nameservice to do this for you,
or
> do you have to use the JaguarORB.Resolve_Initial_References(), and narrow
> everything down to the component to take advantage of this?  What is "the
> best way" to instantiate Jag components in PB if you want clustering,
> fail-over, and load balancing?
>
> Thanks for any help.
>
> Erik T.
>
>

0 Erik 6/25/2001 3:47:48 PM

Erik,
Thanks for the info, I can use this to convince our project decision
makers that leaving the client PB is the way to go ( especially with the
skill level in PB/PFC ) and then if needed move PB server components to
Java.

>>long live PB!
Thanks for the positive attitude... PB has been getting a hammering
lately ;-)

A.

Erik Toft wrote:
> 
> Thanks to both Dean and Adam.
> 
> I just wanted to be sure...I am re-writing a desktop application from java
> (PowerJ) to PB.  So, since you have to use the Naming facilities when using
> Java, I did not know if the same held for PB.
> 
> BTW the PB version of the app. took much less time to write, is much more
> stable, and much faster than the PowerJ equivalent.  We thought the java
> DataWindow was going to be great...our experience proved us wrong.  We have
> ongoing memory leak problems...and we are pretty sure that we have narrowed
> it down to the DW.  We have opened issues, and updated to the latest
> software to no avail.  Moving back to PB on the client was our only
> recourse...and a welcome one for me...long live PB!
> 
> Please NOTE that the java DataStore seems to be OK, and we are continuing
> with our existing java Jaguar components.  We have good results with PB on
> the client, and java on the server.  To the folks who want PB and Jaguar,
> but want Linux for the Jaguar server, you may want to look into this
> solution.  I am going to re-post this info for folks not interested in this
> thread, but may like to know this.
> 
> Erik T.
> 
> "Erik Toft"  wrote in message
> news:HhnNRkY$AHA.194@forums.sybase.com...
> > That is my question.
> >
> > I want to use clustering and load balancing on my jag servers, so I'm not
> > sure if I need to do this or if the connection object handles this "behind
> > the scenes".
> >
> > In PB does the connection object use the nameservice to do this for you,
> or
> > do you have to use the JaguarORB.Resolve_Initial_References(), and narrow
> > everything down to the component to take advantage of this?  What is "the
> > best way" to instantiate Jag components in PB if you want clustering,
> > fail-over, and load balancing?
> >
> > Thanks for any help.
> >
> > Erik T.
> >
> >

-- 
__________________________

Adam Simmonds [TeamSybase]
System Architect
ITS FLEXSIS PROJECT
The University of Sydney
Phone:  +61 2 9351 5174
Mobile: +61 403 341 474
Fax:    +61 2 9351 7711

0 Adam 6/25/2001 3:49:32 PM

I'll tell you what.  I tried to like java.  I have tried really hard to.
But I just can't.  I'm not saying that it is a bad language, but it sure
doesn't meet up to the hype.  If I want or need to write code the hard way
(grin) I will go with MFC and C or C++.  Java's lack of performance erases
any gains made in ease of use or ease of learning (actually there aren't
many).  PowerJ has been problematic in and of itself, and that just added to
my frusteration.  We decided on PowerJ to get the Jaguar integration, and
the DataWindow tech. so that we could leverage a bit of what we have learned
in PB over the years...it paid off a bit, but then we ran in to some serious
memory growth (aka leaks) when using the java DW.

We are trying to build applications...not applets.  These apps are monitor
applications that may need to be up and working for many hours...even days
without failing...all the time filling with data which is appended to the
bottom rows of a datawindow which scrolls bottom to top <-- yes that *was* a
trick in java!  The java datawindow would just chew through the heap till it
depleated it, and then start whining about being out of memory.  Sure we
understand that, so we begin to monitor the number of rows in the DW, and
discard the oldest...guess what?  No change.  It did not matter what we did
to discard the data, call the GC, destroy references, etc. the memory was
not freeing up.  As we experimented we dwindled our test app down to just a
datawindow and some controls to initiate actions on our jag components.
After just a few fetches, we can cause memory errors to scroll up the
console window...the official answer...increase your virtual memory which
was already set to 600MB.  We gave up and re-built in PB.

Though the app is not complete yet, we are seeing much better performance in
memory and a very niticable increase in response times...especially on calls
to jag components.

We are not throwing the baby out with the bath water yet.  In an odd twist
of fate, it seems that the PowerJ datastore does not suffer from the same
memory afflictions as does the DW...at least not that we can see.  We have a
very stable datastore based service component running in Jaguar that is
constantly retrieving and dumping data...no mem leak there.  Saves us a good
cunk of work...WHEW!

I'm only relating our observations and experience, but maybe this will give
you more to go to your boss with, and/or research on your own.  Good luck.

Erik T.


"Adam Simmonds [TeamSybase]"  wrote in message
news:3B375D8C.BF68A384@mail.usyd.edu.au...
> Erik,
> Thanks for the info, I can use this to convince our project decision
> makers that leaving the client PB is the way to go ( especially with the
> skill level in PB/PFC ) and then if needed move PB server components to
> Java.
>
> >>long live PB!
> Thanks for the positive attitude... PB has been getting a hammering
> lately ;-)
>
> A.
>
> Erik Toft wrote:
> >
> > Thanks to both Dean and Adam.
> >
> > I just wanted to be sure...I am re-writing a desktop application from
java
> > (PowerJ) to PB.  So, since you have to use the Naming facilities when
using
> > Java, I did not know if the same held for PB.
> >
> > BTW the PB version of the app. took much less time to write, is much
more
> > stable, and much faster than the PowerJ equivalent.  We thought the java
> > DataWindow was going to be great...our experience proved us wrong.  We
have
> > ongoing memory leak problems...and we are pretty sure that we have
narrowed
> > it down to the DW.  We have opened issues, and updated to the latest
> > software to no avail.  Moving back to PB on the client was our only
> > recourse...and a welcome one for me...long live PB!
> >
> > Please NOTE that the java DataStore seems to be OK, and we are
continuing
> > with our existing java Jaguar components.  We have good results with PB
on
> > the client, and java on the server.  To the folks who want PB and
Jaguar,
> > but want Linux for the Jaguar server, you may want to look into this
> > solution.  I am going to re-post this info for folks not interested in
this
> > thread, but may like to know this.
> >
> > Erik T.
> >
> > "Erik Toft"  wrote in message
> > news:HhnNRkY$AHA.194@forums.sybase.com...
> > > That is my question.
> > >
> > > I want to use clustering and load balancing on my jag servers, so I'm
not
> > > sure if I need to do this or if the connection object handles this
"behind
> > > the scenes".
> > >
> > > In PB does the connection object use the nameservice to do this for
you,
> > or
> > > do you have to use the JaguarORB.Resolve_Initial_References(), and
narrow
> > > everything down to the component to take advantage of this?  What is
"the
> > > best way" to instantiate Jag components in PB if you want clustering,
> > > fail-over, and load balancing?
> > >
> > > Thanks for any help.
> > >
> > > Erik T.
> > >
> > >
>
> --
> __________________________
>
> Adam Simmonds [TeamSybase]
> System Architect
> ITS FLEXSIS PROJECT
> The University of Sydney
> Phone:  +61 2 9351 5174
> Mobile: +61 403 341 474
> Fax:    +61 2 9351 7711

0 Erik 6/25/2001 6:35:55 PM

>>I'm only relating our observations and experience, but maybe this will give
>>you more to go to your boss with, and/or research on your own.  Good luck.
From my knowledge you are the first to step up and say this about Java and
PowerJ in particular so it makes my ranting and raving about not going Java
justifed ( at least in the present climate! ) I hope with the exception handling
in PB ( and maybe some more enhancements ) that PB may well be the best way to
go and just use java/powerj for the nonvisual tasks on the server if required.
A.

Erik Toft wrote:

> I'll tell you what.  I tried to like java.  I have tried really hard to.
> But I just can't.  I'm not saying that it is a bad language, but it sure
> doesn't meet up to the hype.  If I want or need to write code the hard way
> (grin) I will go with MFC and C or C++.  Java's lack of performance erases
> any gains made in ease of use or ease of learning (actually there aren't
> many).  PowerJ has been problematic in and of itself, and that just added to
> my frusteration.  We decided on PowerJ to get the Jaguar integration, and
> the DataWindow tech. so that we could leverage a bit of what we have learned
> in PB over the years...it paid off a bit, but then we ran in to some serious
> memory growth (aka leaks) when using the java DW.
>
> We are trying to build applications...not applets.  These apps are monitor
> applications that may need to be up and working for many hours...even days
> without failing...all the time filling with data which is appended to the
> bottom rows of a datawindow which scrolls bottom to top <-- yes that *was* a
> trick in java!  The java datawindow would just chew through the heap till it
> depleated it, and then start whining about being out of memory.  Sure we
> understand that, so we begin to monitor the number of rows in the DW, and
> discard the oldest...guess what?  No change.  It did not matter what we did
> to discard the data, call the GC, destroy references, etc. the memory was
> not freeing up.  As we experimented we dwindled our test app down to just a
> datawindow and some controls to initiate actions on our jag components.
> After just a few fetches, we can cause memory errors to scroll up the
> console window...the official answer...increase your virtual memory which
> was already set to 600MB.  We gave up and re-built in PB.
>
> Though the app is not complete yet, we are seeing much better performance in
> memory and a very niticable increase in response times...especially on calls
> to jag components.
>
> We are not throwing the baby out with the bath water yet.  In an odd twist
> of fate, it seems that the PowerJ datastore does not suffer from the same
> memory afflictions as does the DW...at least not that we can see.  We have a
> very stable datastore based service component running in Jaguar that is
> constantly retrieving and dumping data...no mem leak there.  Saves us a good
> cunk of work...WHEW!
>
> I'm only relating our observations and experience, but maybe this will give
> you more to go to your boss with, and/or research on your own.  Good luck.
>
> Erik T.
>
> "Adam Simmonds [TeamSybase]"  wrote in message
> news:3B375D8C.BF68A384@mail.usyd.edu.au...
> > Erik,
> > Thanks for the info, I can use this to convince our project decision
> > makers that leaving the client PB is the way to go ( especially with the
> > skill level in PB/PFC ) and then if needed move PB server components to
> > Java.
> >
> > >>long live PB!
> > Thanks for the positive attitude... PB has been getting a hammering
> > lately ;-)
> >
> > A.
> >
> > Erik Toft wrote:
> > >
> > > Thanks to both Dean and Adam.
> > >
> > > I just wanted to be sure...I am re-writing a desktop application from
> java
> > > (PowerJ) to PB.  So, since you have to use the Naming facilities when
> using
> > > Java, I did not know if the same held for PB.
> > >
> > > BTW the PB version of the app. took much less time to write, is much
> more
> > > stable, and much faster than the PowerJ equivalent.  We thought the java
> > > DataWindow was going to be great...our experience proved us wrong.  We
> have
> > > ongoing memory leak problems...and we are pretty sure that we have
> narrowed
> > > it down to the DW.  We have opened issues, and updated to the latest
> > > software to no avail.  Moving back to PB on the client was our only
> > > recourse...and a welcome one for me...long live PB!
> > >
> > > Please NOTE that the java DataStore seems to be OK, and we are
> continuing
> > > with our existing java Jaguar components.  We have good results with PB
> on
> > > the client, and java on the server.  To the folks who want PB and
> Jaguar,
> > > but want Linux for the Jaguar server, you may want to look into this
> > > solution.  I am going to re-post this info for folks not interested in
> this
> > > thread, but may like to know this.
> > >
> > > Erik T.
> > >
> > > "Erik Toft"  wrote in message
> > > news:HhnNRkY$AHA.194@forums.sybase.com...
> > > > That is my question.
> > > >
> > > > I want to use clustering and load balancing on my jag servers, so I'm
> not
> > > > sure if I need to do this or if the connection object handles this
> "behind
> > > > the scenes".
> > > >
> > > > In PB does the connection object use the nameservice to do this for
> you,
> > > or
> > > > do you have to use the JaguarORB.Resolve_Initial_References(), and
> narrow
> > > > everything down to the component to take advantage of this?  What is
> "the
> > > > best way" to instantiate Jag components in PB if you want clustering,
> > > > fail-over, and load balancing?
> > > >
> > > > Thanks for any help.
> > > >
> > > > Erik T.
> > > >
> > > >
> >
> > --
> > __________________________
> >
> > Adam Simmonds [TeamSybase]
> > System Architect
> > ITS FLEXSIS PROJECT
> > The University of Sydney
> > Phone:  +61 2 9351 5174
> > Mobile: +61 403 341 474
> > Fax:    +61 2 9351 7711

--
__________________________

Adam Simmonds [TeamSybase]
System Architect
ITS FLEXSIS PROJECT
The University of Sydney
Phone:  +61 2 9351 5174
Mobile: +61 403 341 474
Fax:    +61 2 9351 7711

0 Adam 6/26/2001 4:44:07 AM