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***


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
The Oracle´┐Ż BPM administrator ( 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 Could not connect to SMTP host: smtp, port: 25
at fuego.server.service.MailNotificationDispatcher.sendNow(
at fuego.ejbengine.service.EJBMailNotificationDispatcher.send(
at fuego.components.Mail.send(
at fuego.components.Mail.send(
at fuego.server.notification.InstanceArrivedMailNotifier.sendMail(
at fuego.server.notification.InstanceArrivedMailNotifier.notify(
at fuego.server.ActiveProcessImpl.processServerNews(
at fuego.server.ProcInst.checkActivityNews(
at fuego.server.execution.EngineExecutionContext.instancesAfterCommit(
at fuego.server.execution.EngineExecutionContext.afterCommit(
at fuego.transaction.TransactionAction.afterCompletion(
at fuego.connector.ConnectorTransaction.afterCompletion(
at fuego.connector.ConnectorTransaction.commit(
at fuego.transaction.TransactionAction.commit(
at fuego.transaction.TransactionAction.startBaseTransaction(
at fuego.transaction.TransactionAction.startTransaction(
at fuego.transaction.TransactionAction.start(
at fuego.server.execution.DefaultEngineExecution.executeImmediate(
at fuego.server.execution.EngineExecution.executeImmediate(
at fuego.ejbengine.ItemExecutionBean.processMessage(
at fuego.ejbengine.ItemExecutionBean.onMessage(
at weblogic.ejb.container.internal.MDListener.execute(
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(
at weblogic.ejb.container.internal.MDListener.onMessage(
at weblogic.jms.client.JMSSession.onMessage(
at weblogic.jms.client.JMSSession.execute(
at weblogic.jms.client.JMSSession$
Caused by: javax.mail.MessagingException: Could not connect to SMTP host: smtp, port: 25;
nested exception is: No route to host
at com.sun.mail.smtp.SMTPTransport.openServer(
at com.sun.mail.smtp.SMTPTransport.protocolConnect(
at javax.mail.Service.connect(
at javax.mail.Service.connect(
at javax.mail.Service.connect(
at javax.mail.Transport.send0(
at javax.mail.Transport.send(
... 31 more
Caused by: No route to host
at Method)
at com.sun.mail.util.SocketFetcher.createSocket(
at com.sun.mail.util.SocketFetcher.getSocket(
at com.sun.mail.smtp.SMTPTransport.openServer(
... 38 more"


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