RE: Can I stop the "Attempting to Rebind" after EnvMgr goesAWOL ...

Question

You might want to export the Environment definition and
use it to restore the Environment when you restart( after the
environment manager dies ungracefully ).
Ajith Kallambella. M
Forte Systems Engineer,
International Business Corporation
-----Original Message-----
From: Haben, Dirk [mailto:[email protected]]
Sent: Tuesday, December 29, 1998 1:47 AM
To: 'Soapbox Forte Users'
Subject: Can I stop the "Attempting to Rebind" after EnvMgr goes AWOL
Hi All.
In the last few weeks I have had the Environment Manager (for development)
go AWOL in as many weeks.
During a restart - after cleaning up (stop/id) all other Forte processes - I
run into virtual memory limitations - and the restart fails.
A larger virtual memory quota (doubling the pagefile quota actually) did the
trick.
However the quota is too large to be kept and I have reverted to 400,000
blocks (OpenVMS talk for about 200MB).
The problem appears to be caused by all this attempted rebinding.
"With Forte Release 3, this rebinding process is asynchronous" (see
TN11537).
Q: Can I disable the attempted rebind so to reduce memory needs on a restart
after the EnvMgr goes AWOL?
Supplementary Q: If so - How?
TIA and Seasons Greetings,
Dirk
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Answer 1

Hi,
We usually do a shutdown on the topmost level using escript. I assume that
will shutdown all installed partitions and the environment. Or did I get it
wrong that we have to shutdown application first that the environment?
Regards,
Peter Sham.
-----Original Message-----
From: Daniel Nguyen [SMTP:[email protected]]
Sent: Tuesday, January 05, 1999 6:38 PM
To: Peter Sham (HTHK - Assistant Manager - Software Development,
IITB)
Cc: [email protected]
Subject: Re: Can I stop the "Attempting to Rebind" after
EnvMgr goes AWOL ...
Hi,
Sorry, I don't have that kind of problem. Are you doing your
shutdown
on the application level from EConsole ? Do you shutdown your
application
before shutting down the environment ? Do you have the same symptom
after
having rebuilt your environment repository ?
The best I could say is still to make an export of the environment
on
your exploitation procedures (every day for instance) and to restart
your environment from this export. I presume that you still have
referenced
links in your environment repository which are not available. Until
you
make a clean Environement repository from an edf file you may have
the
problem.
Hope this helps,
Daniel Nguyen
Freelance Forte Consultant
Peter Sham (HTHK - Assistant Manager - Software Development, IITB)
wrote:
>
> Hi,
>
> The problem that I described happened not only after crashes but
also after
> clean shutdown. Observe your <hostname>.log and you will find
that each
> time after startup, there is a large chunk of message saying
"rebinding".
> When system crashes, this rebinding will disturb normally
operation too.
>
> Regards,
> Peter Sham.
>
> -----Original Message-----
> From: Daniel Nguyen [SMTP:[email protected]]
> Sent: Monday, January 04, 1999 8:58 PM
> To: Haben, Dirk; [email protected]
> Subject: Re: Can I stop the "Attempting to Rebind"
after
> EnvMgr goes AWOL ...
>
> Hi,
>
> The restart of your application is not exactly the problem
> the rebind is linked to the restart of your environment.
> If you want your application to restart, you should use
the
> autostart. Problem : if you are using load balancing, you
should
> restart
> as Degraded (with only one replicate). But, the main
problem seams
> to
> be your application. The partitions should not fall. You
may have
> some
> classes or attributes which are used but not instanciated.
This
> should
> causes a segmentation error and a crash of your partition.
This
> symptom
> is not the same if you are running on interpreted mode
(you will
> only
> receive a NIL object Usage Exception). Be aware that, on
the
> developement
> workshop, Arrays are instanciated automatically. This is
not true if
> you
> are distributed.
> On the application I worked on, this caused 150 autostarts
a day
> before
> resolution and an increase of the environment repository
up to 6 Mo.
> To avoid the crash of your environment, you should use -fm
to
> reserve
> enough memory (we used 60 Mo of memory for a standard
environment).
> You should not use the same environement for production
and
> compilation
> which needs much more memory if you use auto-compile, or
make your
> compilations with FCompile directly on the compilation
server.
> Normally the application (if it's already startded) should
not need
> the
> environment. You can stop the environment, your
application should
> still
> run, but new clients should not be able to attach to
partitions. It
> is
> a way to be sure that no new clients are connecting to the
> application,
> if you can be sure that all the proxies are already
resolved.
> The rebind is made to reconnect the environment to clients
and
> partitions,
> but I didn't see a real difference on instruments using
rebind or
> not.
> Rebind success is when your partitions or clients are
still there
> (with
> the same UUID). On a shutdown, your server partitions are
rebuilt,
> so
> it should not be successfull. Same case if the clients
stop their
> client partition.
>
> Hope this helps,
>
> Daniel Nguyen
> Freelance Forte Consultant
>
> Haben, Dirk wrote:
> >
> > I agree with Peter.
> >
> > My reason to stop the rebind in the first place is to be
able to
> have my
> > weekends etc to myself - so the application must restart
without
> manual
> > interference!
> >
> > Has anyone ever seen a rebind succeed? Was it worth it?
> >
> > Cheers,
> > Dirk
> >
> > -----Original Message-----
> > From: Peter Sham (HTHK - Assistant Manager - Software
Development,
> IITB)
> > [mailto:[email protected]]
> > Sent: Monday, 4 January 1999 11:09
> > To: Kallambella, Ajith; 'Haben, Dirk'
> > Cc: 'Forte'
> > Subject: RE: Can I stop the "Attempting to Rebind" after
EnvMgr
> goes
> > AWOL ...
> >
> > Hi,
> >
> > By restoring the environment from export will clean up
and skip
> any
> > "rebind". However, I would query that ... Is it
feasible in an
> production
> > environment. When the system is down, we have to put it
back
> asap.
> > Restoring the environment takes time and, I would say,
quite
> risky. Any
> > installation to the production has to be accompanied by
an export,
> > otherwise, after re-installing the export, the
deployment would be
> lost.
> >
> > I just wonder if there is a better way.
> >
> > Regards,
> > Peter Sham.
> > -----Original Message-----
> > From: Kallambella, Ajith
> [SMTP:[email protected]]
> > Sent: Tuesday, December 29, 1998 10:11 PM
> > To: 'Haben, Dirk'
> > Cc: 'Forte'
> > Subject: RE: Can I stop the "Attempting
to Rebind"
> after
> > EnvMgr goes AWOL ...
> >
> > You might want to export the Environment
definition and
> > use it to restore the Environment when you
restart( after
> the
> > environment manager dies ungracefully ).
> >
> > Ajith Kallambella. M
> > Forte Systems Engineer,
> > International Business Corporation
> >
> > -----Original Message-----
> > From: Haben, Dirk
[mailto:[email protected]]
> > Sent: Tuesday, December 29, 1998 1:47 AM
> > To: 'Soapbox Forte Users'
> > Subject: Can I stop the "Attempting to Rebind"
after
> EnvMgr goes
> > AWOL
> > ...
> >
> > Hi All.
> >
> > In the last few weeks I have had the Environment
Manager
> (for
> > development)
> > go AWOL in as many weeks.
> > During a restart - after cleaning up (stop/id)
all other
> Forte
> > processes - I
> > run into virtual memory limitations - and the
restart
> fails.
> >
> > A larger virtual memory quota (doubling the
pagefile quota
> actually)
> > did the
> > trick.
> > However the quota is too large to be kept and I
have
> reverted to
> > 400,000
> > blocks (OpenVMS talk for about 200MB).
> >
> > The problem appears to be caused by all this
attempted
> rebinding.
> > "With Forte Release 3, this rebinding process is
> asynchronous" (see
> > TN11537).
> >
> > Q: Can I disable the attempted rebind so to
reduce memory
> needs on a
> > restart
> > after the EnvMgr goes AWOL?
> >
> > Supplementary Q: If so - How?
> >
> > TIA and Seasons Greetings,
> > Dirk
> >
> > -
> > To unsubscribe, email '[email protected]'
with
> > 'unsubscribe forte-users' as the body of the
message.
> > Searchable thread archive
> > <URL:http://pinehurst.sageit.com/listarchive/>
> > -
> > To unsubscribe, email '[email protected]'
with
> > 'unsubscribe forte-users' as the body of the
message.
> > Searchable thread archive
> > <URL:http://pinehurst.sageit.com/listarchive/>
> > -
> > To unsubscribe, email '[email protected]' with
> > 'unsubscribe forte-users' as the body of the message.
> > Searchable thread archive
> <URL:http://pinehurst.sageit.com/listarchive/>
>
> -
> To unsubscribe, email '[email protected]' with
> 'unsubscribe forte-users' as the body of the message.
> Searchable thread archive
> <URL:http://pinehurst.sageit.com/listarchive/>
> -
> To unsubscribe, email '[email protected]' with
> 'unsubscribe forte-users' as the body of the message.
> Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>