Re: Starting WLS 5.1 SP9 w/ JDK 1.3

SP9 ships a new (compatible with JDK 1.3) version of wlconfig & wlserver.exe
Pls see SP9 release notes.
kumar
James Nuzzi wrote:
Hello,
I have seen a lot of posts about this error, but I cannot find a solution to
my problem. I am running WLS 5.1 SP9 with JDK 1.3 on W2K SP1. I can start
WLS fine using StartWeblogic.cmd but I cannot start it using wlserver.exe
(Start/Programs/Weblogic 5.1.0/Weblogic Server). Here is the error:
Java Ver: 1.3 C:\jdk1.3
"DumpThreads" is not defined.
Weblogic server can not be run in your jvm.
loadIt: InitFunctions returned error (2)
The Windows registry is misconfigured
for the WebLogic Server
Can't start WebLogic Server: (Can't start Java VM) err=0x2000001
Any help on this would be appreciated.
Thank You

I am using the new version of wlconfig & wlserver.exe that came with SP9.
Are there any new settings that I need to set wuth wlconfig.exe?
Thanks
"Kumar Allamraju" <[email protected]> wrote in message
news:[email protected]..
SP9 ships a new (compatible with JDK 1.3) version of wlconfig &wlserver.exe
Pls see SP9 release notes.
kumar
James Nuzzi wrote:
Hello,
I have seen a lot of posts about this error, but I cannot find a
solution to
my problem. I am running WLS 5.1 SP9 with JDK 1.3 on W2K SP1. I canstart
WLS fine using StartWeblogic.cmd but I cannot start it usingwlserver.exe
(Start/Programs/Weblogic 5.1.0/Weblogic Server). Here is the error:
Java Ver: 1.3 C:\jdk1.3
"DumpThreads" is not defined.
Weblogic server can not be run in your jvm.
loadIt: InitFunctions returned error (2)
The Windows registry is misconfigured
for the WebLogic Server
Can't start WebLogic Server: (Can't start Java VM) err=0x2000001
Any help on this would be appreciated.
Thank You

Similar Messages

Starting WLS 5.1 SP9 w/ JDK 1.3

Hello,
I have seen a lot of posts about this error, but I cannot find a solution to
my problem. I am running WLS 5.1 SP9 with JDK 1.3 on W2K SP1. I can start
WLS fine using StartWeblogic.cmd but I cannot start it using wlserver.exe
(Start/Programs/Weblogic 5.1.0/Weblogic Server). Here is the error:
Java Ver: 1.3 C:\jdk1.3
"DumpThreads" is not defined.
Weblogic server can not be run in your jvm.
loadIt: InitFunctions returned error (2)
The Windows registry is misconfigured
for the WebLogic Server
Can't start WebLogic Server: (Can't start Java VM) err=0x2000001
Any help on this would be appreciated.
Thank You

After applying SP9, we are getting this exact message also. I see nothing
relevant in the "release" notes. It is interesting that you can start the
server up using the startWebLogic.cmd script. It is the wlserver.exe
program that is choking.
"James Nuzzi" <[email protected]> wrote in message
news:3addae50$[email protected]..
Hello,
I have seen a lot of posts about this error, but I cannot find a solutionto
my problem. I am running WLS 5.1 SP9 with JDK 1.3 on W2K SP1. I canstart
WLS fine using StartWeblogic.cmd but I cannot start it using wlserver.exe
(Start/Programs/Weblogic 5.1.0/Weblogic Server). Here is the error:
Java Ver: 1.3 C:\jdk1.3
"DumpThreads" is not defined.
Weblogic server can not be run in your jvm.
loadIt: InitFunctions returned error (2)
The Windows registry is misconfigured
for the WebLogic Server
Can't start WebLogic Server: (Can't start Java VM) err=0x2000001
Any help on this would be appreciated.
Thank You

WLS 6.1 SP2 and JDK 1.4.0

In configuring our WLS 6.1 SP2 to run on the released JDK 1.4 and starting the
server, most things seemed to start fine except for our ObjectIDFactorySession
EJB. It cacked when it tried to create a bean in the free pool. Stack trace
below. I know this is not supported, but can anyone shed some light?
####<Feb 15, 2002 3:05:03 PM EST> <Warning> <EJB> <023app11> <port7011server>
<main> <system> <> <010063> <The EJB: ObjectIDFactorySession had an <initial-beans-in-free-pool>
setting in its weblogic-ejb-jar.xml. An error occurred while creating these initial
bean instances. The error was:
nulljava.lang.ExceptionInInitializerError
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
     at java.lang.Class.newInstance0(Class.java:296)
     at java.lang.Class.newInstance(Class.java:249)
     at javax.rmi.CORBA.Util.createDelegateIfSpecified(Util.java:339)
     at javax.rmi.CORBA.Util.<clinit>(Util.java:51)
     at javax.rmi.PortableRemoteObject.createDelegateIfSpecified(PortableRemoteObject.java:179)
     at javax.rmi.PortableRemoteObject.<clinit>(PortableRemoteObject.java:58)
     at prototype.com.guardian.util.HomeFactory.createHome(HomeFactory.java:81)
     at prototype.com.guardian.util.HomeFactory.newHome(HomeFactory.java:49)
     at prototype.com.guardian.util.HomeFactory.newSession(HomeFactory.java:95)
     at prototype.com.guardian.fw.ObjectIDFactorySessionBean.ejbCreate(ObjectIDFactorySessionBean.java:31)
     at prototype.com.guardian.fw.ObjectIDFactorySessionBean_r4ogoq_Impl.ejbCreate(ObjectIDFactorySessionBean_r4ogoq_Impl.java:112)
     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:324)
     at weblogic.ejb20.pool.StatelessSessionPool.createBean(StatelessSessionPool.java:153)
     at weblogic.ejb20.pool.Pool.createInitialBeans(Pool.java:198)
     at weblogic.ejb20.pool.Pool.onAfterDeploy(Pool.java:177)
     at weblogic.ejb20.deployer.Deployer.runAfterDeploymentListeners(Deployer.java:1325)
     at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1013)
     at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
     at weblogic.j2ee.Application.addComponent(Application.java:163)
     at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
     at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:984)
     at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:971)
     at weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.java:956)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:648)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy65.addTarget(Unknown Source)
     at weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationManager.java:867)
     at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:966)
     at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:886)
     at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:802)
     at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:733)
     at weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:206)
     at weblogic.management.mbeans.custom.ApplicationManager.startAdminManager(ApplicationManager.java:278)
     at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:152)
     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:324)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy5.start(Unknown Source)
     at weblogic.management.Admin.startApplicationManager(Admin.java:1184)
     at weblogic.management.Admin.finish(Admin.java:590)
     at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
     at weblogic.Server.main(Server.java:35)
Caused by: java.lang.RuntimeException: could not find or instantiate any UtilDelegate
class
     at weblogic.iiop.UtilDelegateImpl.<clinit>(UtilDelegateImpl.java:73)
     ... 77 more
>

I've solved my own problem. I learned that there was a sp4 (let alone a
sp3) for WLS. Installed that and the problem went away. Sorry for the
noise.
-Phil
Philip Bower <[email protected]> wrote in
news:[email protected]:
When I try to deploy the struts-example.war or if I add the struts.jar
to any other web app I've created, I get this error when I start WLS
and it tries to deploy that war.
java.lang.StringIndexOutOfBoundsException
at weblogic.servlet.internal.WebAppHelper.resolveManifestName
(WebAppHelper.java:469)
I'm using version 1.1b3 of struts. I'm having no problems with
version 1.0.2 of struts.
I'm guessing its complaining about the manifest file in struts.jar,
but I don't understand why.
Here's my version info and the stack trace (my web app is called
findme in this example). Thanks in advance.
-Phil
Server BuildWebLogic Server 6.1 SP2 12/18/2001 11:13:46 #154529
All Server Product VersionsWebLogic Server 6.1 SP2 12/18/2001
11:13:46 #154529 WebLogic XML Module 6.1 SP2 12/18/2001 11:28:02
#154529
<Feb 11, 2003 7:45:25 AM EST> <Error> <J2EE> <Error deploying
application findme: Could not load findme>
<Feb 11, 2003 7:45:25 AM EST> <Error> <Management> <ApplicationManager
starting Config caught throwable
java.lang.reflect.UndeclaredThrowableException:
java.lang.StringIndexOutOfBoundsException: String index out of range:
-1
at java.lang.String.substring(String.java:1525)
at
weblogic.servlet.internal.WebAppHelper.resolveManifestName(WebAppHelper
.jav a:469)
at
weblogic.servlet.internal.WebAppHelper.extractClassFiles(WebAppHelper.j
ava: 234)
at
weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebApp
Serv letContext.java:3407)
at
weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServlet
Cont ext.java:3376)
at
weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContex
t.ja va:862)

Error while starting WLS server

Hi,
Am getting the below error
starting weblogic with Java version:
java version "1.6.0_20"
Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
Java HotSpot(TM) Client VM (build 16.3-b01, mixed mode, sharing)
Starting WLS with line:
C:\PROGRA~1\Java\JDK16~1.0_2\bin\java -client -Xms256m -Xmx512m -XX:CompileThr
eshold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m -Dweblogic.Name=myserver -Dja
<Jun 14, 2012 5:26:19 PM IST> <Info> <Management> <BEA-141107> <Version: WebLogi
c Server 10.3.6.0 Tue Nov 15 08:52:36 PST 2011 1441050 >
<Jun 14, 2012 5:26:19 PM IST> <Critical> <WebLogicServer> <BEA-000362>
<Server f ailed. Reason: [Management:141266]Parsing Failure in config.xml: java.lang.IllegalArgumentException: The provider Provider already exists>
<Jun 14, 2012 5:26:19 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to FAILED>
<Jun 14, 2012 5:26:19 PM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Jun 14, 2012 5:26:19 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to FORCE_SHUTTING_DOWN>
This is very urgent and I need help to solve this.
Please reply back soon

this is the config.xml
<?xml version='1.0' encoding='UTF-8'?>
<domain xmlns="http://xmlns.oracle.com/weblogic/domain" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/security/xacml http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator/1.0/passwordvalidator.xsd http://xmlns.oracle.com/weblogic/domain http://xmlns.oracle.com/weblogic/1.0/domain.xsd http://xmlns.oracle.com/weblogic/security http://xmlns.oracle.com/weblogic/1.0/security.xsd http://xmlns.oracle.com/weblogic/security/wls http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.xsd">
<name>mydomain</name>
<domain-version>10.3.6.0</domain-version>
<security-configuration>
<name>mydomain</name>
<realm>
<sec:authentication-provider xsi:type="wls:default-authenticatorType"></sec:authentication-provider>
<sec:authentication-provider xsi:type="wls:default-identity-asserterType">
<sec:active-type>AuthenticatedUser</sec:active-type>
</sec:authentication-provider>
<sec:role-mapper xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
<sec:authorizer xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
<sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
<sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
<sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
<sec:name>myrealm</sec:name>
<sec:password-validator xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator" xsi:type="pas:system-password-validatorType">
<sec:name>SystemPasswordValidator</sec:name>
<pas:min-password-length>8</pas:min-password-length>
<pas:min-numeric-or-special-characters>1</pas:min-numeric-or-special-characters>
</sec:password-validator>
</realm>
<default-realm>myrealm</default-realm>
<credential-encrypted>{AES}DO7UStBZljQz8xV6biUOFJqdK5gsj1D1riTUGbO7Il4FWYqlhurBQqPIDqAINVjswiUuNnqW6Fgh0Q5w4DUkQRmdVVHObsY/RXP7geTmt3Ps3eW3s/ucrlxdMYGzv8Y/</credential-encrypted>
<node-manager-username>weblogic</node-manager-username>
<node-manager-password-encrypted>{AES}+mvIGJfWsqWkZekqkwYV6gc9tsY7DPmRWa/avipt80U=</node-manager-password-encrypted>
</security-configuration>
<server>
<name>myserver</name>
<listen-address></listen-address>
</server>
<embedded-ldap>
<name>mydomain</name>
<credential-encrypted>{AES}yVDi5dwjQzQyCxCHXqjB4h3brKgkcLEgHP/3nu0yf81UC/t27TfkQuFjKl8cxm7r</credential-encrypted>
</embedded-ldap>
<configuration-version>10.3.6.0</configuration-version>
<app-deployment>
<name>demantra_new2</name>
<target>myserver</target>
<module-type>war</module-type>
<source-path>D:\Oracle_Demantra_Spectrum_122\Collaborator\demantra_new2.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<app-deployment>
<name>demantra_JUNE14</name>
<target>myserver</target>
<module-type>war</module-type>
<source-path>D:\Oracle_Demantra_Spectrum_122\Collaborator\demantra_JUNE14.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<library>
<name>api</name>
<target>myserver</target>
<module-type xsi:nil="true"></module-type>
<source-path>C:\Oracle\Middlewareforweblogic\wlserver_10.3\server\lib\api.jar</source-path>
<deployment-principal-name>api</deployment-principal-name>
<security-dd-model>DDOnly</security-dd-model>
</library>
<library>
<name>javax.servlet.jsp.jstl#[email protected]</name>
<target>myserver</target>
<module-type xsi:nil="true"></module-type>
<source-path>D:\Oracle_Demantra_Spectrum_122\Collaborator\Tomcat\lib\jstl-1.2.jar</source-path>
<deployment-principal-name>jstl</deployment-principal-name>
<security-dd-model>DDOnly</security-dd-model>
</library>
<library>
<name>jstl#[email protected]</name>
<target>myserver</target>
<module-type>war</module-type>
<source-path>C:\Oracle\Middlewareforweblogic\wlserver_10.3\common\deployable-libraries\jstl-1.2.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
</library>
<admin-server-name>myserver</admin-server-name>
<jdbc-system-resource>
<name>JDBC Data Source-0</name>
<target>myserver</target>
<descriptor-file-name>jdbc/JDBC_Data_Source-0-3407-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
</domain>
Edited by: Manikanda Prabhu on Jun 14, 2012 5:03 AM

Problem with start WLS

Peace!
I'm developing servlets that invoke ejb object under WLE.
I include in classpath for starting WLS 4 jar in udataobj of WLE.
When I try to start server there are problem and it doesn't start.
What do I include to run a client of EJB?
PS: I think that there are conflict problem between WLE classes and WLS
classes.
Thanks.

Giuseppe -
Are you using WLE 5.1? If no, I'd recommend you upgrade.
WLE 5.1 includes examples of how to access EJBs on the T-Engine from the
J-Engine, or WLS, and addresses some issues you may be encountering.
Will
Giuseppe Villanova wrote:
Peace!
I'm developing servlets that invoke ejb object under WLE.
I include in classpath for starting WLS 4 jar in udataobj of WLE.
When I try to start server there are problem and it doesn't start.
What do I include to run a client of EJB?
PS: I think that there are conflict problem between WLE classes and WLS
classes.
Thanks.

Platform Support for WLS 5.1 SP9 and / or WLS 6.x

When will BEA support WLPS with either WLS 5.1 SP9 or WLS 6.x?

Should have been more specific:
When will BEA support WLPS __3.2__ with either WLS 5.1 SP9 or WLS 6.x? The
docs say it currently only supports WLS 5.1 sp6/sp8, depending on platform.
Are there plans for BEA to support WLPS __3.5__ with WLS 5.1 SP9? The doc
says it currently only supports WLS 6.x
Jesus M. Salvo Jr. wrote:
>
When will BEA support WLPS with either WLS 5.1 SP9 or WLS 6.x?

How to start WLS in RedHat 6.2

Hi everyone,
Everytime when I try to start WLS in RedHat with the command -
./startWebLogic.sh in command line console,
an error - "Don't know how to set the shared library for Linux" is displyed.
Could anyone help me solve this problem at your earliest convenience sine
it is quite urgent to me to solve this problem?
Thanks in advance

Open startWebLogic.sh
look for label LINUX)
substitute the line with
LINUX | Linux)
and try again.
Marco.
Rex Law <[email protected]> wrote in message
news:[email protected]..
Hi everyone,
Everytime when I try to start WLS in RedHat with the command -
./startWebLogic.sh in command line console,
an error - "Don't know how to set the shared library for Linux" isdisplyed.
>
Could anyone help me solve this problem at your earliest conveniencesine
it is quite urgent to me to solve this problem?
Thanks in advance

Problems starting WLS on XP - Unable to bind to port

Hi
I recently changed my development environment from W2000 to XP.
Apparently everything works as before.
However, when I start WLS again shortly after stopping it (either by console or
CTRL^C) I get the following error
<01-10-2003 14:48:40 CEST> <Emergency> <WebLogicServer> <BEA-000351> <Unable to
create a server socket on Channel Default for port: 28041. j
ava.net.BindException: Address in use Perhaps another process is using port 28041.>
<01-10-2003 14:48:40 CEST> <Emergency> <Security> <BEA-090085> <Server failed
to bind to the configured port. The port may already be used b
y another process.>
<01-10-2003 14:48:40 CEST> <Emergency> <WebLogicServer> <BEA-000342> <Unable to
initialize the server: Server failed to bind to the requeste
d port. See preceeding log message for details.>
This situation times out after an unpredictable delay (5-20 min) - and I can restart
my WLS.
Does anybody know how to resolve this problem.
Regards
Peter

Hi Werner,
SYSLOG is UDP port 514. Normally this means that some other program is running and using port 514.
Some of the TFTP servers are also SYSLOG servers and will "listen" on this port.
You can see if port 514 is listening with Fabric Manager not running.
To find out what is using port 514:
(a)     Open a command prompt window. From Start / Run enter: cmd
(b)     From the command prompt enter: netstat -ano
(c)      Note the PID (process identifier) associated with the ports you are concerned about. (Also note the Local Address, Foreign Address, Protocol and State.)
(d)     Then do ctrl-alt-del to bring up the Windows Task Manager.
(e)     In Windows Task Manager, select the Processes tab.
(f)      Look for the PID you noted when you did the netstat in step (c). Look to left to the image name and that tells you which process has that PID.
- If you dont see a PID column, click on View / Select Columns. Make sure PID is selected. Click OK.
- Make sure Show processes from all users is selected.
Now you can see what process is using port 514. FM would be listed as javaw.exe ( java exec without a console window ).
Best regards,
Jim

How are duplicate parameters handled when starting WLS?

I was given some memory tuning suggestions for WLS and told to set them in $USER_MEM_ARGS. However, when I try to start the AdminServer I am getting an error "Invalid initial heap size: -Xms512m". This puzzles me because it looks like that was the original heap size. I am wondering if it is because the parameter appears twice.
So my question is, "If a parameter is used twice, is the first one used? the last one? or is it an error?"
Now to see if I can add an image. Guess not. Soooo... note -Xms=512m appears twice.
* 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 *
RRP Debugging...
$SERVER_NAME: AdminServer
$JAVA_VENDOR: Sun
$USER_MEM_ARGS: -Xms=512m -Xmx=512m -Xns=128m -d64 -XgcPrio:throughput -XXnoSystemGC -Djava.security.egd=file:/dev/../dev/urandom -XX:PermSize=128m -XX:MaxPermSize=256m -XX:PermSize=128m -XX:MaxPermSize
starting weblogic with Java version:
java version "1.6.0_25"
Java(TM) SE Runtime Environment (build 1.6.0_25-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.0-b11, mixed mode)
Starting WLS with line:
/app/oracle/product/ofm/jdk1.6.0_25/bin/java -server -Xms=512m -Xmx=512m -Xns=128m -d64 -XgcPrio:throughput -XXnoSystemGC -Djava.security.egd=file:/dev/../dev/urandom -XX:PermSize=128m -XX:MaxPermSize=256m -XX:PermSize=128m -XX:MaxPermSize -Dweblogic.Name=AdminServer -Djava.security.policy=/app/oracle/product/ofm/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.ProductionModeEnabled=true -da -Dplatform.home=/app/oracle/product/ofm/wlserver_10.3 -Dwls.home=/app/oracle/product/ofm/wlserver_10.3/server -Dweblogic.home=/app/oracle/product/ofm/wlserver_10.3/server -XX:PermSize=256m -XX:MaxPermSize=512m -Dcommon.components.home=/app/oracle/product/ofm/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=/app/oracle/product/ofm/user_projects/domains/IDMDomain -Djrockit.optfile=/app/oracle/product/ofm/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.server.config.dir=/app/oracle/product/ofm/user_projects/domains/IDMDomain/config/fmwconfig/servers/AdminServer -Doracle.domain.config.dir=/app/oracle/product/ofm/user_projects/domains/IDMDomain/config/fmwconfig -Digf.arisidbeans.carmlloc=/app/oracle/product/ofm/user_projects/domains/IDMDomain/config/fmwconfig/carml -Digf.arisidstack.home=/app/oracle/product/ofm/user_projects/domains/IDMDomain/config/fmwconfig/arisidprovider -Doracle.security.jps.config=/app/oracle/product/ofm/user_projects/domains/IDMDomain/config/fmwconfig/jps-config.xml -Doracle.deployed.app.dir=/app/oracle/product/ofm/user_projects/domains/IDMDomain/servers/AdminServer/tmp/_WL_user -Doracle.deployed.app.ext=/- -Dweblogic.alternateTypesDirectory=/app/oracle/product/ofm/oracle_common/modules/oracle.ossoiap_11.1.1,/app/oracle/product/ofm/oracle_common/modules/oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dem.oracle.home=/app/oracle/product/ofm/oracle_common -Djava.awt.headless=true -Didm.oracle.home=/app/oracle/product/ofm/Oracle_IDM1 -Xms512m -Xmx1024m -Xss512K -Djava.net.preferIPv6Addresses=true -DuseIPv6Address=true -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.management.discover=false -Djava.net.preferIPv6Addresses=true -Dweblogic.management.discover=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/app/oracle/product/ofm/patch_wls1035/profiles/default/sysext_manifest_classpath:/app/oracle/product/ofm/patch_ocp360/profiles/default/sysext_manifest_classpath weblogic.Server
Invalid initial heap size: -Xms=512m
Could not create the Java virtual machine.
Edited by: rrp on Oct 26, 2011 10:38 AM

I just noticed that in one place it is -Xms=512m and in the other it is -Xms512m. But the example I was given works - but apparently with JRocket, not sun. Does the format of this parameter vary between Hotspot and JRocket??? But the question on duplicate parameters remains.
Edited by: rrp on Oct 26, 2011 10:50 AM

Problem Starting WLS 5.1 from windows 2000 program group

Hi
I couldn't able to start Weblogic server 5.1 from windows 2000 program
group(start > Programs > Weblogic 5.10 > Weblogic Server). I can start WLS
without any problem from the console . I've check every configuration and
environment setting, the problem still come out. Whenever I start WLS from
program group , a window dialog with error messages will come out , here's
the error messages :
wlserver.exe - Application Error
The instruction at "0x04d5d0d6" referenced memory at
"0x00000000". The memory could not be "written".
Click on OK to terminate the program
Click on CANCEL to debug the program
Any suggestions/solution will be appreciated .
Thanks
Chew Leong
[email protected]

look for weblogic.system.password property in your weblogic.properties
file and see what's in there.
Shailesh Mungikar wrote:
I am trying to install WLS 5.1 SP12 on my Windows 2000 machine.
I have WLS 6.1 already installed my PC.
When I try to install, at the very end when
"System" password required
dialog pops up, I get another dialog box saying
WLPASS~1.exe Application Error
The exception Floating point division by zero (0xc000008e) occured in
the application at location 0x50147c14
When I press OK, it kill the "System password" dialog.
The installation seems to be complete.
If I go ahead and try to start weblogic, I get Exceptio
java.security.AccessControlException: access denied
(java.lang.RuntimePermission createSecurityManager)
Any solution/workaround?
thanks,
_shailesh

Unable to start WLS 9.2 nodemanager service

I have installed the nodemanager on the machine and can run it from the command line using
beasvc -debug "BEA Products NodeManager (D_bfapps_bea_weblogic92)"
This should run the service from the command line as if I started it from the computer management window correct? I ask this b/c the installed service will not start, and I get the following error:
"Could not start the BEA Products NodeManager(D_bfapps_bea_weblogic92) service on Local Computer.
Error 1067: The process terminated unexpectedly."
There is no other information logged on the machine. Please help!
Thanks.

Have you gotten a resolution to this problem? If so, please post the solution. I'm having this exact same problem. I installed WebLogic 9.2 and then installed NodeManager 9.2 as a Windows service. The NodeManager service actually ran for a couple of days--I was able to stop and start WLS servers and connect to the NodeManager via WLST. However, a day or two later the NodeManager service stopped working. Just like you, no debugging information is logged when the service fails. I CAN start NodeManager with startnodemanager.cmd. However, I need the NodeManager Windows Service to work. I opened a ticket with BEA regarding this issue, but they have not come back with a solution, yet.

NEWBIE: Help needed - Eclipse freeze after starting WLS 9.2

Hi All,
I'm very new in development with wls 9.2 and eclipse.
I'm trying to create a simple application (an EAR with a Session Bean).
When I start the WLS inside Eclipse (debug or run mode), this one, after a few seconds or clicks, freeze with 99%CPU usage.
Thanks in advance for help.... it's urgent....
Eclipse 3.3.0
WLST 1.1.0
WLS 9.2
Edited by mtode at 10/07/2007 2:04 AM
Edited by mtode at 10/07/2007 2:05 AM

If I understand you correctly, Eclipse stops responding after a while.
This may not be actually related to starting WLS. It sounds a bit like
you might be having a memory problem. Could you specify your operating
system, the amount of physical memory and the contents of your
eclipse.ini file?
Thanks,
- Konstantin

Availability date for WLS 5.10 SP9 ?

Is there a planned availability date for WLS 5.1 SP9, specifically
the 128-bit version ? I could of sworn that I've seen a page on
BEA's site that listed the scheduled releases dates for the service
packs, but I can't seem to find it any longer. Has anyone seen
somthing like that ?
Thanks.

contact [email protected]
David Brown wrote:
Is there a planned availability date for WLS 5.1 SP9, specifically
the 128-bit version ? I could of sworn that I've seen a page on
BEA's site that listed the scheduled releases dates for the service
packs, but I can't seem to find it any longer. Has anyone seen
somthing like that ?
Thanks.

Start wls using shortcut in a dos window

Hi,
I created a shortcut to startManagedWeblogic on desktop, when I need to start
wls, just click it. But whenever I stop the server, the window is gone, I would
like to let the window stay after the server stops, because sometime the wls crashed,
window is gone, nothing is in log file.
how can I modify the batch file to let the window stay? Thanks

You might try looking at launching the startManagedWeblogic script using the
windows "start" shell command. So you might create a new batch file with
this command in it
start %WEBLOGIC_HOME%\startManagedWeblogic.cmd
then launch that script via a shortcut
HTH,
Mike Jasnowski / BEA
"Jen" <[email protected]> wrote in message
news:3f9025e3$[email protected]..
>
Hi,
I created a shortcut to startManagedWeblogic on desktop, when I need tostart
wls, just click it. But whenever I stop the server, the window is gone, Iwould
like to let the window stay after the server stops, because sometime thewls crashed,
window is gone, nothing is in log file.
how can I modify the batch file to let the window stay? Thanks

Can't start WLS after change of JDK

I changed JDK from 131 to 140 and the server won't even start....pls let me
know what I need to change in the cmd file.
Thanks.
W

It's not supported, but if you want to experiment, you can
read this document: http://www.genuitec.com/products/JDK14_WLS61.pdf
Jay Shen <[email protected]> wrote:
I changed JDK from 131 to 140 and the server won't even start....pls let me
know what I need to change in the cmd file.
Thanks.
W--
Dimitri

Re: Starting WLS 5.1 SP9 w/ JDK 1.3

Similar Messages

Maybe you are looking for