Problem Cloning a Managed Server

Hello,
I am trying to add a managed server to an OSB CLUSTER with Weblogic Version 11.1.1.3.
What I am doing is cloning an existing NODE but with a diferent Listen Port.
And when I try to start it, I obtain the following error:
bash-3.2$ tail -f osb_server4.out
* 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:
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
Abort - core dumped
Starting WLS with line:
/usr/jdk/instances/jdk1.6.0/bin/java -client -d64 -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8455,server=y,suspend=n -Djava.compiler=NONE -d64 -XX:+UseConcMarkSweepGC -Xms4096m -Xmx4096m -XX:PermSize=256m -XX:MaxPermSize=512m -Dweblogic.Name=osb_server4 -Djava.security.policy=/soaosbt/Oracle/OSB_Middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.system.BootIdentityFile=/soaosbt/Oracle/OSB_Middleware/user_projects/domains/soasoat_osb_domain/servers/osb_server4/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.ReverseDNSAllowed=false -Xverify:none -da:org.apache.xmlbeans... -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=/soaosbt/Oracle/OSB_Middleware/wlserver_10.3 -Dwls.home=/soaosbt/Oracle/OSB_Middleware/wlserver_10.3/server -Dweblogic.home=/soaosbt/Oracle/OSB_Middleware/wlserver_10.3/server -Dcommon.components.home=/soaosbt/Oracle/OSB_Middleware/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=/soaosbt/Oracle/OSB_Middleware/user_projects/domains/soasoat_osb_domain -Djrockit.optfile=/soaosbt/Oracle/OSB_Middleware/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.server.config.dir=/soaosbt/Oracle/OSB_Middleware/user_projects/domains/soasoat_osb_domain/config/fmwconfig/servers/osb_server4 -Doracle.domain.config.dir=/soaosbt/Oracle/OSB_Middleware/user_projects/domains/soasoat_osb_domain/config/fmwconfig -Digf.arisidbeans.carmlloc=/soaosbt/Oracle/OSB_Middleware/user_projects/domains/soasoat_osb_domain/config/fmwconfig/carml -Digf.arisidstack.home=/soaosbt/Oracle/OSB_Middleware/user_projects/domains/soasoat_osb_domain/config/fmwconfig/arisidprovider -Doracle.security.jps.config=/soaosbt/Oracle/OSB_Middleware/user_projects/domains/soasoat_osb_domain/config/fmwconfig/jps-config.xml -Doracle.deployed.app.dir=/soaosbt/Oracle/OSB_Middleware/user_projects/domains/soasoat_osb_domain/servers/osb_server4/tmp/_WL_user -Doracle.deployed.app.ext=/- -Dweblogic.alternateTypesDirectory=/soaosbt/Oracle/OSB_Middleware/oracle_common/modules/oracle.ossoiap_11.1.1,/soaosbt/Oracle/OSB_Middleware/oracle_common/modules/oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dem.oracle.home=/soaosbt/Oracle/OSB_Middleware/oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=false -Dweblogic.management.server=http://192.168.183.178:7201 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/soaosbt/Oracle/OSB_Middleware/patch_wls1034/profiles/default/sysext_manifest_classpath:/soaosbt/Oracle/OSB_Middleware/patch_ocp360/profiles/default/sysext_manifest_classpath weblogic.Server
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
I have read that this error could be caused for a Port Used by another application o a problem with the debug port.
But the port that I am setting is free (Checked with netstat ) and the Debbug is not enable.
I would appreciate some help.

Hi,
The cause is server running in debug mode and having the same debug port as an existing server on same machine.
For each domain running in development mode on the same machine make sure DEBUG_PORT in the setDomainEnv script has different values.
If you have multiple managed servers on the same domain and same machine. Create a separate startManagedWeblogic script to start your managed servers and set the Debug Port in that script.
Regards,
Kal

Similar Messages

Logon problem with oracle management server

I have problem with Oracle Management Server when I connect to the OMS message comes
The exception (java.lang.NullPointerException) occurred.
if any body have any idea pls tell us

Hi,
Oracle has changed the Enterprise Manager from version 1.5 to 2.0 .
With the new Oracle8i dataase server another service has been added.
If you want to user the OEM you have to install The Managment Server.
The Managment server has its own user and privileges and is recommended when using OEM.

Having problems starting Weblogic Managed Server

Hi,
I am new to WebLogic and I was looking at the webservices examples in samples dir and I took the example and just moved it to one of my currently deployed Web Application folder and changed the dir strutcure instead of the samples dir strutcure, compiled and deployed as standalone Application(not as part of my currently deployed Web App). It worked fine.
Then since there would be a need for reuse of lot of the current Web App. in the web services we are trying to implement, I tried to put the ear that got created in the WEB-INF/lib of the currently deployed exploded dir. It was pretty dumb to put the ear there, just thought, worst case it wont work, I thought I could pull the ear out of there. But seems like this changed the entire config.xml and ever since that my admin server got changed to myserver, I corrected all the problems with the admin server and admin server and node server they come up just fine. When trying to bring up Managed server, I get the following excpetion
Jul 16, 2004 4:00:37 PM EDT> <Debug> <HTTP> <BEA-101158> <Exception thrown while loading epic_dev: java.lang.NullPointerException
java.lang.NullPointerException
     at weblogic.utils.enumerations.FileEnumeration.getNextFile(FileEnumeration.java:155)
     at weblogic.utils.enumerations.FileEnumeration.hasMoreFiles(FileEnumeration.java:102)
     at weblogic.utils.enumerations.FileEnumeration.hasMoreElements(FileEnumeration.java:134)
     at weblogic.utils.jars.ExplodedJarFile$1.hasNext(ExplodedJarFile.java:112)
     at weblogic.utils.classloaders.ExtractionHelper.extractClassFiles(ExtractionHelper.java:117)
     at weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebAppServletContext.java:5119)
     at weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:4991)
     at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:560)
     at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:511)
     at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:594)
     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:623)
     at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:2896)
     at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1532)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:822)
     at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3085)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:930)
     at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:398)
     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:230)
     at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
     at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
     at weblogic.Server.main(Server.java:32)
>
<Jul 16, 2004 4:00:37 PM EDT> <Info> <Deployer> <BEA-149061> <Module epic_dev of application appsdirepic_dev_dir failed to transition from unprepared to prepared on server betsy_dev.>
<Jul 16, 2004 4:00:37 PM EDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application appsdirepic_dev_dir due to error weblogic.management.ApplicationException: prepare failed for epic_dev
Module Name: epic_dev, Error: Could not load epic_dev: java.lang.NullPointerException
weblogic.management.ApplicationException: prepare failed for epic_dev
Module Name: epic_dev, Error: Could not load epic_dev: java.lang.NullPointerException
     at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1555)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:822)
     at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3085)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:930)
     at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:398)
     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:230)
     at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
     at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
     at weblogic.Server.main(Server.java:32)
>
Could someone help me with resolving this.(This is only the dev machine, I played thannkfully!).
And also would like to get suggestions on setting up the new webserverces that we are trying to do. If I need to reuse lot of class files from current appl., how do i go about implementing this webservice? Should this be part of the existing application? or Web service could be a separate application and somehow we could look at the web app which is in the same domain.
Any help is appreciated.
Thanks
Anna

There was an access problem in the application I was trying to deploy and it had nothing to do with EAR file, once the access problem is taken care of, I could deploy the app just fine.

Deployment problem to the managed server in 11.1.1.1..

Our deployment problem still continue. We can deploy at last one application to the admin server.
We can see ADF domain ans jsf libs in deployment list
But for managed server following error occurs.
Even we tried small new application.
But error is the same.
An error occurred during activation of changes, please see the log for details.
weblogic.management.DeploymentException:
oracle.mds.lcm.weblogic.WLLifecycleListener
Failure occurred in the execution of deployment request with ID '1247067738026' for task '16'. Error is: 'weblogic.management.DeploymentException: ' weblogic.management.DeploymentException: at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:171) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:99) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:103) at weblogic.application.internal.flow.HeadLifecycleFlow.createListeners(HeadLifecycleFlow.java:172) at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:277) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:609) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:185) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:53) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) java.lang.ClassNotFoundException: oracle.mds.lcm.weblogic.WLLifecycleListener at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:247) at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:135) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:99) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:103) at weblogic.application.internal.flow.HeadLifecycleFlow.createListeners(HeadLifecycleFlow.java:172) at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:277) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:609) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:185) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:53) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Jul 8, 2009 6:45:10 PM EEST J2EE Info BEA-160170 Imported library Extension-Name: oracle.jsp.next, Specification-Version: 11.1.1, Implementation-Version: 11.1.1 for Application Application1_application1
Jul 8, 2009 6:45:10 PM EEST J2EE Info BEA-160170 Imported library Extension-Name: adf.oracle.domain, Specification-Version: 1, Implementation-Version: 11.1.1.1.0 for Application Application1_application1

last error we take is (we are not even use MDS customisation)
Failure occurred in the execution of deployment request with ID '1247124709107' for task '2'. Error is: 'weblogic.management.DeploymentException: ' weblogic.management.DeploymentException: at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:171) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:99) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:103) at weblogic.application.internal.flow.HeadLifecycleFlow.createListeners(HeadLifecycleFlow.java:172) at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:277) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:609) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:185) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:53) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) java.lang.ClassNotFoundException: oracle.mds.lcm.weblogic.WLLifecycleListener at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:247) at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:135) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:99) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:103) at weblogic.application.internal.flow.HeadLifecycleFlow.createListeners(HeadLifecycleFlow.java:172) at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:277) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:609) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:185) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:53) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

Having problems removing a managed server from WL console

Background:
Running the 11 g R1 (11.1.1.5) server on Linux.
Installed OIM, OAM, OVD, OID, WL. (other components may be added later)
Have not yet integrated OIM and OAM.
The Problem:
We were running into a problem on our oim server, that warranted removal and reinstallation.
we were attempting to remove the oim_server1 instance from the weblogic admin console.
went to deployments, and deleted the entry there for oim_server1
Then went to environment | servers
     The oim_server1 now shows as "FAILED_NOT_RESTARTABLE"
     and we can not remove this instance frome the admin instance.
     If we attempt to remove it, It gives the errors
          The server oim_server1 is a running server and may not be deleted.
          All of the servers selected are in a state which is incompatible with this operation.
Restarted the WL Admin server, then went back into the console. This did not change the status of the managed server.
Tried going to
/data01/app/oracle/product/Middleware/user_projects/domains/IDMDomain/servers/oim_server1/tmp
and removing the *.lok file...
No luck.
How do we get around this, so we can remove the incorrectly configured oim_server1 ?
Edited by: 992276 on Mar 6, 2013 11:30 AM

i was in the EXACT same situation but on weblogic 10.3.3.
* two servers in FAILED_NOT_RESTARTABLE
* try to delete them from admin console and i get the "is a running server and my not be deleted..../incompatible with this operation" messages
i tried lots of things and but i could not get rid of those servers.
### What ended up working. ###
i just started the servers. there is no way they should have started. i had already even deleted the server directories. but they started. and then i shut them down. and at that point i was able to delete them.
hope this helps you or somebody. it seemed like such an unlikely solution. but it worked for me.
Edited by: user8825653 on Mar 15, 2013 8:25 AM

HANDSHAKE_FAILURE problem when starting managed server via NOdeManager

hi all, i am trying to start a managed server using nodeManager, but i keep on
getting following exception:
weblogic.nodemanager.NodeManagerException: [Could not execute command start for
server managedServer via the Node Manager - reason: [CommandInvoker: Failed to
send command: 'online to server 'managedServer' to NodeManager at host: 'localhost:5555'
with exception FATAL Alert:HANDSHAKE_FAILURE - The handshake handler was unable
to negotiate an acceptable set of security parameters.. Please ensure that the
NodeManager is active on the target machine].] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeManagerRuntime.java:472)
at weblogic.nodemanager.NodeManagerRuntime.start(NodeManagerRuntime.java:76) at
java.lang.reflect.Method.invoke(Native Method) at
here is my script for starting nodemanager
set JAVA_HOME=c:\bea\jdk131
set WL_HOME=c:\bea\weblogic700
set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
set CLASSPATH=.;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar
java -hotspot -ms16m -mx16m -classpath %CLASSPATH% -Dbea.home=C:\bea\weblogic700
-Djava.security.policy=C:\bea\weblogic700\server\lib\weblogic.policy -Dweblogic.nodemanager.weblogicHome=C:\bea\weblogic700
-Dweblogic.nodemanager.listenAddress=172.21.73.94 -Dweblogic.nodemanager.listenPort=5555
-Dweblogic.nodemanager.trustedHosts=C:\bea\weblogic700\common\nodemanager\config\nodemanager.hosts
-Dweblogic.nodemanager.certificateFile=C:\bea\weblogic700\common\nodemanager\config\demo.crt
weblogic.nodemanager.NodeManager
i have created an admin server, called adminserver
then i have created in the same domain a server called managedserver
both servers run on the same machine,at different port number.
i have created a machine, and associated managedserver to it.
in the machine/configuration/nodemanager i have set listenaddress localhost and
listenport 5555.
my nodemanager starts automatically at htat port. however, when i try to start
the managed server via adminserver console, i got the exception mentioned in
the subject.
can anyone help?
regards
marco
can anyone point me to the right direction for solving this problem?
in the adminserver console i have defined a machine for teh managedserver, and
nodemanager is supposed to run at localhost:5555 (and indeed it does, because
ihave started it successfully).
thanx in advance and regards marco

Marco.
Sorry, this is not a solution to your problem but i am trying to solve the same
problem for a week now.
I have wl7.0 sp2, 1 admin server, 2 managed servers on the same box. I get the
same error. I know that the default certificate installed provides a hostname
verification of weblogic.com. I turned the hostname verification off, i put in
the Dweblogic.nodemanager.sslHostNameVerificationEnabled=false, i get the same
error when starting the managed server. I went ahead and created my own certificate
for machine called mallik, created my own passphrase, created a new keystore,
made the admin server view the keystore, used the same certificate for both the
admin server and the node manager. It still fails with the same error. I went
ahead and added the machine 'mallik' to nodeManager.hosts file. It fails. I am
totally confused now what needs to be done.
My nodeManger.hosts looks like this:
mallik 10.100.10.130
managedServer1 10.100.10.130
managedServer2 10.100.10.13
Below is the startNodeManager.cmd.
@echo off
@rem *************************************************************************
@rem This script can be used to start the WebLogic NodeManager
@rem
@rem This script sets the following variables before starting the NodeManager:
@rem
@rem WL_HOME - The root directory of your WebLogic installation.
@rem NODEMGR_HOME - The home directory for this NodeManager instance.
@rem JAVA_HOME - Location of the version of Java used to start WebLogic
@rem Server. This variable must point to the root directory of
@rem a JDK installation and will be set for you by the
@rem installer. See the WebLogic platform support page
@rem (http://e-docs.bea.com/wls/platforms/index.html) for an up-to-date
list of
@rem supported JVMs on Windows NT.
@rem PATH - Adds the JDK and WebLogic directories to the system path.
@rem CLASSPATH - Adds the JDK and WebLogic jars to the classpath.
@rem JAVA_OPTIONS - Java command-line options for running the server. (These
@rem will be tagged on to the end of the JAVA_VM and MEM_ARGS)
@rem JAVA_VM - The java arg specifying the VM to run. (i.e. -server,
@rem -client, etc.)
@rem MEM_ARGS - The variable to override the standard memory arguments
@rem passed to java
@rem
@rem *************************************************************************
SETLOCAL
set WL_HOME=C:\bea7.0\weblogic700
set NODEMGR_HOME=%WL_HOME%\common\nodemanager
set JAVA_HOME=C:\bea7.0\jdk131_06
Call %WL_HOME%\common\bin\commEnv.cmd
@rem If NODEMGR_HOME does not exist, create it
:checkNodeManagerHome
if exist %NODEMGR_HOME% goto checkJava
echo.
echo NODEMGR_HOME %NODEMGR_HOME% does not exist, creating it..
mkdir %NODEMGR_HOME%
@rem Check that java is where we expect it to be
:checkJava
if exist %JAVA_HOME%\bin\java.exe goto runNodeManager
echo The JDK wasn't found in directory %JAVA_HOME%.
echo Please edit this script so that the JAVA_HOME
echo variable points to the location of your JDK.
goto finish
:runNodeManager
if not "%JAVA_VM%" == "" goto noResetJavaVM
rem set JAVA_VM=-hotspot
set JAVA_VM=%COMM_VM%
:noResetJavaVM
if not "%MEM_ARGS%" == "" goto noResetMemArgs
set MEM_ARGS=-Xms32m -Xmx200m
:noResetMemArgs
@echo on
set CLASSPATH=.;%JAVA_HOME%\lib\tools.jar;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar;%CLASSPATH%
set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
cd %NODEMGR_HOME%
#"%JAVA_HOME%\bin\java.exe" %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -classpath "%CLASSPATH%"
"-Dbea.home=C:\bea7.0" "-Dweblogic.security.SSL.trustedCAKeyStore=%WL_HOME%\server\lib\cacerts"
"-Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy" "-Dweblogic.nodemanager.reverseDnsEnabled=true"
"-Dweblogic.nodemanager.javaHome=%JAVA_HOME%" weblogic.nodemanager.NodeManager
"%JAVA_HOME%\bin\java.exe" %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -classpath "%CLASSPATH%"
"-Dbea.home=C:\bea7.0" "-Dweblogic.security.SSL.trustedCAKeyStore=%WL_HOME%\server\lib\cacerts"
"-Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy" "-Dweblogic.nodemanager.certificateFile=C:\bea7.0\user_projects\myDomain\mallikcert.pem"
"-Dweblogic.nodemanager.sslHostNameVerificationEnabled=false" "-Dweblogic.nodemanager.javaHome=%JAVA_HOME%"
"-Dweblogic.ListenAddress=mallik" "-Dweblogic.nodemanager.nativeVersionEnabled=true"
"-Dweblogic.nodemanager.reverseDnsEnabled=true" "-Dweblogic.nodemanager.javaHome=%JAVA_HOME%"
"-Dweblogic.nodemanager.trustedHosts=%WL_HOME%\common\nodemanager\config\nodemanager.hosts"
"-Dweblogic.management.pkpassword=weblogic" weblogic.nodemanager.NodeManager
goto finish
:finish
ENDLOCAL
I would appreciate if anybody can help me.
Mallik.
"Marco" <[email protected]> wrote:
>
hi all, i am trying to start a managed server using nodeManager, but
i keep on
getting following exception:
weblogic.nodemanager.NodeManagerException: [Could not execute command
start for
server managedServer via the Node Manager - reason: [CommandInvoker:
Failed to
send command: 'online to server 'managedServer' to NodeManager at host:
'localhost:5555'
with exception FATAL Alert:HANDSHAKE_FAILURE - The handshake handler
was unable
to negotiate an acceptable set of security parameters.. Please ensure
that the
NodeManager is active on the target machine].] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeManagerRuntime.java:472)
at weblogic.nodemanager.NodeManagerRuntime.start(NodeManagerRuntime.java:76)
at
java.lang.reflect.Method.invoke(Native Method) at
here is my script for starting nodemanager
set JAVA_HOME=c:\bea\jdk131
set WL_HOME=c:\bea\weblogic700
set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
set CLASSPATH=.;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar
java -hotspot -ms16m -mx16m -classpath %CLASSPATH% -Dbea.home=C:\bea\weblogic700
-Djava.security.policy=C:\bea\weblogic700\server\lib\weblogic.policy
-Dweblogic.nodemanager.weblogicHome=C:\bea\weblogic700
-Dweblogic.nodemanager.listenAddress=172.21.73.94 -Dweblogic.nodemanager.listenPort=5555
-Dweblogic.nodemanager.trustedHosts=C:\bea\weblogic700\common\nodemanager\config\nodemanager.hosts
-Dweblogic.nodemanager.certificateFile=C:\bea\weblogic700\common\nodemanager\config\demo.crt
weblogic.nodemanager.NodeManager
i have created an admin server, called adminserver
then i have created in the same domain a server called managedserver
both servers run on the same machine,at different port number.
i have created a machine, and associated managedserver to it.
in the machine/configuration/nodemanager i have set listenaddress localhost
and
listenport 5555.
my nodemanager starts automatically at htat port. however, when i try
to start
the managed server via adminserver console, i got the exception mentioned
in
the subject.
can anyone help?
regards
marco
can anyone point me to the right direction for solving this problem?
in the adminserver console i have defined a machine for teh managedserver,
and
nodemanager is supposed to run at localhost:5555 (and indeed it does,
because
ihave started it successfully).
thanx in advance and regards marco

Cloning UCM Managed Server

Hi,
We have implemented WCM in our project. (Webcenter Portal + Webcenter content) PS3.
UAT :1
We have Internet and Intranet applications deployed in the same domain under different managed servers.
Common webserver is present for both Internet and Intranet. Reference to this webserver has been put in the config.cfg file of UCM.
Prod :
We have Internet and Intranet applications deployed in the same domain under different managed servers.
Different webservers for both Internet and Intranet applications. In this case, if we map to either of the webservers, load on it will be heavy. If the webserver goes down, contents for both Internet and Intranet applications will not be available.
Our query:
1. Do we have any option to give mulitple entries of httpServeraddress variable in config.cfg.
2. We were thinking of cloning the current ucm managed server, point it to the same repository and just point to different webservers. But is cloning of UCM Managed server recommended.
Please Suggest.
Regards,
Bhaskar

Great!
I had the same error: when starting UCM on WL Console, it starts and says Running. But when accessing it on the browser receive the error 404. In the other hand, when starting with Commands, it force shutdowns.
I have set the StartScriptEnabled property to true, now I can start UCM only on the command Line, to start it on WL Console, I have to manually start the node manager.
Is there a way/script to start the node manager automatically?
Regards,

XI 3.0 Installation Problem: no central managment server running

Hi, I am totally new to BO our company just purchased the application and I have installed XI 3.0 on one of our server. I have setup the DB and the installation finished successfully. However I can't find CMS anywhere on the server. It seems like all the other XI 3.0 components are there Business view manager, central configuration manager, etc. they are all in the program list.
The only thing I didn't install is Tomcat. In Central configuration Manager ther Server Intelligence Agent is running. When I try to connect to the server in Business view Manager I receive the following error "The system servername cannot be contacted, but there is no Central Managment Server running at port 6400."
During the installation for "Web Application Server" part I checked the "other" option since I want to use IIS. I have a feeling I need to do some type of post configuration for IIS? Where do I perform this?
Our setup is:
Window Server 2003 SP2 with all the latest window updates
The latest XI 3.0 (I downloaded it from the product page)
My questions are:
1. Does XI work with IIS at all?
2. Do I need to install Tomcat and run some kind of connector to have IIS work?
3. What am I missing for my XI 3.0 it seem the core component is missing (CS)?
Edited by: Amy Williams on Sep 24, 2008 11:18 AM
Moved from Xcelsius forum to BOE Administration

Hi Allan,
In answer to your questions - XI 3.0 does not have an IIS interface right now. You will need to install a java application components in order to access the end user interface for viewing reports (InfoView), the report viewers, the web services and SDKs and the management console (CMC). The easiest way to do this is to choose the default Tomcat components in the installation and work from there.
If you left everything else as default, then you will have all the necessary application components installed to get the system up and running. It may just be that your CMS has not started for some reason. Try stopping and restarting the Server Intelligence Agent (SIA) in the Central Config Manager (CCM) - found in the Start/Programs/Business Objects group.
Once started, try clicking on the "Manage Servers" icon of the CCM (the one with a server and a check mark on it). This should allow you connect to the system and see which servers have started. IF you cannot connect, the next step would be to check the windows Event Log. See if the CMS service started OK. If it didn't the log should provide you with more information, which you can post here for further assistance.
If it did, and you still cannot connect, you may need to review your network firewall settings and/or your DEP status (see the properties panel for My Computer, choose the Advanced tab, select the Performance settings button, then the Data Execution Prevention tab).
Happy hunting.
Derek.

Problem in starting managed server

hi all,
i have configure a admin server and 3 managed server. after i startup the
admin server and node manager , i start managed server in admin console, but
got a list of errors as follows:
####<May 3, 2003 4:04:49 PM HKT> <Info> <J2EE> <eg103> <myserver3> <main>
<kernel identity> <> <160037> <J2EE service initializing>
####<May 3, 2003 4:04:49 PM HKT> <Emergency> <WebLogicServer> <eg103>
<myserver3> <main> <kernel identity> <> <000342> <Unable to initialize the
server: Fatal initialization exception
Throwable: weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[
Cannot intialize Resource Manager Connection Factory resources because could
not get JNDI context: javax.naming.ConfigurationException [Root exception is
java.net.MalformedURLException: no protocol: localhost:1099] ]
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot
intialize Resource Manager Connection Factory resources because could not
get JNDI context: javax.naming.ConfigurationException [Root exception is
java.net.MalformedURLException: no protocol: localhost:1099] ]
at
weblogic.j2ee.RMCFactoryDeployer.<init>(RMCFactoryDeployer.java:50)
at weblogic.j2ee.J2EEService.initialize(J2EEService.java:93)
at
weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
i have checked that rmiregistry is up and 1099 port is listening. Does
anyone know why ?
thank you very much
regrds
and

hi all,
i have configure a admin server and 3 managed server. after i startup the
admin server and node manager , i start managed server in admin console, but
got a list of errors as follows:
####<May 3, 2003 4:04:49 PM HKT> <Info> <J2EE> <eg103> <myserver3> <main>
<kernel identity> <> <160037> <J2EE service initializing>
####<May 3, 2003 4:04:49 PM HKT> <Emergency> <WebLogicServer> <eg103>
<myserver3> <main> <kernel identity> <> <000342> <Unable to initialize the
server: Fatal initialization exception
Throwable: weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[
Cannot intialize Resource Manager Connection Factory resources because could
not get JNDI context: javax.naming.ConfigurationException [Root exception is
java.net.MalformedURLException: no protocol: localhost:1099] ]
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot
intialize Resource Manager Connection Factory resources because could not
get JNDI context: javax.naming.ConfigurationException [Root exception is
java.net.MalformedURLException: no protocol: localhost:1099] ]
at
weblogic.j2ee.RMCFactoryDeployer.<init>(RMCFactoryDeployer.java:50)
at weblogic.j2ee.J2EEService.initialize(J2EEService.java:93)
at
weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
i have checked that rmiregistry is up and 1099 port is listening. Does
anyone know why ?
thank you very much
regrds
and

Problem starting Weblogic Managed Server SOA11g

While restarting the server, after starting weblogic server(no errors), when i try to start managed server, getting this exception,
SEVERE: FabricProviderServlet.handleException Error during retrieval of test page or composite resourceoracle.fabric.common.FabricException: Failed to concatanate the following 2 urls: home= "null" and relative="SCA-INF/classes".: no protocol: SCA-INF/classes
at oracle.fabric.common.metadata.MetadataManagerImpl.resolve(MetadataManagerImpl.java:316)
at oracle.fabric.composite.model.CompositeModel.getClassLoaderFiles(CompositeModel.java:362)
at oracle.fabric.composite.model.CompositeModel.getCompositeClassloader(CompositeModel.java:203)
at oracle.integration.platform.blocks.soap.FabricProviderServlet.doGet(FabricProviderServlet.java:289)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
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.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:326)
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)
Caused by: java.net.MalformedURLException: no protocol: SCA-INF/classes
at java.net.URL.<init>(URL.java:567)
at java.net.URL.<init>(URL.java:464)
at oracle.fabric.common.metadata.MetadataManagerImpl.resolve(MetadataManagerImpl.java:313)
... 20 more
Also on the em console, all the deployed composites' status are shown as pending.
Any idea why this is happening ?
Thanks,
Shyamala

I am facing the same issue...
any solution on this?
Regards,
Vikrant korde

Problem while starting managed server using nodemanager

Hi everyone,
I am using WLST of Weblogic server 10.3, to automate the creation of domain, managed servers,JDBC,JMS resources etc.. and trying to start the managed servers using node manager. I have an environment which contains few domains. All the domains are using machine named "X".
Now, i am creating the same machine in my domain WLSTDomain. I have the following doubts.
Is there a way to check whether the nodemanager(of X) is already running.
If there is a way to check that, how can we start the managed servers in WLSTDomain using that existing nodemanager.

1. yes you can check if the nodemanage is running using the following ways.
For linux env:-
a. Check if the JAVA process for nodemanager is running ps -ef | grep java and see the nodemanager process else /usr/sbin/lsof -i:$port (port of nodemanager).
b. Login to Admin Console --> Environment --> Machines --> Click on Machines --> Nodemanager --> Monitoring will give you nodemanager status from Admin console.
c. use nm() command with WLST
Example:
wls:/mydomain/serverConfig> nm()
Currently connected to Node Manager that is monitoring the domain "mydomain"
wls:/mydomain/serverConfig> nm()
Not connected to any Node Manager
wls:/mydomain/serverConfig>
To see if WLST connects to nodemanager or not?
help('nmLog') --> to check the nm logs
2. To start the nodemanager using WLST here are the commands
Example:
For single managed Server
wls:/mydomain/serverConfig> start('myserver', 'Server', block='false')
Starting server 'myserver' ...
The server 'myserver' started successfully.
wls:/mydomain/serverConfig>
For Cluster
wls:/mydomain/serverConfig> start('mycluster', 'Cluster')
Starting the following servers in Cluster, mycluster: MS1, MS2, MS3...
All servers in the cluster mycluster are started successfully.
wls:/mydomain/serverConfig>

OIM 11gR2 : Problem while starting managed server

Hello Experts,
I ran config.sh in order to extend my schema to include APM (Authorization Policy Manager) in OIM 11gR2.
After that i took a restart of the servers. When i am trying to start the managed servers they're not starting in the RUNNING mode. Instead they're starting in the ADMIN mode.
The logs are showing the following error :
Internal Exception: java.sql.SQLException: Listener refused the connection with the following error:
ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
Kindly help me out.

1. yes you can check if the nodemanage is running using the following ways.
For linux env:-
a. Check if the JAVA process for nodemanager is running ps -ef | grep java and see the nodemanager process else /usr/sbin/lsof -i:$port (port of nodemanager).
b. Login to Admin Console --> Environment --> Machines --> Click on Machines --> Nodemanager --> Monitoring will give you nodemanager status from Admin console.
c. use nm() command with WLST
Example:
wls:/mydomain/serverConfig> nm()
Currently connected to Node Manager that is monitoring the domain "mydomain"
wls:/mydomain/serverConfig> nm()
Not connected to any Node Manager
wls:/mydomain/serverConfig>
To see if WLST connects to nodemanager or not?
help('nmLog') --> to check the nm logs
2. To start the nodemanager using WLST here are the commands
Example:
For single managed Server
wls:/mydomain/serverConfig> start('myserver', 'Server', block='false')
Starting server 'myserver' ...
The server 'myserver' started successfully.
wls:/mydomain/serverConfig>
For Cluster
wls:/mydomain/serverConfig> start('mycluster', 'Cluster')
Starting the following servers in Cluster, mycluster: MS1, MS2, MS3...
All servers in the cluster mycluster are started successfully.
wls:/mydomain/serverConfig>

Problem with starting managed server

In a domain , I have one admin server and one managed server. When im trying to start managed server , the message says,
Message icon - Warning For server Server-0, the Node Manager associated with machine Machine-0 is not reachable.
Message icon - Warning All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed.
Already i started the node manager , i checked with node manager's log files, and I found these error in log files,
<Jul 30, 2010 12:54:32 PM> <Warning> <Uncaught exception in server handler: javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from 127.0.0.1 - 127.0.0.1. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from 127.0.0.1 - 127.0.0.1. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.
     at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
     at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertReceived(Unknown Source)
     at com.certicom.tls.record.alert.AlertHandler.handle(Unknown Source)
     at com.certicom.tls.record.alert.AlertHandler.handleAlertMessages(Unknown Source)
     at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
     at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
     at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
     at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
     at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
     at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
     at com.certicom.tls.record.ReadHandler.read(Unknown Source)
     at com.certicom.io.InputSSLIOStreamWrapper.read(Unknown Source)
     at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
     at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
     at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
     at java.io.InputStreamReader.read(InputStreamReader.java:167)
     at java.io.BufferedReader.fill(BufferedReader.java:136)
     at java.io.BufferedReader.readLine(BufferedReader.java:299)
     at java.io.BufferedReader.readLine(BufferedReader.java:362)
     at weblogic.nodemanager.server.Handler.run(Handler.java:66)
     at java.lang.Thread.run(Thread.java:619)
Can any one help me to troubleshoot this.

Hi Jose,
To Disable SSL communication for NodeManager do the following:
<b><font color=maroon>Step1).</font></b> Open the *"nodeManager.properties"* file from *<WL_HOME>\common\nodemenager* (Example Location : C:\bea103\wlserver_10.3\common\nodemanager ) directory and change the value of SecureListener property to false:
SecureListener=false
<b><font color=maroon>Step2).</font></b> Login to AdminConsole and then
AdminConsoleHome--->Machines --><Your_MachineName> (Click here)--->NodeManager (Tab)---> Select the type as "Plain" from the combo box (by default it will be SSL)
<b><font color=maroon>Step3).</font></b> Restart the NodeManager ....better if you follow Step4) as well...
<b><font color=maroon>Step4).</font></b> Please Enroll your NodeManager as described in the Step8) of the following Link: http://weblogic-wonders.com/weblogic/2010/04/28/weblogic-clustering-in-remote-boxes/
Thanks
Jay SenSharma

Problem with stoping managed server

I have wls 10.3.5 on solaris10 64bit, created the domain mytest_cluster with AdminServer and two managed servers in one cluster: ms1 and m2.
All are on the same server.
For ms1 I can start and stop with no problem.
For ms2 I can start, but I cannot stop it without killin it from OS.
The log for the stop as :
>
Stopping Weblogic Server...
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
This Exception occurred at Mon Dec 05 15:44:53 GMT 2011.
java.lang.NullPointerException
at weblogic.management.scripting.WLSTHelper.loadUsernameAndPasswordFromBootProperties(WLSTHelper.java:293)
at weblogic.management.scripting.WLSTHelper.loadUsernameAndPasswordFromBootProperties(WLSTHelper.java:281)
at weblogic.management.scripting.WLSTHelper.getUsernameAndPassword(WLSTHelper.java:270)
at weblogic.management.scripting.WLSTHelper.connect(WLSTHelper.java:158)
at weblogic.management.scripting.WLScriptContext.connect(WLScriptContext.java:61)
at weblogic.management.scripting.utils.WLSTUtil.initializeOnlineWLST(WLSTUtil.java:147)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.python.core.PyReflectedFunction.__call__(Unknown Source)
at org.python.core.PyMethod.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.core.PyObject.invoke(Unknown Source)
at org.python.pycode._pyx4.connect$1(<iostream>:16)
at org.python.pycode._pyx4.call_function(<iostream>)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyFunction.__call__(Unknown Source)
at org.python.pycode._pyx15.f$0(/oraclebase/product/Middleware11.1.1/user_projects/domains/mytest_cluster/shutdown.py:6)
at org.python.pycode._pyx15.call_function(/oraclebase/product/Middleware11.1.1/user_projects/domains/mytest_cluster/shutdown.py)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyCode.call(Unknown Source)
at org.python.core.Py.runCode(Unknown Source)
at org.python.util.PythonInterpreter.execfile(Unknown Source)
at weblogic.management.scripting.WLST.main(WLST.java:124)
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 weblogic.WLST.main(WLST.java:29)
Problem invoking WLST - Traceback (innermost last):
File "/oraclebase/product/Middleware11.1.1/user_projects/domains/mytest_cluster/shutdown.py", line 6, in ?
File "<iostream>", line 22, in connect
File "<iostream>", line 646, in raiseWLSTException
WLSTException: Error occured while performing connect : Error connecting to the server
Use dumpStack() to view the full stacktrace
Done
Stopping Derby Server...
>
The error is kind og generic, How I can troubleshoot this?
Note that I can start it and all the components are on the same server.
Thanks
Edited by: gadba on Dec 5, 2011 11:04 AM

Has anyone had the similar problem?
There is another problem with the MS2. I created boot.properties and seems it does not affect because the start still asks for the username and the password.
I have done the same with MS1 without the problem.

Authentication for user weblogic denied problem when starting managed serve

Hi All,
I have a strange situation here. I installed WLS and SOA and BAM servers. Initially I could start both WLS and SOA.
Later I changed some files (possibly startManagedWebLogic.sh or deleted soa_server1/data/ldap/ or AdminServer/security/boot.properties), but later I remember I changed them back. I am now seeing that my WLS is starting up fine, but SOA is not. I am always getting the error:
<Critical> <WebLogicServer> <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(CommonSecurityServiceManagerDelegateImpl.java:965)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
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)
Truncated. see log file for complete stacktrace
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 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)
Truncated. see log file for complete stacktrace
>
I tried to go to admin console to change/verify the password for weblogic user, and then put plaintext password in AdminServer/security/boot.properties, then restart Adminserver. But I still cannot start SOA server.
Could you please let me know how to resolve this issue? I do want to save my environment at this point. Many thanks.

Hi,
My understanding is admin user server is coming up fine but when you try to bring the soa_server1(managed instance) is not coming up due the below mentioned exception.
If not please correct me.
I have a few query, please give me comment on this.
1) Admin and managed instances are running on the same box or different
2) Did you try to reset the password from console or using weblogic.security command
3) Did you cleared the soa_server1 temp directory(server/soa_server1/*)
Solution-1 (If Domain running on different box)
=============================
1) Copy the DefaultAuthenticatorInit.ldift file from Domain_dir/Security/ to Remote machine - Domain_dir/Security/
Note- Remote machine - take a backup of DefaultAuthenticatorInit file.
2) Remote machine- rename or take a backup of ldap directory and boot.properties file
/servers/soa_server1/ldap
/servers/soa_server1/security/boot.properties.
3) Now try to brought up the soa_server1.It will prompt you the username and password.
Please let me know.
Thanks,
Rajkumar

Problem Cloning a Managed Server

Similar Messages

Maybe you are looking for