NameNotFound exceotion

i am just copying exmaple from i have done as given in book
but getting error while running client
i used same ejb-jar and weblogic-jar.xml which is given in the book
they have not use ejb-local-ref in xml file and use simple ejb name
'FinancialNeedCalculator' and i am getting same error NameNotFound 'FinancialNeedCalculator' my aplication is StandAlone
so help me

Hi Dear,
Basically NameNotFound Exception is comes due to deployment problem. There may be some problem in the DD so that your bean can not able to deploy.
Please see your DD carefully and check at the time of server up that your bean is depoyed successfully or not.
Regards

Similar Messages

Exception NameNotFound Exception

HiWhen i run the clint i get this exception javax.naming.NameNotFoundException:'JNDInameofclient';remaining name 'JNDInameofclient' at weblogic.rmi.extensions.AbstractRequest.sendreceive(Abstractrequest.java:76)I am using WEBLOGIC 5.1 on win98Please help me to figure this out

Are searching ejbhome?
If yes, check your jndi-name of deployed ejb. It should match exactly.
This is Namenotfound exception. It's just that name is matching within your
context.
sandip <[email protected]> wrote in message
news:3a8924e9$[email protected]..
HiWhen i run the clint i get this exceptionjavax.naming.NameNotFoundException:'JNDInameofclient';remaining name
'JNDInameofclient' at
weblogic.rmi.extensions.AbstractRequest.sendreceive(Abstractrequest.java:76)
I am using WEBLOGIC 5.1 on win98Please help me to figure this out

Bi exceotion error on WAD

hai all,
    here is the error i got while publishing a webtemplate on portal..
HELP ME PLEASE...
        while publishing the web template on the portal (WAD)...I get the bi exception error as described below..
     some times report is opening fine on portal ,when i make some selection from the dropdwn also it works ,,but at one point of time on the dropdown selection i get the
error. so i refresh, it works .again i navigate the report.. then i get the same error so again refresh ....
       when i do the same again and again the frequency of getting these error becomes more ....at one point of time the report itself is not opening on
portal..And everytime i get different error message as follows..
1.Message:
Error while generating HTML
2.Message: No connection possible to BI master system DB7CLNT800 3.Message: Error while executing function module: RSBOLAP_BICS_STATISTIC_INFO    4.message
Concurrent call. Connection currently used in another thread.
Message: 5.JCo exception thrown when connecting to system "DB7CLNT800"                      ...............................................................
The detailed error:
1. Exception in BI runtime
Initial cause
Message:
CPIC-CALL: CMSEND on convId: 24803423LOCATION    CPIC (TCP/IP) on local host with UnicodeERROR       connection to partner 'blade07.wipro.com:3300' brokenTIME        Mon Mar 03 10:05:28 2008RELEASE     700COMPONENT   NI (network interface)VERSION     38RC          -6MODULE      nixxi.cppLINE        3797DETAIL      NiIWriteSYSTEM CALL WSASendERRNO       10054ERRNO TEXT WSAECONNRESET: Connection reset by peerCOUNTER     30
Stack trace:
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: CPIC-CALL: CMSEND on convId: 24803423LOCATION    CPIC (TCP/IP) on local host with UnicodeERROR       connection to partner 'blade07.wipro.com:3300' brokenTIME        Mon Mar 03 10:05:28 2008RELEASE     700COMPONENT   NI (network interface)VERSION     38RC          -6MODULE      nixxi.cppLINE        3797DETAIL      NiIWriteSYSTEM CALL WSASendERRNO       10054ERRNO TEXT WSAECONNRESET: Connection reset by peerCOUNTER     30     at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:455)

Hi,
I recommend you to implement the following Note:
1045008 RRK_LIST_OPEN: CX_SY_REF_IS_INITIAL UNCAUGHT_EXCEPTION
It seems this as the typical case that the Abap-Java Communication
was not restarted perfectly. We have for this purpose
various notes in order to help here:
917950: SAP NetWeaver 2004s: Setting Up BEx Web (Overview)
888687: Java BEx Web: Analysis of Communication / logon problem's
937697: Usage of of BI SAP NetWeaver diagnostics & Support Desk
Tool (Dump Comm. Settings plus traces)
Further notes:
https://bis.wdf.sap.corp/twiki/bin/view/Sapinternal/BISuiteNotes
If the error still exists, please run the support desk tool as per note
937697, in the systeminfo.txt file you will see outlined the issues
Try to solve the issues using notes 917950, and 888687.
If useful please allocate some points.
Regards,
Suman Raju

Import/removal policy not working javax.naming.NameNotFound

Hi, i am experiencing some problems with my import/removal policy...more so the removal workstation policy not working.
When the policy schedule time initiates - the following shows up on the zenworks removal workstation removal screen:
30-Oct-2009 17:35:39 javax.naming.NameNotFoundException [Root exception is com.novell.service.jncp.NDSException: ccode = -601 (0xfffffda7)]
I keep seeing this on the screen and in the zenwsrem.log file.
I am running:
Zenworks 6.5 sp2
Netware 6.5 sp5
Can anyone help as i want to keep my tree clean from all the thousands of workstation objects that are generating and are mostly redundant.
Any help with this would be very helpful.
I do not know why this is happening...i have read a few tids, but the naming of my container does not use any special characters, just "Workstations".
regards
Dennis

Did any of the removals succeed?
i.e.
20-Sep-2009 23:00:31 Removed workstation:T82715.Workstations.BilletRd.WF
20-Sep-2009 23:00:32 Removed workstation:T87490.Workstations.BuxtonRd.WF
20-Sep-2009 23:00:32 Removed workstation:T87810.Workstations.BuxtonRd.WF
Are they still in eDir?
I'm assuming that edir is clean.. so the only other thing that would come to
mind is that the server/workstation policy doesn't have rights to delete
from the OU's your workstations are in?
I didn't go thru the log exactly line by line, but it looks like its always
bombing on workstations in
your BuxtonRd.WF and CecilRd.WF containers.
>>> On 11/5/2009 at 10:26 AM, in message
<[email protected]>,
dchitolie<[email protected]> wrote:
> In relation to the tid, i do not have any / in my containers?
> Here is my Zenwsrem.log:
>
> NameNotFoundException [Root exception
> iscom.novell.service.jncp.NDSException: ccode = -601 (0xfffffda7)]
> 27-Dec-2008 23:00:04 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 03-Jan-2009 23:00:03 Removed
workstation:T87306.Workstations.BuxtonRd.WF
> 03-Jan-2009 23:00:04 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 10-Jan-2009 23:00:50 Removed
workstation:T84740.Workstations.BilletRd.WF
> 10-Jan-2009 23:00:50 Removed
workstation:T87424.Workstations.BilletRd.WF
> 10-Jan-2009 23:00:50 Removed
workstation:T87324.Workstations.BuxtonRd.WF
> 10-Jan-2009 23:00:51 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 17-Jan-2009 23:00:16 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 31-Jan-2009 23:00:07 Removed
workstation:T85290.Workstations.BilletRd.WF
> 31-Jan-2009 23:00:08 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
>
> 14-Mar-2009 23:00:36 Removed
workstation:T87327.Workstations.BuxtonRd.WF
> 14-Mar-2009 23:00:37 Removed
workstation:T87484.Workstations.BuxtonRd.WF
> 14-Mar-2009 23:00:39 Removed workstation:T93380.Workstations.CecilRd.WF
> 14-Mar-2009 23:00:39 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 22-Mar-2009 23:00:04 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 28-Mar-2009 23:00:48 Removed workstation:T88849.Workstations.CecilRd.WF
> 28-Mar-2009 23:00:49 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 29-Mar-2009 23:00:27 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 02-Apr-2009 17:51:08 Could not authenticate as policy:
> 05-Apr-2009 23:00:31 Removed workstation:T8102T.Workstations.CecilRd.WF
> 05-Apr-2009 23:00:32 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 12-Apr-2009 23:00:23 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 17-Apr-2009 11:12:04 Could not authenticate as policy:
> 19-Apr-2009 23:00:23 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 26-Apr-2009 23:00:21 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 03-May-2009 22:59:55 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 10-May-2009 23:00:04 Removed workstation:T88842.Workstations.CecilRd.WF
> 10-May-2009 23:00:04 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 17-May-2009 23:00:22 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 24-May-2009 22:59:47 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 31-May-2009 23:00:15 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 07-Jun-2009 23:00:49 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 14-Jun-2009 23:00:04 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 21-Jun-2009 23:00:38 Removed workstation:T88834.Workstations.CecilRd.WF
> 21-Jun-2009 23:00:38 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 28-Jun-2009 08:09:11 No removal policy found.
> 28-Jun-2009 09:08:54 No removal policy found.
> 28-Jun-2009 10:08:37 No removal policy found.
> 28-Jun-2009 11:08:20 No removal policy found.
> 28-Jun-2009 12:08:03 No removal policy found.
> 28-Jun-2009 13:07:45 No removal policy found.
> 28-Jun-2009 14:07:28 No removal policy found.
> 28-Jun-2009 15:07:11 No removal policy found.
> 28-Jun-2009 16:06:55 No removal policy found.
> 28-Jun-2009 17:06:37 No removal policy found.
> 28-Jun-2009 18:06:20 No removal policy found.
> 28-Jun-2009 19:06:03 No removal policy found.
> 28-Jun-2009 20:05:46 No removal policy found.
> 28-Jun-2009 21:05:29 No removal policy found.
> 28-Jun-2009 22:05:12 No removal policy found.
> 28-Jun-2009 22:55:58 No removal policy found.
> 28-Jun-2009 23:04:55 No removal policy found.
> 29-Jun-2009 00:04:38 No removal policy found.
> 29-Jun-2009 01:04:21 No removal policy found.
> 29-Jun-2009 02:04:04 No removal policy found.
> 29-Jun-2009 03:03:47 No removal policy found.
> 29-Jun-2009 04:03:30 No removal policy found.
> 29-Jun-2009 05:03:13 No removal policy found.
> 29-Jun-2009 06:02:56 No removal policy found.
> 29-Jun-2009 07:02:38 No removal policy found.
> 29-Jun-2009 08:02:22 No removal policy found.
> 29-Jun-2009 09:02:05 No removal policy found.
> 05-Jul-2009 23:00:30 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 12-Jul-2009 23:00:44 Removed workstation:T82363.Workstations.CecilRd.WF
> 12-Jul-2009 23:00:44 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 19-Jul-2009 23:00:28 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 26-Jul-2009 23:00:19 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 02-Aug-2009 23:00:41 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 09-Aug-2009 23:00:22 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 16-Aug-2009 23:00:22 Removed
workstation:T85264.Workstations.BuxtonRd.WF
> 16-Aug-2009 23:00:22 Removed
workstation:T85266.Workstations.BuxtonRd.WF
> 16-Aug-2009 23:00:24 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 23-Aug-2009 23:00:20 Removed
workstation:T85261.Workstations.BuxtonRd.WF
> 23-Aug-2009 23:00:21 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 30-Aug-2009 23:00:02 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 06-Sep-2009 23:00:19 Removed workstation:T82722.Workstations.CecilRd.WF
> 06-Sep-2009 23:00:20 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 13-Sep-2009 23:00:13 Removed
workstation:T85336.Workstations.BilletRd.WF
> 13-Sep-2009 23:00:15 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 20-Sep-2009 23:00:31 Removed
workstation:T82715.Workstations.BilletRd.WF
> 20-Sep-2009 23:00:32 Removed
workstation:T87490.Workstations.BuxtonRd.WF
> 20-Sep-2009 23:00:32 Removed
workstation:T87810.Workstations.BuxtonRd.WF
> 20-Sep-2009 23:00:33 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 27-Sep-2009 23:00:03 Removed
workstation:T85179.Workstations.BilletRd.WF
> 27-Sep-2009 23:00:04 Removed
workstation:T87494.Workstations.BuxtonRd.WF
> 27-Sep-2009 23:00:05 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 04-Oct-2009 23:00:22 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 11-Oct-2009 23:00:03 javax.naming.NamingException [Root exception
> iscom.novell.service.jncp.NDSException: ccode = -637
> (0xfffffd83)];remaining name 'T87395'
> 11-Oct-2009 23:00:04 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 18-Oct-2009 23:00:35 Removed
workstation:T87395.Workstations.BuxtonRd.WF
> 18-Oct-2009 23:00:36 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 30-Oct-2009 17:30:31 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
> 30-Oct-2009 17:35:39 javax.naming.NameNotFoundException [Rootexception
> is com.novell.service.jncp.NDSException: ccode = -601(0xfffffda7)]
>
> Any ideas.....
> thanks
> regards
>
> Dennis--
dchitolie-------------------------------------------------------------------
-----dchitolie's Profile:
> http://forums.novell.com/member.php?userid=4304View this thread:
> http://forums.novell.com/showthread.php?t=391202

NameNotFound exception for java:comp/WorkContextMap

Hi,
we need to write a context propagation code. I tried the same using the example from - http://e-docs.bea.com/wls/docs90/programming/context.html#1058673. I have written the web service and it is getting the jndi for java:comp/WorkContextMap OK from it's own initial context. However, when I am writing a standalone java client to use WorkContextMap from the client side by getting a initial context to the weblogic 9.2 server by setting the initial context factory and the provider url, it does not work. I also tried by using only "WorkContextMap" in place of "java:comp/WorkContextMap". but that does not work either. How can this be fixed?
Just to test, I also tried to doa look up of "java:comp/UserTransaction" from the standalone client and it did not work either. I tried with different types of the jndi string - like with and without java:comp.
Here is the client code snippet -
 Hashtable env = new Hashtable() ;
 env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
 env.put(Context.PROVIDER_URL, "t3://172.20.8.211:7001");
 InitialContext ctx = new InitialContext(env) ;
 logger.info("in testEchoService...InitialContext=" + ctx) ;
 WorkContextMap map = (WorkContextMap) ctx.lookup("java:comp/WorkContextMap") ;
 logger.info("in testEchoService...map=" + map) ;
Appreciate your help,
Thanks.

Goutam Mukherjee <> writes:
The issue you are seeing has to do with client initialization - which is a big and hairy topic I won't bore you with. The simplest way to get this working is to use the J2EE appliction client which will ensure proper initialization - including the comp entries.
weblogic.j2eeclient.Main
You will need a generated client jar as well I believe.
andy
Hi,
we need to write a context propagation code. I tried the same using the example from - http://e-docs.bea.com/wls/docs90/programming/context.html#1058673. I have written the web service and it is getting the jndi for java:comp/WorkContextMap OK from it's own initial context. However, when I am writing a standalone java client to use WorkContextMap from the client side by getting a initial context to the weblogic 9.2 server by setting the initial context factory and the provider url, it does not work. I also tried by using only "WorkContextMap" in place of "java:comp/WorkContextMap". but that does not work either. How can this be fixed?
Just to test, I also tried to doa look up of "java:comp/UserTransaction" from the standalone client and it did not work either. I tried with different types of the jndi string - like with and without java:comp.
Here is the client code snippet -
 Hashtable env = new Hashtable() ;
 env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
 env.put(Context.PROVIDER_URL, "t3://172.20.8.211:7001");
 InitialContext ctx = new InitialContext(env) ;
 logger.info("in testEchoService...InitialContext=" + ctx) ;
 WorkContextMap map = (WorkContextMap) ctx.lookup("java:comp/WorkContextMap") ;
 logger.info("in testEchoService...map=" + map) ;
Appreciate your help,
Thanks.

Uncaught Exceotion

i am using whatsapp in my blackberry curve 8520.when i keep whatsapp openened for morethan 5 minutes it force closes showing "Uncaught Exception:4<=4".How to solve this problem.??

I'd suggest to uninstall whatsapp, reboot your device and reinstall. You need to secure your SD card also with copying the data to your computer. WhatsApp consumes large memory usage which makes error especially with BB OS 7 and earlier.
• Click Likes to appreciate those who helps you
• If your issue solved, mark the best post in your thread as Solution

NameNotFound exception

I am using weblogic 4.5. My application deployment descriptor shows like this:
SessionDescriptor
beanHomeName com.mortgagefamily.web.projects.loanstatus.businessservices.RequestDoradoLoanStatusHome
My client code is like this:
Context ctx = getInitialContext();
RequestDoradoLoanStatusHome home = (RequestDoradoLoanStatusHome)
ctx.lookup("com.mortgagefamily.web.projects.loanstatus.businessservices.RequestDoradoLoanStatusHome");
But when I try to run my client to find the bean with the given JNDI name I get
the following error.
dammala(ldevapp01)> java DoradoLoanStatusClient
Started client application
got context
javax.naming.NameNotFoundException: 'com.mortgagefamily.web.projects.loanstatus.
businessservices.RequestDoradoLoanStatusHome'; Remaining Name: 'loanstatus.busin
essservices.RequestDoradoLoanStatusHome'
at java.lang.Throwable.fillInStackTrace(Native Method)
at weblogic.rmi.extensions.BasicRequest.sendReceive(BasicRequest.java:44
at weblogic.jndi.WLContext_WLStub.lookup(WLContext_WLStub.java:192)
at weblogic.jndi.toolkit.WLContextStub.lookup(Compiled Code)
at javax.naming.InitialContext.lookup(InitialContext.java:280)
at DoradoLoanStatusClient.main(Compiled Code)

Goutam Mukherjee <> writes:
The issue you are seeing has to do with client initialization - which is a big and hairy topic I won't bore you with. The simplest way to get this working is to use the J2EE appliction client which will ensure proper initialization - including the comp entries.
weblogic.j2eeclient.Main
You will need a generated client jar as well I believe.
andy
Hi,
we need to write a context propagation code. I tried the same using the example from - http://e-docs.bea.com/wls/docs90/programming/context.html#1058673. I have written the web service and it is getting the jndi for java:comp/WorkContextMap OK from it's own initial context. However, when I am writing a standalone java client to use WorkContextMap from the client side by getting a initial context to the weblogic 9.2 server by setting the initial context factory and the provider url, it does not work. I also tried by using only "WorkContextMap" in place of "java:comp/WorkContextMap". but that does not work either. How can this be fixed?
Just to test, I also tried to doa look up of "java:comp/UserTransaction" from the standalone client and it did not work either. I tried with different types of the jndi string - like with and without java:comp.
Here is the client code snippet -
 Hashtable env = new Hashtable() ;
 env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
 env.put(Context.PROVIDER_URL, "t3://172.20.8.211:7001");
 InitialContext ctx = new InitialContext(env) ;
 logger.info("in testEchoService...InitialContext=" + ctx) ;
 WorkContextMap map = (WorkContextMap) ctx.lookup("java:comp/WorkContextMap") ;
 logger.info("in testEchoService...map=" + map) ;
Appreciate your help,
Thanks.

Help please - JNDI NameNotFound exception

I am running Sun's Java Application Server 8.1 PE
 
When I deploy my application, it gives me a NameNotFoundException: No object bound to name java:comp/env/jdbc/test:
 
[#|2005-04-06T12:58:26.300-0500|SEVERE|sun-appserver-pe8.0.0_01|org.springframework.web.context.ContextLoader|_ThreadID=13;|Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'targetDataSource' defined in ServletContext resource [WEB-INF/applicationContext-jdbc.xml]: Initialization of bean failed; nested exception is javax.naming.NameNotFoundException: No object bound to name java:comp/env/jdbc/test
javax.naming.NameNotFoundException: No object bound to name java:comp/env/jdbc/test
at com.sun.enterprise.naming.NamingManagerImpl.lookup(NamingManagerImpl.java:665)
at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:108)
 
I verified (using the Sun App Server Admin console) that the connection pool I have set up can be pinged, and I verified through the Sun Java Studio Creator application that the JNDI name associated with the JDBC connection is indeed jdbc/test.
 
Can anyone see what it is I may be doing wrong? If I add a JDBC Resource with a JNDI name of jdbc/test, then shouldn't the app server be able to find it at java:comp/env/jdbc/test?
 
Thanks!

Probably, you need to configure the <resource-ref> tag in your deployment descriptors. :-)

NameNotFound exception by using javax.jts.UserTransaction

Hello:
          I am working on using jts for the transaction access to a Oracle 7.3
          database.
          In the property file of my application, I used
          weblogic.jdbc.connectionPool.oraclePool=\
          url=jdbc:oracle:thin:@10.10.0.201:1521:orcl,\
          driver=oracle.jdbc.driver.OracleDriver,\
          loginDelaySecs=1,\
          initialCapacity=4,\
          maxCapacity=10,\
          capacityIncrement=2,\
          allowShrinking=true,\
          shrinkPeriodMins=15,\
          refreshMinutes=10,\
          testTable=dual,\
          props=user=joe;password=tiger
          weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=guest
          weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.jtsPool=oraclePool
          In my servlet, I used
          Context ctx = null;
          Hashtable env = new Hashtable();
          env.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
          env.put(Context.PROVIDER_URL, "t3://127.0.0.1:8080");
          env.put(Context.SECURITY_PRINCIPAL, "system");
          env.put(Context.SECURITY_CREDENTIALS, "Administrator");
          ctx = new InitialContext(env);
          UserTransaction tx = (UserTransaction)
          ctx.lookup("javax.jts.UserTransaction");
          When I access the servlet, the following exception were thrown.
          javax.naming.NameNotFoundException: 'javax.jts.UserTransaction';
          remaining name 'jts.UserTransaction' at
          weblogic.jndi.toolkit.BasicWLContext.resolveName(BasicWLContext.java,
          Compiled Code)at
          weblogic.jndi.toolkit.BasicWLContext.lookup(BasicWLContext.java:133)at
          weblogic.jndi.toolkit.BasicWLContext.lookup(BasicWLContext.java:574)at
          javax.naming.InitialContext.lookup(InitialContext.java:349) at
          jtsdemo.SelectAccessor.accessDatabase(SelectAccessor.java:20)at
          jtsdemo.SelectJTS.doPost(SelectJTS.java:29) at
          jtsdemo.SelectJTS.doGet(SelectJTS.java:12)
          When I open the weblogic console, in directory Naming, I could not find
          javax.jts.UserTransaction entry. However there is weblogic.jdbc.jts
          entry which is generated by the following line, which I put into the
          properties file.
          weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.jtsPool=oraclePool
          Thank you for any thoughts.
          MSU
          [att1.html]


Hello:
          Thank Kumar for a reply.
          I checked the document and able to follow it and use
          javax.sql.DataSource to get a jts connection and select from database.
          In the properties file of the weblogic application server,
          weblogic.jdbc.TXDataSource.jtsOraclePool=oraclePool
          Some questions follow.
          In this way, I could not get a handle to UserTransaction. I am
          wondering in case of database insertion, does this connection
          automatically commit for each execUpdate(), if I do not call
          conn.setAutoCommit(false)?
          If a programmer has to manage the transaction on the Connection,
          what is the advantage to use jts connection pool? Does this performed
          faster or internally it behaves the same?
          Look forward to any insight.
          MSU
          Kumar Allamraju wrote:
          > Michelle,
          >
          > see the correct usage here:
          > http://www.weblogic.com/docs50/classdocs/DataSource.html#998209
          >
          > -Kumar
          >
          > Michelle Sue wrote:
          >
          >> Hello, Kumar:
          >> Thank you for the information given.
          >> Now what I did is
          >> Properties p = new Properties();
          >> p.put(Context.INITIAL_CONTEXT_FACTORY,
          >> "weblogic.jndi.WLInitialContextFactory");
          >> Context ctx = new InitialContext(p);
          >> UserTransaction tx = (UserTransaction)
          >> ctx.lookup("javax.transaction.UserTransaction");
          >> try {
          >> tx.begin();
          >> Driver myDriver = (Driver)
          >> Class.forName("weblogic.jdbc.jts.Driver").newInstance();
          >> Properties props = new Properties();
          >> props.put("connectionPoolID", "oraclePool");
          >> conn = myDriver.connect("jdbc:weblogic:jts", props);
          >> Statement stmt = conn.createStatement();
          >>
          >> The new error is
          >> JTS JDBC Driver being called without a pool name
          >> at
          >> weblogic.jdbcbase.jts.Connection.openConnectionIfNecessary(Connection.java:569)
          >>
          >> at weblogic.jdbcbase.jts.Connection.createStatement
          >>
          >> I guess something wrong with the props.put("connectionPoolID",
          >> "oraclePool");
          >> In the properties file, it seems to me that the only line related to
          >> jts is
          >>
          >> weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.oraclePool=oraclePool
          >> oraclePool was also defined in this properties file as a
          >> weblogic.jdbc.connectionPool
          >>
          >> MSU
          >>
          >>
          >> Kumar Allamraju wrote:
          >>
          >> > Hi Michelle,
          >> >
          >> > The use of javax.jts.UserTransaction is deprecated in EJB 1.1
          >> > The correct package name is javax.transaction.UserTransaction.
          >> >
          >> > Remeber you shouldn't make any t3 connections from the server side
          >> > class.
          >> >
          >> > you can directly say context c = new InitialContext( )
          >> > Pls refer one of our examples directory.
          >> > for e.g weblogic/examples/ejb/basic/beanManaged/Servlet.java
          >> >
          >> > Hope this helps
          >> > -Kumar
          >> >
          >> >
          >> >
          >> > Michelle Sue wrote:
          >> >
          >> >> Hello:
          >> >> I am working on using jts for the transaction access to a
          >> >> Oracle 7.3 database.
          >> >> In the property file of my application, I used
          >> >>
          >> >> weblogic.jdbc.connectionPool.oraclePool=\
          >> >> url=jdbc:oracle:thin:@10.10.0.201:1521:orcl,\
          >> >> driver=oracle.jdbc.driver.OracleDriver,\
          >> >> loginDelaySecs=1,\
          >> >> initialCapacity=4,\
          >> >> maxCapacity=10,\
          >> >> capacityIncrement=2,\
          >> >> allowShrinking=true,\
          >> >> shrinkPeriodMins=15,\
          >> >> refreshMinutes=10,\
          >> >> testTable=dual,\
          >> >> props=user=joe;password=tiger
          >> >>
          >> >> eblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=guest
          >> >>
          >> >> weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.jtsPool=oraclePool
          >> >>
          >> >>
          >> >> In my servlet, I used
          >> >> Context ctx = null;
          >> >> Hashtable env = new Hashtable();
          >> >>
          >> >> env.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
          >> >>
          >> >> env.put(Context.PROVIDER_URL, "t3://127.0.0.1:8080");
          >> >> env.put(Context.SECURITY_PRINCIPAL, "system");
          >> >> env.put(Context.SECURITY_CREDENTIALS, "Administrator");
          >> >> ctx = new InitialContext(env);
          >> >> UserTransaction tx = (UserTransaction)
          >> >> ctx.lookup("javax.jts.UserTransaction");
          >> >>
          >> >> When I access the servlet, the following exception were thrown.
          >> >>
          >> >> javax.naming.NameNotFoundException: 'javax.jts.UserTransaction';
          >> >> remaining name 'jts.UserTransaction' at
          >> >> weblogic.jndi.toolkit.BasicWLContext.resolveName(BasicWLContext.java,
          >> >> Compiled Code)at
          >> >> weblogic.jndi.toolkit.BasicWLContext.lookup(BasicWLContext.java:133)at
          >> >> weblogic.jndi.toolkit.BasicWLContext.lookup(BasicWLContext.java:574)at
          >> >> javax.naming.InitialContext.lookup(InitialContext.java:349) at
          >> >> jtsdemo.SelectAccessor.accessDatabase(SelectAccessor.java:20)at
          >> >> jtsdemo.SelectJTS.doPost(SelectJTS.java:29) at
          >> >> jtsdemo.SelectJTS.doGet(SelectJTS.java:12)
          >> >>
          >> >> When I open the weblogic console, in directory Naming, I could
          >> >> not find javax.jts.UserTransaction entry. However there is
          >> >> weblogic.jdbc.jts entry which is generated by the following line,
          >> >> which I put into the properties file.
          >> >> weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.jtsPool=oraclePool
          >> >>
          >> >> Thank you for any thoughts.
          >> >>
          >> >> MSU
          >> >>
          >> >>
          >> >
          [att1.html]

How to use JNDI lookup from a JSP

Hello,
I know I should not be doing this (writing the lookup code in a JSP) but have to do it for some reasons.
I am using this code in my JSP:
try
 Context ctx = new InitialContext();
 dataSource = (DataSource)ctx.lookup("jdbc/mybillingora");
 conn = dataSource.getConnection();
 statement = conn.createStatement();
catch(Exception excep)
Is this code enough for a JNDI look up?? When I use this code, I get an exception:
"javax.naming.NameNotFound exception:jdbc/mybillingora"
Do I need to do something else??
Why do we use :
Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY,
"<some_context_factory>");
env.put(Context.PROVIDER_URL, PROVIDER_URL);
env.put(Context.SECURITY_PRINCIPAL, JNDI_USER);
env.put(Context.SECURITY_CREDENTIALS, JNDI_PWD);
InitialContext = new InitialDirContext(env);
where JNDI_USER is the userid If ACL is configured at the JNDI server
where JNDI_PWD is the password If ACL is configured at the JNDI server
Context.INITIAL_CONTEXT_FACTORY is the initial Context factory and depends on ur JNDI service provider.
PROVIDER_URL is the url of the JNDI server containing protocol/ip/port
do i need to use this??
would appreciate your help on this....
Thanks

If Tomcat is your servlet/JSP engine, they have a nice bit about how to do it:
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html
MOD

Re: junit test for entity beans ... ejb 3.0

I'm confused. I'm trying to test my entity bean.
I have:
- an entity bean
- a stateless session bean for accessing the entity bean (facade)
- an interface for accessing the the stateless bean
And I'm trying to write a JUnit test class to test this bean. However, I am uncertain as to how to test this (I'm new to EJB 3.0, JBoss and Eclipse).
What would the JUnit test look like? I'm confused as to whether or not I should be injecting the interface/bean/what???
I've tried several variations. I either get "NameNotFound" - not bound exceptions or Null pointer exceptions.
What would the @EJB syntax look like or how would I do it through the context?
For Example:
@EJB private TestFacade myTest; //interface to stateless bean ?
OR
InitialContext ctx = new InitialContext();
TestResultFacadeBean myTest = (TestResultFacadeBean) ctx.lookup("localTest");
I'm confused at to which method I should be using and what object I should be accessing. If I could get either one to work, I'd be happy. :)
How do I ensure my bean is deployed to the container? What do I need to do?
If anyone has a simple example or explanation as to which method I should use and how to use it, I'd be very grateful.
Thanks very much,
LisaD

OK, you need to have several layers of testing.
Layer 0. Test the entity beans are deployable (more on this later). Basically, you need to know that all your annotations work. Things to watch out for are multiple @Id fields in one class or @EmbeddedID or @IdClass in conjuction with @ManyToOne, @ManyToMany, @OneToMany, @OneToOne and fun with @JoinTable, @JoinColumn and @JoinColumns. Once you know how these are supposed to work with the spec, it's not too bad to write it correctly each time. But there are some gotchas that will break things later on.
Layer 1. Do the functions in the classes that don't depend on annotations work as expected. Typically, this is just going to be the getters and setters in your entity classes. Of course JUnit best practice says we don't bother testing functions that look like:
public T getX() {
return this.x;
or
public void setX(T x) {
this.x = x;
as there is nothing that can go wrong with them. So in that case, your level 1 tests will just be initial values specified from constructors and verifying that the non-get/set pairs work, and that the getters you have tagged @Transient work (because you've likely put some logic in them)
Layer 2. Test the session bean methods that don't require injection to work.
Layer 3. Test the session bean methods that require injection (Mock Objects). Simulate the injection for yourself, injecting Mock Objects for the entity manager. Then you can confirm that the correct methods are being called in the correct sequences, etc.
[Note this may require some skill in designing the mock. I'm working on developing my own entitymanager mock, and if it looks usefull I'll release it to the world.
Layer 4. Test the session bean methods that require injection (Real entity manager) (See Layer 0)
For this you will need an out of container persistence implementation. Currently Hibernate and Glassfish provide beta versions. You will need a different persistence.xml file that lists all the entities. You will have to use reflection to inject the entity manager(s) that you create from an entity manager factory unless you provide a constructor that takes an EntityManager as a parameter. You may need to use reflection to call any @PostConstruct method if you made it private.
Layer 5. Navigate the relationships in the objects returned from Layer 4 using a database that has been loaded with test data.
I am currently using Layers 0, 1, 2 & 4 to test my session beans and entity beans.

How to consume Stateless session bean (ejb3.0)

Hi,
Using SAP NWDS, and Java EE 5 engine, I created an EJB 3.0 project (using the wizard) that includes my bean, local and remote classes with the correponding annotation.
Now I have headhackes trying to consume (at least to call a methode from my bean).
Here is the framework:
Ejb project includes: myClassBean, myClassLocal (interface), myClassRemote(interface).
In another java project, I try to use my bean method like this:
InitialContext ctx = new InitialContext();
myClassRemote classRemote= (myClassRemote) ctx.lookup("sap.com/<name of the ear>/myClassBean");
ResultSet rs = classRemote.getMyMethod("param");
Thus this implementation do not work. The nasted exception is NameNotFound exception during the look up.
I readt a lot of document on the sdn and sap portal but all describe the creation of ejb and not really their consumption.
Can you help?
Thanks in advance,
Marc

Hi Marc,
Hope <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/605ff5f2-e589-2910-3ead-e558376e6f3d">this</a> answers your questions!
Cheers,
Vladimir

Getting error while calling ejb business methods from servlet

Hi
Iam getting error when i try to call a ejb method from servlet.Error is
"com.netscape.server.eb.UncheckedException: unchecked exception nested exception is:java.lang.NullPointerException".
I build the application and deployed it successfully.Iam using IAS 6.O with windows NT 4.0.
This is just a method which takes values from database and return as an array of bean to servlet.
Any help on this.Thanks Shank

Hi
I was using the session bean.Your suggestion helped me a lot.Perfect.
I debug my program and found that from ejbCreate()exception is getting.
I was getting the datasource object thro ejb create() initialisation.
Somehow the look up jndi which i mentioned was not interpretting from ejb-jar.xml ias-ejb-jar.xml and datasource ref .Due to this iam getting jndi Namenotfound exception which in turns to null pointer as datasource is getting null.
when i hardcoded in the ejb the the jndi name for datasource it is working fine.Bit worried all the existing ejbs working with the xml referenced datasource and jndi,but when i added a new ejb with same properties it is failing to get the jndi name.
Piece of code from ias-ejb-jar.xml
<resource-ref>
 <res-ref-name>myDataSource</res-ref-name>
 <jndi-name>jdbc/nb/myData</jndi-name>
</resource-ref>
Piece of code from ejb-jar.xml
<resource-ref>
 <res-ref-name>myDataSource</res-ref-name>
 <res-type>javax.sql.DataSource</res-type>
 <res-auth>Container</res-auth>
</resource-ref>
Thanks a lot meka

Invocation Target Exception while Migrating application to weblogic 10.3

Hi All,
We are currently migrating our application from weblogic 8.1 to weblogic 10.3.
The deployment in wls 10.3 is successful, but while performing some operations(User Registration.. etc)
we are getting SQLIntegrityConstraintViolationException.
=================================================================================================
2010-10-27 17:03:50,968 DEBUG com.sns.ana.services.ConnPoolService - Param 0: java.util.Hashtable
2010-10-27 17:03:50,968 DEBUG com.sns.ana.services.ConnPoolService - Param 1: java.lang.String
2010-10-27 17:03:50,968 DEBUG com.sns.ana.services.ConnPoolService - Param 2: weblogic.jdbc.wrapper.PoolConnection_oracle_jdbc_driver_T4CConnection
2010-10-27 17:03:50,968 DEBUG com.sns.ana.dbsource.AuthorisationDBSource - [addRolesToDB] rows: 0, sql: delete from tana_role where userid = 'odcwls104'
2010-10-27 17:03:51,030 ERROR com.sns.ana.services.ConnPoolService - [getRestrictedService] InvocationTargetException:
java.sql.SQLIntegrityConstraintViolationException: ORA-02291: integrity constraint (ESIUSER.FK_TANAROLE_UID) violated - parent key not found
     at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:85)
     at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:112)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:173)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:413)
     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1030)
     at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:194)
     at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:947)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1222)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3381)
     at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3462)
     at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1349)
     at weblogic.jdbc.wrapper.PreparedStatement.executeUpdate(PreparedStatement.java:159)
     at com.sns.ana.dbsource.AuthorisationDBSource.addRolesToDB(AuthorisationDBSource.java:684)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.sns.ana.services.ConnPoolService.getRestrictedDataService(ConnPoolService.java:39)
     at com.sns.ana.services.DataServiceProvider.getRestrictedDataService(DataServiceProvider.java:45)
     at com.sns.ana.user.SNSUser.updateRoles(SNSUser.java:303)
     at com.sns.ana.utils.RoleUtility.processNewRequest(RoleUtility.java:114)
     at com.sns.ana.ui.servlet.ManageUserServlet.doPost(ManageUserServlet.java:395)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at com.sns.ana.ui.servlet.AuthorisationBaseServlet.service(AuthorisationBaseServlet.java:86)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:502)
     at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:432)
     at com.sns.ana.ui.servlet.ANAADMMainServlet.doPost(ANAADMMainServlet.java:741)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at com.sns.ana.ui.servlet.AuthorisationBaseServlet.service(AuthorisationBaseServlet.java:86)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3495)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
=================================================================================================
Upon weblogic server shut down below NameNotFoundException is thrown.
=================================================================================================
BaseException: ClassName=null,MethodName=null,MajorCode=-1,MajorMsg=Message Not Available,MinorCode=null,ExceptionObjMsg=[DBConnection][getConnec
tion]Unable to init database connection due to unresolved DataSource Name com.fortressit.ejb.PortableContextException: javax.naming.NameNotFoundE
xception: While trying to look up comp/env/jdbc/ap2esiDSLocal in /app/webapp/webadminesi/26700672. [Root exception is java.rmi.ConnectIOException
: Server is being shut down]; remaining name 'comp/env/jdbc/ap2esiDSLocal'
While trying to look up comp/env/jdbc/ap2esiDSLocal in /app/webapp/webadminesi/26700672.
at com.sns.base.util.DBConnection.getConnection(Unknown Source)
at com.sns.ana.services.ConnPoolService.getParamsWithDBConnection(ConnPoolService.java:93)
at com.sns.ana.services.ConnPoolService.getRestrictedDataService(ConnPoolService.java:35)
at com.sns.ana.services.DataServiceProvider.getRestrictedDataService(DataServiceProvider.java:45)
at com.sns.ana.ui.servlet.listener.CleanupAppSessionListener.sessionDestroyed(CleanupAppSessionListener.java:43)
at weblogic.servlet.internal.EventsManager.notifySessionLifetimeEvent(EventsManager.java:265)
at weblogic.servlet.internal.session.SessionData.remove(SessionData.java:873)
at weblogic.servlet.internal.session.MemorySessionContext.invalidateSession(MemorySessionContext.java:69)
at weblogic.servlet.internal.session.MemorySessionContext$SessionCleanupAction.run(MemorySessionContext.java:114)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.session.MemorySessionContext.destroy(MemorySessionContext.java:90)
at weblogic.servlet.internal.WebAppServletContext.destroy(WebAppServletContext.java:3062)
at weblogic.servlet.internal.ServletContextManager.destroyContext(ServletContextManager.java:240)
at weblogic.servlet.internal.HttpServer.unloadWebApp(HttpServer.java:457)
at weblogic.servlet.internal.WebAppModule.destroyContexts(WebAppModule.java:1398)
at weblogic.servlet.internal.WebAppModule.deactivate(WebAppModule.java:492)
at weblogic.application.internal.flow.ModuleStateDriver$2.previous(ModuleStateDriver.java:188)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:148)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:138)
at weblogic.application.internal.flow.ModuleStateDriver.deactivate(ModuleStateDriver.java:71)
at weblogic.application.internal.flow.ScopedModuleDriver.deactivate(ScopedModuleDriver.java:206)
at weblogic.application.internal.flow.ModuleListenerInvoker.deactivate(ModuleListenerInvoker.java:124)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.previous(DeploymentCallbackFlow.java:417)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:148)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:138)
at weblogic.application.internal.flow.DeploymentCallbackFlow.deactivate(DeploymentCallbackFlow.java:91)
at weblogic.application.internal.flow.DeploymentCallbackFlow.deactivate(DeploymentCallbackFlow.java:83)
at weblogic.application.internal.BaseDeployment$2.previous(BaseDeployment.java:641)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:148)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:138)
at weblogic.application.internal.BaseDeployment.deactivate(BaseDeployment.java:234)
at weblogic.application.internal.EarDeployment.deactivate(EarDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.deactivate(DeploymentStateChecker.java:199)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.deactivate(AppContainerInvoker.java:98)
at weblogic.deploy.internal.targetserver.BasicDeployment.deactivate(BasicDeployment.java:263)
at weblogic.deploy.internal.targetserver.BasicDeployment.deactivateFromServerLifecycle(BasicDeployment.java:458)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doDeactivate(DeploymentAdapter.java:73)
at weblogic.management.deploy.internal.DeploymentAdapter.deactivate(DeploymentAdapter.java:211)
at weblogic.management.deploy.internal.AppTransition$6.transitionApp(AppTransition.java:66)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.deactivate(ConfiguredDeployments.java:198)
at weblogic.management.deploy.internal.ConfiguredDeployments.undeploy(ConfiguredDeployments.java:191)
at weblogic.management.deploy.internal.DeploymentServerService.shutdownApps(DeploymentServerService.java:188)
at weblogic.management.deploy.internal.DeploymentServerService.shutdownHelper(DeploymentServerService.java:120)
at weblogic.application.ApplicationShutdownService.halt(ApplicationShutdownService.java:142)
at weblogic.t3.srvr.ServerServicesManager.haltInternal(ServerServicesManager.java:502)
at weblogic.t3.srvr.ServerServicesManager.halt(ServerServicesManager.java:334)
at weblogic.t3.srvr.T3Srvr.shutdown(T3Srvr.java:948)
at weblogic.t3.srvr.T3Srvr.forceShutdown(T3Srvr.java:854)
at weblogic.t3.srvr.T3Srvr$2.run(T3Srvr.java:867)
##### proxy instance has been created !!!
=================================================================================================
From the above exceptions i can infer that, the database connection failed due to unresolved datasource name.
However we have configured all the Datasources, application seems to be having problem in wls 10.3.
Waiting in anticipation for replies.
Regards
Avinash

Hi Avinash,
It seems that the application is not able to get the DataSource JNDI name which you have given that the reason you are getting the NameNotFoundException exception.
Try to give the same JNDI name in the datasource which your application is trying to lookup, once you have created the datasource make sure you test the connection using Test Connection option by which you can be sure that if the test connection can get a connection from the DB everything is fine also check the JNDI tree if you can see the datasource JNDI name in there.
Hope this helps you.
Regards,
Ravish Mody

Weblogic 11g Error

Hello ,
We are having an Spring based application which was running in weblogic 8.1 , we are migrating to weblogic 11g .
I created all the configurations in 11g as it was in 8.1 . But I am getting a set of errors as shown below while deploying the application.
Error while deploying
• Substituted for missing class org.springframework.beans.FatalBeanException - Can't resolve reference to bean 'prixcarAdapter' while setting property 'messageHandler' on bean 'ftpAdapter';
• nested exception is: org.springframework.beans.FatalBeanException: Can't resolve reference to bean 'prixcarGateway' while setting property 'gateway' on bean 'prixcarAdapter';
• nested exception is: org.springframework.beans.FatalBeanException: Can't resolve reference to bean 'jmsPrixcarConnectionFactory' while setting property 'connectionFactory' on bean 'prixcarGateway';
• nested exception is: org.springframework.beans.FatalBeanException: afterPropertiesSet() on bean with name 'jmsPrixcarConnectionFactory' threw exception;
• nested exception is: javax.naming.NameNotFoundException: Unable to resolve 'PrixcarConnectionFactory'. Resolved ''; remaining name 'PrixcarConnectionFactory'
Log file error
The Message-Driven EJB: PRIXCAR_IMPORT_GATEWAY_QUEUE is unable to connect to the JMS destination: jms.PrixcarDamageQueue. The Error was: javax.naming.NameNotFoundException: Unable to resolve 'jms.PrixcarDamageQueue'. Resolved 'jms'; remaining name 'PrixcarDamageQueue' 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:393) at javax.naming.InitialContext.lookup(InitialContext.java:392) at weblogic.jms.common.CDS$2.run(CDS.java:222) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:216) at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1295) at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1092) at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1324) at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:480) at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227) at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:415) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:75) at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:67) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409) at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844) at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253) at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java
In the spring xml I have configured the bean as shown below
<bean id="jmsPrixcarQueue" class="org.springframework.jndi.JndiObjectFactoryBean">
<property name="jndiName"><value>jms.PrixcarDamageQueue</value></property>
<property name="inContainer"><value>false</value></property>
</bean>
<bean id="jmsPrixcarConnectionFactory" class="org.springframework.jndi.JndiObjectFactoryBean">
<property name="jndiName"><value>jms.PrixcarConnectionFactory</value></property>
<property name="inContainer"><value>false</value></property>
</bean>
And in weblogic-ejb-jar.xml it is as shown below
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 8.1.0 EJB//EN"
"http://www.oracle.com/technology/weblogic/weblogic-ejb-jar/1.1/weblogic-ejb-jar.xsd">
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>PRIXCAR_IMPORT_GATEWAY_QUEUE</ejb-name>
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>1</max-beans-in-free-pool>
<initial-beans-in-free-pool>1</initial-beans-in-free-pool>
</pool>
<destination-jndi-name>jms.PrixcarDamageQueue</destination-jndi-name>
</message-driven-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
I configured jms modules in weblogic 11g server console with the jndi names
jms.PrixcarDamageQueue
jms.PrixcarConnectionFactory
Please let us know the reason for this error also the doctype for 11g in weblogic-ejb-jar.xml above.
Edited by: user13295341 on Jun 15, 2010 5:21 AM

Jay and Maxence , I tried what you guys said by removing the jms. and using only PrixcarDamageQueue and PrixcarConnectionFactory but still I am getting an error like Namenotfound as shown below,
The Message-Driven EJB: PRIXCAR_IMPORT_GATEWAY_QUEUE is unable to connect to the JMS destination: PrixcarDamageQueue. The Error was: javax.naming.NameNotFoundException: Unable to resolve 'PrixcarDamageQueue'. Resolved ''; remaining name 'PrixcarDamageQueue' 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.WLEventContextImpl.lookup(WLEventContextImpl.java:254) at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393) at javax.naming.InitialContext.lookup(InitialContext.java:392) at weblogic.jms.common.CDS$2.run(CDS.java:222) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:216) at
My doubt is will queue be displayed in JNDI tree ?? I mean there is a JNDI tree in weblogic admin screen and I am getting only the PrixcarConnectionFactory in that and not the PrixcarDamageQueue , may be thats why its showing "unable to connect to the JMS ???" Please advice.....
I changed both the xml's and the JNDI names in the admin screen.

NameNotFound exceotion

Similar Messages

Maybe you are looking for