Jump to content

Can't replicate


lifeweaver

Recommended Posts

Test conditions:

Fresh server+client installation on 2 computers.

Both are configured to use SSL.

Launched VS and added one project to source control under Plastic.

Made a few changes, including branching.

Local server works without problems.

Replication ("Push this branch..." menu) fails. VS, GUI, cm.exe, whatever.

FYI, loader.log.txt says something like this most of the time:

(null) (null) (null) ERROR Replication - Error processing replication operation. Unknown response message from server: xxx.xxx.xxx.xxx:xxxx.

Server stack trace:

Exception rethrown at [0]:

at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

at Codice.CM.Interfaces.IReplicationHandler.GetChangesetsOnBranch(Int64 repId, Guid brId)

at Codice.CM.Server.Replication.RemoteReplicationOperation.GetRemoteCsets(RepositoryInfo repInfo, Guid brId)

at a.f()

at a.h()

at u4.a(Object A_0)

And this sometimes:

(null) (null) (null) ERROR Replication - Error processing replication operation. This stream does not support seek operations.: xxx.xxx.xxx.xxx:xxxx.

Server stack trace:

Exception rethrown at [0]:

at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

at Codice.CM.Interfaces.IReplicationHandler.GetChangesetsOnBranch(Int64 repId, Guid brId)

at Codice.CM.Server.Replication.RemoteReplicationOperation.GetRemoteCsets(RepositoryInfo repInfo, Guid brId)

at a.f()

at a.h()

at u4.a(Object A_0)

Creating package and importing it to remote server seems to work.

Link to comment
Share on other sites

No luck. Replicating between 2 SSL-enabled servers doesn't work.

More info:

Replication works only if:

1. Client is set to non-SSL. (do not use SSL port, do not change client.conf to use <ServerProtocol> thing)

2. Profile is set to non-SSL. (do not use SSL port)

Initial test was done only using SSL port. It turned out that only non-SSL port should be used.

I feel that SSL feature needs more caring :-)

Link to comment
Share on other sites

Life,

yep, I tested it as well, and with replication a no go now.

but the good news !! :)

already have a first implementation, since the ssl as you know is a best effort from development here, we tested a new build, and possibly will be included in one of the coming releases.

cheers,

Miller

Link to comment
Share on other sites

  • 4 weeks later...

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...