20742195

The RFC 6665 specification states that proxy servers that do not add Record-Route header fields to the initial SUBSCRIBE request are then prohibited from adding Record-Route header fields to any associated NOTIFY requests. However, Converged Application Server does not check for Record-Route header fields in NOTIFY requests.

Developers creating applications for Converged Application Server should not call Proxy.setRecordRoute(true), or proxyBranch.setRecordRoute(true) when handling notify requests that did not already set the Record-Route header field in a Register request.

Associating too many sessions with a single key causes performance problems.

When using the new SipApplicationSession addIndexKey() method, ensure that the session keys you create are unique to subscribers. This strategy helps you avoid performance degradation problems.

If your session keys are unique to subscribers and large reads still cause performance problems, try paging the result when iterating over the read index record.

If your session keys are unique to subscribers and large writes still cause performance problems, try splitting large index records into smaller "chunks." That way you do not need to deserialize the full record to add or remove values from it.

Deploying SIP applications that declare ServletContainerInitializer can in some cases cause the onStartup() method to be called twice.

You can prevent this by using the wlss.initializer.classes system property to specify and limit SIP specific container initializers.

Applications should not try to inject a resource with the same name in both a field and method. For example, injecting a SipFactory resource with the same name into both the setMySipFactory method and the mySipFactory field is not supported.

This behavior is prohibited by JavaEE specification EE.5.2.3, but this release of Converged Application Server does not specifically check for this error.

Violating this rule can cause unexpected behavior.