Starting UCM Servers from Nodemanager
Hi,
We wanted to start UCM servers from nodemanager. But, when I am starting AdminServer from nodemanager, EM and FMW Welcome Page Application (11.1.0.0.0) applications are failing to deloy. Admin logs are complaining for ClassNotFound like below:-
<Feb 10, 2012 10:03:07 AM IST> <Critical> <WebLogicServer> <BEA-000286> <Failed to invoke startup class "JRF Startup Class", java.lang.ClassNotFoundException: oracle.jrf.wls.JRFStartup
java.lang.ClassNotFoundException: oracle.jrf.wls.JRFStartup
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
Truncated. see log file for complete stacktrace
>
<Feb 10, 2012 10:03:07 AM IST> <Critical> <WebLogicServer> <BEA-000286> <Failed to invoke startup class "JPS Startup Class", java.lang.ClassNotFoundException: oracle.security.jps.wls.JpsWlsStartupClass
java.lang.ClassNotFoundException: oracle.security.jps.wls.JpsWlsStartupClass
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
Truncated. see log file for complete stacktrace
>
<Feb 10, 2012 10:03:07 AM IST> <Critical> <WebLogicServer> <BEA-000286> <Failed to invoke startup class "ODL-Startup", java.lang.ClassNotFoundException: oracle.core.ojdl.weblogic.ODLConfiguration
java.lang.ClassNotFoundException: oracle.core.ojdl.weblogic.ODLConfiguration
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
Truncated. see log file for complete stacktrace
>
<Feb 10, 2012 10:03:07 AM IST> <Critical> <WebLogicServer> <BEA-000286> <Failed to invoke startup class "AWT Application Context Startup Class", java.lang.ClassNotFoundException: oracle.jrf.AppContextStartup
java.lang.ClassNotFoundException: oracle.jrf.AppContextStartup
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
Truncated. see log file for complete stacktrace
>
<Feb 10, 2012 10:03:07 AM IST> <Critical> <WebLogicServer> <BEA-000286> <Failed to invoke startup class "JMX Framework Startup Class", java.lang.ClassNotFoundException: oracle.as.jmx.framework.wls.spi.StartupListener
java.lang.ClassNotFoundException: oracle.as.jmx.framework.wls.spi.StartupListener
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
Truncated. see log file for complete stacktrace
>
<Feb 10, 2012 10:03:07 AM IST> <Critical> <WebLogicServer> <BEA-000286> <Failed to invoke startup class "JOC-Startup", java.lang.ClassNotFoundException: oracle.ias.cache.Startup
java.lang.ClassNotFoundException: oracle.ias.cache.Startup
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
Truncated. see log file for complete stacktrace
>
<Feb 10, 2012 10:03:07 AM IST> <Critical> <WebLogicServer> <BEA-000286> <Failed to invoke startup class "DMS-Startup", java.lang.ClassNotFoundException: oracle.dms.wls.DMSStartup
java.lang.ClassNotFoundException: oracle.dms.wls.DMSStartup
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
Truncated. see log file for complete stacktrace
>
<Feb 10, 2012 10:03:10 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Feb 10, 2012 10:03:10 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Feb 10, 2012 10:03:29 AM IST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'DMS Application [Version=11.1.1.1.0]' due to error java.lang.NoClassDefFoundError: oracle/dms/http/Request.
java.lang.NoClassDefFoundError: oracle/dms/http/Request
at java.lang.Class.getDeclaredFields0(Native Method)
at java.lang.Class.privateGetDeclaredFields(Class.java:2291)
at java.lang.Class.getDeclaredFields(Class.java:1743)
at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAnnotationProcessor.java:1024)
at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAnnotationProcessor.java:1017)
Truncated. see log file for complete stacktrace
Caused By: java.lang.NoClassDefFoundError: oracle/dms/http/Request
at java.lang.Class.getDeclaredFields0(Native Method)
at java.lang.Class.privateGetDeclaredFields(Class.java:2291)
at java.lang.Class.getDeclaredFields(Class.java:1743)
at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAnnotationProcessor.java:1024)
at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAnnotationProcessor.java:1017)
Truncated. see log file for complete stacktrace
>
<Feb 10, 2012 10:03:29 AM IST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'FMW Welcome Page Application [Version=11.1.0.0.0]' due to error weblogic.management.DeploymentException: .
weblogic.management.DeploymentException:
at weblogic.application.internal.flow.BaseLifecycleFlow$CreateMainClassAction.run(BaseLifecycleFlow.java:270)
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:104)
at weblogic.application.internal.flow.HeadLifecycleFlow.createMainClass(HeadLifecycleFlow.java:86)
Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: oracle.jrf.wls.StartupClassesAppExecutor
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:280)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:253)
at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:177)
Truncated. see log file for complete stacktrace
>
When processing WebService module 'wsil.war'. Failed to load servlet Class: oracle.j2ee.ws.server.wsil.WSILServlet
Ignoring: unable to load class:java.lang.ClassNotFoundException: oracle.j2ee.ws.server.wsil.WSILServlet at: weblogic.xml.schema.binding.util.ClassUtil.loadClass(ClassUtil.java:76)
When processing WebService module 'wsil.war'. Failed to load servlet Class: oracle.j2ee.ws.server.wsil.WSILServlet
Ignoring: unable to load class:java.lang.ClassNotFoundException: oracle.j2ee.ws.server.wsil.WSILServlet at: weblogic.xml.schema.binding.util.ClassUtil.loadClass(ClassUtil.java:76)
<Feb 10, 2012 10:03:29 AM IST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'em' due to error weblogic.management.DeploymentException: .
weblogic.management.DeploymentException:
at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:176)
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:104)
at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117)
Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: oracle.security.jps.wls.listeners.JpsApplicationLifecycleListener
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:280)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:253)
at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:177)
Truncated. see log file for complete stacktrace
>
Feb 10, 2012 10:03:31 AM com.sun.faces.config.ConfigureListener contextInitialized
INFO: Initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/console'
Feb 10, 2012 10:03:31 AM com.sun.faces.config.ConfigureListener contextInitialized
INFO: Completed initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/console'
<Feb 10, 2012 10:03:33 AM IST> <Error> <HTTP> <BEA-101165> <Could not load user defined filter in web.xml: ServletContext@35590877[app:wsil-wls module:/inspection.wsil path:/inspection.wsil spec-version:2.5] oracle.dms.wls.DMSServletFilter.
java.lang.ClassNotFoundException: oracle.dms.wls.DMSServletFilter
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:280)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:253)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:56)
at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
Truncated. see log file for complete stacktrace
>
<Feb 10, 2012 10:03:33 AM IST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'wsil-wls'.
weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1514)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: oracle.dms.wls.DMSServletFilter
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:280)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:253)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:56)
at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
Truncated. see log file for complete stacktrace
>
<Feb 10, 2012 10:03:33 AM IST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<Feb 10, 2012 10:03:33 AM IST> <Critical> <WebLogicServer> <BEA-000286> <Failed to invoke startup class "Audit Loader Startup Class", java.lang.ClassNotFoundException: oracle.security.audit.ajl.loader.JEEAuditLoader
java.lang.ClassNotFoundException: oracle.security.audit.ajl.loader.JEEAuditLoader
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
Truncated. see log file for complete stacktrace
<Feb 10, 2012 10:46:59 AM IST> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=AppApplicationOverviewPage&AppApplicationOverviewPortlethandle=com.bea.console.handles.AppDeploymentHandle%28%22com.bea%3AName%3DFMW+Welcome+Page+Application%2311.1.0.0.0%2CType%3DAppDeployment%22%29.>
java.lang.ClassNotFoundException: oracle.as.jmx.framework.util.MBeansXmlServletContextListenerSupport
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:280)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:253)
at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:177)
at weblogic.servlet.internal.WebAnnotationProcessorImpl.processListeners(WebAnnotationProcessorImpl.java:249)
at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:211)
at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:108)
at weblogic.application.compiler.WARModule.processAnnotations(WARModule.java:433)
at weblogic.application.compiler.EARModule.processAnnotations(EARModule.java:227)
at weblogic.application.compiler.WARModule.merge(WARModule.java:483)
at weblogic.application.compiler.flow.MergeModuleFlow.compile(MergeModuleFlow.java:23)
at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:70)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
at weblogic.application.compiler.FlowDriver$CompilerFlowDriver.compile(FlowDriver.java:97)
at weblogic.application.compiler.ReadOnlyEarMerger.merge(ReadOnlyEarMerger.java:50)
at weblogic.application.compiler.flow.AppMergerFlow.mergeInput(AppMergerFlow.java:88)
at weblogic.application.compiler.flow.AppMergerFlow.compile(AppMergerFlow.java:42)
at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:70)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
at weblogic.application.compiler.FlowDriver$CompilerFlowDriver.compile(FlowDriver.java:97)
at weblogic.application.compiler.AppMerge.runBody(AppMerge.java:157)
at weblogic.utils.compiler.Tool.run(Tool.java:158)
at weblogic.utils.compiler.Tool.run(Tool.java:116)
at weblogic.application.compiler.AppMerge.merge(AppMerge.java:170)
at weblogic.deploy.api.internal.utils.AppMerger.merge(AppMerger.java:88)
at weblogic.deploy.api.internal.utils.AppMerger.getMergedApp(AppMerger.java:63)
at weblogic.deploy.api.model.internal.WebLogicDeployableObjectFactoryImpl.createDeployableObject(WebLogicDeployableObjectFactoryImpl.java:181)
at weblogic.deploy.api.model.internal.WebLogicDeployableObjectFactoryImpl.createDeployableObject(WebLogicDeployableObjectFactoryImpl.java:163)
at weblogic.deploy.api.tools.SessionHelper.initialize(SessionHelper.java:727)
at weblogic.deploy.api.tools.SessionHelper.initializeConfiguration(SessionHelper.java:557)
at weblogic.deploy.api.tools.SessionHelper.initializeConfiguration(SessionHelper.java:545)
at weblogic.deploy.api.tools.SessionHelper.initializeConfiguration(SessionHelper.java:628)
at com.bea.console.utils.DeploymentConfigurationHelper$1.execute(DeploymentConfigurationHelper.java:760)
at com.bea.console.utils.DeploymentUtils.runDeploymentAction(DeploymentUtils.java:5000)
at com.bea.console.utils.DeploymentConfigurationHelper.initDeploymentConfiguration(DeploymentConfigurationHelper.java:747)
at com.bea.console.utils.DeploymentConfigurationHelper.<init>(DeploymentConfigurationHelper.java:352)
at com.bea.console.utils.DeploymentConfigurationManager.createDeploymentConfigurationHelper(DeploymentConfigurationManager.java:238)
at com.bea.console.utils.DeploymentConfigurationManager.getDeploymentConfiguration(DeploymentConfigurationManager.java:104)
at com.bea.console.utils.DeploymentConfigurationManager.getDeploymentConfiguration(DeploymentConfigurationManager.java:65)
at com.bea.console.utils.PersistenceUtils.getPersistenceUnitNames(PersistenceUtils.java:76)
at com.bea.console.utils.PersistenceUtils.hasPersistenceUnits(PersistenceUtils.java:52)
at com.bea.console.utils.AppDeploymentBackingFile.preRender(AppDeploymentBackingFile.java:103)
at com.bea.netuix.servlets.controls.Backable$Impl.preRender(Backable.java:191)
at com.bea.netuix.servlets.controls.AdministeredBackableControl.preRender(AdministeredBackableControl.java:104)
at com.bea.netuix.servlets.controls.window.Window.preRender(Window.java:432)
at com.bea.netuix.servlets.controls.page.Page.preRender(Page.java:247)
at com.bea.netuix.nf.ControlLifecycle$6.visit(ControlLifecycle.java:429)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:727)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:146)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
at com.bea.netuix.nf.Lifecycle.runOutbound(Lifecycle.java:208)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:162)
at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:389)
at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258)
at com.bea.netuix.servlets.manager.UIServlet.doGet(UIServlet.java:212)
at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:196)
at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:253)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.service(MBeanUtilsInitSingleFileServlet.java:47)
at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:131)
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:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
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:2268)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
<Feb 10, 2012 10:47:28 AM IST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1328851041750' for task '0'. Error is: 'weblogic.management.DeploymentException: '
weblogic.management.DeploymentException:
at weblogic.application.internal.flow.BaseLifecycleFlow$CreateMainClassAction.run(BaseLifecycleFlow.java:270)
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:104)
at weblogic.application.internal.flow.HeadLifecycleFlow.createMainClass(HeadLifecycleFlow.java:86)
Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: oracle.jrf.wls.StartupClassesAppExecutor
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:280)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:253)
at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:177)
Truncated. see log file for complete stacktrace
>
Thanks,
Sanjeev
Thanks Srinath! It worked, however nodemanager is not coming reachable from ADMIN console :(. nodemanager log contains
<Feb 13, 2012 9:46:12 AM> <WARNING> <Uncaught exception in server handlerjavax.net.ssl.SSLHandshakeException: [Security:090476]Invalid/unknown SSL header was received from peer PUNITP196433D.ad.infosys.com - 10.76.246.81 during SSL handshake.>
javax.net.ssl.SSLHandshakeException: [Security:090476]Invalid/unknown SSL header was received from peer PUNITP196433D.ad.infosys.com - 10.76.246.81 during SSL handshake.
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(Unknown Source)
at com.certicom.tls.record.ReadHandler.fireAlert(Unknown Source)
Regards,
Sanjeev
Similar Messages
-
Unable to start managed servers from Admin Console "FAILED_NOT_RESTARTABLE"
I recently installed WebLogic 10.3.5, JRockit, and ECM 11.1.1.5. I'm to the point where I am trying to get Nodemanager configured so I can stop/start managed servers through the admin console. I have the following listed in Environment > Servers:
AdminConsole - running
IBR_server1 - FAILED_NOT_RESTARTABLE
managedServer1 - FAILED_NOT_RESTARTABLE
UCM_server1 - FAILED_NOT_RESTARTABLE
I followed the tutorial at http://blogs.oracle.com/jamesbayer/entry/weblogic_nodemanager_quick_sta to get to the point where the AdminServer starts when the server reboots, so I think Nodemanager is working there. If I view Machines > Monitoring, it says Nodemanager "Reachable." However, when I go to restart IBR_server1, managedServer1, or UCM_server1, I get the FAILED_NOT_RESTARTABLE status. I am using the weblogic server's IP for the machine name/host because our DNS is still screwed up. Would that have any affect on this?
I'm completely unsure what to do now. The Nodemanager log shows:
INFO - <Loading domains file: E:\oracle\MIDDLE~1\WLSERV~1.3\common\nodemanager\nodemanager.domains>
WARNING - <Domains file not found: E:\oracle\MIDDLE~1\WLSERV~1.3\common\nodemanager\nodemanager.domains>
INFO - <Loading identity key store: FileName=E:/oracle/MIDDLE~1/WLSERV~1.3/server\lib\DemoIdentity.jks, Type=jks, PassPhraseUsed=true>
WARNING - <Node manager configuration properties file 'E:\oracle\MIDDLE~1\WLSERV~1.3\common\nodemanager\nodemanager.properties' not found. Using default settings.>
So I'm confused why it's saying the properties file and domains file are not found... I've checked and they exist at
E:\oracle\middleware\wlserver_10.3\common\nodemanager\nodemanager.properties
and
E:\oracle\middleware\wlserver_10.3\common\nodemanager\nodemanager.domains
The domains file contains
base_domain=e\:\\oracle\\middleware\\user_projects\\domains\\base_domain
Which is correct.
Any idea what I'm missing here? I can provide more detail if needed. Thank you.
EDIT: I should add that I can start the UCM and IBR managed servers using the start up scripts on the server, but that's not what I'm after. I want everything controlled through the AdminConsole and want to be sure that when the server reboots, all the managed servers come back up correctly.
Edited by: user5824683 on Oct 5, 2011 5:04 PM
Edited by: user5824683 on Oct 5, 2011 5:09 PMI did a bit of digging, and it seems I have an issue with -Xnohup... I've verified this arugment exists in all of my managed servers properties files, yet it still bombs when I try to restart from the webLogic console. I should note that if I start fresh from the server, I can start all my manager servers using WLST nmStart().
starting weblogic with Java version:
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
Oracle JRockit(R) (build R28.1.3-11-141760-1.6.0_24-20110301-1430-windows-x86_64, compiled mode)
Starting WLS with line:
E:\java\JROCKI~1.1\bin\java -jrockit -Xms256m -Xmx512m -Dweblogic.Name=IBR_server1 -Djava.security.policy=E:\oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=E:\oracle\middleware\user_projects\domains\base_domain\servers\IBR_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xnohup -Xverify:none -da -Dplatform.home=E:\oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=E:\oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=E:\oracle\MIDDLE~1\WLSERV~1.3\server -Dcommon.components.home=E:\oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1 -Djrockit.optfile=E:\oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\FMWCON~1\servers\IBR_server1 -Doracle.domain.config.dir=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\FMWCON~1\carml -Digf.arisidstack.home=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\servers\IBR_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=E:\oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,E:\oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Ducm.oracle.home=E:\oracle\MIDDLE~1\ORACLE~2 -Dem.oracle.home=E:\oracle\middleware\oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=false -Dweblogic.management.server=http://138.126.180.177:7001 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=e:\oracle\MIDDLE~1\patch_wls1035\profiles\default\sysext_manifest_classpath weblogic.Server
Exception in thread "Main Thread" java.lang.NoClassDefFoundError: –Xnohup
Caused by: java.lang.ClassNotFoundException: –Xnohup
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
Could not find the main class: –Xnohup. Program will exit.
<Oct 6, 2011 12:38:13 PM> <FINEST> <NodeManager> <Waiting for the process to die: 4252>
<Oct 6, 2011 12:38:13 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Oct 6, 2011 12:38:13 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters> -
Facing error in starting managed server from nodemanager
Hi All,
I have installed WebLogic server 10.3.4 and installed OSB 11.1.1.4.0. I created domain with one admin server and one managed server for osb. When I started managed server with the startManagedWebLogic command it got started successfully but when I am trying tp start the managed server from nodemanager I am getting the following error
starting weblogic with Java version:
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
[ERROR] aborted
JRockit aborted: Unknown error (50)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
Starting WLS with line:
D:\JDK\JROCKI~1.0\bin\java -jrockit -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms256m -Xmx512m -Dweblogic.Name=osb_server1 -Djava.security.policy=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=D:\Oracle_OSB\Middleware\user_projects\domains\osb_domain\servers\osb_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xverify:none -da:org.apache.xmlbeans... -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3 -Dwls.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server -Dcommon.components.home=D:\ORACLE~1\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1 -Djrockit.optfile=D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\servers\osb_server1 -Doracle.domain.config.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\carml -Digf.arisidstack.home=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\servers\osb_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dem.oracle.home=D:\Oracle_OSB\Middleware\oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=false -Dweblogic.management.server=http://soaspt-app01.scotwat.net:7010 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=D:\ORACLE~1\MIDDLE~1\patch_wls1034\profiles\default\sysext_manifest_classpath;D:\ORACLE~1\MIDDLE~1\patch_ocp360\profiles\default\sysext_manifest_classpath weblogic.Server
[WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
[ERROR] aborted
JRockit aborted: Unknown error (50)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
<11-Mar-2013 13:22:17> <FINEST> <NodeManager> <Waiting for the process to die: 5916>
<11-Mar-2013 13:22:17> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<11-Mar-2013 13:22:17> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
My nodemanager is started and reachable. The error above says "Address already in use" but I am able to start my managed server through startManagedWebLogic.cmd command.
Can anyone please tell me what could be the issue. It is really urgent. Please help!!Hi Roshni,
It is likely that a configuration is missing or not set properly in the Node Manager properties file (nodemanager.properties) since the managed server can be started up using startManagedWebLogic.cmd but not with Node Manager. I would complete the following steps to fix the problem:
1. Go to %WLS_HOME%\common\nodemanager and open up nodemanager.properties (Make a backup of the file first). NOTE: WLS_HOME is your WebLogic Server home.
2. Look for the parameters "StartScriptEnabled" and "StopScriptEnabled". They should be set to true. If not, please set them to true.
3. Save and close the file.
4. Restart the Node Manager
If you are still unable to start the manager server using Node Manager, you may need to update the DEBUG_PORT parameter in setDomainEnv.cmd located in %MIDDLEWARE_HOME%\user_projects\domains\%DOMAIN_HOME%\bin (always make a backup before changing a configuration file). You may refer to Oracle Support note 1272642.1 for more information about the nodemanager.properties file and how to configure the DEBUG_PORT parameter in setDomainEnv.cmd if needed.
Thanks,
Scott (PITSS)
http://pitss.com/us -
Unable to start Managed servers from admin console
Hello!
We have a problem to start Managed Servers throw Node manager.
We get an error:
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Boot identity properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/boot.properties">
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Boot identity properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/boot.properties"
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Startup configuration properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/startup.properties">
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Startup configuration properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/startup.properties"
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server error log also redirected to server log>
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.LogFileRotationUtil log
INFO: Server error log also redirected to server log
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Starting WebLogic server with command line: /software/psoft/pt851/webserv/peoplesoft/bin/startManagedWebLogic.sh >
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Starting WebLogic server with command line: /software/psoft/pt851/webserv/peoplesoft/bin/startManagedWebLogic.sh
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Working directory is '/software/psoft/pt851/webserv/peoplesoft'>
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Working directory is '/software/psoft/pt851/webserv/peoplesoft'
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Rotated server output log to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out00001">
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.LogFileRotationUtil log
INFO: Rotated server output log to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out00001"
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server error log also redirected to server log>
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.LogFileRotationUtil log
INFO: Server error log also redirected to server log
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server output log file is '/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out'>
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Server output log file is '/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out'
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server failed during startup so will not be restarted>
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Server failed during startup so will not be restarted
<Jan 26, 2012 2:17:54 PM> <WARNING> <Exception while starting server 'PIA1'>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:662)
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'PIA1'
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:662)
Additional information:
weblogic 10.3.3
PT8.51.11
Linux x86_64 RH5
When we starting Manged servers manualy, it's works fine.
Thank you.Hello!
The problem is found.
We tried to startup managed server by running startManagedServer.sh script, but this script expecting to get parameters.
The NodeManager unable to send parameters to script that appears in nodemanager.properties file (StartScriptName).
So, I created a new script startPIA.sh, that calls to startManagedServer.sh and sends it 2 parameters:
./startManagedWebLogic.sh $SERVER_NAME $ADMIN_URL
Now, we can start and stop managed servers from admin console, BUT we still have an error in NodeManager:
<Jan 29, 2012 11:15:39 AM> <INFO> <peoplesoft> <PIA1> <Server failed during startup so will not be restarted>
Jan 29, 2012 11:15:39 AM weblogic.nodemanager.server.ServerManager log
INFO: Server failed during startup so will not be restarted
<Jan 29, 2012 11:15:39 AM> <WARNING> <Exception while starting server 'PIA1'>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:662)
Jan 29, 2012 11:15:39 AM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'PIA1'
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:662)
There are no errors in managed servers logs.
PIA1.out:
<Jan 29, 2012 11:15:38 AM> <INFO> <NodeManager> <Server output log file is '/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out'>
Attempting to start WebLogic Server PIA1
No activity will be logged to this window.
Server activity will be logged to /software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1_*
PID for WebLogic Server PIA1 is: 27018
<Jan 29, 2012 11:15:39 AM> <FINEST> <NodeManager> <Waiting for the process to die: 26847>
<Jan 29, 2012 11:15:39 AM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Jan 29, 2012 11:15:39 AM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
The status of managed server in admin console is RUNNING, but "Status of Last Action" is FAILED.
What can be the reason?
Thank you. -
Cannot start Managed server from NodeManager
Hello All,
Software version installed:-
Oracle Jdeveloper 11.1.1.7
Weblogic 10.3.6
RCU:- 11.1.1.7
SOA suite:-11.1.1.7
OSB 11.1.1.7
OS windows 7 ultimate 64 bit
=====================
Sucessfully installed all the above software. I planned to install AIA Foundation Pack and for this i need to configure node manager do start
manage servers.
Node manager configuration sucessfully done by following @http://neeraj-soa-tips.blogspot.in/2010/06/part-1-how-to-configure-node-manager-to.html
after this i am see node manger status as reachable in weblogic console.
From admin console under servers control tab, i tried starting soa_server1 but i am getting below error in nodemanger window.
java.io.IOException: Cannot run program "E:\Oracle\MiddleWare\wlserver_10.3\comm
on\bin\bin\startWebLogic.cmd" (in directory "E:\Oracle\MiddleWare\wlserver_10.3\
common\bin"): CreateProcess error=2, The system cannot find the file specified
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1041)
at weblogic.nodemanager.server.WLSProcessImpl.start(WLSProcessImpl.java:
44)
at weblogic.nodemanager.server.WLSProcess.startProcess(WLSProcess.java:1
94)
at weblogic.nodemanager.server.AbstractServerMonitor.startWLSProcess_inn
er(AbstractServerMonitor.java:419)
at weblogic.nodemanager.server.AbstractServerMonitor.startWLSProcess(Abs
tractServerMonitor.java:358)
at weblogic.nodemanager.server.AbstractServerMonitor.start(AbstractServe
rMonitor.java:103)
at weblogic.nodemanager.server.ServerMonitor.start(ServerMonitor.java:25
at weblogic.nodemanager.server.AbstractServerManager.startServer(Abstrac
tServerManager.java:210)
at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServe
rManager.java:181)
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:609)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
at weblogic.nodemanager.server.Handler.run(Handler.java:71)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.io.IOException: CreateProcess error=2, The system cannot find th
e file specified
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(ProcessImpl.java:385)
at java.lang.ProcessImpl.start(ProcessImpl.java:136)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1022)
... 13 more
I request everyone that if any one has idea on the above error then please throw light on me , this issue is really annoying me.
Also to make sure i tried starting startManagedWebLogic.cmd and sucessfull can see soa_server1 in running state.Note that it is saying that it cannot the file
" Cannot run program "E:\Oracle\MiddleWare\wlserver_10.3\common\bin\bin\startWebLogic.cmd" (in directory "E:\Oracle\MiddleWare\wlserver_10.3\common\bin"): CreateProcess error=2, The system cannot find the file specified"
What is somewhat strange is that it is expecting startWebLogic to be present in ${WL_HOME}/common/bin/bin. The second /bin/ does not exist (well not in normal installations). Also the location of startWebLogic is odd, usually this should be present, in the ${DOMAIN_HOME}/bin directory. Could be there are some paths incorrect in JDeveloper. -
Starting managed servers from admin console vs. command line
Will the arguments I enter in the "Arguments" section of the "Server start" admin console page also be used if I start the managed server from the command line using startManagedWeblogic.sh?
And conversely, will changes I make to the scripts take effect when I start the server from the admin console?No,
the arguments that you set thru Console GUI are effective when Node manager start your server.
Ammar Sajdi -
Problem while starting Managed Servers from Admin Server console
I am facing a problem while trying to start the managed servers in wlp8.1 portal from the admin server console.
<Dec 7, 2004 4:52:14 PM IST> <Info> <NodeManager@*.*:5555> <Starting Server orbitPortalDomain::orbit_ManagedServer1 ...>
<Dec 7, 2004 4:52:16 PM IST> <Info> <NodeManager@*.*:5555> <Server orbitPortalDomain::orbit_ManagedServer1 started, process id = 1,832>
<Dec 7, 2004 4:52:17 PM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.4.2_04-b05 from Sun Microsystems Inc.>
<Dec 7, 2004 4:52:18 PM IST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://10.6.0.212:7001 to check if there exists a running admin server at this URL.>
<Dec 7, 2004 4:52:18 PM IST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Dec 7, 2004 4:52:18 PM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
WebLogic XMLX Module 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973 >
<Dec 7, 2004 4:52:18 PM IST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://10.6.0.212:7001 to retrieve the initial configuration.>
<Dec 7, 2004 4:52:21 PM IST> <Notice> <Log Management> <BEA-170019> <The server log file D:\bea_turner\weblogic81\common\nodemanager\orbit_ManagedServer1\orbit_ManagedServer1.log is opened. All server side log events will be written to this file.>
The WebLogic Server did not start up properly.
java.lang.NoClassDefFoundError: com/bea/wsrp/util/debug/Debug
at com.bea.wsrp.security.WSRPIdentityAsserterProviderImpl.<clinit>(WSRPIdentityAsserterProviderImpl.java:45)
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:274)
at java.lang.Class.newInstance0(Class.java:308)
at java.lang.Class.newInstance(Class.java:261)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.createSecurityProvider(SecurityServiceManagerDelegateImpl.java:232)
at weblogic.security.service.SecurityServiceManager.createSecurityProvider(SecurityServiceManager.java:939)
at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:151)
at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:257)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.doATN(SecurityServiceManagerDelegateImpl.java:581)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealm(SecurityServiceManagerDelegateImpl.java:420)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.loadRealm(SecurityServiceManagerDelegateImpl.java:698)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealms(SecurityServiceManagerDelegateImpl.java:731)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(SecurityServiceManagerDelegateImpl.java:874)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:717)
at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:822)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:670)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:344)
at weblogic.Server.main(Server.java:32)
Reason: com/bea/wsrp/util/debug/Debug
pls advice
Thanks
SasankaHello,
There is a lot of stuff on this thread:
http://forum.java.sun.com/thread.jspa?threadID=567363&messageID=2801617
these guys are trying to run weblogic with JBuilder.
Looks like your classpath is incorrect, can you go to your admin console-->server-->remote start
copy the classpath and post it here.
Check for spaces in your classpath, missing jars or directories and miss spelt paths.
Has this problem been occuring as soon as you installed WLP or not?
Cheers,
Hoos -
Starting managed servers using Nodemanager
When I try to start a manage server using the nodemanager sitting on the same machine
as the Admin Server and the nodemanager itself, I get the following message:
<Error> <NodeManager> <Could not start server 'serverA' via Node Manager - reason:
'[SecureSocketListener: Could not load certificate '.\\c:\weblogic6.1\wlserver6.1/config/mydomain/demo.crt'
of type 'RSA' - reason: '.\\c:\weblogic6.1\wlserver6.1/config/mydomain/demo.crt
(The filename, directory name, or volume label syntax is incorrect)']'>
What's causing this?Hi,
Try deactivating Hostname Verification to None in the admin server throught the WLS console. If you have configured the nodemanager.hosts with the ip of the admin server with this step should work. I fthe admin server is with dns name then you need to enable reverse DNS lookup in the nodemanager.properties file, or with the command-line argument:
ReverseDnsEnabled=true -
Hi,
Environment: WebLogic 6.1 SP2, JDK1.3.1, Solaris 8
1. How to start the managed servers using NodeManager from the command line? Already
NodeManager configured and able to start managed servers from the Admin Console.
So from the console start/stop/kill managed servers is fine. From the command
line, if I use `weblogic.Server` to start managed server it's not using the node
manager.
2. In the `java weblogic.nodemanager.NodeManager help`, option `starttemplate`
defaults to `nodemanager.sh`. Any details on this please ?
3. Each time we start managed server with Node Manager, it writes the output to
the new file `OutputFile=./config/NodeManagerlogs/<server>/startserver-<XXXX.log`.
From the documentation it looks like we can set logs directory
`-Dweblogic.nodemanager.savedLogsDirectory=path`, however is it possible to specify
the log file name also?
4. Where is the location of the java applications `System.out`, if the managed
server is started with NodeManager. If the managed server is started with `weblogic.Server`
the `System.out` are printed to the console. So this enables us to redirect to
a file.
thanks
Sarva MeduriI think you can configure the NodeMgr to start ManagedServers instead of having the
Windows Service start the servers. Basically you configure NodeMgr as a Windows Service
and then let NM take care of starting other servers. I believe you have to set
ManagedServer's HostsMigratableServices attribute to false to enable NM start the server.
By default it is true.
prasen
Gerardo Rojas wrote:
Hi:
I have been trying to configure my WebLogic environment to start the managed servers
in a domain automatically when the machine is rebooted. I have done some testing
with Node Manager but, as I understood, Node Manager only restarts a server if
it was started using Node Manager and the server crashes or fails. On the other
hand, if the server is installed as a Windows service, it will be started at reboot
time, but not when the server (not the machine) crashes or fails. So, both solutions
seems to be uncompatible. Is it right?? Is it possible to have both benefits,
that is, to get the managed servers started at boot time (as done by Windows services)
and restarted each time they fail (as done by Node Manager)?
Thanks,
Gerardo -
Node Manager starting managed servers under different users
Hi all,
I have multiple domains running on the same server.
Is it possible to get node manager to start managed servers from different domains under different users?
Default is the user under which node manager was started originally.
Thanks
ArnaudOracle documentation is still in confussion state for Unix platform nodemanager.
NodeManager Admin Guide had chapter 3 for General configuration of nodemanger. Chapter 5 is for script based nodemanager.
In chapter 5 there is clear way defined for " Starting a node manger for Unix machine".
chapter 3 is mess there is clear-cut direction to reach the remote startup of servers.
Why we have so many types of nodemanager for connect. howbout start them?
Can someone expert in Oracle WebLogic please respond to this.
*Nodemanagers are NOT meant for multiuser development env.
They are defined for production env and for HA, FailOver.*
Edited by: PavanBhavanishekhar on Jan 6, 2010 9:10 PM -
Can i start managed server from another UNIX BOX ..
Hello,
I have created Admin Server on 1 UNIX Box & Managed SErver on 2nd UNIX Box. After
starting ADMIN server on one UNIX Box, i wanted to start managed server using
same script.I can manually login to 2nd unix box & start managed server. I am
wondering if i can start using startup script from 1st UNIX Server.
Thanks
You have to run the startup script from the machine where you want to start the server
for now. Also the script has to be different for admin and managed server as the init
arguments to java commands are different.
We have plans in future to start managed servers from admin servers itself.
Viresh Garg
Principal Developer Relations Engineer
BEA Systems
Wlstech wrote:
> Hello,
>
> I have created Admin Server on 1 UNIX Box & Managed SErver on 2nd UNIX Box. After
> starting ADMIN server on one UNIX Box, i wanted to start managed server using
> same script.I can manually login to 2nd unix box & start managed server. I am
> wondering if i can start using startup script from 1st UNIX Server.
>
> Thanks
-
Unable to start Managed server from admin console using nodemanager
I changed the ip address and hostname of the server on which Weblogic Server 10.3.5 is running. After that I am unable to start the managed servers using Admin console. Is there any changes in the nodemanager configuration files which need to be done to start the managed servers from admin console.
Hi there,
Can you check the following configuration in Weblogic admin console ?
1- Check which listen address mentioned under the Machine configuration ( Environment > Machines > select appropriate nodemanager machine >Configuration > Node Manager ). If it is pointing to old host name, change it to new one.
2- Once you done with Step 1. Check whether the machine is reachable or not. ( Machine > [Your Machine] > Monitoring > status.
3- If still isuse persists.. Check the managed server startup log files ( for eg:- managedserver1.out under the path $DOMAIN_HOME\Servers\managedserver1\logs directory.
Thanks
Lakshman -
Have NodeManager start managed servers on machine reboot
Is there any way to have the Node Manager start all the managed servers belonging to a domain when a server reboots?
I know I could create a separate Windows service for each of the managed servers I want running when the server comes on-line, or I could do some fancy scripting at start-up to connect to the Node Manager and have it start the managed servers.
But I was hoping there would be a more elegant way of having the NM start them when it comes on-line.
Ideas appreciated,
dmac.Hi Dmac,
To achieve this in Windows, you must consider the following WLS Components:
1. Node Manager
2. Admin Server
3. Managed Server
Node Manager
For Node Manager, if you want the component to start automatically on boot up, your best option is to create a Windows Service. You may have selected the option to create a service for Node Manager during the WebLogic Server installation. Use Start -> Run -> services.msc from the Start menu to load the Windows Services Manager. If there is no service for Node Manager, use the following steps to create one.
Create a Windows service for Node Manager:
1. WL_HOME\server\bin\installNodeMgrSvc.cmd
2. Verify in Windows Services that a service was created.
Admin Server
For the Admin Server, you can also create a Windows Service. Here are the steps for doing so:
Create a Windows service for the Admin Server
1. Create a text file named %MIDDLEWARE_HOME%\user_projects\domains\<domain name>\servers\AdminServer\security\boot.properties. Add the following lines:
username=weblogic
password=<the weblogic username password>
2. Create a command script called installAdmServer_Service.cmd which you will want to make sure has lines like:
SETLOCAL
set DOMAIN_NAME=<your wls domain>
set USERDOMAIN_HOME=<path to domain> # e.g., C:\middleware\FMW11g\user_projects\domains\ClassicDomain
set SERVER_NAME=AdminServer
set PRODUCTION_MODE=true
cd %USERDOMAIN_HOME%
call %USERDOMAIN_HOME%\bin\setDomainEnv.cmd
call "<your middleware home>\wlserver_10.3\server\bin\installSvc.cmd"
ENDLOCAL
3. For troubleshooting/debugging purposes it is helpful to redirect standard out and error to a text file. Although most information is captured in the AdminServer server log files, you will not see all standard out and error when the server is started via a MS Windows Service (unlike when you start an AdminServer from the command prompt using startWebLogic.cmd). To redirect standard out to a text file, backup and edit installSvc.cmd and change the line at the bottom of the file so it includes the -log parameter, e.g.
"%WL_HOME%\server\bin\beasvc" -install -svcname:"%DOMAIN_NAME%_%SERVER_NAME%" -javahome:"%JAVA_HOME%" -execdir:"%USERDOMAIN_HOME%" -extrapath:"%WL_HOME%\server\bin" -password:"%WLS_PW%" -cmdline:%CMDLINE% -log:"<your middleware home>\user_projects\domains\<your wls domain name>\servers\AdminServer\logs\AdminServer-stdout.txt"
4. Now run "installAdmServer_Service.cmd." The Service should be installed. It will have a name like "beasvc %DOMAIN_NAME%_%SERVER_NAME%" (e.g. beasvc ClassicDomain_AdminServer). The Service "Startup Type" will be "Automatic." Start the Service. The Service will come back fairly quickly to say it is started. The actual time taken for the admin server to start and reach a state of 'RUNNING' will be longer - perhaps two or three minutes. The state of the server can be monitored by reviewing the stdout txt file.
Managed Server
For the Managed Server, you can also create a Windows Service. Here are the steps for doing so:
Create a Windows service for the Managed Server (using wls_forms as an example)
1. Create a text file named %MIDDLEWARE_HOME%\user_projects\domains\<domain name>\servers\WLS_FORMS\security\boot.properties. Add the following lines:
username=weblogic
password=<the weblogic username password e.g manager11g>
2. Create a command script called installWLSFORMS_Service.cmd which has lines like
SETLOCAL
set DOMAIN_NAME=<your wls domain>
set USERDOMAIN_HOME=<path to domain> # e.g. C:\middleware\FMW11g\user_projects\domains\ClassicDomain
set SERVER_NAME=WLS_FORMS
set PRODUCTION_MODE=true
set ADMIN_URL=http://mymachine.mycompany.com:7001
cd %USERDOMAIN_HOME%
call %USERDOMAIN_HOME%\bin\setDomainEnv.cmd
call "<your middleware home>\wlserver_10.3\server\bin\installSvc.cmd"
ENDLOCAL
NOTES:
a. The ADMIN_URL value should reference the AdminServer hostname and listen port.
b. The SERVER_NAME value is case sensitive. For example, if you are creating a MS Windows service for a different managed server such as 'wls_ods1' then the value needs to match the case of the server name otherwise the startup of the server via the MS Windows service will fail.
c. Be careful that there are no trailing spaces after each line in the command file - trailing spaces will cause the managed server to fail at startup. For example a trailing space in the ADMIN_URL value will result in the error
<19-Jan-2010 11:37:58 o'clock GMT> <Error> <EmbeddedLDAP> <BEA-171524> <Cannot determine the Listen address for the Admin server
3. Now run "installWLSFORMS_Service.cmd." The Service should be installed, it will have a name like "beasvc %DOMAIN_NAME%_%SERVER_NAME%" (e.g. beasvc ClassicDomain_WLS_FORMS). The Service "Startup Type" will be "Automatic." Start the Service. The Service will come back fairly quickly to say it is started. The actual time taken for the managed server to start and reach a state of 'RUNNING' will be longer - perhaps two or three minutes. The state of the server can be monitored by reviewing the stdout txt file.
Configuring the Windows service to restart upon failure
As with any Windows Service, it is possible to configure the service to restart itself upon failure. These are standard options available when configuring a Windows Service in the context of Windows Services Manager. However, it is important to understand that Windows Services Manager only monitors the JVM process. If the JVM process fails (shuts down), then Windows Services Manager will attempt to restart it. But there are some scenarios where the Admin Server or Managed Server may go into an unhealthy or failed state but the JVM is still running. The Windows Service will not know to restart the process in these cases, whereas if the Admin Server and Managed Server had been started using Node Manager, Node Manager would recognize such a state and restart the process accordingly. So it may be desirable to start Node Manager with a Windows Service and then start the Admin Server and Managed Servers with Node Manager to take advantage of this monitoring feature. Below you will find one such example of how to do this.
Example of starting the Admin Server and a Managed Server using Node Manager
1. Create a batch script similar to this:
Myscript.cmd
call D:\Product\Oracle\Middleware\user_projects\domains\base_domain\bin\setDomainEnv.cmd
java weblogic.WLST D:\Product\Oracle\Middleware\user_projects\domains\base_domain\ServerStart.py
2. Create a Python script similar to this:
ServerStart.py
nmConnect('weblogic', 'welcome1', '192.168.0.101', '5556', 'base_domain','D:\Product\Oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1','ssl')
nmStart('AdminServer')
connect ('weblogic','welcome1','t3://192.168.0.101:7001')
nmstart('myserver','Server','t3://192.168.0.101:7002')
If you want this to happen automatically on boot up, you can run the script (myscript.cmd) from the Windows Scheduler. You must configure the scheduler to run the script on system startup. This will execute the script without requiring an interactive login to Windows (unattended).
Some Additional Information to Remember
The startup.properties file for the Admin and Managed servers must have "AutoRestart=true." This can be set in the "Health Monitoring" tab for each respective server in the WLS console.
The boot.properties file must be configured and present for each server that you plan to start automatically so that you are not prompted for the user name and password each time. If you are not currently prompted when you start the servers then it is already done.
The nodemanager.properties file must have "StartScriptEnabled=true" and "StartScriptName=StartWeblogic.cmd" in place. -
How nodemanager starts managed servers?
Hello All,
I'm facing strange issue with weblogic server. Currently i'm using WLS 8.1 SP 4 on solaris 9 server.
To start weblogic i have customize the script such that when server goes on reboot it will pick the startweblogic.sh script from /opt/bin and start the weblogic. Where as in startweblogic.sh i have mentioned -
NMLOG=/u001/wls8/bea/user_projects/prodDomain/logs/optbin/nodemanager.log; export WL8NMLOG
ADMINLOG=/u001/wls8/bea/user_projects/prodDomain/logs/optbin/adminserver.log; export WL8ADMINLOG
CLUSTERLOG=/u001/wls8/bea/user_projects/prodDomain/logs/optbin/cluster.log; export WL8CLUSTERLOG
cd /u001/wls8/bea/weblogic81/server/bin/
su weblogic -c "./startNodeManager.sh >> $NMLOG 2>&1" &
sleep 60
cd /u001/wls8/bea/user_projects/prodDomain/
su weblogic -c "./startadminserver.sh >> $ADMINLOG 2>&1" &
sleep 1200
cd /u001/wls8/bea/user_projects/prodDomain/
su weblogic -c "./startcluster.sh >> $CLUSTERLOG 2>&1" &
Though the script works as expected till adminserver is UP/Running, but script doesn't wait for 1200 secs. to start cluster. Somehow nodemanager starts the managed servers immediately after the adminserver is UP.
I have checked the nodemanager.properties file, there is nothing such mentioned. Also, from console i have unchecked the option of AutoStart for both managed servers.
Can anyone tell me how nodemanager starts the managed servers automatically??
Thanks,
HKcan you please tell me what is this .startCluster.sh script.
is it your custom script?
And the idea i have in my mind is that after
cd /u001/wls8/bea/weblogic81/server/bin/
su weblogic -c "./startNodeManager.sh >> $NMLOG 2>&1" &
sleep 60
cd /u001/wls8/bea/user_projects/prodDomain/
su weblogic -c "./startadminserver.sh >> $ADMINLOG 2>&1" &
sleep 1200
you can give the command to start the individual managed servers like:
cd /u001/wls8/bea/user_projects/prodDomain/
su weblogic -c "./startManagedWebLogic.sh <arguments> >> $CLUSTERLOG 2>&1" &
I think this way it will work.... -
Starting port 80 server from NodeManager
Under Solaris, how do I start a managed server running port 80 from
NodeManager? Will it work if I start NodeManager with root user?
Thanks."JJ" <[email protected]> wrote:
Start with root might work. Just give a try!It is not just a matter of 'it might work'. In Unix[1], it is absolute required
to use the superuser in order to open up a port < 1024.
My recommendation would be to use a web-server(Apache, iPlanet, or whatever you
can find a plug-in for) that support a well-known Unix trick: "Start me (the web-server)
as the superuser. As the superuser, I will open port 80. Then I will create another
process, but this time running as a non-privileged user (e.g. Mr. Nobody). Mr.
Nobody will run the web-server, and since he is 'family' he can inherit my port
80 when I am done. And now I am going to kill myself." And bye, bye Mr. Superuser
process.
Regards,
Jan Bruun Andersen
[1] I haven't tried this, but in some modern Unix'es, you have more advance system
of privileges. Checkout your local man pages for stuff like 'profiles' and 'roles'.
Perhaps you can assign the privilege to create low-numbered ports to your BEA-user?
Maybe you are looking for
-
Dear All, I was able to write below AES/CFB/NoPadding encryption/decryption program (with many thanks to the Internet) and it works fine on Windows. But it's "getByte()" gives problems on Linux. Which is the "symmKey.length()" inside "SymmCipher" con
-
Having trouble sycning apps to phone.
-
eversince i tried to upgrade my electric turned off and something got lost from my origional itunes now i cant uninstall or reinstall and keep getting the message QTCF_CFHTTPmessagesetheaderfieldvalue could not be located in the dynamic link library
-
Hi, I am taking daily online backup from BRTOOLS on a disk(BACKUP SEVER).If I want to take the online backup through DB13 in the disk what is the procedure to be used(step by step) Server ECC5.0 ORACLE 9.2.0.7.0 Regards AAA
-
Ok so I am having a very large problem. My site is only viewed well when it is really small. When i stretch the screen out that i am viewing it on the iframe moves behind my picture. Can someone help? Thanks! PS: i need help with this quick. Here is