Error during SLD syncronisation

[christiaan_schaake2]

We have configured a central SLD enigine. All PI 7.1 systems are connected to there own local SLD engine. The local SLD engines syncronise via SLD Syncronisation with the central SLD.

This synchronisation is not stable. When activating a full-sync we often get the following error:

Error: CIM_ERR_FAILED: IO error on releasing response stream

The SLD log on the local SLD shows the error:

#58 04/23/2010 09:50:44.511 [SLD ContentSync sld/active] ERROR com.sap.sld.contentsync.SyncRunner: Error during sync of sld/active from http://CENSORED:

56000/sld/cimom, namespace sld/active

Thrown:

com.sap.sld.api.wbem.exception.CIMCommunicationException: CIM_ERR_FAILED: HTTP error: Invalid begin of response [expected: 'HTTP', found: 'T']

at com.sap.sld.api.wbem.client.WBEMHttpRequestSender.sendImpl(WBEMHttpRequestSender.java:225)

at com.sap.sld.api.wbem.client.WBEMRequestSender.send(WBEMRequestSender.java:205)

at com.sap.sld.api.wbem.client.WBEMRequestSender.send(WBEMRequestSender.java:175)

at com.sap.sld.api.wbem.client.WBEMRequestSender.send(WBEMRequestSender.java:238)

at com.sap.sld.api.wbem.client.WBEMRequestSender.send(WBEMRequestSender.java:268)

at com.sap.sld.api.wbem.client.WBEMRemoteClient.getClassImpl(WBEMRemoteClient.java:148)

at com.sap.sld.api.wbem.client.WBEMAbstractClient.exists(WBEMAbstractClient.java:819)

at com.sap.sld.api.wbem.client.WBEMClientUtil.checkServer(WBEMClientUtil.java:139)

at com.sap.sld.api.wbem.client.WBEMClientUtil.ping(WBEMClientUtil.java:101)

at com.sap.sld.contentsync.SyncRunner.checkSyncPrerequisites(SyncRunner.java:631)

at com.sap.sld.contentsync.SyncRunner.runFullSync(SyncRunner.java:103)

at com.sap.sld.contentsync.SyncRunner.runFullSync(SyncRunner.java:67)

at com.sap.sld.contentsync.SyncRunner.run(SyncRunner.java:274)

at com.sap.sld.contentsync.SyncRunner.run(SyncRunner.java:377)

at java.lang.Thread.run(Thread.java:665)

Caused by: com.tssap.dtr.client.lib.protocol.HTTPException: Invalid begin of response [expected: 'HTTP', found: 'T']

at com.tssap.dtr.client.lib.protocol.impl.Response.initialize(Response.java:483)

at com.tssap.dtr.client.lib.protocol.Connection.getResponse(Connection.java:2610)

at com.tssap.dtr.client.lib.protocol.Connection.sendInternal(Connection.java:1578)

at com.tssap.dtr.client.lib.protocol.Connection.send(Connection.java:1427)

at com.sap.sld.api.wbem.client.WBEMHttpRequestSender.sendImpl(WBEMHttpRequestSender.java:201)

... 14 more

#57 04/23/2010 09:50:44.493 [HTTP Worker [7]] ERROR com.sap.sld.contentsync.SyncManager: Cannot retrieve source path for source: http://CENSORED:56000/s

ld/cimom, namespace sld/active, target: <local>, namespace sld/active

#56 04/23/2010 09:50:44.306 [HTTP Worker [7]] ERROR com.sap.sld.contentsync.SyncManager: Cannot retrieve source path for source: http://CENSORED:56000/s

ld/cimom, namespace sld/active, target: <local>, namespace sld/active

#55 04/23/2010 09:50:43.019 [HTTP Worker [7]] INFO com.sap.sld.contentsync.SyncManager: Starting sync of sld/active from http://CENSORED:56000/sld/cimom

, namespace sld/active

#54 04/23/2010 09:50:42.936 [HTTP Worker [7]] INFO com.sap.sld.contentsync.SyncManager: Stopping sync of sld/active from destination SLD_SyncDest0

Does anyone reconise this problem?

Or central SLD is running on 7.0 and the locals are running on 7.1. The CIM model is the some for all SLD's.

Cheers,

Christiaan Schaake

[stuart_campbell]

The local SLDs need to be able to do a full sync option (this might only available on certain Netweaver versions or SP levels)

The central SLD has to be able to recieve a full sync (again only available on certain NW versions and SP levels)

The central SLD has to be able to recieve all data in the sync - that is the central SLD has to be on a equal or higher version CIM, CR and SP than all local SLDs

To my knowledge a full sync also includes CIM, CR definitions -if you are doing a full sync from local to central then as I see it this will overwrite and indeed create a new CIM import line everytime you update the Central SLD from each synchronizing local SLD - this is not recommended - mainly because the central SLD should only ever receive CIM, CR content from its original source

(usually SAP service marketplace downloads) but also local SLDs may be on lower or different versions thus cause a downgrade/mis-match

It might be a better setup to just export landscape data only, between the local SLDs and central SLD

Best wishes

Stuart

[Former Member]

HI,

is it possible for sld synchronization between pi7.0 and pi7.1？as i know sld syschronization is the new function of pi7.1.

are your sure your central sld version is 7.0, i think you should check your syschronization config for the url.