Skip to main content
Question

IFS CONNECT connectors not initializing

  • June 19, 2026
  • 4 replies
  • 18 views
BerenguerE
Do Gooder (Employee)
Forum|alt.badge.img+4

Log from /int/soapgateway?log=true:

2026-06-19 17:24:00,048 313 DEBUG [Integration]{ifsapp-int,FILE_READER1} ifs.fnd.connect.readers.ConnectReader.getReader(): Creating Connect Reader of type [File]
2026-06-19 17:24:00,049 313 DEBUG [Integration]{ifsapp-int,FILE_READER1} ifs.fnd.connect.readers.ConnectReader.initConfig(): Initializing Reader Config [ifs.fnd.connect.config.FileConnectorReadersConfig]
2026-06-19 17:24:00,049 313 DEBUG [Integration]{ifsapp-int,FILE_READER1} ifs.fnd.connect.readers.ConnectReader.initReader(): Calling nativeInitReader()...
2026-06-19 17:24:00,050 313 TRACE [Integration]{ifsapp-int,FILE_READER1} ifs.fnd.connect.config.ConfigUtil.lookupExecutorService(): Successfully looked up ManagedExecutorService [java:jboss/ee/concurrency/executor/ConnectReader] for [Reader]
2026-06-19 17:24:00,050 313 DEBUG [Integration]{ifsapp-int,FILE_READER1} ifs.fnd.connect.readers.ConnectReaderManager.nativeCallImpl(): Creating ConnectReaderManager(FILE_READER1, INIT_READER, null)
2026-06-19 17:24:00,051 313 DEBUG [Integration]{ifsapp-int,FILE_READER1} ifs.fnd.connect.readers.ConnectReaderManager.nativeCallImpl(): Submiting work
2026-06-19 17:24:00,051 313 DEBUG [Integration]{ifsapp-int,FILE_READER1} ifs.fnd.connect.readers.ConnectReaderManager.nativeCallImpl(): Waiting [10] seconds for completion of work...
2026-06-19 17:24:00,051 5356 DEBUG [Integration]{ifsapp-int,FILE_READER1} ifs.fnd.connect.readers.FileConnectReader.nativeInitReader(): Initializing File Reader [FILE_READER1]...
2026-06-19 17:24:10,052 313 ERROR [Integration]{ifsapp-int,FILE_READER1} ifs.fnd.connect.readers.ConnectReaderManager.nativeCallImpl(): Timeout when waiting for work to be completed [Error GUID:b1355fea-2bba-4792-9196-5b7cdac96af9]
2026-06-19 17:24:10,053 313 DEBUG [Integration]{ifsapp-int,FILE_READER1} ifs.fnd.connect.readers.ConnectReaderManager.nativeCall(): Restoring previous Logger
2026-06-19 17:24:10,053 313 DEBUG [Integration]{ifsapp-int,FILE_READER1} ifs.fnd.connect.readers.ConnectReader.close(): Calling nativeClose()...
2026-06-19 17:24:10,054 313 INFO [Integration]{ifsapp-int,FILE_READER1} ifs.fnd.connect.impl.TimerErrorManager$TimerContext.error(): Fatal error in timer [READER:FILE_READER1] count=205 delay=600000 
2026-06-19 17:24:40,052 439 ERROR [Integration]{ifsapp-int,SFTP_READER1} ifs.fnd.connect.readers.ConnectReaderManager.nativeCallImpl(): Timeout when waiting for work to be completed [Error GUID:cdfd10a2-8da8-4267-a236-72a22fd7bdc8]
2026-06-19 17:25:00,048 225 TRACE [Integration]{ifsapp-int,FILE_READER1} ifs.fnd.connect.ejbs.ReaderProcessorBean.reinitializeLogger(): Setting Integration log level: current = 1, reader = 4, changed = true

 

ifs-connect pod log:

[0m2026-06-19 18:16:40,063 INFO  [stdout] (EJB default - 6) 441 ERROR [Integration]{ifsapp-int,SFTP_READER1} ifs.fnd.connect.readers.ConnectReaderManager.nativeCallImpl(): Timeout when waiting for work to be completed [Error GUID:e0d02a98-bf65-402e-9755-7a8a701079cd]
[31m2026-06-19 18:16:40,063 ERROR [stderr] (EJB default - 6) 441 ERROR [Integration]{ifsapp-int,SFTP_READER1} ifs.fnd.connect.readers.ConnectReaderManager.nativeCallImpl(): Timeout when waiting for work to be completed [Error GUID:e0d02a98-bf65-402e-9755-7a8a701079cd]
[0m[31m2026-06-19 18:17:08,731 ERROR [org.jboss.as.ejb3.invocation] (EJB default - 7) WFLYEJB0034: Jakarta Enterprise Beans Invocation failed on component ConnectTimerInvokeForwarder for method public abstract void ifs.fnd.connect.ejbs.ConnectTimerBean$ConnectTimerLocal.createTimer(ifs.fnd.connect.ejbs.ConnectTimerBean$TimerType,long,long,ifs.fnd.log.Logger): javax.ejb.ConcurrentAccessTimeoutException: WFLYEJB0241: Enterprise Beans 3.1 PFD2 4.8.5.5.1 concurrent access timeout on ConnectTimerInvokeForwarder - could not obtain lock within 5000MILLISECONDS

 

 We’ve already restarted the app server, database, deleted and recreated ifs-connect pod and nothing worked. IFS Connect simply doesn’t work anymore, but it did work in the past.

 

IFS CLOUD 23R1

    4 replies

    N
    Hero (Customer)
    Forum|alt.badge.img+9
    • N.GEORGI
    • Hero (Customer)
    • June 22, 2026

    Perhaps a corrupted Connect configuration object in the database or a bad formatted message.

    Would it be possible to provide :

    • the full stack trace around ConcurrentAccessTimeoutException
    • a JVM thread dump (jstack) 
    BerenguerE
    Do Gooder (Employee)
    Forum|alt.badge.img+4
    • BerenguerE
    • Author
    • Do Gooder (Employee)
    • June 22, 2026

    Hi ​@N.GEORGI !

      I’e attached the logs you requested. I really appreciate your help… Thank you very much! :)

     

    Regards,

    Elaine Berenguer

    N
    Hero (Customer)
    Forum|alt.badge.img+9
    • N.GEORGI
    • Hero (Customer)
    • June 22, 2026

    FILE_READER1 submits work to JBoss's  ManagedExecutorService and sets a strict 10-second wait limit. Exactly 10 seconds later (17:24:10), it hits a timeout. Shortly after, SFTP_READER1hits the exact same timeout.

     

    Could you try disabling 

    FILE_READER1 and SFTP_READER1please?

    Then Restart or delete the ifs-connect pod

    If that did the trick, you need to look for files in the reader source folder that may be corrupted

     

     

    Also check for any messages stuck in a processing state (Application messages page)

     

     

     

     

     

    BerenguerE
    Do Gooder (Employee)
    Forum|alt.badge.img+4
    • BerenguerE
    • Author
    • Do Gooder (Employee)
    • June 23, 2026

    Hi! I’ve deactivated all active connectors, changed the status of all application messages to CANCEL, redeployed the pod, restarted the DB and IFS server and nothing worked so far…

    When the pod starts, it gives the error immediately… 

    [0m[0m2026-06-23 14:45:28,300 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
    [0m[0m2026-06-23 14:45:28,317 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 26.1.2.Final (WildFly Core 18.1.2.Final) started in 15161ms - Started 2619 of 2822 services (400 services are lazy, passive or on-demand) - Server configuration file in use: standalone-full.xml
    [0m[0m2026-06-23 14:45:28,323 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://0.0.0.0:9990/management
    [0m[0m2026-06-23 14:45:28,323 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://0.0.0.0:9990
    [0m[0m2026-06-23 14:45:43,323 INFO  [stdout] (Thread-2 (ActiveMQ-client-global-threads)) 270   >>>>> HANDLER [connectlog] CLOSED AND REMOVED <<<<<
    [31m2026-06-23 14:45:43,324 ERROR [stderr] (Thread-2 (ActiveMQ-client-global-threads)) 270   >>>>> HANDLER [console_err] CLOSED AND REMOVED <<<<<
    [0m[31m2026-06-23 14:46:08,419 ERROR [org.jboss.as.ejb3.invocation] (EJB default - 4) WFLYEJB0034: Jakarta Enterprise Beans Invocation failed on component ConnectTimerInvokeForwarder for method public abstract void ifs.fnd.connect.ejbs.ConnectTimerBean$ConnectTimerLocal.createTimer(ifs.fnd.connect.ejbs.ConnectTimerBean$TimerType,long,long,ifs.fnd.log.Logger): javax.ejb.ConcurrentAccessTimeoutException: WFLYEJB0241: Enterprise Beans 3.1 PFD2 4.8.5.5.1 concurrent access timeout on ConnectTimerInvokeForwarder - could not obtain lock within 5000MILLISECONDS

    I will try to open a case to IFS, because I don’t know what else to do… :(

    Terms & ConditionsAccessibility statement