cancel
Showing results for 
Search instead for 
Did you mean: 

JDBC Queue Blocked

Former Member
0 Kudos

Hi there.

There is problem that's been bugging me.

We use XI 7.0. and all of patchs have been up-to-date.

Queue Hanging in the Adapter engine(JDBC) occasionally happen.

Like below,

In 2009-01-14 13:21:59, Receiver JDBC adapter successfully processed.

But Next step took approximately 10 min ( 13:31:07 ).

In that time, Work process in PI was idle and Only this Interface processed

I really don't know why this waiting situation in a queue occurs.

Truely appreciate your help.

Regards,

Miru.

============================== Symptoms =================================

2009-01-14 13:21:59 Success Receiver JDBC adapter: processing started; QoS required: ExactlyOnce

2009-01-14 13:31:07 Success JDBC adapter receiver channel PCCM_JDBC_Receiver_Temp:

processing started; party , service SKEC_CCMS_PRD_PCCM

Edited by: Tae-Woo Kim on Jan 14, 2009 7:18 AM

Edited by: Tae-Woo Kim on Jan 14, 2009 7:26 AM

Accepted Solutions (0)

Answers (3)

Answers (3)

dharamveer_gaur2
Active Contributor
0 Kudos

Hi

Try this solution

Deactivate adapter first and then do Full CPA Cache refresh Using user PIDIRUSER.

After Refreshing activate the adapter.

dharamveer_gaur2
Active Contributor
0 Kudos

Hi

look Henrique reply in this thread for monitoring and maintain Queque Adapter Engine.

.

What is your SP level?

Former Member
0 Kudos

Hi, Dharamveer

Thanks for the answer.

My case is similar with Henrique's reply.

But In my case, we don't have any EOIO scinarios( only use EO and BE )

and there were not error in the queue at that time.

Problem is taking so much time to process message that is blocked with status "Delivering in AE queue.

SP Level is 17 ( Both ABAP and J2EE)

Regards,

Miru.

dharamveer_gaur2
Active Contributor
0 Kudos

Hi

You can Deregister queue and Register again.

Mannualy restart your hang queue.use this thread

Former Member
0 Kudos

Thank you for your immediate reply.

But, The Queue that problem have occured was Adapter Engine Queue.

Not Integration engine queue in XI ABAP Stack.

Regards,

Miru.

Edited by: Tae-Woo Kim on Jan 14, 2009 7:56 AM