Databases
StackOverflow2013
Postsdbo
POReturn an Object in a thread safe class
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POReturn an Object in a thread safe class
    primarykey
    data
    text
    <p>I am having a problem that appears to indicate Java objects aren't created on the heap I expected. The short version is that I have a JMS onMessage() method that is calling another method to instantiate the proper object (routingCommand) based on the JSon payload of the TextMessage.</p> <pre><code> public void onMessage(Message message) throws RuntimeException { IRoutingCommand routingCommand = null; routingCommand = instantiateRoutingCommand(message); ... process(routingCommand); } private IRoutingCommand instantiateRoutingCommand(Message message) { IRoutingCommand routingCommand = null; ... lots of code to build the correct type of RoutingCommand routingCommand = new IeRoutingCommand(ieNotification); return routingCommand; } </code></pre> <p>The problem is that during my load test, on Extremely Rare occasions, the same JMS message is being "process()ed" multiple times. When I set maxConcurrentConsumers=1 this does not happen.</p> <p>I found this gem of wisdom on the Internet that I never knew but assuming it is correct it would explain my problem:</p> <p><em>Local references to objects are a bit different. The reference itself is not shared. The object referenced however, is not stored in each threads's local stack. All objects are stored in the shared heap.</em></p> <p>The instantiateRoutingCommand method is the around 50 lines long - that's why I broke it out to begin with. I COULD examine the JMS message enough to figure out what type of object it represents and instantiate it in the onMessage() method and convert instantiateRoutingCommand to just use setters on the passed object. That would satisfy the above stipulation. But even that is not entirely trivial and would clutter up the onMessage() method.</p> <p>I didn't try making the object volatile or making anything synchronized because if the above is true then I don't see any of that helping. So what's the best way to handle passing objects in a multi-threaded object?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USTerry
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POReturn an Object in a thread safe class
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POReturn an Object in a thread safe class
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POReturn an Object in a thread safe class
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAll the variables you're using in your code are local references, meaning they're not shared among multiple threads. So, I can't see where the threading problem could be, unless some of the lines you hid are the actually important ones.
      singulars
      1. POReturn an Object in a thread safe class
      1. USGiulio Franco
    2. CO"Local references" are the variables you declare inside a method body. This variables cannot be accessed by multiple threads, unless you publish them. Publishing a variable means to assign its value to a non-local reference (i.e. a instance/class field)
      singulars
      1. POReturn an Object in a thread safe class
      1. USGiulio Franco
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload