Naming exception

I need to start a servlet on server startup. It has to do some database operations, I have to get the Connection from ConnetionPool factory.<br>
It is using this code:<p>
Context initCtx = new InitialContext();
Context envCtx = (Context) initCtx.lookup( "java:comp/env" );
DataSource ds = (DataSource)envCtx.lookup( "jdbc/cmsdb" );
con = ds.getConnection();
<br>
but i am getting exception like this:<p>
javax.naming.NamingException: Not in an application scope - start Orion with t
-userThreads switch if using user-created threads
at com.evermind.server.PreemptiveApplicationContext.getContext(Preempt
eApplicationContext.java:34)
at com.evermind.naming.FilterContext.lookup(FilterContext.java:138)
at javax.naming.InitialContext.lookup(Unknown Source)
please any one tell me what is this exception meaning....
Thanks in advance

JDev 3.0 works with rdbms 8.1.5 only --
both have gone out of support as of dec 31, 2000.
use :
JDev 3.1.x.x with rdbms 8.1.6 or ias 8i. JDev 3.2.x.x with rdbms 8.1.7 or ias 9i.
null

Similar Messages

Naming exception from the pcd... occurred in PI 7.1

In PI 7.1 Iu2019ve got a process which gets invoked as SOAP service and synchronously calls a second SOAP service. The service returns the correct result and works, when called from the Web Services Navigator. When I call the Service on PI the Web Services Navigator only shows a NullPointerException (although the service gets invoked). The Message Monitoring of the Runtime Workbench doesnu2019t show any Message at all.
I looked at the Trace-Log and found the Message:
Naming exception from the pcd when trying to access the principal ROLE.PCD_ROLE_PERSISTENCE.VvlvkEGjiW9zPFaxR/4pd2/bX5Q=
Has anybody got an idea what could cause this behavior or how one can solve this problem? As far as I could find out PCD_ROLE_PERSISTENCE is part of the portal which is not meant to be Part of PI.
Regards,
Tarik

Hello Osman,
We are also facing same ROLE.PCD_ROLE_PERSISTENCE.VvlvkEGjiW9zPFaxR/4pd2/bX5Q= error.
Also when I send a message via SAOPUI I get error:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.ConfigException: Some of the IS access information is not available. SLDAccess property may be set to true, but SLD is not available.
How did you exactly solve your issue?
System: PI 7.1
SP: 71006

Weblogic.deploy causes JNDI naming exception resp java.io.StreamCorruptedException

Help needed!
I'm using WLS6.1 with SP1.
Calling weblogic.deploy on command line causes the following exceptions no
matter if i'm using list or deploy option:
java weblogic.deploy -port 7501 list 12345678
java.io.StreamCorruptedException: Type code out of range, is 0
at java.io.ObjectInputStream.peekCode(ObjectInputStream.java:1280)
at
java.io.ObjectInputStream.SkipToEndOfBlockData(ObjectInputStream.java:1211)
at
java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java:776)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:353)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:232)
at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:978)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:232)
at
weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectIn
putStream.java:107)
at
weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectIn
putStream.java:115)
at
weblogic.rjvm.ConnectionManager.readPeerInfo(ConnectionManager.java:686)
at
weblogic.rjvm.ConnectionManagerClient.handleIdentifyResponse(ConnectionManag
erClient.java:140)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:627)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java,
Compiled Code)
at
weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java,
Compiled Code)
at
weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java,
Compiled Code)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
Code)
--------------- nested within: ------------------
weblogic.utils.AssertionError: ***** ASSERTION FAILED ***** - with nested
exception:
[java.io.StreamCorruptedException: Type code out of range, is 0]
at
weblogic.rjvm.ConnectionManager.readPeerInfo(ConnectionManager.java:688)
at
weblogic.rjvm.ConnectionManagerClient.handleIdentifyResponse(ConnectionManag
erClient.java:140)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:627)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java,
Compiled Code)
at
weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java,
Compiled Code)
at
weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java,
Compiled Code)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
Code)
JNDI naming exception: Naming exception trying to connect to:
t3://localhost:7501 as: system: beaadmin

yes, that was the reason.
thank you very much!
"Dimitri Rakitine" <[email protected]> schrieb im Newsbeitrag
news:[email protected]...
That sounds like you use 1.2 on the client side - make sure that you use1.3.
>
In weblogic.developer.interest.ejb Nora Serinek <[email protected]>
wrote:
Help needed!
I'm using WLS6.1 with SP1.
Calling weblogic.deploy on command line causes the following exceptionsno
matter if i'm using list or deploy option:
java weblogic.deploy -port 7501 list 12345678
java.io.StreamCorruptedException: Type code out of range, is 0
at
java.io.ObjectInputStream.peekCode(ObjectInputStream.java:1280)
at
java.io.ObjectInputStream.SkipToEndOfBlockData(ObjectInputStream.java:1211)
at
java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java:776)
atjava.io.ObjectInputStream.readObject(ObjectInputStream.java:353)
atjava.io.ObjectInputStream.readObject(ObjectInputStream.java:232)
atjava.io.ObjectInputStream.inputObject(ObjectInputStream.java:978)
atjava.io.ObjectInputStream.readObject(ObjectInputStream.java:369)
atjava.io.ObjectInputStream.readObject(ObjectInputStream.java:232)
at
weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectIn
putStream.java:107)
at
weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectIn
putStream.java:115)
at
weblogic.rjvm.ConnectionManager.readPeerInfo(ConnectionManager.java:686)
at
weblogic.rjvm.ConnectionManagerClient.handleIdentifyResponse(ConnectionManag
erClient.java:140)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:627)
atweblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java,
Compiled Code)
at
weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java,
Compiled Code)
at
weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java,
Compiled Code)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java,Compiled
Code)
--------------- nested within: ------------------
weblogic.utils.AssertionError: ***** ASSERTION FAILED ***** - withnested
exception:
[java.io.StreamCorruptedException: Type code out of range, is 0]
at
weblogic.rjvm.ConnectionManager.readPeerInfo(ConnectionManager.java:688)
at
weblogic.rjvm.ConnectionManagerClient.handleIdentifyResponse(ConnectionManag
erClient.java:140)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:627)
atweblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java,
Compiled Code)
at
weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java,
Compiled Code)
at
weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java,
Compiled Code)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java,Compiled
Code)
JNDI naming exception: Naming exception trying to connect to:
t3://localhost:7501 as: system: beaadmin--
Dimitri

JNDI naming exception: javax.naming.ServiceUnavailableException

Hi,
I am running a standalone version of WLS 6.1 sp4. When I start WLS, it throws
this exception:
<Mar 19, 2004 2:39:11 PM PST> <Critical> <Log Management> <Unable
to contact managed server - med1d2ms01, at d_conitti/10.0.4.81:7301.
Domain logfile will notcontain messages from this server.
java.lang.IllegalArgumentException: JNDI naming exception: javax.naming.ServiceUnavailableException
[Root exception is java.net.UnknownHostException: d_conitti]
However, weblogic doesn't shut down after this. It continues and deploys all the
apps. What intrigues me is, where is weblogic reading the 'd_conitti' managed
server from. I am not running any cluster. It beats me totally. I searched for
'd_conitti' on my whole machine. I didn't find any file with that word.
My environment is:
Win2k Server
wls 6.1 sp4
jdk 1.3.1
I would appreciate any help.
Thanks,
Abbas

Hi,
I am running a standalone version of WLS 6.1 sp4. When I start WLS, it throws
this exception:
<Mar 19, 2004 2:39:11 PM PST> <Critical> <Log Management> <Unable
to contact managed server - med1d2ms01, at d_conitti/10.0.4.81:7301.
Domain logfile will notcontain messages from this server.
java.lang.IllegalArgumentException: JNDI naming exception: javax.naming.ServiceUnavailableException
[Root exception is java.net.UnknownHostException: d_conitti]
However, weblogic doesn't shut down after this. It continues and deploys all the
apps. What intrigues me is, where is weblogic reading the 'd_conitti' managed
server from. I am not running any cluster. It beats me totally. I searched for
'd_conitti' on my whole machine. I didn't find any file with that word.
My environment is:
Win2k Server
wls 6.1 sp4
jdk 1.3.1
I would appreciate any help.
Thanks,
Abbas

Naming Exception error in initiate task

Hi guys, I'm really in need of help. I'm getting naming exception error in my initiate task. There is no error code from bpel. I had copied my workflow from my development server (using oracle 10g) to my production server (using oracle 9i). I did not get this error when I'm in my development server.
The difference between these two servers are:
1) IP address
2) Oracle database version as stated above
3) domain name
The initiate task is just after setsystemdefineattribute and before my next task of sending email. The error did not halt the workflow but continue to the task of sending email.
Can someone help me? I can't seems to find the error which cause this problem.

I've found out the reason why I'm getting the naming exception error. It is due to wrong configuration in is_config.xml. I'm using Active Directory instead of JAZN and somehow I configure it wrongly to get the error.
I've switch back to JAZN XML base provider and it is working fine now but I would want to use the active directory as my identity service provider.
Currently my active directory in my production server is win2000. I'm using the is_config_for_activedirectory template but I still don't understand what values is needed to provide for the is_config.
Below are some of the items I don't understand.
1) Can I still use this if my AD is on win2k? If not, what should i use as I'm using AD as my id service provider now.
2) The default xmlns after the tag <BPMIdentityServiceConfig> do we need to change it? If so, to what values?
3) What is this property name and values after the providerType?
4) What is needed for binddn? I only know what to put for ou and dc but I'm not sure about cn.
5) What is this password for and whose password?
6) The whole lot under userControls and roleControl, I'm totally lost.
I've read through the Identity Service Provider (16.7.1) but I still can't understand how to config the active directory part.
I really hope someone could help enlighten me on this. Thanks
Hi guys, I'm really in need of help. I'm getting
naming exception error in my initiate task. There is
no error code from bpel. I had copied my workflow
from my development server (using oracle 10g) to my
production server (using oracle 9i). I did not get
this error when I'm in my development server.
The difference between these two servers are:
1) IP address
2) Oracle database version as stated above
3) domain name
The initiate task is just after
setsystemdefineattribute and before my next task of
sending email. The error did not halt the workflow
but continue to the task of sending email.
Can someone help me? I can't seems to find the error
which cause this problem.

DataSource CORP_LDAP: Naming exception when trying to create principal

Using NetWeaver 6.40 SP 15.
I have configured the UME to use writable LDAP and database. Specifically, for LDAP I'm using the Sun One Directory Server. I'm able to authenticate using one of the LDAP users using a Web Dynpro app.
When I try to create a user through the NWA web app, I simply get a "Could not create user" error in the application. In the server instance "security.log" I found the following:
Date : 03/08/2006
Time : 16:22:59:248
Message : DataSource CORP_LDAP: Naming exception when trying to create principal ***************************************************************************
com.sap.security.core.persistence.imp.PrincipalDatabagMaint Wed Mar 08 16:22:59 CST 2006
UniqueID: USER.CORP_LDAP.testuser
Type: USER
Home data source: CORP_LDAP
Private id part: testuser
"com.sap.security.core.usermanagement"|->"uniquename" (no time limit)="testuser"
"com.sap.security.core.usermanagement"|->"department" (no time limit)="CI&T"
"com.sap.security.core.usermanagement"|->"PRINCIPAL_CREATION_DATE" (no time limit)="0001141856579248"
"com.sap.security.core.usermanagement"|->"firstname" (no time limit)="user"
"com.sap.security.core.usermanagement"|->"lastname" (no time limit)="test"
"com.sap.security.core.usermanagement"|->"PRINCIPAL_TYPE_ATTRIBUTE" (no time limit)="USER"
"com.sap.security.core.usermanagement"|->"email" (no time limit)="[email protected]"
"com.sap.security.core.usermanagement"|->"company" (no time limit)=""
"com.sap.security.core.usermanagement"|->"accessibilitylevel" (no time limit)="0"
Severity : Error
Category : /System/Security/Usermanagement
Location : com.sap.security.core.persistence
Application : sap.com/com.sap.security.core.admin
Thread : SAPEngine_Application_Thread[impl:3]_22
Datasource : 1141856104605:C:\usr\sap\J2E\JC00\j2ee\cluster\server0\log\system\security.log
Message ID : 000D60DD8A4D00540000001C0000136000040E8333C9FD7C
Source Name : /System/Security/Usermanagement
Argument Objs : CORP_LDAP,***************************************************************************
com.sap.security.core.persistence.imp.PrincipalDatabagMaint Wed Mar 08 16:22:59 CST 2006
UniqueID: USER.CORP_LDAP.testuser
Type: USER
Home data source: CORP_LDAP
Private id part: testuser
"com.sap.security.core.usermanagement"|->"uniquename" (no time limit)="testuser"
"com.sap.security.core.usermanagement"|->"department" (no time limit)="CI&T"
"com.sap.security.core.usermanagement"|->"PRINCIPAL_CREATION_DATE" (no time limit)="0001141856579248"
"com.sap.security.core.usermanagement"|->"firstname" (no time limit)="user"
"com.sap.security.core.usermanagement"|->"lastname" (no time limit)="test"
"com.sap.security.core.usermanagement"|->"PRINCIPAL_TYPE_ATTRIBUTE" (no time limit)="USER"
"com.sap.security.core.usermanagement"|->"email" (no time limit)="[email protected]"
"com.sap.security.core.usermanagement"|->"company" (no time limit)=""
"com.sap.security.core.usermanagement"|->"accessibilitylevel" (no time limit)="0"
Arguments : CORP_LDAP,***************************************************************************
com.sap.security.core.persistence.imp.PrincipalDatabagMaint Wed Mar 08 16:22:59 CST 2006
UniqueID: USER.CORP_LDAP.testuser
Type: USER
Home data source: CORP_LDAP
Private id part: testuser
"com.sap.security.core.usermanagement"|->"uniquename" (no time limit)="testuser"
"com.sap.security.core.usermanagement"|->"department" (no time limit)="CI&T"
"com.sap.security.core.usermanagement"|->"PRINCIPAL_CREATION_DATE" (no time limit)="0001141856579248"
"com.sap.security.core.usermanagement"|->"firstname" (no time limit)="user"
"com.sap.security.core.usermanagement"|->"lastname" (no time limit)="test"
"com.sap.security.core.usermanagement"|->"PRINCIPAL_TYPE_ATTRIBUTE" (no time limit)="USER"
"com.sap.security.core.usermanagement"|->"email" (no time limit)="[email protected]"
"com.sap.security.core.usermanagement"|->"company" (no time limit)=""
"com.sap.security.core.usermanagement"|->"accessibilitylevel" (no time limit)="0"
Dsr Component : <masked id>_J2E_7234450
Dsr Transaction : 79521ee0aef011da9168000d60dd8a4d
Dsr User : Administrator
Indent : 0
Level : 0
Message Code :
Message Type : 1
Relatives : com.sap.security.core.persistence
Resource Bundlename :
Session : 200
Source : /System/Security/Usermanagement
ThreadObject : SAPEngine_Application_Thread[impl:3]_22
Transaction :
User : Administrator
Where can I find the initial NamingException?

Hi All,
Thanks for your replies and SORRY for my late response.
Now, what I actually want is that though my UME is connected to LDAP i want to the portal admin to be able to create users in the portal DB. I checked my UME configuration and it says
Microsoft ADS (Deep Hheirarchy) + Database
and the name of the configuration file is
dataSourceConfiguration_ads_deep_writeable_db.xml
Now I could not understand why I am not able to create users in the DB?
Does the portal has any restriction like at any given point of time only one of the user stores can be active? Doesnt the portal allow both the user stores to be active at a time?
regards,
PK

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.

JNDI naming exception: Naming exception trying to connect to:help !!!!!!!!!

Hi,
Iam getting this exception and i have no clue what is this exception means.....and how to resolve this Naming Exceptions problem.
what iam doing is.....Iam trying to deploy a war file from my unix system to a win2000 machine(amasdqyt095).
This is where and how my script(myscript.sh) looks like:
java -classpath /xyz/bea/wlserver6.1/lib/weblogic.jar weblogic.deploy -port 7001 -host amasdqyt095 -component myWebApp:myserver update weblogic myWebApp /export/home/applications/xyz.war
i have created this script at: /xyz/bea/wlserver6.1/config/scripts/myscript.sh
then i did chmod +x myscript.sh
and the i did:
./myscript.sh
and then iam getting this exception:
JNDI naming exception: Naming exception trying to connect to: t3://amasdqyt095:7001 as: system: weblogic
please help ????
-sangita

I had the same problem because the weblogic.jar's version in the server was diferent from my machine (SP2 and SP4). I stops when I updated the server to SP4.
But now I'm having the same problem in another server, and the versions are ok. If anybody knows something else, please let me know.
I'm using Weblogic 6.1
[]s
Leonardo

Getting Naming exception

Hello all,
I have written a small sample code in Oracle ADF and when I try to run the client I am getting following error. This seems to be related to context lookup. Please advice what wrong am I doing here.
try {
final Context context = getInitialContext();
PracticeSessionEJB practiceSessionEJB = (PracticeSessionEJB)context.lookup("PracticeSessionEJB");
String department_name = "IT Administration 12";
String location_id = "1500";
practiceSessionEJB.addDepartment( department_name, location_id );
long empid = 100;
System.out.println(practiceSessionEJB.getSalary( empid ));
} catch (NamingException nex) {
System.out.println("***********Naming exception has occured**********");
nex.printStackTrace();
catch (Exception ex) {
ex.printStackTrace();
It is catching Naming exception here.
The exact stack trace which I am getting is
javax.naming.CommunicationException: Connection refused: connect [Root exception is java.net.ConnectException: Connection refused: connect]
     at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:258)
     at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:50)
     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     at buslogic.PracticeSessionEJBClient.main(PracticeSessionEJBClient.java:11)
Please help.
Thanks
Ranjana

Please provide some inputs..The database I am using is getting connected properly cause I am able to see all tables and their data in Jdev. This is related to context lookup only.
Ranjana

EJB Naming Exception

Hi,
I'm deploying an application at the server with no errros, application that works with my Jdeveloper9 at my local PC.
I have made an EAR file for deploying, and looks like anothers I have from another applications.
I can see my application (from my WAR file) at the OC4J instance I'm deploying to. I can see the EJB module, and everything looks good.
But I get Naming Exception when triying to access to my EJB.
I think I should have all my XML conf files right and that's all, isn't it ?
Thanx in advance
Joe

First thanx for replying,
as I told, my new application has the same appearance than anothers webApp I've got, XML conf files, EAR, WAR, and ejb's JAR file,...
What I dont know if I have to do somthing I dont know to make it works. Something to make available my EJB name.
I think I shouldn't but maybe I'm wrong.

Injecting EntityManager into Interceptor class, naming exception

Hello , I try the code below :
class MyInterceptor {
@PersistenceContext(unitName="Model")
private EntityManager em;
@AroundInvoke
doIntercept....
but I got a naming exception , oc4j told me ....failed to inject the resource.....
Anyone know ,why ?
Anyway I resolved to make a special name into context :
class MySessioBean { // this bean use MyInterceptor
@PersistenceContext(name ="AdminPC",unitName="Model")
private EntityManager em;
and on MyInterceptor :
class MyInterceptor{
@AroundInvoke
public Object doIntercept(InvocationContext ic)throws BusinessException{
try {
InitialContext ctx = new InitialContext();
EntityManager temp = (EntityManager)ctx.lookup("java:comp/env/AdminPC");
em =temp;
} catch (NamingException e) {
// TODO
}

Hi,
Try verifying that all configuration details are set for OC4J.
You may refer the to following end-to-end quickstart enterprise application tutorial that contains the same @PersistenceContext injection on a stateless session ejb bean.
http://wiki.eclipse.org/EclipseLink/Examples/JPA/OC4J_Web_Tutorial
specifically
http://wiki.eclipse.org/EclipseLink/Examples/JPA/OC4J_Web_Tutorial#Perform_a_JPQL_query
and code
http://dev.eclipse.org/svnroot/rt/org.eclipse.persistence/trunk/examples/org.eclipse.persistence.example.jpa.server.oc4j.enterpriseEJB/ejbModule/org/eclipse/persistence/example/jpa/server/business/ApplicationService.java
If configurations match between both apps, then we can triage further.
thank you
/michael
www.eclipselink.org

EJB 3.0 stand alone client programe throws Naming Exception

Hi My application wont work , please take look my small stateless session using EJB 3.0
Business Inteface
==================================
package ejb30;
import javax.ejb.Remote;
@Remote
public interface Sless {
public String hello();
=====================
Bean Class
================
package ejb30;
import javax.ejb.Stateless;
@Stateless
public class SlessBean implements Sless {
public String hello() {
return "hello, world!\n";
================
Comiled the above 2 files and put into "s1.jar" file then deployed into SJS Application Server.
Deployed Sucuess fully
Created Client programs like below file
Client
========
package ejb30;
import javax.naming.InitialContext;
public class client
public static void main(String[] args)
     try
     InitialContext ctx = new InitialContext();
Sless sless = (Sless) ctx.lookup(Sless.class.getName());
     System.out.println(sless.hello());
     catch(Exception ex)
          ex.printStackTrace();
===============
when i am going the programe from console it throws the followin exception
===============
C:\Sun\AppServer\jdk\bin>java ejb30.client
javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645)
at javax.naming.InitialContext.getDefaultInitCtx InitialContext.java:247
at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:284)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at ejb30.client.main(client.java:13)
=============
please help me on this if any knows.........
Waiting for you great response
urs balasubramanyam

appserv-rt.jar already contains a jndi.properties file, and users don't need to worry about anything about jndi.properties file. For your sample app, it should work when you have appserv-rt.jar and javaee.jar in classpath.
If you still have failures, pls post your complete command you used to run client.

Naming Exception when deploying app

Hi, I hope someone can point me in the right direction.
Ths app was deploying and working fine until I added the user-manager to the orion-application.xml. The I use the data source in the main app so I know that is defined okay but I get the following error.
Deployment failed: Nested exception
Root Cause: deploy failed!: ; nested exception is:
oracle.oc4j.admin.internal.DeployerException: Error initializing userManager 'com.evermind.sql.DataSourceUserManager': NamingException: jdbc/FooDB not found
Resolution: . deploy failed!: ; nested exception is:
oracle.oc4j.admin.internal.DeployerException: Error initializing userManager 'com.evermind.sql.DataSourceUserManager': NamingException: jdbc/FooDB not found
Here is the user-manager tags
<user-manager class="com.evermind.sql.DataSourceUserManager">
<property name="dataSource" value="jdbc/FooDB" />
<property name="table" value="users" />
<property name="usernameField" value="user_name" />
<property name="passwordField" value="user_pass" />
<property name="defaultGroups" value="oracle_groups" />
<property name="staleness" value="0" />
</user-manager>
Thanks in advance

Now I'm getting the following error, but I've tried to 100 different ways of setting up the xml config files to get rid of the error and I can't
05/01/19 17:00:47 Error instantiating application at file:/C:/OraHome1/j2ee/Development/applications/Foo.ear: Error initializing
userManager 'com.evermind.sql.DataSourceUserManager': NamingException: Need to specify class name in environment or system property, or
as an applet parameter, or in an application resource file: java.naming.factory.initial
I've added the datasource (that works from within the application) to the "Development" instance using the Enterprise Manager 10g (9.0.4)
<data-source location="jdbc/FooBarDB" class="com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource" password="FooBar" max-connect-attempts="20" xa-location="jdbc/FooBarXADB" ejb-location="jdbc/FooBarEJBDB" wait-timeout="10" schema="database-schemas/mysql.xml" connection-driver="com.mysql.jdbc.Driver" username="FooBar" min-connections="5" max-connections="100" url="jdbc:mysql://172.16.120.6/FooBar" inactivity-timeout="200" name="jdbc/FooBarDB"><description>defined in app for security</description></data-source>
I've just run out of ideas, or got confused or both, any help great before I lose all my hair

Naming Exception in looking up JMS queue

I use my code to send message to queue (DeliveryService/inbound) configured in an weblogic app server in a Dev. Environment. But when I use the same code but ofcourse different URL, username, password etc. to send to another queue with same JNDI (DeliveryService/inbound) @ SQA environment setup I get the following error:
javax.naming.NameNotFoundException: Exception in lookup.: `DeliveryService/inbound' could not be found. [Root exception is weblogic.corba.cos.naming.NamingContextAnyPackage.NotFound: IDL:weblogic/corba/cos/naming/NamingContextAny/NotFound:1.0]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:63)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:235)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:171)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at gov.va.med.deliveryservice.dsd.delegates.jms.JMSDeliveryServiceDelegate.getOutboundQueue(JMSDeliveryServiceDelegate.java:229)
at gov.va.med.deliveryservice.dsd.delegates.jms.JMSDeliveryServiceDelegate.deliverMessage(JMSDeliveryServiceDelegate.java:147)
at gov.va.med.deliveryservice.dsd.delegates.BaseDeliveryServiceDelegate.sendMessagePTP(BaseDeliveryServiceDelegate.java:99)
at gov.va.med.deliveryservice.samples.PTPSend.dsTest1(PTPSend.java:202)
at gov.va.med.deliveryservice.samples.PTPSend.main(PTPSend.java:219)
Caused by: weblogic.corba.cos.naming.NamingContextAnyPackage.NotFound: IDL:weblogic/corba/cos/naming/NamingContextAny/NotFound:1.0
at weblogic.corba.cos.naming.NamingContextAnyPackage.NotFoundHelper.read(NotFoundHelper.java:72)
at weblogic.corba.cos.naming._NamingContextAnyStub.resolve_any(_NamingContextAnyStub.java:87)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:213)
... 7 more
Any help/suggestion would be appreciated.
-Ankur

Hi ,
i am also facing the same problem on Unix OS, even the Queue and Connectionfactories are deployed properly.
Any help/suggestion would be appreciated.
But in Windows env its working fine.
java.security.PrivilegedActionException: javax.naming.NameNotFoundException: Exception in lookup.: `
com/bt/jms/bridge/connectionFactory/CLA' could not be found. [Root exception is weblogic.corba.cos.n
aming.NamingContextAnyPackage.NotFound: IDL:weblogic/corba/cos/naming/NamingContextAny/NotFound:1.0]
at weblogic.security.subject.SubjectProxy.doAs(SubjectProxy.java:97)
at weblogic.security.subject.SubjectManager.runAs(SubjectManager.java:258)
at weblogic.security.Security.runAs(Security.java:67)
at com.concert.msc.common.util.WLUtil.runAs(WLUtil.java:43)
at com.bt.btgs.eai.testclient.JMSClient.processStart(JMSClient.java:49)
at com.bt.btgs.eai.testclient.JMSClient.main(JMSClient.java:40)
at com.bt.btgs.eai.testclient.PushFileOnebyOne.getInputFromUser(PushFileOnebyOne.java:85)
at com.bt.btgs.eai.testclient.StartTestClient.start(StartTestClient.java:49)
at com.bt.btgs.eai.testclient.StartTestClient.main(StartTestClient.java:23)
Caused by: javax.naming.NameNotFoundException: Exception in lookup.: `com/bt/jms/bridge/connectionFa
ctory/CLA' could not be found. [Root exception is weblogic.corba.cos.naming.NamingContextAnyPackage.
NotFound: IDL:weblogic/corba/cos/naming/NamingContextAny/NotFound:1.0]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:63)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:235)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:171)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.bt.btgs.eai.testclient.JMSClient.publishToQueue(JMSClient.java:90)
at com.bt.btgs.eai.testclient.JMSClient$Inner_PublishAction.run(JMSClient.java:74)
at weblogic.security.subject.SubjectProxy.doAs(SubjectProxy.java:89)
... 8 more
Caused by: weblogic.corba.cos.naming.NamingContextAnyPackage.NotFound: IDL:weblogic/corba/cos/naming
/NamingContextAny/NotFound:1.0
at weblogic.corba.cos.naming.NamingContextAnyPackage.NotFoundHelper.read(NotFoundHelper.java
:72)
at weblogic.corba.cos.naming._NamingContextAnyStub.resolve_any(_NamingContextAnyStub.java:87
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:213)
plz Would you reply me back quick.

Naming Exception while using the javax.jms.QueueConnectionFactory

Hi All,
I am quite new to JMS. I am trying to run the example QueueSender program shipped with weblogic5.1 . When i run the program i get the following error ...
Exception in thread "main" javax.naming.Name
NotFoundException:
'javax.jms.QueueConnectionFactory'; remaining name 'jms.QueueConnectionFactory'
at weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.j
ava:76)
at weblogic.jndi.toolkit.BasicWLContext_WLStub.lookup(BasicWLContext_WLS
tub.java:246)
at weblogic.jndi.toolkit.WLContextStub.lookup(WLContextStub.java:545)
at javax.naming.InitialContext.lookup(InitialContext.java:350)
at examples.jms.queue.QueueSend.init(QueueSend.java:37)
at examples.jms.queue.QueueSend.main(QueueSend.java:82)
I am desperate to get any guidance regarding the above mentioned exception
Thanx
Shanks

I don't use weblogic but the javax.naming.Name
NotFoundException suggests that the JNDI name cannot be found or resolved.
The name is specified in 2 locations, one in your java codes and the other during the deployment of the JMS application.
The error means the java program cannot find the JNDI name which means you did not specify the name correctly during the deployment.
Make sure both the names in java codes and deployment are right and matching. That should solve the problem.

Naming exception

Similar Messages

Maybe you are looking for