Installing WLS6.1SP3

While installing wls61sp3_upgrade_generic.zip into an installation ow WLS 6.1 SP1, I get an error that "WebLogic Server 6.1 not found" and the text "WebLogic Server Service Pack 3 Installation failed. You do not seem to have WebLogic Server 6.1 installed for BEAHOME" and lists my home directory. I found a message on the bea site that this could be a problem with the hostname in the registry.xml, but I checked that and it is valid. Does anyone have any ideas?
Thanks,
Mike

I don't know what has changed, but it sounds like you installed SP3 and
then tried to do it again without removing SP3 first. If you are on
Windows, you can remove it through the Control Panel. On UNIX, there is
an uninstall script. I don't recall all the details yet; still on my
first cup of coffee. The documentation should help ->
http://e-docs.bea.com/wls/docs61/index.html
http://e-docs.bea.com/wls/docs61/install/index.html
http://e-docs.bea.com/wls/docs61/install/instsp.html#1075407
{uninstalling}
We can also turn on debugging to make Install Anywhere say what it is doing:
LAX_DEBUG=true -- either set or export, depending on platform.
Wayne
Jim wrote:
I have the same exact problem as this except that I only have one installation.
I had a working install of wls 6.1, sp1. I installed sp2 installation set and
then put the patch of sp3 on. The site was not working correctly, so I restored
a backup of the BEAHOME directory by copying it over the updated directory. Now
when I try to update it to SP3, it gives me the same message Mr. Jackson is getting.
I now know that my restore was the wrong way to go about it. Is there a file
elsewhere that I should be looking at? I tried all the things that Mr. Scott
suggested. What has changed?
Thanks,
Jim
"Wayne W. Scott" <[email protected]> wrote:
Hi Mike:
I figure you used the correct command for the install since it got as
far as it did.
Since you have 2 installations of WLS 6.1, check the InstallDir in the
registry.xml.
Then, what do you see from the following commands:
java -version
which java
There is a good chance the best jdk for this is not being chosen. For
the WLS installation you want to upgrade, note the FULL path to its jdk
and put that one's /bin in FRONT of PATH. For example:
export PATH=/opt/mike/bea/jdk131/bin:$PATH
You might have a jdk131_01 or jdk131_02; use the newer one.
If this doesn't do it, either download the package with WLS + the SP
and
use that, or file a support case.
Thanks,
Wayne

Similar Messages

Install Wls6.0 on Solaris 8.0 for x86

I have a pc with Solaris 8.0 for x86 installed .I also install jre1.3 on it.
When I try to install wls6.0 on it ,there comes an error message"can't find
libjava.so ".
I've found the file libjava.so at path "j2re1_3_0/lib/i386/" .
Why the installer didn't find the file ??

create a link (or copy the files) from your $JDK13/bin/i386 to the /usr/bea/jdk130/bin.
Eric Ma wrote:
Glen:
I followed your instructions and was able to install the server.
However, when I tried to start the server from under mydomain,
I got an error message saying java was not found in /usr/bea/jdk130/bin/i386/native_threads/java.
I did copy the i386 directory from the J2SDK SE 1.3.0 home to
under /usr/bea/jdk130/jre/lib per your earlier post. Can you tell
me what else I have to do? TIA,
Eric
glen wilcox <[email protected]> wrote:
You will need to install the 1.3 JDK on your Solairs x86
box, then invoke
the install script from the command line with the following
flag:
LAX_VM /usr/local/jdk/bin/java
where /usr/local/jdk/bin/java represents your installation
of JDK1.3.
Eric Ma wrote:
Have you been able to install WLS 6.0 on Solaris 8 Intel?I cannot
get the downloaded bin file to execute (therefore impossibleto
copy anything into the bea/jdk130 directory), becausethe libjava.so
file cannot be found, even though I included /usr/jdk1.3/jre/lib/i386
in LD_LIBRARY_PATH.
Any further suggestion is appreciated.
Eric Ma
glen wilcox <[email protected]> wrote:
Technically the x86 platform isn't supported but we
had
a similar need to use
it. Try copying the i386 directory that came with the
JDK1.3 you downloaded into
/usr/bea/jdk130/jre/lib (your path may be differentbut
you want to place i386
in the JDK1.3 that came with the WLS6.0). Also be aware
that WLS will ignore
your suggestion to use your JDK and will use it's own
(regardless of what you
specify in the startup file). You will not be ableto
use the Performance Pack
(you'll see the exception when you start the serverbut
it doesn't appear to be
fatal).
Glen Wilcox
Senior Consultant
Valtech

WLS6.1sp3 silly logging problem

Hello everybody.
I'm not sure this is the proper newsgroup but I hope
someone can help me, please.
I can't get any System.out.println from my EJBs
to appear in the WLS log files. Details below.
I have this WLS6.1sp3 domain on SunOS 5.8:
- machine 1: Admin WLS + "dev" single Managed WLS;
- machine 2: "cluster Proxy Servlet" Managed WLS;
- machine 3: "production" pair of clustered Managed WLSs;
all WLs instances are managed from the Console
through NodeManager.
I'm dealing with the "backend" layer of an application,
which is an EAR with just a JAR for EJBs and some
additional libraries. This is deployed on both the
"dev" single WLS and the "production" cluster.
In short, NO System.out.println from any class in
the EAR will ever appear in the WLS instances' log
files: the log files only show the WLS' own messages,
according to the selected logging level.
Yet, all the output from the EAR classes can be read from
the WSL console through "Get StdOut for this server".
I was told that this can sometimes happen if the WLS
log file has an extension of ".log" and can be fixed by
changing the extension to ".out", but it didn't work.
Moreover, in a separate test domain (with just a single
WLS instance) the logging from the same EAR
with the same server settings works properly.
Where am I doing wrong? Or am I missing something
basic about the way WLS works? Please help.
With lots of TIA,
Paola R.

Hello Paola:
if you want to print messages to the WLS log files, you must either use a
message catalog or the weblogic.logging.NonCatalogLogger class.
For information about the 6.1 message catalogs, see http://e-
docs.bea.com/wls/docs61/i18n/index.html
For information about NonCatalogLogger, refer to the Javadoc:
http://e-docs.bea.com/wls/docs61/javadocs/weblogic/logging/package-
summary.html
In WLS 7.0 and later, there's a document that describes how to use the WLS
logging services. Much of it applies to 6.1:
http://e-docs.bea.com/wls/docs70/logging/index.html
Darren Carlton
Technical Writer for BEA WebLogic Server

Problem In Installing WLS6.1sp1 on Linux

Hi,
When I am installing weblogic6.1 sp1 on Linux 7.1 I am getting a page full specified font not found.
Any Ideas about it?
Thanks In Advance
-Siva

Hi.
No one else seems to be reporting this. Please post the full text of the error here.
Thanks,
Michael
Siva wrote:
Hi,
When I am installing weblogic6.1 sp1 on Linux 7.1 I am getting a page full specified font not found.
Any Ideas about it?
Thanks In Advance
-Siva--
Developer Relations Engineer
BEA Support

Install wls6.1

I have installed wls 6.1sp4 on a winxp, but it seems that the WL_HOME/bin directory
is not created.
So now I am missing the files that is supposed to be there.
Kris

Hello, David. I don't see any reason why this would not work. Please be sure
to check out the docs on "Upgrading from a Pre-6.0 Version of WebLogic
Server" at http://e-docs.bea.com/wls/docs61/install/instpre.html#1070180
before you proceed.
Regards,
-- Ian
"David Jian" <[email protected]> wrote in message
news:3b840aa8$[email protected]..
Is that possible to keep wls5.1 and install wls 6.1 on the same NT box? We
are not running them at the same time, but need to keep both and run one
version at a time.
Thanks
DJ

Problems compiling jsps using WLS6.1sp3 as Win2k service

Two related issues:
Issue #1:
I'm encountering an error where the javac compiler cannot be found (when
trying to compile jsps) when running as a Windows Service. JAVA_HOME is set
in the profile and I'm passing in E:\bea\jdk131\bin in the extrapath
parameter of beasvc.exe. The error I get is a file permission exception -
unable to access (read) C:\WINNT\System32\javac. Question is - why is it
looking there and not in JAVA_HOME? To try and isolate this, I've removed
everything from the PATH and CLASSPATH environment variables except for
E:\bea\jdk131\bin but to no avail.
Issue #2:
I've also tried hard-coding the location E:\bea\jdk131\bin\javac.exe into
the config.xml and weblogic.xml. The error is then a file permission
exception - unable to access (read) .\E:\bea\jdk131\bin\javac. Note the
initial dot-slash... however, the weblogic.policy file is set to allow
read,execute access for all files and directories below E:\bea (I've even
tried to grant a permission to .\E:\....... but that didn't work either)
Hope someone can help - it's been driving me nuts for a week now! What do I
need to do to get Weblogic to find javac when running as a Windows Service?

Hi Sudha
Plese see the error in the starting post. Do u agree with me now? The server is looking for org.apache.jsp.techSupport_jsp class.
Generated servlet error:
[javac] Compiling 1 source file
D:\MANTRA\jboss-3.0.4_tomcat-4.1.12\tomcat-4.1.x\work\M
inEngine\localhost\JSPTechSupport\techSupport_jsp.java:
2: cannot resolve symbol
symbol : class TechSupportBean
location: class org.apache.jsp.techSupport_jsp
TechSupportBean techSupportBean = null;
^
An error occurred at line: 2 in the jsp file:
/techSupport.jsp
Generated servlet error:
D:\MANTRA\jboss-3.0.4_tomcat-4.1.12\tomcat-4.1.x\work\M
inEngine\localhost\JSPTechSupport\techSupport_jsp.java:
4: cannot resolve symbol
symbol : class TechSupportBean
location: class org.apache.jsp.techSupport_jsp
techSupportBean = (TechSupportBean)
rtBean) pageContext.getAttribute("techSupportBean",
PageContext.APPLICATION_SCOPE);
^Take care.
Hafizur Rahman
SCJP

Problem using file based JNDI with JMS Bridge, WL 6.1sp3

          I am trying to connect an MQ queue to a Weblogic JMS queue using the JMS bridge,
          WLS6.1sp3. I have the CR081404_61sp3.jar and CR081511_61sp3.jar patches.
          I am having trouble getting the bridge to look up the MQ queue in the file based
          JNDI. According to the log it is trying to use a weblogic.jndi.WLInitialContextFactory
          instead of a com.sun.jndi.fscontext.RefFSContextFactory, which is what it is configured
          to use. I am getting the following error:
          <Sep 29, 2002 12:16:22 PM EDT> <Info> <MessagingBridge> <Bridge "Provd Messaging
          Bridge" is getting the connections to the two adapters.>
          <Sep 29, 2002 12:16:22 PM EDT> <Debug> <MessagingBridge> <Messaging Bridge Debugging
          RUNTIME! Bridge Provd Messaging Bridge In getConnections: isStopped = false>
          <Sep 29, 2002 12:16:22 PM EDT> <Debug> <MessagingBridge> <Messaging Bridge Debugging
          RUNTIME! Bridge Provd Messaging Bridge Getting source connection: sourceConnSpec
          = weblogic.jms.adapter.JMSConnectionSpec@27166f>
          <Sep 29, 2002 12:16:22 PM EDT> <Info> <Connector> <Unable to locate context: java:/comp/env/wls-connector-resref>
          <Sep 29, 2002 12:16:22 PM EDT> <Info> <Connector> <Unable to determine Resource
          Principal for Container Managed Security Context.>
          <Sep 29, 2002 12:16:22 PM EDT> <Info> <Connector> <Unable to locate context: java:/comp/env/wls-connector-resref>
          <Sep 29, 2002 12:16:22 PM EDT> <Info> <Connector> <Unable to determine Resource
          Principal for Container Managed Security Context.>
          <Sep 29, 2002 12:16:22 PM EDT> <Warning> <Connector> << Weblogic Messaging Bridge
          Adapter (XA) > ResourceAllocationException of javax.resource.ResourceException:
          ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory,
          url = file:/opt/mqm/java/mq-jndi, user name = guest, password = guest on createManagedConnection.>
          <Sep 29, 2002 12:16:22 PM EDT> <Error> <Connector> <Error granting connection
          request.>
          <Sep 29, 2002 12:16:22 PM EDT> <Info> <MessagingBridge> <Bridge "Provd Messaging
          Bridge" failed to connect to the source destination and will try again in 25 seconds.
          (javax.resource.spi.ResourceAllocationException: CreateManagedConnection Error:
          ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory,
          url = file:/opt/mqm/java/mq-jndi, user name = guest, password = guest)>
          <
          The configuration of the bridge, printed out in the log, is:
          <Sep 29, 2002 12:16:00 PM EDT> <Debug> <MessagingBridge> <Messaging Bridge Debugging
          STARTUP! Bridge Provd Messaging Bridge's source properties are:
          AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
          Classpath=null
          ConnectionFactoryJNDIName = PMS.mqQcf
          ConnectionURL = file:/opt/mqm/java/mq-jndi
          InitialConnectionFactory = com.sun.jndi.fscontext.RefFSContextFactory
          DestinationType = Queue
          DestinationJNDIName = PMS.mqProvdRequest>
          <Sep 29, 2002 12:16:00 PM EDT> <Debug> <MessagingBridge> <Messaging Bridge Debugging
          STARTUP! Bridge Provd Messaging Bridge's target properties are:
          AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
          Classpath=null
          DestinationType = Queue>
          Am I correct in assuming it should be using the fscontext connection factory?
          Why is it using the weblogic one?
          Jason


CR081511_61sp3.jar patch should fix the problem. Make sure that the
          jar file is picked up. It should be put before other weblogic jar files.
          You should be able to tell if it is picked up by looking at the first
          couple of lines of your server log file.
          Dongbo
          Jason Kriese wrote:
          >
          > I am trying to connect an MQ queue to a Weblogic JMS queue using the JMS bridge,
          > WLS6.1sp3. I have the CR081404_61sp3.jar and CR081511_61sp3.jar patches.
          >
          > I am having trouble getting the bridge to look up the MQ queue in the file based
          > JNDI. According to the log it is trying to use a weblogic.jndi.WLInitialContextFactory
          > instead of a com.sun.jndi.fscontext.RefFSContextFactory, which is what it is configured
          > to use. I am getting the following error:
          >
          > <Sep 29, 2002 12:16:22 PM EDT> <Info> <MessagingBridge> <Bridge "Provd Messaging
          > Bridge" is getting the connections to the two adapters.>
          > <Sep 29, 2002 12:16:22 PM EDT> <Debug> <MessagingBridge> <Messaging Bridge Debugging
          > RUNTIME! Bridge Provd Messaging Bridge In getConnections: isStopped = false>
          > <Sep 29, 2002 12:16:22 PM EDT> <Debug> <MessagingBridge> <Messaging Bridge Debugging
          > RUNTIME! Bridge Provd Messaging Bridge Getting source connection: sourceConnSpec
          > = weblogic.jms.adapter.JMSConnectionSpec@27166f>
          > <Sep 29, 2002 12:16:22 PM EDT> <Info> <Connector> <Unable to locate context: java:/comp/env/wls-connector-resref>
          >
          > <Sep 29, 2002 12:16:22 PM EDT> <Info> <Connector> <Unable to determine Resource
          > Principal for Container Managed Security Context.>
          > <Sep 29, 2002 12:16:22 PM EDT> <Info> <Connector> <Unable to locate context: java:/comp/env/wls-connector-resref>
          >
          > <Sep 29, 2002 12:16:22 PM EDT> <Info> <Connector> <Unable to determine Resource
          > Principal for Container Managed Security Context.>
          > <Sep 29, 2002 12:16:22 PM EDT> <Warning> <Connector> << Weblogic Messaging Bridge
          > Adapter (XA) > ResourceAllocationException of javax.resource.ResourceException:
          > ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory,
          > url = file:/opt/mqm/java/mq-jndi, user name = guest, password = guest on createManagedConnection.>
          >
          > <Sep 29, 2002 12:16:22 PM EDT> <Error> <Connector> <Error granting connection
          > request.>
          > <Sep 29, 2002 12:16:22 PM EDT> <Info> <MessagingBridge> <Bridge "Provd Messaging
          > Bridge" failed to connect to the source destination and will try again in 25 seconds.
          > (javax.resource.spi.ResourceAllocationException: CreateManagedConnection Error:
          > ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory,
          > url = file:/opt/mqm/java/mq-jndi, user name = guest, password = guest)>
          > <
          >
          > The configuration of the bridge, printed out in the log, is:
          >
          > <Sep 29, 2002 12:16:00 PM EDT> <Debug> <MessagingBridge> <Messaging Bridge Debugging
          > STARTUP! Bridge Provd Messaging Bridge's source properties are:
          > AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
          > Classpath=null
          > ConnectionFactoryJNDIName = PMS.mqQcf
          > ConnectionURL = file:/opt/mqm/java/mq-jndi
          > InitialConnectionFactory = com.sun.jndi.fscontext.RefFSContextFactory
          > DestinationType = Queue
          > DestinationJNDIName = PMS.mqProvdRequest>
          > <Sep 29, 2002 12:16:00 PM EDT> <Debug> <MessagingBridge> <Messaging Bridge Debugging
          > STARTUP! Bridge Provd Messaging Bridge's target properties are:
          > AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
          > Classpath=null
          > DestinationType = Queue>
          >
          > Am I correct in assuming it should be using the fscontext connection factory?
          > Why is it using the weblogic one?
          >
          > Jason

Does WLS6.1-sp2 support J2EE-1.3 spec by default?

hi All,
          Just installed WLS6.1-sp2 30-day evaluation. I tested on it with a simple
          Filter servlet, but it didn't work at all.
          I tried to find some docs related to J2EE spec compliance and they say the
          default is J2EE-1.3. Can anyone tell me the default J2EE spec supported by
          WLS6.1-sp2? And how can I check the currently-used J2EE spec in my running
          WLS? How can I switch between J2EE-1.2 and 1.3?
          Thanks
          Liu Yan


I think it is enabled by default. Note that javax.servlet.Filter which is
          shipped with WebLogic is different from one in final Servlet 2.3. Also you
          can search this newsgroup - there are lots of problems with Filters in 6.1.
          If you think that the problem is with your program, try to deploy it on Resin
          or Tomcat to see if it is actually the case.
          Liu Yan <[email protected]> wrote:
          > Thanks for your reply. I found that WLS6.1 DOES support so-called non-final
          > version of J2EE-1.3 spec. And my downloaded version is J2EE-1.3
          > feature-enabled by default. Seems the problem of my filter program.
          > But do you know how to configure J2EE compatibility in admin console? I mean
          > can I switch back and forth between J2EE-1.2 and 1.3?
          > Thanks
          > Liu Yan
          > "Dimitri Rakitine" <[email protected]> Ð´ÈëÏûÏ¢ÐÂÎÅ
          > :[email protected]...
          >> 6.1 does not support final Servlet 2.3 spec. You can see release notes
          >> for details: http://e-docs.bea.com/wls/docs61/notes/index.html
          >>
          >> Liu Yan <[email protected]> wrote:
          >> > hi All,
          >>
          >> > Just installed WLS6.1-sp2 30-day evaluation. I tested on it with a
          > simple
          >> > Filter servlet, but it didn't work at all.
          >>
          >> > I tried to find some docs related to J2EE spec compliance and they say
          > the
          >> > default is J2EE-1.3. Can anyone tell me the default J2EE spec supported
          > by
          >> > WLS6.1-sp2? And how can I check the currently-used J2EE spec in my
          > running
          >> > WLS? How can I switch between J2EE-1.2 and 1.3?
          >>
          >> > Thanks
          >>
          >> > Liu Yan
          >>
          >>
          >>
          >>
          >> --
          >> Dimitri
          Dimitri

Install failed on solaris

I am getting the following error when installing wls6.0 on a solaris 5.7 system.
Does anyone know what is missing? Thanks.
$ sh weblogic600sp1_sol.bin
Preparing to install...
Invocation of this Java Application has caused an InvocationTargetException. This
application will now exit. (LAX)
Stack Trace:
java.lang.NoClassDefFoundError
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:120)
at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:58)
at java.awt.Window.<init>(Window.java:186)
at java.awt.Frame.<init>(Frame.java:315)
at java.awt.Frame.<init>(Frame.java:262)
at com.zerog.ia.installer.Main.b([DashoPro-V1.2-120198])
at com.zerog.ia.installer.Main.main([DashoPro-V1.2-120198])
at java.lang.reflect.Method.invoke(Native Method)
at com.zerog.lax.LAX.launch([DashoPro-V1.2-120198])
at com.zerog.lax.LAX.main([DashoPro-V1.2-120198])
GUI-

Your DISPLAY variable is not set. By default the installation runs in GUI mode.
To run in console (line mode) use the "-i console" option.
JD
"Cynthia He" <[email protected]> wrote:
>
I am getting the following error when installing wls6.0 on a solaris
5.7 system.
Does anyone know what is missing? Thanks.
$ sh weblogic600sp1_sol.bin
Preparing to install...
Invocation of this Java Application has caused an InvocationTargetException.
This
application will now exit. (LAX)
Stack Trace:
java.lang.NoClassDefFoundError
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:120)
at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:58)
at java.awt.Window.<init>(Window.java:186)
at java.awt.Frame.<init>(Frame.java:315)
at java.awt.Frame.<init>(Frame.java:262)
at com.zerog.ia.installer.Main.b([DashoPro-V1.2-120198])
at com.zerog.ia.installer.Main.main([DashoPro-V1.2-120198])
at java.lang.reflect.Method.invoke(Native Method)
at com.zerog.lax.LAX.launch([DashoPro-V1.2-120198])
at com.zerog.lax.LAX.main([DashoPro-V1.2-120198])
GUI-

Install error :InvocationTargetException

I am installing Weblogic v 6.1 sp2 on Sun Solaris 8 on executing the command "
sh weblogic600sp2_sol.bin -i console" the installation starts and after selecting
the language as English, console displays the following error and the installation
stops, please advice
"Invocation of this Java Application has caused an InvocationTargetException.
This application will now exit. (LAX)
Stack Trace:
java.lang.NullPointerException
at java.util.StringTokenizer.<init>(StringTokenizer.java:122)
at java.util.StringTokenizer.<init>(StringTokenizer.java:138)
at com.zerog.ia.installer.steps.ChooseJavaVM.j([DashoPro-V1.2-120198])
at com.zerog.ia.installer.steps.ChooseJavaVM.c([DashoPro-V1.2-120198])
at com.zerog.ia.installer.Main.a([DashoPro-V1.2-120198])
at com.zerog.ia.installer.Main.main([DashoPro-V1.2-120198])
at java.lang.reflect.Method.invoke(Native Method)
at com.zerog.lax.LAX.launch([DashoPro-V1.2-120198])
at com.zerog.lax.LAX.main([DashoPro-V1.2-120198])
GUI-"
Has someone faced similar problem before? I have also tried installing the WebLogic
Server 6.1 as well but I get the same error.
Thanx !!

I too am in the process of installing WLS6.1SP1. I get similar
exception. You are lucky enough to get pass the 'language selection
step' ;-)
For me all i get when i invoke the installer is
preparing to install....
java.lang.NoClassDefFoundException : com/zerog/lax/LAX not found.
Well, now that we are done with the bad news, im trying the following.
Apparently the installanywhere is using WRONG VERSION OF JVM. Try
using jdk1.3.1
Also try downloading the .bin installer in the BINARY mode if you have
access to the remote ftp server where the installer is sitting.
Make sure that you have enough space in /tmp dir. I think the
installer writes all the temp files there.
Hope this helps me too :-)
--S
"BingYi" <[email protected]> wrote in message news:<3c405318$[email protected]>...
I am installing Weblogic v 6.1 sp2 on Sun Solaris 8 on executing the command "
sh weblogic600sp2_sol.bin -i console" the installation starts and after selecting
the language as English, console displays the following error and the installation
stops, please advice
"Invocation of this Java Application has caused an InvocationTargetException.
This application will now exit. (LAX)
Stack Trace:
java.lang.NullPointerException
at java.util.StringTokenizer.<init>(StringTokenizer.java:122)
at java.util.StringTokenizer.<init>(StringTokenizer.java:138)
at com.zerog.ia.installer.steps.ChooseJavaVM.j([DashoPro-V1.2-120198])
at com.zerog.ia.installer.steps.ChooseJavaVM.c([DashoPro-V1.2-120198])
at com.zerog.ia.installer.Main.a([DashoPro-V1.2-120198])
at com.zerog.ia.installer.Main.main([DashoPro-V1.2-120198])
at java.lang.reflect.Method.invoke(Native Method)
at com.zerog.lax.LAX.launch([DashoPro-V1.2-120198])
at com.zerog.lax.LAX.main([DashoPro-V1.2-120198])
GUI-"
Has someone faced similar problem before? I have also tried installing the WebLogic
Server 6.1 as well but I get the same error.
Thanx !!

Sample of weblogic.policy for WLS6.0

Dear all,
I had installed WLS6.0 on Solaris 2.6 and try to turn on
java security manager with this option
-Djava.security.policy==/usr/home/bea/wlserver6.0/lib/
weblogic.policy -Djava.security.manager
This make me unable to boot WLS. Here is contents of my weblogic.policy
grant {
// Permission "enableSubstitution" needed to run the WebLogic console
permission java.io.SerializablePermission "enableSubstitution";
// Permission "modifyThreadGroup" required to run the WebLogic Server
permission java.lang.RuntimePermission "modifyThreadGroup";
permission java.lang.RuntimePermission "setContextClassLoader";
// Permission "setIO" needed to start a server from the WebLogic console
permission java.lang.RuntimePermission "setIO";
// Permission "getClassLoader" needed for many EJB clients
permission java.lang.RuntimePermission "getClassLoader";
permission java.lang.RuntimePermission "stopThread";
permission java.net.SocketPermission "localhost:1024-", "listen";
permission java.util.PropertyPermission "*", "read,write";
permission java.io.FilePermission "${/}usr${/}home${/}bea${/}wlserver6.0${/}-",
"read,write,delete,execute";
And here is the error occurs
java.security.AccessControlException: access denied (java.io.FilePermission /usr/home/bea/wlserver6.0
read)
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:272)
at java.security.AccessController.checkPermission(AccessController.java:399)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:545)
at java.lang.SecurityManager.checkRead(SecurityManager.java:890)
at java.io.File.exists(File.java:535)
at weblogic.utils.classloaders.ClasspathClassFinder.<init>(ClasspathClassFinder.java:61)
at weblogic.Home.getFileSource(Home.java:64)
at weblogic.Home.<init>(Home.java:29)
at weblogic.Home.getInstance(Home.java:82)
at weblogic.Home.getPath(Home.java:90)
at weblogic.security.internal.ServerAuthenticate.main(ServerAuthenticate.java:76)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:167)
at weblogic.Server.main(Server.java:35)
Could anyone give me what goes wrong. If you have a working version of weblogic.policy,
please share with me.
Regards,
Khemchart

Here's a snippet from upcoming release notes about the Java
security manager and the example weblogic.policy file.
Using the Java Security Manager with WebLogic Server
When you run WebLogic Server under Java 2 (JDK 1.2 or 1.3), WebLogic
Server can use the Java Security Manager in Java 2 to provide
additional access control for WebLogic Server resources. The Java
Virtual Machine (JVM) has security mechanisms built into it which can
be managed via a security policy file. The Java Security Manager can
enforce a set of permissions granted to CodeSource or SignedBy
classes. The permissions allow certain classes running in that
instance of the JVM to do or not do certain runtime operations. In
many cases, where the threat model does not include malicious code
being run on the JVM, the Java Security Manager is unnecessary. In
cases such as when an Application Service Provider uses WebLogic
Server and unknown classes are being run, the Java Security Manager is
necessary. To use the Java Security Manager with WebLogic Server,
specify the -Djava.security.manager property when starting WebLogic
Server.
Note: In past releases of WebLogic Server, the Java Security Manager
was enabled by using the -Dweblogic.security.manager property when
starting WebLogic Server. Please note the change in the property for
WebLogic Server version 6.0 and greater.
The Java Security Manager uses a security policy file that defines
permissions. The full pathname of security policy is specified in the
-Djava.security.policy property when starting WebLogic Server. If you
enable the Java Security Manager but do not specify a security policy
file, the Java Security Manager uses the default security policies
defined in the java.security and java.policy files in the
$JAVA_HOME/lib/security directory.
WebLogic Server includes an example security policy file named
weblogic.policy. This file contains a set of default permissions.
You need to make the following edits to the file in order to use the
file with your WebLogic Server deployment.
1. Edit the following lines in the weblogic.policy file, replacing the
specified location with the location of your WebLogic Server
installation:
grant codebase "file://BEA/-"{
permission java.io.FilePermission "D:${/}BEA${/}=", ...
Note: This change assumes your installation directory structure is the
same as the one described in the BEA Home Directory topic in the BEA
WebLogic Server Installation Guide.
2. If you want to run the Administration Console, add the following
grant block and permissions to the weblogic.policy file:
grant {
     permission java.io.FilePermission
"D:{/}BEA${/}wlserver600${/}weblogic${/}management${/}console${/}-",
"read";
     permission java.io.FilePermission
"D:{/}BEA${/}wlserver600${/}config${/}mydomain${/}applications${/}.wl_te\
mp_do_not_delete${/}weblogic${/}management${/}console${/}-", "read";
     permission java.util.PropertyPermission "user.*", "read";
3. If you have extra directories in your CLASSPATH or if you are
deploying applications in extra directories, you need to add specific
permissions for those directories to your weblogic.policy file.
BEA also recommends taking the following precautions:
? Make a backup copy of the weblogic.policy file and put the backup
copy in a secure location.
? Set the permissions on the weblogic.policy file such that the
adminstrator of the WebLogic Server deployment has write and read
privileges and no other users
To use the Java Security Manager and the weblogic.policy file with
your WebLogic Server deployment, use the following properties when
starting WebLogic Server:
$java... -Djava.security.manager \
-Djava.security.policy==D:/BEA/wlserver600/lib/weblogic.policy
For more information about the Java Security Manager, see the Javadoc
shipped with Java 2.
The RecordingSecurityManager utility can be used to detect permission
problems that occur when starting and running WebLogic Server. The
utility outputs permissions that can be added to your security policy
file to resolve the permission problems that the utility finds. The
RecordingSecurityManager is available at the BEA Developer's Center.

WL6.1sp3 problem with getServletContext?

          I have just installed WL6.1sp3 and tried to move a web application from Tomcat
          4.02 to WebLogic. When I access a jsp, I get the following compile error indicating
          that it does not recognize the getServletContext method.
          Can anyone tell me why this is happening and how I can fix this?
          E:\WRS\WEB-INF\_tmp_war_WRS\jsp_servlet\__wrslogin.java:101: cannot resolve symbol
          symbol : method getServletContext ()
          location: class jsp_servlet.__wrslogin
          String wrsDBLogin = getServletContext().getInitParameter("wrsDBLogin");
          //[ /WRSLogin.jsp; Line: 12]
          Thanks,
          Chris


AFAIK there is no getServletContext() method in javax.servlet.Servlet.
          change your JSP to
          String wrsDBLogin =
          getServletConfig().getServletContext().getInitParameter("wrsDBLogin");
          or
          String wrsDBLogin = application.getInitParameter("wrsDBLogin");
          "Chris L" <[email protected]> wrote in message
          news:[email protected]..
          >
          > I have just installed WL6.1sp3 and tried to move a web application from
          Tomcat
          > 4.02 to WebLogic. When I access a jsp, I get the following compile error
          indicating
          > that it does not recognize the getServletContext method.
          >
          > Can anyone tell me why this is happening and how I can fix this?
          >
          > E:\WRS\WEB-INF\_tmp_war_WRS\jsp_servlet\__wrslogin.java:101: cannot
          resolve symbol
          > symbol : method getServletContext ()
          > location: class jsp_servlet.__wrslogin
          > String wrsDBLogin =
          getServletContext().getInitParameter("wrsDBLogin");
          > //[ /WRSLogin.jsp; Line: 12]
          >
          >
          >
          > Thanks,
          >
          > Chris
          Dimitri

Scalability of the security realm / isUserInRole?

When callling isUserInRole(), it seems that WLS6.1sp3 wants to load all
the users in the role into memory and eventually call getUser() on each of
them. Could someone verify or debunk that this is indeed what's happening?
We have roles with thousands of users in them so the above gets very
expensive to do (even with group/user caching timeout extended.)
Are there any workarounds to improve isUserInRole performance?
thanks,
-Ade

We wanted some thread dumps at intervals, but didn't want to have to do it manually so I created a Windows Scripting Host script to perform the Ctrl-Breaks.
You may be able to do the same and execute it from a telnet command prompt (this of course assumes that you have telnet set up and also the Windows Scripting host installed).

Error creating a connection pool (No suitable driver)

I have just installed WLS6.1 SP3
I try to create a connection with the following parameters
URL = jdbc:oracle:thin@myOracleServer:1521:myOracleSID
DriverName = oracle.jdbc.driver.OracleDriver
every thing else is left as the defaults,
when I click create everything is OK.
I then go to the "Targets" tab and select myserver,
move it to the chosen column and click apply.
I then get the error
<Error> <JDBC> <Cannot startup connection pool "myCP" No suitable driver>
I looked at the doc edocs.bea.com/wls/docs61/jdbc/thirdparty.html
Under the section "Setting environment for your third party driver"
it implys that if your using sybase jconnect or oracle thin drivers
you do not need to do anything else.
I looked in the weblogic.jar file and the OracleDriver.class file
is there under oracle\jdbc\driver.
the CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
I would have thought that the driver class in the jar file
would have be picked up given the path & classname match the
driver name enter in the console.
Any ideas on how to fix this problem?

"Robert Towler" <[email protected]> wrote in message
news:3dd3ea04$[email protected]..
Thanks Slava, you were correct,
I really appreciate it.Glad to help :)
Regards,
Slava Imeshev
"Slava Imeshev" <[email protected]> wrote:
Hi Robert,
Looks like colon is missing after jdbc:oracle:thin. The url should be
jdbc:oracle:thin:@myOracleServer:1521:myOracleSID
Regards,
Slava Imeshev
"Robert Towler" <[email protected]> wrote in message
news:3dd3e3c6$[email protected]..
I have just installed WLS6.1 SP3
I try to create a connection with the following parameters
URL = jdbc:oracle:thin@myOracleServer:1521:myOracleSID
DriverName = oracle.jdbc.driver.OracleDriver
every thing else is left as the defaults,
when I click create everything is OK.
I then go to the "Targets" tab and select myserver,
move it to the chosen column and click apply.
I then get the error
<Error> <JDBC> <Cannot startup connection pool "myCP" No suitable
driver>
>>>
I looked at the doc edocs.bea.com/wls/docs61/jdbc/thirdparty.html
Under the section "Setting environment for your third party driver"
it implys that if your using sybase jconnect or oracle thin drivers
you do not need to do anything else.
I looked in the weblogic.jar file and the OracleDriver.class file
is there under oracle\jdbc\driver.
the CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
I would have thought that the driver class in the jar file
would have be picked up given the path & classname match the
driver name enter in the console.
Any ideas on how to fix this problem?

Console doesn't start?

Hi
I installed WLS6.0 SP1 to NT4 SP6. Console doesn't start when I'm logged to
our domain. Dr. Watson reports application error in beaexec2.exe. When I'm
logged in as a local administrator console works fine. What's wrong?
Seppo

I am having the same Problem.Can anyone give some suggestions

Installing WLS6.1SP3

Similar Messages

Maybe you are looking for