APAR status
Closed as program error.
Error description
Within a Sterling B2B Integrator 5.1 2 node cluster running on AIX, the second node becomes unstable after startup. The problem is caused by 4 noapp instances starting concurrently. In addition, there are communication failures on node 2 that are caused by the 4 instances of noapp starting.
Local fix
STRRTC - 318066 SB / SB Circumvention: Set the AIX OS level parameter to 0: tcp_bad_port_limit=0 (this is the default parameter)
Problem summary
Users Affected: AIX users Problem Description: NOAPP server can start multiple times when the OPS server is running slow and exceeding its timeout limit. Platforms Affected: Non Windows Platforms
Problem conclusion
Resolution Summary: Added synchronization step to only allow one NOAPP JVM to be started. Delivered In: 5104
Temporary fix
Comments
Published 4/18/2012
APAR Information
APAR number
IC82289
Reported component name
STR FILE GATEWA
Reported component ID
5725D0700
Reported release
210
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-03-27
Closed date
2012-03-28
Last modified date
2012-11-14
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
STR FILE GATEWA
Fixed component ID
5725D0700
Applicable component levels
R210 PSY
UP
Rate this page:
Average rating
Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.