[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fop-dev
Subject:    [jira] [Resolved] (FOP-2333) knowing Multi threading issues for FOP 1.1
From:       "Krishankant singh (JIRA)" <jira () apache ! org>
Date:       2015-02-28 23:47:04
Message-ID: JIRA.12690801.1390494136000.43677.1425167224653 () Atlassian ! JIRA
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/FOP-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Krishankant singh resolved FOP-2333.
------------------------------------
    Resolution: Fixed

> knowing Multi threading issues for FOP 1.1
> ------------------------------------------
> 
> Key: FOP-2333
> URL: https://issues.apache.org/jira/browse/FOP-2333
> Project: Fop
> Issue Type: Improvement
> Components: unqualified
> Affects Versions: 1.1
> Environment: Production
> Reporter: Krishankant singh
> Priority: Critical
> Labels: performance
> Fix For: 1.1
> 
> Original Estimate: 672h
> Remaining Estimate: 672h
> 
> Hi,
> I am a software engineer - java/j2ee
> We have a production application that creates 500 thousand pdf/day and it has \
> implemented fop 0.95  As per current implementation in our code, we have not shared \
> the FopFactory instance for threads. For each thread, we create a new FopFactory  \
> instance, so after 6 or 7 days, the application CPU usage is too high and the \
> application needs to be restarted every 6 - 7 days. As we know that creating new  \
> FopFactory instance for each thread is a very costly operation, so to cater to \
> above problem can we share one FopFactory instance for all threads. Are there any \
> problems reported with this approach in fop 1.1 because we can for sure upgrade to \
> fop 1.1 from fop 0.95



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[prev in list] [next in list] [prev in thread] [next in thread]