when the whole application is migrated to the new chipset with SPARC IV and above running Solaris 10,So, maybe it is a thread synchronization or a timing issue.
the application blows up with CPU utilizationation peaking at 100% occupancy
and threads queuing to the point where the whole application crashes.
The application overall was design to run in a non thread safe way, and certainly on on a CMT chipset.That seems to be garbled.
The application is written in C and each component is started within the C Application Container.I'm not sure what "C Application Container" is.
1. Has anyone seen this type of behaviour before.No, not that I remember.
2. If so, was it possbile to migrate the application to newer hardware, and with what fixes.Most applications written in C will port to new hardware with no changes.
3. If someone has successfully done this, can the application run in a virtualized environment?Once you get it running, it should also run in a virtualized environment.