|
| Re: Reg:Report Engine start and shutdown [message #765247 is a reply to message #765219] |
Tue, 13 December 2011 17:32   |
|
The engine should be able to stay up as long as you want it to. If you
are sharing rptdocuments it would be best to synchronize access to them,
by synchronizing the render tasks.
Jason
On 12/13/2011 11:48 AM, kkp wrote:
> Hi,
>
>
> We are using BIRT 3.7 to generate reports, in the process of generating
> we will start birt reporting engine when our web logic application
> server is started.
>
> We are using JMS queues to submit report request to engine, in this
> process we sometimes get reports error ed out due to simultaneous access
> of rptdocument and there on any subsequent requests will not be
> processed and the engine gets corrupted.To get back the engine we had to
> bounce the application server.
>
> We are in the process of fixing the issue, but would like to know what
> is the optimum life span of the reporting engine ? I mean how long we
> can have reporting engine running from once started. Do we have to
> bounce our application server in any regular intervals to have
> continuous functioning of the engine?
>
> We cannot bounce the app server in production environment as there would
> be customer impact if reports are not run because the application server
> is brought down.
>
> Any advise on this would be highly appreciated.
>
> Thanks,
> KKP
|
|
|
| Re: Reg:Report Engine start and shutdown [message #765744 is a reply to message #765247] |
Wed, 14 December 2011 15:47 |
Eclipse User |
|
|
|
KKP,
Inter-system messaging services fit very nicely with
intra-system(thread) Queues/Producers/Consumers. Look at Java's
Concurrent BlockingQueue and the example.
http://docs.oracle.com/javase/1.5.0/docs/api/java/util/concurrent/BlockingQueue.html
Encapsulate the JMS listener in a Producer, that feeds the queue with
requests to the Engine.
Then if you set up the engine to run on a separate thread and feed it
the requests that are pulled off the Queue from a Consumer you will not
need to use blocking calls to the engine.
John
On 12/13/2011 11:32 AM, Jason Weathersby wrote:
> The engine should be able to stay up as long as you want it to. If you
> are sharing rptdocuments it would be best to synchronize access to them,
> by synchronizing the render tasks.
>
>
> Jason
>
> On 12/13/2011 11:48 AM, kkp wrote:
>> Hi,
>>
>>
>> We are using BIRT 3.7 to generate reports, in the process of generating
>> we will start birt reporting engine when our web logic application
>> server is started.
>>
>> We are using JMS queues to submit report request to engine, in this
>> process we sometimes get reports error ed out due to simultaneous access
>> of rptdocument and there on any subsequent requests will not be
>> processed and the engine gets corrupted.To get back the engine we had to
>> bounce the application server.
>>
>> We are in the process of fixing the issue, but would like to know what
>> is the optimum life span of the reporting engine ? I mean how long we
>> can have reporting engine running from once started. Do we have to
>> bounce our application server in any regular intervals to have
>> continuous functioning of the engine?
>>
>> We cannot bounce the app server in production environment as there would
>> be customer impact if reports are not run because the application server
>> is brought down.
>>
>> Any advise on this would be highly appreciated.
>>
>> Thanks,
>> KKP
>
|
|
|
Powered by
FUDForum. Page generated in 0.01780 seconds
] 
Search
Help
Register
Login
Home
