Could not cycle save the messages

Are you attempting to cyclesave through the GUI’s.   What steps are you taking in doing so?

You said you followed these instructions:

just right click my outbound thread icon –> choose “control” –> choose “full” –> choose “cycle save” –> choose “in” –> click “ok” –> click “done”.

If this is an outbound thread and you have the outbound SMAT set up, you will need to choose “out” instead of “in”.  Try this and see if it works for you.

Thanks…

Tom Rioux

Is the thread up or down?   The thread needs to be up when doing this in order to create the .old files.

Thanks…

Tom Rioux

I recall there can be challenges like yours when 2 different threads in the same site use the same SMAT filename.

It is a common problem when doing a copy/paste of a thread to overlook modifying the SMAT filename to something different.

Check your NetConfig to make sure you haven’t defined the same SMAT file name in more than one place.

Try this from the command line to see if it gives you an error:

hcicmd-p -c ” save_cycle_out”

Just plug in the name of the process and the name of the thread in the command.

Tom

Also, if the SMAT file has become extremely large and reached the system maximum allowable size for a single file, then you may have to stop the thread and move it out of the way or get rid of it since it will likely be to big to use anyway.

What is, or how can I find out the system maximum allowable size for a single file?  Tried to do a cycle save through the web (threads are all up).

Old IDX file is 217,000 KB,  MSG file is 344,000 KB.

Current IDX is 310,000 KB,   MSG file is 475,000 KB.

(Old files have been renamed, so they shouldn’t be deleted in a cyclesave.)

Tried to use SMAT to see the old messages and saw the hourglass for >30 minutes.  

Any suggestions/clarifications would be appreciated.

I’m running on an AIX box and have root access and can answer the question you are asking, “What is the biggest file hci can create?”, by looking in /etc/security/limits which shows

hci:

       fsize = 2097151

       core = 2097151

       cpu = -1

       data = 3145728

       rss = 524288

       stack = 524288

       nofiles = 10000

which tells me I can create about a 2 GB file before the system says that’s big enough.

Others may have methods to find out the same information without having to have root access but I haven’t had to go there.

Thanks.   I’ve been looking through the other threads, and it looks like it is a Java default limit of 256Mb.  That can be set.

Doug,

What release of Cloverleaf(R)?

Releases prior to 5.6 were slow with very large SMAT files (if using the client GUI rather than say the TK SMAT on Unix).

I have noticed the 5.6 Client SMAT GUI is pretty fast and handles large files pretty well.

Release 5.4.1.    

Would it give an error if the file was too large?

Doug,

I don’t recall that it does.

I think it just ‘hangs’ – but then I rarely used the client GUI SMAT with large files so I could be wrong there. I used to use the TK SMAT from the AIX command line.

With 5.6 though I think I will get into the habit of using the Client GUI.