[Sblim-devel] wseventsink could not receive indication.

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Hello All,

I successfully using wsman/openwsman/sfcb/wseventsink to observe indications on SLES 11 sp3.
Now my work turn on RHEL 6.5
I can use wsman to enumerate instances. And I can use wsman to subscribe indication, however, wseventsink can't output the indications.
Here is the log from openwsman:

Dec 24 16:07:24 [10716] one heartbeat document created for 36ee65fc-ee43-1e43-8002-a0926d2fb5b4
Dec 24 16:07:24 [10716] wse_heartbeat_sender for 36ee65fc-ee43-1e43-8002-a0926d2fb5b4 started
Dec 24 16:07:24 [10716] Endpoint: http://127.0.0.1:80/eventsink
Dec 24 16:07:24 [10716] cl->authentication.verify_peer: 1
Dec 24 16:07:24 [10716] *****set post buf len = 482******
Dec 24 16:07:27 [10716] curl error code: 1.
Dec 24 16:07:27 [10716] cl->response_code: 0.
Dec 24 16:07:27 [10716] cl->last_error code: 3.
Dec 24 16:07:27 [10716] [ wse_notification_sender thread for 36ee65fc-ee43-1e43-8002-a0926d2fb5b4 quit! ]

The wseventsink continue print the something like:
                At Dec 24 16:07:40 received:

<?xml version="1.0" encoding="UTF-8"?>
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:xs="http://www.w3.org/2001/XMLSchema">
  <s:Header>
    <wsa:To>http://127.0.0.1:80/eventsink</wsa:To>
    <wsa:Action xs:mustUnderstand="true">http://schemas.xmlsoap.org/wbmem/wsman/1/wsman/Heartbeat</wsa:Action>
    <wsa:MessageID>uuid:3cf8cf63-ee43-1e43-801d-a0926d2fb5b4</wsa:MessageID>
 </s:Header>
  <s:Body/>
</s:Envelope>

It looks like the communication between openwsman and wseventsink encounter some problem. Am I right?

By the way, I found the following defects:
1. I set openwsman to use PAM authentication, it requests pam_unix2.so, however, on RHEL6.5 this library doesn't exist. I have to manually create a link to pam_unix.so.
2. I have to install sblim-sfcc-devel to let the whole process work. The sblim-sfcc-devel will create libcimcClientXML.so libcimcclient.so libcmpisfcc.so to those ended with ".so.x".  But the developer package not always available to customer. This problem exist on SLES 11 sp 3 too.

Thanks and Regards,
Bai, Bin.