Problems starting Managed Server on WL6.0 Solaris
Hi,
I installed a WL6.0 on Solaris 8. Everythings works fine.
I careated a Domain and an additional Server wich is located at a
different machine. As is start this managed server on the other machine
it complains with the following error message:
<Aug 30, 2001 12:41:18 PM CEST> <Info> <Security> <Getting boot password
from user.>
Enter password to boot WebLogic server:weblogic
Starting WebLogic Server ....
Connecting to http://sol23:7001...
The WebLogic Server did not start up properly.
Exception raised:
weblogic.management.configuration.ConfigurationException: paros not
found
weblogic.management.configuration.ConfigurationException: paros not
found
at
weblogic.management.Admin.getBootstrapLocalServer(Admin.java:927)
at weblogic.management.Admin.initialize(Admin.java:287)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:317)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
In the access-Log of the Admin-Server the following line appears
my IP - - [30/Aug/2001:12:41:13 +0200] "GET
/wl_management_internal2/Bootstrap HTTP/1.0" 404 0
So my question: Where does this "wl_management_internal2" Application
come from?
Do I have to install some special things when I start an Admin-Server?
thanks
Falko Zurell . Webmaster
Pixelpark AG . http://www.pixelpark.com
Rotherstrasse 8 . 10245 Berlin . Germany
phone: + 49 30 5058 - 1963 . fax: -1600
Hi Falko,
This is not a problem. when you want to add a new managed server to the
admin server, you need to use weblogic console to create that server in the
admin server first, then start the managed server with that name to connect
to the admin server. That is like you have to let the admin server know
there is such a server, then let it join to the Admin server. you can do
that by using the admin console, from left panel, click on Servers -->
"Create a new server" and name it to be "paros", specify the port and IP.
and hit "create". then start the managed server.
Thanks
Yu
"Falko Zurell" <[email protected]> wrote in message
news:[email protected]...
Hi,
I installed a WL6.0 on Solaris 8. Everythings works fine.
I careated a Domain and an additional Server wich is located at a
different machine. As is start this managed server on the other machine
it complains with the following error message:
<Aug 30, 2001 12:41:18 PM CEST> <Info> <Security> <Getting boot password
from user.>
Enter password to boot WebLogic server:weblogic
Starting WebLogic Server ....
Connecting to http://sol23:7001...
The WebLogic Server did not start up properly.
Exception raised:
weblogic.management.configuration.ConfigurationException: paros not
found
weblogic.management.configuration.ConfigurationException: paros not
found
at
weblogic.management.Admin.getBootstrapLocalServer(Admin.java:927)
at weblogic.management.Admin.initialize(Admin.java:287)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:317)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
>
In the access-Log of the Admin-Server the following line appears
my IP - - [30/Aug/2001:12:41:13 +0200] "GET
/wl_management_internal2/Bootstrap HTTP/1.0" 404 0
So my question: Where does this "wl_management_internal2" Application
come from?
Do I have to install some special things when I start an Admin-Server?
thanks
Falko Zurell . Webmaster
Pixelpark AG . http://www.pixelpark.com
Rotherstrasse 8 . 10245 Berlin . Germany
phone: + 49 30 5058 - 1963 . fax: -1600
Similar Messages
-
Has anyone managed to setup a WLS 7.0 Active Directory authenticator and booted
a managed server using the node manager? I can boot the server without the AD
authenticator and I can also boot the server using a script and successfully authenticate
through AD. My AD control flag is set to OPTIONAL and I have also setup a default
authenticator to boot weblogic - the control flag here is set to SUFFICIENT. This
configuration works fine with weblogic running on W2K, but not on Solaris (it
looks like the control flag is being ignored). Errors as follows
####<Oct 1, 2002 1:59:08 PM BST> <Info> <Logging> <mymachine> <server01> <main>
<kernel identity> <> <000000> <FileLo
gger Opened at /opt/app/live/appserver/domains/test/NodeManager/server01/server01.log>
####<Oct 1, 2002 1:59:09 PM BST> <Info> <socket> <mymachine> <server01> <main>
<kernel identity> <> <000415> <System
has file descriptor limits of - soft: 1,024, hard: 1,024>
####<Oct 1, 2002 1:59:09 PM BST> <Info> <socket> <mymachine> <server01> <main>
<kernel identity> <> <000416> <Using e
ffective file descriptor limit of: 1,024 open sockets/files.>
####<Oct 1, 2002 1:59:09 PM BST> <Info> <socket> <mymachine> <server01> <main>
<kernel identity> <> <000418> <Allocat
ing: 3 POSIX reader threads>
####<Oct 1, 2002 1:59:19 PM BST> <Critical> <WebLogicServer> <mymachine> <server01>
<main> <kernel identity> <> <0003
64> <Server failed during initialization. Exception:weblogic.security.service.SecurityServiceRuntimeException:
Problem instantiating
Authentication Providerjavax.management.RuntimeOperationsException: RuntimeException
thrown by the getAttribute method of the Dynam
icMBean for the attribute Credential>
weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
Authentication Providerjavax.management.RuntimeOper
ationsException: RuntimeException thrown by the getAttribute method of the DynamicMBean
for the attribute Credential
at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:186)
at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:236)
at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1506)
at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1308)
at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1247)
at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1364)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1107)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
####<Oct 1, 2002 1:59:19 PM BST> <Emergency> <WebLogicServer> <mymachine> <server01>
<main> <kernel identity> <> <000
342> <Unable to initialize the server: Fatal initialization exception
Throwable: weblogic.security.service.SecurityServiceRuntimeException: Problem
instantiating Authentication Providerjavax.management.
RuntimeOperationsException: RuntimeException thrown by the getAttribute method
of the DynamicMBean for the attribute Credential
weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
Authentication Providerjavax.management.RuntimeOper
ationsException: RuntimeException thrown by the getAttribute method of the DynamicMBean
for the attribute Credential
at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:186)
at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:236)
at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1506)
at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1308)
at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1247)
at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1364)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1107)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)Solved the problem. The 'domain root' directory specified in the remote start configuration,
must contain a copy of the file 'SerializedSystemIni.dat' that was created along
with the domain, in order to boot when an AD authenticator is configured. If an
AD authenticator is not configured, no file is required. This was not a platform
specific issue; on Win2K I had configured the 'domain root' remote start parameter
to point to an existing domain root and not a new directory.
"Andrew Walker" <[email protected]> wrote:
>
Has anyone managed to setup a WLS 7.0 Active Directory authenticator
and booted
a managed server using the node manager? I can boot the server without
the AD
authenticator and I can also boot the server using a script and successfully
authenticate
through AD. My AD control flag is set to OPTIONAL and I have also setup
a default
authenticator to boot weblogic - the control flag here is set to SUFFICIENT.
This
configuration works fine with weblogic running on W2K, but not on Solaris
(it
looks like the control flag is being ignored). Errors as follows
####<Oct 1, 2002 1:59:08 PM BST> <Info> <Logging> <mymachine> <server01>
<main>
<kernel identity> <> <000000> <FileLo
gger Opened at /opt/app/live/appserver/domains/test/NodeManager/server01/server01.log>
####<Oct 1, 2002 1:59:09 PM BST> <Info> <socket> <mymachine> <server01>
<main>
<kernel identity> <> <000415> <System
has file descriptor limits of - soft: 1,024, hard: 1,024>
####<Oct 1, 2002 1:59:09 PM BST> <Info> <socket> <mymachine> <server01>
<main>
<kernel identity> <> <000416> <Using e
ffective file descriptor limit of: 1,024 open sockets/files.>
####<Oct 1, 2002 1:59:09 PM BST> <Info> <socket> <mymachine> <server01>
<main>
<kernel identity> <> <000418> <Allocat
ing: 3 POSIX reader threads>
####<Oct 1, 2002 1:59:19 PM BST> <Critical> <WebLogicServer> <mymachine>
<server01>
<main> <kernel identity> <> <0003
64> <Server failed during initialization. Exception:weblogic.security.service.SecurityServiceRuntimeException:
Problem instantiating
Authentication Providerjavax.management.RuntimeOperationsException:
RuntimeException
thrown by the getAttribute method of the Dynam
icMBean for the attribute Credential>
weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
Authentication Providerjavax.management.RuntimeOper
ationsException: RuntimeException thrown by the getAttribute method of
the DynamicMBean
for the attribute Credential
at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:186)
at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:236)
at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1506)
at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1308)
at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1247)
at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1364)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1107)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
####<Oct 1, 2002 1:59:19 PM BST> <Emergency> <WebLogicServer> <mymachine>
<server01>
<main> <kernel identity> <> <000
342> <Unable to initialize the server: Fatal initialization exception
Throwable: weblogic.security.service.SecurityServiceRuntimeException:
Problem
instantiating Authentication Providerjavax.management.
RuntimeOperationsException: RuntimeException thrown by the getAttribute
method
of the DynamicMBean for the attribute Credential
weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
Authentication Providerjavax.management.RuntimeOper
ationsException: RuntimeException thrown by the getAttribute method of
the DynamicMBean
for the attribute Credential
at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:186)
at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:236)
at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1506)
at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1308)
at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1247)
at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1364)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1107)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31) -
Problem starting managed server (WL6.1sp2)
I'm trying to staret a managed server, but keep getting errors fetching the
configuration from the admin server?
Right after the first error message, it says"> This condition generally
results when the managed and admin servers are using the same listen address
and port.>"
However, this is not the case here. Any ideas?
The managed server and the admin server uses the same password,
"adminpassword" (yes, this is an internal development system :-)
Here's the error message:
C:\bea\wlserver6.1>"C:\bea\jdk131\bin\java" -hotspot -ms64m -mx64m -classpat
h
".;.\lib\weblogic_sp.jar;.\lib\weblogic.jar" -Dweblogic.Domain=wavetech -Dbe
a.home=C:\bea -Dweblogic.management.password=adminpassword -Dweblogic.Produc
tionModeEnabled=false -Dweblogic.Name=cbfilter -Dweblogic.management.server=
http://192.168.10.31:6001/ -Djava.security.policy=C:\bea\wlserver6.1/lib/web
logic.policy weblogic.Server
Starting WebLogic Server ....
Connecting to http://192.168.10.31:6001/...
<08-03-2002 14:22:49 CET> <Emergency> <Configuration Management> <Errors
detected attempting to connect to admin server at http://192.168.10.31:6001/
during initialization of managed server ( 192.168.10.85:80 ). The reported
error was: < weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
> This condition generally results when the managed and admin servers are
using the same listen address and port.>
<08-03-2002 14:22:49 CET> <Emergency> <Server> <Unable to initialize the
server: 'Fatal initialization exception
Throwable: weblogic.management.configuration.ConfigurationException:
weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException:
weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:988)
at weblogic.management.Admin.start(Admin.java:363)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:375)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
'>
The WebLogic Server did not start up properly.
Exception raised:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException:
weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:988)
at weblogic.management.Admin.start(Admin.java:363)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:375)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
C:\bea\wlserver6.1>cd config\wavetech
C:\bea\wlserver6.1\config\wavetech>ENDLOCALI'm trying to staret a managed server, but keep getting errors fetching the
configuration from the admin server?
Right after the first error message, it says"> This condition generally
results when the managed and admin servers are using the same listen address
and port.>"
However, this is not the case here. Any ideas?
The managed server and the admin server uses the same password,
"adminpassword" (yes, this is an internal development system :-)
Here's the error message:
C:\bea\wlserver6.1>"C:\bea\jdk131\bin\java" -hotspot -ms64m -mx64m -classpat
h
".;.\lib\weblogic_sp.jar;.\lib\weblogic.jar" -Dweblogic.Domain=wavetech -Dbe
a.home=C:\bea -Dweblogic.management.password=adminpassword -Dweblogic.Produc
tionModeEnabled=false -Dweblogic.Name=cbfilter -Dweblogic.management.server=
http://192.168.10.31:6001/ -Djava.security.policy=C:\bea\wlserver6.1/lib/web
logic.policy weblogic.Server
Starting WebLogic Server ....
Connecting to http://192.168.10.31:6001/...
<08-03-2002 14:22:49 CET> <Emergency> <Configuration Management> <Errors
detected attempting to connect to admin server at http://192.168.10.31:6001/
during initialization of managed server ( 192.168.10.85:80 ). The reported
error was: < weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
> This condition generally results when the managed and admin servers are
using the same listen address and port.>
<08-03-2002 14:22:49 CET> <Emergency> <Server> <Unable to initialize the
server: 'Fatal initialization exception
Throwable: weblogic.management.configuration.ConfigurationException:
weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException:
weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:988)
at weblogic.management.Admin.start(Admin.java:363)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:375)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
'>
The WebLogic Server did not start up properly.
Exception raised:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException:
weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:988)
at weblogic.management.Admin.start(Admin.java:363)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:375)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
C:\bea\wlserver6.1>cd config\wavetech
C:\bea\wlserver6.1\config\wavetech>ENDLOCAL -
Problem starting managed server using Node Manager/WL 7
I have just configured Node Manager for the first time to start a managed server,
following the documentation 'Managing Server Availability with Node Manager'. However
when I attempt to start the managed server from the Administration Console I always
get the following exception:
<Jul 10, 2002 1:59:29 PM EDT> <Info> <[email protected]:5555> <Starting
Server webdevDomain::apps ...>
<Jul 10, 2002 1:59:29 PM EDT> <Info> <[email protected]:5555> <BaseProcessControl:
saving process id of Weblogic Managed server 'apps', pid: 15094>
Starting WebLogic Server...
Connecting to http://198.242.140.49:17043...
<Jul 10, 2002 1:59:32 PM EDT> <Critical> <WebLogicServer> <000364> <Server failed
during initialization. Exception:weblogic.management.configuration.ConfigurationException:
Exception encountered connecting to http://198.242.140.49:17043/wl_management_internal2/Bootstrap
- with nested exception:
[java.io.StreamCorruptedException: InputStream does not contain a serialized object]
java.io.StreamCorruptedException: InputStream does not contain a serialized object
at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:844)
at java.io.ObjectInputStream.<init>(ObjectInputStream.java:163)
at weblogic.management.ManagedServerAdmin.bootstrapLocalServer(ManagedServerAdmin.java:212)
at weblogic.management.ManagedServerAdmin.initialize(ManagedServerAdmin.java:122)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:665)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
But I am able to start the managed server using the startApps.sh script with no problems.
I am running WL 7 on Solaris 2.8. All processes are running on the same host.
Any help is appreciated!
JohnRe-installing WL Server 7.0.0.1 resolved this problem.
- John -
Problems starting managed server via nodemanager
Hello,
I have a WebLogic 6.1 SP2 installation on two Solaris 8 maschines.
One hosts the admin server and the seconds hosts a managed server.
I installed the nodemanager on both maschines. They seems to run
normally.
I configured the "Remot Start" for the managed server as mentioned in
the manual. I didn't specified any values in that panel because the
nodemanager uses the same environment as the WLS so these values should
fit the managed WLS too.
But as I try to start the managed server I got the following error
message:
Starting WebLogic Server ....
Child exited
The WebLogic Server did not start up properly.
Exception raised:
java.lang.NoClassDefFoundError: java/lang/reflect/InvocationHandler
at weblogic.management.Admin.initialize(Admin.java:279)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
So I specified some basic values on the "Remote Start" panel:
BEA_HOME: /www/apps/bea/
ROOT_DIR: /www/apps/bea/wlserver6.1
CLASSPATH:
/www/apps/bea/wlserver6.1/lib/weblogic_sp.jar:/www/apps/bea/wlserver6.1/lib/weblogic.jar
No I got this message:
Starting WebLogic Server ....
The WebLogic Server did not start up properly.
Exception raised:
java.lang.NoClassDefFoundError: java/lang/reflect/InvocationHandler
at weblogic.management.Admin.initialize(Admin.java:279)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
Child exited
What did I wrong?
Has anybody experiences on this problem?
Thanks !
Falko Zurell - Webmaster
Pixelpark AG
Germanynodemanager must be using the old jvm (1.2.2 or whatever comes by
default with 2.8). set up the environment or modify
startNodeManager.sh so that it uses java 1.3.1 that ships with WLS6.1
o.
Falko Zurell <[email protected]> wrote in message news:<[email protected]>...
Hello,
I have a WebLogic 6.1 SP2 installation on two Solaris 8 maschines.
One hosts the admin server and the seconds hosts a managed server.
I installed the nodemanager on both maschines. They seems to run
normally.
I configured the "Remot Start" for the managed server as mentioned in
the manual. I didn't specified any values in that panel because the
nodemanager uses the same environment as the WLS so these values should
fit the managed WLS too.
But as I try to start the managed server I got the following error
message:
Starting WebLogic Server ....
Child exited
The WebLogic Server did not start up properly.
Exception raised:
java.lang.NoClassDefFoundError: java/lang/reflect/InvocationHandler
at weblogic.management.Admin.initialize(Admin.java:279)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
So I specified some basic values on the "Remote Start" panel:
BEA_HOME: /www/apps/bea/
ROOT_DIR: /www/apps/bea/wlserver6.1
CLASSPATH:
/www/apps/bea/wlserver6.1/lib/weblogic_sp.jar:/www/apps/bea/wlserver6.1/lib/weblogic.jar
No I got this message:
Starting WebLogic Server ....
The WebLogic Server did not start up properly.
Exception raised:
java.lang.NoClassDefFoundError: java/lang/reflect/InvocationHandler
at weblogic.management.Admin.initialize(Admin.java:279)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
Child exited
What did I wrong?
Has anybody experiences on this problem?
Thanks ! -
Problem starting managed server in Cluster
Hi,
I'm using cluster with 2 managed server. other managed server2 is runing ok in the cluster now when I am starting managed server1 in a cluster this error is coming
The WebLogic Server encountered a critical failure
Reason: Assertion violated
Exception in thread "main" java.lang.NoClassDefFoundError
at weblogic.protocol.ServerIdentityManager.findServerIdentity(ServerIdentityManager.java:65)
at weblogic.protocol.URLManager.findAdministrationURL(URLManager.java:170)
at weblogic.server.ServerLifeCycleRuntime.getLifeCycleOperationsRemote(ServerLifeCycleRuntime.java:677)
at weblogic.t3.srvr.ServerRuntime.sendStateToAdminServer(ServerRuntime.java:406)
at weblogic.t3.srvr.ServerRuntime.updateRunState(ServerRuntime.java:392)
at weblogic.t3.srvr.T3Srvr.setState(T3Srvr.java:172)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:373)
at weblogic.Server.main(Server.java:67)
Could you pl tell the reason of this error?
Thanks in advance
Hi,
Can anybody help?
Edited by: user10680571 on Dec 4, 2008 4:42 AMThanks David.
During starting this managed server in cluster when I do tail -f <log_file_name> I can see this error message. But this message I can't see in log however ending log details- Is this something related with CLASSPATH problem?
<04-Dec-2008 10:11:18 o'clock GMT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to t
he end of the classpath:
/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n-schemas.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_c
ommon.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wl
p/netuix_common.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/netuix_schemas.jar:/software/bea/wls/920/weblogic92/pla
tform/lib/wlp/netuix_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/wsrp-common.jar>
<04-Dec-2008 10:11:21 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Serve
r VM Version 1.5.0_07-b03 from Sun Microsystems Inc.>
<04-Dec-2008 10:11:33 o'clock GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 Fri Jun 23 20:47:26 EDT 20
06 783464 >
<04-Dec-2008 10:12:06 o'clock GMT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /software/bea/wls/920/license.bea>
<04-Dec-2008 10:12:06 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<04-Dec-2008 10:12:06 o'clock GMT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<04-Dec-2008 12:12:26 o'clock GMT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to t
he end of the classpath:
/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n-schemas.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_c
ommon.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wl
p/netuix_common.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/netuix_schemas.jar:/software/bea/wls/920/weblogic92/pla
tform/lib/wlp/netuix_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/wsrp-common.jar>
<04-Dec-2008 12:12:35 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Serve
r VM Version 1.5.0_07-b03 from Sun Microsystems Inc.>
<04-Dec-2008 12:13:03 o'clock GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 Fri Jun 23 20:47:26 EDT 20
06 783464 >
<04-Dec-2008 12:13:56 o'clock GMT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /software/bea/wls/920/license.bea>
<04-Dec-2008 12:13:58 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<04-Dec-2008 12:14:00 o'clock GMT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<05-Dec-2008 06:21:55 o'clock GMT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to t
he end of the classpath:
/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n-schemas.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_c
ommon.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wl
p/netuix_common.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/netuix_schemas.jar:/software/bea/wls/920/weblogic92/pla
tform/lib/wlp/netuix_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/wsrp-common.jar>
<05-Dec-2008 06:21:57 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Serve
r VM Version 1.5.0_07-b03 from Sun Microsystems Inc.>
<05-Dec-2008 06:22:04 o'clock GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 Fri Jun 23 20:47:26 EDT 20
06 783464 >
<05-Dec-2008 06:22:23 o'clock GMT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /software/bea/wls/920/license.bea>
<05-Dec-2008 06:22:23 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<05-Dec-2008 06:22:23 o'clock GMT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
Thanks for your help..... -
Problem starting managed server.
Hi,
I have my weblogic server running on UNIX server which has 2 users (UserA and UserB). The Admin server has been started with UserA and the nodemanager with UserB. I have 3 clusters with 2 managed servers each configured in my server. When i start my managed servers from my console 2 clusters (i.e. 4 managed servers have started) but only 1 cluster failed to start throwing the following error.
<Sep 26, 2009 8:41:29 AM GMT> <Error> <Security> <BEA-090033> <Failed to Switch to User UserA java.lang.IllegalArgumentException: Cannot seteuid("UserA"), system error: 'Not owner'
at weblogic.platform.Unix.setEUser0(Native Method)
at weblogic.platform.Unix.setEffectiveUser(Unix.java:49)
at weblogic.t3.srvr.SetUIDManager.switchEffectiveUser(SetUIDManager.java:178)
at weblogic.t3.srvr.SetUIDManager.makeUnprivileged(SetUIDManager.java:104)
at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:777)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:669)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:343)
at weblogic.Server.main(Server.java:32)
.>
Kindly help me with this issue. i wonder why only 1 cluster failed?
Thanks,
Tom
Edited by: user11949331 on Sep 28, 2009 4:24 AMManish, Thanks for your response.
The issue is resolved. The problem seems to be with the privilege.
Whenever i start the Managed server the owner of the Managed server's directory is "UserB" whereas all other files and directories in the domain dir have "UserA" as owner.
So i changed the owner of all the files and dir in the domain directory to "UserA" and tried starting the managed server from command line and it worked.
Thanks,
Tom. -
We have the following setup.
CLLUSTER1 and CLUSTER2 are the servers to be in the cluster. CLUSTER3 is the cluster
administrator. We start CLUSTER3 as a self-managed server and then try and start
CLUSTER1 and CLUSTER3 as a managed server pointing at CLUSTER3. When we start
1 and 2 we get the following:
D:\bea\wlserver6.1\config\CLUSTER1>startmanagedweblogic CLUSTER3 http://10.0.1.1
03:7001
D:\bea\wlserver6.1>set PATH=.\bin;C:\WINNT\System32;d:\jdk1.3.1\bin
D:\bea\wlserver6.1>set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
D:\bea\wlserver6.1>echo off
* To start WebLogic Server, use the password *
* assigned to the system user. The system *
* username and password must also be used to *
* access the WebLogic Server console from a web *
* browser. *
D:\bea\wlserver6.1>"d:\bea\jdk131\bin\java" -hotspot -ms64m -mx64m -classpath
;.\lib\weblogic_sp.jar;.\lib\weblogic.jar" -Dweblogic.Domain=CLUSTER1 -Dbea.home
="d:\bea" -Dweblogic.management.password= -Dweblogic.ProductionModeEnabled=true
-Dweblogic.Name="CLUSTER3" -Dweblogic.management.server="http://10.0.1.103:7001"
"-Djava.security.policy==d:\bea\wlserver6.1/lib/weblogic.policy" weblogic.Serve
r
<20/11/2001 12:05:10> <Info> <Security> <Getting boot password from user.>
Enter password to boot WebLogic server:
Starting WebLogic Server ....
Connecting to http://10.0.1.103:7001...
The WebLogic Server did not start up properly.
Exception raised: weblogic.management.configuration.ConfigurationException: The
name of the managed server is same as admin server. The managed server will not
be allowed to start up.
weblogic.management.configuration.ConfigurationException: The name of the manage
d server is same as admin server. The managed server will not be allowed to star
t up.
at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:998)
at weblogic.management.Admin.initialize(Admin.java:320)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
D:\bea\wlserver6.1>goto finish
D:\bea\wlserver6.1>cd config\CLUSTER1
D:\bea\wlserver6.1\config\CLUSTER1>ENDLOCAL
D:\bea\wlserver6.1\config\CLUSTER1>
Many thanks in advance,
Alex Burton
http://www.e-plus.com.au/
Don't start the admin server as managed. Removing
-Dweblogic.management.server...
from the command line should help.
Alex Burton wrote:
> We have the following setup.
> CLLUSTER1 and CLUSTER2 are the servers to be in the cluster. CLUSTER3 is the cluster
> administrator. We start CLUSTER3 as a self-managed server and then try and start
> CLUSTER1 and CLUSTER3 as a managed server pointing at CLUSTER3. When we start
> 1 and 2 we get the following:
>
> D:\bea\wlserver6.1\config\CLUSTER1>startmanagedweblogic CLUSTER3 http://10.0.1.1
> 03:7001
>
> D:\bea\wlserver6.1>set PATH=.\bin;C:\WINNT\System32;d:\jdk1.3.1\bin
>
> D:\bea\wlserver6.1>set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
>
> D:\bea\wlserver6.1>echo off
>
> ***************************************************
> * To start WebLogic Server, use the password *
> * assigned to the system user. The system *
> * username and password must also be used to *
> * access the WebLogic Server console from a web *
> * browser. *
> ***************************************************
>
> D:\bea\wlserver6.1>"d:\bea\jdk131\bin\java" -hotspot -ms64m -mx64m -classpath
> ".
> ;.\lib\weblogic_sp.jar;.\lib\weblogic.jar" -Dweblogic.Domain=CLUSTER1 -Dbea.home
> ="d:\bea" -Dweblogic.management.password= -Dweblogic.ProductionModeEnabled=true
> -Dweblogic.Name="CLUSTER3" -Dweblogic.management.server="http://10.0.1.103:7001"
> "-Djava.security.policy==d:\bea\wlserver6.1/lib/weblogic.policy" weblogic.Serve
> r
> <20/11/2001 12:05:10> <Info> <Security> <Getting boot password from user.>
> Enter password to boot WebLogic server:
> Starting WebLogic Server ....
> Connecting to http://10.0.1.103:7001...
> ***************************************************************************
> The WebLogic Server did not start up properly.
> Exception raised: weblogic.management.configuration.ConfigurationException: The
> name of the managed server is same as admin server. The managed server will not
> be allowed to start up.
> weblogic.management.configuration.ConfigurationException: The name of the manage
> d server is same as admin server. The managed server will not be allowed to star
> t up.
> at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:998)
> at weblogic.management.Admin.initialize(Admin.java:320)
> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
> at weblogic.Server.main(Server.java:35)
> Reason: Fatal initialization exception
> ***************************************************************************
>
> D:\bea\wlserver6.1>goto finish
>
> D:\bea\wlserver6.1>cd config\CLUSTER1
>
> D:\bea\wlserver6.1\config\CLUSTER1>ENDLOCAL
>
> D:\bea\wlserver6.1\config\CLUSTER1>
>
> Many thanks in advance,
> Alex Burton
> http://www.e-plus.com.au/
-
Problems starting managed server from admin console WL70 portal
I get the following exception when I try to start the managed server from admin server console. Both Admin server and managed server are on the same machine.
I get the following exception when I try to start the managed server from admin server console. Both Admin server and managed server are on the same machine.
-
Forwarding to the security news group...
-------- Original Message --------
Subject: Starting Managed server problem ......
Date: 1 Jun 2004 23:02:53 -0700
From: Sameer <barsatkiraat2001>
Newsgroups: weblogic.developer.interest.management
Hi All,
I need you guy's help in this regard, that I am using solaris 8 and
installed Weblogic8.1 Server.
My Scenario is;
Have configured Admin Server and Managed server with nodemanager on one
unix machine.
So, what am facing the problem;
I am not able to get run Managed server after starting the nodemanager
and admin server, getting the error in nodemanager logs that is :
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <Security> <BEA-090482>
<BAD_CERTIFICATE alert was received from PortalQA - 10.12.10.94. Check
the peer to determine why it rejected the certificate chain (trusted CA
configuration, hostname verification). SSL debug tracing may be required
to determine the exact reason the certificate was rejected.>
And in Admin Server logs it's saying;
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <Security> <BEA-090504>
<Certificate chain received from PortalQA - 10.12.10.94 failed hostname
verification check. Certificate contained AdminQA but check expected
PortalQA>
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.'
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <NodeManager> <BEA-300038>
<The node manager is unable to monitor this server. Could not create an
SSL connection to the node manager. Reason :
[Security:090504]Certificate chain received from PortalQA - 10.12.10.94
failed hostname verification check. Certificate contained AdminQA but
check expected PortalQA>
Reason: weblogic.management.configuration.ConfigurationException: Due to
faulty SSL configuration, this server is unable to establish a
connection to the node manager.
<Jun 2, 2004 9:44:26 AM GMT 04:00> <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.>
If some one can help me, I do appreciate in all due respect.
Sameer.Hello Satya/All,
I'm also experiencing the exact problem you are facing. It would be great if
somebody could help in this regard at the earliest.
Thanks, senthil
Satya Ghattu <[email protected]> wrote:
Forwarding to the security news group...
-------- Original Message --------
Subject: Starting Managed server problem ......
Date: 1 Jun 2004 23:02:53 -0700
From: Sameer <barsatkiraat2001>
Newsgroups: weblogic.developer.interest.management
Hi All,
I need you guy's help in this regard, that I am using solaris 8 and
installed Weblogic8.1 Server.
My Scenario is;
Have configured Admin Server and Managed server with nodemanager on one
unix machine.
So, what am facing the problem;
I am not able to get run Managed server after starting the nodemanager
and admin server, getting the error in nodemanager logs that is :
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <Security> <BEA-090482>
<BAD_CERTIFICATE alert was received from PortalQA - 10.12.10.94. Check
the peer to determine why it rejected the certificate chain (trusted
CA
configuration, hostname verification). SSL debug tracing may be required
to determine the exact reason the certificate was rejected.>
And in Admin Server logs it's saying;
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <Security> <BEA-090504>
<Certificate chain received from PortalQA - 10.12.10.94 failed hostname
verification check. Certificate contained AdminQA but check expected
PortalQA>
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.'
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <NodeManager> <BEA-300038>
<The node manager is unable to monitor this server. Could not create
an
SSL connection to the node manager. Reason :
[Security:090504]Certificate chain received from PortalQA - 10.12.10.94
failed hostname verification check. Certificate contained AdminQA but
check expected PortalQA>
Reason: weblogic.management.configuration.ConfigurationException: Due
to
faulty SSL configuration, this server is unable to establish a
connection to the node manager.
<Jun 2, 2004 9:44:26 AM GMT 04:00> <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.>
If some one can help me, I do appreciate in all due respect.
Sameer. -
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 -
Path problem when use node manager to start Managed Server
Hi, I have met a problem:
My managed server's root directory is /usr/local/bea/cluster1/usr_projects/mydomain
My Node Manager 's default directory is /usr/local/bea/cluster1/weblogic700/common/nodemanager
I have some config file located under managed server's root directory and log
file is also should be generated in managed server's root directory.
But when I try to use node manager to startup/shutdown the Managed Server, I found
weblogic can not find the config file if I don't move the config file from Managed
server's root directory to node manager server's default directory. and also log
file was created under node manager's default directory.
It seems that managed server's default directory has been changed to node manager's
default directory.
What shall I do if I want Managed Server's default directory to be kept?Hi Lumin,
If the weblogic version is 8.1, there is a RootDirectory field in Remote
Start tab which should resolve your problem. Just enter the absolute
directory pathname on the machine where you are starting your managed server
and the current working directory of the managed server will be this
RootDirectory. Before 8.1, the RootDirectory was used for finding the config
file for weblogic but it was never used to change the working directory of
the managed server created by the node manager.
cheers,
gaurav.
"lumin" <[email protected]> wrote in message
news:3eb7a4ae$[email protected]..
>
Hi, I have met a problem:
My managed server's root directory is/usr/local/bea/cluster1/usr_projects/mydomain
My Node Manager 's default directory is/usr/local/bea/cluster1/weblogic700/common/nodemanager
>
I have some config file located under managed server's root directory andlog
file is also should be generated in managed server's root directory.
But when I try to use node manager to startup/shutdown the Managed Server,I found
weblogic can not find the config file if I don't move the config file fromManaged
server's root directory to node manager server's default directory. andalso log
file was created under node manager's default directory.
It seems that managed server's default directory has been changed to nodemanager's
default directory.
What shall I do if I want Managed Server's default directory to be kept? -
Problem in starting managed server
hi all,
i have configure a admin server and 3 managed server. after i startup the
admin server and node manager , i start managed server in admin console, but
got a list of errors as follows:
####<May 3, 2003 4:04:49 PM HKT> <Info> <J2EE> <eg103> <myserver3> <main>
<kernel identity> <> <160037> <J2EE service initializing>
####<May 3, 2003 4:04:49 PM HKT> <Emergency> <WebLogicServer> <eg103>
<myserver3> <main> <kernel identity> <> <000342> <Unable to initialize the
server: Fatal initialization exception
Throwable: weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[
Cannot intialize Resource Manager Connection Factory resources because could
not get JNDI context: javax.naming.ConfigurationException [Root exception is
java.net.MalformedURLException: no protocol: localhost:1099] ]
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot
intialize Resource Manager Connection Factory resources because could not
get JNDI context: javax.naming.ConfigurationException [Root exception is
java.net.MalformedURLException: no protocol: localhost:1099] ]
at
weblogic.j2ee.RMCFactoryDeployer.<init>(RMCFactoryDeployer.java:50)
at weblogic.j2ee.J2EEService.initialize(J2EEService.java:93)
at
weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
i have checked that rmiregistry is up and 1099 port is listening. Does
anyone know why ?
thank you very much
regrds
andhi all,
i have configure a admin server and 3 managed server. after i startup the
admin server and node manager , i start managed server in admin console, but
got a list of errors as follows:
####<May 3, 2003 4:04:49 PM HKT> <Info> <J2EE> <eg103> <myserver3> <main>
<kernel identity> <> <160037> <J2EE service initializing>
####<May 3, 2003 4:04:49 PM HKT> <Emergency> <WebLogicServer> <eg103>
<myserver3> <main> <kernel identity> <> <000342> <Unable to initialize the
server: Fatal initialization exception
Throwable: weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[
Cannot intialize Resource Manager Connection Factory resources because could
not get JNDI context: javax.naming.ConfigurationException [Root exception is
java.net.MalformedURLException: no protocol: localhost:1099] ]
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot
intialize Resource Manager Connection Factory resources because could not
get JNDI context: javax.naming.ConfigurationException [Root exception is
java.net.MalformedURLException: no protocol: localhost:1099] ]
at
weblogic.j2ee.RMCFactoryDeployer.<init>(RMCFactoryDeployer.java:50)
at weblogic.j2ee.J2EEService.initialize(J2EEService.java:93)
at
weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
i have checked that rmiregistry is up and 1099 port is listening. Does
anyone know why ?
thank you very much
regrds
and -
Problem with starting managed server
In a domain , I have one admin server and one managed server. When im trying to start managed server , the message says,
Message icon - Warning For server Server-0, the Node Manager associated with machine Machine-0 is not reachable.
Message icon - Warning All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed.
Already i started the node manager , i checked with node manager's log files, and I found these error in log files,
<Jul 30, 2010 12:54:32 PM> <Warning> <Uncaught exception in server handler: javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from 127.0.0.1 - 127.0.0.1. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from 127.0.0.1 - 127.0.0.1. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertReceived(Unknown Source)
at com.certicom.tls.record.alert.AlertHandler.handle(Unknown Source)
at com.certicom.tls.record.alert.AlertHandler.handleAlertMessages(Unknown Source)
at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
at com.certicom.tls.record.ReadHandler.read(Unknown Source)
at com.certicom.io.InputSSLIOStreamWrapper.read(Unknown Source)
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
at java.io.InputStreamReader.read(InputStreamReader.java:167)
at java.io.BufferedReader.fill(BufferedReader.java:136)
at java.io.BufferedReader.readLine(BufferedReader.java:299)
at java.io.BufferedReader.readLine(BufferedReader.java:362)
at weblogic.nodemanager.server.Handler.run(Handler.java:66)
at java.lang.Thread.run(Thread.java:619)
Can any one help me to troubleshoot this.Hi Jose,
To Disable SSL communication for NodeManager do the following:
<b><font color=maroon>Step1).</font></b> Open the *"nodeManager.properties"* file from *<WL_HOME>\common\nodemenager* (Example Location : C:\bea103\wlserver_10.3\common\nodemanager ) directory and change the value of SecureListener property to false:
SecureListener=false
<b><font color=maroon>Step2).</font></b> Login to AdminConsole and then
AdminConsoleHome--->Machines --><Your_MachineName> (Click here)--->NodeManager (Tab)---> Select the type as "Plain" from the combo box (by default it will be SSL)
<b><font color=maroon>Step3).</font></b> Restart the NodeManager ....better if you follow Step4) as well...
<b><font color=maroon>Step4).</font></b> Please Enroll your NodeManager as described in the Step8) of the following Link: http://weblogic-wonders.com/weblogic/2010/04/28/weblogic-clustering-in-remote-boxes/
Thanks
Jay SenSharma -
Problem Starting Managed Servers
Hi,
I am trying to start Managed Server on Sun Solaris. My admin Server and managed Server
are on the same Machine.
My admin Server starts up with out any problem. WhenI try to bring up my Managed
Server its not reading the command line arguments which I supplied through the Console:
Servers -> serverName -> Remote Start->Arguments. For some reason these command arguments
are not read and so I am having errors like Unable to load libraries, etc.
Also when I saw the log file for managed server the class path and the arguments
are printed in a different way than I have set. I dont know if thats a problem or
not. I am copying part of that for your reference.
classpath=/opt/j2sdk1_3_1_01/jre/lib/rt.jar\:/opt/weblogic6.1\:/opt/weblogic6.1/lib/weblogic_sp.jar\:/opt/weblogic6.1/lib/weblogic.jar\
serverStartArgs=-Dweblogic.management.server\=sunserver\:7210 -Djava.security.policy\=\=/opt/weblogic6.1/lib/weblogic.policy
I have checked the config.xml file and what ever I have set in the console is being
saved properly in the xml file.
Can any one know why the back slash is printed above even though I havent typed that
in the console. Has any one have experince with setting the command line arguments
and class path through console for Managed servers.
I am stuck up at this point. Any help in this regard will be greatly appreciated.
Thanks,
KiranSeems a method signature does not match with the implementation in the
library either due to namemangling or incompatible versions of libraries.
You are loading your own custom native libraries for security.
Best would be use the default startManagedServer -- once the server has
started, copy and paste the entire value of java.library.path into the
startup arguments for Remote start.
For instance in my server log file:
####<Apr 10, 2002 6:47:10 PM PDT> <Info> <Management> <mountview> <myserver>
<main> <system> <> <141034> <Java system property: java.library.path =
/home/sabha/600sp2only/jdk130/jre/bin/../lib/sparc/hotspot:/home/sabha/600sp
2only/jdk130/jre/bin/../lib/sparc::/home/sabha/600sp2only/wlserver6.0/lib/so
laris:/home/sabha/600sp2only/wlserver6.0/lib/solaris/oci816_8:/usr/lib>
I would set that as the arguments :
-Djava.library.path=/home/sabha/600sp2only/jdk130/jre/lib/sparc/hotspot:/hom
e/sabha/600sp2only/jdk130/jre/bin/../lib/sparc::/home/sabha/600sp2only/wlser
ver6.0/lib/solaris:/home/sabha/600sp2only/wlserver6.0/lib/solaris/oci816_8:/
usr/lib
If this does not work, then java for some reason is not taking library paths
set as java.library.path and I dont know how to set LD_LIBRARY_PATH as part
of arguments to java. Another thing is before starting the NodeManager, set
the LD_LIBRARY_PATH to point the library directories and see if this helps.
regards,
Sabha
"Kiran" <[email protected]> wrote in message
news:[email protected]...
>
Sabha,
I am trying to start the managed server via remote start. After readingyour reply
I have cleaned up the argument list for remote start. Now I am gettingaltogether
a different error.(Surpsisingly I was able to start the managed serversusing srartManagedServer.sh.
I dont know why I am having trouble to do the same through the remotestart).
>
I am getting a unsatisfied link error. In your reply you have asked me toadd -Djava.library.path
to the argument liist which I did. Below you can find the exact error Ihave got:
>
>
The WebLogic Server did not start up properly.
Exception raised:
java.lang.UnsatisfiedLinkError:/export/home/spbbprf1/Servers/v25_0/bb/pub/libinterface.so:
ld.so.1: /usr/bin/../java/bin/../bin/sparc/native_threads/java: fatal:relocation
error: file /export/home/spbbprf1/Servers/v25_0/bb/pub/libinterface.so:symbol Opsys_oneWayCryptCmpApi:
referenced symbol not found
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1382)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1306)
at java.lang.Runtime.loadLibrary0(Runtime.java:749)
at java.lang.System.loadLibrary(System.java:820)
atamdocs.APILink.accesscontrol.sum.EncryptApi.<clinit>(EncryptApi.java:20)
atamdocs.APILink.accesscontrol.sum.UserJoltBackend.<clinit>(UserJoltBackend.ja
va:52)
>
atamdocs.APILink.accesscontrol.sum.SumManagerImpl.<init>(SumManagerImpl.java:5
9)
>
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
atamdocs.uamsimpl.server.storage.multi.MultiManagerImpl.<init>(MultiManagerImp
l.java:208)
>
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
atamdocs.uamsimpl.server.storage.cache.CachingManagerImpl.<init>(CachingManage
rImpl.java:81)
>
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
at amdocs.uams.UamsSystem.getUamsManager(UamsSystem.java:156)
atamdocs.uamsimpl.server.ejb.wl6.WLUamsDelegate.<init>(WLUamsDelegate.java:61)
atamdocs.uamsimpl.server.ejb.wl6.WLUamsDelegate.<init>(WLUamsDelegate.java:55)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
at amdocs.uamsimpl.server.ejb.wl6.WLUamsRealm.<init>(WLUamsRealm.java:42)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
at weblogic.security.acl.Realm.getRealm(Realm.java:84)
at weblogic.security.acl.Realm.getRealm(Realm.java:62)
atweblogic.security.SecurityService.initializeRealm(SecurityService.java:258)
at weblogic.security.SecurityService.initialize(SecurityService.java:115)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:402)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
>
>
Please let me know if you need more description.
Thanks,
Kiran
"Sabha" <[email protected]> wrote:
Either you are attempting to start a managed server through its
NodeManager
for which the remote startup arguments are not correct or something else
is
wrong. How are you starting the server? The remote start is only when you
want to start the server through NodeManager and not for normalinvocation
of the startManagedServer script.
Does the server really start? can you paste the startup arguments for the
remote start of the managed server as saved in the config.xml.
What is the log generated when the managed server is startedup.
-Sabha
"Kiran" <[email protected]> wrote in message
news:[email protected]...
Sabha,
The main problem is:
What ever I am trying to give in the command line arguments through theConsole:
Servers -> serverName -> Remote Start->Arguments.
is not being read during managed server start up.
I have all the libraries defined defined in java.lib.path. I dont knowwhy
its not
being read by managed server during start up. Am I missing something.
-Kiran
"Sabha" <[email protected]> wrote:
If its unable to load the performance packs, try setting
java.library.path
to the solaris lib directories. /usr/lib, /home/oracle/lib paths -- oryou
can just copy what is in the admin weblogic.log file for the
java.library.path (make sure the paths are correct and applicable forthe
maanged server box also) and pass that as an argument as
in -Djava.library.path=/usr/lib:/bea/wlserver6.1/lib/solaris...
-Sabha
"Kiran" <[email protected]> wrote in message
news:[email protected]...
Hi,
I am trying to start Managed Server on Sun Solaris. My admin Server
and
managed Server
are on the same Machine.
My admin Server starts up with out any problem. WhenI try to bring
up
my
Managed
Server its not reading the command line arguments which I supplied
through
the Console:
Servers -> serverName -> Remote Start->Arguments. For some reason
these
command arguments
are not read and so I am having errors like Unable to load
libraries,
etc.
Also when I saw the log file for managed server the class path and
the
arguments
are printed in a different way than I have set. I dont know if thats
a
problem or
not. I am copying part of that for your reference.
classpath=/opt/j2sdk1_3_1_01/jre/lib/rt.jar\:/opt/weblogic6.1\:/opt/weblog
i
c
6.1/lib/weblogic_sp.jar\:/opt/weblogic6.1/lib/weblogic.jar\
serverStartArgs=-Dweblogic.management.server\=sunserver\:7210 -Djava.secur
i
t
y.policy\=\=/opt/weblogic6.1/lib/weblogic.policy
I have checked the config.xml file and what ever I have set in the
console
is being
saved properly in the xml file.
Can any one know why the back slash is printed above even though I
havent
typed that
in the console. Has any one have experince with setting the command
line
arguments
and class path through console for Managed servers.
I am stuck up at this point. Any help in this regard will be greatlyappreciated.
Thanks,
Kiran
Maybe you are looking for
-
Is there a way to add/change the modifier keys?
Hi I would like to have the smooth tool be a modifier key like it used to be. aaah the old days. anyway I'm sure I'm not the only one. Thanks!
-
HP Innovations in Education Worldwide Summit
I've always maintained that we need to look to the students of today to figure out what the adults are going to be doing next. We look at it with most things of technology. I'm not sure if these forums would exist if it wasn't for student groups buil
-
Not sure if I should post this error here or in the WorkShop forum. Anyway, I am using WLS 7 sp2 with an Informix DBMS. I need to use Distributed Transactions so I am re-configuring a few of my DataSources and Connection Pools to use the Informix XA
-
GL balances table and asset transactions
I would like to know the tables where I can find the information for GL balances monthwise and which tables to look for in asset accounting for Asset transactions like acquisitions, retirements depreciation etc monthwise. Any clarifications will be a
-
When I execute the following I get a error saying that the transaction has already been committed or aborted. void MyFunc(XmlTransaction& txn,XmlResults result) while(retry){ try{ result = myContainer->getAllDocuments(txn,DB_READ_CO