java.net.ConnectException: Connection refused: connect, Status Type :DELIVERY_TO_GATEWAY_FAILURE, Received from Driver : Farm_oim_domain/oim_domain/soa_server1/usermessagingdriver-email:oracle_sdpmessagingdriver_email#Email-Driver, Received at :Tue Mar 08 14:30:00 EST 2011 ]] [2011-03-08T14:30:01.122-05:00] [soa_server1] [ERROR] [] [oracle.soa.services.notification] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: OracleSystemUser] [ecid: 0000IuMwcgYALQ05zzp2iW1DTc1r00007W,0] [APP: soa-infra] [dcid: c3da69ddac93cb47:-6c8e30d7:12e96e675fe:-7ffd-000000000000181e] <.> Error while sending notification.[[ Error while sending notification to 'email:pete@hubcitymedia.com; 96f2872a0a0014a201d831ad3db09391'. Possible causes : SDPMessaging Driver not configured; Invalid To Address is used; Email server/Messaging gateway is down; using IP address as part of email ID instead of domain name;. ORABPEL-31015 Error while sending notification. Error while sending notification to 'email:pete@hubcitymedia.com; 96f2872a0a0014a201d831ad3db09391'. Possible causes : SDPMessaging Driver not configured; Invalid To Address is used; Email server/Messaging gateway is down; using IP address as part of email ID instead of domain name;.

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 727499, 1 year ago
: SDPMessaging Driver not configured; Invalid To Address is used; Email server/Messaging gateway is down; using IP address as part of email ID instead of domain name;. ORABPEL-31015 Error while sending notification. Error while sending notification to
via Oracle Community by 727499, 1 year ago
: SDPMessaging Driver not configured; Invalid To Address is used; Email server/Messaging gateway is down; using IP address as part of email ID instead of domain name;. ORABPEL-31015 Error while sending notification. Error while sending notification to
java.net.ConnectException: Connection refused: connect, Status Type :DELIVERY_TO_GATEWAY_FAILURE, Received from Driver : Farm_oim_domain/oim_domain/soa_server1/usermessagingdriver-email:oracle_sdpmessagingdriver_email#Email-Driver, Received at :Tue Mar 08 14:30:00 EST 2011 ]] [2011-03-08T14:30:01.122-05:00] [soa_server1] [ERROR] [] [oracle.soa.services.notification] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: OracleSystemUser] [ecid: 0000IuMwcgYALQ05zzp2iW1DTc1r00007W,0] [APP: soa-infra] [dcid: c3da69ddac93cb47:-6c8e30d7:12e96e675fe:-7ffd-000000000000181e] <.> Error while sending notification.[[ Error while sending notification to 'email:pete@hubcitymedia.com; 96f2872a0a0014a201d831ad3db09391'. Possible causes : SDPMessaging Driver not configured; Invalid To Address is used; Email server/Messaging gateway is down; using IP address as part of email ID instead of domain name;. ORABPEL-31015 Error while sending notification. Error while sending notification to 'email:pete@hubcitymedia.com; 96f2872a0a0014a201d831ad3db09391'. Possible causes : SDPMessaging Driver not configured; Invalid To Address is used; Email server/Messaging gateway is down; using IP address as part of email ID instead of domain name;.
at oracle.bpel.services.notification.impl.asns.ASNSDriver.onStatus(ASNSDriver.java:680)
at oracle.bpel.services.notification.impl.asns.ASNSInteractionBean.onStatus(ASNSInteractionBean.java:235)
at oracle.bpel.services.notification.impl.asns.ASNSInteraction_rwgsr4_ELOImpl.onStatus(ASNSInteraction_rwgsr4_ELOImpl.java:504)
at oracle.sdpinternal.messaging.MessageDispatcherBean.dispatchStatus(MessageDispatcherBean.java:332)
at oracle.sdpinternal.messaging.MessageDispatcherBean.onMessage(MessageDispatcherBean.java:247)
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:4659)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:4345)
at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3821)
at weblogic.jms.client.JMSSession.access$000(JMSSession.java:115)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5170)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.

Know the solutions? Share your knowledge to help other developers to debug faster.