Need information: Change of Object Server Name in SLD??

[Former Member]

Hi,

we are using an SLD and the Name server on a central system for JDI. At the beginning when we started using this SLD we configured the system.domain name as object server name. Now we activated the name server function on that SLD and we have problems with the name reservation.

Is this problem related to the wrong object server name which is not reserved at service marketplace?

What does it mean to change the name of an object server in a heavily used SLD????

Many thanks for any help!

[former_member183805]

Hi,

If the name-reservation issue you are mentioning is the one you've mentioned in this thread :

then you should double-check the URL of the name server defined in DTR and in the development configuration.

To find out more about the problem, you can switch severity of the com.tssap.dtr.server.deltav.nameres.impl.NameReservationManager location to DEBUG, and then look into the defaultTrace again (in the LogViewer). There should be more detailed messages describing what's the problem.

Regards,

Manohar

[Former Member]

Hi Manohar,

this helped: I got the following debug entry: "didn't find direct match of http://<server.domain>:50000 in name server list -> try to resolve URLs via hostname lookup"

The name server is configured with URL "http://<server.domain>:50000/sld/cimom" and the logon credentials. Is this entry wrong?

Many thanks!

Birgit

[former_member183805]

Hi Birgit,

Yes, that entry is wrong. Remove the part "/sld/cimom" and it should work fine.

Regards,

Manohar

[Former Member]

Hi Manohar,

I got one step further )

Now we get the following error but no debug information is awaylable:

Error during finalization of name-reservation -> operation will be retried  name reservation : name server=http://<server.domain>:50000/,  category=SAP_DevelopmentComponentName, name=hp.com/appl/axis, reservationKey=97651255, state=FINALIZE_PENDING 
[EXCEPTION]
 java.lang.NullPointerException

It's funny that the name server containes entries for the DCs in status preres. As the name server wasn't found before I wander how these entries got in there...

Any help is welcome!

Many thanks,

Birgit

[Former Member]

Hi Manohar,

I now found a more detailed dump:

[code]Error during finalization of name-reservation -> operation will be retried name reservation : name server=http://<server.domain>:50000/, category=SAP_DevelopmentComponentName, name=hp.com/appl/servlet2, reservationKey=93675310, state=FINALIZE_PENDING

[EXCEPTION]

java.lang.NullPointerException

at com.sap.guid.GUID.<init>(GUID.java:289)

at com.sap.guid.GUIDGenerator.createGUID(GUIDGenerator.java:47)

at com.tssap.dtr.pvc.util.guid.CentralGUIDGenerator.createGUID(CentralGUIDGenerator.java:107)

at com.tssap.dtr.pvc.changemg.DevlinePersistentClass.loadKnownDevline(DevlinePersistentClass.java:209)

at com.tssap.dtr.pvc.changemg.DevlineTransientClass.loadKnownDevline(DevlineTransientClass.java:63)

at com.tssap.dtr.pvc.changemg.ChangeManager.getKnownDevline(ChangeManager.java:150)

at com.tssap.dtr.server.deltav.impl.WorkspaceTransientClass.loadWorkspace(WorkspaceTransientClass.java:80)

at com.tssap.dtr.server.deltav.impl.Resource.getWorkspace(Resource.java:601)

at com.tssap.dtr.server.deltav.impl.Activity.getWorkspace(Activity.java:632)

at com.tssap.dtr.server.deltav.nameres.impl.MultiNameReservation.getWorkspace(MultiNameReservation.java:391)

at com.tssap.dtr.server.deltav.nameres.impl.NameReservation.getWorkspace(NameReservation.java:87)

at com.tssap.dtr.server.deltav.nameres.impl.NameReservationManager$NameServer.reserveFinally(NameReservationManager.java:107)

at com.tssap.dtr.server.deltav.nameres.impl.NameReservationManager._doSynchronousFinalize(NameReservationManager.java:459)

at com.tssap.dtr.server.deltav.nameres.impl.NameReservationManager.processQueue(NameReservationManager.java:253)

at com.tssap.dtr.server.deltav.nameres.ProcessNameReservationsTask._run(ProcessNameReservationsTask.java:35)

at com.tssap.dtr.pvc.basics.transaction.AbstractSessionBoundTask.run(AbstractSessionBoundTask.java:37)

at com.tssap.dtr.pvc.util.scheduler.Invocation$Worker.run(Invocation.java:130)

at java.lang.Thread.run(Thread.java:534)[/code]

Many thanks!

Birgit

[former_member470750]

Hi Birgit,

this is a known bug that was fixed in the latest SP12 patch.

Please upgrade your JDI to, at least, the latest SP12 patch.

best regards

Sasa

[Former Member]

Hi Sasa,

our development environment is on 6.40 SP12 ... ????

Best regards,

Birgit

[former_member470750]

Hi Birgit,

did you apply all SP12 patches available from the SAP service marketplace?

regards

Sasa