Archived

This forum has been archived. Please start a new discussion on GitHub.

Purify and IceBox services

xdm
xdm La Coruña, Spain
Hello all

any body know if is posible check icebox services with purify?

the run command for purify only acept executables, i try to purify icegridregistry.exe but when do it this i don´t see the memory allocations of my services.

other way to do it, is rewrite my icebox services as server executables but i trying to aboid this extra work

any ideas are wellcome

thanks

Comments

  • bernard
    bernard Jupiter, FL
    Yes, you can purify IceBox services. Instead of
     iceboxd --Ice.Config=config
    

    you run
     purify iceboxd --Ice.Config=config
    

    (I recommend to purify debug builds!)


    The icegridregistry is not an IceBox service, so I don't see the relationship with IceBox or why purifying icegridregistry would tell you anything about your own services.

    Cheers,
    Bernard
  • xdm
    xdm La Coruña, Spain
    Hi bernard

    i comment IceGrid beacuse i use IceGridregistry to deploy my services

    can i put the purify command in the application descriptor?
      <icebox id="SessionService"
                    exe="purify"
                    activation="on-demand">
                    <option>c:\Ice-3.0.1/bin/iceboxd.exe</option>
                    <service name="Session" entry="App:create">
                        <adapter name="${service}" endpoints="tcp">
                                <object 
                                    identity="${sessionServiceId}" 
                                    type="::Oz::App::Service"/>
                                <object 
                                    identity="${service}-SessionManager" 
                                    type="::Oz::App::SessionManager"/>
                                <object 
                                    identity="${service}-permission-verifier" 
                                    type="::Glacier2::PermissionsVerifier"/>
                        </adapter>
                        
                        <!-- Id para identificar este servicio-->
                        <property name="serviceId" value="${sessionServiceId}"/>
                        <!-- Id del servicio DomainManager-->
                        <property name="domainManagerServiceId" value="${domainServiceManagerId}"/>
                        <!-- Id del servicio FileManager-->
                        <property name="fileManagerServiceId" value="${fileServiceManagerId}"/>
                        <!-- Id del servicio DomainManager-->
                        <property name="metaManagerServiceId" value="${metaServiceManagerId}"/>
                        <!-- Id del servicio domains que en el cual se logean los usuarios-->
                        <property name="domainServiceId" value="${domainServiceId}"/>
                        <!--Nombre del dominio que se usa-->
                        <property name="domainName" value="${domainName}"/>
                    </service>
                </icebox>
    

    should this work?

    thanks
  • benoit
    benoit Rennes, France
    Hi,

    Yes, I don't see why it wouldn't work, I suggest that you just give it a try and see how it goes ;).

    Another option would be to disable your server to prevent the node from activating it and start it manually from the command line using the configuration file generated by the IceGrid node in the <nodedb>/servers/<server id>/config directory (in addition to the configuration file, you'll also have to pass the --Ice.ServerId=<server id> property and the --Ice.Default.Locator=<proxy of the location service> property).

    Cheers,
    Benoit.
  • xdm
    xdm La Coruña, Spain
    I add the purify command to the descriptor and works perfectly

    thanks