Binding to jndi tree takes ages

Hi we are loading all the master tables in to objects at the app server startup (SUN ONE 7) and then binding the whole object to the jndi tree. All the tables data in text files comes to about 5 MB and the serilized object with data to about 8 MB. But when the app server tries to bind the object the app server process consumes over 500MB of ram and gives OutOfmemoryError as the total ram is 512MB. why is it consuming so much memory. It does bind an object of about 5 MB but when trying to lookup subsequent to the first lookup it fails. Is this a bug or what??? the same thing works perfectly with Weblogic and Websphere and also Weblogic is very efficient in memory consumption and response time is amazing. For a 5 MB object the lookup takes about 5Secs in Weblogic and about 15Mins in Sun One. We might have to drop the Sun One App Srv and go for Weblogic though we dont want. This same thing is working with about 4MB object in Sun One but takes about 45 Mins to 1 Hour to finish the serialization etc for jndi .Kindly provide some guidance.Thanks in advance.

Similar Messages

Bind a huge object to jndi tree in sun one 7

Hi we are loading all the master tables in to objects at the app server startup (SUN ONE 7) and then binding the whole object to the jndi tree. All the tables data in text files comes to about 5 MB and the serilized object with data to about 8 MB. But when the app server tries to bind the object the app server process consumes over 500MB of ram and gives OutOfmemoryError as the total ram is 512MB. why is it consuming so much memory. It does bind an object of about 5 MB but when trying to lookup subsequent to the first lookup it fails. Is this a bug or what??? the same thing works perfectly with Weblogic and Websphere and also Weblogic is very efficient in memory consumption and response time is amazing. For a 5 MB object the lookup takes about 5Secs in Weblogic and about 15Mins in Sun One. We might have to drop the Sun One App Srv and go for Weblogic though we dont want. Kindly provide some guidance. Thanks in advance.

Hi,
Refer http://java.sun.com/products/jndi/tutorial/objects/storing/remote.html
-amol

Binding huge object to the jndi tree.

Hi we are loading all the master tables in to objects at the app server startup (SUN ONE 7) and then binding the whole object to the jndi tree. All the tables data in text files comes to about 5 MB and the serilized object with data to about 8 MB. But when the app server tries to bind the object the app server process consumes over 500MB of ram and gives OutOfmemoryError as the total ram is 512MB. why is it consuming so much memory. It does bind an object of about 5 MB but when trying to lookup subsequent to the first lookup it fails. Is this a bug or what??? the same thing works perfectly with Weblogic and Websphere and also Weblogic is very efficient in memory consumption and response time is amazing. For a 5 MB object the lookup takes about 5Secs in Weblogic and about 15Mins in Sun One. We might have to drop the Sun One App Srv and go for Weblogic though we dont want. This same thing is working with about 4MB object in Sun One but takes about 45 Mins to 1 Hour to finish the serialization etc for jndi .Kindly provide some guidance.Thanks in advance.

True. At the end I configured the value as a "server property". The cool thing about configuring the jndi tree is that it is replicated in a cluster.
Obviously the values that I inserted affected all the applications, like the url of our SOA server.

Bind remote object to JNDI tree

I want to create a JNDI tree in the same JVM with remote object, and then I have two problem:
1> Should I bind remote object or its stub to the JNDI tree?
2> How to look up the JNDI tree to get the binded stub from the client side? (Suppose server ip is 192.168.99.42)
I hope a gentleman would give me a piece of code, so i would be much clearer. Thanks a lot!

Hi,
Refer http://java.sun.com/products/jndi/tutorial/objects/storing/remote.html
-amol

Unable to bind object in JNDI tree.

While I try to bind a simple object in JNDI tree I get the following error.
I have not used any cluster .
Server : Web Logic 8.1 SP 6
Jdk version 1.4.2 comes along with bea weblogic 8.1 sp 6
Javax.naming.communicationException[
Root exception is java.rmi.unmarshalException:
Error unmarshalling arguments; nested exception is :
Java.lang.ClassNotFoundException: com.examples.person : This error could indicate that a compound was deployed on a cluster member but not other members of that cluster. Make sure that any component deployed on a server that is part of a cluster is also deployed on a server that is part of a cluster is also deployed on all other member of that cluster.

Is this somehow being called from the parameterless constructor?
You sometimes have to wrap bits of code with in designer checks to stop em running.
In c# that would be:
if (!DesignerProperties.GetIsInDesignMode(this))
// do your stuff only at runtime
Please don't forget to upvote posts which you like and mark those which answer your question.
My latest Technet article - Dynamic XAML

How to bind an object to JNDI tree in iAS?

Hi all,
When I try to bind a string object to jndi tree, the following exception
occurs:
javax.naming.NamingException: Unable to get object instance from reference.
Roo
t exception is javax.naming.NamingException: Can't bind instance of class
java.lang.String
at com.netscape.server.jndi.RootContext.bindCtx(Unknown Source)
at com.netscape.server.jndi.RootContext.rebind(Unknown Source)
at com.netscape.server.jndi.RootContext.rebind(Unknown Source)
at javax.naming.InitialContext.rebind(InitialContext.java:385)
at jsp.APPS.bmx.test2._jspService(test2.java:76)
at jsp.APPS.bmx.test2.service(test2.java:42)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
com.netscape.server.servlet.servletrunner.ServletInfo.service(Unknown
Source)
The code fragment is:
Context ctx = new InitialContext();
String str = "hell,every one!";
ctx.rebind("abc", str);
Can anyone give some help? Thanks in advance.
Johnson

To bind an object into the JNDI tree check the documentation here:
http://e-docs.bea.com/wls/docs81/jndi/jndi.html#475702
If this is to be used by all your applications that you deploy on the server check out the startup/shutdown class documentation here:
http://edocs.bea.com/wls/docs81/ConsoleHelp/startup_shutdown.html
Cheers
IV

How to delete conext entries in JNDI tree after undeployment?

Hi,
When I deploy an EAR or JAR file with EJBs, they bind in the JNDI server.
When I undeploy the application the beans are no longer bound to the JNDI
tree, but the contexts they created remain.
For example, I deploy a bean that binds its home object to the following
entry in the JNDI:
myapp/mymodule/MyBean
When I undeploy MyBean, the context myapp/mymodule remain.
Is there an utility to remove these entries or do I have to develop my own
utility? I did not find anything in the administration console to do this.
This has been a source of some trouble, because sometimes I get error
messages when I want to redeploy the beans.
Thanks in advance,
Vegeta

Please don't cross post. see my reply in the ejb newsgroup.
Thanks,
Michael
Vegeta wrote:
Hi,
When I deploy an EAR or JAR file with EJBs, they bind in the JNDI server.
When I undeploy the application the beans are no longer bound to the JNDI
tree, but the contexts they created remain.
For example, I deploy a bean that binds its home object to the following
entry in the JNDI:
myapp/mymodule/MyBean
When I undeploy MyBean, the context myapp/mymodule remain.
Is there an utility to remove these entries or do I have to develop my own
utility? I did not find anything in the administration console to do this.
This has been a source of some trouble, because sometimes I get error
messages when I want to redeploy the beans.
Thanks in advance,
Vegeta--
Michael Young
Developer Relations Engineer
BEA Support

Error While Viewing JNDI Tree

          Hi
          I'm facing the following problem while viewing the JNDI tree. I had configured
          two servers ejbServer,ejbServer1 both clustered, i can able to start both the
          servers, but in the JNDI tree when i click ejbServer or Replication Manager
          i'm getting the following error please help me out.
          An unexpected error was encountered in processing your request.
          Exception
          javax.naming.NameNotFoundException: Unable to resolve weblogic.transaction.coordinators.ejbServer.
          Resolved: 'weblogic.transaction.coordinators' Unresolved:'ejbServer' ; remaining
          name ''
               <>
          Current Date
          Mon Aug 27 09:15:19 GMT+08:00 2001
          Console Release Build
          6.0 Service Pack 2
          Console Build
          6.0 Service Pack 2 05/24/2001 11:55:28 #117037
          Server Release Build
          6.0 Service Pack 2
          Server Build
          6.0 Service Pack 2 05/24/2001 11:55:28 #117037
          All Server Product Versions
          WebLogic Server Build:     6.0 Service Pack 2 05/24/2001 11:55:28 #117037
          WebLogic XML Module:     6.0 Service Pack 2 05/24/2001 12:34:27 #117037
          Request Info
          Protocol: HTTP/1.1
          ServerName: 127.0.0.1
          ServerPort: 7001
          Secure: false
          ContextPath: /console
          ServletPath: /common/error.jsp
          QueryString: null
          PathInfo: null
          PathTranslated: null
          RequestURI: /console/common/error.jsp
          AuthType: Basic
          ContentType: null
          CharacterEncoding: null
          Locale: hi
          Method: GET
          Session: weblogic.servlet.internal.session.MemorySessionData@37b6ef
          RequestedSessionId: O4meRts3MSQ1pr2YCfOsUGA3MckiUv6wmiQVYrdcQBy3oYpYTz2Q/console
          RequestedSessionIdFromCookie: true
          RequestedSessionIdFromURL: false
          UserPrincipal: system
          RemoteUser: system
          RemoteAddr: 127.0.0.1
          RemoteHost: localhost
          Parameters
          binding = ejbServer
          context = weblogic.transaction.coordinators
          Attributes
          console.original./console/common/error.jsp.ContextPath = /console
          console.original./console/common/error.jsp.Method = GET
          console.original./console/common/error.jsp.RemoteUser = system
          console.original./console/common/error.jsp.RequestURI = /console/common/error.jsp
          console.original./console/common/error.jsp.ServletPath = /common/error.jsp
          console.original./console/panels/mbean/JNDIBinding.jsp.ContextPath = /console
          console.original./console/panels/mbean/JNDIBinding.jsp.Method = GET
          console.original./console/panels/mbean/JNDIBinding.jsp.QueryString = context=weblogic.transaction.coordinators&binding=ejbServer
          console.original./console/panels/mbean/JNDIBinding.jsp.RemoteUser = system
          console.original./console/panels/mbean/JNDIBinding.jsp.RequestURI = /console/panels/mbean/JNDIBinding.jsp
          console.original./console/panels/mbean/JNDIBinding.jsp.ServletPath = /panels/mbean/JNDIBinding.jsp
          console.preferences.ContextKey = /panels/mbean/JNDIBinding.jsp
          javax.servlet.include.context_path = /console
          javax.servlet.include.request_uri = /console/common/requestinfo.jsp
          javax.servlet.include.servlet_path = /common/requestinfo.jsp
          javax.servlet.jsp.jspException = javax.naming.NameNotFoundException:
          Unable to resolve weblogic.transaction.coordinators.ejbServer. Resolved: 'weblogic.transaction.coordinators'
          Unresolved:'ejbServer' ; remaining name ''
          weblogic.httpd.user = system
          weblogic.management.console.tags.ContentTag = java.lang.Object@397a54
          weblogic.management.console.tags.HeaderTag = java.lang.Object@e4a33
          Headers
          Accept = image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel,
          application/msword, application/vnd.ms-powerpoint, */*
          Accept-Encoding = gzip, deflate
          Accept-Language = hi
          Authorization = Basic c3lzdGVtOm1hbmFnZXIx
          Connection = Keep-Alive
          Cookie = JSESSIONID=O4meRts3MSQ1pr2YCfOsUGA3MckiUv6wmiQVYrdcQBy3oYpYTz2Q!2557472653882942880!-1062729946!7001!7002
          Host = 127.0.0.1:7001
          User-Agent = Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0)
          BrowserInfo
          User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0)
          IE: true
          Netscape: false
          Supported: true
          JavscriptHrefs: false
          TableCellClick: true
          DocumentReloadedOnResize: false
          DropdownStretchable: true
          CellSpacingBlank: false
          EmptyCellBlank: false
          ImgOnclickSupported: true
          TableBorderFancy: true
          PartialToWideTables: false
          Server System Properties
          awt.toolkit = sun.awt.windows.WToolkit
          bea.home = d:\Weblogic
          cloudscape.system.home = ./samples/eval/cloudscape/data
          file.encoding = Cp1252
          file.encoding.pkg = sun.io
          file.separator = \
          java.awt.fonts =
          java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
          java.awt.printerjob = sun.awt.windows.WPrinterJob
          java.class.path = .;d:\Weblogic\jdk130\lib\tools.jar;d:\Weblogic\wlserver\lib\weblogic_sp.jar;d:\Weblogic\wlserver\lib\weblogic.jar;d:\Weblogic\wlserver\lib\xmlx.jar;d:\Weblogic\wlserver\lib\ejb20.jar;d:\Weblogic\wlserver\samples\eval\cloudscape\lib\cloudscape.jar;;;;d:\Weblogic;d:\Weblogic\wlserver\bin\oci816_8;d:\Oracle_Home\iSuites\jdbc\lib\classes12.zip;d:\Weblogic\wlserver\lib;d:\Oracle_Home\iSuites\lib\xmlparserv2.jar;d:\JDeveloper\lib\xsu12.jar;;
          java.class.version = 47.0
          java.ext.dirs = d:\Weblogic\jdk130\jre\lib\ext
          java.home = d:\Weblogic\jdk130\jre
          java.io.tmpdir = C:\TEMP\
          java.library.path = d:\Weblogic\jdk130\bin;.;C:\WINNT\System32;C:\WINNT;.\bin;D:\Oracle_Home\iSuites\BIN;D:\Oracle_Home\iSuites\Apache\Perl\5.00503\bin\mswin32-x86;C:\Program
          Files\Oracle\jre\1.1.7\bin;C:\WINNT\system32;C:\WINNT;C:\VisualCafeSE\Java2\Bin;C:\Program
          Files\Common Files\WebGain Shared;C:\VisualCafeSE\Bin;
          java.naming.factory.initial = weblogic.jndi.WLInitialContextFactory
          java.naming.factory.url.pkgs = weblogic.jndi.factories
          java.protocol.handler.pkgs = weblogic.utils|weblogic.utils|weblogic.net|weblogic.management|weblogic.net|weblogic.net|weblogic.utils
          java.runtime.name = Java(TM) 2 Runtime Environment, Standard
          Edition
          java.runtime.version = 1.3.0-C
          java.security.policy = =d:\Weblogic\wlserver/lib/weblogic.policy
          java.specification.name = Java Platform API Specification
          java.specification.vendor = Sun Microsystems Inc.
          java.specification.version = 1.3
          java.vendor = Sun Microsystems Inc.
          java.vendor.url = http://java.sun.com/
          java.vendor.url.bug = http://java.sun.com/cgi-bin/bugreport.cgi
          java.version = 1.3.0
          java.vm.info = mixed mode
          java.vm.name = Java HotSpot(TM) Client VM
          java.vm.specification.name = Java Virtual Machine Specification
          java.vm.specification.vendor = Sun Microsystems Inc.
          java.vm.specification.version = 1.0
          java.vm.vendor = Sun Microsystems Inc.
          java.vm.version = 1.3.0-C
          javax.rmi.CORBA.PortableRemoteObjectClass = weblogic.iiop.PortableRemoteObjectDelegateImpl
          javax.rmi.CORBA.UtilClass = weblogic.iiop.UtilDelegateImpl
          javax.xml.parsers.DocumentBuilderFactory = weblogic.xml.jaxp.RegistryDocumentBuilderFactory
          javax.xml.parsers.SAXParserFactory = weblogic.xml.jaxp.RegistrySAXParserFactory
          jmx.implementation.name = JMX RI
          jmx.implementation.vendor = Sun Microsystems
          jmx.implementation.version = 1.0
          jmx.specification.name = Java Management Extensions
          jmx.specification.vendor = Sun Microsystems
          jmx.specification.version = 1.0 Final Release
          line.separator =
          os.arch = x86
          os.name = Windows NT
          os.version = 4.0
          path.separator = ;
          sun.boot.class.path = d:\Weblogic\jdk130\jre\lib\rt.jar;d:\Weblogic\jdk130\jre\lib\i18n.jar;d:\Weblogic\jdk130\jre\lib\sunrsasign.jar;d:\Weblogic\jdk130\jre\classes
          sun.boot.library.path = d:\Weblogic\jdk130\jre\bin
          sun.cpu.endian = little
          sun.cpu.isalist = pentium_pro+mmx pentium_pro pentium+mmx
          pentium i486 i386
          sun.io.unicode.encoding = UnicodeLittle
          user.dir = D:\Weblogic\wlserver
          user.home = C:\WINNT\Profiles\venkata
          user.language = en
          user.name = venkata
          user.region = US
          user.timezone = Asia/Singapore
          weblogic.Domain = DNSdomain
          weblogic.Name = DNSserver
          weblogic.management.discover = true
          weblogic.security.jaas.Configuration = weblogic.security.internal.ServerConfig
          weblogic.security.jaas.Policy = d:/Weblogic/wlserver/lib/Server.policy


[att1.html]

Adapter JNDI are errored out in JNDI tree on Weblogic

Hey,
I have setup weblogic 10.3.4 and SOA Suite 11g.
The adapters seem to be deployed and active with a green 'OK' status in the deployments on the soa_server1. However when I go to the jndi tree for the soa_server1, all the adapters have an '!' for errored out.
This is causing various problems. In particular when a process using the Oracle Apps Adapter is deployed it is unable to find the jdbc connection associated with the adapter. However, the jdbc jndi entry is in the tree and the jdbc connection test's just fine.
So there seems to be a missing link in how the adapters are deployed and how the JNDI is getting updated or something.
The error is below. Any help appreciated.
====> CubeEngine load MIS_INB_WorkOrder_AR_Sync/Process_WO_AR_Sync took 726 ms
INFO: DeploymentEventPublisher.invoke Publishing deploy event for default/MIS_INB_WorkOrder_AR_Sync!1.0*soa_85dcf1de-1d63-4b34-9f99-3e52c1f04366
<Aug 10, 2011 1:25:33 PM EDT> <Warning> <oracle.soa.services.notification> <BEA-000000> <<.> Notification via email, voice, SMS or IM will not be sent. If you would like to enable them, please configure corresponding sdpmessaging driver. Then modify the accounts and set NotificationMode attribute to either NONE, EMAIL or ALL in workflow-notification-config.xml>
INFO: SchemaManager.isIncrementalBuildSupported XMLSchema incremental build enabled.
<Aug 10, 2011 1:25:44 PM EDT> <Error> <oracle.soa.adapter> <BEA-000000> <JCABinding=> MIS_INB_WorkOrder_AR_Sync Error while performing endpoint Activation: javax.resource.ResourceException: Unable to find data source null>
<Aug 10, 2011 1:25:44 PM EDT> <Error> <oracle.soa.adapter> <BEA-000000> <JCABinding=> MIS_INB_WorkOrder_AR_Sync
javax.resource.ResourceException: Unable to find data source null
     at oracle.tip.adapter.aq.v2.database.AppsDequeueAgentFactory.createAppsDequeueAgent(AppsDequeueAgentFactory.java:52)
     at oracle.tip.adapter.aq.v2.AppsEndpoint.activate(AppsEndpoint.java:51)
     at oracle.tip.adapter.aq.v2.jca.AQResourceAdapter.endpointActivation(AQResourceAdapter.java:62)
     at oracle.tip.adapter.apps.AppsResourceAdapter.endpointActivation(AppsResourceAdapter.java:152)
     at oracle.integration.platform.blocks.adapter.fw.impl.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:494)
     at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.performEndpointActivation(JCAEndpointActivation.java:637)
     at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.activateInboundJcaEndpoint(JCAEndpointActivation.java:620)
     at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.performActivation(JCAEndpointActivation.java:383)
     at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.endpointActivation(AdapterServiceRevisionRegistry.java:583)
     at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.activate(AdapterServiceRevisionRegistry.java:438)
     at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.setDefaultRevision(AdapterServiceRevisionRegistry.java:403)
     at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceSeries.setDefaultRevision(AdapterServiceRevisionRegistry.java:328)
     at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceSeriesSet.setDefaultRevision(AdapterServiceRevisionRegistry.java:134)
     at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry.setDefaultRevision(AdapterServiceRevisionRegistry.java:96)
     at oracle.integration.platform.blocks.adapter.AdapterService.defaultRevisionChanged(AdapterService.java:309)
     at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.processDefaultInSeries(FabricKernelInitializerServlet.java:577)
     at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.run(FabricKernelInitializerServlet.java:526)
     at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
     at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
     at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Caused by: java.sql.SQLException: javax.resource.ResourceException: Unable to find data source null
     at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getDatabaseConnection(DBQueueFactory.java:97)
     at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getQueue(DBQueueFactory.java:68)
     at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getQueue(DBQueueFactory.java:216)
     at oracle.tip.adapter.aq.v2.database.AppsDequeueAgentFactory.createAppsDequeueAgent(AppsDequeueAgentFactory.java:49)
     ... 19 more
Caused by: javax.resource.ResourceException: Unable to find data source null
     at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getDataSourceConnection(AppsManagedConnectionFactory.java:429)
     at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getConnection(AppsManagedConnectionFactory.java:308)
     at oracle.tip.adapter.apps.AppsManagedConnection.getConnection(AppsManagedConnection.java:147)
     at oracle.tip.adapter.apps.AppsConnection.getJdbcConnection(AppsConnection.java:77)
     at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getDatabaseConnection(DBQueueFactory.java:94)
     ... 22 more
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.AppsDataSource'. Resolved 'jdbc'; remaining name 'AppsDataSource'
     at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
     at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
     at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
     at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
     at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
     at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
     at javax.naming.InitialContext.lookup(InitialContext.java:392)
     at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getDataSourceConnection(AppsManagedConnectionFactory.java:426)
     ... 26 more
>
oracle.fabric.common.FabricDeploymentException: [JCABinding] [MIS_INB_WorkOrder_AR_Sync.consumeARTrgReq/1.0]Unable to complete initialization due to: Endpoint Activation Error.
AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
The Resource Adapter Oracle Applications Adapter was unable to activate the endpoint oracle.tip.adapter.apps.AppsWFBesQueueDequeueActivationSpec:{QueueName=WF_BPEL_Q, DatabaseSchema=APPS, Consumer=ORA_850j4e1g8gsjcc9g6oo36e9h65, MessageSelectorRule=tab.user_data.event_name = 'oracle.apps.mas.soa.workorder2ar.trigger', AppsEventSchema=CUSTOM_SCHEMA} due to the following reason: javax.resource.ResourceException: Unable to find data source null
Please correct the reported issue and redeploy the BPEL process.
: Endpoint Activation Error.
AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
The Resource Adapter Oracle Applications Adapter was unable to activate the endpoint oracle.tip.adapter.apps.AppsWFBesQueueDequeueActivationSpec:{QueueName=WF_BPEL_Q, DatabaseSchema=APPS, Consumer=ORA_850j4e1g8gsjcc9g6oo36e9h65, MessageSelectorRule=tab.user_data.event_name = 'oracle.apps.mas.soa.workorder2ar.trigger', AppsEventSchema=CUSTOM_SCHEMA} due to the following reason: javax.resource.ResourceException: Unable to find data source null
Please correct the reported issue and redeploy the BPEL process.
{rootCauses=[]}
     at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry.access$3600(AdapterServiceRevisionRegistry.java:66)
     at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.endpointActivation(AdapterServiceRevisionRegistry.java:608)
     at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.activate(AdapterServiceRevisionRegistry.java:438)
     at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.setDefaultRevision(AdapterServiceRevisionRegistry.java:403)
     at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceSeries.setDefaultRevision(AdapterServiceRevisionRegistry.java:328)
     at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceSeriesSet.setDefaultRevision(AdapterServiceRevisionRegistry.java:134)
     at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry.setDefaultRevision(AdapterServiceRevisionRegistry.java:96)
     at oracle.integration.platform.blocks.adapter.AdapterService.defaultRevisionChanged(AdapterService.java:309)
     at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.processDefaultInSeries(FabricKernelInitializerServlet.java:577)
     at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.run(FabricKernelInitializerServlet.java:526)
     at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
     at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
     at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Caused by: BINDING.JCA-12517
Endpoint Activation Error.
AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
The Resource Adapter Oracle Applications Adapter was unable to activate the endpoint oracle.tip.adapter.apps.AppsWFBesQueueDequeueActivationSpec:{QueueName=WF_BPEL_Q, DatabaseSchema=APPS, Consumer=ORA_850j4e1g8gsjcc9g6oo36e9h65, MessageSelectorRule=tab.user_data.event_name = 'oracle.apps.mas.soa.workorder2ar.trigger', AppsEventSchema=CUSTOM_SCHEMA} due to the following reason: javax.resource.ResourceException: Unable to find data source null
Please correct the reported issue and redeploy the BPEL process.
     at oracle.integration.platform.blocks.adapter.fw.impl.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:513)
     at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.performEndpointActivation(JCAEndpointActivation.java:637)
     at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.activateInboundJcaEndpoint(JCAEndpointActivation.java:620)
     at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.performActivation(JCAEndpointActivation.java:383)
     at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.endpointActivation(AdapterServiceRevisionRegistry.java:583)
     ... 11 more
Caused by: javax.resource.ResourceException: Unable to find data source null
     at oracle.tip.adapter.aq.v2.database.AppsDequeueAgentFactory.createAppsDequeueAgent(AppsDequeueAgentFactory.java:52)
     at oracle.tip.adapter.aq.v2.AppsEndpoint.activate(AppsEndpoint.java:51)
     at oracle.tip.adapter.aq.v2.jca.AQResourceAdapter.endpointActivation(AQResourceAdapter.java:62)
     at oracle.tip.adapter.apps.AppsResourceAdapter.endpointActivation(AppsResourceAdapter.java:152)
     at oracle.integration.platform.blocks.adapter.fw.impl.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:494)
     ... 15 more
Caused by: java.sql.SQLException: javax.resource.ResourceException: Unable to find data source null
     at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getDatabaseConnection(DBQueueFactory.java:97)
     at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getQueue(DBQueueFactory.java:68)
     at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getQueue(DBQueueFactory.java:216)
     at oracle.tip.adapter.aq.v2.database.AppsDequeueAgentFactory.createAppsDequeueAgent(AppsDequeueAgentFactory.java:49)
     ... 19 more
Caused by: javax.resource.ResourceException: Unable to find data source null
     at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getDataSourceConnection(AppsManagedConnectionFactory.java:429)
     at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getConnection(AppsManagedConnectionFactory.java:308)
     at oracle.tip.adapter.apps.AppsManagedConnection.getConnection(AppsManagedConnection.java:147)
     at oracle.tip.adapter.apps.AppsConnection.getJdbcConnection(AppsConnection.java:77)
     at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getDatabaseConnection(DBQueueFactory.java:94)
     ... 22 more
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.AppsDataSource'. Resolved 'jdbc'; remaining name 'AppsDataSource'
     at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
     at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
     at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
     at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
     at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
     at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
     at javax.naming.InitialContext.lookup(InitialContext.java:392)
     at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getDataSourceConnection(AppsManagedConnectionFactory.java:426)
     ... 26 more
<Aug 10, 2011 1:25:44 PM EDT> <Error> <oracle.integration.platform> <SOA-20020> <Deployment of composite "MIS_INB_WorkOrder_AR_Sync" failed: [JCABinding] [MIS_INB_WorkOrder_AR_Sync.consumeARTrgReq/1.0]Unable to complete initialization due to: Endpoint Activation Error.
AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
The Resource Adapter Oracle Applications Adapter was unable to activate the endpoint oracle.tip.adapter.apps.AppsWFBesQueueDequeueActivationSpec:{QueueName=WF_BPEL_Q, DatabaseSchema=APPS, Consumer=ORA_850j4e1g8gsjcc9g6oo36e9h65, MessageSelectorRule=tab.user_data.event_name = 'oracle.apps.mas.soa.workorder2ar.trigger', AppsEventSchema=CUSTOM_SCHEMA} due to the following reason: javax.resource.ResourceException: Unable to find data source null
Please correct the reported issue and redeploy the BPEL process.
: Endpoint Activation Error.
AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
The Resource Adapter Oracle Applications Adapter was unable to activate the endpoint oracle.tip.adapter.apps.AppsWFBesQueueDequeueActivationSpec:{QueueName=WF_BPEL_Q, DatabaseSchema=APPS, Consumer=ORA_850j4e1g8gsjcc9g6oo36e9h65, MessageSelectorRule=tab.user_data.event_name = 'oracle.apps.mas.soa.workorder2ar.trigger', AppsEventSchema=CUSTOM_SCHEMA} due to the following reason: javax.resource.ResourceException: Unable to find data source null
Please correct the reported issue and redeploy the BPEL process.

Hey,
I have setup weblogic 10.3.4 and SOA Suite 11g.
The adapters seem to be deployed and active with a green 'OK' status in the deployments on the soa_server1. However when I go to the jndi tree for the soa_server1, all the adapters have an '!' for errored out.
This is causing various problems. In particular when a process using the Oracle Apps Adapter is deployed it is unable to find the jdbc connection associated with the adapter. However, the jdbc jndi entry is in the tree and the jdbc connection test's just fine.
So there seems to be a missing link in how the adapters are deployed and how the JNDI is getting updated or something.
The error is below. Any help appreciated.
====> CubeEngine load MIS_INB_WorkOrder_AR_Sync/Process_WO_AR_Sync took 726 ms
INFO: DeploymentEventPublisher.invoke Publishing deploy event for default/MIS_INB_WorkOrder_AR_Sync!1.0*soa_85dcf1de-1d63-4b34-9f99-3e52c1f04366
<Aug 10, 2011 1:25:33 PM EDT> <Warning> <oracle.soa.services.notification> <BEA-000000> <<.> Notification via email, voice, SMS or IM will not be sent. If you would like to enable them, please configure corresponding sdpmessaging driver. Then modify the accounts and set NotificationMode attribute to either NONE, EMAIL or ALL in workflow-notification-config.xml>
INFO: SchemaManager.isIncrementalBuildSupported XMLSchema incremental build enabled.
<Aug 10, 2011 1:25:44 PM EDT> <Error> <oracle.soa.adapter> <BEA-000000> <JCABinding=> MIS_INB_WorkOrder_AR_Sync Error while performing endpoint Activation: javax.resource.ResourceException: Unable to find data source null>
<Aug 10, 2011 1:25:44 PM EDT> <Error> <oracle.soa.adapter> <BEA-000000> <JCABinding=> MIS_INB_WorkOrder_AR_Sync
javax.resource.ResourceException: Unable to find data source null
     at oracle.tip.adapter.aq.v2.database.AppsDequeueAgentFactory.createAppsDequeueAgent(AppsDequeueAgentFactory.java:52)
     at oracle.tip.adapter.aq.v2.AppsEndpoint.activate(AppsEndpoint.java:51)
     at oracle.tip.adapter.aq.v2.jca.AQResourceAdapter.endpointActivation(AQResourceAdapter.java:62)
     at oracle.tip.adapter.apps.AppsResourceAdapter.endpointActivation(AppsResourceAdapter.java:152)
     at oracle.integration.platform.blocks.adapter.fw.impl.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:494)
     at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.performEndpointActivation(JCAEndpointActivation.java:637)
     at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.activateInboundJcaEndpoint(JCAEndpointActivation.java:620)
     at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.performActivation(JCAEndpointActivation.java:383)
     at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.endpointActivation(AdapterServiceRevisionRegistry.java:583)
     at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.activate(AdapterServiceRevisionRegistry.java:438)
     at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.setDefaultRevision(AdapterServiceRevisionRegistry.java:403)
     at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceSeries.setDefaultRevision(AdapterServiceRevisionRegistry.java:328)
     at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceSeriesSet.setDefaultRevision(AdapterServiceRevisionRegistry.java:134)
     at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry.setDefaultRevision(AdapterServiceRevisionRegistry.java:96)
     at oracle.integration.platform.blocks.adapter.AdapterService.defaultRevisionChanged(AdapterService.java:309)
     at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.processDefaultInSeries(FabricKernelInitializerServlet.java:577)
     at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.run(FabricKernelInitializerServlet.java:526)
     at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
     at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
     at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Caused by: java.sql.SQLException: javax.resource.ResourceException: Unable to find data source null
     at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getDatabaseConnection(DBQueueFactory.java:97)
     at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getQueue(DBQueueFactory.java:68)
     at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getQueue(DBQueueFactory.java:216)
     at oracle.tip.adapter.aq.v2.database.AppsDequeueAgentFactory.createAppsDequeueAgent(AppsDequeueAgentFactory.java:49)
     ... 19 more
Caused by: javax.resource.ResourceException: Unable to find data source null
     at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getDataSourceConnection(AppsManagedConnectionFactory.java:429)
     at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getConnection(AppsManagedConnectionFactory.java:308)
     at oracle.tip.adapter.apps.AppsManagedConnection.getConnection(AppsManagedConnection.java:147)
     at oracle.tip.adapter.apps.AppsConnection.getJdbcConnection(AppsConnection.java:77)
     at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getDatabaseConnection(DBQueueFactory.java:94)
     ... 22 more
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.AppsDataSource'. Resolved 'jdbc'; remaining name 'AppsDataSource'
     at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
     at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
     at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
     at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
     at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
     at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
     at javax.naming.InitialContext.lookup(InitialContext.java:392)
     at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getDataSourceConnection(AppsManagedConnectionFactory.java:426)
     ... 26 more
>
oracle.fabric.common.FabricDeploymentException: [JCABinding] [MIS_INB_WorkOrder_AR_Sync.consumeARTrgReq/1.0]Unable to complete initialization due to: Endpoint Activation Error.
AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
The Resource Adapter Oracle Applications Adapter was unable to activate the endpoint oracle.tip.adapter.apps.AppsWFBesQueueDequeueActivationSpec:{QueueName=WF_BPEL_Q, DatabaseSchema=APPS, Consumer=ORA_850j4e1g8gsjcc9g6oo36e9h65, MessageSelectorRule=tab.user_data.event_name = 'oracle.apps.mas.soa.workorder2ar.trigger', AppsEventSchema=CUSTOM_SCHEMA} due to the following reason: javax.resource.ResourceException: Unable to find data source null
Please correct the reported issue and redeploy the BPEL process.
: Endpoint Activation Error.
AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
The Resource Adapter Oracle Applications Adapter was unable to activate the endpoint oracle.tip.adapter.apps.AppsWFBesQueueDequeueActivationSpec:{QueueName=WF_BPEL_Q, DatabaseSchema=APPS, Consumer=ORA_850j4e1g8gsjcc9g6oo36e9h65, MessageSelectorRule=tab.user_data.event_name = 'oracle.apps.mas.soa.workorder2ar.trigger', AppsEventSchema=CUSTOM_SCHEMA} due to the following reason: javax.resource.ResourceException: Unable to find data source null
Please correct the reported issue and redeploy the BPEL process.
{rootCauses=[]}
     at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry.access$3600(AdapterServiceRevisionRegistry.java:66)
     at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.endpointActivation(AdapterServiceRevisionRegistry.java:608)
     at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.activate(AdapterServiceRevisionRegistry.java:438)
     at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.setDefaultRevision(AdapterServiceRevisionRegistry.java:403)
     at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceSeries.setDefaultRevision(AdapterServiceRevisionRegistry.java:328)
     at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceSeriesSet.setDefaultRevision(AdapterServiceRevisionRegistry.java:134)
     at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry.setDefaultRevision(AdapterServiceRevisionRegistry.java:96)
     at oracle.integration.platform.blocks.adapter.AdapterService.defaultRevisionChanged(AdapterService.java:309)
     at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.processDefaultInSeries(FabricKernelInitializerServlet.java:577)
     at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.run(FabricKernelInitializerServlet.java:526)
     at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
     at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
     at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Caused by: BINDING.JCA-12517
Endpoint Activation Error.
AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
The Resource Adapter Oracle Applications Adapter was unable to activate the endpoint oracle.tip.adapter.apps.AppsWFBesQueueDequeueActivationSpec:{QueueName=WF_BPEL_Q, DatabaseSchema=APPS, Consumer=ORA_850j4e1g8gsjcc9g6oo36e9h65, MessageSelectorRule=tab.user_data.event_name = 'oracle.apps.mas.soa.workorder2ar.trigger', AppsEventSchema=CUSTOM_SCHEMA} due to the following reason: javax.resource.ResourceException: Unable to find data source null
Please correct the reported issue and redeploy the BPEL process.
     at oracle.integration.platform.blocks.adapter.fw.impl.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:513)
     at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.performEndpointActivation(JCAEndpointActivation.java:637)
     at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.activateInboundJcaEndpoint(JCAEndpointActivation.java:620)
     at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.performActivation(JCAEndpointActivation.java:383)
     at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.endpointActivation(AdapterServiceRevisionRegistry.java:583)
     ... 11 more
Caused by: javax.resource.ResourceException: Unable to find data source null
     at oracle.tip.adapter.aq.v2.database.AppsDequeueAgentFactory.createAppsDequeueAgent(AppsDequeueAgentFactory.java:52)
     at oracle.tip.adapter.aq.v2.AppsEndpoint.activate(AppsEndpoint.java:51)
     at oracle.tip.adapter.aq.v2.jca.AQResourceAdapter.endpointActivation(AQResourceAdapter.java:62)
     at oracle.tip.adapter.apps.AppsResourceAdapter.endpointActivation(AppsResourceAdapter.java:152)
     at oracle.integration.platform.blocks.adapter.fw.impl.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:494)
     ... 15 more
Caused by: java.sql.SQLException: javax.resource.ResourceException: Unable to find data source null
     at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getDatabaseConnection(DBQueueFactory.java:97)
     at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getQueue(DBQueueFactory.java:68)
     at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getQueue(DBQueueFactory.java:216)
     at oracle.tip.adapter.aq.v2.database.AppsDequeueAgentFactory.createAppsDequeueAgent(AppsDequeueAgentFactory.java:49)
     ... 19 more
Caused by: javax.resource.ResourceException: Unable to find data source null
     at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getDataSourceConnection(AppsManagedConnectionFactory.java:429)
     at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getConnection(AppsManagedConnectionFactory.java:308)
     at oracle.tip.adapter.apps.AppsManagedConnection.getConnection(AppsManagedConnection.java:147)
     at oracle.tip.adapter.apps.AppsConnection.getJdbcConnection(AppsConnection.java:77)
     at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getDatabaseConnection(DBQueueFactory.java:94)
     ... 22 more
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.AppsDataSource'. Resolved 'jdbc'; remaining name 'AppsDataSource'
     at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
     at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
     at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
     at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
     at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
     at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
     at javax.naming.InitialContext.lookup(InitialContext.java:392)
     at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getDataSourceConnection(AppsManagedConnectionFactory.java:426)
     ... 26 more
<Aug 10, 2011 1:25:44 PM EDT> <Error> <oracle.integration.platform> <SOA-20020> <Deployment of composite "MIS_INB_WorkOrder_AR_Sync" failed: [JCABinding] [MIS_INB_WorkOrder_AR_Sync.consumeARTrgReq/1.0]Unable to complete initialization due to: Endpoint Activation Error.
AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
The Resource Adapter Oracle Applications Adapter was unable to activate the endpoint oracle.tip.adapter.apps.AppsWFBesQueueDequeueActivationSpec:{QueueName=WF_BPEL_Q, DatabaseSchema=APPS, Consumer=ORA_850j4e1g8gsjcc9g6oo36e9h65, MessageSelectorRule=tab.user_data.event_name = 'oracle.apps.mas.soa.workorder2ar.trigger', AppsEventSchema=CUSTOM_SCHEMA} due to the following reason: javax.resource.ResourceException: Unable to find data source null
Please correct the reported issue and redeploy the BPEL process.
: Endpoint Activation Error.
AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
The Resource Adapter Oracle Applications Adapter was unable to activate the endpoint oracle.tip.adapter.apps.AppsWFBesQueueDequeueActivationSpec:{QueueName=WF_BPEL_Q, DatabaseSchema=APPS, Consumer=ORA_850j4e1g8gsjcc9g6oo36e9h65, MessageSelectorRule=tab.user_data.event_name = 'oracle.apps.mas.soa.workorder2ar.trigger', AppsEventSchema=CUSTOM_SCHEMA} due to the following reason: javax.resource.ResourceException: Unable to find data source null
Please correct the reported issue and redeploy the BPEL process.

Jndi tree different in different servers in a cluster?

I bind a Properties object in jndi tree and it comes up fine in one node
i.e. I can see it in the jndi tree on one Server.
But I cannot see it in another Server in the cluster. Any idea why this
behaviour?
the code looks like this:
Hashtable h = new Hashtable();
h.put(Context.INITIAL_CONTEXT_FACTORY, JNDITags.JNDI_FACTORY);
h.put(WLContext.CREATE_INTERMEDIATE_CONTEXTS, new
Boolean(true));
if (user != null) {
h.put(Context.SECURITY_PRINCIPAL, user);
if (pwd == null)
pwd = "";
h.put(Context.SECURITY_CREDENTIALS, pwd);
InitialContext ic = new InitialContext(h);
Context ctx = ic.createSubcontext( "yy");
ctx.bind( "lp", props );
ctx.close();
ic.close();
Komal

If you are trying to do the lookup "at startup time for server 2", the JNDI
replication may not be complete yet. We had a similar problem trying to deploy
MDBs against JMS destinations on remote servers...
komal mangtani wrote:
Can't a bind an object on 1 server and do a lookup on other server ?
Like in my case, when 1st server starts, it binds the object to the jndi
tree in its startup class.
Then the second server comes up and does a lookup on the same object in its
own startup class.
Isn't the jndi tree, suppose to get replicated to another server?
Komal.
komal mangtani wrote:
I bind a Properties object in jndi tree and it comes up fine in one node
i.e. I can see it in the jndi tree on one Server.
But I cannot see it in another Server in the cluster. Any idea why this
behaviour?
the code looks like this:
Hashtable h = new Hashtable();
h.put(Context.INITIAL_CONTEXT_FACTORY, JNDITags.JNDI_FACTORY);
h.put(WLContext.CREATE_INTERMEDIATE_CONTEXTS, new
Boolean(true));
if (user != null) {
h.put(Context.SECURITY_PRINCIPAL, user);
if (pwd == null)
pwd = "";
h.put(Context.SECURITY_CREDENTIALS, pwd);
InitialContext ic = new InitialContext(h);
Context ctx = ic.createSubcontext( "yy");
ctx.bind( "lp", props );
ctx.close();
ic.close();
Komal

Loading the JNDI Tree in a Cluster

Is there any special processing that occurs with a Startup class when it
          has been
          started via the cluster level properties file?
          We've got a class that loads the JNDI tree for various configuration for
          our application.
          It's written that so that it will rebind() entries in the tree, so two
          copies could work together
          in the cluster, but I'd like to prevent the double work. (One copy
          bind()s an element, then the other rebind()s the same value.
          Are Startups "cluster" aware, and is there any magic to simplify this
          for me (or do I do the
          work of creating a semaphore-like setup in my class to detect two copies
          running.)
          Thanks in Advance,
          Brian Homrich
          Chicago, Illinois


In the startup class on Environment object if you don't set
          replicatebindings to false, in a cluster all locally bound objects will be
          replicated. The default it true. So, jndi will try replicate every
          bind/rebind etc.
          Rebind will remove old copy and bind the new copy. But I have to understand
          more what you are trying to do, before I can be of any help.
          - Prasad
          Brian Homrich wrote:
          > Is there any special processing that occurs with a Startup class when it
          > has been
          > started via the cluster level properties file?
          >
          > We've got a class that loads the JNDI tree for various configuration for
          > our application.
          > It's written that so that it will rebind() entries in the tree, so two
          > copies could work together
          > in the cluster, but I'd like to prevent the double work. (One copy
          > bind()s an element, then the other rebind()s the same value.
          >
          > Are Startups "cluster" aware, and is there any magic to simplify this
          > for me (or do I do the
          > work of creating a semaphore-like setup in my class to detect two copies
          > running.)
          >
          > Thanks in Advance,
          >
          > Brian Homrich
          > Chicago, Illinois

Trouble in storing and retrieving RMI object in Weblogic 7 JNDI tree.

I have created a simple server (BankImpl), implementing a RMI interface
called Bank. A stub class (BankImpl_Stub.class) is generated from BankImpl
class using
"rmic -v1.2". Then I bind an instance of the BankImpl class to the JNDI tree
in Weblogic
server 7 under the name of "PeopleBank".
After the binding, I can see the stub class in the JNDI tree, but with a
different name: BankImpl_WLStub.class). when a
client program is trying to lookup the stub associated with "PeopleBank", it
failed with a puzzling message:
java.io.NotSerializableException: BankImpl_WLStub
Why a stub of a RMI object is not serializable? Does Weblogic needs a
different rmic to generate RMI stubs?
Thanks,
Lian

I have created a simple server (BankImpl), implementing a RMI interface
called Bank. A stub class (BankImpl_Stub.class) is generated from BankImpl
class using
"rmic -v1.2". Then I bind an instance of the BankImpl class to the JNDI tree
in Weblogic
server 7 under the name of "PeopleBank".
After the binding, I can see the stub class in the JNDI tree, but with a
different name: BankImpl_WLStub.class). when a
client program is trying to lookup the stub associated with "PeopleBank", it
failed with a puzzling message:
java.io.NotSerializableException: BankImpl_WLStub
Why a stub of a RMI object is not serializable? Does Weblogic needs a
different rmic to generate RMI stubs?
Thanks,
Lian

Added DataSource not in JNDI tree; WLS6.1SP1

I have added a new DataSource, but I don't see it in the JNDI tree? I have restarted the server after adding. (BTW if I check the examples server, not every name is in the JNDI tree either?! eg. examples-dataSource-demoPool is not in the tree; but examples-dataSource-demoXAPool is in the tree)
If possible please also reply to my email address... [email protected]

Thanks for your suggestion. I did this after adding the pool. I should have mentioned
this in my first post.
I have tried again to add a ConnectionPool and a DataSource: to my supprise it
was in the JNDI tree. So everything seemed OK now, but read on...
Because I couldn't access other PC's in my network (Weblogic is installed on my
laptop, which I used during the day without network connection) I rebooted my
laptop and the JNDI name was gone??? Must be something with IP addresses or so.
I will investigate and reply when I have figured it out.
Deepak Vohra <[email protected]> wrote:
Ben
Set the Targets Server.
Click on JDBC node. Click on Data Sources Node. Click on the DataSource
node. click on Targets tab. Choose a Targets Server. click Apply. The
added DataSource should get a JNDI binding.
Deepak
Ben Verloop wrote:
I have added a new DataSource, but I don't see it in the JNDI tree?I have restarted the server after adding. (BTW if I check the examples
server, not every name is in the JNDI tree either?! eg. examples-dataSource-demoPool
is not in the tree; but examples-dataSource-demoXAPool is in the tree)
If possible please also reply to my email address... [email protected]

Jndi tree

I am running WLS (non clustering) on two machines (Mach A and Mach B),
each host 1 bean (Bean A and Bean B). Bean A and B need to get
reference to one another. Are there 2 JNDI tree (one at each WLS) or is
there a way I can setup 1 JNDI tree so that both Beans can be looked up
at one JNDI url?

If these machines were clustered would you need to make this setting in the
properties file or would the cluster take care of it?
Cameron Purdy <[email protected]> wrote in message
news:8ghgnb$rol$[email protected]..
You can set up one to use the other. In your <jre>/lib/jndi.properties
file:
java.naming.factory.initial=jndi.WLInitialContextFactory
java.naming.provider.url=t3://<ipaddress>:<port>
Cameron Purdy, LiveWater
"David Tran" <[email protected]> wrote in message
news:[email protected]..
I am running WLS (non clustering) on two machines (Mach A and Mach B),
each host 1 bean (Bean A and Bean B). Bean A and B need to get
reference to one another. Are there 2 JNDI tree (one at each WLS) or is
there a way I can setup 1 JNDI tree so that both Beans can be looked up
at one JNDI url?

JNDI tree replicated to an external global naming service

Hi!
Is it possible to have a JNDI tree replicated to an external
global naming service? For instance, to merge two clusters
of WLS 5.1 servers from two different network zones?
Thanking you in advance,
Guillaume Bedard

Yes, you can use federation do achieve this but remember federation is
just putting a refence that points to the original JNDI provider and
doesn't really give you replication of the entire JNDI namespace.
Guillaume Bedard wrote:
Hi!
Can you elaborate as to what makes it impossible?
What if we "federate" the two clusters, which have their
own autonomous naming systems, by binding a reference to
these naming systems in another naming service?
Thanks,
Guillaume
"Raja Mukherjee" <[email protected]> wrote:
No
..raja
"Guillaume Bedard" <[email protected]> wrote in message
news:3cab4a00$[email protected]..
More specifically, I would like be able to join two clusters
(each having their own cluster-wide replicated naming tree)
by replicating their bindings into a global naming tree,
possibly hosted by a dedicated "jndi" server.
Guillaume
"Raja Mukherjee" <[email protected]> wrote:
My immediate response would be 'No', but I am confused as to what
are
you
trying to achieve?
..raja
"Guillaume Bedard" <[email protected]> wrote in message
news:3ca9cd9c$[email protected]..
Hi!
Is it possible to have a JNDI tree replicated to an external
global naming service? For instance, to merge two clusters
of WLS 5.1 servers from two different network zones?
Thanking you in advance,
Guillaume Bedard

Binding to jndi tree takes ages

Similar Messages

Maybe you are looking for