Weblogic server 8.1 SP2 to SP6 ugrade

Hello All
Am looking for any document that would outline steps to upgrade weblogic 8.1 SP2 to SP6.
Can we directly upgrade to SP6 ?
Found the patch 9479129 BEA WebLogic Platform: Patchset WEBLOGIC PLATFORM 8.1 WITH SP6 UPGRADE INSTALLER but the readme doesnt have any instructions.
Neither could i find in http://docs.oracle.com/cd/E13222_01/wls/docs81/index.html
Any pointers in this regard would be helpful.
Thanks
Sundari

WLS 8.1SP2 can not be upgraded directly to WLS8.1 SP6.
The existing domain should be at WLS 8.1 SP4 atleast so that it can be upgraded to WLS 8.1 SP6.
The link:
http://commerce.bea.com/
Has be decommissioned and now in order to download the upgrade installers and WLS service pack versions you should have a Support ID which is required to create a login to metalink.oracle.com .
Then You can follow the following:
Login to: https://Metalink.oracle.com
Go to tab: Patches & Updates
Quick Links to: Latest Patchsets, Mini Packs and Maintenance Packs
Patch Bundles for Individual Products or Components
Select BEA Weblogic Platform
Select the WebLogic Main version and SP version
Then you should see the download screen.
Thanks,
Sandeep

Similar Messages

BIBeans internationalization issue with weblogic server 8.1 sp2

We use oralce bibeans 9.0.4 to develop OLAP web application in Chinsese Simplified environment. When deploy the web application on the embedded OC4J server, everything goes well. All the labels (Line items and image button labels etc. ) of the crosstab is displayed in chinese. but it always display English labels when delploy it on weblogic server V8.1 sp2.
currently on my web page java.util.Locale.getDefault() return zh_CN
I have done two things:
first, add exportCharacterEncoding init param for UIXServlet
<init-param>
<param-name>exportCharacterEncoding</param-name>
<param-value>GBK</param-value>
</init-param>
second,Set locale for the BIThinSession instance in jsp file.
oracle.dss.addins.jspTags.BIThinSession bisession = (oracle.dss.addins.jspTags.BIThinSession) pageContext.findAttribute("SalesBIThinSession");
bisession.setLocale(Locale.getDefault());
Is this a bug that bibeans can not locate resource bundles correctly base on the user's specified environment? Is there an invisible environment variable base on which the bibean tags judge to select a resource file and result in this phenomenon?

The intersting point here is that the application works using an Oracle stack but does not work using an IBM stack. I will contact our development engineers for more information and will post another response when I have a reply.
Business Intelligence Beans Product Management Team
Oracle Corporation

Location for dll files in weblogic server 6.1 sp2

"where to keep *.dll files in weblogic server 6.1 sp2". Application is deployed on weblogic server 6.1 sp2. Application is being integrated with webmethod to publish data. For that we need to put awssl40jn.dll in weblogic server. Could not able to locate where to put this dll file.

You can have the dll's anywhere. You just need to mention the location
in java.library.path.
For example if you have your Dll's in C:\bea\lib
You need to mention the following in your command line args:
java -Djava.library.path=C:\bea\lib ****Other Command Line Args****
weblogic.Server
Hope this helps.
-Kiran
"Dave Martin" <[email protected]> wrote in message news:<[email protected]>...
I don't see a DLL like yours in a fresh install of WLS 6.1 SP2
This is the complete list of DLLs I find in my fresh install of WLS 6.1 SP2 (starting
from the BEA home) on Windows:
/jdk131/bin/dt_shmem.dll
/jdk131/bin/dt_socket.dll
/jdk131/bin/jdwp.dll
/jdk131/jre/bin/ActPanel.dll
/jdk131/jre/bin/agent.dll
/jdk131/jre/bin/awt.dll
/jdk131/jre/bin/classic/jvm.dll
/jdk131/jre/bin/cmm.dll
/jdk131/jre/bin/dcpr.dll
/jdk131/jre/bin/dt_socket.dll
/jdk131/jre/bin/fontmanager.dll
/jdk131/jre/bin/hotspot/jvm.dll
/jdk131/jre/bin/hpi.dll
/jdk131/jre/bin/hprof.dll
/jdk131/jre/bin/ioser12.dll
/jdk131/jre/bin/java.dll
/jdk131/jre/bin/jawt.dll
/jdk131/jre/bin/jcov.dll
/jdk131/jre/bin/JdbcOdbc.dll
/jdk131/jre/bin/jdwp.dll
/jdk131/jre/bin/jpeg.dll
/jdk131/jre/bin/jpins32.dll
/jdk131/jre/bin/jpishare.dll
/jdk131/jre/bin/jsound.dll
/jdk131/jre/bin/msvcrt.dll
/jdk131/jre/bin/net.dll
/jdk131/jre/bin/NPJava11.dll
/jdk131/jre/bin/NPJava12.dll
/jdk131/jre/bin/NPJava131.dll
/jdk131/jre/bin/NPJava32.dll
/jdk131/jre/bin/NPOJI600.dll
/jdk131/jre/bin/packager.dll
/jdk131/jre/bin/server/jvm.dll
/jdk131/jre/bin/server/jvm_g.dll
/jdk131/jre/bin/verify.dll
/jdk131/jre/bin/zip.dll
/wlserver6.1/bin/fastfile.dll
/wlserver6.1/bin/iisforward.dll
/wlserver6.1/bin/iisproxy.dll
/wlserver6.1/bin/jsafe.dll
/wlserver6.1/bin/md5.dll
/wlserver6.1/bin/md5_g.dll
/wlserver6.1/bin/nodemanager.dll
/wlserver6.1/bin/oci816_7/weblogicoci37.dll
/wlserver6.1/bin/oci816_7/weblogicoxa37.dll
/wlserver6.1/bin/oci816_8/weblogicoci37.dll
/wlserver6.1/bin/oci816_8/weblogicoxa37.dll
/wlserver6.1/bin/oci817_8/weblogicoci37.dll
/wlserver6.1/bin/oci817_8/weblogicoxa37.dll
/wlserver6.1/bin/oci901_8/weblogicoci37.dll
/wlserver6.1/bin/oci901_8/weblogicoxa37.dll
/wlserver6.1/bin/proxy30.dll
/wlserver6.1/bin/proxy35.dll
/wlserver6.1/bin/proxy36.dll
/wlserver6.1/bin/stackdump.dll
/wlserver6.1/bin/stackdump_g.dll
/wlserver6.1/bin/terminalio.dll
/wlserver6.1/bin/wlenv.dll
/wlserver6.1/bin/wlntio.dll
/wlserver6.1/bin/wlntio_g.dll
/wlserver6.1/bin/wlntrealm.dll
/wlserver6.1/bin/wlntrealm_ms.dll
/wlserver6.1/uninstaller/resource/iawin32.dll
/wlserver6.1/uninstaller_servicepack/resource/iawin32.dll
manoj <[email protected]> wrote:
"where to keep *.dll files in weblogic server 6.1 sp2". Application is
deployed on weblogic server 6.1 sp2. Application is being integrated
with webmethod to publish data. For that we need to put awssl40jn.dll
in weblogic server. Could not able to locate where to put this dll file.

Location of WebLogic Server 6.0 sp2 installable file in ZIP format

Hello
I would like to use the ".zip" file of the WebLogic Server 6.0 sp2 installable
instead of the default ".bin" file.
Can someone help me locate the URL for downloading it?
Thanks and Regards
Kapil Pawar

Hi.
The installation for Compaq Tru64 is a zip file - 'weblogic600sp2_generic.zip'.
However, be aware that installation is not simply a matter of unzipping the file
like earlier versions of WLS. See the installation directions for details.
Thanks,
Michael
Kapil Pawar wrote:
Hello
I would like to use the ".zip" file of the WebLogic Server 6.0 sp2 installable
instead of the default ".bin" file.
Can someone help me locate the URL for downloading it?
Thanks and Regards
Kapil Pawar--
Michael Young
Developer Relations Engineer
BEA Support

Weblogic server 7.0 SP2 with jdk1.4

Our current environment is installed WLS 7.0 with SP2 on Win2000 Server. And we
like to upgrade the JDK version to 1.4.
Any suggection? Will it cause any problem to start WLS once we upgrade the JDK
version?
Thanks!
Evan

WebLogic 7.0 would not support the additional features in JDK 1.4
thanks,
Deepak
"Evan" <[email protected]> wrote:
>
Thanks for the replying.
But if we'd like to keep using WebLogic Server 7.0.
Is there any impact to upgrade to JDK 1.4?
Evan
"Deepak Vohra" <[email protected]> wrote:
WebLogic Server 7.0 supports the 1.3.1_02 JDK.
WebLogic Server 8.1 supports JDK 1.4
"Evan" <[email protected]> wrote:
Our current environment is installed WLS 7.0 with SP2 on Win2000 Server.
And we
like to upgrade the JDK version to 1.4.
Any suggection? Will it cause any problem to start WLS once we upgrade
the JDK
version?
Thanks!
Evan

WebLogic Server 8.1 SP2 - Sudden Crash

Hello,
We have WebLogic 8.1 SP2 installed on Unix box (SunOS 5.8 Generic_108528-29 sun4u sparc SUNW,Sun-Fire-880). We have configured 2 domains on the same box, one for development and other for staging environment. Both are running normally fine.
Couple of days back the managed server of development domain crashed sudenly. It generated a CORE file and a log file with following details:
Can anyone tell me, what exactly happened, and what would be the corrective / preventive action to be taken?
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : 10 occurred at PC=0xFE7E2D9C
Function=[Unknown. Nearest: ZIP_Lock+0x48]
Library=/opt/bea/wls811/jdk141_03/jre/lib/sparc/libzip.so
Current Java thread:
 at java.util.zip.ZipFile.getEntry(Native Method)
 at java.util.zip.ZipFile.getEntry(ZipFile.java:146)
 - locked <c13f7250> (a weblogic.utils.classloaders.ClasspathClassFinder$ZipFileWrapper)
 at weblogic.servlet.internal.WarClassFinder.getSource(WarClassFinder.java:236)
 at weblogic.servlet.internal.WebAppServletContext.getSource(WebAppServletContext.java:4402)
 at weblogic.servlet.internal.WebAppServletContext.getResourceAsSource(WebAppServletContext.java:5986)
 at weblogic.servlet.FileServlet.findSource(FileServlet.java:273)
 at weblogic.servlet.FileServlet.service(FileServlet.java:186)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
 at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
 at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
Dynamic libraries:
0x10000 /opt/bea/wls811/jdk141_03/bin/java
0xff350000 /usr/lib/libthread.so.1
0xff340000 /usr/lib/libdl.so.1
0xff200000 /usr/lib/libc.so.1
0xff390000 /usr/platform/SUNW,Sun-Fire-880/lib/libc_psr.so.1
0xfe000000 /opt/bea/wls811/jdk141_03/jre/lib/sparc/client/libjvm.so
0xff2d0000 /usr/lib/libCrun.so.1
0xff1e0000 /usr/lib/libsocket.so.1
0xff100000 /usr/lib/libnsl.so.1
0xff0d0000 /usr/lib/libm.so.1
0xff1c0000 /usr/lib/libmp.so.2
0xff090000 /opt/bea/wls811/jdk141_03/jre/lib/sparc/native_threads/libhpi.so
0xff060000 /opt/bea/wls811/jdk141_03/jre/lib/sparc/libverify.so
0xff020000 /opt/bea/wls811/jdk141_03/jre/lib/sparc/libjava.so
0xfe7e0000 /opt/bea/wls811/jdk141_03/jre/lib/sparc/libzip.so
0xfa050000 /opt/bea/wls811/jdk141_03/jre/lib/sparc/libnet.so
0xfa110000 /opt/bea/wls811/weblogic81/server/lib/solaris/libstackdump.so
0xfa030000 /opt/bea/wls811/weblogic81/server/lib/solaris/libmuxer.so
0xfa010000 /usr/ucblib/libucb.so.1
0xb9fb0000 /usr/lib/libresolv.so.2
0xb9e40000 /usr/lib/libelf.so.1
0xb9e20000 /opt/bea/wls811/jdk141_03/jre/lib/sparc/libnio.so
0xb9d20000 /usr/lib/librt.so.1
0xb9c10000 /usr/lib/libaio.so.1
0xb9b60000 /opt/bea/wls811/jdk141_03/jre/lib/sparc/libioser12.so
0xaec80000 /opt/bea/wls811/jdk141_03/jre/lib/sparc/libawt.so
0xaec00000 /opt/bea/wls811/jdk141_03/jre/lib/sparc/libmlib_image.so
0xb1490000 /opt/bea/wls811/jdk141_03/jre/lib/sparc/motif21/libmawt.so
0xae980000 /usr/dt/lib/libXm.so.4
0xaee10000 /usr/openwin/lib/libXt.so.4
0xb3890000 /usr/openwin/lib/libXext.so.0
0xb32e0000 /usr/openwin/lib/libXtst.so.1
0xae880000 /usr/openwin/lib/libX11.so.4
0xb10a0000 /usr/openwin/lib/libdps.so.5
0xb2e60000 /usr/openwin/lib/libSM.so.6
0xb16d0000 /usr/openwin/lib/libICE.so.6
Local Time = Thu Sep 9 17:56:49 2004
Elapsed Time = 520313
# The exception above was detected in native code outside the VM
# Java VM: Java HotSpot(TM) Client VM (1.4.1_03-b02 mixed mode)
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+

WLS 8.1SP2 can not be upgraded directly to WLS8.1 SP6.
The existing domain should be at WLS 8.1 SP4 atleast so that it can be upgraded to WLS 8.1 SP6.
The link:
http://commerce.bea.com/
Has be decommissioned and now in order to download the upgrade installers and WLS service pack versions you should have a Support ID which is required to create a login to metalink.oracle.com .
Then You can follow the following:
Login to: https://Metalink.oracle.com
Go to tab: Patches & Updates
Quick Links to: Latest Patchsets, Mini Packs and Maintenance Packs
Patch Bundles for Individual Products or Components
Select BEA Weblogic Platform
Select the WebLogic Main version and SP version
Then you should see the download screen.
Thanks,
Sandeep

Weblogic server 7.0 sp2 - servlet deployment

Hi,
Is there any way that i can delpoy a servlet with out context root name ?
I am using weblogic 7.0 sp2.
for eg. if i deply a war say "example.war"
then it works only if i refer http://hostname:7001/example/servletClass. I need
to refer like
http://hostname:7001/servletClass.
Is there any to deploy as a root servlet with out contxt root name ?
Thanks

"Bala" <[email protected]> wrote:
>
Hi Govind,
To add what Selva said, you can also configure <context-root>/</context-root>
parameter in weblogic.xml DD file. But you can have only one application
as the
default application for every WLS instance.
Bala
"Selvamohan Neethiraj" <[email protected]> wrote:
Make the example application as the default Web application in the server.
Thanks,
Selva-
"Govind" <[email protected]> wrote in message
news:3f96e951$[email protected]..
Hi,
Is there any way that i can delpoy a servlet with out context rootname ?
I am using weblogic 7.0 sp2.
for eg. if i deply a war say "example.war"
then it works only if i refer http://hostname:7001/example/servletClass.
I need
to refer like
http://hostname:7001/servletClass.
Is there any to deploy as a root servlet with out contxt root name?
Thanks

Deploying MDB on WebLogic server 8.1 (SP2) with Tibco JMS

Hi,
 I am currently facing problems to deploy and run my MDB on weblogic connecting it to Tibco JMS as the foreign jms server.
 
 My ejb-jar.xml:
 
 <message-driven>
 <ejb-name>DeAMMsgFactors</ejb-name>
 <ejb-class>com.db.deam.mdb.DeAMMsgFactors</ejb-class>
 <transaction-type>Container</transaction-type>
 <message-driven-destination>
 <destination-type>javax.jms.Topic</destination-type>
 </message-driven-destination>
 </message-driven>
 </enterprise-beans>
 <assembly-descriptor>
 <security-role>
 <role-name>soiadmin</role-name>
 </security-role>
 </assembly-descriptor>
 
 weblogic-ejb-jar.xml:
 
 <weblogic-enterprise-bean>
 <ejb-name>DeAMMsgFactors</ejb-name>
 <message-driven-descriptor>
 <pool>
 <max-beans-in-free-pool>20</max-beans-in-free-pool>
 <initial-beans-in-free-pool>10</initial-beans-in-free-pool>
 </pool>
 <destination-jndi-name>WLFactorsTopic</destination-jndi-name>
 <connection-factory-jndi-name>WLFactorsCF</connection-factory-jndi-name>
 <jms-polling-interval-seconds>10</jms-polling-interval-seconds>
 </message-driven-descriptor>
 <transaction-descriptor>
 <trans-timeout-seconds>100000</trans-timeout-seconds>
 </transaction-descriptor>
 </weblogic-enterprise-bean>
 <security-role-assignment>
 <role-name>soiadmin</role-name>
 <principal-name>jmsusername</principal-name>
 </security-role-assignment>
 
 Error:
 weblogic.ejb20.WLDeploymentException: [EJB:011014]The Message-Driven EJB failed while creating a JMS Connection. The err
 or was:
 javax.jms.JMSSecurityException: invalid name or password.
 javax.jms.JMSSecurityException: invalid name or password
 at com.tibco.tibjms.Tibjmsx.buildException(Tibjmsx.java:395)
 at com.tibco.tibjms.TibjmsConnection._create(TibjmsConnection.java:581)
 at com.tibco.tibjms.TibjmsConnection.<init>(TibjmsConnection.java:1743)
 at com.tibco.tibjms.TibjmsTopicConnection.<init>(TibjmsTopicConnection.java:35)
 at com.tibco.tibjms.TibjmsxCFImpl._createImpl(TibjmsxCFImpl.java:92)
 at com.tibco.tibjms.TibjmsxCFImpl._createConnection(TibjmsxCFImpl.java:121)
 at com.tibco.tibjms.TibjmsTopicConnectionFactory.createTopicConnection(TibjmsTopicConnectionFactory.java:66)
 at weblogic.ejb20.internal.JMSConnectionPoller.getConnection(JMSConnectionPoller.java:607)
 at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1783)
 at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1087)
 at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:970)
 at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
 at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
 at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
 at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:50)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
 at weblogic.ejb20.internal.JMSConnectionPoller.getConnection(JMSConnectionPoller.java:638)
 at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1783)
 at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1087)
 at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:970)
 at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
 at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
 at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
 at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:50)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
 [JMSConnectionPoller] : ** Connect attempt for: WLFactorsTopic was: unsuccessful
 
 Any help would be appreciated.
 
 Thanks, 
 Kiran Kumar MV.

I was able to use MDB to receive msg from a Tibco JMS queue. This is what you have to do: using WL console,
 - set up a foreign JMS Server. Make sure you specify the following correctly: jndi initial context factory (tibjms class), tibjms server url, username/password
 - create a foreign connection factory (if you are using CMT, make sure you create a XA compliant connection factory in Tibco JMS server). It seems that you have to specify URL again when creating XA connection factory in Tibjms.
 - create a foreign destination (queue/topic)
 In ejb-jar.xml and weblogic-ejb-jar.xml,
 - use resource-ref (wrapper) to specify the foreign connection factory
 - use resource-env-ref to specify the foreign destination.
 - In MDB ejb-jar.xml, specify destination-jndi-name and connection-factory-jndi-name.
 See Message Driven Beans chapter in Programming WebLogic EJB doc.
 Good luck.

Weblogic 6.1 server upgrade from SP2 to SP3

Hi All
We have weblogic server 6.1 SP2 installed on the solaris machine. Now we
have to upgrade our weblogic server 6.1 SP3. We also have downloaded the installable.
But that installable seems to over-write the previous weblogic server & installs
the server afresh. Is there any patch kinda thing available which allows me to
upgrade from SP2 to SP3 ? I don't want a fresh new install of SP3 server.
thanks in advance
-Kiran Rane

Upgrade installer from SP2 to SP3 is only available for paid BEA
customers. You need a login at http://support.bea.com
Kumar
kiran rane wrote:
Hi All
We have weblogic server 6.1 SP2 installed on the solaris machine. Now we
have to upgrade our weblogic server 6.1 SP3. We also have downloaded the installable.
But that installable seems to over-write the previous weblogic server & installs
the server afresh. Is there any patch kinda thing available which allows me to
upgrade from SP2 to SP3 ? I don't want a fresh new install of SP3 server.
thanks in advance
-Kiran Rane

Can't start weblogic server using Ant

Hello,
I can't start the WL Portal after installation.
On a Windows 2000 Server SP2 : - I installed WebLogic Server 6.1 SP2 with the examples
- I installed WebLogic Portal 4.0 SP2 (giving the same password as during the WL
Server installation) -I installed EBCC 4.0 SP2 .
I updated the license with UpdateLicense.cmd
Now If I run - run the default WL server, both from the menu and as a service -
enter the WL server console (on port 7001) - run the EBCC .
When I try to start the WL Portal, from the program menu I am able to start the
WP server properly , But I I try to start it from an ant wlrun then I get the error
an IllegalAccessError (with the same password I gave during installation and I use
to enter the server console): The WebLogic Server did not start up properly. Exception
raised: java.lang.IllegalAccessError: try to access method weblogic/management/internal/Helper.preloadMBeanInfos()V
from class weblogic/management/Admin at weblogic.management.Admin.initialize(Admin.java:210)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362) at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35) Reason: Fatal initialization exception
Any idea ?

Hi VG,
thank u a lot for ur answer. But there are no files at the Admin Server boot.properties path.
and at the BI Server boot.properties path there is no security folder. Do u have any idea why i cant found anything at this directions ? Also I tried again the command "./startWeblogic.sh " and get a new error message which I post below. I am rlly worry about this. Is there maybe a way to reset the OBIEE and undo all changes ?
<Oct 30, 2013 10:00:47 AM CET> <Warning> <EJB> <BEA-010001> <While deploying EJB 'AsyncAdminService_AsyncRequestProcessorMDB', class oracle.j2ee.ws.server.jaxws.AsyncRequestProcessorMDB was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Oct 30, 2013 10:00:47 AM CET> <Warning> <EJB> <BEA-010001> <While deploying EJB 'AsyncAdminService_AsyncResponseProcessorMDB', class oracle.j2ee.ws.server.jaxws.AsyncResponseProcessorMDB was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Oct 30, 2013 10:00:48 AM CET> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application em is not versioned.>
^C<Oct 30, 2013 10:39:50 AM CET> <Notice> <WebLogicServer> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>
<Oct 30, 2013 10:39:50 AM CET> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>>
<Oct 30, 2013 10:39:50 AM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

Problem in starting weblogic server as proxy

I am using weblogic server as Proxy to forward the requests to weblogic cluster.
When i bring up the proxy, it works fine, but when i try to access the application deployed in cluster through Proxy, the proxy server crashes with the follwoing error.
I am Pasting my complete logs below.
Setting JVM memory params for server IRISProxy
Using server IRISProxy-specfic java memory arguments: -Xms32m -Xmx200m -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=80 -XX:MaxPermSize=128m -XX:+DisableExplicitGC -XX:NewRatio=4
WLS Production Mode=true
./startWebLogic.sh[68]: B: not found.
maxfiles=8192
CLASSPATH=/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/CR211812_81sp4.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/CR235145_81sp4.jar:/home/weblogic/bea_wli/weblogic81/common/lib/CR224719_81sp2.jar:/home/weblogic/bea_wli/weblogic81/common/lib/CR137449_81sp2.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic_knex_patch.jar:/home/weblogic/bea_wli/weblogic81/common/lib/log4j.jar:/home/weblogic/bea_wli/weblogic81/server/lib/debugging.jar:/home/weblogic/bea_wli/weblogic81/server/lib/knex.jar:/home/weblogic/bea_wli/weblogic81/javelin/lib/javelin.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wlw-lang.jar:/home/weblogic/bea_wli/jdk141_05/lib/tools.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic_sp.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic.jar:/home/weblogic/bea_wli/weblogic81/server/lib/ojdbc14.jar:/home/weblogic/bea_wli/weblogic81/server/lib/ant/ant.jar:/home/weblogic/bea_wli/jdk141_05/jre/lib/rt.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/agent_tools_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-Admin:/opt/jes/policy_agent/IdentityServer/j2ee_agents/locale:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_agent_sdk_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_agent_filter_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_sdk.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_services.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_sso_provider.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_logging.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_wl70_agent_2_1.jar:::::/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/SecurityClient-v1.0.7.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/Log4JInitServlet.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/log4j_IRIS-1.2.4.jar:::/home/weblogic/bea_wli/weblogic81/server/lib/webserviceclient.jar:/home/weblogic/bea_wli/weblogic81/server/lib/webserviceclient+ssl.jar:/home/weblogic/bea_wli/weblogic81/server/lib/xbean.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wlxbean.jar:/home/weblogic/bea_wli/weblogic81/server/lib/xqrl.jar:/home/weblogic/bea_wli/weblogic81/server/lib/netui/netui-compiler.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wli.jar:/home/weblogic/bea_wli/weblogic81/server/lib/fop.jar:/home/weblogic/bea_wli/weblogic81/integration/adapters/sample/lib/sample-eis.jar:
PATH=/home/weblogic/bea_wli/weblogic81/server/bin:/home/weblogic/bea_wli/weblogic81/server/bin:/home/weblogic/bea_wli/jdk141_05/jre/bin:/home/weblogic/bea_wli/jdk141_05/bin:/usr/sbin:/usr/bin:/usr/ccs/bin:/usr/contrib/bin:/usr/local/bin:/opt/hparray/bin:/opt/nettladm/bin:/opt/upgrade/bin:/opt/fcms/bin:/opt/pd/bin:/usr/bin/X11:/usr/contrib/bin/X11:/opt/resmon/bin:/opt/perf/bin:/opt/prm/bin:/opt/mx/bin:/opt/gnome/bin:/opt/wbem/bin:/opt/wbem/sbin:/opt/ignite/bin:/opt/graphics/common/bin:/usr/sbin/diag/contrib:/opt/sec_mgmt/spc/bin:/opt/networker/bin:/opt/sec_mgmt/bastille/bin:/opt/hpnpl//bin:/opt/mozilla:/opt/OV/bin/OpC:/opt/OV/bin:/sbin:/home/root:/util:/home/weblogic/bea_wli/jdk141_05/jre/bin:/usr/local/bin:/usr/local/sbin:.
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://hostname:port/console *
starting weblogic with Java version:
java version "1.4.1.05"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1.05-030910-01:23)
Java HotSpot(TM) Server VM (build 1.4.1 1.4.1.05-030910-02:49-PA_RISC2.0 PA2.0, mixed mode)
Starting WLS with line:
/home/weblogic/bea_wli/jdk141_05/bin/java -server -Xms32m -Xmx200m -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=80 -XX:MaxPermSize=128m -XX:+DisableExplicitGC -XX:NewRatio=4 -Dweblogic.security.SSL.trustedCAKeyStore=/home/weblogic/bea_wli/weblogic81/server/lib/cacerts -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dapp.config.dir=/home/weblogic/upload/appsvcdomain/IRIS/config -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dapp.config.dir=/home/weblogic/upload/appsvcdomain/IRIS/config -da -Dplatform.home=/home/weblogic/bea_wli/weblogic81 -Dwls.home=/home/weblogic/bea_wli/weblogic81/server -Dwli.home=/home/weblogic/bea_wli/weblogic81/integration -Dlog4j.configuration=file:/home/weblogic/bea_wli/weblogic81/common/lib/workshopLogCfg.xml -Dweblogic.management.discover=false -Dweblogic.management.server=t3://170.63.142.14:8100 -Dweblogic.security.SSL.ignoreHostnameVerify=false -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=true -Dweblogic.security.SSL.trustedCAKeyStore=/home/weblogic/bea_wli/weblogic81/server/lib/cacerts -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dweblogic.Name=IRISProxy -Dweblogic.ProductionModeEnabled=true -Djava.security.policy=/home/weblogic/bea_wli/weblogic81/server/lib/weblogic.policy weblogic.Server
Bad level value for property: com.iplanet.services.debug.level
Bad level value for property: com.sun.identity.agents.logging.level
Bad level value for property: com.sun.am.policy.amFilter.audit.level
<Mar 15, 2006 3:40:33 PM EST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.4.1 1.4.1.05-030910-02:49-PA_RISC2.0 PA2.0 from Hewlett-Packard Company>
<Mar 15, 2006 3:40:34 PM EST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://170.63.142.14:8100 to check if there exists a running admin server at this URL.>
<Mar 15, 2006 3:40:34 PM EST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Mar 15, 2006 3:40:35 PM EST> <Warning> <Configuration Management> <BEA-150033> <The managed server should not be started in development mode.>
<Mar 15, 2006 3:40:35 PM EST> <Info> <Management> <BEA-141107> <Version: WebLogic Temporary Patch for CR211812 01/23/2005 22:15:39
WebLogic Temporary Patch for CR235145 08/16/2005 11:44:59
WebLogic Temporary Patch for CR224719 04/29/2005 16:40:35
WebLogic Temporary Patch for CR137449 02/24/2004 10:48:06
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Integration 8.1 SP2 Thu Dec 11 22:07:14 PST 2003 148883>
<Mar 15, 2006 3:40:35 PM EST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://170.63.142.14:8100 to retrieve the initial configuration.>
<Mar 15, 2006 3:40:46 PM EST> <Notice> <Log Management> <BEA-170019> <The server log file /home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/IRISProxy/IRISProxy.log is opened. All server side log events will be written to this file.>
<Mar 15, 2006 3:41:29 PM EST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Mar 15, 2006 3:41:29 PM EST> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "IRISProxy" for domain "AppSvcDomain">
<Mar 15, 2006 3:41:57 PM EST> <Warning> <HTTP> <BEA-101299> <The servlet-mapping for servlet-name "HttpClusterServlet" will override the default mapping for *.jsp. This can lead to a show code vulnerability.>
<Mar 15, 2006 3:42:06 PM EST> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias irisqa from the jks keystore file /home/weblogic/bea_wli/weblogic81/server/lib/trustIdentityKeys/iris_qa.jks.>
<Mar 15, 2006 3:42:06 PM EST> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias irisqa from the jks keystore file /home/weblogic/bea_wli/weblogic81/server/lib/trustIdentityKeys/iris_qa.jks.>
<Mar 15, 2006 3:42:08 PM EST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /home/weblogic/bea_wli/jdk141_05/jre/lib/security/cacerts.>
<Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "IRISProxy" for domain "AppSvcDomain" running in Production Mode>
<Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 7001, ip address 170.63.142.29>
<Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000355> <Thread "SSLListenThread.Default" listening on port 443, ip address 170.63.142.29>
<Mar 15, 2006 5:02:26 PM EST> <Emergency> <WebLogicServer> <BEA-000209> <ListenThread.run() failed: java.lang.NoSuchMethodError: com.certicom.tls.interfaceimpl.TLSSystem.createServer(Ljavax/net/ssl/SSLSocket;Ljava/io/InputStream;Ljava/io/OutputStream;Ljava/io/Serializable;)Lcom/certicom/tls/TLSConnection;
java.lang.NoSuchMethodError: com.certicom.tls.interfaceimpl.TLSSystem.createServer(Ljavax/net/ssl/SSLSocket;Ljava/io/InputStream;Ljava/io/OutputStream;Ljava/io/Serializable;)Lcom/certicom/tls/TLSConnection;
 at javax.net.ssl.impl.SSLSocketImpl.resetConnection(Unknown Source)
 at javax.net.ssl.impl.SSLServerSocketImpl.accept(Unknown Source)
 at weblogic.t3.srvr.ListenThread.accept(ListenThread.java:739)
 at weblogic.t3.srvr.ListenThread.run(ListenThread.java:292)
>
<Mar 15, 2006 5:02:26 PM EST> <Emergency> <WebLogicServer> <BEA-000210> <The WebLogic Server is no longer listening for connections.>
<Mar 15, 2006 5:02:26 PM EST> <Alert> <WebLogicServer> <BEA-000218> <Server shutdown has been requested by <WLS Kernel>>
<Mar 15, 2006 5:02:26 PM EST> <Notice> <WebLogicServer> <BEA-000353> <Thread "ListenThread.Default" stopped listening on port 7001, ip address 170.63.142.29>
<Mar 15, 2006 5:02:26 PM EST> <Notice> <WebLogicServer> <BEA-000353> <Thread "SSLListenThread.Default" stopped listening on port 443, ip address 170.63.142.29>
<Mar 15, 2006 5:02:26 PM EST> <Alert> <WebLogicServer> <BEA-000219> <The shutdown sequence has been initiated.>
Can someone help me in solving this problem
Thanks
Kris

I solved this problem by commenting the 8.1 SP4 patches i applied in 8.1 SP2
WebLogic Temporary Patch for CR211812
WebLogic Temporary Patch for CR235145
Once i commented the above patches in the CLASSPATH.
The issue is resolved.

Bea weblogic server

My weblogic server is not getting started... software is installed succesfully....

a picture from processor load
"Steffen Schenk" <[email protected]> wrote:
>
Hey,
we have a problem with the new release of WebLogic Server 8.1 SP2.
For a while everything is going fine but after a few hours the server
is too busy
to process the requests. During the analyzing of weblogic parameters
we found
in the monitoring that the number of daemon threads is really high.
We have set the thread count for processing the requests to 30 and in
some cases
we have a queue length about 100. The daemon threads were counted with
over 450?
For what are the daemon threads used?
Is it necessary to have so many?
Another thing was that the JVM (JRockit) Processor Load was very high
often up
to 100 percent, but the All processors avarage load is under 50 percent.
Is there
a possibility to change this settings.
Must I increase the thread count?
Bye
Steffen

WebLogic Server 7.0 and MS SQL Server 2000

Hi,
I'm trying to create a connection pool in WebLogic Server 7.0 for MS SQL Server
2000, but I always get the following error message:
<Error> <JDBC> <001060> <Cannot startup connection pool "mcp-ConnectionPool
" weblogic.common.ResourceException: weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: Login failed for user 'JavaUser'. Severity 14, State 1,
Procedure 'null null'
, Line 0 Unable to connect, please check your server's version and availability.
at weblogic.jdbc.mssqlserver4.TdsStatement.microsoftLogin(TdsStatement.java:2823)
at weblogic.jdbc.mssqlserver4.MicrosoftConnection.beginLogin(MicrosoftConnection.java:44)
When I try to connect to the database with dbping, I get the following error:
Error encountered:
java.sql.SQLException: Login failed for user 'JavaUser'. Severity 14, State 1,
Procedure 'null null'
, Line 0 Unable to connect, please check your server's version and availability.
I'm able to connect to the same database with WebLogic Server 6.0 (SP2) using
the exact same settings. Does anyone have an idea of what is wrong here? Do I
need an updated driver?
Here is an extract from my config file:
<JDBCConnectionPool CapacityIncrement="5" DriverName="weblogic.jdbc.mssqlserver4.Driver"
LoginDelaySeconds="5" MaxCapacity="20" Name="mcp-ConnectionPool" Password="{3DES}A4GocdgagGc="
Properties="user=JavaUser" Targets="myserver"
Any help would be greatly appreciated,
Koen

Hi. This is very odd. Would you please try a simple standalone program,
such as below? Tell me what it does in both environments.
Joe
import java.sql.*;
import java.util.*;
public class foo
public Connection connection;
public static void main(String args[])
throws Exception
Connection c = null;
try
Properties properties = new Properties();
properties.put("user", "sa"); // change for your properties...
properties.put("password", "");
properties.put("server", "QA75");
Class.forName("weblogic.jdbc.mssqlserver4.Driver").newInstance();
c = DriverManager.getConnection("jdbc:weblogic:mssqlserver4", properties);
System.out.println("got a connection.");
catch(Exception exception1)
exception1.printStackTrace();
finally
if (c != null)
try { c.close(); } catch(Exception ex) {}
Koen Van hamme wrote:
Hi,
I'm trying to create a connection pool in WebLogic Server 7.0 for MS SQL Server
2000, but I always get the following error message:
<Error> <JDBC> <001060> <Cannot startup connection pool "mcp-ConnectionPool
" weblogic.common.ResourceException: weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: Login failed for user 'JavaUser'. Severity 14, State 1,
Procedure 'null null'
, Line 0 Unable to connect, please check your server's version and availability.
at weblogic.jdbc.mssqlserver4.TdsStatement.microsoftLogin(TdsStatement.java:2823)
at weblogic.jdbc.mssqlserver4.MicrosoftConnection.beginLogin(MicrosoftConnection.java:44)
When I try to connect to the database with dbping, I get the following error:
Error encountered:
java.sql.SQLException: Login failed for user 'JavaUser'. Severity 14, State 1,
Procedure 'null null'
, Line 0 Unable to connect, please check your server's version and availability.
I'm able to connect to the same database with WebLogic Server 6.0 (SP2) using
the exact same settings. Does anyone have an idea of what is wrong here? Do I
need an updated driver?
Here is an extract from my config file:
<JDBCConnectionPool CapacityIncrement="5" DriverName="weblogic.jdbc.mssqlserver4.Driver"
LoginDelaySeconds="5" MaxCapacity="20" Name="mcp-ConnectionPool" Password="{3DES}A4GocdgagGc="
Properties="user=JavaUser" Targets="myserver"
Any help would be greatly appreciated,
Koen

Weblogic Server 7.0 - CipherIsExportable

Hi,
I need a small help. In weblogic7.0 when I set Ciphersuites="TLS_RSA_WITH_AES_128_CBC_SHA" at config.xml file, the server console shows :
<Alert> <WebLogicServer> <000297> <Inconsistent security configuration, java.lang.NullPointerException>
java.lang.NullPointerException at weblogic.security.utils.SSLCipherUtility.getCipherIsExportable(SSLCip
herUtility.java:74)
at weblogic.t3.srvr.SSLListenThread.<init>(SSLListenThread.java:265)
at weblogic.t3.srvr.SSLListenThread.<init>(SSLListenThread.java:122)
at weblogic.t3.srvr.T3Srvr.initializeListenThreads(T3Srvr.java:1548)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:891)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:300)
at weblogic.Server.main(Server.java:32)
The SSL port is not starting ..
My Weblogic License allows full strength (domestic) SSL
Thanks in advance,
Pallab

Here's how to find out if your version of weblogic supports a particular ssl cipher suite:
import weblogic.security.SSL.SSLSocketFactory;
public class Test {
 public static void main(String [] args) {
 SSLSocketFactory f =
 (SSLSocketFactory) SSLSocketFactory.getDefaultJSSE();
 String [] suites = f.getSupportedCipherSuites();
 for (int i = 0; i < suites.length; i++) {
 System.out.println(suites);
You'll need to compile this against your weblogic.jar file.
(In WL7, its in <bea dir>/weblogic700/server/lib)
I ran it against my Weblogic Server 7.0 SP2 and it did not contain TLS_RSA_WITH_AES_128_CBC_SHA.
But it did appear in the list supported list for my Weblogic 8.1 jar.
So, Im not sure what you can do other than upgrade to 8.1. Maybe BEA has
an updated jar you can download without upgrading...

Problem installing weblogic server 7.0 in Mandrake Linux 10.1

hi
i am very new to Mandrake Linux ..i have installed Mandrake Linux 10.1 in my machine ...the problem is that when i try i to install weblogic server 7.0 it gives some error
** Error during execution, error code = 11
my machine spec
* 512MB RAM
* 40GB HDD
* P4 2.8GHZ
can any one help me..
the weblogic server i downloaded from bea site its version is weblogic server 7.0 with jrockit (sp6)
regards
babu

Hi,
first of all, unfortunately, WebLogic Server is not supported under Mandrivia (use the right name ;-) ), so you should use Novell Suse or Redhat AS, check this list
Anyway, error code 11 should be related to permission issues, so you should check that the user you are using is allowed to write under the installation directory and under /var/log/
Could you kindly post the log messages?
Regards.
Antenore Gatta
Middleware Specialist
Hequa S.r.l
C.so Buenos Aires 77
20124 Milano
http://www.Hequa.it
Tel +39(0)267493078
Fax +39(0)267493079
Mobile +39 3481537897
______________________________________

Weblogic server 8.1 SP2 to SP6 ugrade

Similar Messages

Maybe you are looking for