Clustering of JMS vs distributed Destinations / persistent stores and failover

Similar Questions

• Persistent [store and String]

  I am fairly new to the BlackBerry development but have a vast experiece in c# so I understand the syntax, but I'm having a hard time getting an array of String to save in the persistent store.

  Here's a piece of my constructor code:

  pObjet = PersistentStore.getPersistentObject (key);
   
  If (pObject.getContents () is nothing)
  {
  sFriendList = new String() {"no friends added"};
  pObject.setContents (sFriendList);
  }
  on the other
  {
  sFriendList = (String []) pObject.getContents ();
  }
    
  Add (olfList);

  olfList.set (sFriendList);

  Here is the custom method that is called the closure of my custom screen:

  public void AddFriendCallback (String sFriend)
  {
  String [] NewArray;
    
  If (sFriendList [0] .equals ('no friends added"))
  {
  NewArray = new String() {sFriend};
  }
  on the other
  {
  NewArray = new String [sFriendList.length + 1];
     
  for (int i = 0; i)< sfriendlist.length;="">
  {
  NewArray [i] = sFriendList [i];
  }
     
  NewArray [NewArray.length - 1] = sFriend;
  }
    
  sFriendList = NewArray;
  olfList.set (sFriendList);
  }

  And here is my saving method:

  public void save() throws IOException
  {
  pObject.commit ();
  }

  Everything works fine until I try to write the data to store and reopen the form. When I open it the screen is like nothing has been added to the store. He said still "no added friend. Anyone know what I am doing wrong?

  Thanks in advance!

  I thought about it. Just after the olfList.set (sFriendList); line in my callback method, that I had to do the following:

• JMS distributed Destinations &amp; queues in a clustered environment

  I'm a little confused trying to configure the JMS subsystem for my application.
  
  I am migrating my configuration of WLS8.1-> 11 g and rather than use the migration tools, I created from scratch.
  
  We have 4 JAVA virtual machine in a cluster with a store server and JMS queue on each server. The JMS servers are called JMS01, JMS02, JMS03 and JMS04
  
  We use destinations spread to most of the lines that cater to all JMS servers 01-04, but there are a set of queues "pins" where a group of intended to JMS01, one other group is intended for the JMS02 and so on.
  
  Thus, we distributed destinations targeted at JMS01, 2, 3, 4
  
  and
  
  1 JMS destination group, for the JMS01
  Destination JMS 2 group, for the JMS02
  Destination JMS 3 Group, for the JMS03
  JMS 4 destination group, for the JMS04
  
  Someone would be able to give me some advice on creating this configuration with modules and subdeployments in 11g?
  
  Pete

  Hi Peter,.

  I highly recommend reading [JMS Configuration recommended | http://download.oracle.com/docs/cd/E15523_01/web.1111/e13738/best_practice.htm#CACJCGHG] and therefore recommend the establishment of 5 modules, each with a single 'subdeployment. A module/subdeployment each for JMS1, 2, 3 and 4 and an additional which refers to all 4 JMS servers. Alternatively, you can put all configurations in a single module that relies on multiple subdeployments, but this tends to be much more difficult to manage and understand over time (for example, its easier to keep a one-to-one correspondence between module and subdeployment). The "Best Practices" chapter is new to 11gR1PS1/10.3.2, but the advice applies to all the way back to version 9.0.

  In the case where you already did, I also recommend to get hold of the new book "Professional WebLogic"

  Hope this helps,

  Tom

• JMS persist Store: how to store the messages in a table?

  Hi all
  
  I'm looking to create a composite that stores messages to a JMS queue on a custom table created. Please advise if the following approach is correct.
  
  1 has created a table within the dev soainfra: TEST_TABLE
  2 created a wls data source to point to the table: TestDS
  3. has created a persistent store based on above data source: TestStore
  4. has created a server with TestStore JMS in the persistent store: TestServer
  5 has created a JMS Module and the queue to the breast (* TestMod * & jms/TestQueue) it addressed to the TestServer.
  
  I created a JMS in my composite adapter configured to use my queue jms/TestQueue. The JNDI name used for the JMS adapter is the environmental assessment environmental/wls/queue.
  
  I ran a test and see nothing in my table. Is there something that I missed?
  
  JDev version: 11.1.1.4
  
  Thank you and best regards.

  in response to

  Also, how you consume messages from this table when the data is to the LONG RAW format?

  You do not have. It is an integral part of WLS JMS. You consume messages using a JMS consumer, whether another instance of the adapter or another java client. If you start deleting messages from this table manually, you will mess up JMS and cause of exceptions. I suggest you leave well alone.

• iCal - * terminating app due to an untrapped exception 'NSInternalInconsistencyException', reason: 'this NSPersistentStoreCoordinator has no persistent store (unknown).  He is unable to perform a backup operation

  About a month after moving to OS X 10.11.3 calendar application does not load. I thought that ~/Library/Containers/com.apple.iCal deletion would empty it. I no longer get the error earlier, even if it also started with the ApplicationSpecificInformation:

  * End app because of the untrapped exception 'NSInternalInconsistencyException', reason: 'this NSPersistentStoreCoordinator has no persistent store.  He is unable to perform a backup operation

  Don't know what to do next to timing of recovery. Can someone give me some pointers?

  Thank you

  Process: Calendar [980]

  Path: /Applications/Calendar.app/Contents/MacOS/Calendar

  ID: com.apple.iCal

  Version: 8.0 (2092.2)

  Generation information: iCal-2092002000000000 ~ 70

  Code type: X 86-64 (Native)

  Parent process:? [1]

  Manager: Calendar [980]

  User ID: 501

  Date/time: 2016-02-13 21:05:17.964-0700

  OS version: Mac OS X 10.11.3 (15 d 21)

  Report Version: 11

  Anonymous UUID: EFEF6C45-F9F8-9E0B-6C80-8622F8520537

  Time since started awake: 410 seconds

  Integrity of system protection: enabled

  Crashed thread: 0 dispatch queue: com.apple.main - wire

  Exception type: EXC_CRASH (SIGABRT)

  Exception codes: 0 x 0000000000000000, 0 x 0000000000000000

  Note the exception: EXC_CORPSE_NOTIFY

  Request for clarification:

  Reason for termination due to an untrapped exception 'NSInternalInconsistencyException' app,: ' this NSPersistentStoreCoordinator has no persistent store (unknown).  He is unable to perform a backup operation. »

  ending with an exception uncaught of print type

  Abort() called

  Specific application Backtrace 1:

  0 CoreFoundation 0x00007fff84644ae2 __exceptionPreprocess + 178

  1 libobjc. A.dylib 0x00007fff8a95bf7e objc_exception_throw + 48

  CoreData 0x00007fff8c524fd3 2-[NSPersistentStoreCoordinator _coordinator_you_never_successfully_opened_the_database_so_saving_back_to_it_is _kinda_hard:] + 51

  3 CoreData 0x00007fff8c5251ed-[NSPersistentStoreCoordinator _introspectLastErrorAndThrow] + 77

  4 CoreData 0x00007fff8c5253b1 __65-[NSPersistentStoreCoordinator executeRequest:withContext:error:] _block_invoke + 321

  5 CoreData 0x00007fff8c530b63 gutsOfBlockToNSPersistentStoreCoordinatorPerform + 179

  6 libdispatch.dylib 0x00007fff86f4b33f _dispatch_client_callout + 8

  7 libdispatch.dylib 0x00007fff86f4c926 _dispatch_barrier_sync_f_invoke + 74

  8 CoreData 0x00007fff8c51f662 _perform + 194

  9 CoreData 0x00007fff8c4635c5-[NSPersistentStoreCoordinator executeRequest:withContext:error:] + 533

  10 CoreData 0x00007fff8c4635f4-[NSPersistentStoreCoordinator executeRequest:withContext:error:] + 580

  11 CoreData 0x00007fff8c48e6da-[NSManagedObjectContext save:] + 890

  12 CalendarPersistence 0x00007fff9090ba47-[CalManagedObjectContext save:] + 71

  13 CalendarPersistence 0x00007fff90ab9221 + [CalPersistence createBirthdayCalendar:error:] + 251

  Calendar calendar 14 0x00000001021a5f66 + 278374

  15 calendar 0x00000001021a5852 + 276562

  Calendar calendar 16 0x00000001021a56f3 + 276211

  Calendar calendar 17 0x00000001021a54ef + 275695

  18 libdispatch.dylib 0x00007fff86f56871 _dispatch_call_block_and_release + 12

  19 libdispatch.dylib 0x00007fff86f4b33f _dispatch_client_callout + 8

  20 libdispatch.dylib 0x00007fff86f5ec1d _dispatch_main_queue_callback_4CF + 1685

  21 0x00007fff8458acd9 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9 CoreFoundation

  22 CoreFoundation 0x00007fff84545d3d __CFRunLoopRun + 1949

  23 CoreFoundation 0x00007fff84545338 CFRunLoopRunSpecific + 296

  24 HIToolbox 0x00007fff85f26935 RunCurrentEventLoopInMode + 235

  25 HIToolbox 0x00007fff85f2676f ReceiveNextEventCommon + 432

  26 HIToolbox 0x00007fff85f265af _BlockUntilNextEventMatchingListInModeWithFilter + 71

  27 AppKit 0x00007fff892a60ee _DPSNextEvent + 1067

  28 AppKit 0x00007fff89672943-[NSApplication _nextEventMatchingEventMask:untilDate:inMode: dequeue:] + 454

  AppKit 29 0x00007fff8929bfc8-[NSApplication run] + 682

  30 AppKit 0x00007fff8921e520 NSApplicationMain + 1176

  Calendar calendar 31 0 x 0000000102164027 + 8231

  32 libdyld.dylib 0x00007fff81d985ad start + 1

  Thread 0 crashed: Dispatch queue: com.apple.main - wire

  0 libsystem_kernel.dylib 0x00007fff8c43f002 __pthread_kill + 10

  1 libsystem_pthread.dylib 0x00007fff8fea85c5 pthread_kill + 90

  2 libsystem_c.dylib 0x00007fff952726e7 demolition + 129

  3 libc ++ abi.dylib 0x00007fff833d6f81 abort_message + 257

  4 libc ++ abi.dylib 0x00007fff833fca47 default_terminate_handler() + 267

  libobjc 5. A.dylib 0x00007fff8a95e6ae _objc_terminate() + 103

  6 libc ++ abi.dylib 0x00007fff833fa19e std::__terminate (void (*) ()) + 8

  7 libc ++ abi.dylib 0x00007fff833fa213 std::terminate() + 51

  8 libdispatch.dylib 0x00007fff86f4b353 _dispatch_client_callout + 28

  libdispatch.dylib 9 _dispatch_main_queue_callback_4CF + 1685 0x00007fff86f5ec1d

  10 com.apple.CoreFoundation 0x00007fff8458acd9 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9

  11 com.apple.CoreFoundation 0x00007fff84545d3d __CFRunLoopRun + 1949

  12 com.apple.CoreFoundation 0x00007fff84545338 CFRunLoopRunSpecific + 296

  13 com.apple.HIToolbox 0x00007fff85f26935 RunCurrentEventLoopInMode + 235

  14 com.apple.HIToolbox 0x00007fff85f2676f ReceiveNextEventCommon + 432

  15 com.apple.HIToolbox 0x00007fff85f265af _BlockUntilNextEventMatchingListInModeWithFilter + 71

  16 com.apple.AppKit 0x00007fff892a60ee _DPSNextEvent + 1067

  17 com.apple.AppKit 0x00007fff89672943-[NSApplication _nextEventMatchingEventMask:untilDate:inMode: dequeue:] + 454

  18 com.apple.AppKit 0x00007fff8929bfc8-[NSApplication run] + 682

  19 com.apple.AppKit 0x00007fff8921e520 NSApplicationMain + 1176

  20 com.apple.iCal 0 x 0000000102164027 0 x 102162000 + 8231

  21 libdyld.dylib 0x00007fff81d985ad start + 1

  Thread 1:

  0 libsystem_kernel.dylib 0x00007fff8c43f6de __workq_kernreturn + 10

  1 libsystem_pthread.dylib 0x00007fff8fea6729 _pthread_wqthread + 1283

  2 libsystem_pthread.dylib 0x00007fff8fea4365 start_wqthread + 13

  Thread 2: Dispatch queue: com.apple.libdispatch - Manager

  0 libsystem_kernel.dylib 0x00007fff8c43fff6 kevent_qos + 10

  1 libdispatch.dylib 0x00007fff86f51099 _dispatch_mgr_invoke + 216

  2 libdispatch.dylib 0x00007fff86f50d01 _dispatch_mgr_thread + 52

  3 wire:

  0 libsystem_kernel.dylib 0x00007fff8c43f6de __workq_kernreturn + 10

  1 libsystem_pthread.dylib 0x00007fff8fea6729 _pthread_wqthread + 1283

  2 libsystem_pthread.dylib 0x00007fff8fea4365 start_wqthread + 13

  Thread 4:

  0 libsystem_kernel.dylib 0x00007fff8c43f6de __workq_kernreturn + 10

  1 libsystem_pthread.dylib 0x00007fff8fea6729 _pthread_wqthread + 1283

  2 libsystem_pthread.dylib 0x00007fff8fea4365 start_wqthread + 13

  Wire 5:

  0 libsystem_kernel.dylib 0x00007fff8c43f6de __workq_kernreturn + 10

  1 libsystem_pthread.dylib 0x00007fff8fea6729 _pthread_wqthread + 1283

  2 libsystem_pthread.dylib 0x00007fff8fea4365 start_wqthread + 13

  Line 6:

  0 libsystem_kernel.dylib 0x00007fff8c43f6de __workq_kernreturn + 10

  1 libsystem_pthread.dylib 0x00007fff8fea6729 _pthread_wqthread + 1283

  2 libsystem_pthread.dylib 0x00007fff8fea4365 start_wqthread + 13

  Line 7:

  0 libsystem_kernel.dylib 0x00007fff8c43f6de __workq_kernreturn + 10

  1 libsystem_pthread.dylib 0x00007fff8fea6729 _pthread_wqthread + 1283

  2 libsystem_pthread.dylib 0x00007fff8fea4365 start_wqthread + 13

  Thread 8:

  0 libsystem_kernel.dylib 0x00007fff8c43f6de __workq_kernreturn + 10

  1 libsystem_pthread.dylib 0x00007fff8fea6729 _pthread_wqthread + 1283

  2 libsystem_pthread.dylib 0x00007fff8fea4365 start_wqthread + 13

  Wire 9:

  0 libsystem_kernel.dylib 0x00007fff8c43f6de __workq_kernreturn + 10

  1 libsystem_pthread.dylib 0x00007fff8fea6729 _pthread_wqthread + 1283

  2 libsystem_pthread.dylib 0x00007fff8fea4365 start_wqthread + 13

  Thread 10:

  0 libsystem_kernel.dylib 0x00007fff8c43f6de __workq_kernreturn + 10

  1 libsystem_pthread.dylib 0x00007fff8fea6729 _pthread_wqthread + 1283

  2 libsystem_pthread.dylib 0x00007fff8fea4365 start_wqthread + 13

  Wire 11:

  0 libsystem_kernel.dylib 0x00007fff8c43f6de __workq_kernreturn + 10

  1 libsystem_pthread.dylib 0x00007fff8fea6729 _pthread_wqthread + 1283

  2 libsystem_pthread.dylib 0x00007fff8fea4365 start_wqthread + 13

  12 wire:

  0 libsystem_kernel.dylib 0x00007fff8c43f6de __workq_kernreturn + 10

  1 libsystem_pthread.dylib 0x00007fff8fea6729 _pthread_wqthread + 1283

  2 libsystem_pthread.dylib 0x00007fff8fea4365 start_wqthread + 13

  Line 13: com.apple.NSEventThread

  0 libsystem_kernel.dylib 0x00007fff8c439386 mach_msg_trap + 10

  1 libsystem_kernel.dylib 0x00007fff8c4387c7 mach_msg + 55

  2 com.apple.CoreFoundation 0x00007fff84546624 __CFRunLoopServiceMachPort + 212

  3 com.apple.CoreFoundation 0x00007fff84545aec __CFRunLoopRun + 1356

  4 com.apple.CoreFoundation 0x00007fff84545338 CFRunLoopRunSpecific + 296

  5 com.apple.AppKit 0x00007fff89365065 _NSEventThread + 149

  6 libsystem_pthread.dylib 0x00007fff8fea6c13 _pthread_body + 131

  7 libsystem_pthread.dylib 0x00007fff8fea6b90 _pthread_start + 168

  8 libsystem_pthread.dylib 0x00007fff8fea4375 thread_start + 13

  Thread 14:

  0 libsystem_kernel.dylib 0x00007fff8c43f6de __workq_kernreturn + 10

  1 libsystem_pthread.dylib 0x00007fff8fea6729 _pthread_wqthread + 1283

  2 libsystem_pthread.dylib 0x00007fff8fea4365 start_wqthread + 13

  Thread 15: com.apple.appkit - heartbeat

  0 libsystem_kernel.dylib 0x00007fff8c43f206 __semwait_signal + 10

  1 libsystem_c.dylib 0x00007fff95293d17 nanosleep + 199

  usleep libsystem_c.dylib 2 0x00007fff95293c0a + 54

  3 com.apple.AppKit 0x00007fff894ff6f4-[NSUIHeartBeat _heartBeatThread:] + 2181

  4 com.apple.Foundation 0x00007fff92cbdc6f __NSThread__start__ + 1351

  5 libsystem_pthread.dylib 0x00007fff8fea6c13 _pthread_body + 131

  6 libsystem_pthread.dylib 0x00007fff8fea6b90 _pthread_start + 168

  7 libsystem_pthread.dylib 0x00007fff8fea4375 thread_start + 13

  Thread 0 crashed with X 86 State of Thread (64-bit):

  Rax: 0 x 0000000000000000 rbx: 0000000000000006 rcx 0 x: 0x00007fff5da9be28 rdx: 0 x 0000000000000000

  RDI: 0x000000000000160b rsi: 0 x 0000000000000006 PBR: RER 0x00007fff5da9be50: 0x00007fff5da9be28

  R8: 0 x 0000000000000003 r9: 0x00007fff833fda7c r10: 0 x 0000000008000000 r11: 0 x 0000000000000206

  R12: 0x00007fff5da9bfb0 r13: 0x0000000103001b40 r14: 0x00007fff746a1000 r15: 0x00007fff5da9be90

  RIP: 0x00007fff8c43f002 rfl: 0 x 0000000000000206 cr2: 0x00007fff7554a008

  Please, back up all data. If you have iCloud calendars, archive them by following the instructions on this page under the heading "download a calendar of iCloud.com." all you need is a web browser, not the calendar application. Do the same with the other calendars of network you have, if possible.

  Before taking each of these steps, quit (leave by force if necessary) application. After taking stage, recovery and test. When the problem is solved (or when you have completed step 3 without resolving), stop and close the library folder.

  Step 1

  Hold down the option key and select

  Go ▹ library

  in the Finder menu bar. In the folder that opens, move these items (some may not exist) to the trash, leaving the open library folder:

  Calendars/calendar Cache

  Calendars/calendar Cache-shm

  Calendars/calendar Cache-wal

  Step 2

  Move these files to the library folder on the desktop (even once, some cannot exist):

  Containers/com.apple.CalendarAgent (and all others with a start of name in 'com.apple.Calendar')

  Containers/com.apple.iCal (and all others with a name in 'com.apple.iCal' beginning)

  Preferences/com.apple.CalendarAgent.plist

  Preferences/com.apple.iCal.plist

  If the problem is resolved, you may be able to put some of the items you have moved in this stage, recovery and testing after each of them. Finally, you can find the one that caused the problem; Delete it. Re-create your settings if necessary.

  If the problem is not yet solved, put back to each of the points you have moved in this step, crushing the that may have been created in its place. Do not put the files that you moved in step 1.

  Step 3

  Move this folder on the desktop:

  Calendars

  Note: you do not move the application to calendars; you move a folder named "calendars". If there is no change, put the folder back where he was.

  If the problem is resolved after you move the calendars folder, the event database is corrupted. You have these choices:

  Restore the snapshot folder Time Machine or another backup prior to corruption.

  Use a third party application like "Calendar cleaner" (not tested by me) to try to repair the database.

  For the calendar network accounts, such as iCloud, all you need to do is re-enter the preferences. For subscribed calendars, simply re - subscribe.

• can we save the bitmap to persistent store?

  City previous forums:

  Smiley Messages: 29 From: Canada Join date: May 2008	can we save the bitmap to persistent store? Posted the: July 14, 2008 12:41	Response
  	I am trying to save a bitmap in Bank persistence and get an error msg saying Bitmap is not persistent. is it possible to save a bitmap? Thank you

  Yes it is possible.  You can use the Bitmap.getARGB method to get an array of bytes of the Bitmap image.  Then store its contents in a ByteVector.

  I am aware of the problem and would use a solution like that set up by MiuTunes.  Basically, generating thumbnails on the front and store them on the SD card.

  As neil says, there is a small performance lag, compared, but I find personally unacceptable in this application.  Don't know what you develop, and perhaps there are moments where in memory is better.  I'm also assuming (wrongly?) that you were going to leave them in the persistent store after your application ends.  Anyway, Neil knows more about what I do.

• Persistent Store - is this good or bad idea?

  Currently, I have setup an application with a vector of objects that I store, works great!  For my next request, I want to save more information and thought of different ways to do this.  This first one saves a whole bunch of a single type of object...

  I want to create 3 vectors over other types of objects I created... I thought I could store each vector with id different, maybe I could make a vector of vectors, or maybe make another object that has inside and just vectors that store... examples below:

  the idea of vectors vector

  Vector vectorOfAObjects;

  Vector vectorOfBObjects;

  Vector vectorOfCObjects;

  Vector vectorOfDObjects;

  Vector storeMyVectors;

  storeMyVectors.insertElementAt (vectorOfAObjects, 0);

  storeMyVectors.insertElementAt (vectorOfBObjects, 0);

  storeMyVectors.insertElementAt (vectorOfCObjects, 0);

  storeMyVectors.insertElementAt (vectorOfDObjects, 0);

  and then to get my stuff back, I would use storeMyVectors.elementAt (0) to return vectorOfAobjects...

  I thought I could do as an object that contained the four vectors as fields... like

  class relatedVectors implements {persistable

  Vector vectorOfAObjects;

  Vector vectorOfBObjects;

  Vector vectorOfCObjects;

  Vector vectorOfDObjects;

  relatedVectors (vector a, vector b, vector c, vector d) {}

  vectorOfAObjects = a;

  vectorOfBObjects = b;

  vectorOfCObjects = c;

  vectorOfDObjects = d;

  }

  }

  Finally, could I simply store different types of objects in the same vector, keeping the tack of indexing point?  For some reason any I have in my head a vector must be of the same type of object, but I don't think it's true...  In this case, I could do a vector and the index 1, 5, 9, etc... Once object type and 2, 6, 10 other etc...

  What idea is the best?

  Thank you!

  Vector objects are not the same.  Mix them as you like.

  Re have one or several store ID persisting, I actually don't think it's important.  I have found that if you update some of the vector, then commit, it does not take too long - I think that only the modified part commits again.  Replacement of the entire vehicle with a completely new would have more load.

  The design basically your data store around the needs of your application, rather than worrying about the consequences this will have on the device.

  BUT, a big concern.

  Remember that the objects that you save in the persistent store must remain the same to be accessible, if persist you an object with 2 integer values, then change this class so that there are three integer values, then your persistent object becomes illegible.  So try to future proof your persistent objects or design a path for them.

• Editing an object that I stored in the persistent store

  I store a custom object in the store persistent and would like to add a new Member.  Someone knows how can I do this?  I'd rather not delete it and store an object in its place because what happens if I need to add more members in the future.  This would encourage me to juggle all versions of my object.  Is there a kind of model for version control that I can apply to my objects stored persistently?

  I don't think it will work.  The link that you say talk us too much serialization, but the persistent object is not serialized as part of persistence.  If you want to serialize her, you should do it yourself.

  I'm guessing that you did not design your class being "expandable". And I'm guessing that you do not want your users to have to recreate these data.

  So I investigate an approach to migration.  In the code that gets the persistent store, got it get the object persistent, then check that it is indeed a picture of your old items.  If it is, convert it to an object type, store it in a collection (vector or Hashtable as suggested, for example) and keep the result, by replacing your old array of persistent storage object.  So your new application includes the old class of objects, exactly as it was, which means that you can install it on top of your existing application.  But once your request is used at the same time, the old persistent object is no longer used.

  Does make sense?

• How does the synchronization, the persistent store

  I have number of persistent store for the storage of data, etc.

  When I handle a store (addition, deletion or update), should I need to block the manipulation on another store?

  as there is no reviews for the class being thread-safe, I suggest that you synchronize access yourself.

• Update the persistent store

  Hi all

  I am a soft developer for BB. I need a little clarification. Is it possible to update the data stored in the persistent store? Pls answer...

  Thank you in advance...

  Welcome on the support forums.

  If you commit something to the store, you replace the existing value. of course, you can read the existing value and change it before you engage again, or commit any other thing.

• How to store and retrieve long values in the store persistent

  Hello

  In my application I want to store and retrieve long values in the persistent store that I used with Longvector and all is well, but LongVector is supported for operating system > = 4.6

  I need to work my request in 4.5 also, can any one infrom me what are the other alternatives, I have to get my pls any abstract requirement...

  Vector v = new Vector();
  fill vector
  Long premierElement = (Long) v.firstElement ();
  myLong long = firstElement.longValue ();

• store an entire class in persistent store?

  I need to store a set of many parameters in the persistent store. I wonder if it is possible to create a class that contains all the settings and get an instance of the class into the store, instead of putting every parameter in the store separately. The questions are:

  1 is it possible?

  2. If so, are there performance issues with the storage of an instance of the class, or any other concers?

  Thank you

  1 Yes its possible, you must make sure that your class extends the persistable interface

  2. Yes, there are performance concerns and limitations in number of handles object that you could use on some operating systems... see these articles for a more detailed explanation:

  http://www.BlackBerry.com/knowledgecenterpublic/livelink.exe/fetch/2000/7979/1181821/832210/Memory_b...

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

• Memory persist Store isn't getting released.

  Hi all

  help please!

  biggg memory problem...

  I have developed an application that uses the persistent store...

  as suggested by peter_strange here

  http://supportforums.BlackBerry.com/T5/Java-development/how-to-delete-persistent-store-when-app-is-U...

  I uninstalled the app, but no use. The memory is not released. For the newly installed also, application the memory block allocate comes in action game. Can't detect the application startup, where there is no data at all.

  am store an array of vectors in the persistent store.

  Is so the vector you store specific to your Application - in other words, it is a class that extends the vector that is defined in your Application?

• increase the size of an array stored in the persistent store

  Hello

  I have a question.  I use the persistent store to store the data.

  When there is a new medium, I need to add it in this table.

  The problem is the size of the table is fixed, how do I re - set the size of the array? and save the persistent store return?

  Thank you

  Yes, vector will be better because you can't copy items.

  If you use the simple table of data types would be more effective, I think, you can take a look at Arrays.fill, then.

  No referenced objects are captured by garbage collection.

• issue of chain vacuum persistent store

  Hello

  I have an application that uses data from a persistent store location. These data are stored in an array of strings. Unfortunately, I made the mistake of allowing a user to save a blank. When this happens, I get an error al load time "empty string eception exception" as always, the application waits for an entry to be present.

  Is it possible to revisit loadtime if one of the persistent object fields is empty and default highlight? I tried the following code, but it does not work:

  protected void GetLocation(){
  
          synchronized(perStore) {
  
              String[] currentinfo = (String[])perStore.getContents();
              if(currentinfo == null) {
              return;
              }
              if(currentinfo[0] == ""){
                      currentinfo[0] = "0";
                  }   
  
              else{
                  edtLong.setText(currentinfo[0]);
                  edtLat.setText(currentinfo[1]);
                  edtTZ.setText(currentinfo[2]);
                  rbgLong.setSelectedIndex(Integer.parseInt(currentinfo[3]));
                  rbgLat.setSelectedIndex(Integer.parseInt(currentinfo[4]));
                  rbgTZ.setSelectedIndex(Integer.parseInt(currentinfo[5]));
                  rbgHemisphere.setSelectedIndex(Integer.parseInt(currentinfo[6]));
              }
              }
  
      }
  

  Any help appreciated.

  "it does not work: '-in what it does not work?

  Here's a suggested code:

  Object o = perStore.getContents ();

  If (o == null) {}

  ...

  } else

  If (!) o instanceof (String [])))) {}

  .....

  } else {}

  String [] currentinfo = o (String []);

  If (currentinfo.length! = 7) {}

  ...

  } else {}

  for (int = 0; i< currentinfo.length;="" i++="" )="">

  FIR (currentInfo [i] == null) {}

  CurrentInfo [i] = "";

  }

  }

  }

  }