ClearCase stream synchronization issues

Hi

I have some concerns around the synchornization.

We are using RTC on a test basis and we set up a RTC CC
synchronized stream that is associated with a ClearCase
UCM stream where no checkouts or checkins are done on the
ClearCase side but the stream will be rebased with its parent
once a week to update the stream with the latest code baseline.

After i rebased the stream and performed the synchronization
I got these errors

1. First - Current login name CCOWNER does not match
expected login name ccowner.
I never got this error the first time i synchronized. Anyways...I
changed the "CLEARCASE_LOGIN_NAME" and it worked.

2.But this time after 40 minutes of working i got a runtime error -
nullpoint exception.

3.The other issue I have is when i ran the synchronizaiton I
selected only a particular directory but the sync seems to
run for all the directories.

Please help.

Thanks.

Regards
SN

These sound like 3 separate issues. Please submit a workitem on each of
them, so we can get them addressed.

For issue 1, is CCOWNER or ccowner the correct login name?

For issue 2, please attach the logs from the sync run, so we can see
where the null pointer exception is coming from.

For issue 3, also please attach the logs from the sync run (so we can
see what the sync engine was processing).

And as always, please make sure to specify which version of RTC you are
using (there was an NPE bug that was fixed in 1.0.1.1, so upgrading to
the 1.0.1.1 client might solve that problem, but we'd need the
stacktrace to be sure).

If you need any help with submitting workitems, please let us know.

Cheers,
Geoff

nsankara wrote:

Hi

I have some concerns around the synchornization.

We are using RTC on a test basis and we set up a RTC CC
synchronized stream that is associated with a ClearCase
UCM stream where no checkouts or checkins are done on the
ClearCase side but the stream will be rebased with its parent
once a week to update the stream with the latest code baseline.

After i rebased the stream and performed the synchronization
I got these errors

1. First - Current login name CCOWNER does not match
expected login name ccowner.
I never got this error the first time i synchronized. Anyways...I
changed the "CLEARCASE_LOGIN_NAME" and it worked.

2.But this time after 40 minutes of working i got a runtime error -
nullpoint exception.

3.The other issue I have is when i ran the synchronizaiton I
selected only a particular directory but the sync seems to
run for all the directories.

Please help.

Thanks.

Regards
SN

Thanks Geoff.

For issue 2 i have submitted defect 68734. I hope I have
submitted the workitem the right way.

For the first issue -
"Current login name CCOWNER does not match
expected login name ccowner."
I never got this error the first time i synchronized.
I changed the "CLEARCASE_LOGIN_NAME" from ccowner to CCOWNER
and it worked.
So ccowner is the correct login name and it was the initial
value of "CLEARCASE_LOGIN_NAME" but the error means that
it is interpreting ccowner as CCOWNER and asking me to set it
right...Strange?





gmclemmwrote:
These sound like 3 separate issues. Please submit a workitem on each
of
them, so we can get them addressed.

For issue 1, is CCOWNER or ccowner the correct login name?

For issue 2, please attach the logs from the sync run, so we can see

where the null pointer exception is coming from.

For issue 3, also please attach the logs from the sync run (so we
can
see what the sync engine was processing).

And as always, please make sure to specify which version of RTC you
are
using (there was an NPE bug that was fixed in 1.0.1.1, so upgrading
to
the 1.0.1.1 client might solve that problem, but we'd need the
stacktrace to be sure).

If you need any help with submitting workitems, please let us know.

Cheers,
Geoff

nsankara wrote:
Hi

I have some concerns around the synchornization.

We are using RTC on a test basis and we set up a RTC CC
synchronized stream that is associated with a ClearCase
UCM stream where no checkouts or checkins are done on the
ClearCase side but the stream will be rebased with its parent
once a week to update the stream with the latest code baseline.

After i rebased the stream and performed the synchronization
I got these errors

1. First - Current login name CCOWNER does not match
expected login name ccowner.
I never got this error the first time i synchronized. Anyways...I
changed the "CLEARCASE_LOGIN_NAME" and it worked.

2.But this time after 40 minutes of working i got a runtime error -
nullpoint exception.

3.The other issue I have is when i ran the synchronizaiton I
selected only a particular directory but the sync seems to
run for all the directories.

Please help.

Thanks.

Regards
SN

Thanks, the defect you submitted has the info we need to start
investigating (if we need more info, we'll let you know).

For the login-name strangeness, we haven't been able to reproduce that
here. I've created defect 68755 to see if we can track that down. If
by any chance you can reproduce it, please let us know (just post a
comment in defect 68755).

We did want to follow-up on issue 3 as well, i.e. the sync running on
directories other than the ones you specified ... could you file a
workitem on that as well, indicating what directory you specified, and
what directories were actually brought over? Note: to find out what the
current set of directories being synchronized, you can request the
"select files/directories to synchronize" operation in the CC
synchronized stream view, and then select the "show existing" check box.

Cheers,
Geoff

nsankara wrote:

Thanks Geoff.

For issue 2 i have submitted defect 68734. I hope I have
submitted the workitem the right way.

For the first issue -
"Current login name CCOWNER does not match
expected login name ccowner."
I never got this error the first time i synchronized.
I changed the "CLEARCASE_LOGIN_NAME" from ccowner to CCOWNER
and it worked.
So ccowner is the correct login name and it was the initial
value of "CLEARCASE_LOGIN_NAME" but the error means that
it is interpreting ccowner as CCOWNER and asking me to set it
right...Strange?





gmclemmwrote:
These sound like 3 separate issues. Please submit a workitem on each
of
them, so we can get them addressed.

For issue 1, is CCOWNER or ccowner the correct login name?

For issue 2, please attach the logs from the sync run, so we can see

where the null pointer exception is coming from.

For issue 3, also please attach the logs from the sync run (so we
can
see what the sync engine was processing).

And as always, please make sure to specify which version of RTC you
are
using (there was an NPE bug that was fixed in 1.0.1.1, so upgrading
to
the 1.0.1.1 client might solve that problem, but we'd need the
stacktrace to be sure).

If you need any help with submitting workitems, please let us know.

Cheers,
Geoff

nsankara wrote:
Hi

I have some concerns around the synchornization.

We are using RTC on a test basis and we set up a RTC CC
synchronized stream that is associated with a ClearCase
UCM stream where no checkouts or checkins are done on the
ClearCase side but the stream will be rebased with its parent
once a week to update the stream with the latest code baseline.

After i rebased the stream and performed the synchronization
I got these errors

1. First - Current login name CCOWNER does not match
expected login name ccowner.
I never got this error the first time i synchronized. Anyways...I
changed the "CLEARCASE_LOGIN_NAME" and it worked.

2.But this time after 40 minutes of working i got a runtime error -
nullpoint exception.

3.The other issue I have is when i ran the synchronizaiton I
selected only a particular directory but the sync seems to
run for all the directories.

Please help.

Thanks.

Regards
SN

Thanks Geoff.

1.The null point error is of top priority for us because we
are not able to move forward.

2.The login name issue is really strange. One other thing
I noticed is, when I try creating a new synchronized stream,
in the second form where you have "import from an existing
stream" and all that, the ClearCase user id is
"CCOWNER".

3.I checked "select files/directories to synchronize" and
then checked "show currently synchronized objects in table"
and the table gives me a list of the directories that
succeeded and failed in the past.
If I remove all these entries and just add the entry
for the directory I want to currently sync, will it
delete information about the previously successfully
synchronized directories?

Thanks.

Regards
Sankara N




gmclemmwrote:
Thanks, the defect you submitted has the info we need to start
investigating (if we need more info, we'll let you know).

For the login-name strangeness, we haven't been able to reproduce
that
here. I've created defect 68755 to see if we can track that down.
If
by any chance you can reproduce it, please let us know (just post a

comment in defect 68755).

We did want to follow-up on issue 3 as well, i.e. the sync running
on
directories other than the ones you specified ... could you file a
workitem on that as well, indicating what directory you specified,
and
what directories were actually brought over? Note: to find out what
the
current set of directories being synchronized, you can request the
"select files/directories to synchronize" operation in the
CC
synchronized stream view, and then select the "show
existing" check box.
Cheers,
Geoff

nsankara wrote:
Thanks Geoff.

For issue 2 i have submitted defect 68734. I hope I have
submitted the workitem the right way.

For the first issue -
"Current login name CCOWNER does not match
expected login name ccowner."
I never got this error the first time i synchronized.
I changed the "CLEARCASE_LOGIN_NAME" from ccowner to
CCOWNER
and it worked.
So ccowner is the correct login name and it was the initial
value of "CLEARCASE_LOGIN_NAME" but the error means that
it is interpreting ccowner as CCOWNER and asking me to set it
right...Strange?





gmclemmwrote:
These sound like 3 separate issues. Please submit a workitem on
each
of
them, so we can get them addressed.

For issue 1, is CCOWNER or ccowner the correct login name?

For issue 2, please attach the logs from the sync run, so we can
see
where the null pointer exception is coming from.

For issue 3, also please attach the logs from the sync run (so we
can
see what the sync engine was processing).

And as always, please make sure to specify which version of RTC you
are
using (there was an NPE bug that was fixed in 1.0.1.1, so upgrading
to
the 1.0.1.1 client might solve that problem, but we'd need the
stacktrace to be sure).

If you need any help with submitting workitems, please let us know.

Cheers,
Geoff

nsankara wrote:
Hi

I have some concerns around the synchornization.

We are using RTC on a test basis and we set up a RTC CC
synchronized stream that is associated with a ClearCase
UCM stream where no checkouts or checkins are done on the
ClearCase side but the stream will be rebased with its parent
once a week to update the stream with the latest code baseline.

After i rebased the stream and performed the synchronization
I got these errors

1. First - Current login name CCOWNER does not match
expected login name ccowner.
I never got this error the first time i synchronized. Anyways...I
changed the "CLEARCASE_LOGIN_NAME" and it worked.

2.But this time after 40 minutes of working i got a runtime error -
nullpoint exception.

3.The other issue I have is when i ran the synchronizaiton I
selected only a particular directory but the sync seems to
run for all the directories.

Please help.

Thanks.

Regards
SN

WRT the null pointer error, I've marked that as high priority, and added
the CC Connector team lead as a subscriber. One thing to do until then:
create another synchronized stream, and select a different directory to
sync over. This would give us a chance to see any of the problems you
saw can easily be reproduced.

WRT 3, no, if you remove entries from the list to be synchronized, it
will not delete the files/directories that have already been
synchronized into the Jazz stream (they will just no longer be
synchronized). Note that you can always add the directory back to the
list to be synchronized later, if you want it to start synchronizing again.

Cheers,
Geoff


nsankara wrote:

Thanks Geoff.

1.The null point error is of top priority for us because we
are not able to move forward.

2.The login name issue is really strange. One other thing
I noticed is, when I try creating a new synchronized stream,
in the second form where you have "import from an existing
stream" and all that, the ClearCase user id is
"CCOWNER".

3.I checked "select files/directories to synchronize" and
then checked "show currently synchronized objects in table"
and the table gives me a list of the directories that
succeeded and failed in the past.
If I remove all these entries and just add the entry
for the directory I want to currently sync, will it
delete information about the previously successfully
synchronized directories?

Thanks.

Regards
Sankara N




gmclemmwrote:
Thanks, the defect you submitted has the info we need to start
investigating (if we need more info, we'll let you know).

For the login-name strangeness, we haven't been able to reproduce
that
here. I've created defect 68755 to see if we can track that down.
If
by any chance you can reproduce it, please let us know (just post a

comment in defect 68755).

We did want to follow-up on issue 3 as well, i.e. the sync running
on
directories other than the ones you specified ... could you file a
workitem on that as well, indicating what directory you specified,
and
what directories were actually brought over? Note: to find out what
the
current set of directories being synchronized, you can request the
"select files/directories to synchronize" operation in the
CC
synchronized stream view, and then select the "show
existing" check box.
Cheers,
Geoff

nsankara wrote:
Thanks Geoff.

For issue 2 i have submitted defect 68734. I hope I have
submitted the workitem the right way.

For the first issue -
"Current login name CCOWNER does not match
expected login name ccowner."
I never got this error the first time i synchronized.
I changed the "CLEARCASE_LOGIN_NAME" from ccowner to
CCOWNER
and it worked.
So ccowner is the correct login name and it was the initial
value of "CLEARCASE_LOGIN_NAME" but the error means that
it is interpreting ccowner as CCOWNER and asking me to set it
right...Strange?





gmclemmwrote:
These sound like 3 separate issues. Please submit a workitem on
each
of
them, so we can get them addressed.

For issue 1, is CCOWNER or ccowner the correct login name?

For issue 2, please attach the logs from the sync run, so we can
see
where the null pointer exception is coming from.

For issue 3, also please attach the logs from the sync run (so we
can
see what the sync engine was processing).

And as always, please make sure to specify which version of RTC you
are
using (there was an NPE bug that was fixed in 1.0.1.1, so upgrading
to
the 1.0.1.1 client might solve that problem, but we'd need the
stacktrace to be sure).

If you need any help with submitting workitems, please let us know.

Cheers,
Geoff

nsankara wrote:
Hi

I have some concerns around the synchornization.

We are using RTC on a test basis and we set up a RTC CC
synchronized stream that is associated with a ClearCase
UCM stream where no checkouts or checkins are done on the
ClearCase side but the stream will be rebased with its parent
once a week to update the stream with the latest code baseline.

After i rebased the stream and performed the synchronization
I got these errors

1. First - Current login name CCOWNER does not match
expected login name ccowner.
I never got this error the first time i synchronized. Anyways...I
changed the "CLEARCASE_LOGIN_NAME" and it worked.

2.But this time after 40 minutes of working i got a runtime error -
nullpoint exception.

3.The other issue I have is when i ran the synchronizaiton I
selected only a particular directory but the sync seems to
run for all the directories.

Please help.

Thanks.

Regards
SN