ICEpush in WebSphere Portal requires EPS to work. Old version of eps.jar from March 5 still works, but new version generated from maintenance branch does not, which indicates the IBM infrastructure is configured properly.

 Symptom include a loop requesting the following:


[620.01 10:06:26.258s] -- POST /eps/listen.icepush HTTP/1.1
[620.02 10:06:26.268s] -- POST /eps/listen.icepush HTTP/1.1
[620.02 10:06:26.277s] -- POST /eps/listen.icepush HTTP/1.1
[620.14 10:06:26.394s] -- POST /eps/listen.icepush HTTP/1.1

The responses are all <noop/>

logging on the console contains:

[22/08/12 10:28:05:852 PDT] 00000031 BlockingConne 1 ICEpush metric: IP: 127.0.0.1 pushIds: [v59mrr05, v59mrr06] Cloud Push ID: null Browser: 5h66oci3l last request: 6 Latency: 5 connectionRecreationTimeout: 500
[22/08/12 10:28:05:852 PDT] 00000031 BlockingConne 1 Request does not contain pushIDs.
[22/08/12 10:28:05:853 PDT] 00000031 BlockingConne 3 Sending NoOp.
[22/08/12 10:28:05:858 PDT] 00000031 BlockingConne 1 ICEpush metric: IP: 127.0.0.1 pushIds: [v59mrr05, v59mrr06] Cloud Push ID: null Browser: 5h66oci3l last request: 6 Latency: 5 connectionRecreationTimeout: 500
[22/08/12 10:28:05:858 PDT] 00000031 BlockingConne 1 Request does not contain pushIDs.
[22/08/12 10:28:05:858 PDT] 00000031 BlockingConne 3 Sending NoOp.
[22/08/12 10:28:06:055 PDT] 0000003a BlockingConne 1 ICEpush metric: IP: 127.0.0.1 pushIds: [v59mrr05, v59mrr06] Cloud Push ID: null Browser: 5h66oci3l last request: 197 Latency: 197 connectionRecreationTimeout: 500
[22/08/12 10:28:06:055 PDT] 0000003a BlockingConne 1 Request does not contain pushIDs.
[22/08/12 10:28:06:055 PDT] 0000003a BlockingConne 3 Sending NoOp.


I'll post further logging statements as they become available.