Problem while starting the managed server
Hi
We have following configuration :-
We have 2 physical sesrvers :-
Server1 and Server2 in Sun Cluster running Solaris 10.
We also have Oracle DB server 9.2.0.8 in RAC mode, one instance each on Server1 & Server2.
Server 1 :-
cluster1 :- 1 Managed Server running
Server 2 :-
cluster2 :- 1 Managed Server running
we are getting following error in admin server log :-
<Error> <NodeManager> <BEA-300034> <Could not execute command "kill" for server "cluster1" using the node manager. Reason: Connection refused. Couldn't connect to NodeManager. Check that it is running at localhost:5556.>
Recently we have enabled the Connection Filter.
also getting following info in logs :-
<Notice> <Socket> <BEA-000445> <Connection rejected, filter blocked Socket[addr=192.193.164.8,port=53666,localport=8001], weblogic.security.net.FilterException: [Security:090220]rule 16>
<Notice> <Socket> <BEA-000445> <Connection rejected, filter blocked Socket[addr=163.37.174.126,port=58284,localport=8002], weblogic.security.net.FilterException: [Security:090220]rule 17>
Is it because of any misconfiguration in Connection filter ?
Or filter is not allowing the request for ipaddress and port of Managed Server in cluster1
Thanks in advance .. :)
Thanks for the information.
Node Manager is not used.
I found problem in Connection filter.
169.187.186.76 - address ManagedServer1
169.187.186.77- address Managed server2
169.187.186.51 :- Admin Server (8001 is http and 8002 is https)
Tunneling is enable for Managed Server
Please help me understanding below things is there any ambiguity in this rules :-
In the script to stop Managed server we are using t3 protocol like : t3://ip:port but its not allowing t3 protocol .whereas t3 protocol is no where denied in rules.
If I use https to issue request still not working
<connection-filter>weblogic.security.net.ConnectionFilterImpl</connection-filter>
<connection-filter-rule>127.0.0.1 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>172.16.0.129 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>172.16.1.1 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>169.187.186.59 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>169.187.186.51 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>169.187.186.76 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>192.168.10.4 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>172.16.4.1 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>169.187.186.77 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>169.187.186.60 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>172.16.0.130 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>172.16.1.2 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>192.168.10.5 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>172.16.4.2 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>ocs1.in.citicorp.com 169.187.186.51 8002 allow https</connection-filter-rule>
<connection-filter-rule>* 169.187.186.51 8001 deny</connection-filter-rule>
<connection-filter-rule>* 169.187.186.51 8002 deny</connection-filter-rule>
Thanks in Advance .......
Similar Messages
-
Problems while starting the Managed Server through Node Manager..
When I was trying to start a Managed Server using the Nodemanager , I am getting the following error :
NodeManager not configured to receive commands from host : emis-develop
I have the "nodemanager.hosts" file under the directory "c:\bea\wlserver6.1\config" and even while invoking the script for the startnodemanager , I am indicating this in the script ! Any ideas for this problem ??The system is vulnerable to security attacks, since it trusts certificates signed by the demo trusted CA.> You may configure custom Identity and Trust in weblogic. It is not recommended to use Demo Trsut and Demo Identity for environments higher to Dev. -
http://download.oracle.com/docs/cd/E14571_01/web.1111/e13707/identity_trust.htm#i1202182
Regards,
Anuj -
Error while starting the managed server using nodemanager
HI ,
I am getting the below error while starting the managed server from the Admin console. All the serverstart and the node manager proeprties looks fine.
Below is the error in the managed server log,
startWebLogic.sh: grep: not found
startWebLogic.sh: uname: not found
startWebLogic.sh: test: argument expected
can you help me to solve the problem please. i am using weblogic 10.3.3
thanks
ArunI think you've changed and added some lines into your startWebLogic.sh script. Can you put your script here?
-
Error while starting the managed server
Hi,
While starting the managed server i get ClassNotFoundException for the following files.
oracle.as.jmx.framework.wls.spi.StartupListener - jmxframework.jar
oracle.security.jps.wls.JpsWlsStartupClass - jps-wls.jar
oracle.security.audit.ajl.loader.JEEAuditLoader
oracle.dms.wls.DMSStartup - dms.jar
oracle.core.ojdl.weblogic.ODLConfiguration - odl2.jar
oracle.ias.cache.Startup -
oracle.mds.lcm.weblogic.WLLifecycleListener
oracle.dms.wls.DMSServletFilter
When checked I found jars related to above classes in BEAHOME/jdeveloper/modules folder.
are the jars also present some where in weblogic related folders.
Also "wsil-wls" and "dms" applications are not properly deployed in the ManagedServer.
When I am trying to deploy another application in managed server i get DMSServletFilter ClassNotFoundException.
I tried to add the above jars from jdeveloper folder to the POST_CLASSPATH in setDomainEnv.sh but i still get the same ClassNotFOundException while deploying.
Which config file should i update?
Thank You.I think you've changed and added some lines into your startWebLogic.sh script. Can you put your script here?
-
Errors while starting the manager server
Hi
I have created a manager server under weblogic 6.1 with sp2.
I am trying to start the managed server using the command file provided by weblogic. And I am getting the following exceptions.... The Admin server is up and running.
Configuration for the managed server
Name: MngdServer
Machine: None
ListenPort: 9001
ListenAddress: <null>
External DNSName: <null>
The exception I am getting is ....
java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:320)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:133)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:120)
at java.net.Socket.<init>(Socket.java:273)
at java.net.Socket.<init>(Socket.java:127)
at weblogic.net.http.HttpClient.openServer(HttpClient.java:201)
at weblogic.net.http.HttpClient.openServer(HttpClient.java:261)
at weblogic.net.http.HttpClient.<init>(HttpClient.java:121)
at weblogic.net.http.HttpClient.New(HttpClient.java:156)
at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:111)
at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:283)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:230)
at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1019)
at weblogic.management.Admin.initialize(Admin.java:326)
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)
>
The WebLogic Server did not start up properly.
Exception raised:
java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: 'localhost', port: '9001'
at weblogic.net.http.HttpClient.openServer(HttpClient.java:210)
at weblogic.net.http.HttpClient.openServer(HttpClient.java:261)
at weblogic.net.http.HttpClient.<init>(HttpClient.java:121)
at weblogic.net.http.HttpClient.New(HttpClient.java:156)
at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:111)
at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:283)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:230)
at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1019)
at weblogic.management.Admin.initialize(Admin.java:326)
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)
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: connecting to http://localhost:9001/wl_management_internal2/Bootstr
ap - with nested exception:
[java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: 'localhost', port: '9001']
at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1110)
at weblogic.management.Admin.initialize(Admin.java:326)
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
***************************************************************************startManagedWebLogic.cmd MngdServer
http://localhost:9001
You should give the url for the admin server and name of the managed server as arguments for this command. you seem like giving the url for the managed server.
this command needs url for the admin server so that it can connect to that admin server and add this managed server to that domain.
Good luck -
While Starting the Managed server using node manager
The system is vulnerable to security attacks, since it trusts certificates signed by the demo trusted CA.>
####<Nov 24, 2010 11:12:08 AM IST> <Notice> <Security> <HYDHTC99264D> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <147c637c707a0ee8:-6a0778d9:12c7c6421ea:-7fd5-000000000000000a> <1290577328874> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<Nov 24, 2010 11:12:08 AM IST> <Notice> <Security> <HYDHTC99264D> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <147c637c707a0ee8:-6a0778d9:12c7c6421ea:-7fd5-000000000000000a> <1290577328874> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<Nov 24, 2010 11:12:08 AM IST> <Notice> <Security> <HYDHTC99264D> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <147c637c707a0ee8:-6a0778d9:12c7c6421ea:-7fd5-000000000000000a> <1290577328890> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<Nov 24, 2010 11:12:08 AM IST> <Notice> <Security> <HYDHTC99264D> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <147c637c707a0ee8:-6a0778d9:12c7c6421ea:-7fd5-000000000000000a> <1290577328890> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<Nov 24, 2010 11:12:08 AM IST> <Notice> <Security> <HYDHTC99264D> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <147c637c707a0ee8:-6a0778d9:12c7c6421ea:-7fd5-000000000000000a> <1290577328890> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<Nov 24, 2010 11:12:08 AM IST> <Info> <WebLogicServer> <HYDHTC99264D> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <147c637c707a0ee8:-6a0778d9:12c7c6421ea:-7fd5-000000000000000a> <1290577328890> <BEA-000307> <Exportable key maximum lifespan set to 500 uses.>
####<Nov 24, 2010 11:12:22 AM IST> <Error> <NodeManager> <HYDHTC99264D> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <147c637c707a0ee8:-6a0778d9:12c7c6421ea:-7fd5-000000000000000d> <1290577342764> <BEA-300048> <Unable to start the server soa_server1 : Exception while starting server 'soa_server1'>
And the state of server is "FAILED_NOT_RESTARTABLE". Please help me in this
Regards
VeenaThe system is vulnerable to security attacks, since it trusts certificates signed by the demo trusted CA.> You may configure custom Identity and Trust in weblogic. It is not recommended to use Demo Trsut and Demo Identity for environments higher to Dev. -
http://download.oracle.com/docs/cd/E14571_01/web.1111/e13707/identity_trust.htm#i1202182
Regards,
Anuj -
Problem occured while starting the Manged server of weblogic9.2
Hi all,
I am cnfiguring the OWSM on 2 machine which are in Clustering mode(Pre-Prod Env)
I have done the installation of SOA SUITE10.1.3.1 for the same.
After installation , i started Admin server.
But i am facing issue while starting the managed server of weblogic9.2 through admin Server Console.(which are clustered).The managed Server state goes to ADMIN and raise the error that failed to start the server.It does not go into RUNNING state.
The error i was recieved is :
*####<May 13, 2009 10:21:01 AM IST> <Info> <ServletContext-/bea_wls_internal> <ggneai65> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1242190261158> <000000> <HTTPClntLogin: Login rejected with code: 'Failed', reason: java.net.ProtocolException: HTTP tunneling is disabled*
* at weblogic.rjvm.http.HTTPServerJVMConnection.acceptJVMConnection(HTTPServerJVMConnection.java:88)*
* at weblogic.rjvm.http.TunnelLoginServlet.service(TunnelLoginServlet.java:80)*
* at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)*
* at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)*
* at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)*
* at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)*
* at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)*
* at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3244)*
* at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)*
* at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)*
* at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2010)*
* at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1916)*
* at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)*
* at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)*
* at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)*
*'>*
because of which deployment of OWSM failed at managed server.
please help me for the same ASAP.
its urgent.
Regards
GauravThat is an INFO message you received and would not stop a managed server from starting. To get rid of that INFO message, enable tunneling on the admin server.
Check your node manager log file to see why the managed server is not starting. -
AuditLogFileException while starting a managed server
Hi all,
I implemented custom JAAS authentication for WLS 7.0 server and console. There
are no issues with a standalone or single server in the domain. When testing an
AdminServer with a managed server, I could still start the Admin Server without
any problem after configuring the security realm. I got the following errors while
starting the managed server. I tested with both servers on the same machine.
Any help would be appreciated.
<Server failed during initialization. Exception:weblogic.security.service.AuditLogFileException:
Couldn't rename C:\bea7\user_projects\deletedomain\.\DefaultAuditRecorder.log
to C:\bea7\user_projects\deletedomain\.\DefaultAuditRecorder.log2598.old
weblogic.security.service.AuditLogFileException: Couldn't rename C:\bea7\user_pr
ojects\deletedomain\.\DefaultAuditRecorder.log to C:\bea7\user_projects\deletedo
main\.\DefaultAuditRecorder.log2598.old
at weblogic.security.service.AuditLogFile.<init>(AuditLogFile.java:98)
at weblogic.security.providers.audit.DefaultAuditProviderImpl.createLogF
ile(DefaultAuditProviderImpl.java:106)
at weblogic.security.providers.audit.DefaultAuditProviderImpl.initialize
(DefaultAuditProviderImpl.java:89)
at weblogic.security.service.SecurityServiceManager.createSecurityProvid
er(SecurityServiceManager.java:1752)Hi,
Please remember to mark the answers accordingly... Helpful or correct... You will be helping the forum community by doing that.
First thing to fix is the Admin_URL, there should be something like:
-Dweblogic.management.server=http://localhost:7001How are you starting this managed server? Node manager or command line? Try both options and see if they bring up the same error.
Cheers,
Vlad -
Problem while starting the weblogic managed server
Hi,
I am facing the following error while starting the managed weblogic server :
weblogic.diagnostics.lifecycle.DiagnosticComponentLifecycleException: weblogic.store.PersistentStoreException:
java.io.IOException: [Store:280021]There was an error while opening the file store file "WLS_DIAGNOSTICS000000.DAT"
at weblogic.diagnostics.lifecycle.ArchiveLifecycleImpl.initialize(ArchiveLifecycleImpl.java:66)
at weblogic.diagnostics.lifecycle.DiagnosticFoundationService.start(DiagnosticFoundationService.java:107)
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: weblogic.store.PersistentStoreException: java.io.IOException: [Store:280021]There was an error while opening the
file store file "WLS_DIAGNOSTICS000000.DAT"
at weblogic.store.io.file.Heap.open(Heap.java:185)
at weblogic.store.io.file.FileStoreIO.open(FileStoreIO.java:88)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
at weblogic.store.xa.PersistentStoreManagerXA.createFileStore(PersistentStoreManagerXA.java:104)
at weblogic.store.xa.PersistentStoreManagerXA.createFileStore(PersistentStoreManagerXA.java:177)
at weblogic.diagnostics.archive.DiagnosticStoreRepository.getStore(DiagnosticStoreRepository.java:85)
at weblogic.diagnostics.lifecycle.ArchiveLifecycleImpl.initialize(ArchiveLifecycleImpl.java:64)
... 4 more
Caused by: java.io.IOException: [Store:280021]There was an error while opening the file store file
"WLS_DIAGNOSTICS000000.DAT"
at weblogic.store.io.file.StoreDir.throwIOException(StoreDir.java:214)
at weblogic.store.io.file.StoreDir.open(StoreDir.java:104)
at weblogic.store.io.file.Heap.open(Heap.java:183)
... 11 more
Caused by: java.io.IOException: Error from fcntl() for file locking, Resource temporarily unavailable, errno=11
at weblogic.store.io.file.direct.DirectIONative.open(Native Method)
at weblogic.store.io.file.direct.DirectFileChannel.<init>(DirectFileChannel.java:52)
at weblogic.store.io.file.direct.DirectIOManager.open(DirectIOManager.java:139)
at weblogic.store.io.file.StoreFile.openInternal(StoreFile.java:118)
at weblogic.store.io.file.StoreFile.open(StoreFile.java:148)
at weblogic.store.io.file.StoreDir.open(StoreDir.java:96)
... 12 more
>
The WebLogic Server encountered a critical failure
Reason: Assertion violated
Exception in thread "main" java.lang.NoClassDefFoundError: Could not initialize class
weblogic.protocol.ServerIdentityManager$Initializer
at weblogic.protocol.ServerIdentityManager.findServerIdentity(ServerIdentityManager.java:64)
at weblogic.protocol.URLManager.findAdministrationURL(URLManager.java:172)
at weblogic.server.ServerLifeCycleRuntime.getLifeCycleOperationsRemote(ServerLifeCycleRuntime.java:801)
at weblogic.t3.srvr.ServerRuntime.sendStateToAdminServer(ServerRuntime.java:423)
at weblogic.t3.srvr.ServerRuntime.updateRunState(ServerRuntime.java:409)
at weblogic.t3.srvr.T3Srvr.setState(T3Srvr.java:187)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:458)
at weblogic.Server.main(Server.java:67)
Kindly suggest some solution for this.
Best Regards,
VarunHi,
I killed the processes hunged up and now m facing the following error while starting the managed weblogic:
<Oct 12, 2012 3:01:53 AM PDT> <Error> <Security> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: java.lang.NoClassDefFoundError: com/thortech/util/logging/Logger.
weblogic.security.service.SecurityServiceException: java.lang.NoClassDefFoundError: com/thortech/util/logging/Logger
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: java.lang.NoClassDefFoundError: com/thortech/util/logging/Logger
at com.thortech.xl.security.wl.XellerateAuthenticationProviderImpl.<clinit>(XellerateAuthenticationProviderImpl.java:73)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:51)
at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363)
Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: com.thortech.util.logging.Logger
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
Truncated. see log file for complete stacktrace
>
<Oct 12, 2012 3:01:53 AM PDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Oct 12, 2012 3:01:53 AM PDT> <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) -
Error while starting weblogic Managed Server
Hi ,
I am new to SOA 11g. I installled the latest version(11.1.1.4) of all the components.I started web logic and able to login into Admin Console but I have a problem
while starting Managed Server.It gives me an error saying
<Feb 2, 2011 2:01:29 PM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 17.0-b17
from Sun Microsystems Inc.>
<Feb 2, 2011 2:01:30 PM IST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.management.ManagementException: Unable to obtain lock on C:\Oracle\Middleware\user_projects\domains\fmw_domain\servers\AdminServer\tmp\AdminServer.lok.
Server may already be running
at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.java:159)
at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.java:58)
at weblogic.management.internal.DomainDirectoryService.start(DomainDirectoryService.java:74)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:879)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:566)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:467)
at weblogic.Server.main(Server.java:71)>
<Feb 2, 2011 2:01:30 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Feb 2, 2011 2:01:30 PM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Feb 2, 2011 2:01:30 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Can anyone help ?
Regards,
Vikas Manchanda
Edited by: 829347 on Feb 2, 2011 12:48 AMHow are you starting the managed server? Is it a new install? The error suggests that the managed server is already running. You could check the windows task manager to see if there is a Java process running (or two if managed and admin server is on the same machine)
Damien -
Error while starting oam managed server
Hi Experts,
I am facing the following errors while starting the managed oam server instance.
I am using 11gR2.
<Jan 8, 2013 12:13:32 PM IST> <Error> <oracle.jps.audit> <BEA-000000> <IAU:IAU-5
048: Problem in transferring audit record to Audit Store null null. Please verif
y your Audit Store configuration>
<Jan 8, 2013 12:13:49 PM IST> <Error> <oracle.security.audit.logger> <BEA-000000
<IAU:JNDI Resource does not exist JNDI Name=AuditDB><Jan 8, 2013 12:13:49 PM IST> <Error> <oracle.jps.audit> <BEA-000000> <IAU:IAU-5
047: Problem in transferring audit record from file:C:\Oracle\MIDDLE~1\USER_P~1\
domains\OAM_OA~3\servers\oam_server1\logs\auditlogs\OAM\audit.log position:898,9
24 will retry in next cycle. caught exception oracle.security.audit.AuditExcepti
on: javax.naming.NameNotFoundException: Unable to resolve 'AuditDB'. Resolved ''
; remaining name 'AuditDB'
at oracle.security.audit.ajl.loader.OracleRepository.<init>(OracleReposi
tory.java:84)
at oracle.security.audit.ajl.loader.JDBCLogWriter.reinit(JDBCLogWriter.j
ava:59)
at oracle.security.audit.ajl.loader.JDBCLogWriter.write(JDBCLogWriter.ja
va:104)
at oracle.security.audit.ajl.loader.AuditLoader.readMessages(AuditLoader
.java:488)
at oracle.security.audit.service.AuditLoaderManager.readMessages(AuditLo
aderManager.java:209)
at oracle.security.audit.service.AuditLoaderManager$Runner.run(AuditLoad
erManager.java:284)
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'AuditDB'. Reso
lved ''; remaining name 'AuditDB'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(Basic
NamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.jav
a:252)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.j
ava:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:20
6)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.j
ava:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:412)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at oracle.security.audit.ajl.loader.OracleRepository.<init>(OracleReposi
tory.java:74)
... 5 more
Any pointers would be appreciated.
Thanks,
SubinHi Subin,
Once the server is started, is Auditing to DB successful?
Assuming that you have auditing to DB configured and that it is generally working, I suspect that the errors messages are occurring during the time when the server is making the jndi sources available to the server. If so, the messages are harmless (although I do not think they should happen).
Regards,
Colin -
Is there any way changing the priviledge after starting the managed server with the other user
Hi,
is there any way to change the user privilege after i have started the managed
server with one user.....say for example ....i have started one of my Managed
server as "root" ...but after that i wanted to make this instance work under as
"inet"
how do i do this OR is it possible ????
please advise ....
sangitaThanks again Rob.
Rob Woollen <[email protected]> wrote:
>
>
sangita wrote:
Thanks Rob for been so quick in responding.
I have 3 questions for you:
Running a server under root is a huge security hole.My Question: 1) what are the probable security issues while runninga server under
root ?
are these security issues external(from outside world) or internal(internally
within a company) ?
Iam basically curious to know external threats.
The problem is the root user can do anything. So if someone finds a
security hole in your server, then they have complete control of your
system.
The usual reason people want to do this is so they can bind to a port
<
1024. ie they want their web server to listen to 80.My Question: 2) What is the harm in using port 80 for webserver andwhy do the
people wanted to bind to a port < 1024 ?
People normally use 80 for web servers because that's the well-known
port.
Personally I would not recommend that you go that route. I would
recommend that you start the server as a very unprivileged user andbind
it to some port (say 7001).
Most firewalls support redirecting ports. Your firewall can redirect
80
on the external net to 7001 on the internal net. That's the solution
I
would recommend.My Question: 3) Suppose iam having a cluster of 2 Managed servers runningon port
7070. And Iam having a Iplanet server working as a Webserver that basicallyproxies
requests to this cluster. Then what is the best approach that i shouldfollow
in this context.....to be honest with you ....i still couldnot understandwhat
does "binding" the webserver port to a managed server in weblogic mean.
I would have your firewall redirect 80 to whatever port Iplanet is
listening on and then have iplanet proxy to WLS.
Do not run your WLS servers as root.
-- Rob
Iam sorry for asking these "silly" questions(in your opinion) ...butiam a bit
confused.
thanks, sangita
Rob Woollen <[email protected]> wrote:
Running a server under root is a huge security hole.
The usual reason people want to do this is so they can bind to a port
<
1024. ie they want their web server to listen to 80.
There is a set uid option in WLS where you start the server as root
and
then after it binds to the low port, it will switch to another userthat
you specify.
Personally I would not recommend that you go that route. I would
recommend that you start the server as a very unprivileged user andbind
it to some port (say 7001).
Most firewalls support redirecting ports. Your firewall can redirect
80
on the external net to 7001 on the internal net. That's the solution
I
would recommend.
-- Rob
sangita wrote:
<Sure, it's possible to do this, >
how to do this?
<but why do you want to do it? >
Iam not sure why this group (the other group than me) does start theirserver
as "root"...but somebody from that group asked me about this today.
I would not recommend that you start WLS as root on your production
system ever under any cirucmstance.then what is the best approach and what are the pros and cons if westart the
server as "root" OR as different user ????
please advise ....
thanks again.
Rob Woollen <[email protected]> wrote:
Sure, it's possible to do this, but why do you want to do it?
I would not recommend that you start WLS as root on your production
system ever under any cirucmstance.
-- Rob
sangita wrote:
Hi,
is there any way to change the user privilege after i have startedthe managed
server with one user.....say for example ....i have started one
of
my Managed
server as "root" ...but after that i wanted to make this instance
work
under as
"inet"
how do i do this OR is it possible ????
please advise ....
sangita -
Facing Problem in Starting Weblogic Managed Server
Hi,
While starting a managed server through Weblogic Console it is giving "nodemanager is not running" related error. I am not sure what is happening here. It was working fine earlier.
Thanks
PawanHi,
Please check wheather node manager is running inside the server. Please check the nodemanager listen port in nodemanager.properties file and issue below command from your server.
netstat -a |grep "port"
Regards,
Kishore -
Error while running the Managed server
Hi
i am getting the below error while running the Managed server.
java.lang.IllegalArgumentException: config=oracle.dms.config.DumpConfig@186793e logDir=null agency=oracle.dms.reporter.SpyAgency@181f91a dmsTimer=java.util.concurrent.ScheduledThreadPoolExecutor@95b5c
at oracle.dms.impl.producer.Dumper.<init>(Dumper.java:100)
at oracle.dms.app.ServerInitializer.init(ServerInitializer.java:136)
at oracle.dms.app.BaseInitializer.getInitializer(BaseInitializer.java:360)
at oracle.dms.app.DmsSpy.init(DmsSpy.java:210)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<Dec 6, 2011 7:47:30 PM IST> <Info> <Deployer> <01hw198371> <managed_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JGJiy3T5EgGqywAhMG1ErYE5000002> <1323181050633> <BEA-149059> <Module dms.war of application DMS Application [Version=11.1.1.1.0] is transitioning from STATE_ADMIN to STATE_PREPARED on server managed_server1.>
####<Dec 6, 2011 7:47:30 PM IST> <Info> <Deployer> <01hw198371> <managed_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JGJiy3T5EgGqywAhMG1ErYE5000002> <1323181050711> <BEA-149060> <Module dms.war of application DMS Application [Version=11.1.1.1.0] successfully transitioned from STATE_ADMIN to STATE_PREPARED on server managed_server1.>
####<Dec 6, 2011 7:47:30 PM IST> <Error> <Deployer> <01hw198371> <managed_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JGJiy3T5EgGqywAhMG1ErYE5000002> <1323181050726> <BEA-149231> <Unable to set the activation state to true for the application 'DMS Application [Version=11.1.1.1.0]'.
weblogic.application.ModuleException: [HTTP:101216]Servlet: "Spy" failed to preload on startup in Web application: "dms.war".
java.lang.IllegalArgumentException: config=oracle.dms.config.DumpConfig@186793e logDir=null agency=oracle.dms.reporter.SpyAgency@181f91a dmsTimer=java.util.concurrent.ScheduledThreadPoolExecutor@95b5c
at oracle.dms.impl.producer.Dumper.<init>(Dumper.java:100)
at oracle.dms.app.ServerInitializer.init(ServerInitializer.java:136)
at oracle.dms.app.BaseInitializer.getInitializer(BaseInitializer.java:360)
at oracle.dms.app.DmsSpy.init(DmsSpy.java:210)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: java.lang.IllegalArgumentException: config=oracle.dms.config.DumpConfig@186793e logDir=null agency=oracle.dms.reporter.SpyAgency@181f91a dmsTimer=java.util.concurrent.ScheduledThreadPoolExecutor@95b5c
at oracle.dms.impl.producer.Dumper.<init>(Dumper.java:100)
at oracle.dms.app.ServerInitializer.init(ServerInitializer.java:136)
at oracle.dms.app.BaseInitializer.getInitializer(BaseInitializer.java:360)
at oracle.dms.app.DmsSpy.init(DmsSpy.java:210)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
can anyone helpSrinath is 100% correct.
If the deployment failed, then there will very likely be some mention in the log.
You state that you checked the log, but you didn't mention whether you found an error, no error, a successful startup, etc. you are providing painfully few details to assist.
I would bet if you posted your .log and .out logs to Pastebin.com - #1 paste tool since 2002 and provided us links, We would be able to point out the error.
Lacking that information, my best advice would be to re-install and double-check you're completing all steps in the correct order.
Also, be sure to always search the product documentation first, the search this forum. For basic issues (e.g., standard installation), there is a high probability that someone else has asked that question.
I hope that helps,
-ryan -
OSB: problem when starting a managed server in an OSB cluster
Hi,
I used the configuration wizard to setup a very simple domain, containing a cluster with a managed server. When I start the managed server from the console I get prompted for the boot user and password. I specify the values I defined during the installation (weblogic user and custom passwort). After some time the managed server exists with the following exception:
####<21.04.2010 19.25 Uhr CEST> <Critical> <WebLogicServer> <DEMUC10525> <ManagedServer1> <main> <<WLS Kernel>> <> <> <1271870735741> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(Unknown Source)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(Unknown Source)
at weblogic.security.service.SecurityServiceManager.initialize(Unknown Source)
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)
What is its problem and how do I fix it? I have not configured anything special in the domain - just the cluster, a single machine and the managed server and admin server targeted at this machine.
The admin server starts without these problems. I also tried copying the boot.properties from the admin server to the managed server without any success - the same problem.
Regards
Dimo
Edited by: dimo velev on 21.04.2010 11:24Hi Anuj,
it turned out to be an OSB related problem - WLS forum would not have been able to help.
The startManagedWebLogic script should be run only within an environment which has been correctly setup using the domain setDomainEnv script. This seems to add some classpaths and stuff like this which, if missing, produces the exception - it actually has absolutely nothing to do with the user and password being wrong.
If you are using a node manager to start the managed servers then it should also be run within an evironment correctly setup with the domain's setDomainEnv script.
Best regards
Dimo
Maybe you are looking for
-
My Mac Mini goes to sleep when I turn off my TV.
Hello and thanks in advance for all help. I have a Intel mac mini that I currently have hooked up via DVI/DVI cable to my Sony LCD television. I recently upgraded the OS to 10.5 from 10.4. The issue that I am having after the OS upgrade has to do wit
-
Hi, I was working on the Oracle ADF workshop with the above version of JDeveloper and Oracle 9i as database. As per the instructions in the workshop I developed a JSP, browseCustomers.jsp and Ran it. In the "Enbedded OC4J Sever" panel in the JDevelop
-
Error with Render Multiple Frames
I have this problem before and the only solution I had was to reinstall the WHOLE system and it was fixed that way (but manually install Adobe CC). The problem is the next: After Effects doesn't render anything if I have "Render Multiple Frames Simul
-
How to get better performance to this sql code?
Guys I need your help. I have a master table, 80 columns, more than millions data in it. MasterTable PK_Column_1 PK_Column_2 Column_3 Column_4 Select column_3, column_4 from MasterTable where PK_Column_1 = '1' and PK_Column_2 = '2'; I don't know how
-
The audio in the timeline is uneven. If I isolate the channel are there any adjustments I can make to improve the sound? I know sound is the worst thing to be trying to fix. But any advice would be great. Thanks.