OSB Coherence Cache Provider has not been initialized

YOu have done a fresh isntallation of OSB 11.1.1.3

and when you are starting your admin server you are getting following
warning messages in you admin server logs


<OSB Kernel> <BEA-398316> <Error getting the Result Cache /osb/service/ResultCache because the OSB Coherence Cache Provider has not been initialized.

There are some more errors following this-

<June 07, 2010 9:25:27 AM > <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application em is not versioned.>
<June 07, 2010 9:25:57 AM > <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: oracle.rules, referenced from: /osb/oracle/bea/user_projects/domains/base_domain/servers/AdminServer/tmp/_WL_user/emai/xalnv4]. Make sure the referenced optional package has been deployed as a library.>
[ERROR] AdapterManager - ServletContainerAdapter manager not initialized correctly.

Oracle Service Bus Debugger listening on port 7002.

<June 07, 2010 9:26:38 AM > <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.ftp. The Error was:
The destination for the MDB PolledMessageListenerMDBEJB(Application: Ftp Transport Provider, EJBComponent: ftp_transport.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.ftp. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
<June 07, 2010 9:26:38 AM > <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.ftp. The Error was:
Can not get destination information. The destination JNDI name is wlsb.internal.transport.task.queue.ftp, the provider URL is null>
<June 07, 2010 9:26:38 AM > <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.email. The Error was:
The destination for the MDB PolledMessageListenerMDBEJB(Application: Email Transport Provider, EJBComponent: emailtransport.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.email. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
<June 07, 2010 9:26:38 AM > <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.email. The Error was:
Can not get destination information. The destination JNDI name is wlsb.internal.transport.task.queue.email, the provider URL is null>
<June 07, 2010 9:26:38 AM > <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.file. The Error was:
The destination for the MDB PolledMessageListenerMDBEJB(Application: File Transport Provider, EJBComponent: filepoll.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.file. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
<June 07, 2010 9:26:38 AM > <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.file. The Error was:
Can not get destination information. The destination JNDI name is wlsb.internal.transport.task.queue.file, the provider URL is null>


As per the Oracle coherence document

BEA-2032480


Error: Unable to initialize OSB Coherence Cache Provider because Oracle Coherence is not installed.
Description
Unable to initialize OSB Coherence Cache Provider because Oracle Coherence is not installed.

Action
Ensure that Oracle Coherence is installed

BEA-2032481


Error: Unable to initialize OSB Coherence Cache Provider because there was an error starting Coherence:\nt\n \n The error can be caused by one of the following:\n \n 1) The operational configuration file is invalid (see $DOMAIN_DIR$/config/osb/coherence/osb-coherence-override.xml)\n 2) The cache configuration file is invalid (see $DOMAIN_DIR$/config/osb/coherence/osb-coherence-cache-config.xml)

Description
Unable to initialize OSB Coherence Cache Provider because there was an error starting Coherence. The error can be caused by one of the following: 1) The operational configuration file is invalid (see $DOMAIN_DIR$/config/osb/coherence/osb-coherence-override.xml) 2) The cache configuration file is invalid (see $DOMAIN_DIR$/config/osb/coherence/osb-coherence-cache-config.xml) The exception message should provide more detail as to the actual cause.

Action
Correct the errors details in the exception message.


I verified the files but just was not aware of what all needs to be verified.

Did compared my installation and found that BEA_HOME/coherence_3.5/lib/coherence.jar was not existing for me.

Thought of copying it from other environment but then i process with creating a new domain again.

Created a new domain and this time it was working fine for me.