Error in starting MDM Server from MDM Console
Hi,
I have installed SAP MDM 5.5 SP05 on Windows 2003 Server.
When i try to start the MDM Server (i.e. MDM Service) from the MDM console it gives me the following error:
<i>Error Starting apmdmd(MDM Server): The machine 'apmdmd' is not Windows-based. The MDM server cannot be started from this application; please use CLIX on the machine instead. </i>
But if i start the MDM Service manually and then mount the server, it works fine.
Kindly help.
Regards,
Chintan Sheth
It sounds to me like a problem potentially with either the permissions of the Windows user or perhaps a software firewall. The Console uses a low-level Windows API function to determine if the target machine on which MDS is installed is Windows-based. This function may be blocked by some OS or firewall-level setting. This may be the case even if you are able to use the same client machine to connect to the target machine via the Service Control Manager and start MDS from there.
I would like to help with this problem, but I need to know a few more things:
When the problem occurs, is the Console running on the same Windows machine as MDS?
You mentioned Windows 2003 Server... when you run the Console on this machine, are you logged in as an Administrator of the machine? And do you still get the error when you attempt to start MDS from within the Console?
Once MDS is started, and you mount it within the Console, are you having any other problems, such as logging in to a repository, or viewing logs?
Is there a firewall installed on the machine or machines that the software is installed on? We may have to review the settings of the firewall, or try temporarily disabling it (on both ends, or at least on the machine running MDS), to see if the problem goes away -- then we'll know the problem is with the firewall settings.
CLIX is a fine workaround if you can use it, but clearly this problem needs to be rectified.
-cleo
Similar Messages
-
Error start managed server from admin console in SSL mode
I have configured Admin server, managed servers and node manager on the same physical server and commonly using a single SSL sertificate.
There is no problem to start node manager, admin server and managed server individually. But if I try to start managed server from the admin console then I am getting the following errors.
<Feb 22, 2005 11:02:26 AM CST> <Info> <[email protected]:6666> <Starting Server peoplesoft::PIA1 ...>
<Feb 22, 2005 11:02:26 AM CST> <Info> <NodeManager@xxxxxxxxxx:6666> <BaseProcessControl: saving process id of Weblogic Managed server 'PIA1', pid: 285390>
<Feb 22, 2005 11:02:35 AM CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Classic VM Version 1.4.1 from IBM Corporation>
<Feb 22, 2005 11:02:36 AM CST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://xxxxxxxx:admin_server_portnumber to check if there exists a running admin server at this URL.>
<Feb 22, 2005 11:02:36 AM CST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Feb 22, 2005 11:02:36 AM CST> <Info> <Management> <BEA-141107> <Version: WebLogic Temporary Patch 8 CR174605 for PeopleSoft 09/09/2004 18:11:35
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284 >
<Feb 22, 2005 11:02:37 AM CST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://xxxxxxxxx.org:Admin_server_portnumber to retrieve the initial configuration.>
<Feb 22, 2005 11:02:45 AM CST> <Notice> <Log Management> <BEA-170019> <The server log file /home/xxxx/webserv/peoplesoft/PIA1/PIA1.log is opened. All server side log events will be written to this file.>
<Feb 22, 2005 11:03:01 AM CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Feb 22, 2005 11:03:01 AM CST> <Warning> <Security> <BEA-090066> <Problem handling boot identity. The following exception was generated: java.lang.NullPointerException>
<Feb 22, 2005 11:03:10 AM CST> <Critical> <Security> <BEA-090174> <The trust keystore configuration specified on the command line or in boot.properties does not match the trust keystore configuration specified in config.xml.>
<Feb 22, 2005 11:03:10 AM CST> <Warning> <NodeManager> <BEA-300038> <The node manager is unable to monitor this server. Could not create an SSL connection to the node manager. Reason : null>
<Feb 22, 2005 11:03:10 AM CST> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.>
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.'
Reason: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.
I am running everything on IBM UNIX server.
I appriciate your help.
Thanks & regards,
Laxman.Hi
From the admin console ... Are you able to check the status of Node Manager ?
If yes ... please check the SSL configuration of managed servers ...
Check the domain administration port also.
Jin -
Starting Managed Server from Administration Console
Hi
I am new for SOA and fusion. Can anyone share the brief steps that are needed to start/stop a Managed Server from Admin Console.
I did a fresh install on RHEL5 and configure a domain. i was able to start the services from script which are created when creating a domain.
But when i assigned a Managed Server to a Node Manager and try starting the Managed server. It does not start and in the log i can see exceptions like below
Failed to invoke startup class "JPS Startup Class", java.lang.ClassNotFoundException: oracle.security.jps.wls.JpsWlsStartupClass
java.lang.ClassNotFoundException
Failed to invoke startup class "ODL-Startup", java.lang.ClassNotFoundException: oracle.core.ojdl.weblogic.ODLConfiguration
java.lang.ClassNotFoundException
I start the services in below order
Weblogic Server
node Manager
and
soa_server
Thanks
Hariyou must set to true the StartScriptEnabled property in nodemanager.properties
-
DS XI3.2 SP1 - Problem when starting RFC server from management console
Hi,
We're using DataServices XI 3.2 SP1 FP1 on a windows 2008 server 64bits to load SAP BW. We have set up an external system in SAP BW called "DI_SOURCE" and then successfully created a RFC server interface (DI_SOURCE) within the management console.
When we try to start this RFC server from the management console, we immediately get the following error message : "An internal error occurred in: server.start()::rfc_bad_connection".
On the other hand, when we follow the "old method" (pre SP2) and start the RFC server from a command window, it works : we have "CONNECTION DI_SOURCE OK" in SAP BW.
Any ideas how to solve this ?
Thanks,
OlivierHi,
We have tried your suggestions above.
Instead of just crashing we now get an error from designer (before closing down). Seems as if our librfc32.dll has a problem.
We have verified that the librfc32.dll from the Data Services package is the only one on the server.
Problem signature:
Problem Event Name: BEX
Application Name: al_designer.exe
Application Version: 12.2.2.0
Application Timestamp: 4b99c5ef
Fault Module Name: LIBRFC32.DLL
Fault Module Version: 7100.3.144.6097
Fault Module Timestamp: 49bec8be
Exception Offset: 000179a4
Exception Code: c0000409
Exception Data: 00000000
OS Version: 6.1.7600.2.0.0.272.7
Locale ID: 1030
Additional Information 1: 4b85
Additional Information 2: 4b85a4b06dde50b4e092d24f447efca0
Additional Information 3: 45fe
Additional Information 4: 45feda9db76a48384005c14dafbddc29
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt -
Have Weblogic 10.3.5 error when starting weblogic server from CLI
I have installed wls 10.3.5 and ADF 11.1.1.5 runtime on windows machine.when I start the weblogic server from command line using C:\Oracle\Middleware\user_projects\domains\adf_domain\bin\startWebLogic.cmd
My em doesnt start and is in Failed state and when I looked at the log I see errors too.
Here is the stack trace.
<Sep 1, 2011 10:51:13 AM EDT> <Error> <org.apache.beehive.netui.pageflow.internal.AdapterManager> <BEA-000000> <ServletContainerAdapter manager not initializedcorrectly.>
<Sep 1, 2011 10:51:17 AM EDT> <Warning> <HTTP> <BEA-101162> <User defined listener com.sun.faces.config.ConfigureListener failed: java.lang.NoSuchMethodError: org/apache/xerces/impl/xs/models/CMBuilder.<init>()V.java.lang.NoSuchMethodError: org/apache/xerces/impl/xs/models/CMBuilder.<init>()V
at org.apache.xerces.impl.xs.XMLSchemaLoader.<init>(XMLSchemaLoader.java:234)
at org.apache.xerces.impl.xs.XMLSchemaLoader.<init>(XMLSchemaLoader.java:199)
at org.apache.xerces.jaxp.validation.XMLSchemaFactory.<init>(Unknown Source)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
Truncated. see log file for complete stacktrace>
<Sep 1, 2011 10:51:17 AM EDT> <Warning> <HTTP> <BEA-101162> <User defined listener com.sun.faces.config.ConfigureListener failed: java.lang.NullPointerException.java.lang.NullPointerException
at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:241)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run
(EventsManager.java:482)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.EventsManager.notifyContextDestroyedEvent(EventsManager.java:200)
Truncated. see log file for complete stacktrace>
<Sep 1, 2011 10:51:18 AM EDT> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'em'.
weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
Truncated. see log file for complete stacktrace
Caused By: java.lang.NoSuchMethodError: org/apache/xerces/impl/xs/models/CMBuilder.<init>()V
at org.apache.xerces.impl.xs.XMLSchemaLoader.<init>(XMLSchemaLoader.java:234)
at org.apache.xerces.impl.xs.XMLSchemaLoader.<init>(XMLSchemaLoader.java:199)
at org.apache.xerces.jaxp.validation.XMLSchemaFactory.<init>(Unknown Source)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
Truncated. see log file for complete stacktrace
<Sep 1, 2011 10:51:18 AM EDT> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<Sep 1, 2011 10:51:18 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Sep 1, 2011 10:51:18 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<Sep 1, 2011 10:51:18 AM EDT> <Notice> <Server> <BEA-002613> <Channel "Default"is now listening on :7001 for protocols iiop, t3, ldap, snmp, http.>
<Sep 1, 2011 10:51:18 AM EDT> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
<Sep 1, 2011 10:51:18 AM EDT> <Notice> <WebLogicServer> <BEA-000329> <Started WebLogic Admin Server "AdminServer" for domain "adf_domain" running in ProductionMode>
<Sep 1, 2011 10:51:18 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Sep 1, 2011 10:51:18 AM EDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
Can you please help me resolve the issue?
Thanks,
--John.I ran the upgradeADF command command successfully and this is the final errors I have:
####<Sep 7, 2011 1:19:29 PM EDT> <Warning> <HTTP> <GAXGPRS32DV> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <7f351c71d03e540b:-3797f225:13244e58545:-8000-0000000000000003> <1315415969805> <BEA-101162> <User defined listener com.sun.faces.config.ConfigureListener failed: java.lang.RuntimeException: java.lang.NoSuchMethodError: org/apache/xerces/impl/xs/models/CMBuilder.<init>()V.
java.lang.RuntimeException: java.lang.NoSuchMethodError: org/apache/xerces/impl/xs/models/CMBuilder.<init>()V
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:294)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1874)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3154)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:485)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:201)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:249)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:28)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:637)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:52)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:31)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:170)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:124)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: java.lang.NoSuchMethodError: org/apache/xerces/impl/xs/models/CMBuilder.<init>()V
at org.apache.xerces.impl.xs.XMLSchemaLoader.<init>(XMLSchemaLoader.java:234)
at org.apache.xerces.impl.xs.XMLSchemaLoader.<init>(XMLSchemaLoader.java:199)
at org.apache.xerces.jaxp.validation.XMLSchemaFactory.<init>(Unknown Source)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at javax.xml.validation.SchemaFactoryFinder.loadFromService(SchemaFactoryFinder.java:431)
at javax.xml.validation.SchemaFactoryFinder._newFactory(SchemaFactoryFinder.java:246)
at javax.xml.validation.SchemaFactoryFinder.newFactory(SchemaFactoryFinder.java:145)
at javax.xml.validation.SchemaFactory.newInstance(SchemaFactory.java:205)
at com.sun.faces.config.DbfFactory.initStatics(DbfFactory.java:228)
at com.sun.faces.config.DbfFactory.<clinit>(DbfFactory.java:190)
at com.sun.faces.config.ConfigManager$ParseTask.<init>(ConfigManager.java:815)
at com.sun.faces.config.ConfigManager.getConfigDocuments(ConfigManager.java:653)
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:309)
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:226)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1872)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<Sep 7, 2011 1:19:29 PM EDT> <Info> <Deployer> <GAXGPRS32DV> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <7f351c71d03e540b:-3797f225:13244e58545:-8000-0000000000000003> <1315415969852> <BEA-149059> <Module /em of application em is transitioning from STATE_ADMIN to STATE_PREPARED on server AdminServer.>
####<Sep 7, 2011 1:19:30 PM EDT> <Info> <Deployer> <GAXGPRS32DV> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <7f351c71d03e540b:-3797f225:13244e58545:-8000-0000000000000003> <1315415970649> <BEA-149060> <Module /em of application em successfully transitioned from STATE_ADMIN to STATE_PREPARED on server AdminServer.>
####<Sep 7, 2011 1:19:30 PM EDT> <Info> <Deployer> <GAXGPRS32DV> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <7f351c71d03e540b:-3797f225:13244e58545:-8000-0000000000000003> <1315415970649> <BEA-149059> <Module empty.jar of application em is transitioning from STATE_ADMIN to STATE_PREPARED on server AdminServer.>
####<Sep 7, 2011 1:19:30 PM EDT> <Info> <Deployer> <GAXGPRS32DV> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <7f351c71d03e540b:-3797f225:13244e58545:-8000-0000000000000003> <1315415970649> <BEA-149060> <Module empty.jar of application em successfully transitioned from STATE_ADMIN to STATE_PREPARED on server AdminServer.>
####<Sep 7, 2011 1:19:30 PM EDT> <Error> <Deployer> <GAXGPRS32DV> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <7f351c71d03e540b:-3797f225:13244e58545:-8000-0000000000000003> <1315415970649> <BEA-149231> <Unable to set the activation state to true for the application 'em'.
weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:201)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:249)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:28)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:637)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:52)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:31)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:170)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:124)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: java.lang.NoSuchMethodError: org/apache/xerces/impl/xs/models/CMBuilder.<init>()V
at org.apache.xerces.impl.xs.XMLSchemaLoader.<init>(XMLSchemaLoader.java:234)
at org.apache.xerces.impl.xs.XMLSchemaLoader.<init>(XMLSchemaLoader.java:199)
at org.apache.xerces.jaxp.validation.XMLSchemaFactory.<init>(Unknown Source)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at javax.xml.validation.SchemaFactoryFinder.loadFromService(SchemaFactoryFinder.java:431)
at javax.xml.validation.SchemaFactoryFinder._newFactory(SchemaFactoryFinder.java:246)
at javax.xml.validation.SchemaFactoryFinder.newFactory(SchemaFactoryFinder.java:145)
at javax.xml.validation.SchemaFactory.newInstance(SchemaFactory.java:205)
at com.sun.faces.config.DbfFactory.initStatics(DbfFactory.java:228)
at com.sun.faces.config.DbfFactory.<clinit>(DbfFactory.java:190)
at com.sun.faces.config.ConfigManager$ParseTask.<init>(ConfigManager.java:815)
at com.sun.faces.config.ConfigManager.getConfigDocuments(ConfigManager.java:653)
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:309)
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:226)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1872)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Can someone Help?
Thanks,
--John. -
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 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 -
Problems starting managed server from admin console WL70 portal
I get the following exception when I try to start the managed server from admin server console. Both Admin server and managed server are on the same machine.
I get the following exception when I try to start the managed server from admin server console. Both Admin server and managed server are on the same machine.
-
Starting managed server from admin console
Hi Anand Byrappagiri(Bea guy, I saw him on this group but can't remember),
I did the same way as you said here but still getting following error.....Could you
address me where I did a mistake
Starting WebLogic Server ....
Connecting to http://localhost:7001...
<Mar 4, 2002 5:19:17 PM EST> <Notice> <WebLogicServer> <Starting WebLogic Managed
Server "MyServer1" for domain "mydomain">
<Mar 4, 2002 5:19:20 PM EST> <Emergency> <Server> <Unable to initialize the server:
'Fatal initialization exception
Throwable: java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:164)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
***************************************************************************Start
server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:164)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
'>
The WebLogic Server did not start up properly.
Exception raised: weblogic.management.configuration.ConfigurationException: connecting
to http://localhost:7001/wl_management_internal2/Bootstrap - with nested exception:
[java.net.ConnectException: Tried all: '1' addresses, but could not connect over
HTTP to server: 'localhost', port: '7001']
java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP
to server: 'localhost', port: '7001'
at weblogic.net.http.HttpClient.openServer(HttpClient.java:203)
at weblogic.net.http.HttpClient.openServer(HttpClient.java:254)
at weblogic.net.http.HttpClient.<init>(HttpClient.java:117)
at weblogic.net.http.HttpClient.New(HttpClient.java:149)
at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:109)
at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:279)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:230)
at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:990)
at weblogic.management.Admin.initialize(Admin.java:320)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: connecting to http://localhost:7001/wl_management_internal2/Bootstrap
- with nested exception:
[java.net.ConnectException: Tried all: '1' addresses, but could not connect over
HTTP to server: 'localhost', port: '7001']
at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1081)
at weblogic.management.Admin.initialize(Admin.java:320)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
t weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
Reason: Fatal initialization exception
<Mar 4, 2002 5:37:12 PM EST> <Info> <[email protected]:5555> <WindowsProcessControl:
online successfully invoked on server 'MyServer1', pid: 1892>
Change the "Listen Address" attribute of the admin server to be its machine
name or IP address. I think you currently have it set to "localhost".
Hopefully this should fix atleast one of the exceptions below.
-- Anand
"Janavi" <[email protected]> wrote in message
news:[email protected]...
>
> Hi Anand Byrappagiri(Bea guy, I saw him on this group but can't remember),
>
> I did the same way as you said here but still getting following
error.....Could you
> address me where I did a mistake
>
>
> __________________________________________
> Starting WebLogic Server ....
> Connecting to http://localhost:7001...
>
> <Mar 4, 2002 5:19:17 PM EST> <Notice> <WebLogicServer> <Starting WebLogic
Managed
> Server "MyServer1" for domain "mydomain">
> <Mar 4, 2002 5:19:20 PM EST> <Emergency> <Server> <Unable to initialize
the server:
> 'Fatal initialization exception
> Throwable: java.lang.ClassCastException:
weblogic.security.acl.DefaultUserInfoImpl
>
>
> Start server side stack trace:
> java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
> at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
> at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
> at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
> at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
> at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
>
> at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
> at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
> at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
> at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
> End server side stack trace
>
> java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
>
>
***************************************************************************S
tart
> server side stack trace:
> java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
> at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
> at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
> at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
> at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
> at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
>
> at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
> at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
> at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
> at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
> End server side stack trace
>
> <<no stack trace available>>
> '>
>
> The WebLogic Server did not start up properly.
> Exception raised:
weblogic.management.configuration.ConfigurationException: connecting
> to http://localhost:7001/wl_management_internal2/Bootstrap - with nested
exception:
>
> [java.net.ConnectException: Tried all: '1' addresses, but could not
connect over
> HTTP to server: 'localhost', port: '7001']
> java.net.ConnectException: Tried all: '1' addresses, but could not connect
over HTTP
> to server: 'localhost', port: '7001'
> at weblogic.net.http.HttpClient.openServer(HttpClient.java:203)
> at weblogic.net.http.HttpClient.openServer(HttpClient.java:254)
> at weblogic.net.http.HttpClient.<init>(HttpClient.java:117)
> at weblogic.net.http.HttpClient.New(HttpClient.java:149)
> at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:109)
> at
weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:27
9)
>
> at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:230)
> at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:990)
> at weblogic.management.Admin.initialize(Admin.java:320)
> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
> at weblogic.Server.main(Server.java:35)
> --------------- nested within: ------------------
> weblogic.management.configuration.ConfigurationException: connecting to
http://localhost:7001/wl_management_internal2/Bootstrap
> - with nested exception:
> [java.net.ConnectException: Tried all: '1' addresses, but could not
connect over
> HTTP to server: 'localhost', port: '7001']
> at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1081)
> at weblogic.management.Admin.initialize(Admin.java:320)
> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
> at weblogic.Server.main(Server.java:35)
> Reason: Fatal initialization exception
>
> t weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
> End server side stack trace
>
> <<no stack trace available>>
> Reason: Fatal initialization exception
>
> <Mar 4, 2002 5:37:12 PM EST> <Info> <[email protected]:5555>
<WindowsProcessControl:
> online successfully invoked on server 'MyServer1', pid: 1892>
> _______________________________________
>
-
Getting error when starting managed server from administration server
When i start one of my managed server in the cluster i get the following error
The WebLogic Server did not start up properly.
Exception raised: java.lang.ArrayIndexOutOfBoundsException
java.lang.ArrayIndexOutOfBoundsException
at com.bea.utils.misc.ProcessUtil.base64ToBytes(ProcessUtil.java:552)
at com.bea.utils.misc.Process.validate(Process.java:1231)
at com.bea.utils.misc.Process.isValidSignature(Process.java:518)
at com.bea.utils.misc.ProcessManager.memCheck(ProcessManager.java:647)
at weblogic.t3.srvr.T3Srvr.checkAccess(T3Srvr.java:278)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:335)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
Please tell if somebody know it
Do you have any other products from BEA other than WLS?
I can't seem to find the following (com/bea/utils/misc) from WLS source
line ?
Kumar
Ritesh Kapoor wrote:
> When i start one of my managed server in the cluster i get the following error
> The WebLogic Server did not start up properly.
> Exception raised: java.lang.ArrayIndexOutOfBoundsException
> java.lang.ArrayIndexOutOfBoundsException
> at com.bea.utils.misc.ProcessUtil.base64ToBytes(ProcessUtil.java:552)
> at com.bea.utils.misc.Process.validate(Process.java:1231)
> at com.bea.utils.misc.Process.isValidSignature(Process.java:518)
> at com.bea.utils.misc.ProcessManager.memCheck(ProcessManager.java:647)
> at weblogic.t3.srvr.T3Srvr.checkAccess(T3Srvr.java:278)
> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:335)
> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
> at weblogic.Server.main(Server.java:35)
> Reason: Fatal initialization exception
>
> Please tell if somebody know it
>
>
-
Error while connecting to MDM server from Webdynpro
Hi ,
I am trying to connect to MDM server (5.5 SP04 no patches) through a webdynpro application . The following is the piece of code that I am using as a test .
CatalogData CatalogData = new CatalogData();
int resultLogin = 0;
try {
resultLogin = CatalogData.Login("USNOC01AQ05",2005,"Admin","Erico1234","English [US]");
}catch(Exception e){
wdContext.currentContextElement().setValueattr("Not Connected");
//System.out.println("Error while establishing connection");
if (resultLogin != RC.RC_OK){
wdContext.currentContextElement().setValueattr("Not Connected");
//System.out.println("Error logging to the SDM server");
//System.exit(-1);
wdContext.currentContextElement().setValueattr("Connected");
//System.out.println("MDM server connected");
The import statements are as follows
import a2i.common.CatalogData;
import a2i.generated.RC;
I have put the following jar files in the java build path
MDM4J
mdm-admin
mdm-common
mdm-core
mdm-data
mdm-protocol
When I deploy my application I get the following error
java.lang.NoClassDefFoundError: a2i/common/CatalogData
It can't be determined from the exception chain, which class loader failed to load the above class. But at least the class loader of the current application does not contain a resource with name 'a2i/common/CatalogData'.
What do you guys think is the problem ?
Regards
DeepaK SinghHi ,
I found a document which says that MDM4J is the legacy API and is considered deprecated .The MDM Java API is the new one .I have both of them in the java build path . I am not sure if this is that cause of the problem .
Now I had a look at the javadoc for the new API but I am not able to locate the class to obtain a connection to the MDM server from a custom application being built in Netweaver Developer Studio . Can someone help me out with the same ?What would be the code to obtain the connection to the MDM server with the new JAVA API ?
Regards
DeepaK Singh -
Error while retrieving bulk data from mdm in staging server
I am getting an error while retrieving bulk data from MDM. The error goes like this "NiRawReadError: An error occured when reading data from socket.".
Could anyone please suggest me about the possible cause of this error. Please reply soon.
Moderator message: network error, relation to ABAP development unclear, please search for available answers, check with system administrators, consult SAP service marketplace.
Edited by: Thomas Zloch on Nov 22, 2010 5:16 PMCan you elaborate the thing... I don't think /*+ APPEND */ this is working for me ,still I am getting same error.
If you have any other suggestion,I would like to hear.
Should i not put commit after some 500 records inserted ? As i am putting commit once after whole data gets inserted. -
RPD file upgrade from 10g to 11g error: Error in starting opmn server
Dear All,
We have to upgrade an RPD repository file and the catalog from 10 g to 11 g. We use the Oracle Fussion Middleware Upgrade Assistant tool.
BI Service (BI server version: 11.1.1.6).
The operation failed, and we got the following error message:
[2013-09-06T12:03:51.117+02:00] [BIEE] [ERROR] [upgrade.BIEE] oracle.as.management.opmn.optic.OpticException: Error in starting opmn server[[ Operation aborted because of a system call failure or internal error at oracle.as.management.opmn.optic.OpmnAdmin.executeCommand(OpmnAdmin.java:310) at oracle.as.management.opmn.optic.OpmnAdmin.startOpmnServer(OpmnAdmin.java:87) at oracle.ias.upgrade.config.oraclebi.OPMNUtil.startOpmn(OPMNUtil.java:46) at oracle.ias.upgrade.config.oraclebi.OracleBIConfigUpgrade.doUpgrade(OracleBIConfigUpgrade.java:118) at oracle.ias.upgrade.UpgradeSupport.doUpgrade(UpgradeSupport.java:1823) at oracle.ias.upgrade.gui.UAUpgradeThread.run(UAUpgradeThread.java:503)It is curious because the core applications are running (I performed the command "./opmnctl start" successfully) and I can open and use the services like WebLogic Administration Consol, Enterprise Manager, BI Enterprise Edition (Analytics) , BI Publisher etc.
But if I open the enterprise manager the core applications under the tab Fusion Middleware are marked with red (not running)
See screen shot regarding the overview:
http://s24.postimg.org/vdg0o83fp/enterprise_manager.png
If I click on the Core application link the core appilcations are marked with green (they are running).
See screen shot regarding the Core Applications:
http://s10.postimg.org/ogba45ke1/core_app.png
Problem:
the core applications are displayed as down in Enterprise Manager.
I restarted the core applications in the Enterprise Manager successfully but under the tab Fussion Middleware they are still displayed as not running.
Does anybody ever had a problem like this. Thank you!
Regards, Robertok, since installing multiple versions of oracle is a common practice, I will do both on same machine and try them out.
solaris@solaris:~$ cat /etc/release
Oracle Solaris 11 11/11 X86
Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved.
Assembled 18 October 2011
solaris@solaris:~$ uname -a
SunOS solaris 5.11 11.0 i86pc i386 i86pc
solaris@solaris:~$ df -k
Filesystem 1024-blocks Used Available Capacity Mounted on
rpool/ROOT/solaris 718405632 1620554 713290953 1% /
/devices 0 0 0 0% /devices -
Start managed server from console?
If I try to start a new weblogic 10.3 managed server from the console then i get this error:
"The server myserver does not have a machine associated with it.
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."
Starting the same managed server from the dos prompt "bin/startManagedServer.bat myserver" works, so why is the weblogic console not working?Hi,
To start any managed servers from Admin Console you need to have a Machine associated with that Managed server and have to start nodemanager, then only you can start a managed server from console.
Following are the steps:
1) Create a Managed Server (MS-1)
2) Create a Machines (MachineA)
3) In the above created MachineA add the MS-1 which can be done from the below console path
Console Path:
Machines --> MachineA --> Configuration [Tab] --> Servers [Sub-Tab]
4) Now start nodemanager using the startNodeManager.sh script which can be found in the below path
Path:
wlserver_10.3/server/bin/
5) Now you can try to start your MS-1 using the Admin Console.
Note: If you still cannot start the your managed servers then would suggest you to have a look at the below post
Topic: NodeManager is not reachable
http://middlewaremagic.com/weblogic/?p=5205
Topic: Common NodeManager Issues in WebLogic
http://middlewaremagic.com/weblogic/?p=2887
Regards,
Ravish Mody -
Error while shutting down 'Admin Server' from administration console
hi,
When I try to shutdown admin server from administration console(Weblogic server>Control>Shut Down...) I get this error:
No Machine associated with server AdminServer. Please associate a machine to this weblogic server using weblogic console first.
Not able to understand what this means....
thanksRead up on Node Manager - a outside-of-WLS-process that can start/stop WebLogic on your OS instance. Node Manager uses the "machine" concept.
http://download.oracle.com/docs/cd/E12839_01/web.1111/e13740/overview.htm
http://blogs.oracle.com/jamesbayer/2010/01/weblogic_nodemanager_quick_sta.html
Maybe you are looking for
-
[Solved] Greek accented characters and Qt Applications
Hello. This is my first day with Arch linux. My problem has to do with greek accented characters like ά, ή, ό etc. I can type these characters on my browsers, rox file manager and other applications but not on Qt based applications like Skype and TeX
-
I am going nuts with this damn conduit malware. I have tried everything. This morning when I got up it seemed as though my whole computer crashed. It wouldn't even go on. I unplugged a couple of plugs for a while, and lo and behold it came on. Whew!!
-
Simple use of variables in query
Hi, i've just started using PL/SQL and as a long time user of TSQL the syntax is a bit confusing for me. I'm trying to test a simple query - using a variable to select some rows from a table. Lest assume that we have a table with data from different
-
Machine Description - Windows 8.1 x64 (Keypoard, touchpad only no touchscreen !) 8Gb Ram, i7 Processor, Nvidia 630M 2GB Adobe reader installed on my 128Gb SSD. Problem is same whether small/large file is opened from SSD or my another HDD. Disabled al
-
Hi All, could u help on , How to give the list of possible entries for the field in the selection screen.( not a F4 help) customizing entries. Thanks, kumar