While i am starting a Managed server some security Exception is raised

JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m
WLS Start Mode=Development
CLASSPATH=:/home/durgasoft/HDFC_bea/patch_wls1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/durgasoft/HDFC_bea/patch_cie660/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/durgasoft/HDFC_bea/jdk160_05/lib/tools.jar:/home/durgasoft/HDFC_bea/wlserver_10.3/server/lib/weblogic_sp.jar:/home/durgasoft/HDFC_bea/wlserver_10.3/server/lib/weblogic.jar:/home/durgasoft/HDFC_bea/modules/features/weblogic.server.modules_10.3.0.0.jar:/home/durgasoft/HDFC_bea/wlserver_10.3/server/lib/webservices.jar:/home/durgasoft/HDFC_bea/modules/org.apache.ant_1.6.5/lib/ant-all.jar:/home/durgasoft/HDFC_bea/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar::/home/durgasoft/HDFC_bea/wlserver_10.3/common/eval/pointbase/lib/pbclient57.jar:/home/durgasoft/HDFC_bea/wlserver_10.3/server/lib/xqrl.jar::
PATH=/home/durgasoft/HDFC_bea/wlserver_10.3/server/bin:/home/durgasoft/HDFC_bea/modules/org.apache.ant_1.6.5/bin:/home/durgasoft/HDFC_bea/jdk160_05/jre/bin:/home/durgasoft/HDFC_bea/jdk160_05/bin:/usr/lib/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/durgasoft/bin
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://hostname:port/console *
starting weblogic with Java version:
java version "1.6.0_05"
Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode)
Starting WLS with line:
/home/durgasoft/HDFC_bea/jdk160_05/bin/java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m -Xverify:none -da -Dplatform.home=/home/durgasoft/HDFC_bea/wlserver_10.3 -Dwls.home=/home/durgasoft/HDFC_bea/wlserver_10.3/server -Dweblogic.home=/home/durgasoft/HDFC_bea/wlserver_10.3/server -Dweblogic.management.discover=false -Dweblogic.management.server=Admin_URL -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/home/durgasoft/HDFC_bea/patch_wls1030/profiles/default/sysext_manifest_classpath:/home/durgasoft/HDFC_bea/patch_cie660/profiles/default/sysext_manifest_classpath -Dweblogic.Name=hdfc_mng6_1 -Djava.security.policy=/home/durgasoft/HDFC_bea/wlserver_10.3/server/lib/weblogic.policy weblogic.Server
<Jun 24, 2012 5:31:42 AM GMT+05:30> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 10.0-b19 from Sun Microsystems Inc.>
<Jun 24, 2012 5:32:11 AM GMT+05:30> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3 Fri Jul 25 16:30:05 EDT 2008 1137967 >
<Jun 24, 2012 5:32:11 AM GMT+05:30> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://Admin_URL.>
<Jun 24, 2012 5:32:11 AM GMT+05:30> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
<Jun 24, 2012 5:32:11 AM GMT+05:30> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Jun 24, 2012 5:32:11 AM GMT+05:30> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Jun 24, 2012 5:32:11 AM GMT+05:30> <Notice> <Log Management> <BEA-170019> <The server log file /home/durgasoft/HDFC_bea/domains/HDFC_DOV_Domain/servers/hdfc_mng6_1/logs/hdfc_mng6_1.log is opened. All server side log events will be written to this file.>
<Jun 24, 2012 5:32:12 AM GMT+05:30> <Error> <Security> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: com.bea.common.store.service.StoreInitializationException: [Security:099060]The URL specified for the data store connection is invalid: ldap://null:-1,please check all host configuration parameters..
weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: com.bea.common.store.service.StoreInitializationException: [Security:099060]The URL specified for the data store connection is invalid: ldap://null:-1,please check all host configuration parameters.
at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(Unknown Source)
at weblogic.security.service.CSSWLSDelegateImpl.initialize(Unknown Source)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(Unknown Source)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(Unknown Source)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(Unknown Source)
Truncated. see log file for complete stacktrace
com.bea.common.engine.ServiceInitializationException: com.bea.common.store.service.StoreInitializationException: [Security:099060]The URL specified for the data store connection is invalid: ldap://null:-1,please check all host configuration parameters.
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(Unknown Source)
Truncated. see log file for complete stacktrace
com.bea.common.store.service.StoreInitializationException: [Security:099060]The URL specified for the data store connection is invalid: ldap://null:-1,please check all host configuration parameters.
at com.bea.common.ldap.properties.LDAPStoreServicePropertiesConfigurator.convertStoreProperties(LDAPStoreServicePropertiesConfigurator.java:53)
at com.bea.common.security.internal.service.StoreServiceImpl.initJDOProperties(StoreServiceImpl.java:101)
at com.bea.common.security.internal.service.StoreServiceImpl.init(StoreServiceImpl.java:73)
at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363)
at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
Truncated. see log file for complete stacktrace
>
<Jun 24, 2012 5:32:12 AM GMT+05:30> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Jun 24, 2012 5:32:12 AM GMT+05:30> <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(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)
>
<Jun 24, 2012 5:32:12 AM GMT+05:30> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Jun 24, 2012 5:32:12 AM GMT+05:30> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Jun 24, 2012 5:32:12 AM GMT+05:30> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

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

Similar Messages

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
Arun

I 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?

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 AM

How 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 in server.log , while starting soa managed server - B2B not running

Hi All
After starting SOA managed server , we found following error in the server.log , we are successfully able to access em and admin console , but while trying to access B2B console getting no response.
Please help us in understaning this error.
[ServletContext@15501276[app:b2bui module:/b2bconsole path:/b2bconsole spec-version:2.5], request: weblogic.servlet.internal.ServletRequestImpl@4e8b8[ GET /b2bconsole/faces/login.jspx HTTP/1.1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8 ( .NET CLR 3.5.30729) Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Connection: keep-alive Referer: http://172.16.130.34:7001/console/console.portal?_pageLabel=WebAppModuleTestingPage&_nfpb=true&WebAppModuleTestingPortletexpandNode=ROOTCHILDNODE1 Cookie: JSESSIONID=8R1ZM24XMQDs1Z22QNJ4YM1cMrGlKbd77nCTLkTW62Bkvw2nG6vx!-1614137459; ADMINCONSOLESESSION=LKZJM23fPzQQsM2GyHDHWtJ2L8nNNzmB3gNQG1n1phMwv41mJMVN!-145877631 ]] Root cause of ServletException. java.lang.NoClassDefFoundError: Could not initialize class org.apache.myfaces.trinidadinternal.convert.ColorConverter at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at java.lang.Class.newInstance0(Class.java:355) at java.lang.Class.newInstance(Class.java:308) at com.sun.faces.application.ApplicationImpl.newConverter(ApplicationImpl.java:1114) at com.sun.faces.application.ApplicationImpl.createConverter(ApplicationImpl.java:770) at oracle.adfinternal.view.faces.util.rich.ConverterValidatorRegistrationUtils.addConverterByTargetClass(ConverterValidatorRegistrationUtils.java:164) at oracle.adfinternal.view.faces.util.rich.ConverterValidatorRegistrationUtils.register(ConverterValidatorRegistrationUtils.java:84) at oracle.adfinternal.view.faces.config.rich.RegistrationConfigurator.init(RegistrationConfigurator.java:77) at org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl.init(GlobalConfiguratorImpl.java:400) at org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl.beginRequest(GlobalConfiguratorImpl.java:206) at org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl.getExternalContext(GlobalConfiguratorImpl.java:329) at org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl$CacheRenderKit.<init>(FacesContextFactoryImpl.java:86) at org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl.getFacesContext(FacesContextFactoryImpl.java:64) at oracle.adfinternal.controller.application.FacesContextFactoryImpl.getFacesContext(FacesContextFactoryImpl.java:56) at oracle.adfinternal.controller.application.model.FacesContextFactoryImpl.getFacesContext(FacesContextFactoryImpl.java:70) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:260) 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:292) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.tip.b2b.ui.util.SessionTimeoutFilter.doFilter(SessionTimeoutFilter.java:240) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:143) at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:70) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:326) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592) 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:2202) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Thanks
Satendra Pare

Which version of weblogic and SOA suite have you installed? Which OS are you using? Check on em whether soa-infra is up?
BTW, for Oracle B2B related questions, you should raise threads in Oracle B2B forum -
Integration - B2B
Regards,
Anuj

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

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

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

Unable to start WC_Spaces managed server

Iam unable to start WC_Spaces managed server form console/managed weblogic. below is the error.
C:\WC\user_projects\domains\WebCenter_domain\bin>startManagedWebLogic.cmd WC_Spa
ces http://localhost:8888
'WLS_MEM_ARGS_64BIT' is not recognized as an internal or external command,
operable program or batch file.
'WLS_MEM_ARGS_32BIT' is not recognized as an internal or external command,
operable program or batch file.
Launcher.exe version: 11.1.1.4.1 (internal 7.3.2.0)
JAVA Memory arguments: -Xms512m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize
=128m -XX:MaxPermSize=512m
WLS Start Mode=Development
CLASSPATH=C:\WC\ORACLE~1\modules\oracle.jdbc_11.1.1\ojdbc6dms.jar;C:\WC\patch_wl
s1036\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\WC\patch_oep
e180\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\WC\patch_ocp3
71\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\WC\patch_adfr11
11\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\WC\JDK160~1\lib
\tools.jar;C:\WC\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\WC\WLSERV~1.3\server\l
ib\weblogic.jar;C:\WC\modules\features\weblogic.server.modules_10.3.6.0.jar;C:\W
C\WLSERV~1.3\server\lib\webservices.jar;C:\WC\modules\ORGAPA~1.1/lib/ant-all.jar
;C:\WC\modules\NETSFA~1.0_1/lib/ant-contrib.jar;C:/WC/ORACLE~2/ucm/idc/component
s/NativeOsUtils/classes-NativeOsUtils.jar;C:\WC\ORACLE~1\soa\modules\commons-cli
-1.1.jar;C:\WC\ORACLE~1\soa\modules\oracle.soa.mgmt_11.1.1\soa-infra-mgmt.jar;C:
\WC\oracle_common\webcenter\modules\oracle.portlet.server_11.1.1\oracle-portlet-
api.jar;C:\WC\Oracle_WC1\wcps-services-app\modules\oracle.wcps_11.1.1\wcps-conne
ction-mbeans.jar;C:\WC\ORACLE~1\modules\oracle.jrf_11.1.1\jrf.jar;C:\WC\WLSERV~1
.3\common\derby\lib\derbyclient.jar;C:\WC\WLSERV~1.3\server\lib\xqrl.jar;C:\WC\O
RACLE~2\ucm\idc\jlib\idcloader.jar;C:\WC\ORACLE~2\ucm\idc\components\NativeOsUti
ls\classes-NativeOsUtils.jar;
PATH=C:/WC/ORACLE~2/ucm/idc/components/EmailMetadata/lib;C:/WC/ORACLE~2/ucm/idc/
components/NativeOsUtils/lib/win32/7.2.1.1;C:/WC/ORACLE~2/ucm/idc/components/Sit
eStudio/lib;C:/WC/ORACLE~2/ucm/idc/components/SiteStudioPublisher/lib;C:\WC\patc
h_wls1036\profiles\default\native;C:\WC\patch_oepe180\profiles\default\native;C:
\WC\patch_ocp371\profiles\default\native;C:\WC\patch_adfr1111\profiles\default\n
ative;C:\WC\WLSERV~1.3\server\native\win\32;C:\WC\WLSERV~1.3\server\bin;C:\WC\mo
dules\ORGAPA~1.1\bin;C:\WC\JDK160~1\jre\bin;C:\WC\JDK160~1\bin;C:\app\skora\prod
uct\11.2.0\dbhome_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;
c:\Program Files\Microsoft Platform SDK\bin\win64\x86\AMD64;c:\Program Files\Mic
rosoft Platform SDK\Bin\win64\AMD64;c:\Program Files\Microsoft Platform SDK\Bin;
c:\Program Files\Microsoft Platform SDK\Bin\Winnt;C:\PERL\BIN;C:\Program Files (
x86)\Intel\CPP\Compiler80\ia32e\bin;c:\program files (x86)\intel\cpp\idbe80\bin;
c:\jdk150\bin;c:\jdk160\bin;C:\MKSNT;c:\Program Files\WinZip;c:\orautil;C:\WC\WL
SERV~1.3\server\native\win\32\oci920_8
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
starting weblogic with Java version:
java version "1.6.0_29"
Java(TM) SE Runtime Environment (build 1.6.0_29-b11)
Java HotSpot(TM) Client VM (build 20.4-b02, mixed mode)
Starting WLS with line:
C:\WC\JDK160~1\bin\java -client -Xms512m -Xmx1024m -XX:CompileThreshold=8000 -
XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=WC_Spaces -Djava.security
.policy=C:\WC\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.security.SSL.trus
tedCAKeyStore="C:\WC\wlserver_10.3\server\lib\cacerts" -Xverify:none -da -Dpla
tform.home=C:\WC\WLSERV~1.3 -Dwls.home=C:\WC\WLSERV~1.3\server -Dweblogic.home=C
:\WC\WLSERV~1.3\server -Dcommon.components.home=C:\WC\ORACLE~1 -Djrf.version=11
.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logge
r -Ddomain.home=C:\WC\USER_P~1\domains\WEBCEN~1 -Djrockit.optfile=C:\WC\ORACLE~1
\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=C:\WC\
USER_P~1\domains\WEBCEN~1\config\FMWCON~1\servers\WC_Spaces -Doracle.domain.conf
ig.dir=C:\WC\USER_P~1\domains\WEBCEN~1\config\FMWCON~1 -Digf.arisidbeans.carmll
oc=C:\WC\USER_P~1\domains\WEBCEN~1\config\FMWCON~1\carml -Digf.arisidstack.home
=C:\WC\USER_P~1\domains\WEBCEN~1\config\FMWCON~1\arisidprovider -Doracle.securit
y.jps.config=C:\WC\USER_P~1\domains\WEBCEN~1\config\fmwconfig\jps-config.xml -Do
racle.deployed.app.dir=C:\WC\USER_P~1\domains\WEBCEN~1\servers\WC_Spaces\tmp\_WL
_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=C:\WC\ORAC
LE~1\modules\oracle.ossoiap_11.1.1,C:\WC\ORACLE~1\modules\oracle.oamprovider_11.
1.1,C:\WC\ORACLE~1\modules\oracle.jps_11.1.1 -Djava.protocol.handler.pkgs=oracle
.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Djps.auth.debug=false -D
tangosol.coherence.log=jdk -DjiveHome=C:\WC\USER_P~1\domains\WEBCEN~1\config\fmw
config\servers\WC_Spaces\owc_discussions -DUSE_JAAS=false -Djps.policystore.hybr
id.mode=false -Djps.combiner.optimize.lazyeval=true -Djps.combiner.optimize=true
-Djps.auth=ACC -Doracle.core.ojdl.logging.usercontextprovider=oracle.core.ojdl.
logging.impl.UserContextImpl -noverify -Doracle.webcenter.analytics.disable-nati
ve-partitioning=false -Doracle.webcenter.tagging.scopeTags=false -Djava.awt.head
less=true -Doracle.webcenter.tagging.scopeTags=false -XX:+UseParallelGC -XX:+Dis
ableExplicitGC -Dportlet.oracle.home=C:\WC\oracle_common -Dwc.oracle.home=C:\WC\
Oracle_WC1 -Ducm.oracle.home=C:\WC\ORACLE~2 -Dem.oracle.home=C:\WC\oracle_commo
n -Djava.awt.headless=true -Dweblogic.management.discover=false -Dweblogic.manag
ement.server=http://localhost:8888 -Dwlw.iterativeDev=false -Dwlw.testConsole=f
alse -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=C:\WC\patch_wls1036\prof
iles\default\sysext_manifest_classpath;C:\WC\patch_oepe180\profiles\default\syse
xt_manifest_classpath;C:\WC\patch_ocp371\profiles\default\sysext_manifest_classp
ath;C:\WC\patch_adfr1111\profiles\default\sysext_manifest_classpath weblogic.Se
rver
<Jun 7, 2013 1:48:13 AM CDT> <Info> <Security> <BEA-090905> <Disabling CryptoJ J
CE Provider self-integrity check for better startup performance. To enable this
check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Jun 7, 2013 1:48:13 AM CDT> <Info> <Security> <BEA-090906> <Changing the defaul
t Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable
this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Jun 7, 2013 1:48:13 AM CDT> <Notice> <WebLogicServer> <BEA-000395> <Following e
xtensions directory contents added to the end of the classpath:
C:\WC\user_projects\domains\WebCenter_domain\lib\mbeantypes\csp-id-asserter.jar;
C:\WC\user_projects\domains\WebCenter_domain\lib\mbeantypes\jps-wls-trustprovide
r.jar>
<Jun 7, 2013 1:48:13 AM CDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebL
ogic Server with Java HotSpot(TM) Client VM Version 20.4-b02 from Sun Microsyste
ms Inc.>
<Jun 7, 2013 1:48:14 AM CDT> <Info> <Security> <BEA-090065> <Getting boot identi
ty from user.>
Enter username to boot WebLogic server:weblogic
Enter password to boot WebLogic server:
<Jun 7, 2013 1:48:23 AM CDT> <Info> <Management> <BEA-141107> <Version: WebLogic
Server 10.3.6.0 Tue Nov 15 08:52:36 PST 2011 1441050 >
<Jun 7, 2013 1:48:25 AM CDT> <Emergency> <Management> <BEA-141151> <The admin se
rver could not be reached at http://localhost:8888.>
<Jun 7, 2013 1:48:25 AM CDT> <Info> <Configuration Management> <BEA-150018> <Thi
s server is being started in managed server independence mode in the absence of
the admin server.>
<Jun 7, 2013 1:48:25 AM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server stat
e changed to STARTING>
<Jun 7, 2013 1:48:25 AM CDT> <Info> <WorkManager> <BEA-002900> <Initializing sel
f-tuning thread pool>
<Jun 7, 2013 1:48:25 AM CDT> <Notice> <LoggingService> <BEA-320400> <The log fil
e C:\WC\user_projects\domains\WebCenter_domain\servers\WC_Spaces\logs\WC_Spaces.
log will be rotated. Reopen the log file if tailing has stopped. This can happen
on some platforms like Windows.>
<Jun 7, 2013 1:48:25 AM CDT> <Notice> <LoggingService> <BEA-320401> <The log fil
e has been rotated to C:\WC\user_projects\domains\WebCenter_domain\servers\WC_Sp
aces\logs\WC_Spaces.log00014. Log messages will continue to be logged in C:\WC\u
ser_projects\domains\WebCenter_domain\servers\WC_Spaces\logs\WC_Spaces.log.>
<Jun 7, 2013 1:48:25 AM CDT> <Notice> <Log Management> <BEA-170019> <The server
log file C:\WC\user_projects\domains\WebCenter_domain\servers\WC_Spaces\logs\WC_
Spaces.log is opened. All server side log events will be written to this file.>
<Jun 7, 2013 1:48:30 AM CDT> <Notice> <Security> <BEA-090082> <Security initiali
zing using security realm myrealm.>
<Jun 7, 2013 1:48:30 AM CDT> <Error> <Configuration Management> <BEA-150000> <An
error occurred while establishing a connection back to the adminstration server
t3://127.0.0.1:8888 during startup. Since bootstrap succeeded check that t3://1
27.0.0.1:8888 uniquely identifies the administration server.
javax.naming.ServiceUnavailableException [Root exception is java.rmi.NoSuchObjec
tException: The object identified by: '31' could not be found. Either it was ha
s not been exported or it has been collected by the distributed garbage collecto
r.]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(Exceptio
nTranslator.java:70)
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(Exceptio
nTranslator.java:32)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLIni
tialContextFactoryDelegate.java:792)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialReference(WLI
nitialContextFactoryDelegate.java:431)
at weblogic.jndi.Environment.getInitialReference(Environment.java:245)
Truncated. see log file for complete stacktrace
Caused By: java.rmi.NoSuchObjectException: The object identified by: '31' could
not be found. Either it was has not been exported or it has been collected by t
he distributed garbage collector.
at weblogic.rmi.internal.OIDManager.getServerReference(OIDManager.java:2
51)
at weblogic.rmi.extensions.server.ServerHelper.getLocalInitialReference(
ServerHelper.java:455)
at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:131)
at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:124)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialReference(WLI
nitialContextFactoryDelegate.java:427)
Truncated. see log file for complete stacktrace
>
<Jun 7, 2013 1:48:31 AM CDT> <Critical> <WebLogicServer> <BEA-000362> <Server fa
iled. Reason:
There are 1 nested errors:
javax.naming.ServiceUnavailableException [Root exception is java.rmi.NoSuchObjec
tException: The object identified by: '31' could not be found. Either it was ha
s not been exported or it has been collected by the distributed garbage collecto
r.]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(Exceptio
nTranslator.java:70)
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(Exceptio
nTranslator.java:32)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLIni
tialContextFactoryDelegate.java:792)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialReference(WLI
nitialContextFactoryDelegate.java:431)
at weblogic.jndi.Environment.getInitialReference(Environment.java:245)
at weblogic.server.channels.RemoteChannelServiceImpl.registerInternal(Re
moteChannelServiceImpl.java:173)
at weblogic.server.channels.RemoteChannelServiceImpl.registerForever(Rem
oteChannelServiceImpl.java:146)
at weblogic.protocol.ConnectMonitorFactory.registerForever(ConnectMonito
rFactory.java:88)
at weblogic.management.provider.MSIService.registerForReconnectToAdminSe
rver(MSIService.java:174)
at weblogic.management.mbeanservers.compatibility.internal.Compatibility
MBeanServerService.start(CompatibilityMBeanServerService.java:154)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: java.rmi.NoSuchObjectException: The object identified by: '31' could
not be found. Either it was has not been exported or it has been collected by t
he distributed garbage collector.
at weblogic.rmi.internal.OIDManager.getServerReference(OIDManager.java:2
51)
at weblogic.rmi.extensions.server.ServerHelper.getLocalInitialReference(
ServerHelper.java:455)
at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:131)
at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:124)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialReference(WLI
nitialContextFactoryDelegate.java:427)
... 9 more
>
<Jun 7, 2013 1:48:31 AM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server stat
e changed to FAILED>
<Jun 7, 2013 1:48:31 AM CDT> <Error> <WebLogicServer> <BEA-000383> <A critical s
ervice failed. The server will shut itself down>
<Jun 7, 2013 1:48:31 AM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server stat
e changed to FORCE_SHUTTING_DOWN>

try starting managed server with startManagedWebLogic.cmd WC_Spaces without adding any parameter, I know this works in linux with startManagedWebLogic.sh WC_Spaces

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 ....
sangita

Thanks 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

Hard trouble starting a managed server

Hi,
First, I know many have posted similar questions, but I've read them all,
and none of the solutions seem to help me :-(
On a WLS6.1SP1 on Solaris, I have a setup with one administration server
and one managed server. The two server instances are on the same physical
machine, and they are configured in the same domain, only on different
ports. When I start the managed server, it gets a
"weblogic.net.http.HttpUnauthorizedException: 401]" exception.
Here are some further information:
- I use a RDBMSRealm for all security checking.
- The administration server is started by:
java $JAVA_OPTIONS -classpath $CLASSPATH -Dweblogic.Domain=atdomain
-Dweblogic.Name=atadmin -Dbea.home=/opt/bea
-Dweblogic.ProductionModeEnabled=true
-Djava.security.policy==/opt/bea/wlserver6.1/lib/weblogic.policy
weblogic.Server
- The managed server is started with:
java $JAVA_OPTIONS -classpath $CLASSPATH -Dweblogic.Domain=atdomain
-Dweblogic.Name=atserver1 -Dweblogic.management.server=192.168.26.196:7441
-Dbea.home=/opt/bea -Dweblogic.management.username=system
-Dweblogic.management.password=xxxxx -Dweblogic.ProductionModeEnabled=true
-Djava.security.policy==$WL_HOME/lib/weblogic.policy weblogic.Server
- Both the admin server and the managed server is bound to listen to
192.168.26.196 (someone reported problems with using localhost, so I tried
this, no help).
- I've created a password.ini file, with the password for user "system" in.
- Some information on the ACLs and permissions for booting:
In RDBMSRealm, I've defined:
acl: weblogic.server.atadmin
acl: weblogic.server.atserver1
group: "wlsadmin" with permission "boot" on the two ACLs
user: "system" which is defined to be in group wlsadmin
- At boot of administration server I can see, in debugging output, that the
following ACL is checked and found OK: User "system", permission "boot" on
ACL "weblogic.server.atadmin".
- At boot of managed server, I can see in the debugging output, that the
following ACL is checked: User "system", permission "boot" on ACL
"weblogic.server.atserver1".
NOW: The realm implementation returns, that user "system" do have the
needed permission (which is correct), but regardless of this, the
adminstration server logs:
<Dec 28, 2001 2:10:39 PM CET> <Info> <Security> <Access failed (Thread =
Thread[ExecuteThread: '4' for queue: 'default',5,Thread Group for Queue:
'default']), caused java.lang.SecurityException: User "system" does not
have Permission "boot" based on ACL "weblogic.server.atserver1".>
- I've got the same realm, and security data in it, running on my
development machine. This machine only has ONE server, so I don't have the
added managed server setup there. In this setup, all works fine, so the
ACLs are correctly defined.
- If I disable the RDBMS realm, and use the fileRealm, I must define the
exact same ACLs and permissions to boot, but in this setup, it does work
with an administration server and a managed server.
- So, I try a RDBMS realm setup, with fallback on a fileRealm which have
been verified to work, ... same problem.
Hope someone got through the long talk above, and have some suggestion
for what to do, because I'm at a loss here :-(
Regards, Per Olesen

Hi again,
I managed to solve this one myself.
Here is what I finally found out:
- WLS admin server can only be started as user "system".
- If using RDBMS realm and administration server+managed server setup in
conjunction, the permissions needed for booting any server (managed or
administration) must be set using fileRealm.
- All other permissions can come for RDBMSRealm.
Hmm, so my final setup became:
1. RDBMSRealm with a caching realm.
2. fileRealm with user "system" and needed ACLs+permissions at boot time.
Be sure not to define the information from the fileRealm.properties in your
RDBMSRealm. It will not work.
While you can define all your permissions in a fileRealm and use for
booting any servers in a similar setup, you cannot define all your
permissions in a RDBMSRealm and none in a fileRealm :-(
Regards, Per

Trouble starting a managed server

Hi,
First, I know many have posted similar questions, but I've read them all,
and none of the solutions seem to help me :-(
On a WLS6.1SP1 on Solaris, I have a setup with one administration server
and one managed server. The two server instances are on the same physical
machine, and they are configured in the same domain, only on different
ports. When I start the managed server, it gets a
"weblogic.net.http.HttpUnauthorizedException: 401]" exception.
Here are some further information:
- I use a RDBMSRealm for all security checking.
- The administration server is started by:
java $JAVA_OPTIONS -classpath $CLASSPATH -Dweblogic.Domain=atdomain
-Dweblogic.Name=atadmin -Dbea.home=/opt/bea
-Dweblogic.ProductionModeEnabled=true
-Djava.security.policy==/opt/bea/wlserver6.1/lib/weblogic.policy
weblogic.Server
- The managed server is started with:
java $JAVA_OPTIONS -classpath $CLASSPATH -Dweblogic.Domain=atdomain
-Dweblogic.Name=atserver1 -Dweblogic.management.server=192.168.26.196:7441
-Dbea.home=/opt/bea -Dweblogic.management.username=system
-Dweblogic.management.password=xxxxx -Dweblogic.ProductionModeEnabled=true
-Djava.security.policy==$WL_HOME/lib/weblogic.policy weblogic.Server
- Both the admin server and the managed server is bound to listen to
192.168.26.196 (someone reported problems with using localhost, so I tried
this, no help).
- I've created a password.ini file, with the password for user "system" in.
- Some information on the ACLs and permissions for booting:
In RDBMSRealm, I've defined:
acl: weblogic.server.atadmin
acl: weblogic.server.atserver1
group: "wlsadmin" with permission "boot" on the two ACLs
user: "system" which is defined to be in group wlsadmin
- At boot of administration server I can see, in debugging output, that the
following ACL is checked and found OK: User "system", permission "boot" on
ACL "weblogic.server.atadmin".
- At boot of managed server, I can see in the debugging output, that the
following ACL is checked: User "system", permission "boot" on ACL
"weblogic.server.atserver1".
NOW: The realm implementation returns, that user "system" do have the
needed permission (which is correct), but regardless of this, the
adminstration server logs:
<Dec 28, 2001 2:10:39 PM CET> <Info> <Security> <Access failed (Thread =
Thread[ExecuteThread: '4' for queue: 'default',5,Thread Group for Queue:
'default']), caused java.lang.SecurityException: User "system" does not
have Permission "boot" based on ACL "weblogic.server.atserver1".>
- I've got the same realm, and security data in it, running on my
development machine. This machine only has ONE server, so I don't have the
added managed server setup there. In this setup, all works fine, so the
ACLs are correctly defined.
- If I disable the RDBMS realm, and use the fileRealm, I must define the
exact same ACLs and permissions to boot, but in this setup, it does work
with an administration server and a managed server.
- So, I try a RDBMS realm setup, with fallback on a fileRealm which have
been verified to work, ... same problem.
Hope someone got through the long talk above, and have some suggestion
for what to do, because I'm at a loss here :-(
Regards, Per Olesen

Hi Per,
I just wanted to comment really briefly on this.
You can define very nearly everything in the RDBMSRealm rather than the
fileRealm.
The only things that absolutely must exist in the fileRealm are:
"system" user (which can be redundantly declared in the RDBMSRealm, if you
wish)
acl.boot.weblogic.admin=system
If you like, you can declare all other users,groups, and acls in your
RDBMSRealm -- just dup everything you see in the fileRealm and move it to your
RDBMSRealm. I've tried this myself and it works.
But you're right. You can never entirely rid yourself of the fileRealm. :(
Joe Jerry
Per Olesen wrote:
Hi again,
I managed to solve this one myself.
Here is what I finally found out:
- WLS admin server can only be started as user "system".
- If using RDBMS realm and administration server+managed server setup in
conjunction, the permissions needed for booting any server (managed or
administration) must be set using fileRealm.
- All other permissions can come for RDBMSRealm.
Hmm, so my final setup became:
1. RDBMSRealm with a caching realm.
2. fileRealm with user "system" and needed ACLs+permissions at boot time.
Be sure not to define the information from the fileRealm.properties in your
RDBMSRealm. It will not work.
While you can define all your permissions in a fileRealm and use for
booting any servers in a similar setup, you cannot define all your
permissions in a RDBMSRealm and none in a fileRealm :-(
Regards, Per

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
Pawan

Hi,
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 in starting the Managed Server.

Hi,
Weblogic Version : 10.3.6.
I got the below error while i tried to start my Managed server.
I followed the link Starting/Stoping Weblogic Managed Server - weblogicexpert to start my managed server.
I have provided my AdminServer user name and password.Am trying to start my Managed Server MS1.
Error LOG:
weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:966)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: javax.security.auth.login.FailedLoginException: [Security:090303]Authentication Failed: User weblogic weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security:090295]caught unexpected exception
    at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:251)
    at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
    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 javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
    at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
    at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
    at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
    at com.bea.common.security.internal.service.JAASLoginServiceImpl.login(JAASLoginServiceImpl.java:113)
    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 com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
    at $Proxy16.login(Unknown Source)
    at weblogic.security.service.internal.WLSJAASLoginServiceImpl$ServiceImpl.login(WLSJAASLoginServiceImpl.java:89)
    at com.bea.common.security.internal.service.JAASAuthenticationServiceImpl.authenticate(JAASAuthenticationServiceImpl.java:82)
    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 com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
    at $Proxy34.authenticate(Unknown Source)
    at weblogic.security.service.WLSJAASAuthenticationServiceWrapper.authenticate(WLSJAASAuthenticationServiceWrapper.java:40)
    at weblogic.security.service.PrincipalAuthenticator.authenticate(PrincipalAuthenticator.java:338)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:930)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Regards,
Prasad K T,

As Shadab said there is no boot.properties file created in Managed Server MS1.
I manually created boot.properties with the below text.
# Generated by Configuration Wizard on Thu Mar 05 18:08:49 IST 2015
username=weblogic
password=weblogic1
Now i received the error log as
####<Mar 5, 2015 8:05:59 PM IST> <Critical> <Security> <PRASAD-VAIO> <MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1425566159374> <BEA-090402> <Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.>
####<Mar 5, 2015 8:05:59 PM IST> <Critical> <WebLogicServer> <PRASAD-VAIO> <MS1> <main> <<WLS Kernel>> <> <> <1425566159376> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:960)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: javax.security.auth.login.FailedLoginException: [Security:090303]Authentication Failed: User weblogic weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security:090295]caught unexpected exception
    at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:251)
    at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
    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 javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
    at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
    at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
    at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
    at com.bea.common.security.internal.service.JAASLoginServiceImpl.login(JAASLoginServiceImpl.java:113)
    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 com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
    at $Proxy16.login(Unknown Source)
    at weblogic.security.service.internal.WLSJAASLoginServiceImpl$ServiceImpl.login(WLSJAASLoginServiceImpl.java:89)
    at com.bea.common.security.internal.service.JAASAuthenticationServiceImpl.authenticate(JAASAuthenticationServiceImpl.java:82)
    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 com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
    at $Proxy34.authenticate(Unknown Source)
    at weblogic.security.service.WLSJAASAuthenticationServiceWrapper.authenticate(WLSJAASAuthenticationServiceWrapper.java:40)
    at weblogic.security.service.PrincipalAuthenticator.authenticate(PrincipalAuthenticator.java:338)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:930)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
>

Error in Starting OER Managed server on WEBLOGIC 11g..Linux OEL 4.7

Hi All,
While starting the OER managed server from linux server kde console we are getting started with the the following error ..
Pls provide any pointers in resolving the issue...
<Jun 22, 2010 8:35:19 PM IST> <Warning> <HTTP> <BEA-101369> <ServletContext@32289202[app:oer module:/oer path:/oer spec-version:null]: The encoding jsp-descriptor param has been deprecated. Consider declaring the encoding in the jsp-configelement (web.xml) or as a page directive (pageEncoding) instead.>
Jun 22, 2010 8:35:22 PM oracle.as.jmx.framework.LoggerHelper log
SEVERE: Error when parsing mbeans.xml file.
java.lang.InstantiationException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl cannot be cast to javax.xml.parsers.DocumentBuilderFactory
at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.parseSource(ApplicationMBeans.java:227)
at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.<init>(ApplicationMBeans.java:146)
at oracle.as.jmx.framework.generic.spi.BaseJMXFrameworkProviderImpl.getConfigObjectMBeanAssociationInfo(BaseJMXFrameworkProviderImpl.java:196)
at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2380)
at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2310)
at oracle.as.jmx.framework.wls.
Regards,
Ramnath

Hi,
Thanks for the input but modifying xercesImpl jar version did not work out
Extact error I am getting:
<Sep 30, 2010 6:37:11 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Sep 30, 2010 6:37:15 PM IST> <Warning> <HTTP> <BEA-101369> <ServletContext@167504850[app:oer module:/oer path:/oer spec-version:null]: The encoding jsp-descriptor param has been deprecated. Consider declaring the encoding in the jsp-config element (web.xml) or as a page directive (pageEncoding) instead.>
Sep 30, 2010 6:37:32 PM oracle.as.jmx.framework.LoggerHelper log
SEVERE: Error when parsing mbeans.xml file.
java.lang.InstantiationException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
     at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.parseSource(ApplicationMBeans.java:227)
     at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.<init>(ApplicationMBeans.java:146)
     at oracle.as.jmx.framework.generic.spi.BaseJMXFrameworkProviderImpl.getConfigObjectMBeanAssociationInfo(BaseJMXFrameworkProviderImpl.java:196)
     at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2380)
     at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2310)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseAndRegister(ComponentMBeans.java:153)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseDescriptors(ComponentMBeans.java:206)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerDomainLevelMBeans(ComponentMBeans.java:291)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:312)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:305)
     at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2$1.run(JMXFrameworkProviderImpl.java:988)
     at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2.run(JMXFrameworkProviderImpl.java:983)
     at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.ClassCastException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
     at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:123)
     at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.parseSource(ApplicationMBeans.java:174)
     at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.<init>(ApplicationMBeans.java:146)
     at oracle.as.jmx.framework.generic.spi.BaseJMXFrameworkProviderImpl.getConfigObjectMBeanAssociationInfo(BaseJMXFrameworkProviderImpl.java:196)
     at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2380)
     at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2310)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseAndRegister(ComponentMBeans.java:153)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseDescriptors(ComponentMBeans.java:206)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerDomainLevelMBeans(ComponentMBeans.java:291)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:312)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:306)
     at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2$1.run(JMXFrameworkProviderImpl.java:990)
     at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2.run(JMXFrameworkProviderImpl.java:996)
     ... 1 more
Sep 30, 2010 6:37:32 PM oracle.as.jmx.framework.LoggerHelper log
WARNING: Error parsing MBean descriptor file "/u01/app/ora11g/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig/mbeans/webservices.mgmt-mbeans.xml".
java.lang.InstantiationException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
     at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.parseSource(ApplicationMBeans.java:227)
     at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.<init>(ApplicationMBeans.java:146)
     at oracle.as.jmx.framework.generic.spi.BaseJMXFrameworkProviderImpl.getConfigObjectMBeanAssociationInfo(BaseJMXFrameworkProviderImpl.java:196)
     at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2380)
     at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2310)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseAndRegister(ComponentMBeans.java:153)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseDescriptors(ComponentMBeans.java:206)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerDomainLevelMBeans(ComponentMBeans.java:291)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:312)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:305)
     at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2$1.run(JMXFrameworkProviderImpl.java:988)
     at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2.run(JMXFrameworkProviderImpl.java:983)
     at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.ClassCastException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
     at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:123)
     at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.parseSource(ApplicationMBeans.java:174)
     at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.<init>(ApplicationMBeans.java:146)
     at oracle.as.jmx.framework.generic.spi.BaseJMXFrameworkProviderImpl.getConfigObjectMBeanAssociationInfo(BaseJMXFrameworkProviderImpl.java:196)
     at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2380)
     at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2310)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseAndRegister(ComponentMBeans.java:153)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseDescriptors(ComponentMBeans.java:206)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerDomainLevelMBeans(ComponentMBeans.java:291)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:312)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:306)
     at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2$1.run(JMXFrameworkProviderImpl.java:990)
     at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2.run(JMXFrameworkProviderImpl.java:996)
     ... 1 more
Sep 30, 2010 6:37:32 PM oracle.as.jmx.framework.LoggerHelper log
SEVERE: Error when parsing mbeans.xml file.
java.lang.InstantiationException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
     at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.parseSource(ApplicationMBeans.java:227)
     at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.<init>(ApplicationMBeans.java:146)
     at oracle.as.jmx.framework.generic.spi.BaseJMXFrameworkProviderImpl.getConfigObjectMBeanAssociationInfo(BaseJMXFrameworkProviderImpl.java:196)
     at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2380)
     at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2310)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseAndRegister(ComponentMBeans.java:153)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseDescriptors(ComponentMBeans.java:206)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerDomainLevelMBeans(ComponentMBeans.java:291)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:312)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:305)
     at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2$1.run(JMXFrameworkProviderImpl.java:988)
     at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2.run(JMXFrameworkProviderImpl.java:983)
     at java.lang.Thread.run(Thread.java:619)
Sep 30, 2010 6:37:32 PM oracle.as.jmx.framework.LoggerHelper log
WARNING: Error parsing MBean descriptor file "/u01/app/ora11g/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig/mbeans/soa-mbeans.xml".
java.lang.InstantiationException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
     at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.parseSource(ApplicationMBeans.java:227)
     at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.<init>(ApplicationMBeans.java:146)
     at oracle.as.jmx.framework.generic.spi.BaseJMXFrameworkProviderImpl.getConfigObjectMBeanAssociationInfo(BaseJMXFrameworkProviderImpl.java:196)
     at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2380)
     at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2310)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseAndRegister(ComponentMBeans.java:153)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseDescriptors(ComponentMBeans.java:206)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerDomainLevelMBeans(ComponentMBeans.java:291)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:312)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:305)
     at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2$1.run(JMXFrameworkProviderImpl.java:988)
     at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2.run(JMXFrameworkProviderImpl.java:983)
     at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.ClassCastException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
     at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:123)
     at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.parseSource(ApplicationMBeans.java:174)
     at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.<init>(ApplicationMBeans.java:146)
     at oracle.as.jmx.framework.generic.spi.BaseJMXFrameworkProviderImpl.getConfigObjectMBeanAssociationInfo(BaseJMXFrameworkProviderImpl.java:196)
     at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2380)
     at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2310)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseAndRegister(ComponentMBeans.java:153)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseDescriptors(ComponentMBeans.java:206)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerDomainLevelMBeans(ComponentMBeans.java:291)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:312)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:306)
     at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2$1.run(JMXFrameworkProviderImpl.java:990)
     at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2.run(JMXFrameworkProviderImpl.java:996)
     ... 1 more
Sep 30, 2010 6:37:32 PM oracle.as.jmx.framework.LoggerHelper log
SEVERE: Error when parsing mbeans.xml file.
java.lang.InstantiationException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
     at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.parseSource(ApplicationMBeans.java:227)
     at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.<init>(ApplicationMBeans.java:146)
     at oracle.as.jmx.framework.generic.spi.BaseJMXFrameworkProviderImpl.getConfigObjectMBeanAssociationInfo(BaseJMXFrameworkProviderImpl.java:196)
     at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2380)
     at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2310)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseAndRegister(ComponentMBeans.java:153)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseDescriptors(ComponentMBeans.java:206)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerDomainLevelMBeans(ComponentMBeans.java:291)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:312)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:305)
     at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2$1.run(JMXFrameworkProviderImpl.java:988)
     at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2.run(JMXFrameworkProviderImpl.java:983)
     at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.ClassCastException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
     at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:123)
     at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.parseSource(ApplicationMBeans.java:174)
     at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.<init>(ApplicationMBeans.java:146)
     at oracle.as.jmx.framework.generic.spi.BaseJMXFrameworkProviderImpl.getConfigObjectMBeanAssociationInfo(BaseJMXFrameworkProviderImpl.java:196)
     at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2380)
     at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2310)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseAndRegister(ComponentMBeans.java:153)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseDescriptors(ComponentMBeans.java:206)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerDomainLevelMBeans(ComponentMBeans.java:291)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:312)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:306)
     at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2$1.run(JMXFrameworkProviderImpl.java:990)
     at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2.run(JMXFrameworkProviderImpl.java:996)
     ... 1 more
Sep 30, 2010 6:37:32 PM oracle.as.jmx.framework.LoggerHelper log
WARNING: Error parsing MBean descriptor file "/u01/app/ora11g/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig/mbeans/dfw_mbeans.xml".
java.lang.InstantiationException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
     at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.parseSource(ApplicationMBeans.java:227)
     at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.<init>(ApplicationMBeans.java:146)
     at oracle.as.jmx.framework.generic.spi.BaseJMXFrameworkProviderImpl.getConfigObjectMBeanAssociationInfo(BaseJMXFrameworkProviderImpl.java:196)
     at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2380)
     at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2310)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseAndRegister(ComponentMBeans.java:153)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseDescriptors(ComponentMBeans.java:206)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerDomainLevelMBeans(ComponentMBeans.java:291)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:312)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:305)
     at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2$1.run(JMXFrameworkProviderImpl.java:988)
     at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2.run(JMXFrameworkProviderImpl.java:983)
     at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.ClassCastException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
     at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:123)
     at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.parseSource(ApplicationMBeans.java:174)
     at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.<init>(ApplicationMBeans.java:146)
     at oracle.as.jmx.framework.generic.spi.BaseJMXFrameworkProviderImpl.getConfigObjectMBeanAssociationInfo(BaseJMXFrameworkProviderImpl.java:196)
     at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2380)
     at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2310)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseAndRegister(ComponentMBeans.java:153)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseDescriptors(ComponentMBeans.java:206)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerDomainLevelMBeans(ComponentMBeans.java:291)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:312)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:306)
     at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2$1.run(JMXFrameworkProviderImpl.java:990)
     at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2.run(JMXFrameworkProviderImpl.java:996)
     ... 1 more
Sep 30, 2010 6:37:32 PM oracle.as.jmx.framework.LoggerHelper log
SEVERE: Error when parsing mbeans.xml file.
java.lang.InstantiationException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
     at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.parseSource(ApplicationMBeans.java:227)
     at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.<init>(ApplicationMBeans.java:146)
     at oracle.as.jmx.framework.generic.spi.BaseJMXFrameworkProviderImpl.getConfigObjectMBeanAssociationInfo(BaseJMXFrameworkProviderImpl.java:196)
     at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2380)
     at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2310)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseAndRegister(ComponentMBeans.java:153)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseDescriptors(ComponentMBeans.java:206)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerDomainLevelMBeans(ComponentMBeans.java:291)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:312)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:305)
     at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2$1.run(JMXFrameworkProviderImpl.java:988)
     at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2.run(JMXFrameworkProviderImpl.java:983)
     at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.ClassCastException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
     at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:123)
     at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.parseSource(ApplicationMBeans.java:174)
     at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.<init>(ApplicationMBeans.java:146)
     at oracle.as.jmx.framework.generic.spi.BaseJMXFrameworkProviderImpl.getConfigObjectMBeanAssociationInfo(BaseJMXFrameworkProviderImpl.java:196)
     at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2380)
     at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2310)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseAndRegister(ComponentMBeans.java:153)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseDescriptors(ComponentMBeans.java:206)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerDomainLevelMBeans(ComponentMBeans.java:291)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:312)
     at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:306)
     at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2$1.run(JMXFrameworkProviderImpl.java:990)
     at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2.run(JMXFrameworkProviderImpl.java:996)
     ... 1 more
INITIALIZING EXTERNAL EVENTING
running in single server mode
Intializing Thinkmap Server. Version: 2.6.051122173836X
Thinkmap Server initialized.
OER: Asset Preload completed: 8929ms
<Sep 30, 2010 6:37:56 PM IST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<Sep 30, 2010 6:37:57 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Sep 30, 2010 6:37:58 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<Sep 30, 2010 6:37:58 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.195.79:7101 for protocols iiop, t3, ldap, snmp, http.>
<Sep 30, 2010 6:37:58 PM IST> <Notice> <WebLogicServer> <BEA-000332> <Started WebLogic Managed Server "oer_server1" for domain "base_domain" running in Development Mode>
<Sep 30, 2010 6:38:00 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Sep 30, 2010 6:38:00 PM IST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>

While i am starting a Managed server some security Exception is raised

Similar Messages

Maybe you are looking for