Clean up my RuntimeStore object

Similar Questions

• ControlDelegate didn't clean up after itself objects

  In order to avoid slowing down the application startup, I create a dialog box to connect dynamically only if the user has not signed earlier. I have the following code, attached to the Home Page:

      attachedObjects: [
          ControlDelegate {
              id: loginDialogDelegate
              delegateActive: false
              sourceComponent: loginDialogDef
          },
          ComponentDefinition {
              id: loginDialogDef
              LoginDialog {
                  id: loginDialog
                  onCreationCompleted: {
                      open()
                  }
                  onClosed: {
                      loginDialogDelegate.delegateActive = false
                  }
              }
          }
      ]
  

  The dialog box code is in LoginDialog.qml. In the home page, I set loginDialogDelegate.delegateActive true when I need to display the dialog box. However, when I close the application, I get a lot of "ERROR: context: object = name ' 'Label'" [objectId = 103] not unrealised'. "

  I was expecting affecting false to ControlDelegate.delegateActive cleans the LoginDialog instance. It seems I'm wrong. How can I modify the code to do this?

  I already tried to explicitly set delegateActive to false (not only in housing), but it does not work.

  In fact there are MANY waterfalls of the Visual objects that do not properly clean on the rise after themselves. I logged a bug with the invocation of sharing where sharing a page that opens cleans all its buttons and similar. Unfortunately there has been no resolution of this bug so far. It seems that the Cascades development team is a bit lax to ensure that each contained object has a parent.

  

• How to record various objects used by an external C function

  I want to do my own LV component that calls a C function that uses an external API. For the first time, my function is called, it creates and defines variables and some API objects and store them. If the future my function calls do not need to define and create them again. The main problem is that this variables and objects must be different for any instance. I mean: if I have several components to call a library function, the call to my function, running at the same time, I need them to create variables and objects, instead of sharing their own API. So I need to be able to access or to allocate a memory space for each different instance of the NSI component that calls to my function.

  How can I do this with the function of library call? Is there another approach to this? How?

  Thank you very much.

  eduraser wrote:

  OK, I really appreciate this answer, thank you very much.

  Of course, I understand that I need to create a function which deletes, clean, free, etc., all objects and the variables created. But I don't know where exactly call to clean up at the right time. I want to have cleaned up the Labview runtime stops (do not break)... so do I call it as a reminder of the library call feature? Anywhere else? Another option?

  Thank you very much!

  Well in general, you flow "create(), read() read(2)/write(2) () / () use, close() in an application" for any resource and close() would be where you would have to call your function has.

  If you want this fact automatically, half only officially documented way is indeed the named of the dialog configuration node unaptly callback function call library. How is this registrant one or more additional function that takes a pointer as a parameter value. This pointer can be everything you want it to be, and you can configure your function to have an additional parameter which is not exposed on the diagram, but rather helps him pass this pointer.

  LabVIEW maintains such a pointer dataspace CLN instance and calls the callback function that appropriate specified events and pass this pointer to data. For example, you can check in the call to the create function if this parameter is NULL, and if yes to store a handle to your resource in there. When the reminder cancel or abort is called you could go and own up to your resource.

• Problems withdraw the application for RuntimeStore

  I have an application that listens to gps, e-mail and sms events. Because I need this application to run at startup of the bb, I used the method mentioned in many articles in kb by placing my application in the Bank to run at startup so that when my gui starts the user interface checks the runtime of the application store and proceeds accordingly. It all works perfectly. My problem comes when I need to stop the background of the GUI thread. I call shutdown in which the application stops all threads, that it is running and then I call a system.exit (0). All threads stop perfectly and closes my gui. However when I return to run the GUI with to restart the phone the waitForSingleton recover again the same background as application before having no threads running in it, and so nothing happens in the GUI (map changes). I also tried to remove the substantive application of the RuntimeStrore through .abolish. When I do cela background threads perfectly but the user interface may not start because an Exception is thrown stating that

  application running in this process... However, this is not when I call the store of runtime. Any ideas as to what I'm doing wrong?

  Thanks in advance

  if(args.length>0 && args[0].equals("gui"))
          {
  
              System.out.println("Starting GUI");
              Controller controller=waitForSingleton();
              try{
              WhereAreYouMain app=new WhereAreYouMain(controller);
              app.enterEventDispatcher();
              }
              catch(Exception e)
              {
                  System.out.println("************EXCEPTION: "+e.getMessage());
                  return;
              }
          }
          else
          {
  
                  boolean AutoStart=true;
                  if(ApplicationManager.getApplicationManager().inStartup() && AutoStart)
                  {
                      System.out.println("********************STARTING WHEREAREYOU*************************");
                  Controller app=waitForSingleton();
                  System.out.println("****************************Started WhereAreYOU**********************");
                  }
              }
          }
  
      public static Controller waitForSingleton()
      {
          RuntimeStore store=null;
          store=RuntimeStore.getRuntimeStore();
          Controller controller=null;
          controller=(Controller)store.get(AppId);
          if(controller==null)
          {
              try{
  
              store.put(AppId, new Controller());
  
              }
              catch(Exception e)
              {
                  System.out.println("Error putting app in storage"+e.getMessage());
              }
          }
          return (Controller)store.get(AppId);
      }
      public static void removeFromRuntimeStore()
      {
          RuntimeStore store=RuntimeStore.getRuntimeStore();
          store.remove(AppId);
  
      }
      public WhereAreYouMain(Controller controller)
      {
          WhereAreYouMainScreen screen=new WhereAreYouMainScreen(controller);
          controller.setMainScreen(screen);
          pushScreen(screen);
      }
  

  When stop you your application, you also have to remove all listeners?  If one of them has a reference, your application will be not eligible for garbage collection and it will remain.

  I understand that this approach (to put the application in RuntimeStore) is actually used in some articles in the KB, but I wouldn't recommend it.

  Instead, I would say put you a small 'data only' RuntimeStore object, call this myRuntimeStore object.  I - this so that you can set a reference to your UiApplication in this document, for example. Have a myRuntimeStore.setMyApp (.) method.  Now your audience can get your app if they want, using myRuntimeStore.getMyApp ().  More importantly, you can erase it and make sure that your application will.  You may encode your listeners to do nothing if your application is not present.

  However, I would like to recommend more than you do not actually store references to your application.  If you need something to initiate treatment in your application process, use a global event.  This beautifully isolates your application of your listeners.

• Another Question regarding the IPC in the BB platform (secure process for RuntimeStore)

  In my scenario,.

  Process one will constantly be voicemails from somewhere and put it in a table in a RuntimeStore, named _store.

  B process, there is a thread T will waitFor the ID of the table in the _store. If succeeds, then copy to another location, i.e.,.

  persisting an object and then eaten after this, the thread will remove the ID of the table in the _store.

  I wonder if it is safe for both processes simultaneously access the _store.

  Wrote in the store. B is read and write to the store.

  If someone could help?  Very well appreciated.

  I am a bear with very little brain and can never remember the right way of doing things.  I'm sure that someone will take the holes in what follows and suggest the best ways and it would be fantastic.

  I think there are two issues here:

  (a) simultaneous access

  (b) persistence

  (a) the simultaneous access to an object in the persistent store are no different from any object, they are located in PersistentStore, RuntimeStore or RAM.

  Thus, for example, let's say we have a vector in PersistentStore, we use just like a queue to a single server (then only add to the tail and remove the head), with a separate 'lock' in RuntimeStore object.  Synchronize us on the lock object before we add an element, or remove an item, our access is perfectly safe

  (b) persistence

  Yes I agree, this aspect is not clear.  I always thought I want to commit an object placed partially updated, so in this example, would make the validation in the context of add or remove the treatment.

  Of course, things become a little more complicated if you start to talk about data updated in the queue, but I do not think that these problems are related to PersistentStore as a result, I think that these are issues of a general nature and there is probably many places on the web where are discussed different mechanisms to make sure that it works well.

  A few other points:

  (1) I understand that the treatment of validation is "atomic" on the BlackBerry and the "wound", so if you make an object you will persist all changes to this object. Usually, I maintain a collection that is associated with an Application for validation, points specific in the treatment of requests to ensure that the data associated with an application conform to the battery be fired immediately after a commit.

  (2) you can see updates of persistent objects, even if they are not posted.  These changes will be lost if they are not posted. So if you have a line like the one above, and two Clients add entries in the queue without committing, the server see the two entries in the queue until the battery is removed.  When the server restarts, the two went.

  Does that answer the question?

• Satellite L755 - 16 c - ODD can read CD but not DVD more

  I have a laptop Toshiba Satellite L755 - 16 c. The DVD that I ran on it before (installation of games, software, movies, etc.) is no longer detected by the DVD player. CD works for some reason any.

  Whenever I insert a DVD disc in the drive, the light flashes and I feel some movement and hear noises that occurs generally when a disc is entered and be read. However the content of the DVD player does not show. If I click open my computer's DVD player, the DVD is ejected and the computer asks me to enter a disc, as if there was no disc not inserted.

  I downloaded the latest BIOS files on their site, but nothing has changed.

  On this virtual path, it is not easy to say what the problem is here. First try to clean the lens. Objective is maybe dirty.
  Otherwise, it can be mechanical problem. Is that the position of the lens is different for the reading of the CD and DVD. There may be a problem with the calibration of the lens.

  Try to clean it first and post comments.

• which will cause 'notify() and wait()' mechanism no longer works?

  Hi all

  My application has worked for a few years, unless the user recently upgraded to OS7.1 and to try out my new device, all of a sudden, he is part works not properly.

  Appplcaition will download data from the server, long story Short,

  When there is no queue of download, application will wait until asked to download real.

  my code something like the follow up:

          InvokeContainer c = new InvokeContainer(r);
          synchronized (c.syncObj) {
              // push to queue
              synchronized (_queue) { _queue.addElement(c); }
              LogManager.getInstance().add("Notify queue Thread _queue size " + _queue.size());
              synchronized (_queueSyncObj) { _queueSyncObj.notifyAll(); }
              // wait for release
             // LogManager.getInstance().add("Invoke data wait to release");
              //synchronized(c.syncObj){
                  try { c.syncObj.wait(); } catch (Exception ex) {}
              //}
              LogManager.getInstance().add("Invoke data released");
          }
  

          while (!_stop) {
              InvokeContainer c = null;
  
              // wait for invoke
              c = getNextInvoke();
              if (c == null) {
                  LogManager.getInstance().add("Wait For next queue");
                  synchronized (_queueSyncObj) {
                      try {
                          _queueSyncObj.wait();
                          LogManager.getInstance().add("Invoked");
                      } catch (Exception ex) {
                          LogManager.getInstance().add("Exception happened: " + ex.toString());
                      }
                  }
                  c = getNextInvoke();
                  LogManager.getInstance().add("Get a new queue ");
              }
  

  My question is:

  my request always stop at the:

   LogManager.getInstance().add("Notify queue Thread _queue size " + _queue.size());
  

  and I saw there's a queue, waiting, however, the line after wait() never called.

  which will cause notify() citing not wait()?

  For me, in places, your code seems too complicated for what he seeks to achieve.  I'll try to simplify.

  First you have loads of protection around your creating a Singleton RuntimeStore object.  This seems pointless.  Take a look at this:

  http://supportforums.BlackBerry.com/T5/Java-development/create-a-singleton-using-the-RuntimeStore/TA...

  Go through your code, I wonder what follows:

  (1) public static synchronized IPCThread getServerInstance() {}

  Why is this it is synchronized?  Iron several people getting to this offers no additional protection.

  (2) synchronized (GlobalSync.getSyncObj (GUID))...

  This synchronized block offers no additional protection either.  Either the

  IPCThread will be there or it won't, there is no possibility of a race condition causes you a problem here.

  (3) public static synchronized IPCThread initServerInstance() {}
  synchronized (GlobalSync.getSyncObj (GUID)) {}

  Here, there might be some value to have only one person to create it at the same time.  But if it's a question, then the second person through should check if it has been created, this code is not.  Thus, each invocation of

  initServerInstance()

  will create and start a new IPCThread.  The synchronized are totally redundant and you have a potential hole in your treatment.

  (4) public synchronized static getInstance() {} IPCThread

  you have another way to get an IPCThread, which in fact is not identical to the above and, will be different if you start another instance of your Application, for example an alternative entry or a variant of starting.

  I recommend that you replace it with the unique getInstance() method based on article.  Do start the IPCThread if it creates.

  OK, I understand that you don't think that this is related to your problem, but with the code you have, there may be several IPCThreads and would not help.

  Now on your invocation code.

  Can you please remove static from the following:

  private static class InvokeContainer...

  As far as I KNOW, he does not buy you anything in this circumstance, and it confuses me.

  The idea here seems to be that you can provide an executable in this process, which it runs and then inform the task (if necessary) awaiting.  You pack the floor area in an InvokeContainer.

  The first thing to look at, it's how you entered extracting from the queue.  Here you protect with this line:

  synchronized (inasmuch)

  So what you're saying to me here, it's that you will protect this treatment in protecting access to the inasmuch.  Something we will add it to the queue. or something is going to take off it the queue, both may not occur at the same time.  That's ok.

  So how do add you to the queue?

  Ignoring the code that will process if the process id is the same, we get this:

  InvokeContainer c = new InvokeContainer (r);
  synchronized (c.syncObj) {}
  Push the queue
  synchronized (inasmuch) {_queue.addElement (c) ;}
  synchronized (_queueSyncObj) {_queueSyncObj.notifyAll () ;}
  wait for the release
  try {c.syncObj.wait () ;} catch (Exception ex) {}}
  }

  Now, we have already seen the queue is protected using "synchronized (inasmuch).  But this code will not prevent the entry we just added picked up before that we treat the notify - in other words, the notification cannot be taken into account.  But that's OK.  The reverse is not.  If the Thread that processes the code IPCThread is at this point:

  If (c == null) {}

  and the Thread that the addition of the transformation executes these two instructions:

  synchronized (inasmuch) {_queue.addElement (c) ;}
  synchronized (_queueSyncObj) {_queueSyncObj.notifyAll () ;}

  then the IPCThread will miss warn him.

  To fix this, I'll do what I suggested earlier.

  The way, this seems very strange:

  InvokeContainer c = new InvokeContainer (r);
  synchronized (c.syncObj) {...}

  but in fact, this means that the code will never fail of the treated IPCThread this practicable, since the notification

  synchronized (c.syncObj) {c.syncObj.notify () ;}

  Cannot run until this thread is waiting.  It's a good thing.

  So that leaves only one thing to discuss - the.invokeAsync.  This code looks good, if the

  synchronized (c.syncObj) {...}

  is completely redundant.

  Summary - 2 recommendations:

  (a) change your Singleton IPCThread to use the RuntimeStore method suggested in the KB article

  (b) check the inside of the protection of

  synchronized (_queueSyncObj) {}

  which

  c = getNextInvoke();

  is always set to null.

  Finally, have you thought about putting a delay time in your expectations, while without worrying about the activity or not, the Thread will pick up every now and again work?  For example:

  _queueSyncObj.wait (1000);

  Edit: Minor typo and readability...

• Interact with the Application in backup and restore?

  I use a persistent storage to save data in my application.  I would like to be able to retain these data for the upgrades of the device.  Suite How To - backup and restore of small amounts of data using SyncItem, I added another point of entry to my request and created a class that extends SyncItem.  I can now properly save and restore my data with Desktop Manager.

  At the start, my request has copy data storage persistent local data structures.  While it is running, it only reads and writes on these local structures.  At the exit, he empty local data in persistent storage.  For this reason, if my application is running during a restore, will overwrite the data in persistent storage, but my application continues to run with the obsolete data.  Ideally, I would like to say my request to re-read a persistent storage.  Can I call methods in my application?  In setSyncData, I tried to use UiApplication.getUiApplication () to get a reference to my application, but it throws a ClassCastException.  Any ideas?

  Thank you.

  UiApplication.getUiApplication () returns the application to the foreground, which can only be your app.  Instead, you can store a reference to your application in the RuntimeStore while it is running.  The restore process could then access the RuntimeStore object and call methods in your application to know that he has read the new, refreshed from the PersistentStore data.

  The RuntimeStore works in a way similar to the PersistentStore, with the exception that RuntimeStore data are not permanent (it is lost when the device is reset).

  Another approach is to alert the application using a GlobalEvent.

  What is - world events and global event listeners
  Article number: DB-00145

  http://www.BlackBerry.com/knowledgecenterpublic/livelink.exe/fetch/2000/348583/800332/800620/What_Is...

• Starts an application at startup of the BONE

  I need to know how to start an application when the operating system starts and makes it running in the background and listen to events assigned to the application.

  In properties, set the system App and Autostart.  Application of system, it have no icon.  If you want to have a UI and the bottom part of the application, create 2 projects.  The 1st has no flag set (this is the app icon) and the 2nd is defined as "another point of entry" to the main application.  The alternate entry point app has system and auto-start flags.  Add a parameter to the background app, i.e. "BG".

  In your main function, check the arguments.  If there are 0 arguments, the icon was clicked.  If there is 1 argument and it's 'BG', the background process started when the phone starts.  According to the arguments, instantiate a class of UiApplication (from the application icon) or an Application class (for the app in the background).

  Improve the substantive application a GlobalEventListener.  Then, he can listen to signals from the main application.  In addition, you can have listen for events from the call to run periodically on a timer, etc.

  Foreground and background applications can communicate using a RuntimeStore object or world events.

• Running the background (sms listening thread) connected to the GUI (another point of entry) application thread

  Hi, I'm new to the development of Blackberry, I read everything on the application running at startup and have a different point of entry for this application. I still need help with my application

  I use BB JDE 4.7

  Simulator: BB 9530 4.7.0

  I'm developing an application of SMS. (extends UiApplication)

  1) there is a thread that listens for incoming messages

  2) there is a wire which is a SMS sender

  3) there is a main screen and two full screens. for example, when the user clicks a button in one of the screens full... I send you a message

  (4) when a message is received, based on the content of the message I push either a full screen

  (5) I have, all the wires and screens as the class internal to the main class that extends from the UiApplication.

  I got the basic features. I need help making that demand the application of autostartup

  (1) I need to start listening to the sms thread when the BB phone starts

  (2) I need to have the application icon in the applications screen as another entry point for the application (only for the GUI), and the listening thread must remain active in the background.

  (3) when an incoming message is detected, the application GUI should be brought to the foreground (if it isn't already forground) after posting a popup (instead of bring the application to the foreground, is it better to display a flashing icon in the status bar of the home screen blackberry and perhaps global popup)

  (4) when the GUI of the application part is closed, I need to stop the sms sending thread, and when the system shuts down, I need to stop the listening thread.

  Please help me guys... I have read many articles and discussions regarding the automatic start-up of applications, another point of entry, the # of background threads...

  but I couldn't find how to implement my needs.

  (1) should I need to create two different projects (applications [GUI thread, a sender] and one for the listening thread)? or I can achieve in single application?

  (2) should I have to sign in the background thread to the GUI app? If so, how?

  (3) it is necessary to use the RunTimeStore object? If so, I don't know how I can bring to the foreground the application GUI of the background thread.

  (4) if I have to stop the thread of listening by overiding onExit() method, the important question I have is, if the onExit() method is only for applications that extends from the Application class and not for the UiApplication class?

  (5) if I should have two projects (one main and the other as a spare point entry), which project should I do as "autorun at startup" and a "system module".

  As I need to have the background still running thread when the GUI application is active. I don't know how I do.

  Hello world...

  I reached my needs thanks to a single application. I used an other entry point.

  To refer to chk my other post

  http://supportforums.BlackBerry.com/T5/Java-development/how-to-avoid-creating-two-instances-of-the-a...

• Doc / leaves / snow to freeze when I load my custom application

  I have a custom, application that has a different point of entry and runs in the background and the foreground.

  I compiled with JDE 4.6.0 and am he works on "BOLD" with o/s 4.6.0.126.

  For some reason when I have download and install my application, he launched immediately even though I didn't click on

  on 'run '.  This behavior is different from that shown in the 4.2.x JDE

  Anyway, the main question is after the download of my application, Docs to Go and 2 other applications do not respond.

  Only these applications fail, but all other applications work fine.

  Has anyone else had problems of compatibility with their applications and Docs/sheets/slides to go?

  There was a bug in my code. It was because of enterEventDispatcher() called while holding down a synchronization lock

  on the RuntimeStore object.

• Apply the hotfix using ADOPTION in R12.2.4

  Hi all

  EBS R12.2.4

  OEL 6.5

  11 GR 2

  The consultant encoutered issue in the setup and asked me to apply the p18955265_R12 patch. HZ. C_R12_GENERIC.

  I want to apply this fix by using "adoption." I understand that in R12.2.4, you can not apply a patch using adpatch? but only adopt?

  Patch adoption cycles mentioned the following:

  Phases:

  adoption phase = prepare-> copy the code of the application

  adoption phase =-> apply patch in PATCH environment

  adoption phase = finalize-> makes it ready for the failover system

  adoption phase = failover-> bounce the transition to the system of system files and. FS2 becomes runtime environment.

  adoption phase = cleaning-> withdrawal of obsolete objects.

  adoption phase = fs_clone-> synchronize file systems

  Do I have to perform the steps above to apply the p18955265_R12 hotfix. HZ. C_R12_GENERIC?

  Thanks a lot for your kind cooperation.

  MK

  MariaKarpa (MK) wrote:

  Thanks hussein,.

  I think that these phases are carried out in complete sequence if you apply major patches as 12.2.2 12.2.3 and 12.2.4?

  Well, these phases are applicable to the 12.2.x

  Thank you

  Hussein

• FileWriter replacement option?

  I'm using FileWriter (within a stream) to write metadata to a file that will be read by another stream. There is much documentation for information on using FileWriter to write to a file, https://communities.vmware.com/thread/421819

  but that adds data to a file if the file already exists.

  I would like to replace the file.

  I do not want to write each successive entry in a single file called (for example, appended to the name) because it will create problems for future traffic waiting for a specific file location name as source.

  I see references to javascript filewrite indicating a second Boolean is available (FileWrite (outputFile, boolean)) in which the default value (value is is to replace and add a value 'false', but this doesn't seem to be the case with our use of the vCO.) I tried passing the Boolean values as the second parameter, and they have no net effect.

  I would consider with vCO issue a command 'remove' the file before writing, however, what I've read (not sure if this applies to the vCO) there are concerns about the use of javascript to remove the files from the file system.

  Thoughts?

  
  

  Just use the clean() on the fileWriter object method.

• White screen on playback StageVideo iPad 2, can it be controlled?

  Hello

  I'm currently building an application where the substance of the request is a video loop by using the StageVideo API. The video plays very well and works well, however, there are cases where the video will get interrupted (and therefore displays a white screen). One of these cases include double tapping the key home on the iPad, the attempt to switch between apps. When the screen slides up to reveal the applications currently available, the video stops playing and the screen turns white. Another case is when the iPad receives a notification or alert. When this happens, the video stops playing and the screen turns white. Finally, I tested it on two iPads (a Verizon and AT & T). When you enter in any view that this video game, the AT & T of the iPad 2 is expected to Flash a white screen quickly before playing the video. However, on the iPad from Verizon that does not happen.

  I would like to know if there is a way that this can be controlled, so that I can produce a consistent behavior across devices. Would be set using real persistNavigatorState? Or should I be posting for some sort of status on the StageVideo instance?

  What are your thoughts?

  Thanks in advance for your help.

  I actually found what was wrong. On my "viewDeactivate" activity, I cleaned all the references object (including the StageVideo instance). So every time that viewDeactivate has been sent, the white screen white show.

  For all those who throws herself into this situation (on the iPad), you know that the viewDeactivate event is sent not only when moving between views, but also when popup for alerts (or notifications), when she is going back to the home screen, and also when you double press the button of the multitasking bar. Similarly, the viewActivate event fires when you return to any of the States mentioned above on the iPad, not only when moving between views. Knowing this helped me to solve the problem, I was faced with StageVideo.

  Hope this helps someone.

• Java API - finalize the method for XmlResults

  Hello!
  
  I wonder why, in the Java XML DB code, we have a finalize() method that calls the delete() method while we are supposed to call the method delete() manually (according to the documentation). Is this ok if the delete() method is called twice (it happens where GC clean up the XmlResults object)? Can't get us a few problems because of this?
  
  Thank you
  Vyacheslav

  Finalize() is called by the garbage collector of Java before it cleans the object, because the garbage collector may be slow to clean up objects, or can clean them out of use (cleaning a container before cleaning the XmlResults which access), you must call the delete() function manually.

  Several calls to delete() don't matter, after the first call records function as the memory is removed and does not attempt to remove it again.

  Lauren Foutz