ManagedServer

im serching for a foram to find out
problem in starting managedserver while configuring it in WLS
even i edited nodemanager.
im having
windows 7, weblogic 10.3.4
oracle database 11gr1
jdeveloper 11.1.2
Please,

Similar Messages

WebLogic10.3) starting ManagedServer with nodemanager script

When I started ManagedServer with script (startManagedWebLogic.sh), it was OK.
the script was
./startManagedWebLogic.sh ManagedServer_1 http://xxx.xxx.xxx.xxx:7001
But, the problem is here
I used this script to start ManagedServer named as ManagedServer_1
-----------------------------------------------------script run-----------------------------------------------
/home/shon/app/weblogic/10.3/was_1/wlserver_10.3/common/bin/wlscontrol.sh -d shon_domain_1 -n /home/shon/app/weblogic/10.3/was_1/common/nodemanager -r /home/shon/app/weblogic/10.3/was_1/user_projects/domains/shon_domain_1 -c -f startManagedWebLogic.sh -s ManagedServer_1 START
and I get this error log..
---------------------------------------------------error log ------------------------------------------------
<Wed Mar 11 05:08:26 FKST 2009)> <Info> <NodeManager> <Rotated server output log to '/home/shon/app/weblogic/10.3/was_1/user_projects/domains/shon_domain_1/servers/ManagedServer_1/logs/ManagedServer_1.out00004'>
Server failed to start (see server output log for details)
/home/shon/app/weblogic/10.3/was_1/user_projects/domains/shon_domain_1/bin> vi '/home/shon/app/weblogic/10.3/was_1/user_projects/domains/shon_domain_1/servers/ManagedServer_1/logs/ManagedServer_1.out00004'
<Mar 11, 2009 5:05:06 AM FKST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Mar 11, 2009 5:05:06 AM FKST> <Notice> <Log Management> <BEA-170019> <The server log file /home/shon/app/weblogic/10.3/was_1/user_projects/domains/shon_domain_1/servers/ManagedServer_1/logs/ManagedServer_1.log is opened. All server side log events will be written to this file.>
<Mar 11, 2009 5:05:06 AM FKST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError: java.lang.reflect.InvocationTargetException
java.lang.AssertionError: java.lang.reflect.InvocationTargetException
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:175)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:990)
at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:704)
Truncated. see log file for complete stacktrace
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
What the hell is the problem? Anyone knows?
boot.properties was set correctly,

Looks like this is an issue with insufficient privileges.
Regards,
Harsha Chava

Jaas Security and ManagedServer

Current release of Jdeveloper
Use JAAS
I have been using only the adm. server for deployment and using url:
http://localhost:7001/btms/faces/Welcome
The Welcome jsp is in a Unbounded task flow adfc-config.xml.
a button in Welcome.jsp invokes a Menu.jsp in a bounded taskflow.
This all works ok.
I changed the deployment to ManagedServer.
I am NOT using node manager or machine.
I deployed ok.
Both the app and jdbc are targeted to the managedserver.
The url is now:
http://localhost:7003/btms/faces/Welcome
Instead of the Welcome page appearing the login form is displayed.
When I enter userid/password
I received this message
oracle.adf.controller.security.AuthorizationException: ADFC-0619: Authorization check failed: '/Welcome.jspx' 'VIEW'. Error 500
The Welcome pagedef has grants for anonymous and manager roles.
Iam at a loss to how to proceed.
Any help is greatly appreciated.
Chuck
Problem solved.
Must restart managedserver .
http://localhost:7003/btms/faces/Welcome
Edited by: user11444590 on Jul 11, 2010 5:35 AM

Thank you for this.
Have you tried this yourself? It works with embedded OC4J and not for deployed application.
The process starts from index.jsp in the root and a redirection to Home.jspx:
+<% response.sendRedirect("faces/pages/Home.jspx"); %>+
Since Home.jspx is protected, another redirection occurs to Login.jspx, which delivers username and password to LoginBean class. LoginBean class makes a request to j_security_check which is actually hidden and part of JAAS (?).
Here is where I don't know what happens behind the scene. In your LoginBean (in J2EEAuthenticateUser):
out.println("<form action=\"j_security_check\" method=\"post\">");
+...+
out.println("</form>");
out.println("</body>");
out.println("</html>");
out.close();
fctx.responseComplete();
after login is complete, I can see on the location bar such an address:
.../faces/security/pages/j_security_page
and that such a 404 page not found. which I think is true. There is not such a page.
Regards
Hamid

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.

ManagedServer fails on integration domain

          Folks,
          I use weblogic platform 81sp2. I created only one server under a integration domain
          and started the server and it is just fine and connection pools are running fine.
          When I create admin server and managedserver combination, the managed server simply
          crash with connection pool errors and it doesn't find the cgDatasource.Everything
          looks same in config.xml.
          I am in the position to do clustering for my client integration domain and please
          help me to resolve this.
          Please see the errors below.It says 'It can't find the bpmArchPool'.But It is
          there as a target to managed server in config.xml file.
          Thanks, Johnson
          ####<20-Apr-2004 5:08:20 o'clock PM EDT> <Error> <JDBC> <telus-un890sb0w> <cgServer2>
          <main> <<WLS Kernel>> <> <BEA-001151> <Data Source "bpmArchDataSource" deployment
          failed with the following error: DataSource(bpmArchDataSource) can't be created
          with non-existent Pool (connection or multi) (bpmArchPool).> ####<20-Apr-2004
          5:08:20 o'clock PM EDT> <Info> <JDBC> <telus-un890sb0w> <cgServer2> <main> <<WLS
          Kernel>> <> <BEA-001156> <Stack trace associated with message 001151 follows:
          weblogic.common.ResourceException: DataSource(bpmArchDataSource) can't be created
          with non-existent Pool (connection or multi) (bpmArchPool) at weblogic.jdbc.common.internal.DataSourceManager.createDataSource(DataSourceManager.java:253)
          at weblogic.jdbc.common.internal.DataSourceManager.createAndStartDataSource(DataSourceManager.java:106)
          at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:190)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:330)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:590)
          at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:568)
          at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:240)
          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:324) at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:711)
          at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:690)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:476)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557) at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525) at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)
          at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946) at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
          at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7271)
          at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1210)
          at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:362)
          at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
          at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131) at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359) at weblogic.Server.main(Server.java:32)
          > ####<20-Apr-2004 5:08:20 o'clock PM EDT> <Info> <JMS> <telus-un890sb0w> <cgServer2>
          <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "WLI-B2B System
          Topic Factory" is started.> ####<20-Apr-2004 5:08:20 o'clock PM EDT> <Info> <JMS>
          <telus-un890sb0w> <cgServer2> <main> <<WLS Kernel>> <> <BEA-040108> <User connection
          factory "cgQueue" is started.>
          ####<20-Apr-2004 5:08:20 o'clock PM EDT> <Info> <WebLogicServer> <telus-un890sb0w>
          <cgServer2> <main> <<WLS Kernel>> <> <BEA-000256> <Invoking com.bea.wli.init.BPMStartup.main(null)>
          ####<20-Apr-2004 5:08:20 o'clock PM EDT> <Error> <WLW> <telus-un890sb0w> <cgServer2>
          <main> <<WLS Kernel>> <> <000000> <Failed to obtain connection to datasource=cgDataSource,
          using generic DB properties> ####<20-Apr-2004 5:08:20 o'clock PM EDT> <Error>
          <WLW> <telus-un890sb0w> <cgServer2> <main> <<WLS Kernel>> <> <000000> <Error in
          startup class com.bea.wli.store.DocumentStoreSetup Method: init: java.lang.IllegalStateException:
          Unable to start DocumentStore: com.bea.wli.store.DocumentStoreException: Could
          not find SQL Document Store cgDataSource at com.bea.wli.store.DocumentStoreSetup.init(DocumentStoreSetup.java:93)
          at com.bea.wli.store.DocumentStoreSetup.init(DocumentStoreSetup.java:55) 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:324) at com.bea.wli.init.BPMStartupShutdown.invoke(BPMStartupShutdown.java:324)
          at com.bea.wli.init.BPMStartupShutdown.startup(BPMStartupShutdown.java:196) at
          com.bea.wli.init.BPMStartup.main(BPMStartup.java:23) 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:324) at weblogic.t3.srvr.StartupClassService.invokeMain(StartupClassService.java:229)
          at weblogic.t3.srvr.StartupClassService.invokeClass(StartupClassService.java:160)
          at weblogic.t3.srvr.StartupClassService.access$000(StartupClassService.java:36)
          at weblogic.t3.srvr.StartupClassService$1.run(StartupClassService.java:121) at
          weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
          at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118) at
          weblogic.t3.srvr.StartupClassService.invokeStartupClass(StartupClassService.java:116)
          at weblogic.t3.srvr.StartupClassService.addDeployment(StartupClassService.java:88)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:330)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:590)
          at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:568)
          at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:240)
          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:324) at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:711)
          at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:690)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:476)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557) at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525) at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)
          at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946) at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
          at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7271)
          at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1210)
          at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:362)
          at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
          at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131) at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359) at weblogic.Server.main(Server.java:32)


Setup a local replica for the user and set his lotus notes to use this. The script no longer errors on trying to open his inbox.

ManagedServer entry using silent mode

          Folks,
          I created a Silent script for WebLogic81sp2 domain creation and everything seems
          to be ok.After creating the domain, I will be in the position to edit the startManagedWebLogic.cmd
          file manually to add the server name(set SERVER_NAME=ManagedServer).
          How can I update this using silent mode?
          See my script below, Thanks, Johnson
          //////Create the Admin Server
          find Server "myserver" as s1;
          set s1.Name "AdminServer";
          set s1.ListenAddress "localhost";
          set s1.ListenPort "10000";
          set s1.SSL.Enabled "false";
          //set s1.SSL.ListenPort "10001";
          set JavaHome "C:\beaplatform\jdk141_05";
          set ServerStartMode "dev";
          set CreateStartMenu "false";
          //////Create the Managed Server
          create Server "ManagedServer" as s2;
          set s2.ListenAddress "localhost";
          set s2.ListenPort "10010";
          set s2.SSL.Enabled "false";
          //set s2.SSL.ListenPort "10011";
          set JavaHome "C:\beaplatform\jdk141_05";
          set ServerStartMode "dev";
          set CreateStartMenu "false";


Hi
I am getting the below exception any idea?
Error: readTemplate() failed. Do dumpStack() to see details.
Problem invoking WLST – Traceback (innermost last):
File “c:\oracle\silentdomain.py”, line 3, in ?
File “C:\Users\test\AppData\Local\Temp\WLSTOfflineIni1709266438475496258.py
“, line 17, in readTemplate
The template to read must be a jar file containing a valid domain configuration
at com.oracle.cie.domain.script.jython.CommandExceptionHandler.handleExc
eption(CommandExceptionHandler.java:51)
at com.oracle.cie.domain.script.jython.WLScriptContext.handleException(W
LScriptContext.java:1538)
at com.oracle.cie.domain.script.jython.WLScriptContext.readTemplate(WLSc
riptContext.java:340)
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)
com.oracle.cie.domain.script.jython.WLSTException: com.oracle.cie.domain.script.
jython.WLSTException: com.oracle.cie.domain.script.ScriptException: unable to pa
rse “template-info.xml” from template jar “C:\oracle\wlserver_10.3\common\templates\domains\wls.jar
The template to read must be a jar file containing a valid domain configuration

Shared Capacity For Work Managers and state SUSPEND for ManagedServer

Hi!
I have 3 ManagedServers in cluster. I want configure the Overload Conditions for each ManagedServer - set Shared Capacity For Work Managers = 100. So, if the count of concurrent requests will be more than 100 for ManagedServer, this ManagedServer stopes processing new requests (as for sutdown state) and finishes processing the current requests, and all next requests go to a other ManagedServers.
Could you please tell me how to achieve it?
Now, ManagedServer changes state to OVERLOAD temporarily, and becoms to RUNNING.
Failure Action = Suspend this server (dindt help)

You can consider using the capacity constraint
capacity - Causes the server to reject requests only when it has reached its capacity. The default is -1. Note that the capacity includes all requests, queued or executing, from the constrained work set. Work is rejected either when an individual capacity threshold is exceeded or if the global capacity is exceeded. This constraint is independent of the global queue threshold.
Check the below links for more on this:
http://docs.oracle.com/cd/E12839_01/web.1111/e13701/self_tuned.htm#i1060813
http://www.oracle.com/technetwork/articles/entarch/workload-management3-087769.html

Keep on getting exception when trying to start ManagedServer wit h NodeManager in wls 7.0

hi all,
i am trying to start a managed server using nodeManager, but i keep on getting
following exception:
weblogic.nodemanager.NodeManagerException: [Could not execute command start for
server managedServer via the Node Manager - reason: [CommandInvoker: Failed to
send command: 'online to server 'managedServer' to NodeManager at host: 'localhost:5555'
with exception FATAL Alert:HANDSHAKE_FAILURE - The handshake handler was unable
to negotiate an acceptable set of security parameters.. Please ensure that the
NodeManager is active on the target machine].]
     at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeManagerRuntime.java:472)
     at weblogic.nodemanager.NodeManagerRuntime.start(NodeManagerRuntime.java:76)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:732)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:714)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
     at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:952)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:470)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:198)
     at $Proxy86.start(Unknown Source)
     at weblogic.server.ServerLifeCycleRuntime.startServer(ServerLifeCycleRuntime.java:502)
     at weblogic.server.ServerLifeCycleRuntime.access$0(ServerLifeCycleRuntime.java:471)
     at weblogic.server.ServerLifeCycleRuntime$1.execute(ServerLifeCycleRuntime.java:423)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
here is my script for starting nodemanager
set JAVA_HOME=c:\bea\jdk131
set WL_HOME=c:\bea\weblogic700
set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
set CLASSPATH=.;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar
java -Djava.security.policy=C:\bea\weblogic700\server\lib\weblogic.policy weblogic.nodemanager.NodeManager
can anyone point me to the right direction for solving this problem?
in the adminserver console i have defined a machine for teh managedserver, and
nodemanager is supposed to run at localhost:5555 (and indeed it does, because
ihave started it successfully).
thanx in advance and regards
marco

Hi
add this params to the nodemanager start script
-Dweblogic.nodemanager.KeyFile=${NODEMGR_HOME}/config/
demokey.pem
-Dweblogic.nodemanager.certificateFile=${NODEMGR_HOME}/config/democert.pem
-Dweblogic.security.SSL.ignoreHostname.Verification=true
you need to specify certs for nodemanager
make sure servers use the same certs..
Best regards
"Marco" <[email protected]> wrote:
>
hi all,
i am trying to start a managed server using nodeManager, but i keep
on getting
following exception:
weblogic.nodemanager.NodeManagerException: [Could not execute command
start for
server managedServer via the Node Manager - reason: [CommandInvoker:
Failed to
send command: 'online to server 'managedServer' to NodeManager at host:
'localhost:5555'
with exception FATAL Alert:HANDSHAKE_FAILURE - The handshake handler
was unable
to negotiate an acceptable set of security parameters.. Please ensure
that the
NodeManager is active on the target machine].]
     at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeManagerRuntime.java:472)
     at weblogic.nodemanager.NodeManagerRuntime.start(NodeManagerRuntime.java:76)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:732)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:714)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
     at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:952)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:470)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:198)
     at $Proxy86.start(Unknown Source)
     at weblogic.server.ServerLifeCycleRuntime.startServer(ServerLifeCycleRuntime.java:502)
     at weblogic.server.ServerLifeCycleRuntime.access$0(ServerLifeCycleRuntime.java:471)
     at weblogic.server.ServerLifeCycleRuntime$1.execute(ServerLifeCycleRuntime.java:423)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
here is my script for starting nodemanager
set JAVA_HOME=c:\bea\jdk131
set WL_HOME=c:\bea\weblogic700
set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
set CLASSPATH=.;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar
java -Djava.security.policy=C:\bea\weblogic700\server\lib\weblogic.policy
weblogic.nodemanager.NodeManager
can anyone point me to the right direction for solving this problem?
in the adminserver console i have defined a machine for teh managedserver,
and
nodemanager is supposed to run at localhost:5555 (and indeed it does,
because
ihave started it successfully).
thanx in advance and regards
marco

WLS: Several ManagedServer without clustering and same activities

Hi all,
I have a request for special solution for several ManagedServer without clustering and same activities (e.g. SOA or OSB).
In classic case, we have for example 1 AdminServer + 1 ManagedServer (SOA, or OSB). If we want to increase number of SOA-Managedserver, then we add other managed server in WLS-cluster.
In this case, we want to have several "Independent" ManagedServer with different port number and without cluaster but in same domain.
In addition, because we don't want to impact any project in one managed server to other managed server, we need to define different URL:ports for administration: For example: OSB has following URL:
http://localhost:7001/sbconsole
Is it possible to define other ports for other OSB-managed server? e.g. http://localhost:7003/sbconsole, http://localhost:7004/sbconsole
I would like to know, if any experience is available regarding this matter.
Thanks inadvance,
Moh

Hi Moh
1. There are few things that should be clear about the Weblogic Domain and Weblogic Cluster Architecture.
2. Any Weblogic Domain whether its Clustered or Non Clustered will have ONLY ONE Single AdminServer. You CANNOT have more than one AdminServer. Now for Cluster, you can have "n" number of Managed Servers and "n" number of Clusters. Each Cluster is just like a logical grouping of some managed servers. BUT main thing is, if you want to have High Availability architecture to support load balancing, fail over etc, you should and must have a Cluster with managed servers. And expose this Clustered Weblogic Servers into some sort of load balancer like Apace WebServer. Then expose single Apache Web Server URL (host, port + app url) to outside world. General practice is for HA architecture, you do not expose individual managed servers.
3. So coming to your requirement, you can have "n" number of managed servers. And each managed server can deploy their own specific application. And these managed servers naturally will have different port numbers, if they are all on the same physical box. If they are on different boxes, there is no clash of port numbers. Then in front end apache web server, check for each in coming request url and according direct that to appropriate backend weblogic server. This is good but you will NOT get any HA features going in this way. Instead of exposing individual managed servers, I would recommend just create a cluster for each one of them. And expose cluster. For now each cluster can have only 1 manged severs. Later on you can add more also. This gives you HA features. Something like this for example:
Domain = Single Domain
AdminServer = 1 AdminServer only. Not possible more then one.
ManagedServers = 4 (MS1, MS2, MS3, MS4)
Cluster1 = MS1, MS2 -> Deploy App1
Cluster2 = MS3 -> Deploy App2
Cluster3 = MS4 -> Deploy App3
Have a SINGLE Apache WebServer or any other Hard ware load balancer (Apache is free and widely used). Expose this host, port to outside world or actual users (outside or inside). In Apache httpd.conf file, configure like 3 settings, to check for incoming urls and redirect to back end cluster 1 or 2 or 3. Refer docs for full details.
Requests coming to Apache WebServer can use incoming url pattern and pass the request to appropriate backend cluster
http://apachehost:apachport/myApp1 -> Redirect to Cluster1
http://apachehost:apachport/myApp2 -> Redirect to Cluster2
http://apachehost:apachport/myApp3 -> Redirect to Cluster3
Now this gives you full flexibility to add or remove more servers from any of above Clusters. Even if you have single managed server, try to put that into cluster and expose the cluster.
4. Now comes the Adminstration applications like console, sbconsole, em (Enterprise Manager for SOA), cs (Content Server for ECM) etc. All these are deployed only to AdminServer and it makes sense also. Say in above architecture only AdminServer can have visibility to all the managed servers and clusters. Each managed server may not know about the others. Anyhow, the point is, for any Domain you will have only 1 AdminServer and most of the adminstration applications are deployed only to AdminServer. This means literally you will have just one url to control all the applications across all the clusters like http://adminhost:adminport/sbconsole. I am not familiar with sbconole, but for em I am sure its only targetted to admin server. Now, if you manually target these apps to cluster, not sure if this works also. Mostly it may not.
Also, admin urls are not exposed to any users. Only Adminstrators can access them. You can refine some rules like have very few admins with full privileges. Some can do only deployments, some can do only monitoring (read only access) etc.
Thanks
Ravi Jegga

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

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

Unable to Start ManagedServer using Console

Hi,
I created one Admin Server(prot is 7001) and 1 managed server(name: MS1 , port is 7003) and i try to run managed server, it is run fine after that i deleted entire domain and created domain , also created 1 Admin server and 1 managed server(MS1,7003) with same server name and port numbers then i try to start managed server using console by using startManagedServer.cmd MS1 t3://127.0.0.1:7001 but i got error like ### <1294642894256> <BEA-002606> <Unable to create a server socket for listening on channel "Default". The address 0.0.27.92 might be incorrect or another process is using port 7003: java.net.BindException: Cannot assign requested address: JVM_Bind.>
Note:: Even i created manager server MS1 with another port number(ex: 7009) then also i got same error
Pls help any body on this issue???

Hi,
You should not delete the domain without stopping the running servers in that domain.
Try to kill the instance that is already running on 7003 port.
As you said even on 7009 , you are facing the same problem, try to edit the config.xml and change the listen address to 127.0.0.1 .
Make sure that you are taking a backup of config.xml before editing.
Thanks,
Kartheek
http://middlewareforum.com

Accessing loaclMBeanServer on ManagedServer

Hi,
Is it possible to access localMBeanServer using JMX( and not WebLogic's extension, MBeanHome), on a Managed Server?
I am only able to access the admin server using the usual JNDI lookup. How would I go about accessing the localMBeanServer?
Thanks

There is some documentation on accessing the mbean servers, not sure if
you've looked at that already.
For local access to the runtimeMBeanServer:
http://e-docs.bea.com/wls/docs100/jmx/accessWLS.html#RuntimeMBeanServerJNDIAccess
For remote access to mbean servers:
http://e-docs.bea.com/wls/docs100/jmx/accessWLS.html#wp1112969
Tony
Ram Sriharsha wrote:
Hi,
Is it possible to access localMBeanServer using JMX( and not WebLogic's extension, MBeanHome), on a Managed Server?
I am only able to access the admin server using the usual JNDI lookup. How would I go about accessing the localMBeanServer?
Thanks

ManagedServer and NotOwnerException

Hi all,
Our application is running on WIN2000 and is using the RDBMSREALM.
When I try to start a Managed Server to connect to the AdminServer I will receive
the following exceptions:
Thanks for any help!
Connecting to http://localhost:7001...
log file: E:\bea\wlserver6.0sp1\.\test_01.log
<22.05.2001 10:08:15 GMT+02:00> <Info> <Logging> <Only log messages of severity
"Error" or worse will be displayed in this window. This can be changed at Admin
Console> mydomain> Servers> test_01> Logging> General> Stdout severity threshold
>
<22.05.2001 10:08:15 GMT+02:00> <Emergency> <Server> <Unable to initialize the
s
erver: 'Fatal initialization exception
Throwable: java.lang.IllegalAccessError: java.security.acl.NotOwnerException
java.lang.IllegalAccessError: java.security.acl.NotOwnerException
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:36)
at weblogic.security.acl.Realm.authenticate(Realm.java:183)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:11
6)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialConte
xtFactoryDelegate.java:429)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialCon
textFactoryDelegate.java:272)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:244)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:888)
at weblogic.management.Admin.start(Admin.java:303)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
'>
The WebLogic Server did not start up properly.
Exception raised: java.lang.IllegalAccessError: java.security.acl.NotOwnerExcept
ion
java.lang.IllegalAccessError: java.security.acl.NotOwnerException
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:36)
at weblogic.security.acl.Realm.authenticate(Realm.java:183)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:11
6)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialConte
xtFactoryDelegate.java:429)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialCon
textFactoryDelegate.java:272)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:244)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:888)
at weblogic.management.Admin.start(Admin.java:303)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
E:\bea\wlserver6.0sp1>goto finish
E:\bea\wlserver6.0sp1>cd config\mydomain
E:\bea\wlserver6.0sp1\config\mydomain>ENDLOCAL

Hi all,
Our application is running on WIN2000 and is using the RDBMSREALM.
When I try to start a Managed Server to connect to the AdminServer I will receive
the following exceptions:
Thanks for any help!
Connecting to http://localhost:7001...
log file: E:\bea\wlserver6.0sp1\.\test_01.log
<22.05.2001 10:08:15 GMT+02:00> <Info> <Logging> <Only log messages of severity
"Error" or worse will be displayed in this window. This can be changed at Admin
Console> mydomain> Servers> test_01> Logging> General> Stdout severity threshold
>
<22.05.2001 10:08:15 GMT+02:00> <Emergency> <Server> <Unable to initialize the
s
erver: 'Fatal initialization exception
Throwable: java.lang.IllegalAccessError: java.security.acl.NotOwnerException
java.lang.IllegalAccessError: java.security.acl.NotOwnerException
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:36)
at weblogic.security.acl.Realm.authenticate(Realm.java:183)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:11
6)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialConte
xtFactoryDelegate.java:429)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialCon
textFactoryDelegate.java:272)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:244)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:888)
at weblogic.management.Admin.start(Admin.java:303)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
'>
The WebLogic Server did not start up properly.
Exception raised: java.lang.IllegalAccessError: java.security.acl.NotOwnerExcept
ion
java.lang.IllegalAccessError: java.security.acl.NotOwnerException
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:36)
at weblogic.security.acl.Realm.authenticate(Realm.java:183)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:11
6)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialConte
xtFactoryDelegate.java:429)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialCon
textFactoryDelegate.java:272)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:244)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:888)
at weblogic.management.Admin.start(Admin.java:303)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
E:\bea\wlserver6.0sp1>goto finish
E:\bea\wlserver6.0sp1>cd config\mydomain
E:\bea\wlserver6.0sp1\config\mydomain>ENDLOCAL

Problem when we created the managed server to configure different ports.

I am trying to configure different ports for admin console and my communication service as we can’t share admin port to the outside world.
So that only admin can access admin console using admin port.
And out side clients can access my webapplication using different port.
For this i have created the managed server in weblogic.and I deployed the application on managed server.
Now admin server is running on 8001 port and my Communication Service application is running on 7001 port.
But when I tried to configure MBeans related to myCommunicationServiceApplication those were disapper on admin console. And the other wlng services are appearing on admin console.
1. Since my application deployed on managed server MBeans registration happened from myapplication hence it’s disappear on admin console.
Now If I want to configure Mbeans (related to my communication service) how can I configure it?
2. My communication service using configurationStore module and other wlng services.
When I tried to start my application on managed server I got the below error:
<Apr 28, 2009 12:22:44 PM IST> <Error> <Deployer> <BEA-149231> <dscp11166.TechMahindra.com> <Unable to set the activation state to true for the application 'wlng_nt_qualcomm_active_mediation [Version=1.0]'.
com.bea.wlcp.wlng.api.storage.configuration.ConfigurationException: Configuration store module is not available.
3. I tried to target all wlngResources to manged server by editing config.xml file.
Then all wlng services disappears on admin console. If this is the case how can I configure container/account services on wlng?
I have created the Basicweblogic domain.
Below is the config.xml for reference.
"QualcommServer" is managed server name.
Can any one please suggest me how to configure this kind of scenarios?
<server>
<name>AdminServer</name>
<machine>new_Machine_1</machine>
<listen-port>8001</listen-port>
<default-iiop-user>weblogic</default-iiop-user>
<default-iiop-password-encrypted>{3DES}W8nBdoJPRZ8TkwcXwAZoxA==</default-iiop-password-encrypted>
<listen-address>localhost</listen-address>
</server>
<server>
<name>QualcommServer</name>
<machine>new_Machine_1</machine>
<listen-address>localhost</listen-address>
<server-start>
<java-vendor>Sun</java-vendor>
<java-home>C:\Program Files\Java\jdk1.6.0</java-home>
<class-path>C:\bea\wlng400\server\lib\weblogic.jar;C:\bea\wlng_pds400\lib\wlng\wlng.jar</class-path>
<bea-home>C:\bea</bea-home>
<username>weblogic</username>
<password-encrypted>{3DES}W8nBdoJPRZ8TkwcXwAZoxA==</password-encrypted>
</server-start>
</server>
<embedded-ldap>
<name>managedserver</name>
<credential-encrypted>{3DES}9q80YuFJueVVJxoWduJA1OGhbqk14EpgQWWyTrzlmxo=</credential-encrypted>
</embedded-ldap>
<configuration-version>10.0.1.0</configuration-version>
<app-deployment>
<name>wlng_nt_session#4.0</name>
<target>QualcommServer</target>
<module-type>ear</module-type>
<source-path>C:\bea\wlng400/applications/wlng_nt_session.ear</source-path>
<security-dd-model>CustomRolesAndPolicies</security-dd-model>
</app-deployment>
<app-deployment>
<name>interceptors</name>
<target>QualcommServer</target>
<module-type>ear</module-type>
<source-path>C:\bea\wlng400/applications/interceptors.ear</source-path>
<security-dd-model>CustomRolesAndPolicies</security-dd-model>
</app-deployment>
<app-deployment>
<name>wlng_prm</name>
<target>QualcommServer</target>
<module-type>ear</module-type>
<source-path>C:\bea\wlng400/applications/wlng_prm.ear</source-path>
<security-dd-model>CustomRolesAndPolicies</security-dd-model>
</app-deployment>
<app-deployment>
<name>wlng_nt_qualcomm_active_mediation#1.0</name>
<target>QualcommServer</target>
<module-type>ear</module-type>
<source-path>servers\AdminServer\upload\wlng_nt_qualcomm_active_mediation.ear</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<machine>
<name>new_Machine_1</name>
<node-manager>
<name>new_Machine_1</name>
<listen-address>localhost</listen-address>
</node-manager>
</machine>
<jms-server>
<name>JMSServer-AdminServer</name>
<target>AdminServer</target>
</jms-server>
<jms-system-resource>
<name>WLNGJMSResource</name>
<target>QualcommServer</target>
<descriptor-file-name>jms/wlng-jms.xml</descriptor-file-name>
</jms-system-resource>
<custom-resource>
<name>networktier</name>
<target>AdminServer</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>AdminServer</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

Dear Nariharan,
Today I faced a simlar issue, and this SAP Note helped me fix it: 1966807 - Duplication of AET table records in change processing
In my case, cardinality of AET table was 1:1, and I was getting duplicate PARENT_ID every time when trying to create a subsequent service request for my activity.
Regards,
Andrew

ManagedServer

Similar Messages

Maybe you are looking for