• 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
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Memory leak in Flux integrated with Weblogic 8.1 SP3

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

We are using Flux job scheduler(from Flux corp.) with our J2EE application. It appears that there is a continuous memory leak when the Flux Engine is run in the background. Our application is deployed on Weblogic 8.1 SP3.
The memory leak is observed only when the scheduler is started in an EAR application and uses datasources for creating JDBC calls.
The same works fine when instead of datasource, direct JDBC connections are made.

Folllowing class instances were found to be increasing:
java.util.LinkedList$Entry
java.util.LinkedList
weblogic.security.acl.internal.AuthenticatedSubject$SealableSet
javax.security.auth.Subject$SecureSet
weblogic.security.acl.internal.AuthenticatedSubject
javax.security.auth.Subject


Has anybody ever run into this situation ??
Why are the instances for weblogic security classes increasing when security is disabled in Flux?

Any kind of help/suggestion will be highly appreciated.

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

The memory leak was observed in older versions of Flux when using data sources. This was mainly happening due to the way transactions were managed in Flux. In later versions of Flux, we have fixed a lot of these issues by introducing a transaction management configuration property "data_source_user_transactions". This property is enabled by default which always uses container managed transactions. If you are not using container managed transactions in your application, it is recommended to disable this flag so that Flux can manage the transactions effectively.

In order to help our existing customers with older versions of Flux, we have back patched this feature so that users can safely disable this property when not using container managed transactions.

Hope this helps.

Best regards,
Arul

--
Arul Dhesiaseelan, Flux Development

+1 (406) 656-7398
www.fluxcorp.com
blogs.fluxcorp.com/arul

Skype: flux.arul

Flux - Java Job Scheduler. File Transfer. Workflow.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic