Error while starting Managedserver for 2nd server in cluster

Hi
we have 2 Unix servers of which one has Admin and managed server and second has only managed server.
while starting managed server for 2nd unix server we are getting below error though it is in running state: KINDLY HELP!!
changed Location=site:XXX.XXXX.com,machine:<HOSTNAME -SERVER1>, - parameters as are client specific.
>
<Apr 7, 2013 8:49:20 AM PDT> <Error> <Coherence> <BEA-000000> <2013-04-07 08:49:20.986/48.542 Oracle Coherence GE 3.5.3/465p2 <Error> (thread=Cluster, member=n/a): This member is not authorized to join the cluster. Rejected by Member(Id=1, Timestamp=2013-04-07 06:54:45.083, Address=10.93.38.113:9095, MachineId=29041, Location=site:XXX.XXXX.com,machine:<HOSTNAME -SERVER1>,process:10264, Role=WeblogicServer).>
<Apr 7, 2013 8:49:20 AM PDT> <Error> <Coherence> <BEA-000000> <2013-04-07 08:49:20.992/48.548 Oracle Coherence GE 3.5.3/465p2 <Error> (thread=[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)', member=n/a): Error while starting cluster: java.lang.RuntimeException: Failed to start Service "Cluster" (ServiceState=SERVICE_STOPPED, STATE_JOINING)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Service.CDB:38)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:38)
at com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:366)
at com.tangosol.coherence.component.net.Cluster.start(Cluster.CDB:11)
at com.tangosol.coherence.component.util.SafeCluster.startCluster(SafeCluster.CDB:3)
at com.tangosol.coherence.component.util.SafeCluster.restartCluster(SafeCluster.CDB:7)
at com.tangosol.coherence.component.util.SafeCluster.ensureRunningCluster(SafeCluster.CDB:27)
at com.tangosol.coherence.component.util.SafeCluster.start(SafeCluster.CDB:2)
at com.tangosol.net.CacheFactory.ensureCluster(CacheFactory.java:998)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureService(DefaultConfigurableCacheFactory.java:915)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:877)
at com.tangosol.net.DefaultConfigurableCacheFactory.configureCache(DefaultConfigurableCacheFactory.java:1088)
at com.tangosol.net.DefaultConfigurableCacheFactory.configureCache(DefaultConfigurableCacheFactory.java:1104)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:304)
at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:735)
at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:712)
at oracle.security.am.foundation.mapimpl.coherence.CoherenceMapImpl.init(CoherenceMapImpl.java:170)
at oracle.security.am.foundation.mapimpl.coherence.FastAccessMapImpl.init(FastAccessMapImpl.java:62)
at oracle.security.am.foundation.mapimpl.coherence.CoherenceMapImpl.<init>(CoherenceMapImpl.java:159)
at oracle.security.am.foundation.mapimpl.coherence.FastAccessMapImpl.<init>(FastAccessMapImpl.java:58)
at oracle.security.am.engines.sme.mapimpl.SessionStoreImpl.<init>(SessionStoreImpl.java:97)
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 oracle.security.am.admin.config.util.GenericFactory.getManager(GenericFactory.java:317)
at oracle.security.am.admin.config.util.GenericFactory.getManager(GenericFactory.java:305)
at oracle.security.am.admin.config.util.GenericFactory.readObject(GenericFactory.java:220)
at oracle.security.am.admin.config.util.GenericFactory.validateAndGetObjectForMap(GenericFactory.java:115)
at oracle.security.am.admin.config.util.GenericFactory.getInstance(GenericFactory.java:103)
at oracle.security.am.admin.config.util.GenericFactory.getInstance(GenericFactory.java:178)
at oracle.security.am.engines.sme.mgr.AbstractSessionManager.<init>(AbstractSessionManager.java:214)
at oracle.security.am.engines.sme.mgr.SessionManagerImpl.<init>(SessionManagerImpl.java:51)
at oracle.security.am.engines.sme.mgr.SessionManagerImpl.getInstance(SessionManagerImpl.java:66)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.security.am.engines.sme.SessionManagerFactory.getManager(SessionManagerFactory.java:281)
at oracle.security.am.engines.sme.SessionManagerFactory.readObject(SessionManagerFactory.java:207)
at oracle.security.am.engines.sme.SessionManagerFactory.getSessionManager(SessionManagerFactory.java:95)
at oracle.security.am.engines.sso.adapter.AbstractSessionAdapterImpl.checkAndInit(AbstractSessionAdapterImpl.java:101)
at oracle.security.am.engines.sso.adapter.AbstractSessionAdapterImpl.<init>(AbstractSessionAdapterImpl.java:73)
at oracle.security.am.engines.sso.adapter.MultipleUserSessionAdapterImpl.<init>(MultipleUserSessionAdapterImpl.java:56)
at oracle.security.am.engines.sso.adapter.MultipleUserSessionAdapterImpl.<clinit>(MultipleUserSessionAdapterImpl.java:45)
at oracle.security.am.engines.sso.adapter.SessionManagementAdapterFactory.getAdapter(SessionManagementAdapterFactory.java:46)
at oracle.security.am.engines.enginecontroller.SSOEngineController.processEvent(SSOEngineController.java:488)
at oracle.security.am.controller.MasterController.processEvent(MasterController.java:418)
at oracle.security.am.controller.MasterController.processRequest(MasterController.java:586)
at oracle.security.am.controller.MasterController.process(MasterController.java:523)
at oracle.security.am.pbl.transport.http.AMInitServlet.initializeAmServer(AMInitServlet.java:137)
at oracle.security.am.pbl.transport.http.AMInitServlet.init(AMInitServlet.java:79)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.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)

Does server hosting your second managed server has multiple IP addresses?
Also, check if below configuration is set or not in your server config xml file:
<Setting Name="SetWellKnownAddress" Type="xsd:boolean">false</Setting>
Regards,
Sunny
Edited by: delhi on Apr 7, 2013 1:22 PM

Similar Messages

Error while starting the shared service server

Hi john,
I am getting the following error while starting the shared service server.
*25 Jul 2009 10:26:39 - org.apache.slide.common.Domain - ERROR - Unable to migrate hub groups to css*
So shared service console is not starting.
Please tell me the solution for it.
Thanks
Edited by: user11358816 on Jul 24, 2009 10:06 PM
Edited by: user11358816 on Jul 24, 2009 10:09 PM

Hi John,
Yes,It was working earlier.
When I have added NTLM authentication for FDM I am getting that error,but instead of that if
I am adding the authentication provider as LDAP(CSS) I am not getting that error.
So finally i have added only one authentication provider and that is LDAP(CSS).
I fallowed ur document for integrating the FDM application with planning application.(http://john-goodwin.blogspot.com/2008/07/planning-v11-drill-back.html )
For the global logon information I have given admin and password , which I have given while adding the LDAP authentication (CSS).
I am getting machine profile missing error when i clicked on the dimension and the target dimension test box contain connection failed.
Can u suggest me where am I wrong?
Thanks
Edited by: user11358816 on Jul 26, 2009 9:42 PM

Error While Startting the Web Logic Server

Hello All,
I am getting below error while start up the weblogic server.
Can you help me to resolve this error.
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory$1.run(AbstractAutowireCapableBeanFactory.java:409)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.createBean(AbstractAutowireCapableBeanFactory.java:380)
Truncated. see log file for complete stacktrace
Caused By: java.lang.RuntimeException:
ORABPEL START-UP ERROR!!!!!!!!
OraBPEL run-time system failed to start due to exception:
Cannot look up jdbc data source.
The process domain is unable to look up the TX data source "jdbc/SOALocalTxDataS
ource".
The J2EE container was not configured properly; a data source with the expected
name has not been created or has been removed.
Verify that the machine hosting the data source is physically connected to the n
etwork. In addition, verify that the connection pool properties, as defined in t
he application server startup properties, are valid.
Thanks in Advance !
Regards,
Niranjan.

for instance, go to your domain home, cd config/jdbc , and grep for "jdbc/SOALocalTxDataSource" in the existing xml files
maybe for some reasons this DataSource was not created, or is not targeted/deployed, or the corresponding DB is not up and running, or there is some connectivity problem.... grep your log file for SOALocalTxDataSource, probably there is some error reporting that this DataSource could not be created because the DB is down....
http://docs.oracle.com/cd/E14571_01/integration.1111/e10226/soainfra_config.htm

Error while starting the Oracle BI Server

Hi ,
I am getting the services.msc error while starting the Oracle BI Server as -
Error handling the control request.
Please help me out ..
Thanks and Regards ,

It is actually Windows services error that I am facing ....
while starting the BI server after making any changes to NQS config file ..
Could not start the Oracle BI Server service on Local Computer
Error 1064: An exception occured in the service when handling the control request
Message was edited by:
user460211
Message was edited by:
user460211

Error while starting the OIM managed server in oracle VM

Hi ,
I am getting the following error , while starting the OIM managed server in Oracle VM.
<Jun 14, 2012 4:45:38 AM EDT> <Error> <org.quartz.impl.jdbcjobstore.JobStoreCMT> <BEA-000000> <MisfireHandler: Error handling misfires: Unexpected runtime exception: null
org.quartz.JobPersistenceException: Unexpected runtime exception: null [See nested exception: java.lang.NullPointerException]
at org.quartz.impl.jdbcjobstore.JobStoreSupport.doRecoverMisfires(JobStoreSupport.java:3042)
at org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.manage(JobStoreSupport.java:3789)
at org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.run(JobStoreSupport.java:3809)
Caused By: java.lang.NullPointerException
at org.quartz.SimpleTrigger.computeNumTimesFiredBetween(SimpleTrigger.java:800)
at org.quartz.SimpleTrigger.updateAfterMisfire(SimpleTrigger.java:514)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.doUpdateOfMisfiredTrigger(JobStoreSupport.java:944)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.recoverMisfiredJobs(JobStoreSupport.java:898)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.doRecoverMisfires(JobStoreSupport.java:3029)
at org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.manage(JobStoreSupport.java:3789)
at org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.run(JobStoreSupport.java:3809)
>
How to resolve this issue.Any one please suggest me , i am in a big trouble ...
Thanks in advance ..
-Deena.

Hi P.k,
The table QRTZ92_TRIGGERS is there in the database.But while trying to run this command (UPDATE QRTZ92_TRIGGERS set NEXT_FIRE_TIME=1 where NEXT_FIRE_TIME < 0)in database i am getting the table or view does not exist.
What is GTC resource?
OIM version - 11.1.1.5.0.
-Deena.

OIM 11gR2: Error while starting SOA and OIM Server

I have configured 2 OIM Applications hosted on 2 different linux hosts but connecting to one Oracle DB.
Done OIM installation and configuration on HOST1 and it is successful.
now while performing on HOST2,all similar steps have been followed as same on HOST1 except the Database keystore step (copied files while configuring OIM), I am encountering an error while starting SOA server and OIM server.
Error :
2012-10-19T11:49:07.172-07:00] [soa_server2] [NOTIFICATION] [JPS-04093] [oracle.jps.deployment] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 1350dfc6c17c1b80:336be4f6:13a7a59774c:-8000-0000000000000004,0] [APP: soa-infra] Application policy migration for application soa-infra is completed successfully.
[2012-10-19T11:49:16.901-07:00] [soa_server2] [ERROR] [] [oracle.mds] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 1350dfc6c17c1b80:336be4f6:13a7a59774c:-8000-0000000000000004,0] [APP: soa-infra] [[
oracle.mds.lcm.exception.MDSLCMException: MDS-01330: unable to load MDS configuration document
MDS-01329: unable to load element "persistence-config"
MDS-01370: MetadataStore configuration for metadata-store-usage "soa-infra-store" is invalid.
MDS-00929: unable to look up name "jdbc/mds/MDS_LocalTxDataSource" in JNDI context
Unable to resolve 'jdbc.mds.MDS_LocalTxDataSource'. Resolved 'jdbc.mds'
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: oracle.mds.config.MDSConfigurationException: MDS-01330: unable to load MDS configuration document
MDS-01329: unable to load element "persistence-config"
MDS-01370: MetadataStore configuration for metadata-store-usage "soa-infra-store" is invalid.
MDS-00929: unable to look up name "jdbc/mds/MDS_LocalTxDataSource" in JNDI context
Unable to resolve 'jdbc.mds.MDS_LocalTxDataSource'. Resolved 'jdbc.mds'
Please help, thanks

Hi
Did you use pack and unpack command for configuration?
Creating and Starting a Managed Server on a Remote Machine - 11g Release 1 (10.3.6)
Regards
Shashank k

Error while starting ManagedServer

Hi all,
I am getting following error while starting managed server
<Jan 27, 2009 12:30:35 PM PKT> <Error> <HTTP> <BEA-101216> <Servlet: "PubSubServlet" failed to preload on startup in Web applica
tion: "rest/sms".
javax.servlet.ServletException: [HTTP Pubsub Server:2150029]ControllerServlet initialization failed: Cannot create JMS ChannelMa
nager [com.bea.httppubsub.jms.internal.JmsChannelManagerImpl].
java.lang.RuntimeException: Cannot create JMS ChannelManager [com.bea.httppubsub.jms.internal.JmsChannelManagerImpl].
at com.bea.httppubsub.internal.ChannelManagerFactoryImpl.createJmsChannelManager(ChannelManagerFactoryImpl.java:54)
at com.bea.httppubsub.internal.ChannelManagerFactoryImpl.<init>(ChannelManagerFactoryImpl.java:27)
at com.bea.httppubsub.internal.PubSubServerFactoryImpl.createPubSubServer(PubSubServerFactoryImpl.java:116)
at com.bea.httppubsub.internal.PubSubServerFactoryImpl.createPubSubServer(PubSubServerFactoryImpl.java:60)
at com.bea.wlcp.wlng.rest.pubsub.PubSubServerFactoryImpl.createPubSubServer(PubSubServerFactoryImpl.java:17)
at com.bea.httppubsub.servlet.ControllerServlet.init(ControllerServlet.java:171)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:521)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1896)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1873)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1793)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3002)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1375)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:470)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
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:196)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
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:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.reflect.InvocationTargetException
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 com.bea.httppubsub.internal.ChannelManagerFactoryImpl.createJmsChannelManager(ChannelManagerFactoryImpl.java:51)
... 47 more
Caused by: java.lang.RuntimeException: [HTTP Pubsub Server JMS support:2152022]Cannot retrieve ConnectionFactory nor Topic.
javax.naming.NameNotFoundException: Unable to resolve 'com.bea.wlcp.wlng.rest.NotificationTopic'. Resolved 'com.bea.wlcp.wlng.re
st'; remaining name 'NotificationTopic'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:380)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at com.bea.wlcp.wlng.rest.pubsub.JmsProviderImpl.initialize(JmsProviderImpl.java:61)
at com.bea.wlcp.wlng.rest.pubsub.JmsProviderImpl.<init>(JmsProviderImpl.java:34)
at com.bea.wlcp.wlng.rest.pubsub.JmsProviderFactoryImpl.createJmsProvider(JmsProviderFactoryImpl.java:45)
at com.bea.httppubsub.jms.internal.JmsChannelManagerImpl.initJmsTopicListeners(JmsChannelManagerImpl.java:65)
at com.bea.httppubsub.jms.internal.JmsChannelManagerImpl.<init>(JmsChannelManagerImpl.java:37)
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 com.bea.httppubsub.internal.ChannelManagerFactoryImpl.createJmsChannelManager(ChannelManagerFactoryImpl.java:51)
at com.bea.httppubsub.internal.ChannelManagerFactoryImpl.<init>(ChannelManagerFactoryImpl.java:27)
at com.bea.httppubsub.internal.PubSubServerFactoryImpl.createPubSubServer(PubSubServerFactoryImpl.java:116)
at com.bea.httppubsub.internal.PubSubServerFactoryImpl.createPubSubServer(PubSubServerFactoryImpl.java:60)
at com.bea.wlcp.wlng.rest.pubsub.PubSubServerFactoryImpl.createPubSubServer(PubSubServerFactoryImpl.java:17)
at com.bea.httppubsub.servlet.ControllerServlet.init(ControllerServlet.java:171)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:521)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1896)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1873)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1793)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3002)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1375)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:470)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
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:196)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
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:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
at com.bea.wlcp.wlng.rest.pubsub.JmsProviderImpl.initialize(JmsProviderImpl.java:63)
at com.bea.wlcp.wlng.rest.pubsub.JmsProviderImpl.<init>(JmsProviderImpl.java:34)
at com.bea.wlcp.wlng.rest.pubsub.JmsProviderFactoryImpl.createJmsProvider(JmsProviderFactoryImpl.java:45)
at com.bea.httppubsub.jms.internal.JmsChannelManagerImpl.initJmsTopicListeners(JmsChannelManagerImpl.java:65)
at com.bea.httppubsub.jms.internal.JmsChannelManagerImpl.<init>(JmsChannelManagerImpl.java:37)
... 52 more
at com.bea.httppubsub.servlet.ControllerServlet.init(ControllerServlet.java:178)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
Truncated. see log file for complete stacktrace
>
<Jan 27, 2009 12:30:36 PM PKT> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application '
wlng_at_sms_px21 [Version=4.1]'.
weblogic.application.ModuleException: [HTTP:101216]Servlet: "PubSubServlet" failed to preload on startup in Web application: "re
st/sms".
javax.servlet.ServletException: [HTTP Pubsub Server:2150029]ControllerServlet initialization failed: Cannot create JMS ChannelMa
nager [com.bea.httppubsub.jms.internal.JmsChannelManagerImpl].
java.lang.RuntimeException: Cannot create JMS ChannelManager [com.bea.httppubsub.jms.internal.JmsChannelManagerImpl].
at com.bea.httppubsub.internal.ChannelManagerFactoryImpl.createJmsChannelManager(ChannelManagerFactoryImpl.java:54)
at com.bea.httppubsub.internal.ChannelManagerFactoryImpl.<init>(ChannelManagerFactoryImpl.java:27)
at com.bea.httppubsub.internal.PubSubServerFactoryImpl.createPubSubServer(PubSubServerFactoryImpl.java:116)
at com.bea.httppubsub.internal.PubSubServerFactoryImpl.createPubSubServer(PubSubServerFactoryImpl.java:60)
at com.bea.wlcp.wlng.rest.pubsub.PubSubServerFactoryImpl.createPubSubServer(PubSubServerFactoryImpl.java:17)
at com.bea.httppubsub.servlet.ControllerServlet.init(ControllerServlet.java:171)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:521)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1896)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1873)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1793)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3002)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1375)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:470)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
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:196)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
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:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.reflect.InvocationTargetException
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 com.bea.httppubsub.internal.ChannelManagerFactoryImpl.createJmsChannelManager(ChannelManagerFactoryImpl.java:51)
... 47 more
Caused by: java.lang.RuntimeException: [HTTP Pubsub Server JMS support:2152022]Cannot retrieve ConnectionFactory nor Topic.
javax.naming.NameNotFoundException: Unable to resolve 'com.bea.wlcp.wlng.rest.NotificationTopic'. Resolved 'com.bea.wlcp.wlng.re
st'; remaining name 'NotificationTopic'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
Regards,
imran

This is the core of what your issue is:
Caused by: java.lang.RuntimeException: HTTP Pubsub Server JMS support:2152022*Cannot retrieve ConnectionFactory nor Topic.*
javax.naming.NameNotFoundException: Unable to resolve 'com.bea.wlcp.wlng.rest.NotificationTopic'. Resolved 'com.bea.wlcp.wlng.re
st'; remaining name 'NotificationTopic'
Check the server's JNDI tree to make sure it can resolve properly.
There is a sample that ships with the product that has a working JMS example if you need a reference for how to do it correctly:
<INSTALL_DIR>\wlserver_10.3\samples\server\examples\src\examples\webapp\pubsub\stock

Error while starting weblogic 9.0 server .

Hi ,
When I start weblogic 9.0 server , I'm getting the following error and the server gets disconnected .
JRockit dump produced after 0 days, 00:00:45 on Wed Jul 25 11:19:01 2007
Additional information is available in:
C:\bea92\user_projects\domains\dbAdapter\jrockit.1344.dump
C:\bea92\user_projects\domains\dbAdapter\jrockit.1344.mdmp
If you see this dump, please open a support case with BEA and
supply as much information as you can on your system setup and
the program you were running. You can also search for solutions
to your problem at http://forums.bea.com in
the forum jrockit.developer.interest.general.
Error Message: Illegal memory access. [54]
Exception Rec: EXCEPTION_ACCESS_VIOLATION (0xc0000005) at 0x0044CE73 - memory at 0x00000034 could not be read.
Minidump : Wrote mdmp. Size is 173MB
Version : BEA JRockit(R) R25.2.0-28 dra-45238-20050523-2021-win-ia32
GC : System optimized over throughput (initial strategy singleparpar)
: GC strategy for GC 0 was singleparpar
: GC strategy for GC 1 was genparpar
: mmHeap->data = 0x00620000, mmHeap->top = 0x10620000
: mmStartCompaction = 0x0E622030, mmEndCompaction = 0x0F620000
: Heap is not included in dumps.
CPU : Intel Pentium 4 SSE SSE2 NetBurst
Number CPUs : 1
Tot Phys Mem : 1071628288
OS version : Microsoft Windows XP Service Pack 2 (Build 2600)
State : JVM is running
I need to run embedded adapter using weblogic 9.0 .
JRockit used is jrockit90_150_03.
Please help me urgently.

I have downloaded developer license ,but it's still throwing the error .
To start WebLogic Server, use a username and *
password assigned to an admin-level user. For *
server administration, use the WebLogic Server *
console at http:\\hostname:port\console *
tarting weblogic with Java version:
ava version "1.5.0_03"
ava(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_03-b07)
EA JRockit(R) (build dra-45238-20050523-2021-win-ia32, R25.2.0-28)
tarting WLS with line:
:\bea92\JROCKI~1\bin\java -jrockit -Xms256m -Xmx512m -Djrockit.codegen.optpriority=1 -Xverify:none -da -Dplatform.home
\bea92\WEBLOG~1 -Dwls.home=C:\bea92\WEBLOG~1\server -Dwli.home=C:\bea92\WEBLOG~1\integration -Dweblogic.management.discov
true -Dweblogic.ProductionModeEnabled= -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.di
C:\bea92\patch_weblogic901\profiles\default\sysext_manifest_classpath -Dweblogic.Name=AdminServer -Djava.security.policy=C
ea92\WEBLOG~1\server\lib\weblogic.policy weblogic.Server
Jul 25, 2007 2:52:35 PM GMT+05:30> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Vers
dra-45238-20050523-2021-win-ia32 from BEA Systems, Inc.>
Jul 25, 2007 2:52:37 PM GMT+05:30> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.0 Sun Jul 3 21:15:00 PDT
5 598247 >
Jul 25, 2007 2:52:40 PM GMT+05:30> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
nable to start WebLogic Server!
xception occurred while reading the license file.
lease make sure you have a valid license.bea
ile in the BEA home directory associated with this
nstallation. For more information about the license.bea
ile, see the installation guide for the version of the
oftware you are using at http://e-docs.bea.com.
Jul 25, 2007 2:52:40 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
Jul 25, 2007 2:52:40 PM GMT+05:30> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut
elf down>
Jul 25, 2007 2:52:40 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Could you please advise me as to what all I should inclde in the classpath to start weblogic 9.0 server.

Error While Starting the Weblogic Managed server- BEA-160001

Hi,
While starting the managed server (10.3.4) below exception occurs. Help me on why the error occurs.
<Error> <J2EE> <BEA-160001> <Error deploying Internal Application: weblogic.application.ModuleException: [HTTP:101216]Servlet: "CoordinatorPortTypeServlethttp" failed to preload on startup in Web application: "wls-wsat.war".
java.lang.ExceptionInInitializerError
     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)
Caused by: java.lang.IllegalArgumentException: com.sun.xml.messaging.saaj.soap.LocalStrings != com.sun.xml.internal.messaging.saaj.soap.LocalStrings
     at java.util.logging.Logger.getLogger(Logger.java:314)
     at com.sun.xml.internal.messaging.saaj.soap.SAAJMetaFactoryImpl.<clinit>(SAAJMetaFactoryImpl.java:41)
.

Hi,
There are two workaround for this issue.
1) Without disabling wls-wsat application:
Here are the steps:
Add jar saaj-impl-1.3.jar to weblogic classpath
Start weblogic using java options:
-Djavax.xml.soap.MessageFactory=com.sun.xml.messaging.saaj.soap.MessageFactoryImpl
-Djavax.xml.soap.SOAPFactory=com.sun.xml.messaging.saaj.soap.SOAPFactoryImpl
-Djavax.xml.soap.MetaFactory=com.sun.xml.messaging.saaj.soap.SAAJMetaFactoryImpl
2) If wls-wsat is not required:
This is the setting to disable wls-wsat:
-Dweblogic.wsee.wstx.wsat.deployed=false
It is mentioned here in the doc
http://docs.oracle.com/cd/E21764_01/web.1111/e13734/cluster.htm
Regards,
Kal

Error while starting up WLS_Spaces managed server.

Hi,
When i start WLS_Spaces , before i can see the server in runnig mode, i am getting the following errors.
<Error> <Deployer> <BEA-149205> <Failed to initial
ize the application 'wsm-pm' due to error weblogic.management.DeploymentException
<Error> <Deployer> <BEA-149205> <Failed to initial
ize the application 'webcenter' due to error weblogic.management.DeploymentExcep
tion: [J2EE:160149]Error while processing library references. Unresolved applica
tion library references, defined in weblogic-application.xml: [Extension-Name: v
cr-app-lib, exact-match: false]..
Could any one provide some inputs on why these errors are coming up...

Hi George,
THe problem is with the DB im using..I have upgraded the DB to latest version using the patches available for windows.
Now its working fine.
Thanks for your reply..

Error while Starting Sun One Portal Server 6.0

Hi Everyone,
I am trying to install Sun One Portal Server 6.0 Installation. When I start the server (./amserver startall) , I am getting the following in the console
=========================
starting auth helpers ...
done.
checking for directory server ... directory server already running
done
starting web server ... iPlanet-WebServer-Enterprise/6.0SP10 B10/12/2005 00:16
warning: daemon is running as super-user
[LS ls1] http://test.myserver.com, port 80 ready to accept requests
java.lang.NoSuchMethodError: Service
unable to start
iPlanet-WebServer-Enterprise/6.0SP10 B10/12/2005 00:16
warning: daemon is running as super-user
[LS ls1] http://test.myserver.com, port 8089 ready to accept requests
java.lang.NoSuchMethodError: Service
unable to start
done.
=========================================================
When I check in the error log, I am getting the following error message
========================================================
[18/Jul/2008:13:14:42] info (11354): successful server startup
[18/Jul/2008:13:14:42] info (11354): iPlanet-WebServer-Enterprise/6.0SP10 B10/12/2005 00:16
[18/Jul/2008:13:14:42] info (11355): Installing a new configuration
[18/Jul/2008:13:14:42] info (11355): [LS ls1] http://test.myserver.com, port 80 ready to accept requests
[18/Jul/2008:13:14:42] info (11355): A new configuration was successfully installed
[18/Jul/2008:13:14:43] failure (11355): Internal error: Unable to find required methods in Java classes
[18/Jul/2008:13:14:43] failure (11355): Late initialization failed: Error running init function(late) NSServletLateInit: unknown error
=========================================================================
Can anybody tell me what could be issue?
Thanks in Advance.......

This error is solved.However I don't know about the root cause. We tried using some LDAP server. Then this error get resolved.
Edited by: Jeya_14 on 31 Jul, 2008 9:09 AM

Error while starting ManagedServer from admin console.

HI,
can any one please help me on the below error.
i got the below error when i tried to start managedserver from admin console. and below are the steps i have done before start the manages server.
1. started admin server.
2. started nodemanager from C:\bea\wlng400\server\bin\startNodeManager.cmd
3. started managed server from the admin console.
managed server name is "QualcommServer"
Error from QualcommServer.out file is :
<Apr 27, 2009 4:46:37 PM IST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: [Management:141266]Parsing Failure in config.xml: java.lang.AssertionError: java.lang.ClassNotFoundException: com.bea.wlcp.wlng.management.descriptor.bean.WlngTierBean>
Below is config.xml file which i am using:
<jms-server>
<name>JMSServer-AdminServer</name>
<target>AdminServer</target>
</jms-server>
<jms-system-resource>
<name>WLNGJMSResource</name>
<target>AdminServer</target>
<descriptor-file-name>jms/wlng-jms.xml</descriptor-file-name>
</jms-system-resource>
<custom-resource>
<name>networktier</name>
<target>QualcommServer</target>
<descriptor-file-name>custom/nt.xml</descriptor-file-name>
<resource-class>com.bea.wlcp.wlng.management.descriptor.resource.WlngTierResource</resource-class>
<descriptor-bean-class>com.bea.wlcp.wlng.management.descriptor.bean.WlngTierBean</descriptor-bean-class>
</custom-resource>
<custom-resource>
<name>wlng-edr</name>
<target>QualcommServer</target>
<descriptor-file-name>custom/wlng-edr.xml</descriptor-file-name>
<resource-class>com.bea.wlcp.wlng.management.descriptor.resource.WlngEdrResource</resource-class>
<descriptor-bean-class>com.bea.wlcp.wlng.management.descriptor.bean.WlngEdrBean</descriptor-bean-class>
</custom-resource>
<admin-server-name>AdminServer</admin-server-name>
<jdbc-system-resource>
<name>wlng.datasource</name>
<target>QualcommServer</target>
<descriptor-file-name>jdbc/wlng-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<jdbc-system-resource>
<name>wlng.localTX.datasource</name>
<target>QualcommServer</target>
<descriptor-file-name>jdbc/wlng-localTX-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
Thanks,
Srinu Babu P

This classs is usually found in server\lib\wlng\wlng-management.jar, make sure it has that class and that jar is getting loaded by the server.

Error while starting the weblogic admin server for OSB

Hi all,
Please help.
My admin server startup is breaking for weblogic 11g for the following cause :
Caused By: oracle.mds.exception.MDSExceptionList: MDS-01329: unable to load elem
ent "persistence-config"
MDS-01370: MetadataStore configuration for metadata-store-usage "OWSM_TargetRepo
s" is invalid.
ORA-06550: line 1, column 12:
PLS-00201: identifier 'MDS_INTERNAL_SHREDDED.GETREPOSITORYVERSION' must be decla
red
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
at oracle.mds.config.PConfig.loadFromBean(PConfig.java:684)
at oracle.mds.config.PConfig.<init>(PConfig.java:499)
at oracle.mds.config.MDSConfig.loadFromBean(MDSConfig.java:707)
at oracle.mds.config.MDSConfig.loadFromElement(MDSConfig.java:764)
at oracle.mds.config.MDSConfig.<init>(MDSConfig.java:420)
Truncated. see log file for complete stacktrace
*>*
*<Dec 15, 2011 12:51:22 PM GMT+05:30> <Error> <Deployer> <BEA-149231> <Unable to*
set the activation state to true for the application 'wsm-pm'.
*weblogic.application.ModuleException: [HTTP:101216]Servlet: "PolicyManagerValida*
*tor" failed to preload on startup in Web application: "/wsm-pm".*
oracle.adf.share.ADFShareException: MDSConfigurationException encountered in par
seADFConfiguration
at oracle.adf.share.config.ADFMDSConfig.parseADFConfiguration(ADFMDSConf
ig.java:178)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.adf.share.config.ADFConfigImpl.getResultFromComponent(ADFConfi
gImpl.java:472)
at oracle.adf.share.config.ADFConfigImpl.getConfigObject(ADFConfigImpl.j
ava:543)
at oracle.adf.share.config.ADFConfigImpl.getConfigObject(ADFConfigImpl.j
ava:521)
at oracle.adf.share.config.ADFConfigImpl.getMDSInstance(ADFConfigImpl.ja
va:586)
at oracle.adf.share.config.ADFConfigImpl.getMDSInstance(ADFConfigImpl.ja
va:581)
at oracle.adf.share.config.ADFContextMDSConfigHelperImpl.getMDSInstance(
ADFContextMDSConfigHelperImpl.java:274)
at oracle.adf.share.ADFContext.getMDSInstanceAsObject(ADFContext.java:16
*19)*
at oracle.wsm.repository.mds.MDSInstanceFactory.getMDSInstance(MDSInstan
ceFactory.java:95)
at oracle.wsm.policymanager.bean.AbstractBean.getRepository(AbstractBean
*.java:298)*
at oracle.wsm.policymanager.bean.AbstractBean.createSession(AbstractBean
*.java:198)*
at oracle.wsm.policymanager.bean.UpgradeManagerBean.seedWSMPolicyReposit
ory(UpgradeManagerBean.java:506)
at oracle.wsm.policymanager.web.PolicyManagerValidator.init(PolicyManage
rValidator.java:111)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(St
ubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
*120)*
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecuri
tyHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubL
ifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHel
per.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubI
mpl.java:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppS
Thanks...

I had a few packages and types in Invalid state.
I compiled the same.
But even then the same problem persists.
Please help if any idea of any other change that may be needed..
Thanks in advance

Gettin error while starting the weblogic portal server

Hi ,
This is Kalyan. I had installed weblogic portal 10.3 in my system.After installing i had tried for the sample portal web application. I had selected the portal web project-->given the project name and selected the necessary things .I had create sample portal when iam trying to run this portal on the server it showing me the error.
Error(s) found in module 'ProData'. Publish was cancelled. See "Problems" view for details.
A WebLogic Portal web application project should be added as a J2EE module to a WebLogic Portal EAR project for proper deployment at ProData
The associated EAR "ProDataEAR" is not a Portal Application Services EAR at ProData
A Portal Application Services web application should be associated with a Portal Application Services EAR for proper deployment at ProData
Here ProData is the my project name can anybody tell me the solution i will be grate ful to them
Thanks & Regards

Hi Kalyan
1. First you need to create the portal ear project by selecting the portal project facets. Then create the portal web project with portal facets and make sure it is added to first create portal ear project. By default it will show in the list. Then portal data sync project is optional. Since this is your first time you can skip for now. Later on you can add data sync project also to the same portal ear. Once you have this, then you can deploy the portal ear project on the portal domain. Remember that you need to create the portal domain with portal facets.
Delete the project you already created and start from fresh. If you already created any portlets or pageflows or jsps etc, copy those files as backup. Once you create portal ear and web projects, copy them into your new application.
Here is the link for details: http://download.oracle.com/docs/cd/E13155_01/wlp/docs103/quickstart/newproject.html
HTH
Ravi Jegga

Error while creating connection for Application server in Jdeveloper

Hi,
I am trying to create a new connection for my weblogic server from JDeveloper
I am using weblogic 6.1
The error is :javax.naming.AuthenticationException [Root exception is java.lang.SecurityException : attemting to add an object which is not an instance 0f java.security.Principal to a subject's Principal set
I am currectly passing my userID and password. but still it is giving the above exception.
Please advise me.
With thanks
Murthy

HI
In JDeveloper 10.1.3.1.0,
1. Click on the tab for the Connections navigator.
2. Right click on Application Server and select New Application Server Connection.
3. Enter a descriptive name for the new connection, and select the appropriate connection type from the drop down list. Click Next.
4. Specify oc4jadmin for User Name, then enter the oc4jadmin password. Click Next.
5. Select Single Instance for Connect To, then provide the host name where BPEL is installed, the OPMN port number, and the OC4J instance name (the default for 10.1.3.1 is oc4j_soa). Click Next.
6. Click Test Connection. If you have been successful, you should see "Success!"
7. Now, right click on Integration Server and select New Integration Server Connection.
8. Specify a connection name and click Next.
9. In the drop down list by Application Server, select the Application Server Connection you just created. Again, specify the host name where BPEL is installed and the port number. This port number will be the same that you specified for the Integration Server Connection to the home OC4J container. Click Next.
10. Test the connection. You should see something like:
Application Server: OK
BPEL Process Manager Server: OK
ESB Server: OK
11. Now, return to the Applications navigator, and try to redeploy your process using the Integration Server Connection just created. (It is possible that you will have to close JDeveloper and then reopen it for this to work.)
Cheers
Anirudh Pucha

Error while starting Managedserver for 2nd server in cluster

Similar Messages

Maybe you are looking for