Skip to Main Content
Forums

Integration

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Issue while sending email notification via EM

M.NasirApr 15 2015 — edited Apr 15 2015

Hi All,

I followed the following article to configure Email notification but unfortunately after doing everything I am getting one error. When I test email as per asked in this post, the status becomes Sent but when I check my email I don't find any email. In server log I am getting following error. I shall be very thankful for help.

https://technology.amis.nl/2014/08/05/setup-gmail-as-mail-provider-for-soa-suite-12c-configure-smtp-certificate-in-trust…

Error Log:

javax.mail.MessagingException: Could not connect to SMTP host: smtp.gmail.com, port: 465;

  nested exception is:

        java.net.ConnectException: Connection timed out

        at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1934)

        at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:638)

        at javax.mail.Service.connect(Service.java:317)

        at javax.mail.Service.connect(Service.java:176)

        at javax.mail.Service.connect(Service.java:125)

        at oracle.sdpinternal.messaging.driver.email.outbound.EmailOutboundConnection.send(EmailOutboundConnection.java:679)

        at oracle.sdpinternal.messaging.newdriver.connection.DriverManagedConnectionImpl.send(DriverManagedConnectionImpl.java:207)

        at oracle.sdpinternal.messaging.newdriver.connection.DriverConnectionImpl.send(DriverConnectionImpl.java:26)

        at oracle.sdp.messaging.newdriver.SubDriver.onMessage(SubDriver.java:544)

        at oracle.sdpinternal.messaging.jms.QueueWorker.run(QueueWorker.java:89)

        at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)

        at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)

Caused By: java.net.ConnectException: Connection timed out

        at java.net.PlainSocketImpl.socketConnect(Native Method)

        at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)

        at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)

        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)

        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)

        at java.net.Socket.connect(Socket.java:579)

        at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:625)

        at sun.security.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:160)

        at com.sun.mail.util.SocketFetcher.createSocket(SocketFetcher.java:288)

        at com.sun.mail.util.SocketFetcher.getSocket(SocketFetcher.java:205)

        at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1900)

        at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:638)

        at javax.mail.Service.connect(Service.java:317)

        at javax.mail.Service.connect(Service.java:176)

        at javax.mail.Service.connect(Service.java:125)

        at oracle.sdpinternal.messaging.driver.email.outbound.EmailOutboundConnection.send(EmailOutboundConnection.java:679)

        at oracle.sdpinternal.messaging.newdriver.connection.DriverManagedConnectionImpl.send(DriverManagedConnectionImpl.java:207)

        at oracle.sdpinternal.messaging.newdriver.connection.DriverConnectionImpl.send(DriverConnectionImpl.java:26)

        at oracle.sdp.messaging.newdriver.SubDriver.onMessage(SubDriver.java:544)

        at oracle.sdpinternal.messaging.jms.QueueWorker.run(QueueWorker.java:89)

        at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)

        at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
This post has been answered by vladodias on Apr 15 2015
Jump to Answer

Comments

EJP
Since I set max heap size as 2 GB, the resident memory of the java application should be less than 2.5 GB ( Max Heap + Jars Memory + VM Memory ).
Only if you assume the latter two items take up <= 0.5GB each. Do they?
868448
EJP wrote:
Since I set max heap size as 2 GB, the resident memory of the java application should be less than 2.5 GB ( Max Heap + Jars Memory + VM Memory ).
Only if you assume the latter two items take up <= 0.5GB each. Do they?
I am not 100% sure. Just gave worst case assumption. If my code base/jar is high, I should get java.lang.OutOfMemoryError: PermGen space. right ? Do you have any idea ?
802316
What is your maximum direct memory? By default its the same as the heap memory maximum. This can give you a maximum size of 2 GB (heap) + 2 GB (direct) + 0.5 - 1.0 GB for the rest.

BTW: I would try updating your JVM, it is 10 updates behind current.

If you do that, something which can reduce memory consumption without too much overhead is -XX:+UseCompressedOops and -XX:+UseCompressedStrings
1 person found this helpful
EJP
I am not 100% sure. Just gave worst case assumption.
No you didn't. It isn't a 'worst case assumption'. It's just a guess. The true figure might be higher. That's my point. In this case obviously something is a lot higher. The current case is worse than your 'worst case'.
If my code base/jar is high, I should get java.lang.OutOfMemoryError: PermGen space. right?
Among other possibilities. But there is also the question of how much memory the JVM itself needs.
JRK wrote:
....without throwing OutOfMemory error.
...
Can you please help me to solve this issue ? Kindly let me know, if you require any other information.
What is the "issue" exactly?

Since there is no OOM that certainly isn't the issue.
So explain in detail why you think what you are seeing is a problem - specifically what impact it is going to have.
868448
Thanks to all for your help.
No you didn't. It isn't a 'worst case assumption'. It's just a guess.
Yes. It is just a guess not worst case assumption.
jschell wrote:
JRK wrote:
....without throwing OutOfMemory error.
...
Can you please help me to solve this issue ? Kindly let me know, if you require any other information.
What is the "issue" exactly?

Since there is no OOM that certainly isn't the issue.
So explain in detail why you think what you are seeing is a problem - specifically what impact it is going to have.
My server m/c has 8 GB RAM and I am running 2 instance of my java application in that m/c. Since each instance of memory goes to 4 GB, the m/c is not reachable. Because no more memory is available for open ssh session.
What is your maximum direct memory? By default its the same as the heap memory maximum. This can give you a maximum size of 2 GB (heap) >+ 2 GB (direct) + 0.5 - 1.0 GB for the rest.
I didn't mention anything. So it should be default ( 2GB). Thanks Peter Lawrey. Now, I understand that, the memory wiIl go upto 5GB in my case.

Thanks,
Ramesh
1 - 6
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on May 13 2015
Added on Apr 15 2015
#soa-process-management, #soa-suite-discusssions
7 comments
1,990 views