Delays in Receiving Instance Updates (News) in the WorkSpace (Doc ID 1162829.1)

Last updated on OCTOBER 04, 2012

Applies to:

Oracle Business Process Management Suite - Version 10.3.1 and later
Information in this document applies to any platform.
***Checked for relevance on 4-Oct-2012***

Symptoms

Some instances are not updated quickly in the WorkSpace (delays of upto 8 minutes are noticed). The customer is also experiencing the following exception in the thread that is processing the instance in question:

<W>, "Jul 24, 2010 11:12:22 AM", Engine, MailDispat, <20> [ACTIVE] ExecuteThre, "IO exception attempting to send email to:bpm.user@customer.co.uk from:admin@example.com
The Oracle´┐Ż BPM administrator (admin@example.com) will be notified.
Original exception is:
Could not connect to SMTP host: smtp, port: 25
Caused by: Could not connect to SMTP host: smtp, port: 25
Caused by: No route to host
java.io.IOException: Could not connect to SMTP host: smtp, port: 25
at fuego.io.SMTPClient.sendMail(SMTPClient.java:326)
at fuego.io.SMTPClient.sendMail(SMTPClient.java:341)
at fuego.server.service.MailNotificationDispatcher.sendNow(MailNotificationDispatcher.java:157)
at fuego.ejbengine.service.EJBMailNotificationDispatcher.send(EJBMailNotificationDispatcher.java:55)
at fuego.components.Mail.send(Mail.java:1144)
at fuego.components.Mail.send(Mail.java:612)
at fuego.server.notification.InstanceArrivedMailNotifier.sendMail(InstanceArrivedMailNotifier.java:156)
at fuego.server.notification.InstanceArrivedMailNotifier.notify(InstanceArrivedMailNotifier.java:102)
at fuego.server.ActiveProcessImpl.processServerNews(ActiveProcessImpl.java:963)
at fuego.server.ProcInst.checkActivityNews(ProcInst.java:1920)
at fuego.server.execution.EngineExecutionContext.instancesAfterCommit(EngineExecutionContext.java:1822)
at fuego.server.execution.EngineExecutionContext.afterCommit(EngineExecutionContext.java:1010)
at fuego.transaction.TransactionAction.afterCompletion(TransactionAction.java:119)
at fuego.connector.ConnectorTransaction.afterCompletion(ConnectorTransaction.java:683)
at fuego.connector.ConnectorTransaction.commit(ConnectorTransaction.java:434)
at fuego.transaction.TransactionAction.commit(TransactionAction.java:302)
at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:481)
at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66)
at fuego.ejbengine.ItemExecutionBean.processMessage(ItemExecutionBean.java:209)
at fuego.ejbengine.ItemExecutionBean.onMessage(ItemExecutionBean.java:120)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4072)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:3964)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4490)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
Caused by: javax.mail.MessagingException: Could not connect to SMTP host: smtp, port: 25;
nested exception is:
java.net.NoRouteToHostException: No route to host
at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1282)
at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:370)
at javax.mail.Service.connect(Service.java:275)
at javax.mail.Service.connect(Service.java:156)
at javax.mail.Service.connect(Service.java:105)
at javax.mail.Transport.send0(Transport.java:168)
at javax.mail.Transport.send(Transport.java:98)
at fuego.io.SMTPClient.sendMail(SMTPClient.java:319)
... 31 more
Caused by: java.net.NoRouteToHostException: No route to host
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:520)
at java.net.Socket.connect(Socket.java:470)
at com.sun.mail.util.SocketFetcher.createSocket(SocketFetcher.java:232)
at com.sun.mail.util.SocketFetcher.getSocket(SocketFetcher.java:189)
at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1250)
... 38 more"

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms