Unable to resolve JNDI DataSource in weblogic 12c When you upgrade web application

I create a datasource which jndi name is jdbc/allianzB2CDataSource and the target is AdminServer ,and i deploy a web application in AdminServer.In that web application,the code(base on spring framework) is:
public static DataSource getJndiDataSource(String name) {
JndiDataSourceLookup dsLookup = new JndiDataSourceLookup();
Properties jndiEnvironment = new Properties();
jndiEnvironment.put("java.naming.factory.initial",
"weblogic.jndi.WLInitialContextFactory");
dsLookup.setJndiEnvironment(jndiEnvironment);
try {
dsLookup.setResourceRef(false);
return dsLookup.getDataSource(name);
} catch (Exception e) {
dsLookup.setResourceRef(true);
return dsLookup.getDataSource(name);
And the parameter is jdbc/allianzB2CDataSource,everything work fine,but when i restart or upgrate the web application,i got the error like this:
javax.naming.NameNotFoundException: Unable to resolve 'jdbc.allianzB2CDataSource'. Resolved 'jdbc'; remaining name 'allianzB2CDataSource'
Unable to resolve 'jdbc.allianzB2CDataSource'. Resolved 'jdbc'; remaining name 'allianzB2CDataSource'

Similar Messages

Help required in Weblogic 6 - Creation & Configuration of Web Application

Forum Home > Enterprise JavaBeans[tm]
Topic: Help required in Weblogic 6 - Creation & Configuration of Web Application
Duke Dollars
2 Duke Dollars assigned to this topic. Reward the best responses to your question
using the icons below, or transfer additional Duke Dollars to this topic.
Welcome moinshariff!
Watching this topic.
Previous Topic Next Topic
This topic has 1 reply on 1 page (Most recent message: Jan 23, 2002 1:05 AM)
Author: moinshariff Jan 22, 2002 4:55 AM
Hi,
I am using Weblogic 6. I have created a new Web
Application called Web (I have not used the DefaultWebApp_myserver).
And I have the following settings:
Name : Web
URI : Web
and Path : C:\Web
and placed my JSP files under c:\Web\
I am able to access the first page, but after that I am not able to access the
second page.
I get "Error 404--Not Found" on the browser. Basically the class file is not getting
created under /Web-inf/_tmp_war_myserver_myserver_Web/jsp_servlet/ folder .
I tried a work around for this. I copied all my files under one more folder called
web and placed this under C:\Web
The it works. Now I have 2 copied off all the files, 1 copy under c:\web and another
copy under c:\web\web\.
If I have the files under DefaultWebApp_myserver and have the setting as
Name: DefaultWebApp_myserver
URI: DefaultWebApp_myserver
Path: .\config\mydomain\applications
everything works fine.
Can any one please let me know if there is any configuration which has to be done
so that I do not duplicate the code in 2 directories
Thanks in advance.
Regards,
Moin

Forum Home > Enterprise JavaBeans[tm]
Topic: Help required in Weblogic 6 - Creation & Configuration of Web Application
Duke Dollars
2 Duke Dollars assigned to this topic. Reward the best responses to your question
using the icons below, or transfer additional Duke Dollars to this topic.
Welcome moinshariff!
Watching this topic.
Previous Topic Next Topic
This topic has 1 reply on 1 page (Most recent message: Jan 23, 2002 1:05 AM)
Author: moinshariff Jan 22, 2002 4:55 AM
Hi,
I am using Weblogic 6. I have created a new Web
Application called Web (I have not used the DefaultWebApp_myserver).
And I have the following settings:
Name : Web
URI : Web
and Path : C:\Web
and placed my JSP files under c:\Web\
I am able to access the first page, but after that I am not able to access the
second page.
I get "Error 404--Not Found" on the browser. Basically the class file is not getting
created under /Web-inf/_tmp_war_myserver_myserver_Web/jsp_servlet/ folder .
I tried a work around for this. I copied all my files under one more folder called
web and placed this under C:\Web
The it works. Now I have 2 copied off all the files, 1 copy under c:\web and another
copy under c:\web\web\.
If I have the files under DefaultWebApp_myserver and have the setting as
Name: DefaultWebApp_myserver
URI: DefaultWebApp_myserver
Path: .\config\mydomain\applications
everything works fine.
Can any one please let me know if there is any configuration which has to be done
so that I do not duplicate the code in 2 directories
Thanks in advance.
Regards,
Moin

How to use jndi datasource on Weblogic instead of adding a DB data source

Hi All,
version: 11.1.1.4
I am trying to figure out how in my ADF applications I can use an existing jndi datasource out on our weblogic servers instead of having to bury the Database db source in my adf applications. Like SOA I would like to reference the DB directly during design so I can pull in entities and build view objects, but when I deploy I want it to reference the jndi datasource out on the weblogic server.
Is this possible? If so I am not sure how to configure it like I would a DB adapter in SOA.
As always appreciate the info.
Thanks,
S

If you use ADF in the model layer (application modules) you can configure them to use JNDI Datasources. Just right click on the application module and select 'Configurations...'. In the next dialog you see all the configurations currently available (one named xxxxxlocal and one named xxxxxshared at least). Select the local and hit the edit button. This open the DB connect dialog where you can change the connection from JDBC URL to JDBC Datasource (JNDI). Save your work and when you now start the app it will use the JNDI name.
Timo

OSB installed in WebLogic 12C - when it will be supported

As I believed that OSB is nothing more than a webaplication with specific tables in Oracle database I imagined that I could try to install OSB in WebLogic12C. Maybe I am telling a stupid thing because I can see that after installed OSB, there is a specific new server on WebLogic console.
Anyway, even if it was right, there a huge difference between I installed locally to test and I confirmed to do this without comercial support. Then, my question is: Is there some prediction about OSB, OER, OSR (SOA tools) be supported in WebLogic 12C? The more important for me is OSB.
Other question is: is there some prediction about new version of OSB? If so, this probably will work by default at weblogic 12c.

Anyway, even if it was right, there a huge difference between I installed locally to test and I confirmed to do this without comercial supportYou are correct. As Abhishek has already mentioned, OSB is not merely a web-app and it is tightly integrated with Weblogic app server. So there is no meaning putting any effort to try to get it work on Weblogic 12c.
Is there some prediction about OSB, OER, OSR (SOA tools) be supported in WebLogic 12C? The more important for me is OSB.It is too early to talk about 12c but yes, all these products will be part of OFMW 12c.
Other question is: is there some prediction about new version of OSB? If so, this probably will work by default at weblogic 12c.The next version of OSB will be 11g R1 patch set 6 (11.1.1.7) and hence it will only be certified with Weblogic 10.3.7
Regards,
Anuj

How to resolve the "Builld error mxmlc task failed" in flex4 web application

hi all,
I am using flex 4 mxml web application wiht as3. when i deploying this project i am facing the folling error.
Environment:
Flex 3.5 SDK
Flash builder 4 .                 APPLICATION NAME: BillProcess
Ant compile tasks
============
    <property name="FLEX_HOME" value="C:\Program Files\Adobe\Adobe Flash Builder 4\sdks\3.5.0/>
    <property name="JAVA_HOME" value="C:\Program Files\Java\jdk1.6.0_06"/>
    <property name="JRE_HOME" value="C:\Program Files\Java\jre1.6.0_06"/>
ERROR:
init:
[ippprojectproperties] qbServer = workplace.intuit.com
   [delete] Deleting directory C:\Documents and Settings\TIVL\Adobe Flash Builder 4\BillProcess\Dev
    [mkdir] Created dir: C:\Documents and Settings\TIVL\Adobe Flash Builder 4\BillProcess\Dev
checkForCustomBuild:
custombuild:
dependentProjects:
compile:
[ippflexbuild] Parsing: C:\Documents and Settings\TIVL\Adobe Flash Builder 4\BillProcess/.actionScriptProperties
BUILD FAILED
C:\Documents and Settings\TIVL\Adobe Flash Builder 4\BillProcess\ippbuild.xml:101: mxmlc task failed
Total time: 16 seconds.
HOW TO RESOLVE THIS.
please share your useful suggession,
cheers,
B.venkatesan.

hello,
Check out this link http://www.kirupa.com/forum/showthread.php?309387-ant-mxmlc-task-don-t-compile-with-FlexSD K-4 this may solve your problem.
                     Gajanan Hiroji | [email protected] | www.isacglobal.com

Can you reload web application from the Weblogic console?

          Good day, eh!
          Can you reload all your jsp/servlet classes of your
          web application from the Weblogic console?
          A one big button labeled 'Reload application' would be very
          good property in Weblogic
          Thanks for Your answers
          - hoser


Hi,
          I agree it is a much needed feature. Suppose I just change an init
          param of one application in the web.xml, I don't want to take down the
          15 other webapps running on my server just to be able to have that web
          app restart and re-read is configuration. Of course, I could program
          some servlet that allows changing application attributes and to enable
          restarting, but really this a)does not cover all the cases (i.e. addind
          an EBJ reference binding to web.xml) b) should be provided by the app
          server, not programmed by every little programmer again & again.
          Mathieu
          Jeff Nowakowski wrote:
          >
          > The URL you give refers to redeploying EJBs, not web applications. Being
          > able to redeploy a web application would be a very convenient feature.
          >
          > -Jeff
          >
          > Gene Chuang <[email protected]> wrote in message news:[email protected]...
          > > Button is already there!
          > >
          > > http://www.weblogic.com/docs51/techdeploy/hotdeploy.html#consoledeployejb
          > >
          > > Gene
          > >
          > > "hoser" <[email protected]> wrote in message
          > > news:[email protected]...
          > > >
          > > > Good day, eh!
          > > >
          > > > Can you reload all your jsp/servlet classes of your
          > > > web application from the Weblogic console?
          > > >
          > > > A one big button labeled 'Reload application' would be very
          > > > good property in Weblogic
          > > >
          > > > Thanks for Your answers
          > > >
          > > > - hoser
          > >
          > >

Unable to start node manager of WebLogic 12c on OEL 5.9 64 bit

Hi,
I have WLS 12 running on OEL 5.9 64 bit.
The installation ise JDK instead of the default JRockit.
The version of Java that has been installed is from rpm: jdk-7u25-linux-x64.rpm
I have created a domain.
I am unable to start the Node Manager the first time, and thus unable to create the file nodemanager.properties.
I get an error:
weblogic.nodemanager.common.ConfigException: Native version is enabled but nodemanager native library could not be loaded
I have added JAVA_USE_64BIT=true in the commEnv.sh, but it seems not to help.
Does someone know how to get the nodde manager runing on a Linux x86 64 bit?
Thanks by advance for any tip.

Hello, try this:
1. Set the environment to use the 64 bit WLS library:
export LD_LIBRARY_PATH=
/u01/Middleware/wlserver_10.3/server/native/linux/x86_64/:/u01/Middleware/wlserver_10.3/server/native/linux/i686/
2. Retry the domain configuration:
/u01/Middleware/Oracle_PFRD/bin/config.sh

Install weblogic 12c

can i install adf 11.1.1.6 on weblogic 12c ?
then , upgrade adf 11.1.1.6 up to 11.1.2.3 (JDeveloper) ?
and there is any guide to install weblogic 12c and adf 11.1.1.6 ??
can any body tell me , it 's urgent

AFAIK, ADF is not currently supported in WLS 12.1.1 version.

Adobe-livecycle-weblogic.ear deployment issue on weblogic 12c

Hi All,
I am trying to install livecycle 3 on weblogic 12c. but in configuration manager adobe-livecycle-weblogic.ear is not getting deployed when packaged JDBC is selected
has anyone faced this isse before...

Hi Ravi,
WebLogic 12c is not a supported Application Server for LiveCycle ES3.
You can visit http://help.adobe.com/en_US/livecycle/10.0/supported_platforms.html for a list of supported Application Servers for LiveCycle ES3.
Thanks and Regards,
Hina Rastogi

FRM - 40105 : Unable to resolve reference to item item name

Hi,
FRM - 40105 : Unable to resolve reference to item <item name>
When I am opening a form I am getting the above mentioned error. Instead of <Item name> how we can display the error like <:CTRL_BLK.DOC_DATE>
Thanks & Regards,
Jenson

Hi,
Actually I know what is the reason for getting this error. What I tried to ask you is any way to display the item name, which error is occurred.
In the form around more than hundred item setting the SET_ITEM_PROPERTY , there only I am getting this error. Like this around more than five form I have to debug. I would like to know through error handling routine or some other code we can display the exact item name, which error is occurred.
Thanks & Regards,
Jenson V.A.

Failed to start web application in weblogic server 11g R1 RBACx

Hi friends,
I have an error when starting Oracle Identity Analitycs 11g R1, someone can help me solve the problem
Log Weblogic Server server when starting the web application rbacx.war:
####<Apr 7, 2011 11:57:37 AM GMT-05:00> <Warning> <HTTP> <vkpeoplesoft000> <RbacxAdmin> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302195457218> <BEA-101162> <User defined listener org.springframework.web.util.Log4jConfigListener failed: java.lang.IllegalStateException: Cannot set web app root system property when WAR file is not expanded.
java.lang.IllegalStateException: Cannot set web app root system property when WAR file is not expanded
at org.springframework.web.util.WebUtils.setWebAppRootSystemProperty(WebUtils.java:139)
at org.springframework.web.util.Log4jWebConfigurer.initLogging(Log4jWebConfigurer.java:118)
at org.springframework.web.util.Log4jConfigListener.contextInitialized(Log4jConfigListener.java:47)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1863)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
####<Apr 7, 2011 11:57:37 AM GMT-05:00> <Info> <Deployer> <vkpeoplesoft000> <RbacxAdmin> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302195457234> <BEA-149059> <Module rbacx.war of application rbacx is transitioning from STATE_ADMIN to STATE_PREPARED on server RbacxAdmin.>
####<Apr 7, 2011 11:57:37 AM GMT-05:00> <Info> <ServletContext-/rbacx> <vkpeoplesoft000> <RbacxAdmin> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1302195457234> <BEA-000000> <Shutting down log4j>
####<Apr 7, 2011 11:57:37 AM GMT-05:00> <Info> <Deployer> <vkpeoplesoft000> <RbacxAdmin> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302195457265> <BEA-149060> <Module rbacx.war of application rbacx successfully transitioned from STATE_ADMIN to STATE_PREPARED on server RbacxAdmin.>
See the full log:
http://yourpaste.net/7984
Grateful

No wonder you are having problems. The document you have linked to is full of errors and inconsistencies.
Anyway, find log4j.properties under your expanded war file location and update it so that
log4j.appender.file.file=logs/rbacx.log
is updated to point to a location that exists and is writable by weblogic, eg:
log4j.appender.file.file=/opt/oracle/weblogic/user_projects/OIA/logs/rbacx.log

JNDI naming exception...unable to resolve 'weblogic.management.adminhome'

I'm able to start admin server and access admin console (web). When I try to connect to admin server from managed server using WLST, I'm getting the error "compatibility mbean server is not initialized properly....". I tried to ping admin server from managed server using WLST ping command (java weblogic.Admin -url xxxxx -username xxxx-password xxxx PING), I'm getting error "JNDI naming exception....unable to resolve 'weblogic.management.adminhome'".

In order to run it remotely, I need to manually export the EAR file from Eclipse, ftp to the remote server and deploy it to the managed server.
It seems that I missed some jar files in the managed server classpath. But, I don't know which.

Javax.naming.NameNotFoundException: Unable to resolve 'ATGProductionDS'   - in Weblogic on starting the server

Hi,
I am not able to resolve the JNDI name - ATGProductionDS
I have used CIM to create this and i am using ATG10.2 with MYSQL as my database and weblogic.
/atg/epub/file/ConfigFileSystem journaling file system started: vfs=file:/C:
/Stixs/ATG/ATG10.2/home/PublishingAgent/deploymentconfig/live/config/ journalDirectory=C:\Stixs\ATG\ATG10.2\home\PublishingAgent\deploymentc
onfig\data\config
**** Error      Fri Dec 27 20:58:35 EST 2013    1388195915495   /atg/dynamo/service/jdbc/DirectJTDataSource     Failed to resolve ATGProduct
ionDS   javax.naming.NameNotFoundException: Unable to resolve 'ATGProductionDS'. Resolved ''; remaining name 'ATGProductionDS'
**** Error      Fri Dec 27 20:58:35 EST 2013    1388195915495   /atg/dynamo/service/jdbc/DirectJTDataSource             at weblogic.jndi.int
ernal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
**** Error      Fri Dec 27 20:58:35 EST 2013    1388195915495   /atg/dynamo/service/jdbc/DirectJTDataSource             at weblogic.jndi.int
Entries from Weblogic console -datasources
ATGBatchDS
Generic
ATGBatchDS
ATGProductionDS
Generic
ATGProductionDS
atg_production_lockserver, atg_publishing_lockserver
ATGPublishingDS
Generic
ATGPublishingDS
atg_publishing_lockserver
Please provide assistance.

Hi,
if you click the "Control" tab for the ATGProductionDS datasource in the Weblogic console does it show the State as running?
Does the "Monitoring" tab for the datasource show the State as running? If you click on the "Testing" tab can you test the datasource successfully?
If you inspect the Server using the Weblogic console there is a link "View JNDI Tree" If you click the link do you see the datasource listed in the left pane?
Do you see any errors for the ATGProductionDS in the Weblogic server log and out log files?

Unable to do JNDI lookup in JDeveloper-Weblogic server

Dear All,
I'm getting the below error when i try to call stateless EJB which is deployed in Weblogic 10.3 from the java stand alone class.
javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7101: Destination unreachable; nested exception is:
     java.io.IOException: Empty server reply; No available router to destination]
     at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
     at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:788)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:366)
     at weblogic.jndi.Environment.getContext(Environment.java:315)
     at weblogic.jndi.Environment.getContext(Environment.java:285)
     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
     at javax.naming.InitialContext.init(InitialContext.java:223)
     at javax.naming.InitialContext.<init>(InitialContext.java:197)
     at HelloWorldClient.main(HelloWorldClient.java:21)
Caused by: java.net.ConnectException: t3://localhost:7101: Destination unreachable; nested exception is:
     java.io.IOException: Empty server reply; No available router to destination
     at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:216)
     at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
     at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
     at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:345)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)
     ... 8 more
Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
     java.io.IOException: Empty server reply; No available router to destination
     at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:470)
     at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:321)
     at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:254)
     at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
     at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
     at weblogic.rjvm.RJVMFinder.findOrCreateRemoteCluster(RJVMFinder.java:316)
     at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:205)
     ... 14 more
The Client code is :
Hashtable<String, String> env = new Hashtable<String, String>();
env.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
env.put(Context.SECURITY_PRINCIPAL,"weblogic");
env.put(Context.SECURITY_CREDENTIALS,"weblogic123");
env.put(Context.PROVIDER_URL,"t3://localhost:7101");
Context ctx = new InitialContext(env); // Error throws here.
System.out.println("Initial Context created");
I'm able to login localhost as admin console and see the JNDI name binding. But dont know why it throws this error.
Kindly help me out to resolve this issue.

Sir,
First of all pls try giving jdeveloper version...
can you try other combinations
like instead of 127.0.0.1, use localhost, actual ip of PC. Because when you are using 11.1.2.x.x version then before creating default domain jdeveloper asks the IP address to bind and make server accessible from that IP...
At-Last if problem is not solved then
Try this:
1) start integrated weblogic server from jdeveloper by selecting Run -> Start Server Instance
2) when weblogic is up go to http://localhost:7101/console
3) login (username weblogic password weblogic1), go to services, go to jdbc and create your datasource
4) shut weblogic down
5) goto C:\Documents and Settings\<your username>\Application Data\JDeveloper\system11.1.1.2.36.55.36\DefaultDomain\bin the path may be different depending on your version of jdeveloper
6) edit setDomainEnv.cmd and change "set WLS_JDBC_REMOTE_ENABLED=-Dweblogic.jdbc.remoteEnabled=true"
7) go back to jdev and start weblogic as above

Unable to resolve 'weblogic.messaging.dispatcher.S:null'

We have a WLS 10.3 cluster with 1 admin server and 2 managed servers. Each managed server hosts JMS queues so we have a distributed queue environment. Applications periodically report an issue that prevents messages from being dropped onto the queues. The frequency of the issue is weekly and sometimes multiple times during the week. We have found that un-targeting and re-targeting the JMS Servers seems to resolve the problem (at least in the short term). The message producer applications are using the weblogic.jar and an xa connection factory. I've included the stack trace below. I'm hoping that someone can help uncover the root cause of the issue.
Stack Trace:
Caused by: weblogic.jms.common.JMSException: No failover destination.
at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:61)
at weblogic.jms.client.JMSProducer.toFEProducer(JMSProducer.java:1275)
at weblogic.jms.client.JMSProducer.deliveryInternal(JMSProducer.java:783)
at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:541)
at weblogic.jms.client.JMSProducer.sendWithListener(JMSProducer.java:394)
at weblogic.jms.client.JMSProducer.send(JMSProducer.java:384)
at weblogic.jms.client.WLProducerImpl.send(WLProducerImpl.java:970)
at org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:597)
at org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:574)
at org.springframework.jms.core.JmsTemplate$4.doInJms(JmsTemplate.java:551)
at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:471)
... 8 more
Caused by: weblogic.jms.common.JMSException: No failover destination.
at weblogic.jms.frontend.FEProducer.pickNextDestination(FEProducer.java:750)
at weblogic.jms.frontend.FEProducer.sendRetryDestination(FEProducer.java:1092)
at weblogic.jms.frontend.FEProducer.send(FEProducer.java:1399)
at weblogic.jms.frontend.FEProducer.invoke(FEProducer.java:1460)
at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:961)
at weblogic.messaging.dispatcher.DispatcherServerRef.invoke(DispatcherServerRef.java:276)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:141)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: weblogic.messaging.dispatcher.DispatcherException: could not find Server null
at weblogic.messaging.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:176)
at weblogic.messaging.dispatcher.DispatcherManager.dispatcherFindOrCreate(DispatcherManager.java:58)
at weblogic.jms.dispatcher.JMSDispatcherManager.dispatcherFindOrCreate(JMSDispatcherManager.java:219)
at weblogic.jms.dispatcher.JMSDispatcherManager.dispatcherFindOrCreateChecked(JMSDispatcherManager.java:230)
at weblogic.jms.frontend.FEProducer.findDispatcher(FEProducer.java:825)
at weblogic.jms.frontend.FEProducer.sendRetryDestination(FEProducer.java:995)
... 9 more
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:null'. Resolved 'weblogic.messaging.dispatcher'; remaining name 'S:null'
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.BasicNamingNode.lookup(BasicNamingNode.java:214)
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:380)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at weblogic.messaging.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:172)
... 14 more

Hi,
I would suggest you to go through these 2 links which you give all the details about UDD
Topic:Steps to Configure Uniform Distributed Queue (UDQ) on Weblogic Server
http://middlewaremagic.com/weblogic/?p=3747
Topic:JMS Demo using WebLogic Uniform Distributed Queue (UDQ)
http://middlewaremagic.com/weblogic/?page_id=1976
Tips to solve UDQ issues
- Make sure the Server Affinity Enabled parameter should be un-checked (disable) which under the [ Connection factory –> Configuration (tab) –> Load Balance (sub-tab)]
- Disable the Server Affinity Enabled parameter for the connection factory whish is been used by your UDQ.
- All the managed servers are in the same cluster.
- If the managed serves are in different boxes make sure the listing address is given correctly which is under [ Machine –> Configuration (tab) –> Node Manager (sub-tab) ]
- Test if you are able to PING the servers on different boxes and make sure that there is no network issues and you are able to communicate with the servers.
Hope this helps you.
Regards,
Ravish Mody
http://middlewaremagic.com/weblogic/
Come, Join Us and Experience The Magic…

Unable to resolve JNDI DataSource in weblogic 12c When you upgrade web application

Similar Messages

Maybe you are looking for