Patch-ID# 106822-01
Keywords: processing failure get request access control truncated scope base
Synopsis: Solstice CMIP 8.2.1: patch for runtime and examples fixes
Date: Oct/05/98

Solaris Release: 2.4, 2.5, 2.5.1, 2.6

SunOS Release: 5.4, 5.5, 5.5.1, 5.6

Unbundled Product: Solstice CMIP

Unbundled Release: 8.2.1

Relevant Architectures: sparc

BugId's fixed with this patch: 4152169 4160408 4168444 4050437 4117026 4130193 4124501 1234693 4112678 4063010 4045832 4070564 4070565 4049216 4044626 4034011 4018168 4061970 4004093 4005297 4017629 4022483 4023614 4035856 4030607 4029323 4028111 4044804 4054473 4090284 4057461 4085367 4088219 4088728 

Changes incorporated in this version: 

Patches accumulated and obsoleted by this patch: 

Patches which conflict with this patch: 104190-09

Patches required with this patch: 

Obsoleted by: 

Files included with this patch: 

/opt/SUNWconn/cmip/lib/libxmp.so.1 
/opt/SUNWconn/cmip/lib/libxom.so.1 
/opt/SUNWconn/cmip/sbin/cmiptrace 
/opt/SUNWconn/cmip/sbin/cmipoper 
/opt/SUNWconn/cmip/sbin/cmiptool 
/opt/SUNWconn/cmip/lib/osimcsd 
/opt/SUNWconn/cmip/sbin/shmmgr 
/etc/init.d/osimcs 
/opt/SUNWconn/cmip/include/xmp.h 
/opt/SUNWconn/cmip/include/xomi.h 

Problem Description:


4152169 Abort when sending an invalidScope
4168444 Processing Failure inconsistently returned to a scoped get request via TMNscript 
4160408 1320 bytes long user access control field truncated to 350 bytes                 
4124501 mp_wait fails, osimcs goes 3%-->35% cpu, em_cmip loses stack contact and exits
4130193 cmip memory leak causing application to core - not 1227641 duplicate
4117026 OSIMCSD Request time-out
4050437 CMIP is limited to 256 concurrent associations 
4112678 cmip 8.1 free size getscope > 20000 instances
1234693 Association is aborted if the application contexts differ.
4088728 CMIP stack (osimcsd daemon) disconnects after receiving a lot of release_req     
4088219 CMIP 8.1.2 p5 stack cores in MPpurgeCtx out of mp_receive
4085367 Shared Memory not released
4057461 osicms with patch 102245-19 core dump
4090284 CMIP stack returns a Miscellaneous error when operating on associations.
4063010 trace corrupted on hexadecoimal too long
4054473 XMP application core dumps in mp_assoc_rsp on Windows NT platform
4070565 When doing a lot of linked reply, a abort can occur
4070564 mp_bind return communication error on an already used session but unbound now
4045832 Increasing response time when establishing association with the CMIP MPA
4061970 memory corruption in osimcsd  (decodage of long OID) with cmiptrace connected
4018168 XMP (SunTGVON) doesn't support LDN and null OI - it only supports FDN (CONT 2)
4034011 SEm cmipmpa cannot start do to early finish o
4044626 em_cmip timeout can't handle many 128+ con
4049216 CMIP considers an agent already bound after i
4044804 CMIP/XOM gave bogus length byte of FDN causing CMIP MPA crash on EM decode
4028111 On HP machine, C++ compilation errors when including xmp.h or xomi.h
4029323 CMIP XMP 8.2.1 Cannot send a public assoc_result object in an Associate Respons
4030607 CMIP 8.2 trace errors with ERROR : Spurious msg ID(3230, 4) CODE(ff11)
4035856 Asn.1 decoding problem, mp_receive core dumps
4023614 When using associate_request, the object file descriptor is -1.
4004093 osimcs crashes on an access denied on a set_response
4005297 Sun EM/CMIP software does not work with a NULL psel
4017629 In ACM ON Mode we don't send no "user acse data"
4022483 Memory leak in XMP when doing mp_xxx_rsp/mp_xxx_req on invalid session






Patch Installation Instructions: 
-------------------------------- 
Refer to the Install.info file for instructions on using the
generic 'installpatch' and 'backoutpatch' scripts provided with
each patch.  Any other special or non-generic installation
instructions should be described below as special instructions.

Special Install Instructions: 
-----------------------------

Warning : This patch is not compatible with the 104190 patch family
It introduce a change in the interface between XMP / osimcs communication
So this patch can be used for all customer using standard interface.
But it should not be applied on customer using "non standard" interface
(access to osimcs without libxmp/libxom)
