Starting Managed Server: bi_server1 with error
I am installing OBIEE 11.1.1.7, but at configuration time the error occurred below.
The console weblogic start correctly, but is bi_server1 as ADMIN status.
Stopping Derby Server...
Starting AdminServer
Starting the domain ...
progress in calculate progress1
Executing Task: Starting Managed Server: bi_server1
oracle.as.install.bi.wls.ServerLifeCycleException: Failed to achieve state RUNNING in 3600seconds. The server is currently in state ADMIN
at oracle.as.install.bi.wls.ServerLifeCycle.waitForManagedWLSServerState(ServerLifeCycle.java:119)
at oracle.as.install.bi.wls.ServerLifeCycle.startServerSynchronous(ServerLifeCycle.java:59)
at oracle.as.install.bi.biconfig.standard.StartStopManagedServer.doExecute(StartStopManagedServer.java:55)
at oracle.as.install.bi.biconfig.standard.AbstractProvisioningTask.execute(AbstractProvisioningTask.java:70)
at oracle.as.install.bi.biconfig.standard.StandardProvisionTaskList.execute(StandardProvisionTaskList.java:66)
at oracle.as.install.bi.biconfig.BIConfigMain.doExecute(BIConfigMain.java:113)
at oracle.as.install.engine.modules.configuration.client.ConfigAction.execute(ConfigAction.java:375)
at oracle.as.install.engine.modules.configuration.action.TaskPerformer.run(TaskPerformer.java:88)
at oracle.as.install.engine.modules.configuration.action.TaskPerformer.startConfigAction(TaskPerformer.java:105)
at oracle.as.install.engine.modules.configuration.action.ActionRequest.perform(ActionRequest.java:15)
at oracle.as.install.engine.modules.configuration.action.RequestQueue.perform(RequestQueue.java:96)
at oracle.as.install.engine.modules.configuration.standard.StandardConfigActionManager.start(StandardConfigActionManager.java:186)
at oracle.as.install.engine.modules.configuration.boot.ConfigurationExtension.kickstart(ConfigurationExtension.java:81)
at oracle.as.install.engine.modules.configuration.ConfigurationModule.run(ConfigurationModule.java:86)
at java.lang.Thread.run(Thread.java:662)
I had same issue while installing OBIEE 11.1.1.7.0
Check your data Sources are connecting. To do that
1. Login to console, go to Data Sources
2. Click on mds-owsm
3. Click on Monitoring --> Testing on second line below Monitoring
4. Select bi_server1 and click Test Data Source.
If this fails, check your tnsnames.ora file and verify you are able to connect to the database server from the obiee installation server.
If this is working fine, then follow these steps:
1. Login to console, go to servers
2. Click on control on Summary of Servers
3. Click on Lock & Edit in the left pane
4. Select bi_server1 and click resume.
This should work. Sometimes during new installation the weblogic sever times out from connecting to database. So resuming will do the work. DO NOT FORCE SHUT DOWN
Thanks,
Preet Shah
Similar Messages
-
Hi All,
I am trying to install OBIEE 11.1.1.7.1 un a Linux box, but during the Configuration Progress, OBIEE got error at Start Managed server; bi_server1.
Looking into install log I've found the following :
Done
Stopping Derby Server...
Starting AdminServer
Starting the domain ...
progress in calculate progress1
Executing Task: Starting Managed Server: bi_server1
oracle.as.install.bi.wls.ServerLifeCycleException: Failed to achieve state RUNNING in 3600seconds. The server is currently in state ADMIN
at oracle.as.install.bi.wls.ServerLifeCycle.waitForManagedWLSServerState(ServerLifeCycle.java:119)
at oracle.as.install.bi.wls.ServerLifeCycle.startServerSynchronous(ServerLifeCycle.java:59)
at oracle.as.install.bi.biconfig.standard.StartStopManagedServer.doExecute(StartStopManagedServer.java:55)
at oracle.as.install.bi.biconfig.standard.AbstractProvisioningTask.execute(AbstractProvisioningTask.java:70)
at oracle.as.install.bi.biconfig.standard.StandardProvisionTaskList.execute(StandardProvisionTaskList.java:66)
at oracle.as.install.bi.biconfig.BIConfigMain.doExecute(BIConfigMain.java:113)
at oracle.as.install.engine.modules.configuration.client.ConfigAction.execute(ConfigAction.java:375)
at oracle.as.install.engine.modules.configuration.action.TaskPerformer.run(TaskPerformer.java:88)
at oracle.as.install.engine.modules.configuration.action.TaskPerformer.startConfigAction(TaskPerformer.java:105)
at oracle.as.install.engine.modules.configuration.action.ActionRequest.perform(ActionRequest.java:15)
at oracle.as.install.engine.modules.configuration.action.RequestQueue.perform(RequestQueue.java:96)
at oracle.as.install.engine.modules.configuration.standard.StandardConfigActionManager.start(StandardConfigActionManager.java:186)
at oracle.as.install.engine.modules.configuration.boot.ConfigurationExtension.kickstart(ConfigurationExtension.java:81)
at oracle.as.install.engine.modules.configuration.ConfigurationModule.run(ConfigurationModule.java:86)
at java.lang.Thread.run(Thread.java:662)
What could be caussing this failure ?
ThanksI had similar issue in windows 7 [64 bit].
It is found that the nodemanger windows service was not present and I had to create it by executing installNodeMgrSvc.cmd present in wls server location say, 'C:\Oracle\Middleware\wlserver_10.3\server\bin' in my case and then come to bi wls console and 'Resume' the bi_server1 managed server. You would see progress in the installer once the managed server bi_server1 is 'Running' state.
Hope this helps. -
Hi
Gurus, please help me ,before i have OBIEE 11.1.1.5 now i try to change OBIEE 11.1.1.6 at installing time *"Starting Managed Server: bi_server1" failed* in configuration process.
please help me.
Thanks,I had similar issue in windows 7 [64 bit].
It is found that the nodemanger windows service was not present and I had to create it by executing installNodeMgrSvc.cmd present in wls server location say, 'C:\Oracle\Middleware\wlserver_10.3\server\bin' in my case and then come to bi wls console and 'Resume' the bi_server1 managed server. You would see progress in the installer once the managed server bi_server1 is 'Running' state.
Hope this helps. -
How to start managed server automatically with admin server.
Hello all, I have an admin server anda managed server configured in a machine. I want to start the managed server as soon as I run the script to start the admin server and node manager in the unix pc.
The admin and managed server are added to the same machine and the machine is connected with the node manager.
Please let me know what else need to be configured or make change in the script.hello user12003735..
sorry for not mentioning the wlst tool path.
You can start the wlst(WEBLOGIC SCRIPTING TOOL) in two ways and run your jython scripts.
PROCEDURE 1) Directly invoking wlst :
You will find the wlst.cmd(wlst.sh in case of UNIX enviroments) in $WL_HOME/common/bin. From command line do this
wlst <JYTHON SCRIPT>
./wlst.sh <JYTHON SCRIPT> [UNIX]
PROCEDURE 2) From Command Line :
There is a jar file in $WL_HOME/server/lib named weblogic.jar. It conatins a class file named WLST.cmd in the package weblogic[Try jd-gui.exe java decompiler to look inside the jarfile. to get it google it]. This jar file actually makes the wlst tool running. If you try to look inside wlst.cmd or wlst.sh you will find that the scripts are internally adding this jar file in CLASSPATH and calling it:
eval '"${JAVA_HOME}/bin/java"' ${JVM_ARGS} weblogic.WLST '"$@"' [wlst.sh]
"%JAVA_HOME%\bin\java" %JVM_ARGS% weblogic.WLST %* [wslt.cmd]
So you can do exactly what the scripts doing from command line. do this :
{A} $WL_HOME/server/bin/setWLSEnv.sh [or setWLSEnv.cmd] <---------------------------------------- SETS THE CLASSPATH
You will see a lot of jar files added to your classpath and this step is exactly same when you run the wlst from the scripts in PROCEDURE 1.
java weblogic.WLST <JYTHON SCRIPT>
One thing you can also use the weblogic jar file to monitor any weblogic server[You have to first set the env with setWLSEnv.cmd or .sh]:
java weblogic.Admin -url t3://<IP>:<PORT> -username <USERNAME> -password <PASSWORD> GETSTATE <SERVERNAME> [GETTING THE STATE]
java weblogic.Admin -url t3://<IP>:<PORT> -username <USERNAME> -password <PASSWORD> FORCESHUTDOWN <SERVERNAME> [FORCIBLY SHUTTING DOWN SERVERS]
You can do many other things with weblogic.jar not just the previous two. Refer to oracle manuals. -
Error starting managed server with JRockit VM
I getting this error when i start the server with Jrockit VM 3.1 with -Xthinthreads
option on. The OS is NT. Any clues , please ?
exception: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
D:\i252\services>runtxnserver
JRockit build 3.1.4-CROSIS-20020429-1505, Thin Threads, Generational Concurr
Garbage Collector, started.
[JRockit] Starting Management Server on port 7090
Starting WebLogic Server ....
Connecting to http://ocncat2:7991...
<May 10, 2002 11:50:59 AM PDT> <Error> <NT Performance Pack> <Problem on fd:
4', socket: 'weblogic.rjvm.t3.T3JVMConnection@111'
java.io.IOException: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824)
at weblogic.socket.NTSocketMuxer.registerSockInIoPort(Native Method)
35c4a
at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
2410
at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled C
@23e31b90
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled Cod
3e30810
at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
0660
at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
led Code)@23d7ec10
at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
>
<May 10, 2002 11:51:00 AM PDT> <Emergency> <Configuration Management> <Error
tected attempting to connect to admin server at http://ocncat2:7991 during i
alization of managed server ( null:7551 ). The reported error was: < java.io
xception: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) > This condition generally results when the managed and
n servers are using the same listen address and port.>
<May 10, 2002 11:51:00 AM PDT> <Emergency> <Server> <Unable to initialize th
rver: 'Fatal initialization exception
Throwable: weblogic.management.configuration.ConfigurationException: java.io
xception: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
parameter is incorrect.
(error 87, fd 824)
at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
2410
at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled C
@23e31b90
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled Cod
3e30810
at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
0660
at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
led Code)@23d7ec10
at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
ouldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
'>
The WebLogic Server did not start up properly.
Exception raised: weblogic.management.configuration.ConfigurationException:
.io.IOException: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
parameter is incorrect.
(error 87, fd 824)
at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
2410
at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled C
@23e31b90
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled Cod
3e30810
at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
0660
at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
led Code)@23d7ec10
at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
ouldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack traceI found the solution . The reason for this is that JRockit's High Performance Thread
System uses asynchrounous I/O "under the hood". Weblogic's Native I/O is also asynchronous.
The two asynchronous I/O systems clash and the result is the error you see.
There are two ways around this problem. Either disable JRockit's High Performance
Thread System (or thinthreads) by using the -Xnativethreads command line flag, or
disable Weblogic's Native I/O.
For Weblogic 6.0 and higher, edit the config.xml file. Find the line saying NativeIOEnabled="true"
and change this to NativeIOEnabled="false".
For Weblogic 5.1 you edit the file weblogic.properties and change the line weblogic.system.nativeIO.enable=true
to
weblogic.system.nativeIO.enable=false
"Manoj jayadevan" <[email protected]> wrote:
>
I getting this error when i start the server with Jrockit VM 3.1 with -Xthinthreads
option on. The OS is NT. Any clues , please ?
exception: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
D:\i252\services>runtxnserver
JRockit build 3.1.4-CROSIS-20020429-1505, Thin Threads, Generational Concurr
Garbage Collector, started.
[JRockit] Starting Management Server on port 7090
Starting WebLogic Server ....
Connecting to http://ocncat2:7991...
<May 10, 2002 11:50:59 AM PDT> <Error> <NT Performance Pack> <Problem on
fd:
4', socket: 'weblogic.rjvm.t3.T3JVMConnection@111'
java.io.IOException: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824)
at weblogic.socket.NTSocketMuxer.registerSockInIoPort(Native Method)
35c4a
at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
2410
at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled
C
@23e31b90
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled
Cod
3e30810
at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
0660
at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
led Code)@23d7ec10
at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
>
<May 10, 2002 11:51:00 AM PDT> <Emergency> <Configuration Management> <Error
tected attempting to connect to admin server at http://ocncat2:7991 during
i
alization of managed server ( null:7551 ). The reported error was: < java.io
xception: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) > This condition generally results when the managed
and
n servers are using the same listen address and port.>
<May 10, 2002 11:51:00 AM PDT> <Emergency> <Server> <Unable to initialize
th
rver: 'Fatal initialization exception
Throwable: weblogic.management.configuration.ConfigurationException: java.io
xception: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
parameter is incorrect.
(error 87, fd 824)
at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
2410
at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled
C
@23e31b90
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled
Cod
3e30810
at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
0660
at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
led Code)@23d7ec10
at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
ouldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
'>
The WebLogic Server did not start up properly.
Exception raised: weblogic.management.configuration.ConfigurationException:
.io.IOException: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
parameter is incorrect.
(error 87, fd 824)
at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
2410
at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled
C
@23e31b90
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled
Cod
3e30810
at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
0660
at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
led Code)@23d7ec10
at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
ouldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace -
Error while starting Managed server in wls
I am using WebLogic Server Version: 10.3.4.0. I have created one managed server thru admin console. I am starting managed server using startManagedWebLogic.cmd batch file. Chnages I made in this cmd file is added managed server name and wls userid/password.
When execute this, I get below error:
Server
Exception in thread "Main Thread" java.lang.NoClassDefFoundError: weblogic/Server
Caused by: java.lang.ClassNotFoundException: weblogic.Server
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
Could not find the main class: weblogic.Server. Program will exit.
The contents of the startManagedWebLogic.cmd is as below:
@ECHO OFF
@REM WARNING: This file is created by the Configuration Wizard.
@REM Any changes to this script may be lost when adding extensions to this configuration.
SETLOCAL
@REM --- Start Functions ---
GOTO :ENDFUNCTIONS
:usage
echo Need to set SERVER_NAME and ADMIN_URL environment variables or specify
echo them in command line:
echo Usage: %1 SERVER_NAME {ADMIN_URL}
echo for example:
echo %1 managedserver1 http://localhost:7001
GOTO :EOF
:ENDFUNCTIONS
@REM --- End Functions ---
@REM *************************************************************************
@REM This script is used to start a managed WebLogic Server for the domain in
@REM the current working directory. This script can either read in the SERVER_NAME and
@REM ADMIN_URL as positional parameters or will read them from environment variables that are
@REM set before calling this script. If SERVER_NAME is not sent as a parameter or exists with a value
@REM as an environment variable the script will EXIT. If the ADMIN_URL value cannot be determined
@REM by reading a parameter or from the environment a default value will be used.
@REM
@REM For additional information, refer to "Managing Server Startup and Shutdown for Oracle WebLogic Server"
@REM (http://download.oracle.com/docs/cd/E17904_01/web.1111/e13708/overview.htm)
@REM *************************************************************************
@REM Set SERVER_NAME to the name of the server you wish to start up.
Set SERVER_NAME=*ManagedServer1*
set DOMAIN_NAME=mydomain
set ADMIN_URL=http://localhost:7001
@REM Set WLS_USER equal to your system username and WLS_PW equal
@REM to your system password for no username and password prompt
@REM during server startup. Both are required to bypass the startup
@REM prompt.
set WLS_USER=*weblogic*
set WLS_PW=*weblogic1*
@REM Set JAVA_OPTIONS to the java flags you want to pass to the vm. i.e.:
@REM set JAVA_OPTIONS=-Dweblogic.attribute=value -Djava.attribute=value
set JAVA_OPTIONS=-Dweblogic.security.SSL.trustedCAKeyStore="d:\Perforce\weblogic1\src_16020jr\bea\wlserver_10.3\server\..\server\lib\cacerts" %JAVA_OPTIONS%
@REM Set JAVA_VM to the java virtual machine you want to run. For instance:
@REM set JAVA_VM=-server
set JAVA_VM=
@REM Set SERVER_NAME and ADMIN_URL, they must by specified before starting
@REM a managed server, detailed information can be found at
@REM http://download.oracle.com/docs/cd/E17904_01/web.1111/e13708/overview.htm
if "%1"=="" (
if "%SERVER_NAME%"=="" (
CALL :usage %0
GOTO :EOF
) else (
set SERVER_NAME=%1
shift
if "%1"=="" (
if "%ADMIN_URL%"=="" (
CALL :usage %0
GOTO :EOF
) else (
set ADMIN_URL=%1
shift
@REM Export the admin_url whether the user specified it OR it was sent on the command-line
set ADMIN_URL=%ADMIN_URL%
set SERVER_NAME=%SERVER_NAME%
set DOMAIN_HOME=D:\Perforce\weblogic1\dev\src_crmod\wls\mytest
if "%1"=="" (
@REM Call Weblogic Server with our default params since the user did not specify any other ones
call "%DOMAIN_HOME%\bin\startWebLogic.cmd" nodebug noderby noiterativedev notestconsole noLogErrorsToConsole
) else (
@REM Call Weblogic Server with the params the user sent in INSTEAD of the defaults
call "%DOMAIN_HOME%\bin\startWebLogic.cmd" %1 %2 %3 %4 %5 %6 %7 %8 %9
ENDLOCAL
Any help is really appreciated.I could see calling to setDomainEnv.cmd script:
*@REM Call setDomainEnv here.*
set DOMAIN_HOME=D:\Perforce\weblogic1\dev\src_crmod\wls\mytest
for %%i in ("%DOMAIN_HOME%") do set DOMAIN_HOME=%%~fsi
call "%DOMAIN_HOME%\bin\setDomainEnv.cmd" %*
set SAVE_JAVA_OPTIONS=%JAVA_OPTIONS%
set SAVE_CLASSPATH=%CLASSPATH%
But in my environment I do not see these variable set to any, JAVA_HOME, DERBY_CLASSPATH, JAVA_OPTIONS, CLASS_PATH.
This might be the issue? Or anything else? -
Error while starting manages server
Hi All.
M facing problem while starting managed server, this might be related to sip server as i see this in the error log. when i click on the sip server tab in the console then io see below error :-
+++++++++
Error opening /ext-jsp/sipserver/ConfigGeneralForm.jsp.
The source of this error is:
javax.servlet.ServletException: weblogic.servlet.jsp.CompilationException: Failed to compile JSP /ext-jsp/sipserver/ConfigGeneralForm.jsp
Exception occurred while processing '/bea/wls/user_projects/domains/base_domain/servers/AdminServer/tmp/_WL_internal/consoleapp/jxhze9/console-ext/sipserver-console-ext/ext-jsp/sipserver/ConfigGeneralForm.jsp'java.lang.OutOfMemoryError: PermGen space
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:791)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
at com.bea.core.repackaged.jdt.internal.compiler.lookup.CompilationUnitScope.buildTypeBindings(CompilationUnitScope.java:67)
at com.bea.core.repackaged.jdt.internal.compiler.lookup.LookupEnvironment.buildTypeBindings(LookupEnvironment.java:152)
at com.bea.core.repackaged.jdt.internal.compiler.Compiler.internalBeginToCompile(Compiler.java:717)
at com.bea.core.repackaged.jdt.internal.compiler.Compiler.beginToCompile(Compiler.java:377)
at com.bea.core.repackaged.jdt.internal.compiler.Compiler.compile(Compiler.java:422)
at weblogic.jsp.internal.java.JDTJavaCompiler.generateByteCode(JDTJavaCompiler.java:104)
at weblogic.jsp.internal.java.JavaSourceFile._codeGen(JavaSourceFile.java:211)
at weblogic.jsp.internal.java.JavaSourceFile.codeGen(JavaSourceFile.java:201)
at weblogic.jsp.internal.ProxySourceFile.compileGeneratedFiles(ProxySourceFile.java:310)
at weblogic.jsp.internal.ProxySourceFile.codeGen(ProxySourceFile.java:248)
at weblogic.jsp.internal.SourceFile.codeGen(SourceFile.java:327)
at weblogic.jsp.internal.client.ClientUtilsImpl$CodeGenJob.run(ClientUtilsImpl.java:599)
at weblogic.jsp.internal.client.Job.performJob(Job.java:83)
at weblogic.jsp.internal.client.ThreadPool$WorkerThread.run(ThreadPool.java:217)
Caused by: weblogic.servlet.jsp.CompilationException: Failed to compile JSP /ext-jsp/sipserver/ConfigGeneralForm.jsp
Exception occurred while processing '/bea/wls/user_projects/domains/base_domain/servers/AdminServer/tmp/_WL_internal/consoleapp/jxhze9/console-ext/sipserver-console-ext/ext-jsp/sipserver/ConfigGeneralForm.jsp'java.lang.OutOfMemoryError: PermGen space
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:791)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
at com.bea.core.repackaged.jdt.internal.compiler.lookup.CompilationUnitScope.buildTypeBindings(CompilationUnitScope.java:67)
at com.bea.core.repackaged.jdt.internal.compiler.lookup.LookupEnvironment.buildTypeBindings(LookupEnvironment.java:152)
at com.bea.core.repackaged.jdt.internal.compiler.Compiler.internalBeginToCompile(Compiler.java:717)
at com.bea.core.repackaged.jdt.internal.compiler.Compiler.beginToCompile(Compiler.java:377)
at com.bea.core.repackaged.jdt.internal.compiler.Compiler.compile(Compiler.java:422)
at weblogic.jsp.internal.java.JDTJavaCompiler.generateByteCode(JDTJavaCompiler.java:104)
at weblogic.jsp.internal.java.JavaSourceFile._codeGen(JavaSourceFile.java:211)
at weblogic.jsp.internal.java.JavaSourceFile.codeGen(JavaSourceFile.java:201)
at weblogic.jsp.internal.ProxySourceFile.compileGeneratedFiles(ProxySourceFile.java:310)
at weblogic.jsp.internal.ProxySourceFile.codeGen(ProxySourceFile.java:248)
at weblogic.jsp.internal.SourceFile.codeGen(SourceFile.java:327)
at weblogic.jsp.internal.client.ClientUtilsImpl$CodeGenJob.run(ClientUtilsImpl.java:599)
at weblogic.jsp.internal.client.Job.performJob(Job.java:83)
at weblogic.jsp.internal.client.ThreadPool$WorkerThread.run(ThreadPool.java:217)
at weblogic.servlet.jsp.JavelinxJSPStub.reportCompilationErrorIfNeccessary(JavelinxJSPStub.java:226)
at weblogic.servlet.jsp.JavelinxJSPStub.compilePage(JavelinxJSPStub.java:162)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:256)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:216)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:243)
... 184 more
++++++++
Below is the config.xml file i am using :-
<?xml version="1.0" encoding="UTF-8"?>
<domain xsi:schemaLocation="http://xmlns.oracle.com/weblogic/security/wls http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.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/xacml http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd" 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">
<name>base_domain</name>
<domain-version>10.3.4.0</domain-version>
<security-configuration xmlns:xacml="http://xmlns.oracle.com/weblogic/security/xacml" xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator">
<name>base_domain</name>
<realm>
<sec:authentication-provider xsi:type="wls:default-authenticatorType"/>
<sec:authentication-provider xsi:type="wls:default-identity-asserterType">
<sec:active-type>AuthenticatedUser</sec:active-type>
</sec:authentication-provider>
<sec:role-mapper xsi:type="xacml:xacml-role-mapperType"/>
<sec:authorizer xsi:type="xacml:xacml-authorizerType"/>
<sec:adjudicator xsi:type="wls:default-adjudicatorType"/>
<sec:credential-mapper xsi:type="wls:default-credential-mapperType"/>
<sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"/>
<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
<sec:name>myrealm</sec:name>
<sec:password-validator 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}Ax9F8YRCZJqRRoPcjJxTwS03NgNAJSUjUcQ0vMJybMfkxNKN3YZCRsR+jEQrT/n3/KU4Kn5WXqCILWifqYRDlmnGGryHuNEEK83B/FCoBb1h8T47+ML1pULyyNpGPaFq</credential-encrypted>
<node-manager-username>weblogic</node-manager-username>
<node-manager-password-encrypted>{AES}G0nkKdRHqwIqNXGqn7lArIXG1SfKKdkWwTOyZ4SmkwE=</node-manager-password-encrypted>
</security-configuration>
<server>
<name>AdminServer</name>
<self-tuning-thread-pool-size-min>15</self-tuning-thread-pool-size-min>
<socket-readers>2</socket-readers>
<ssl>
<name>AdminServer</name>
<enabled>true</enabled>
</ssl>
<machine>Machine_1</machine>
<listen-address/>
<network-access-point>
<name>sip</name>
<protocol>sip</protocol>
<listen-port>5060</listen-port>
<public-port>5060</public-port>
<http-enabled-for-this-protocol>false</http-enabled-for-this-protocol>
<outbound-enabled>true</outbound-enabled>
</network-access-point>
<network-access-point>
<name>sips</name>
<protocol>sips</protocol>
<listen-port>5061</listen-port>
<public-port>5061</public-port>
<http-enabled-for-this-protocol>false</http-enabled-for-this-protocol>
<outbound-enabled>true</outbound-enabled>
</network-access-point>
</server>
<server>
<name>M1</name>
<ssl>
<name>M1</name>
<enabled>true</enabled>
<listen-port>7503</listen-port>
</ssl>
<machine>Machine_1</machine>
<listen-port>7003</listen-port>
<listen-address/>
<web-service>
<name>M1</name>
<web-service-persistence>
<name>M1</name>
<web-service-logical-store>
<name>WseeStore</name>
<persistence-strategy>LOCAL_ACCESS_ONLY</persistence-strategy>
<request-buffering-queue-jndi-name>weblogic.wsee.BufferedRequestQueue</request-buffering-queue-jndi-name>
<response-buffering-queue-jndi-name>weblogic.wsee.BufferedResponseQueue</response-buffering-queue-jndi-name>
</web-service-logical-store>
</web-service-persistence>
</web-service>
</server>
<server>
<name>M2</name>
<ssl>
<name>M2</name>
<enabled>true</enabled>
<listen-port>7504</listen-port>
</ssl>
<machine>Machine_1</machine>
<listen-port>7004</listen-port>
<listen-address/>
<web-service>
<name>M2</name>
<web-service-persistence>
<name>M2</name>
<web-service-logical-store>
<name>WseeStore</name>
<persistence-strategy>LOCAL_ACCESS_ONLY</persistence-strategy>
<request-buffering-queue-jndi-name>weblogic.wsee.BufferedRequestQueue</request-buffering-queue-jndi-name>
<response-buffering-queue-jndi-name>weblogic.wsee.BufferedResponseQueue</response-buffering-queue-jndi-name>
</web-service-logical-store>
</web-service-persistence>
</web-service>
</server>
<embedded-ldap>
<name>base_domain</name>
<credential-encrypted>{AES}vWDbFLBCN+g/5kGlFyC+Qp8NUIevNXYQEJYBVgoM2BaXRBIGnLy+rHfLzGrQT5JG</credential-encrypted>
</embedded-ldap>
<configuration-version>10.3.4.0</configuration-version>
<machine xsi:type="unix-machineType">
<name>Machine_1</name>
<node-manager>
<name>Machine_1</name>
<listen-address>localhost</listen-address>
</node-manager>
</machine>
<jms-server>
<name>WseeJmsServer_auto_2</name>
<target>M1</target>
<persistent-store>WseeFileStore_auto_2</persistent-store>
</jms-server>
<jms-server>
<name>WseeJmsServer_auto_3</name>
<target>M2</target>
<persistent-store>WseeFileStore_auto_3</persistent-store>
</jms-server>
<jms-server>
<name>WseeJaxwsJmsServer_auto_2</name>
<target>M1</target>
<persistent-store>WseeJaxwsFileStore_auto_2</persistent-store>
</jms-server>
<jms-server>
<name>WseeJaxwsJmsServer_auto_3</name>
<target>M2</target>
<persistent-store>WseeJaxwsFileStore_auto_3</persistent-store>
</jms-server>
<self-tuning>
<fair-share-request-class>
<name>wlss.transport.fsrc</name>
<target>M1,M2</target>
<fair-share>50</fair-share>
</fair-share-request-class>
<fair-share-request-class>
<name>wlss.timer.fsrc</name>
<target>M1,M2</target>
<fair-share>100</fair-share>
</fair-share-request-class>
<fair-share-request-class>
<name>wlss.tracing.fsrc</name>
<target>M1,M2</target>
<fair-share>50</fair-share>
</fair-share-request-class>
<fair-share-request-class>
<name>wlss.connect.fsrc</name>
<target>M1,M2</target>
<fair-share>1000</fair-share>
</fair-share-request-class>
<min-threads-constraint>
<name>wlss.tracing.minthreads</name>
<target>M1,M2</target>
<count>1</count>
</min-threads-constraint>
<min-threads-constraint>
<name>wlss.connect.minthreads</name>
<target>M1,M2</target>
<count>1</count>
</min-threads-constraint>
<max-threads-constraint>
<name>wlss.timer.maxthreads</name>
<target>M1,M2</target>
<count>16</count>
<connection-pool-name/>
</max-threads-constraint>
<max-threads-constraint>
<name>wlss.tracing.maxthreads</name>
<target>M1,M2</target>
<count>1</count>
<connection-pool-name/>
</max-threads-constraint>
<capacity>
<name>wlss.transport.capacity</name>
<target>M1,M2</target>
<count>400</count>
</capacity>
<capacity>
<name>wlss.timer.capacity</name>
<target>M1,M2</target>
<count>256</count>
</capacity>
<work-manager>
<name>wlss.transport</name>
<target>M1,M2</target>
<fair-share-request-class>wlss.transport.fsrc</fair-share-request-class>
<response-time-request-class xsi:nil="true"/>
<context-request-class xsi:nil="true"/>
<capacity>wlss.transport.capacity</capacity>
<ignore-stuck-threads>false</ignore-stuck-threads>
</work-manager>
<work-manager>
<name>wlss.timer</name>
<target>M1,M2</target>
<fair-share-request-class>wlss.timer.fsrc</fair-share-request-class>
<response-time-request-class xsi:nil="true"/>
<context-request-class xsi:nil="true"/>
<max-threads-constraint>wlss.timer.maxthreads</max-threads-constraint>
<capacity>wlss.timer.capacity</capacity>
<ignore-stuck-threads>false</ignore-stuck-threads>
</work-manager>
<work-manager>
<name>wlss.tracing.domain</name>
<target>M1,M2</target>
<fair-share-request-class>wlss.tracing.fsrc</fair-share-request-class>
<min-threads-constraint>wlss.tracing.minthreads</min-threads-constraint>
<max-threads-constraint>wlss.tracing.maxthreads</max-threads-constraint>
<ignore-stuck-threads>false</ignore-stuck-threads>
</work-manager>
<work-manager>
<name>wlss.tracing.local</name>
<target>M1,M2</target>
<fair-share-request-class>wlss.tracing.fsrc</fair-share-request-class>
<response-time-request-class xsi:nil="true"/>
<context-request-class xsi:nil="true"/>
<min-threads-constraint>wlss.tracing.minthreads</min-threads-constraint>
<max-threads-constraint>wlss.tracing.maxthreads</max-threads-constraint>
<ignore-stuck-threads>false</ignore-stuck-threads>
</work-manager>
<work-manager>
<name>wlss.connect</name>
<target>M1,M2</target>
<fair-share-request-class>wlss.connect.fsrc</fair-share-request-class>
<response-time-request-class xsi:nil="true"/>
<context-request-class xsi:nil="true"/>
<min-threads-constraint>wlss.connect.minthreads</min-threads-constraint>
<ignore-stuck-threads>false</ignore-stuck-threads>
</work-manager>
<work-manager>
<name>weblogic.wsee.mdb.DispatchPolicy</name>
<target>M1,M2</target>
</work-manager>
<work-manager>
<name>weblogic.wsee.jaxws.mdb.DispatchPolicy</name>
<target>M1, M2</target>
</work-manager>
</self-tuning>
<file-store>
<name>WseeFileStore_auto_2</name>
<directory>WseeFileStore_auto_2</directory>
<target>M1</target>
</file-store>
<file-store>
<name>WseeFileStore_auto_3</name>
<directory>WseeFileStore_auto_3</directory>
<target>M2</target>
</file-store>
<file-store>
<name>WseeJaxwsFileStore_auto_2</name>
<directory>WseeJaxwsFileStore_auto_2</directory>
<target>M1</target>
</file-store>
<file-store>
<name>WseeJaxwsFileStore_auto_3</name>
<directory>WseeJaxwsFileStore_auto_3</directory>
<target>M2</target>
</file-store>
<file-store>
<name>WseeFileStore</name>
<directory>WseeFileStore</directory>
<target>AdminServer</target>
</file-store>
<jms-system-resource>
<name>WseeJmsModule</name>
<target>M1,M2</target>
<sub-deployment>
<name>WseeJmsServer9127702</name>
<target>WseeJmsServer_auto_2</target>
</sub-deployment>
<sub-deployment>
<name>WseeJmsServer20604610</name>
<target>WseeJmsServer_auto_3</target>
</sub-deployment>
<descriptor-file-name>jms/wseejmsmodule-jms.xml</descriptor-file-name>
</jms-system-resource>
<jms-system-resource>
<name>WseeJaxwsJmsModule</name>
<target>M1,M2</target>
<sub-deployment>
<name>WseeJaxwsJmsServer31278546</name>
<target>WseeJaxwsJmsServer_auto_2</target>
</sub-deployment>
<sub-deployment>
<name>WseeJaxwsJmsServer7750867</name>
<target>WseeJaxwsJmsServer_auto_3</target>
</sub-deployment>
<descriptor-file-name>jms/wseejaxwsjmsmodule-jms.xml</descriptor-file-name>
</jms-system-resource>
<custom-resource>
<name>sipserver</name>
<target>M1,M2</target>
<descriptor-file-name>custom/sipserver.xml</descriptor-file-name>
<resource-class>com.bea.wcp.sip.management.descriptor.resource.SipServerResource</resource-class>
<descriptor-bean-class>com.bea.wcp.sip.management.descriptor.beans.SipServerBean</descriptor-bean-class>
</custom-resource>
<admin-server-name>AdminServer</admin-server-name>
<saf-agent>
<name>ReliableWseeSAFAgent</name>
<target>AdminServer</target>
<store>WseeFileStore</store>
</saf-agent>
<saf-agent>
<name>ReliableWseeJaxwsSAFAgent_M1</name>
<target>M1</target>
<store>WseeJaxwsFileStore_auto_2</store>
</saf-agent>
<saf-agent>
<name>ReliableWseeJaxwsSAFAgent_M2</name>
<target>M2</target>
<store>WseeJaxwsFileStore_auto_3</store>
</saf-agent>
</domain>
Can someone please helpme here..I tried same and facing below error whenever i click on any tab over the console :-
Error opening /jsp/core/server/ServersControlTable.jsp
The source of this error is:
java.lang.OutOfMemoryError: PermGen space
++++++++
below is the MEm_ARGS in commEnv.sh :-
# This script is used to set up a common environment for starting WebLogic
# Server, as well as WebLogic development.
# It sets the following variables:
# BEA_HOME - The home directory of all your BEA installation.
# MW_HOME - The home directory of all your Oracle installation.
# WL_HOME - The root directory of the BEA installation.
# COHERENCE_HOME - The root directory of the COHERENCE installation.
# ANT_HOME - The Ant Home directory.
# ANT_CONTRIB - The Ant contrib directory
# JAVA_HOME - Location of the version of Java used to start WebLogic
# Server. See the Oracle Fusion Middleware Supported System Configurations page
# (http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html) for an
# up-to-date list of supported JVMs on your platform.
# JAVA_VENDOR - Vendor of the JVM (i.e. BEA, HP, IBM, Sun, etc.)
# JAVA_USE_64BIT - Indicates if JVM uses 64 bit operations
# PATH - JDK and WebLogic directories will be added to the system
# path.
# WEBLOGIC_CLASSPATH - Classpath required to start WebLogic Server.
# FMWCONFIG_CLASSPATH - Classpath required to start config tools such as WLST, config wizard, pack, and unpack..
# FMWLAUNCH_CLASSPATH - Additional classpath needed for WLST start script
# LD_LIBRARY_PATH, LIBPATH and SHLIB_PATH
# - To locate native libraries.
# JAVA_VM - The java arg specifying the VM to run. (e.g.
# -server, -hotspot, etc.)
# MEM_ARGS - The variable to override the standard memory arguments
# passed to java.
# CLASSPATHSEP - CLASSPATH delimiter.
# PATHSEP - Path delimiter.
# DERBY_HOME - Derby home directory.
# DERBY_TOOLS - Derby tools jar.
# DERBY_CLASSPATH - Classpath needed to start Derby.
# DERBY_CLIENT_CLASSPATH
# - Derby client classpath.
# PRODUCTION_MODE - Indicates if the Server will be started in PRODUCTION_MODE
# PATCH_CLASSPATH - WebLogic system classpath patch
# PATCH_LIBPATH - Library path used for patches
# PATCH_PATH - Path used for patches
# WEBLOGIC_EXTENSION_DIRS - Extension dirs for WebLogic classpath patch
# It exports the following function:
# trapSIGINT - Get actual Derby PID when running in MKSNT environment;
# trap SIGINT to make sure Derby will also be stopped.
# resetFd - Reset the number of open file descriptors to 1024.
# jDriver for Oracle users: This script assumes that native libraries required
# for jDriver for Oracle have been installed in the proper location and that
# your os specific library path variable (i.e. LD_LIBRARY_PATH/solaris,
# SHLIB_PATH/hpux, etc...) has been set appropriately. Also note that this
# script defaults to the oci920_8 version of the shared libraries. If this is
# not the version you need, please adjust the library path variable
# accordingly.
# sub functions
# limit the number of open file descriptors
resetFd() {
if [ ! -n "`uname -s |grep -i cygwin || uname -s |grep -i windows_nt || \
uname -s |grep -i HP-UX`" ]
then
ofiles=`ulimit -S -n`
maxfiles=`ulimit -H -n`
if [ "$?" = "0" -a `expr ${maxfiles} : '[0-9][0-9]*$'` -eq 0 -a `expr ${ofiles} : '[0-9][0-9]*$'` -eq 0 ]; then
ulimit -n 4096
else
if [ "$?" = "0" -a `uname -s` = "SunOS" -a `expr ${maxfiles} : '[0-9][0-9]*$'` -eq 0 ]; then
if [ ${ofiles} -lt 65536 ]; then
ulimit -H -n 65536
else
ulimit -H -n ${ofiles}
fi
fi
fi
fi
# Get actual Derby process when running in MKS/NT environment;
# Trap SIGINT
# input:
# DERBY_PID -- Derby server process id.
# output:
# DERBY_PID -- Actual Derby pid in MKS/NT environment.
trapSIGINT() {
# With MKS, the pid of $! dosen't show up correctly.
# It starts a shell process to launch whatever commands it calls.
if [ `uname -s` = "Windows_NT" ]; then
DERBY_PID=`ps -eo pid,ppid |
awk -v DERBY_PID=${DERBY_PID} '$2 == DERBY_PID {print $1}'`
POINTBASE_PID=`ps -eo pid,ppid |
awk -v POINTBASE_PID=${POINTBASE_PID} '$2 == POINTBASE_PID {print $1}'`
fi
# Kill Derby on interrupt from this script (^C)
trap 'if [ "${DERBY_PID}" != "" ]; then
kill -9 ${DERBY_PID}
unset DERBY_PID
fi' 2
trap 'if [ "${POINTBASE_PID}" != "" ]; then
kill -9 ${POINTBASE_PID}
unset POINTBASE_PID
fi' 2
# end of sub functions
# Set up BEA Home
BEA_HOME="/bea/wls"
# Set up Middleware Home
MW_HOME="/bea/wls"
# Set up WebLogic Home
WL_HOME="/bea/wls/wlserver_10.3"
# Set up COHERENCE Home
COHERENCE_HOME="/bea/wls/coherence_3.6"
# Set up Common Modules Directory
MODULES_DIR="/bea/wls/modules"
# Set up Common Features Directory
FEATURES_DIR="/bea/wls/modules/features"
# Set up Ant Home
ANT_HOME="${MODULES_DIR}/org.apache.ant_1.7.1"
# Set up Ant contrib
ANT_CONTRIB="${MODULES_DIR}/net.sf.antcontrib_1.1.0.0_1-0b2"
# Setup SUN_ARCH_DATA_MODEL
SUN_ARCH_DATA_MODEL="32"
#JAVA_USE_64BIT, true if JVM uses 64 bit operations
JAVA_USE_64BIT=false
# Reset JAVA_HOME, JAVA_VENDOR and PRODUCTION_MODE unless JAVA_HOME
# and JAVA_VENDOR are pre-defined.
if [ -z "${JAVA_HOME}" -o -z "${JAVA_VENDOR}" ]; then
# Set up JAVA HOME
JAVA_HOME="/usr/jdk/instances/jdk1.7.0_05"
# Set up JAVA VENDOR, possible values are
#Oracle, HP, IBM, Sun ...
JAVA_VENDOR=Oracle
# PRODUCTION_MODE, default to the development mode
PRODUCTION_MODE=""
fi
export BEA_HOME MW_HOME WL_HOME MODULES_DIR FEATURES_DIR COHERENCE_HOME ANT_HOME ANT_CONTRIB JAVA_HOME JAVA_VENDOR PRODUCTION_MODE JAVA_USE_64BIT
# Set up JVM options base on value of JAVA_VENDOR
if [ "$PRODUCTION_MODE" = "true" ]; then
case $JAVA_VENDOR in
Oracle)
JAVA_VM=-server
MEM_ARGS="-Xms128m -Xmx256m"
HP)
JAVA_VM=-server
MEM_ARGS="-Xms32m -Xmx200m -XX:MaxPermSize=128m"
IBM)
JAVA_VM=
MEM_ARGS="-Xms32m -Xmx200m"
Sun)
JAVA_VM=-server
MEM_ARGS="-Xms32m -Xmx200m -XX:MaxPermSize=128m"
Apple)
JAVA_VM=-server
MEM_ARGS="-Xms32m -Xmx200m -XX:MaxPermSize=128m"
JAVA_VM=
MEM_ARGS="-Xms32m -Xmx200m"
esac
else
case $JAVA_VENDOR in
Oracle)
JAVA_VM=-server
MEM_ARGS="-Xms128m -Xmx256m"
-Xms512m -Xmx512m -XX:MaxPermSize=256m
JAVA_OPTIONS="${JAVA_OPTIONS} -Xverify:none"
HP)
JAVA_VM=-client
MEM_ARGS="-Xms32m -Xmx200m -XX:MaxPermSize=128m"
IBM)
JAVA_VM=
MEM_ARGS="-Xms32m -Xmx200m"
Sun)
JAVA_VM=-client
MEM_ARGS="-Xms32m -Xmx200m -XX:MaxPermSize=128m"
JAVA_OPTIONS="${JAVA_OPTIONS} -Xverify:none"
Apple)
JAVA_VM=-client
MEM_ARGS="-Xms32m -Xmx200m -XX:MaxPermSize=128m"
JAVA_VM=
MEM_ARGS="-Xms32m -Xmx200m"
esac
fi
export JAVA_VM MEM_ARGS JAVA_OPTIONS
# Set the classpath separator
case `uname -s` in
Windows_NT*)
CLASSPATHSEP=\;
PATHSEP=\;
CYGWIN*)
CLASSPATHSEP=\;
esac
if [ "${CLASSPATHSEP}" = "" ]; then
CLASSPATHSEP=:
fi
if [ "${PATHSEP}" = "" ]; then
PATHSEP=:
fi
export PATHSEP CLASSPATHSEP
# Set-up patch related class path, extension dirs, library path and path options
if [ -f "${WL_HOME}/common/bin/setPatchEnv.sh" ]; then
. "${WL_HOME}"/common/bin/setPatchEnv.sh
fi
# Figure out how to load java native libraries, also add -d64 for hpux and solaris 64 bit arch.
case `uname -s` in
AIX)
if [ -n "${LIBPATH}" ]; then
if [ "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
LIBPATH=${LIBPATH}:${WL_HOME}/server/native/aix/ppc64
else
LIBPATH=${LIBPATH}:${WL_HOME}/server/native/aix/ppc
fi
else
if [ "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
LIBPATH=${WL_HOME}/server/native/aix/ppc64
else
LIBPATH=${WL_HOME}/server/native/aix/ppc
fi
fi
LIBPATH=${PATCH_LIBPATH}:${LIBPATH}
export LIBPATH
HP-UX)
arch=`uname -m`
if [ "${arch}" = "ia64" ]; then
if [ -n "${SHLIB_PATH}" ]; then
if [ "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
SHLIB_PATH=${SHLIB_PATH}:${WL_HOME}/server/native/hpux11/IPF64:${WL_HOME}/server/native/hpux11/IPF64/oci920_8
else
SHLIB_PATH=${SHLIB_PATH}:${WL_HOME}/server/native/hpux11/IPF32:${WL_HOME}/server/native/hpux11/IPF32/oci920_8
fi
else
if [ "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
SHLIB_PATH=${WL_HOME}/server/native/hpux11/IPF64:${WL_HOME}/server/native/hpux11/IPF64/oci920_8
else
SHLIB_PATH=${WL_HOME}/server/native/hpux11/IPF32:${WL_HOME}/server/native/hpux11/IPF32/oci920_8
fi
fi
else
if [ -n "${SHLIB_PATH}" ]; then
if [ "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
SHLIB_PATH=${SHLIB_PATH}:${WL_HOME}/server/native/hpux11/PA_RISC64:${WL_HOME}/server/native/hpux11/PA_RISC64/oci920_8
else
SHLIB_PATH=${SHLIB_PATH}:${WL_HOME}/server/native/hpux11/PA_RISC:${WL_HOME}/server/native/hpux11/PA_RISC/oci920_8
fi
else
if [ "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
SHLIB_PATH=${WL_HOME}/server/native/hpux11/PA_RISC64:${WL_HOME}/server/native/hpux11/PA_RISC64/oci920_8
else
SHLIB_PATH=${WL_HOME}/server/native/hpux11/PA_RISC:${WL_HOME}/server/native/hpux11/PA_RISC/oci920_8
fi
fi
fi
SHLIB_PATH=${PATCH_LIBPATH}:${SHLIB_PATH}
export SHLIB_PATH
if [ "${JAVA_USE_64BIT}" = "true" ] && [ "${JAVA_VENDOR}" != "Oracle" ]
then
JVM_D64="-d64"
export JVM_D64
JAVA_VM="${JAVA_VM} ${JVM_D64}"
export JAVA_VM
fi
LINUX|Linux)
arch=`uname -m`
if [ -n "${LD_LIBRARY_PATH}" ]; then
if [ "${arch}" = "ia64" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/linux/ia64:${WL_HOME}/server/native/linux/ia64/oci920_8
else
if [ "${arch}" = "x86_64" -a "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/linux/${arch}:${WL_HOME}/server/native/linux/${arch}/oci920_8
if [ "$SIP_ENABLED" = "true" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WLSS_HOME}/server/native/linux/${arch}:${WLSS_HOME}/server/native/linux/${arch}/oci920_8
fi
else
if [ "${arch}" = "s390x" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/linux/s390x
else
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/linux/i686:${WL_HOME}/server/native/linux/i686/oci920_8
fi
if [ "$SIP_ENABLED" = "true" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WLSS_HOME}/server/native/linux/i686:${WLSS_HOME}/server/native/linux/i686/oci920_8
fi
fi
fi
else
if [ "${arch}" = "ia64" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/linux/ia64:${WL_HOME}/server/native/linux/ia64/oci920_8
else
if [ "${arch}" = "x86_64" -a "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
LD_LIBRARY_PATH=${WL_HOME}/server/native/linux/${arch}:${WL_HOME}/server/native/linux/${arch}/oci920_8
if [ "$SIP_ENABLED" = "true" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WLSS_HOME}/server/native/linux/${arch}:${WLSS_HOME}/server/native/linux/${arch}/oci920_8
fi
else
if [ "${arch}" = "s390x" ]; then
LD_LIBRARY_PATH=${WL_HOME}/server/native/linux/s390x
else
LD_LIBRARY_PATH=${WL_HOME}/server/native/linux/i686:${WL_HOME}/server/native/linux/i686/oci920_8
fi
if [ "$SIP_ENABLED" = "true" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WLSS_HOME}/server/native/linux/i686:${WLSS_HOME}/server/native/linux/i686/oci920_8
fi
fi
fi
fi
LD_LIBRARY_PATH=${PATCH_LIBPATH}:${LD_LIBRARY_PATH}
export LD_LIBRARY_PATH
OSF1)
if [ -n "${LD_LIBRARY_PATH}" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/tru64unix
else
LD_LIBRARY_PATH=${WL_HOME}/server/native/tru64unix
fi
LD_LIBRARY_PATH=${PATCH_LIBPATH}:${LD_LIBRARY_PATH}
export LD_LIBRARY_PATH
SunOS)
arch=`uname -m`
if [ -n "${LD_LIBRARY_PATH}" ]; then
if [ "${arch}" = "i86pc" ]; then
if [ "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/solaris/x64
else
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/solaris/x86
fi
else
if [ "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/solaris/sparc64:${WL_HOME}/server/native/solaris/sparc64/oci920_8
if [ "$SIP_ENABLED" = "true" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WLSS_HOME}/server/native/solaris/sparc64:${WLSS_HOME}/server/native/solaris/sparc64/oci920_8
fi
else
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/solaris/sparc:${WL_HOME}/server/native/solaris/sparc/oci920_8
if [ "$SIP_ENABLED" = "true" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WLSS_HOME}/server/native/solaris/sparc:${WLSS_HOME}/server/native/solaris/sparc/oci920_8
fi
fi
fi
else
if [ "${arch}" = "i86pc" ]; then
if [ "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
LD_LIBRARY_PATH=${WL_HOME}/server/native/solaris/x64
else
LD_LIBRARY_PATH=${WL_HOME}/server/native/solaris/x86
fi
else
if [ "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
LD_LIBRARY_PATH=${WL_HOME}/server/native/solaris/sparc64:${WL_HOME}/server/native/solaris/sparc64/oci920_8
if [ "$SIP_ENABLED" = "true" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WLSS_HOME}/server/native/solaris/sparc64:${WLSS_HOME}/server/native/solaris/sparc64/oci920_8
fi
else
LD_LIBRARY_PATH=${WL_HOME}/server/native/solaris/sparc:${WL_HOME}/server/native/solaris/sparc/oci920_8
if [ "$SIP_ENABLED" = "true" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WLSS_HOME}/server/native/solaris/sparc:${WLSS_HOME}/server/native/solaris/sparc/oci920_8
fi
fi
fi
fi
LD_LIBRARY_PATH=${PATCH_LIBPATH}:${LD_LIBRARY_PATH}
export LD_LIBRARY_PATH
if [ "${JAVA_USE_64BIT}" = "true" ] && [ "${JAVA_VENDOR}" != "Oracle" ]
then
JVM_D64="-d64"
export JVM_D64
JAVA_VM="${JAVA_VM} ${JVM_D64}"
export JAVA_VM
fi
Darwin)
if [ -n "${DYLD_LIBRARY_PATH}" ]; then
DYLD_LIBRARY_PATH=${DYLD_LIBRARY_PATH}:${WL_HOME}/server/native/macosx
else
DYLD_LIBRARY_PATH=${WL_HOME}/server/native/macosx
fi
DYLD_LIBRARY_PATH=${PATCH_LIBPATH}:${DYLD_LIBRARY_PATH}
export DYLD_LIBRARY_PATH
Windows_NT*) ;;
CYGWIN*) ;;
echo "$0: Don't know how to set the shared library path for `uname -s`. "
esac
# set up WebLogic Server's class path
WEBLOGIC_CLASSPATH="${JAVA_HOME}/lib/tools.jar${CLASSPATHSEP}${WL_HOME}/server/lib/weblogic_sp.jar${CLASSPATHSEP}${WL_HOME}/server/lib/weblogic.jar${CLASSPATHSEP}${FEATURES_DIR}/weblogic.server.modules_10.3.4.0.jar${CLASSPATHSEP}${WL_HOME}/server/lib/webservices.jar${CLASSPATHSEP}${ANT_HOME}/lib/ant-all.jar${CLASSPATHSEP}${ANT_CONTRIB}/lib/ant-contrib.jar"
export WEBLOGIC_CLASSPATH
# set up config tools class path
FMWCONFIG_CLASSPATH="${JAVA_HOME}/lib/tools.jar${CLASSPATHSEP}${BEA_HOME}/utils/config/10.3/config-launch.jar${CLASSPATHSEP}${WL_HOME}/server/lib/weblogic_sp.jar${CLASSPATHSEP}${WL_HOME}/server/lib/weblogic.jar${CLASSPATHSEP}${FEATURES_DIR}/weblogic.server.modules_10.3.4.0.jar${CLASSPATHSEP}${WL_HOME}/server/lib/webservices.jar${CLASSPATHSEP}${ANT_HOME}/lib/ant-all.jar${CLASSPATHSEP}${ANT_CONTRIB}/lib/ant-contrib.jar"
export FMWCONFIG_CLASSPATH
FMWLAUNCH_CLASSPATH="${BEA_HOME}/utils/config/10.3/config-launch.jar"
export FMWLAUNCH_CLASSPATH
if [ "${PATCH_CLASSPATH}" != "" ] ; then
WEBLOGIC_CLASSPATH="${PATCH_CLASSPATH}${CLASSPATHSEP}${WEBLOGIC_CLASSPATH}"
export WEBLOGIC_CLASSPATH
FMWCONFIG_CLASSPATH="${PATCH_CLASSPATH}${CLASSPATHSEP}${FMWCONFIG_CLASSPATH}"
export FMWCONFIG_CLASSPATH
fi
if [ "$SIP_ENABLED" = "true" ]; then
# set up SIP classpath
SIP_CLASSPATH="${WLSS_HOME}/server/lib/weblogic_sip.jar"
# add to WLS class path
WEBLOGIC_CLASSPATH="${WEBLOGIC_CLASSPATH}${CLASSPATHSEP}${SIP_CLASSPATH}"
export WEBLOGIC_CLASSPATH
FMWCONFIG_CLASSPATH="${FMWCONFIG_CLASSPATH}${CLASSPATHSEP}${SIP_CLASSPATH}"
export FMWCONFIG_CLASSPATH
fi
# DERBY configuration
DERBY_HOME="${WL_HOME}/common/derby"
DERBY_CLIENT_CLASSPATH="${DERBY_HOME}/lib/derbyclient.jar"
DERBY_CLASSPATH="${CLASSPATHSEP}${DERBY_HOME}/lib/derbynet.jar${CLASSPATHSEP}${DERBY_CLIENT_CLASSPATH}"
DERBY_TOOLS="${DERBY_HOME}/lib/derbytools.jar"
DERBY_SYSTEM_HOME=${WL_HOME}/common/derby/demo/databases
DERBY_OPTS="-Dderby.system.home=$DERBY_SYSTEM_HOME"
if [ "${DERBY_PRE_CLASSPATH}" != "" ] ; then
DERBY_CLASSPATH="${DERBY_PRE_CLASSPATH}${CLASSPATHSEP}${DERBY_CLASSPATH}"
fi
if [ "${DERBY_POST_CLASSPATH}" != "" ] ; then
DERBY_CLASSPATH="${DERBY_CLASSPATH}${CLASSPATHSEP}${DERBY_POST_CLASSPATH}"
fi
export DERBY_HOME DERBY_CLASSPATH DERBY_TOOLS DERBY_SYSTEM_HOME DERBY_OPTS
if [ -d "${WL_HOME}/common/eval/pointbase" ]
then
# PointBase configuration
POINTBASE_HOME="${WL_HOME}/common/eval/pointbase"
POINTBASE_CLIENT_CLASSPATH="${POINTBASE_HOME}/lib/pbclient57.jar"
POINTBASE_CLASSPATH="${CLASSPATHSEP}${POINTBASE_HOME}/lib/pbembedded57.jar${CLASSPATHSEP}${POINTBASE_CLIENT_CLASSPATH}"
POINTBASE_TOOLS="${POINTBASE_HOME}/lib/pbtools57.jar"
if [ "${POINTBASE_PRE_CLASSPATH}" != "" ] ; then
POINTBASE_CLASSPATH="${POINTBASE_PRE_CLASSPATH}${CLASSPATHSEP}${POINTBASE_CLASSPATH}"
fi
if [ "${POINTBASE_POST_CLASSPATH}" != "" ] ; then
POINTBASE_CLASSPATH="${POINTBASE_CLASSPATH}${CLASSPATHSEP}${POINTBASE_POST_CLASSPATH}"
fi
export POINTBASE_HOME POINTBASE_CLASSPATH POINTBASE_TOOLS
fi
# Set up PATH
if [ `uname -s` = "CYGWIN32/NT" ]; then
# If we are on an old version of Cygnus we need to turn <letter>:/ in the path
# to //<letter>/
WL_HOME_CYGWIN=`echo $WL_HOME | sed 's#\([a-zA-Z]\):#//\1#g'`
ANT_HOME_CYGWIN=`echo $ANT_HOME | sed 's#\([a-zA-Z]\):#//\1#g'`
ANT_CONTRIB_CYGWIN=`echo $ANT_CONTRIB | sed 's#\([a-zA-Z]\):#//\1#g'`
JAVA_HOME_CYGWIN=`echo $JAVA_HOME | sed 's#\([a-zA-Z]\):#//\1#g'`
PATCH_PATH_CYGWIN=`echo $PATCH_PATH | sed 's#\([a-zA-Z]\):#//\1#g'`
WL_USE_X86DLL=
WL_USE_IA64DLL=
WL_USE_AMD64DLL=
if [ "${WL_USE_IA64DLL}" = "true" ]; then
PATH="${PATCH_PATH_CYGWIN}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/64${PATHSEP}${WL_HOME_CYGWIN}/server/bin${PATHSEP}${ANT_HOME_CYGWIN}/bin${PATHSEP}${JAVA_HOME_CYGWIN}/jre/bin${PATHSEP}${JAVA_HOME_CYGWIN}/bin${PATHSEP}${PATH}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/64/oci920_8"
fi
if [ "${WL_USE_X86DLL}" = "true" ]; then
PATH="${PATCH_PATH_CYGWIN}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/32${PATHSEP}${WL_HOME_CYGWIN}/server/bin${PATHSEP}${ANT_HOME_CYGWIN}/bin${PATHSEP}${JAVA_HOME_CYGWIN}/jre/bin${PATHSEP}${JAVA_HOME_CYGWIN}/bin${PATHSEP}${PATH}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/32/oci920_8"
fi
if [ "${WL_USE_AMD64DLL}" = "true" ]; then
PATH="${PATCH_PATH_CYGWIN}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/x64${PATHSEP}${WL_HOME_CYGWIN}/server/bin${PATHSEP}${ANT_HOME_CYGWIN}/bin${PATHSEP}${JAVA_HOME_CYGWIN}/jre/bin${PATHSEP}${JAVA_HOME_CYGWIN}/bin${PATHSEP}${PATH}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/x64/oci920_8"
fi
else
if [ -n "`uname -s |grep -i cygwin_`" ]; then
# If we are on an new version of Cygnus we need to turn <letter>:/ in
# the path to /cygdrive/<letter>/
CYGDRIVE=`mount -ps | tail -1 | awk '{print $1}' | sed -e 's%/$%%'`
WL_HOME_CYGWIN=`echo $WL_HOME | sed "s#\([a-zA-Z]\):#${CYGDRIVE}/\1#g"`
ANT_HOME_CYGWIN=`echo $ANT_HOME | sed "s#\([a-zA-Z]\):#${CYGDRIVE}/\1#g"`
PATCH_PATH_CYGWIN=`echo $PATCH_PATH | sed "s#\([a-zA-Z]\):#${CYGDRIVE}/\1#g"`
JAVA_HOME_CYGWIN=`echo $JAVA_HOME | sed "s#\([a-zA-Z]\):#${CYGDRIVE}/\1#g"`
WL_USE_X86DLL=
WL_USE_IA64DLL=
WL_USE_AMD64DLL=
if [ "${WL_USE_IA64DLL}" = "true" ]; then
PATH="${PATCH_PATH_CYGWIN}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/64${PATHSEP}${WL_HOME_CYGWIN}/server/bin${PATHSEP}${ANT_HOME_CYGWIN}/bin${PATHSEP}${JAVA_HOME_CYGWIN}/jre/bin${PATHSEP}${JAVA_HOME_CYGWIN}/bin${PATHSEP}${PATH}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/64/oci920_8"
fi
if [ "${WL_USE_X86DLL}" = "true" ]; then
PATH="${PATCH_PATH_CYGWIN}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/32${PATHSEP}${WL_HOME_CYGWIN}/server/bin${PATHSEP}${ANT_HOME_CYGWIN}/bin${PATHSEP}${JAVA_HOME_CYGWIN}/jre/bin${PATHSEP}${JAVA_HOME_CYGWIN}/bin${PATHSEP}${PATH}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/32/oci920_8"
fi
if [ "${WL_USE_AMD64DLL}" = "true" ]; then
PATH="${PATCH_PATH_CYGWIN}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/x64${PATHSEP}${WL_HOME_CYGWIN}/server/bin${PATHSEP}${ANT_HOME_CYGWIN}/bin${PATHSEP}${JAVA_HOME_CYGWIN}/jre/bin${PATHSEP}${JAVA_HOME_CYGWIN}/bin${PATHSEP}${PATH}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/x64/oci920_8"
fi
else
# set PATH for other shell environments
PATH="${WL_HOME}/server/bin${PATHSEP}${ANT_HOME}/bin${PATHSEP}${JAVA_HOME}/jre/bin${PATHSEP}${JAVA_HOME}/bin${PATHSEP}${PATH}"
# On Windows, include WebLogic jDriver in PATH
if [ -n "`uname -s |grep -i windows_nt`" ]; then
WL_USE_X86DLL=
WL_USE_IA64DLL=
WL_USE_AMD64DLL=
if [ "${WL_USE_IA64DLL}" = "true" ]; then
PATH="${PATCH_PATH}${PATHSEP}${WL_HOME}/server/native/win/64${PATHSEP}${PATH}${PATHSEP}${WL_HOME}/server/native/win/64/oci920_8"
fi
if [ "${WL_USE_AMD64DLL}" = "true" ]; then
PATH="${PATCH_PATH}${PATHSEP}${WL_HOME}/server/native/win/x64${PATHSEP}${PATH}${PATHSEP}${WL_HOME}/server/native/win/x64/oci920_8"
fi
if [ "${WL_USE_X86DLL}" = "true" ]; then
PATH="${PATCH_PATH}${PATHSEP}${WL_HOME}/server/native/win/32${PATHSEP}${PATH}${PATHSEP}${WL_HOME}/server/native/win/32/oci920_8"
fi
fi
fi
fi
export PATH
resetFd
=======
my system is not on production mode and using oracle java. please suggest -
Getting error while starting Managed server in clustered environment
Hi All,
I created a cluster in weblogic 9.2 and two manged servers under that cluster through WLST scripts.
I started Node manager through connecting WLST and now when i am starting the managed servers its giving the following error :
wls:/Dist_3/serverConfig> start('managed1','Server')
Starting server managed1 ....NMProcess: <Jan 30, 2009 2:57:27 PM> <Warning> <I/O
error while reading domain directory: java.io.FileNotFoundException: Domain dir
ectory 'C:\bea\weblogic92\common\bin' invalid (domain salt file not found)>
NMProcess: java.io.FileNotFoundException: Domain directory 'C:\bea\weblogic92\co
mmon\bin' invalid (domain salt file not found)
NMProcess: at weblogic.nodemanager.server.DomainManager.initialize(DomainMa
nager.java:80)
NMProcess: at weblogic.nodemanager.server.DomainManager.<init>(DomainManage
r.java:52)
NMProcess: at weblogic.nodemanager.server.NMServer.getDomainManager(NMServe
r.java:242)
NMProcess: at weblogic.nodemanager.server.Handler.handleDomain(Handler.java
:212)
NMProcess: at weblogic.nodemanager.server.Handler.handleCommand(Handler.jav
a:105)
NMProcess: at weblogic.nodemanager.server.Handler.run(Handler.java:66)
NMProcess: at java.lang.Thread.run(Thread.java:595)
NMProcess:
I/O error while reading domain directory: java.io.FileNotFoundException: Domain
directory 'C:\bea\weblogic92\common\bin' invalid (domain salt file not found)
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 1250, in start
WLSTException: 'Error occured while performing start : Error starting the server
Error occured while performing start : Server with name managed1 failed to be st
arted Use dumpStack() to view the full stacktrace'
wls:/Dist_3/serverConfig> start('managed2','Server')
Starting server managed2 ....NMProcess: <Jan 30, 2009 3:05:51 PM> <Warning> <I/O
error while reading domain directory: java.io.FileNotFoundException: Domain dir
ectory 'C:\bea\weblogic92\common\bin' invalid (domain salt file not found)>
NMProcess: java.io.FileNotFoundException: Domain directory 'C:\bea\weblogic92\co
mmon\bin' invalid (domain salt file not found)
NMProcess: at weblogic.nodemanager.server.DomainManager.initialize(DomainMa
nager.java:80)
NMProcess: at weblogic.nodemanager.server.DomainManager.<init>(DomainManage
r.java:52)
NMProcess: at weblogic.nodemanager.server.NMServer.getDomainManager(NMServe
r.java:242)
NMProcess: at weblogic.nodemanager.server.Handler.handleDomain(Handler.java
:212)
NMProcess: at weblogic.nodemanager.server.Handler.handleCommand(Handler.jav
a:105)
NMProcess: at weblogic.nodemanager.server.Handler.run(Handler.java:66)
NMProcess: at java.lang.Thread.run(Thread.java:595)
NMProcess:
I/O error while reading domain directory: java.io.FileNotFoundException: Domain
directory 'C:\bea\weblogic92\common\bin' invalid (domain salt file not found)
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 1250, in start
WLSTException: 'Error occured while performing start : Error starting the server
Error occured while performing start : Server with name managed2 failed to be st
arted Use dumpStack() to view the full stacktrace'
wls:/Dist_3/serverConfig>hi kartheek,
i think u just missed some of steps while starting managed server using nodemanager in WLST.
If u dont mind i'm sending some of steps just check it out. Once u try the same steps.
1.start the ADMIN SERVER
2.start the WLST
java weblogic.WLST
3.Connect to AdminServer
connect('username',password','t3://adminhost:listenport')
example: connect('weblogic','weblogic','t3://localhost:7001')
4.start the nodemanager in WLST
startNodeManager()
5.connect to nodemanager
nmConnect('username','password','nodemanagerhost',
'nodemanagerlistenport','domainname','path to domain')
example: nmConnect('weblogic','weblogic','localhost','5556','base_domain'
'C:/bea/user_projects/domains/base_domain')
6.start the managed server in WLST
start('managedservername','Type','t3://managedhost:listenport')
example:start('man1','Server','t3://localhost:7003')
7.If u want to start cluster in WLST
start('clustername','Type')
example: start('cluster1','Cluster')
If u want to start managed in Cluster u follow STEP-6 only
regards
abhi -
Error starting managed server in weblogic
am having this error wne starting managed server
C:\mydomain\base_domain\bin>startManagedWebLogic.cmd madimad-b533821
JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=
128m -XX:MaxPermSize=512m
WLS Start Mode=Development
CLASSPATH=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jdbc_11.1.1\ojdbc6dms.jar;C
:\PROGRA~1\Java\JDK16~1.0_2\lib\tools.jar;C:\mywls\wlserver\server\lib\weblogic_
sp.jar;C:\mywls\wlserver\server\lib\weblogic.jar;C:\mywls\modules\features\weblo
gic.server.modules_10.3.4.0.jar;C:\mywls\wlserver\server\lib\webservices.jar;C:\
mywls\modules\ORGAPA~1.1/lib/ant-all.jar;C:\mywls\modules\NETSFA~1.0_1/lib/ant-c
ontrib.jar;C:\oracle\Middleware\wlserver_10.3\sip\server\lib\weblogic_sip.jar;C:
\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrf.jar;C:\mywls\wlserver\co
mmon\derby\lib\derbyclient.jar;C:\mywls\wlserver\server\lib\xqrl.jar
PATH=;C:\mywls\wlserver\server\native\win\32;C:\mywls\wlserver\server\bin;C:\myw
ls\modules\ORGAPA~1.1\bin;C:\PROGRA~1\Java\JDK16~1.0_2\jre\bin;C:\PROGRA~1\Java\
JDK16~1.0_2\bin;C:\Program Files\PC Connectivity Solution\;C:\product\11.2.0\dbh
ome_1\bin;C:\product\11.2.0\dbhome_1;C:\forms;C:\DevSuiteHome_1\jlib;C:\Program
Files\PHP;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Fil
es\Common Files\Roxio Shared\DLLShared;C:\Program Files\Common Files\Roxio Share
d\DLLShared;C:\Program Files\Common Files\Roxio Shared\9.0\DLLShared;C:\Program
Files\Common Files\DivX Shared;c:\Program Files\Java\jdk1.6.0_21\bin;C:\Program
Files\Common Files\Roxio Shared\10.0\DLLShared;C:\Program Files\Common Files\Rox
io Shared\DLLShared;C:\Program Files\Common Files\Roxio Shared\10.0\DLLShared;C:
\mywls;C:\mydomain\base_domain\bin;C:\Program Files\Java\jre6\bin\client;C:\Prog
ram Files\Java\jre6\bin;C:\Program Files\Java\jdk1.6.0_21\jre\bin;C:\Program Fil
es\Java\jdk1.6.0_21\bin;C:\Program Files\Java\jdk1.6.0_21;C:\Program Files\Java\
jre6;C:\DevSuiteHome_1\forms;C:\DevSuiteHome_1\cgenf61\admin;C:\DevSuiteHome_1\f
orms;C:\forms\sms_code.pll;C:\mywls\wlserver;C:\Java\jdk1.6.0_21;C:\mywls\wlserv
er\server\native\win\32\oci920_8
* 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.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b07)
Java HotSpot(TM) Client VM (build 17.0-b17, mixed mode)
Starting WLS with line:
C:\PROGRA~1\Java\JDK16~1.0_2\bin\java -client -Xms256m -Xmx512m -XX:CompileThr
eshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=madimad-b533
821 -Djava.security.policy=C:\mywls\wlserver\server\lib\weblogic.policy -Dweblog
ic.security.SSL.trustedCAKeyStore="C:\mywls\wlserver\server\lib\cacerts" -Xveri
fy:none -ea:com.bea.wcp... -da -Dplatform.home=C:\mywls\wlserver -Dwls.home=C:
\mywls\wlserver\server -Dweblogic.home=C:\mywls\wlserver\server -Dcommon.compon
ents.home=C:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.
logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=C:\mydomai
n\BASE_D~1 -Djrockit.optfile=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1
.1\jrocket_optfile.txt -Doracle.server.config.dir=C:\mydomain\BASE_D~1\config\FM
WCON~1\servers\madimad-b533821 -Doracle.domain.config.dir=C:\mydomain\BASE_D~1\c
onfig\FMWCON~1 -Digf.arisidbeans.carmlloc=C:\mydomain\BASE_D~1\config\FMWCON~1\
carml -Digf.arisidstack.home=C:\mydomain\BASE_D~1\config\FMWCON~1\arisidprovide
r -Doracle.security.jps.config=C:\mydomain\BASE_D~1\config\fmwconfig\jps-config.
xml -Doracle.deployed.app.dir=C:\mydomain\BASE_D~1\servers\madimad-b533821\tmp\_
WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=C:\Oracl
e\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\ORACLE~1\mo
dules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.prot
ocol -Dweblogic.jdbc.remoteEnabled=false -Dweblogic.management.discover=false
-Dweblogic.management.server=http://madimad-b533821:7001 -Dwlw.iterativeDev=fal
se -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false weblogic.Server
<24 Jan 2014 12:52:41 PM> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE
Provider self-integrity check for better startup performance. To enable this che
ck, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<24 Jan 2014 12:52:42 PM> <Info> <Security> <BEA-090906> <Changing the default R
andom Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable thi
s change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<24 Jan 2014 12:52:42 PM> <Notice> <WebLogicServer> <BEA-000395> <Following exte
nsions directory contents added to the end of the classpath:
C:\mydomain\base_domain\lib\sipactivator.jar>
<24 Jan 2014 12:52:42 PM> <Info> <Server> <BEA-002647> <The service plugin, com.
oracle.core.sip.activator, was added from C:\mydomain\base_domain\lib\sipactivat
or.jar.>
<24 Jan 2014 12:52:42 PM> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogi
c Server with Java HotSpot(TM) Client VM Version 17.0-b17 from Sun Microsystems
Inc.>
<24 Jan 2014 12:52:45 PM> <Info> <Security> <BEA-090065> <Getting boot identity
from user.>
Enter username to boot WebLogic server:tshifhiwa
Enter password to boot WebLogic server:
<24 Jan 2014 12:52:57 PM> <Info> <Management> <BEA-141107> <Version: WebLogic Se
rver 10.3.4.0 Fri Dec 17 20:47:33 PST 2010 1384255 >
<24 Jan 2014 12:53:01 PM> <Error> <Management> <BEA-141252> <The domain version,
10.3.5.0, is greater than the release version, 10.3.4.0, of this server.>
<24 Jan 2014 12:53:01 PM> <Error> <Configuration Management> <BEA-150001> <An er
ror occurred while connecting to the admin server to bootstrap through URL: http
://madimad-b533821:7001/bea_wls_management_internal2/Bootstrap, user: tshifhiwa
weblogic.management.configuration.ConfigurationException: [Management:141252]The
domain version, 10.3.5.0, is greater than the release version, 10.3.4.0, of thi
s server.
at weblogic.management.provider.internal.BootStrapHelper.getBootStrapStr
uct(BootStrapHelper.java:147)
at weblogic.management.provider.internal.RuntimeAccessImpl.initialize(Ru
ntimeAccessImpl.java:432)
at weblogic.management.provider.internal.RuntimeAccessService.start(Runt
imeAccessService.java:49)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesMan
ager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServ
icesManager.java:166)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:879)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:566)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:467)
at weblogic.Server.main(Server.java:71)
>
<24 Jan 2014 12:53:01 PM> <Notice> <WebLogicServer> <BEA-000365> <Server state c
hanged to STARTING>
<24 Jan 2014 12:53:01 PM> <Info> <WorkManager> <BEA-002900> <Initializing self-t
uning thread pool>
<24 Jan 2014 12:53:02 PM> <Notice> <LoggingService> <BEA-320400> <The log file C
:\mydomain\base_domain\servers\madimad-b533821\logs\madimad-b533821.log will be
rotated. Reopen the log file if tailing has stopped. This can happen on some pla
tforms like Windows.>
<24 Jan 2014 12:53:02 PM> <Notice> <LoggingService> <BEA-320401> <The log file h
as been rotated to C:\mydomain\base_domain\servers\madimad-b533821\logs\madimad-
b533821.log00007. Log messages will continue to be logged in C:\mydomain\base_do
main\servers\madimad-b533821\logs\madimad-b533821.log.>
<24 Jan 2014 12:53:02 PM> <Notice> <Log Management> <BEA-170019> <The server log
file C:\mydomain\base_domain\servers\madimad-b533821\logs\madimad-b533821.log i
s opened. All server side log events will be written to this file.>
<24 Jan 2014 12:54:25 PM> <Critical> <WebLogicServer> <BEA-000386> <Server subsy
stem failed. Reason: java.lang.AssertionError: Assertion violated
java.lang.AssertionError: Assertion violated
at weblogic.utils.Debug.assertion(Debug.java:57)
at weblogic.server.channels.ChannelService.getServerChannel(ChannelServi
ce.java:2060)
at weblogic.server.channels.ChannelService.getServerChannel(ChannelServi
ce.java:1998)
at weblogic.protocol.ServerChannelManager.findServerChannel(ServerChanne
lManager.java:76)
at weblogic.ldap.EmbeddedLDAP.findLdapURL(EmbeddedLDAP.java:1482)
Truncated. see log file for complete stacktrace
>
<24 Jan 2014 12:54:26 PM> <Notice> <WebLogicServer> <BEA-000365> <Server state c
hanged to FAILED>
<24 Jan 2014 12:54:26 PM> <Error> <WebLogicServer> <BEA-000383> <A critical serv
ice failed. The server will shut itself down>
<24 Jan 2014 12:54:26 PM> <Notice> <WebLogicServer> <BEA-000365> <Server state c
hanged to FORCE_SHUTTING_DOWN>Hi,
there are two thing in this issue.
first
It looks like the upgrade which you done is not happen correctly.
Revert the back the upgrade and restart the the server again.
Second
rename the Ldap folder of you managed server and restart the server again.
Regards,
Kal -
Facing error in starting managed server from nodemanager
Hi All,
I have installed WebLogic server 10.3.4 and installed OSB 11.1.1.4.0. I created domain with one admin server and one managed server for osb. When I started managed server with the startManagedWebLogic command it got started successfully but when I am trying tp start the managed server from nodemanager I am getting the following error
starting weblogic with Java version:
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
[ERROR] aborted
JRockit aborted: Unknown error (50)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
Starting WLS with line:
D:\JDK\JROCKI~1.0\bin\java -jrockit -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms256m -Xmx512m -Dweblogic.Name=osb_server1 -Djava.security.policy=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=D:\Oracle_OSB\Middleware\user_projects\domains\osb_domain\servers\osb_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xverify:none -da:org.apache.xmlbeans... -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3 -Dwls.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server -Dcommon.components.home=D:\ORACLE~1\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1 -Djrockit.optfile=D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\servers\osb_server1 -Doracle.domain.config.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\carml -Digf.arisidstack.home=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\servers\osb_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dem.oracle.home=D:\Oracle_OSB\Middleware\oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=false -Dweblogic.management.server=http://soaspt-app01.scotwat.net:7010 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=D:\ORACLE~1\MIDDLE~1\patch_wls1034\profiles\default\sysext_manifest_classpath;D:\ORACLE~1\MIDDLE~1\patch_ocp360\profiles\default\sysext_manifest_classpath weblogic.Server
[WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
[ERROR] aborted
JRockit aborted: Unknown error (50)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
<11-Mar-2013 13:22:17> <FINEST> <NodeManager> <Waiting for the process to die: 5916>
<11-Mar-2013 13:22:17> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<11-Mar-2013 13:22:17> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
My nodemanager is started and reachable. The error above says "Address already in use" but I am able to start my managed server through startManagedWebLogic.cmd command.
Can anyone please tell me what could be the issue. It is really urgent. Please help!!Hi Roshni,
It is likely that a configuration is missing or not set properly in the Node Manager properties file (nodemanager.properties) since the managed server can be started up using startManagedWebLogic.cmd but not with Node Manager. I would complete the following steps to fix the problem:
1. Go to %WLS_HOME%\common\nodemanager and open up nodemanager.properties (Make a backup of the file first). NOTE: WLS_HOME is your WebLogic Server home.
2. Look for the parameters "StartScriptEnabled" and "StopScriptEnabled". They should be set to true. If not, please set them to true.
3. Save and close the file.
4. Restart the Node Manager
If you are still unable to start the manager server using Node Manager, you may need to update the DEBUG_PORT parameter in setDomainEnv.cmd located in %MIDDLEWARE_HOME%\user_projects\domains\%DOMAIN_HOME%\bin (always make a backup before changing a configuration file). You may refer to Oracle Support note 1272642.1 for more information about the nodemanager.properties file and how to configure the DEBUG_PORT parameter in setDomainEnv.cmd if needed.
Thanks,
Scott (PITSS)
http://pitss.com/us -
Getting error while starting Managed Server
Hi All,
I configured Custered environment in Weblogic 9.2 to use in ALSB.
While starting managed server i am getting error :
<Critical> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666363188> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:941)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1029)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
####<Feb 3, 2009 6:36:04 PM IST> <Notice> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666364234> <BEA-000365> <Server state changed to FAILED>
####<Feb 3, 2009 6:36:04 PM IST> <Error> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666364234> <BEA-000383> <A critical service failed. The server will shut itself down>
####<Feb 3, 2009 6:36:04 PM IST> <Notice> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666364594> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<Feb 3, 2009 6:36:04 PM IST> <Info> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666364891> <BEA-000236> <Stopping execute threads.>
Can anybody pls guide me to solve this erro.
Thanks,
KartheekThis statement should be prominently displayed in this and all similar forums, but the best advice I can give anyone here is that if you're struggling with a problem for several DAYS, not to mention weeks, and the only resource you've used is this forum, you should file a support request with Oracle right now. That is one of the most important skills you will need to use WebLogic effectively.
-
Getting error while starting Managed server configured in ALSB(ClusteredEnv
Hi All,
I configured Custered environment in Weblogic 9.2 to use in ALSB.
While starting managed server i am getting error :
<Critical> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666363188> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:941)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1029)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
####<Feb 3, 2009 6:36:04 PM IST> <Notice> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666364234> <BEA-000365> <Server state changed to FAILED>
####<Feb 3, 2009 6:36:04 PM IST> <Error> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666364234> <BEA-000383> <A critical service failed. The server will shut itself down>
####<Feb 3, 2009 6:36:04 PM IST> <Notice> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666364594> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<Feb 3, 2009 6:36:04 PM IST> <Info> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666364891> <BEA-000236> <Stopping execute threads.>
Can anybody pls guide me to solve this erro.
Thanks,
KartheekYou probably changed your system password in the console?
Look for your boot.properties file in the following location:
[domain]\servers\[server]\security
change the following line:
password={3DES}Ytm72Oh4zE0bsptrYn13Xw==
to:
password=mynewpassword
WebLogic Server will encrypt the password on the next boot, and your problem should be resolved. -
Error start managed server from admin console in SSL mode
I have configured Admin server, managed servers and node manager on the same physical server and commonly using a single SSL sertificate.
There is no problem to start node manager, admin server and managed server individually. But if I try to start managed server from the admin console then I am getting the following errors.
<Feb 22, 2005 11:02:26 AM CST> <Info> <[email protected]:6666> <Starting Server peoplesoft::PIA1 ...>
<Feb 22, 2005 11:02:26 AM CST> <Info> <NodeManager@xxxxxxxxxx:6666> <BaseProcessControl: saving process id of Weblogic Managed server 'PIA1', pid: 285390>
<Feb 22, 2005 11:02:35 AM CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Classic VM Version 1.4.1 from IBM Corporation>
<Feb 22, 2005 11:02:36 AM CST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://xxxxxxxx:admin_server_portnumber to check if there exists a running admin server at this URL.>
<Feb 22, 2005 11:02:36 AM CST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Feb 22, 2005 11:02:36 AM CST> <Info> <Management> <BEA-141107> <Version: WebLogic Temporary Patch 8 CR174605 for PeopleSoft 09/09/2004 18:11:35
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 >
<Feb 22, 2005 11:02:37 AM CST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://xxxxxxxxx.org:Admin_server_portnumber to retrieve the initial configuration.>
<Feb 22, 2005 11:02:45 AM CST> <Notice> <Log Management> <BEA-170019> <The server log file /home/xxxx/webserv/peoplesoft/PIA1/PIA1.log is opened. All server side log events will be written to this file.>
<Feb 22, 2005 11:03:01 AM CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Feb 22, 2005 11:03:01 AM CST> <Warning> <Security> <BEA-090066> <Problem handling boot identity. The following exception was generated: java.lang.NullPointerException>
<Feb 22, 2005 11:03:10 AM CST> <Critical> <Security> <BEA-090174> <The trust keystore configuration specified on the command line or in boot.properties does not match the trust keystore configuration specified in config.xml.>
<Feb 22, 2005 11:03:10 AM CST> <Warning> <NodeManager> <BEA-300038> <The node manager is unable to monitor this server. Could not create an SSL connection to the node manager. Reason : null>
<Feb 22, 2005 11:03:10 AM CST> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.>
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.'
Reason: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.
I am running everything on IBM UNIX server.
I appriciate your help.
Thanks & regards,
Laxman.Hi
From the admin console ... Are you able to check the status of Node Manager ?
If yes ... please check the SSL configuration of managed servers ...
Check the domain administration port also.
Jin -
A lot of problem for an error: Cannot start Managed Server through NM
Hi, all. Thank for coming here.
My main problem is cannot start Manager server through Node Manager. I've configured with the same way on my friend's network and It's works but It's wrong with mine.
my weblogic domain:
Machine 1: Administration Server + 1 Managed server
Machine 2: 1 Managed server
all of these servers communicate through SSL protocol. When I try to start Managed Server on remote machine:
output from console which was invoked startWebLogic.sh
+<Sep 9, 2010 12:09:53 PM> <INFO> <devdomain> <MS01> <Server failed during startup so will not be restarted>+
Sep 9, 2010 12:09:53 PM weblogic.nodemanager.server.ServerManager log
INFO: Server failed during startup so will not be restarted
+<Sep 9, 2010 12:09:53 PM> <WARNING> <Exception while starting server 'MS01'>+
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:619)
Sep 9, 2010 12:09:53 PM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'MS01'
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:619)
And this is MS01 log:
starting weblogic with Java version:
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
+JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]+
The application has requested the JVM to exit with an fatal error from JNI. Error message:
JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
Starting WLS with line:
+/opt/Oracle/Middleware/jrockit_160_14_R27.6.5-32/bin/java -jrockit -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms512m -Xmx512m -Dweblogic.Name=MS01 -Djava.security.policy=/opt/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.system.BootIdentityFile=/opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.ReverseDNSAllowed=false -Xrs -Xverify:none -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=/opt/Oracle/Middleware/wlserver_10.3 -Dwls.home=/opt/Oracle/Middleware/wlserver_10.3/server -Dweblogic.home=/opt/Oracle/Middleware/wlserver_10.3/server -Dweblogic.wsee.bind.suppressDeployErrorMessage=true -Dweblogic.wsee.skip.async.response=true -Dweblogic.management.discover=false -Dweblogic.management.server=http://192.168.1.35:7001 -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.logErrorsToConsole=true -Dweblogic.ext.dirs=/opt/Oracle/Middleware/patch_wls1032/profiles/default/sysext_manifest_classpath:/opt/Oracle/Middleware/patch_wlp1032/profiles/default/sysext_manifest_classpath:/opt/Oracle/Middleware/wlportal_10.3/p13n/lib/system:/opt/Oracle/Middleware/wlportal_10.3/light-portal/lib/system:/opt/Oracle/Middleware/wlportal_10.3/portal/lib/system:/opt/Oracle/Middleware/wlportal_10.3/info-mgmt/lib/system:/opt/Oracle/Middleware/wlportal_10.3/analytics/lib/system:/opt/Oracle/Middleware/wlportal_10.3/apps/lib/system:/opt/Oracle/Middleware/wlportal_10.3/info-mgmt/deprecated/lib/system:/opt/Oracle/Middleware/wlportal_10.3/content-mgmt/lib/system -Dweblogic.alternateTypesDirectory=/opt/Oracle/Middleware/wlportal_10.3/portal/lib/security weblogic.Server+
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
+JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]+
The application has requested the JVM to exit with an fatal error from JNI. Error message:
JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
Stopping PointBase server...
PointBase server stopped.
And this is output from console which node manager runs on:
+<Sep 9, 2010 12:09:53 PM> <INFO> <devdomain> <MS01> <Server failed during startup so will not be restarted>+
Sep 9, 2010 12:09:53 PM weblogic.nodemanager.server.ServerManager log
INFO: Server failed during startup so will not be restarted
+<Sep 9, 2010 12:09:53 PM> <WARNING> <Exception while starting server 'MS01'>+
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:619)
Sep 9, 2010 12:09:53 PM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'MS01'
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:619)
I tried to start Managed server some times again, but I face up to strange issue, this is output from console which Admin Server runs on (these exception messages throws continuously):
+<Sep 9, 2010 12:42:53 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "portalDataSourceNeverXA": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
+<Sep 9, 2010 12:42:57 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "cgDataSource": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
+<Sep 9, 2010 12:42:58 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "cgDataSource-nonXA": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
+<Sep 9, 2010 12:42:58 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "p13nDataSource": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
+<Sep 9, 2010 12:42:58 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "portalDataSource": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
+<Sep 9, 2010 12:42:58 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "portalDataSourceAlwaysXA": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
I can ensure that all of these connection pool has configured to run on 9093 port already. Then I view the DOMAIN_NAME/pointbase.log, it said:
Unable to start the server. start server error: java.net.BindException: Address already in use
I cannot understand what's run on pointbase address ?
All of these error make me angry, because I've configured with the same way on other system and It's work. I've spent all of week to fix these bug, but I'm having nothing :((
Please help me.Thank Jay SenSharma.
I've looked for these JAVA_OPTION values you said, but I cant found them. That value is content of JAVA_DEBUG option, not JAVA_OPTION. In my situation, JAVA_DEBUG=" " (it's not set by default).
Please re-view my error log:
Node Manager output:
+<Sep 9, 2010 11:32:44 PM> <WARNING> <Exception while starting server 'MS01'>+
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:619)
Sep 9, 2010 11:32:44 PM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'MS01'
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:619)
Managed server MS01's log:
+<Sep 9, 2010 11:45:05 PM> <INFO> <NodeManager> <Server output log file is '/opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/logs/MS01.out'>+
+<Sep 9, 2010 11:45:07 PM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.5-32_o-121899-1.6.0_14-20091001-2113-linux-ia32 from BEA Systems, Inc.>+
+<Sep 9, 2010 11:45:09 PM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server Temporary Patch for 9216172 Tue Jan 12 02:07:27 PST 2010+
WebLogic Server 10.3.2.0 Tue Oct 20 12:16:15 PDT 2009 1267925 >
+<Sep 9, 2010 11:45:13 PM EDT> <Error> <Management> <BEA-141244> <Schema validation errors while parsing /opt/Oracle/Middleware/user_projects/domains/devdomain/config/config.xml - Invalid xsi:type qname: 'wsrp:wsrp-identity-asserterType' in element realm@http://xmlns.oracle.com/weblogic/domain>+
+<Sep 9, 2010 11:45:13 PM EDT> <Error> <Management> <BEA-141244> <Schema validation errors while parsing /opt/Oracle/Middleware/user_projects/domains/devdomain/config/config.xml - /opt/Oracle/Middleware/user_projects/domains/devdomain/<unknown>:11:9: error: failed to load java type corresponding to t=wsrp-identity-asserterType@http://www.bea.com/ns/wlp/90/security/wsrp>+
+<Sep 9, 2010 11:45:14 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>+
+<Sep 9, 2010 11:45:14 PM EDT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>+
+<Sep 9, 2010 11:45:14 PM EDT> <Notice> <LoggingService> <BEA-320400> <The log file /opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/logs/MS01.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>+
+<Sep 9, 2010 11:45:14 PM EDT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/logs/MS01.log00002. Log messages will continue to be logged in /opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/logs/MS01.log.>+
+<Sep 9, 2010 11:45:14 PM EDT> <Notice> <Log Management> <BEA-170019> <The server log file /opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/logs/MS01.log is opened. All server side log events will be written to this file.>+
+<Sep 9, 2010 11:45:17 PM EDT> <Error> <Security> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal internal error> org.apache.openjpa.util.InternalException: There was an error when invoking the static getInstance method on the named factory class "kodo.jdbc.kernel.KodoJDBCBrokerFactory". See the nested exception for details..+
weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal internal error> org.apache.openjpa.util.InternalException: There was an error when invoking the static getInstance method on the named factory class "kodo.jdbc.kernel.KodoJDBCBrokerFactory". See the nested exception for details.
+ at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:342)+
+ at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:221)+
+ at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1783)+
+ at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)+
+ at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)+
+ Truncated. see log file for complete stacktrace+
Caused By: com.bea.common.engine.ServiceInitializationException: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal internal error> org.apache.openjpa.util.InternalException: There was an error when invoking the static getInstance method on the named factory class "kodo.jdbc.kernel.KodoJDBCBrokerFactory". See the nested exception for details.
+ at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:365)+
+ at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)+
+ at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)+
+ at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)+
+ at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:47)+
+ Truncated. see log file for complete stacktrace+
Caused By: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal internal error> org.apache.openjpa.util.InternalException: There was an error when invoking the static getInstance method on the named factory class "kodo.jdbc.kernel.KodoJDBCBrokerFactory". See the nested exception for details.
+ at org.apache.openjpa.kernel.Bootstrap.getBrokerFactory(Bootstrap.java:95)+
+ at com.bea.common.security.storeservice.util.StoreServiceDelegate$StoreSerivceHelper.getPersistenceManagerFactory(StoreServiceDelegate.java:347)+
+ at com.bea.common.security.storeservice.util.StoreServiceDelegate.initJDO(StoreServiceDelegate.java:145)+
+ at com.bea.common.security.storeservice.util.StoreServiceDelegate.<init>(StoreServiceDelegate.java:98)+
+ at com.bea.common.security.internal.service.StoreServiceImpl.init(StoreServiceImpl.java:76)+
+ Truncated. see log file for complete stacktrace+
Caused By: java.lang.RuntimeException: There were errors initializing your configuration: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal store error> org.apache.openjpa.util.StoreException: com.pointbase.jdbc.jdbcUniversalDriver
+ at org.apache.openjpa.jdbc.schema.DataSourceFactory.newDataSource(DataSourceFactory.java:123)+
+ at org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.createConnectionFactory(JDBCConfigurationImpl.java:776)+
+ at org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(JDBCConfigurationImpl.java:683)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)+
+ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)+
+ at java.lang.reflect.Method.invoke(Method.java:597)+
+ at org.apache.openjpa.lib.conf.ConfigurationImpl.instantiateAll(ConfigurationImpl.java:288)+
+ at org.apache.openjpa.conf.OpenJPAConfigurationImpl.instantiateAll(OpenJPAConfigurationImpl.java:1409)+
+ at org.apache.openjpa.kernel.AbstractBrokerFactory.makeReadOnly(AbstractBrokerFactory.java:646)+
+ at org.apache.openjpa.kernel.AbstractBrokerFactory.pool(AbstractBrokerFactory.java:131)+
+ at kodo.jdbc.kernel.KodoJDBCBrokerFactory.getInstance(KodoJDBCBrokerFactory.java:43)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)+
+ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)+
+ at java.lang.reflect.Method.invoke(Method.java:597)+
+ at org.apache.openjpa.kernel.Bootstrap.invokeFactory(Bootstrap.java:124)+
+ at org.apache.openjpa.kernel.Bootstrap.getBrokerFactory(Bootstrap.java:90)+
+ at com.bea.common.security.storeservice.util.StoreServiceDelegate$StoreSerivceHelper.getPersistenceManagerFactory(StoreServiceDelegate.java:347)+
+ at com.bea.common.security.storeservice.util.StoreServiceDelegate.initJDO(StoreServiceDelegate.java:145)+
+ at com.bea.common.security.storeservice.util.StoreServiceDelegate.<init>(StoreServiceDelegate.java:98)+
+ at com.bea.common.security.internal.service.StoreServiceImpl.init(StoreServiceImpl.java:76)+
+ at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363)+
+ at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)+
+ at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)+
+ at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)+
+ at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:47)+
+ at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:300)+
+ at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:221)+
+ at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1783)+
+ at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)+
+ at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)+
+ at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)+
+ at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)+
+ at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)+
+ at weblogic.security.SecurityService.start(SecurityService.java:141)+
+ at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)+
+ at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)+
+ at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)+
Caused by: java.lang.ClassNotFoundException: com.pointbase.jdbc.jdbcUniversalDriver
+ at java.lang.Class.forName0(Native Method)+
+ at java.lang.Class.forName(Class.java:169)+
+ at org.apache.openjpa.jdbc.schema.DataSourceFactory.newDataSource(DataSourceFactory.java:85)+
+ ... 38 more+
+ at org.apache.openjpa.lib.conf.ConfigurationImpl.instantiateAll(ConfigurationImpl.java:302)+
+ at org.apache.openjpa.conf.OpenJPAConfigurationImpl.instantiateAll(OpenJPAConfigurationImpl.java:1409)+
+ at org.apache.openjpa.kernel.AbstractBrokerFactory.makeReadOnly(AbstractBrokerFactory.java:646)+
+ at org.apache.openjpa.kernel.AbstractBrokerFactory.pool(AbstractBrokerFactory.java:131)+
+ at kodo.jdbc.kernel.KodoJDBCBrokerFactory.getInstance(KodoJDBCBrokerFactory.java:43)+
+ Truncated. see log file for complete stacktrace+
+>+
+<Sep 9, 2010 11:45:17 PM EDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>+
+<Sep 9, 2010 11:45:17 PM EDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:+
There are 1 nested errors:
+weblogic.security.service.SecurityServiceRuntimeException: [Security:090399]Security Services Unavailable+
+ at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:916)+
+ at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)+
+ at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)+
+ at weblogic.security.SecurityService.start(SecurityService.java:141)+
+ at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)+
+ at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)+
+ at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)+
+>+
+<Sep 9, 2010 11:45:17 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>+
+<Sep 9, 2010 11:45:17 PM EDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>+
+<Sep 9, 2010 11:45:17 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>+
+<Sep 9, 2010 11:45:17 PM> <FINEST> <NodeManager> <Waiting for the process to die: 16443>+
+<Sep 9, 2010 11:45:17 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>+
+<Sep 9, 2010 11:45:18 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>+
ps:
I've come your weblog and found alot of tips for debugging WebLogic Server exceptions. It's really helpful. Thanks.
Edited by: Doubt_Man on Sep 10, 2010 10:49 AM
Edited by: Doubt_Man on Sep 10, 2010 3:54 PM -
Starting managed server with nodemanager
Hi there,
Please help me with the weblogic server installation, i've studk with failed to start managed server with node manager. My scenario as below:
(1) set up the main server and able to run the server successfully.
(2) set up one managed server, set up one machine on same server as main server.
(3) assign machine to created managed server.
(4) after that i've tried to run that managed server and error giving as below:
Error from main server terminal
===================
<NodeManager> <BEA-300048> <Unable to start the server 'ManagedServer1': Exception while starting server 'ManagedServer1': java.io.IOException: Server failed to start up. See server output log for more details.>
Error from Node Manager Termal
====================
<Info> <MainServer> <'ManagedServer1'> <Server failed during startup so will not be restarted>
<Dec 7, 2009 7:04:45 PM> <Warning> <Exception while starting server ''ManagedServer1'': java.io.IOException: Server failed to start up. See server output log for more details.>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:303)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:542)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
at weblogic.nodemanager.server.Handler.run(Handler.java:66)
at java.lang.Thread.run(Thread.java:619)
Thanks in advance,
TimSorry , i forgot to mention that the OS i am using is Solaris.
Thx
Maybe you are looking for
-
Engineer visit re: new infinity order need urgent ...
i ordered Infinity yesterday and received all teh relevant emails from BT confirming order. One email states the engineer will visit from 13:00 and 18:00 Ive just check the status of my order and it now states the followin info where previously a tim
-
Is there any way to open an iMovie HD file with iMovie 4?
Subject said it all. My daughter did her iMovie homework on our home computer. When she took the iMovie HD file to school it wouldn't open with their older version of iMovie. Any suggestions? Thanks, lw
-
Object Link to Engineering Record from DIR
Hello Gurus, With respect to the below post. I did the config setting and I see only the CASE GUID showing up and not the Engineering Record number. PLM7 Engineering Record not working as expected And also I am not able to navigate to my ER from the
-
This occurs upon initial boot up and no other users are on. No other firefox is running. The current version will then open without issue. Just want to warning removed
-
Multiple destination tables, oracle sequence problems
Hello, Please look at this sql - there is 2 steps to add data to 2 destination tables: - step1: INSERT INTO OBIEKTY (ID_OB, TELEFON, FAX, NR_LOKALU, UWAGI, ULICA, GEOM, NR_BUDYNKU, KOD_POCZTOWY, LISTA_OBIEKTOW, EMAIL, GMINA, NAZWA, WOJEWODZTWO, MIEJS