- This topic has 3 replies, 2 voices, and was last updated 18 years, 5 months ago by
sspiterifcg.
-
AuthorPosts
-
sspiterifcgMemberHello,
I’m new to MyEclipse and I am having a difficulty setting it up to use it with Weblogic 8.1. I followed the standard instructions in setting it up.
When it comes to starting the server I get this error in the debug perspective under the newLocalContext:
Source not found for WLInitialContextFactoryDelegate.newLocalContext(Environment, String) line: 417
I don’t know if this is of use but in the variables
this=WLInitialContextFactoryDelegate
and when highlighted weblogic.jndi.WLInitialContextFactoryDelegate@1cbd4f7 is given.
Here is some background to what I have set up. My weblogic preferences are:
BEA Home: C:\bea
Weblogic Installation Dir: C:\bea\weblogic81
Admin User: weblogic
Admin Pass: weblogic
Exectuion domain root: C:\bea\user_projects\domains
Execution domain name: mydomain
Execution server name: myserver
Hostname:port: localhost:7001
Security Policy: C:\bea\weblogic81\server\lib\weblogic.policyAs you can see they look pretty standard.
My JDK is set to an install of j2sdk1.4.2_04 and some additional paths have been added to my classpath which are required for my webapp.
I’ve tried it once when my webapp has been deployed and once when I have removed the webapp. I get the same problem both times, so it is to do with weblogic and myeclipse and not my webapp since it runs fine elsewhere.
Also, this is the contents of myserver.log
####<Feb 13, 2007 5:35:16 PM GMT> <Notice> <Log Management> <RocheRTDev> <myserver> <main> <<WLS Kernel>> <> <BEA-170019> <The server log file C:\bea\user_projects\domains\mydomain\myserver\myserver.log is opened. All server side log events will be written to this file.>
Which is not too helpful…
And weblogic does work on my machine because I’ve deployed my webapp without using MyEclipse.
I really want to take advantage of MyEclipse integration because it saves me time, so your help would be much appriciated! I don’t really know where to turn in fixing this error!
Thanks very much,
Steve
February 14, 2007 at 10:32 am #266115
Scott AndersonParticipantSteve,
It looks like your domain has been modified a bit from the defaults (based on the logging going to a file rather than the console) so it’s hard to know where to start since we don’t know what was done.
Could you try the following to help diagnose the issue. Create a new domain using BEA’s Configuration Wizard, using all the defaults. Then, start the new domain and shut it down one time using the commandline scripts that are generated for the new domain. Once that works, configure the WebLogic connector in MyEclipse to point to the new domain and use the explicit Sun JDK that BEA ships on the JDK sub-page. Now start and stop the server using the Servers view, without deploying anything to it. Did that work? Now deploy your project to that new domain and restart the server. Does that work?
February 15, 2007 at 7:54 am #266149
sspiterifcgMemberI did what you said but I still get the problem. I will not start up correctly. any other ideas on how I can get this fixed?
Thanks.
February 15, 2007 at 8:43 am #266152
sspiterifcgMemberFixed it…. Under the breakpoints tab in the debug perspective there was “NoInitialContextException: caught and uncaught” breakpoint checked. Looking at the properties this is of type javax.naming.NoInitialContextException. Don’t know where it came from or whether I set it by accident, but I thought I’d best mension how it was resolved.
Thanks for looking.
-
AuthorPosts