2 Replies Latest reply on Dec 23, 2010 3:47 PM by Scott Rabinow

    exporting/importing BL Packages

    Mike Reider

      IHi all, we are trying to migrate BL Packages from a dev server to a prod server (both servers have same BL version, OS ver, same setup)

       

      BL 8.0, Win2003 Enterprise, SQL2005

       

       

      when we export a BL Package from dev, then try to import that BL Package into same folder on prod, we keep getting this message:

       

      [Client] load package failure: JNI file copy from '//blfileserv/e/bladelogic/NSH/storage/imported/1292350815838imported/1290620409356blpackages/CS_WebServer_Build@2008.08.21-14.56.49.810-0400/bldeploy.xml' to '/D/Program Files/BladeLogic/8.0/NSH/tmp/application_server/bldeploy_667b3d88-502e-4952-9934-6cc5782953fe..xml' failed: : No such file or directory

       

      com.bladelogic.mfw.util.BlException: load package failure: JNI file copy from '//blfileserv/e/bladelogic/NSH/storage/imported/1292350815838imported/1290620409356blpackages/CS_WebServer_Build@2008.08.21-14.56.49.810-0400/bldeploy.xml' to '/D/Program Files/BladeLogic/8.0/NSH/tmp/application_server/bldeploy_667b3d88-502e-4952-9934-6cc5782953fe..xml' failed: : No such file or directory

       

          at com.bladelogic.model.depot.blpackage.BlPackageImpl.loadPackageInstructions(BlPackageImpl.java:417)

          at com.bladelogic.model.base.dependency.importer.ModelObjectImporter.fixBlPackages(ModelObjectImporter.java:4140)

          at com.bladelogic.model.base.dependency.importer.ModelObjectImporter.saveObjectGraphToDatabase(ModelObjectImporter.java:3403)

          at com.bladelogic.model.base.dependency.importer.ModelObjectImporter.access$000(ModelObjectImporter.java:105)

          at com.bladelogic.model.base.dependency.importer.ModelObjectImporter$1.doDBOperation(ModelObjectImporter.java:246)

          at com.bladelogic.app.db.TransactionalOperation.manageTransaction(TransactionalOperation.java:174)

          at com.bladelogic.app.db.TransactionalOperation.execute(TransactionalOperation.java:136)

          at com.bladelogic.model.base.dependency.importer.ModelObjectImporter.saveImportedObject(ModelObjectImporter.java:249)

          at com.bladelogic.message.model.frame.ModelFrame.service(ModelFrame.java:116)

          at com.bladelogic.mfw.net.ClientWorkerThread.processRequest(ClientWorkerThread.java:370)

          at com.bladelogic.mfw.net.ClientWorkerThread.processClientRequest(ClientWorkerThread.java:280)

          at com.bladelogic.mfw.net.ClientWorkerThread.handleClientRequest(ClientWorkerThread.java:180)

          at com.bladelogic.mfw.net.ClientWorkerThread.execute(ClientWorkerThread.java:99)

          at com.bladelogic.mfw.net.ClientWorkerThread.execute(ClientWorkerThread.java:25)

          at com.bladelogic.app.service.thread.BlBlockingThread.run(BlBlockingThread.java:92)

       

       

      It looks like its adding the bolded part to the folder path

       

      //blfileserv/e/bladelogic/NSH/storage/imported/1292350815838imported/1290620409356blpackages/CS_WebServer_Build@2008.08.21-14.56.49.810-0400/bldeploy.xml'

       

      the actual path to this xml file on the file server is:
      X:\bladelogic\NSH\storage\imported\1292354935681\CS_WebServer_Build@2008.08.21-14.56.49.810-0400

       

      did anyone else run into this issue? Thanks.

        • 1. exporting/importing BL Packages
          Bill Robinson

          how are you importing it?  are you pointing it at the copy in x: (not e:) when you do the import?

          • 2. exporting/importing BL Packages
            Scott Rabinow

            I have a conceptually similar setup (export from DEV, import to PROD) with different OS and DB.  I do this export/import process all the time.

             

            Where are you exporting the BLPackage to?  It looks to me like maybe you are exporting to another directory on the same fileserver?

             

            For reference, I happen to always export from my DEV environment to my PC (C:\temp for a nice, concise, easy to find location), then I import from that directory on my PC to the PROD environment.

             

            In my experience, every time I've had a strange "JNI file copy" problem, something was wrong with the source file specification, sometimes because the export failed in some strange way.