cancel
Showing results for 
Search instead for 
Did you mean: 

Error occured while posting the job schedule for JDBCAdapter

pedro_baroni3
Active Contributor
0 Kudos

Hi Experts,

In Application Log in Path: "/usr/sap/<SID>/DVExxxx/j2ee/cluster/server1/log", I see the error:

#/Applications/ExchangeInfrastructure/AdapterFramework/Services/Util

##com.sap.aii.af.service.scheduler.SchedulerManagerImpl.postJobScheduleOthers(String, int)

#J2EE_GUEST#0##n/a##f7956e1f6b4711e0b851001e0b5d3ac8#SAPEngine_Application_Thread[impl:3]_23##0#0

#Error#1#com.sap.aii.af.service.scheduler.SchedulerManagerImpl#Plain

###error occured while posting the job schedule for JDBCAdapter_9f0584b1bcb33b94b67ada456233bcb8 with 2#

Frequently are created Lock's and I need remove them in Visual Admin.

Any idea about this error?

Tks in advance.

Accepted Solutions (0)

Answers (1)

Answers (1)

naveen_chichili
Active Contributor
0 Kudos

Hi Baroni,

Could you please go through the below notes and you will come to know why the locks are getting created.

SAP NOTES: #1083488,#801367,#831162,#1510659

Cheers!!!

Naveen

pedro_baroni3
Active Contributor
0 Kudos

Hi Naveen,

I followed the [SAP Note 1510659|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1510659].

We applied the SP 23 Patch Level 08 of SAP-XI-AFC.

I will monitor the interfaces for a period to see if the JDBC Lock's stopped.

Tks.

Pedro Baroni

pedro_baroni3
Active Contributor
0 Kudos

Hi,

After applying the SP 23 Patch Level 08, LOCK JDBC problems stopped.

But now when a network error or database error, the JDBC Sender Communication channels that were open to connection, are blocked.

Even following the instructions in [SAP Note 1083488 - XI FTP_JDBC sender channel stop polling indefinitely (04_04S)|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1083488] the problem continues.

I've already set the parameter "taskTimeout" and selected the option "Disconnect from Database After Each Message Processing" but not resolved.

Any ideas?

Thanks in advance.

pedro_baroni3
Active Contributor
0 Kudos

Solved,

After change parameter 'taskTimeout' ([SAP Note 1083488|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1083488]) by parameter 'driver:oracle.net.CONNECT_TIMEOUT' ([SAP Note 1398891|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1398891]).

Tks.