Null pointer in OSB Alert in 11g Release 1 (11.1.1.7.0)

When we try to send a mail on sla it is generating null pointer error in logs,Following error log will print on the weblogic OSB console.

####<Sep 16, 2014 12:49:25 PM IST> <Error> <ALSB Alert Rule Engine> <mann-ncr-sandee> <ServiceBusSamples> <pool-2-thread-1> <<anonymous>> <> <bb95dafb3717109e:-3062fb57:1487d2dfba1:-8000-0000000000000003> <1410851965016> <BEA-394004> <Failed to invoke action email that is part of alert destination AlertDestination dbConnection/AlertDestination_SLA. Resource: BusinessService dbConnection/business-service/PROC_CONSPOLIZASTRABAJADOR_db. Alert Rule Name: My_SLA.

com.bea.wli.sb.transports.TransportException

at com.bea.wli.sb.transports.email.EmailOutboundMessageContext.send(EmailOutboundMessageContext.java:81)

at com.bea.wli.sb.transports.email.EmailTransportProvider.sendMessageAsync(EmailTransportProvider.java:152)

at sun.reflect.GeneratedMethodAccessor662.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)

at $Proxy131.sendMessageAsync(Unknown Source)

at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageWithoutService(TransportManagerImpl.java:513)

at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:440)

at com.bea.wli.sb.init.FrameworkStarter$TransportServiceImpl.sendMessageAsync(FrameworkStarter.java:402)

at com.bea.alsb.alert.action.email.EmailActionProvider.executeAction(EmailActionProvider.java:204)

at com.bea.alsb.alert.AlertDestinationHandlerImpl.executeProviderAction(AlertDestinationHandlerImpl.java:95)

at com.bea.alsb.alert.AlertDestinationHandlerImpl.sendAlertToDestination(AlertDestinationHandlerImpl.java:76)

at com.bea.alsb.alert.AlertDestinationHandlerImpl.sendAlertToDestination(AlertDestinationHandlerImpl.java:64)

at com.bea.alsb.alert.sla.SlaAlertManager.generateAlert(SlaAlertManager.java:149)

at com.bea.alsb.alert.sla.SlaAlertManager.access$100(SlaAlertManager.java:33)

at com.bea.alsb.alert.sla.SlaAlertManager$RuleListenerForAlertGeneration.onRuleTrue(SlaAlertManager.java:227)

at com.bea.alsb.rule.RuleEngine$ListenerInvocation.invokeListener(RuleEngine.java:76)

at com.bea.alsb.rule.RuleEngine$ListenerInvocation.access$000(RuleEngine.java:61)

at com.bea.alsb.rule.RuleEngine.addFact(RuleEngine.java:115)

at com.bea.alsb.alert.sla.SlaAlertManager.intervalCompleted(SlaAlertManager.java:202)

at com.bea.alsb.alert.sla.TaskCollector$RuleEvaluationTask.run(TaskCollector.java:177)

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)

at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)

at java.util.concurrent.FutureTask.run(FutureTask.java:139)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:909)

at java.lang.Thread.run(Thread.java:662)

Caused By: java.lang.NullPointerException

at com.bea.wli.sb.transports.email.util.EmailUtil.send(EmailUtil.java:288)

at com.bea.wli.sb.transports.email.EmailOutboundMessageContext.send(EmailOutboundMessageContext.java:69)

at com.bea.wli.sb.transports.email.EmailTransportProvider.sendMessageAsync(EmailTransportProvider.java:152)

at sun.reflect.GeneratedMethodAccessor662.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)

at $Proxy131.sendMessageAsync(Unknown Source)

at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageWithoutService(TransportManagerImpl.java:512)

at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:440)

at com.bea.wli.sb.init.FrameworkStarter$TransportServiceImpl.sendMessageAsync(FrameworkStarter.java:402)

at com.bea.alsb.alert.action.email.EmailActionProvider.executeAction(EmailActionProvider.java:202)

at com.bea.alsb.alert.AlertDestinationHandlerImpl.executeProviderAction(AlertDestinationHandlerImpl.java:95)

at com.bea.alsb.alert.AlertDestinationHandlerImpl.sendAlertToDestination(AlertDestinationHandlerImpl.java:76)

at com.bea.alsb.alert.AlertDestinationHandlerImpl.sendAlertToDestination(AlertDestinationHandlerImpl.java:64)

at com.bea.alsb.alert.sla.SlaAlertManager.generateAlert(SlaAlertManager.java:149)

at com.bea.alsb.alert.sla.SlaAlertManager.access$100(SlaAlertManager.java:33)

at com.bea.alsb.alert.sla.SlaAlertManager$RuleListenerForAlertGeneration.onRuleTrue(SlaAlertManager.java:227)

at com.bea.alsb.rule.RuleEngine$ListenerInvocation.invokeListener(RuleEngine.java:76)

at com.bea.alsb.rule.RuleEngine$ListenerInvocation.access$000(RuleEngine.java:61)

at com.bea.alsb.rule.RuleEngine.addFact(RuleEngine.java:115)

at com.bea.alsb.alert.sla.SlaAlertManager.intervalCompleted(SlaAlertManager.java:198)

at com.bea.alsb.alert.sla.TaskCollector$RuleEvaluationTask.run(TaskCollector.java:177)

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)

at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)

at java.util.concurrent.FutureTask.run(FutureTask.java:138)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

at java.lang.Thread.run(Thread.java:662)

Solution: You are hitting bug 18073828 . Apply the patch, NPE you are facing will be solved. Install patch 18073828

Patch Installation step:

# Bugs Fixed by this patch:

# -------------------------

# 18073828: NPE EXCEPTION WHEN USE ALERT SEND EMAIL WITH SSL

#

# Patch Installation Instructions:

# --------------------------------

#

# Set ORACLE_HOME env var to your OSB_HOME

#

# To apply the patch, unzip the PSE container file:

#

# % unzip 18073828.zip

#

# - Set your current directory to the directory where the patch is located:

#

# % cd 18073828

#

#

# - Ensure that the directory containing the opatch script appears in

# your $PATH; then enter the following command:

#

# % opatch apply -jdk <Path to jdk> -jre <Path to jre>

# e.g. opatch apply -jdk /usr/local/packages/jdk14 -jre /usr/local/packages/jre14

#

#

#

# Patch Special Instructions:

# ---------------------------

# - Stop the servers.

# - Delete all the contents from cache and tmp under the server folder in the domain

# - If patch is for an application deployed in stage mode, delete the patched application deployment directory from stage folder under the server folder in the domain.

# - Restart the servers after applying the patch

#

# - Make sure you have downloaded the correct and latest Standalone OPatch via BUG 5912518 from My Oracle Support (formerly Metalink).

# Please follow the instructions to install this patch. OPatch scripts should be copied under $ORACLE_HOME/OPatch.

# NOTE: This is only required the first time a one-off patch is applied or if there is new opatch version available.

#

# - If you are applying the Standalone patch for the first time, you'll be presented with the following:

# Please enter your choice to enable OPatch to create 'product.xml' file or quit creation...

#

#

# Choice Product Version

# ------ ------- -------

# 1 SA_OSB 11.1.1.7.0

#

# 2. If you wish, quit 'product.xml' creation

#

# Please enter [1-2]:

#

# Enter the value '1'

#

# - If the Oracle inventory is not setup correctly this utility will fail.

# To check accessibility to the inventory you can use the command

#

# % opatch lsinventory

#