• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • paul wheaton
  • Liutauras Vilda
  • Ron McLeod
Sheriffs:
  • Jeanne Boyarsky
  • Devaka Cooray
  • Paul Clapham
Saloon Keepers:
  • Scott Selikoff
  • Tim Holloway
  • Piet Souris
  • Mikalai Zaikin
  • Frits Walraven
Bartenders:
  • Stephan van Hulst
  • Carey Brown

javax.transaction.Transaction Rolledback Exception: CORBA

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi All,

Can anyone tell me what is the reason for the below error and how it can be solved.....

javax.transaction.TransactionRolledbackException: CORBA TRANSACTION_ROLLEDBACK 0x0 No; nested exception is:
org.omg.CORBA.TRANSACTION_ROLLEDBACK: javax.transaction.TransactionRolledbackException: ; nested exception is:
java.lang.OutOfMemoryError vmcid: 0x0 minor code: 0 completed: No
 
High Plains Drifter
Posts: 7289
Netbeans IDE VI Editor
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Moving this to Distributed Java.
 
Bartender
Posts: 4121
IntelliJ IDE Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The transaction rolled back because an error was thrown during the transaction. This error was - java.lang.OutOfMemoryError. Something is causing your JVM to run out of memory. This could be due to a problem with implementation - Java's version of "memory leaks" - objects not getting de-referenced properly so they are never garbage collected. Or it could be that the program is just using a lot of memory for legitimate reasons - you may have to rethink some algorithms or processes you are using (i.e. - if you're processing a large amount of data at a time, you may need to "chunk" the data to make better use of resources), or you may want to increase the amount of memory available to the JVM using the -Xmx or -Xms command line parameters.
 
reply
    Bookmark Topic Watch Topic
  • New Topic