Remove the ALSB ear file under the sbgen folder.

Sometimes, the osb server continuously reports  errors indicating  that  the osb server is trying to connect to the  jms destinations, these jms destinations may be may all be updated but  the osb server is still referring to the old endpoints or  say jms destinations.

After a bit of analysis I found out that inside the  domain home folder there is a sbgen folder, inside that  there are lot of .ear files.I unzipped some of them, again unzipped the ejb.jar file, open the weblogic-ejb-jar.xml file, there I could see the old jms destinations.

Now the question is what are these  and how  these old destinations still exist here and how can I get rid of these?

To answer that these ear files are actually MDB's deployed for JMS proxy services. Some  times while making changes to the JMS based proxy service, the underlying MDB does not get deleted / undeployed properly which leaves multiple MDB's deployed for same proxy service. You should safely delete/undeploy all the MDB's and make changes to the JMS Proxy service and activate the changes in sbconsole. This will create a new MDB.
One way is to delete these old deployments from the Weblogic Admin console.

Please note that: This is a solution  provided by Oracle Guys itself and this worked for me very well, There  is a patch available for this issue and  raising a SR will help you get the patch number....