1 NodeManager, 1 Admin Server and 2 Managed Servers
Hi All, I'm new in Weblogic and this is my 1st time to post a question on this forum. Would like ask for help from you all above my setup, I'm not sure whether it will work or not. Please find out the scenario below:
Setup:
1 Machine (RedHat Enterprise Linux 5.5)
1 NodeManager
1 AdminServer (Name: APP)
2 Managed Servers (Name: APPLIVE, APPUAT)
Currently I would like to using one NodeManager to control both Managed Servers under 1 machine. When I configure my APP Admin Server and two Managed Servers, i would like to nmEnroll both Managed Servers under one NodeManager but it will overwrite my enroll entries if i enroll 2nd Managed Server.
Is it possible to configure NodeManager to accept both Managed Servers entries? Thanks. :)
Edited by: user13602952 on Jan 2, 2011 9:54 PM
Hi Hong,
Following are the few things which you help you understand about NodeManager and nmEnroll
- First of all a Node Manager process is not associated with a specific WebLogic domain but with a machine
- When you run a nmEnroll then you just give "domainDir" and "nmHome" which would then gets the file called "*nm_password.properties*" which contains the encrypted username and password that is used for server authentication and "*SerializedSystemIni.dat*" file.
Example:
nmEnroll([domainDir], [nmHome])
- With above files it also updates the nodemanager.domains file with the domain information which was mentioned in the above command.
Thus when you run the nmEnroll command it would get all the details which it needs to start any managed servers in the same Machine, hence you do not need to run the same commend for each managed servers in the same Machine.
For more information have a look at the below links:
Topic: Search for "nmEnroll"
http://download.oracle.com/docs/cd/E13222_01/wls/docs92/config_scripting/reference.html
Topic: Overview of Node Manager
http://download.oracle.com/docs/cd/E13222_01/wls/docs90/server_start/nodemgr.html#1091317
Regards,
Ravish Mody
http://middlewaremagic.com/weblogic/
Come, Join Us and Experience The Magic…
Similar Messages
-
Run Admin Server with multiple Managed Servers each using different userid?
We currently run separate WebLogic domain instances for each business application in a Unix environment. Each one is created using a unix userid unique to that application and which owns all the files and is used to run the process when that particular WebLogic instance is started up. We have run this way for a while.
I am considering altering our approach to the one that is recommended, i.e. in our Production environment we would run a single Admin instance with numerous managed servers. One issue I'm stuck on is the fact that in our current environment, each application has a different unix userid that owns the files making up the WebLogic domain instance and that WebLogic instance is run under that userid.
I've investigated and experimented using WebLogic 10.3 preview and WebLogic 10.0, but I haven't been able to determine what I have to do to make each managed server's files and processes belong to a different unix userid, if that is even possible.
Is there a way, using the recommended approach, where there is a single Admin instance that has multiple managed servers whose files and processes are owned by different unique, unix userids?
If not, how would you separate access to each of the Managed Servers so that the programmers who maintain them don't have access to Managed Servers that they are not responsible for?
Thanks for any help or suggestions.....Hi:
I played with this stuff and I found that this will work, without the Location elements:
<IfModule mod_weblogic.c>
MatchExpression /app1 WebLogicHost=server1|WebLogicPort=7003
MatchExpression /app2 WebLogicHost=server2|WebLogicPort=7003
</IfModule>
Also this will work too, with no entries inside the IfModule element:
<Location /app1 >
SetHandler weblogic-handler
WebLogicHost server1
WebLogicPort 7003
</Location>
<Location /app2 >
SetHandler weblogic-handler
WebLogicHost server2
WebLogicPort 7003
</Location> -
WLS10 Admin Server disconnecting from managed servers
Anyone come across this issue?
We have a web service using the Apache Axis2 framework running on a WLS10 server on AIX O/S. The managed server that host this web service regularly disconnect from the Admin Server. The server status remains in a 'Running' condition and the web service remains in an 'Active' state but the Health state from the console which should read 'OK' appears blank and the web service is non-responsive. The only way to get out of this issue is to bounce the server which we are doing anywhere from 1 to 5 times a day. Any ideas on why this is happening?some times it may happen due to WLS version difference between admin server and managed server. Please make sure managed server is not running with latest version than admin server. Or it can be JDK issues with memory settings and garbage collection. Or it may be related admin traffic iin domain. these are my guesses only.
-
What is the Ideal Production Setup For One Admin and 4 Managed Servers
Dear Experts
I will be starting with production setup including one Admin server and 4 managed servers in one single domain.
I am thinking of creating a single node environment(no clusters) as the machine has following configuration
OS : Windows Server 2008 R2 Datacenter
RAM : 48 GB
System Type : 64 bit
Processor : Intel(Xenon) 4 processors [email protected]
Can you please let me know if this configuration would suffice for the 4 managed servers if i assign Xmx and Xms as 4096 and Heap Space as 1024 to all the Managed Servers.
It is very urgent and i need to convey to the Infrastructure team if harware procurement is required.
We are looking at somewhere around 300 concurrent users(maximum load) and 100(minimum load) at a given point of time.
Please reply ASAP.
Thanks in advance
Edited by: Abhinav Mittal on Apr 23, 2013 7:58 PM
Edited by: Abhinav Mittal on Apr 23, 2013 8:03 PMHeap size must be calculated according to the applications that are been deployed on each JVM.
With no deployments, you dont need more than 256k for managed servers heap size and 512k for adminserver. As biggest its your heap size, longer will take your garbage collection. And if you can prevent it, better do it.
Kinds,
Gabriel Abelha -
Recommended configuration for Oracle VM Server and VM Manager
Hi,
Currently we have two dedicated DELL servers (VM server and VM Manager) for which are building an Oracle stack environment.
We are facing a problem which we didn't find answer from Oracle docs or via Google. The problem is that the virtual machines we create in VM Manager can't be connected to the outside world, and we think it's because our host (Hetzner) does not allow ports eth1-eth3 to be connected to the servers, unless we have these servers in the same rack and connected via switch.
Our question is, is it recommended configuration to have VM Server and VM Manager servers in the same rack and connected via switch?
If yes, the next question is, if we need in the future to add one more dedicated DELL server to our configuration to host virtual machines, is it possible if the new third dedicated DELL server is not connected via switch to the two dedicated DELL servers we have already have?
If no, the next question is, what could be the recommended configuration and solution to our problem in our case that ports eth1-eth3 cannot be connected to the servers?
Please do not hesitate to ask if you need more information. I do appreciate your time and expertise. Thanks.The architectural environment is now done like on this graphic. For security reasons Hetzner hosting service does not allow ports eth1-eth3 to be connected, but in internal network under switch they do.
-
Different service packs in admin server and managed server
Hi,
Has anybody successfully used a WebLogic 6.1 SP1 managed server that
connects to a WebLogic 6.1 SP 2 admin server?
BEA's docs claim:
"The Administration Server must be running the same version of
WebLogic Server as the Managed Servers in its domain. The
Administration Server must also have the same or later service pack
installed as the Managed Servers in its domain. For example, the
Administration Server could be running version 6.1, Service Pack 2
while the Managed Servers are running version 6.1, Service Pack 1."
This is precisely what we want to do, but it's not working. In this
case, we need to run the admin server and managed server on the same
machine, but we need the managed server to run SP 1 to work around a
bug in SP 2. So to our initial installation of WebLogic 6.1 SP 2,
where I run the admin server, I added a second installation, this time
WebLogic 6.1 SP 1, with a different BEA_HOME. When I start the
managed server from this second installation, I can see from the logs
that it is starting up correctly as 6.1 SP 1. But then it fails with
a ClassCastException when connecting to the admin server (I have
included the stack trace below). This seems typical of version
compatibility problems I've had when I've tried connecting to a server
with a client of a different version.
But in this case, you are supposed to be able to have the managed
server with a lower service pack. Does this work for anybody? Has
anybody encountered the problem I'm having? Note that the servers are
not clustered, if that makes any difference, and we have a custom
security realm in addition to the default file realm (though "system"
of course is in the default file realm).
Thanks in advance for any help,
Jim Doyle
[email protected]
####<Aug 8, 2002 10:25:38 AM EDT> <Emergency> <Server></server>
<chile.iso-ne.com> <webui
server> <main> <system> <> <000000> <Unable to initialize the server:
'Fatal ini
tialization exception
Throwable: java.lang.ClassCastException:
weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException:
weblogic.security.acl.DefaultUserInfoImpl
at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:164)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack traceHi,
Has anybody successfully used a WebLogic 6.1 SP1 managed server that
connects to a WebLogic 6.1 SP 2 admin server?
BEA's docs claim:
"The Administration Server must be running the same version of
WebLogic Server as the Managed Servers in its domain. The
Administration Server must also have the same or later service pack
installed as the Managed Servers in its domain. For example, the
Administration Server could be running version 6.1, Service Pack 2
while the Managed Servers are running version 6.1, Service Pack 1."
This is precisely what we want to do, but it's not working. In this
case, we need to run the admin server and managed server on the same
machine, but we need the managed server to run SP 1 to work around a
bug in SP 2. So to our initial installation of WebLogic 6.1 SP 2,
where I run the admin server, I added a second installation, this time
WebLogic 6.1 SP 1, with a different BEA_HOME. When I start the
managed server from this second installation, I can see from the logs
that it is starting up correctly as 6.1 SP 1. But then it fails with
a ClassCastException when connecting to the admin server (I have
included the stack trace below). This seems typical of version
compatibility problems I've had when I've tried connecting to a server
with a client of a different version.
But in this case, you are supposed to be able to have the managed
server with a lower service pack. Does this work for anybody? Has
anybody encountered the problem I'm having? Note that the servers are
not clustered, if that makes any difference, and we have a custom
security realm in addition to the default file realm (though "system"
of course is in the default file realm).
Thanks in advance for any help,
Jim Doyle
[email protected]
####<Aug 8, 2002 10:25:38 AM EDT> <Emergency> <Server></server>
<chile.iso-ne.com> <webui
server> <main> <system> <> <000000> <Unable to initialize the server:
'Fatal ini
tialization exception
Throwable: java.lang.ClassCastException:
weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException:
weblogic.security.acl.DefaultUserInfoImpl
at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:164)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace -
Problem creating a domain w/ one Admin Server and Managed Server
I went through the config wizard (Weblogic 10.2) and set up a domain w/ 1 Admin Server and Managed Server. When I start the Admin server I get the following error:
####<Jul 30, 2008 6:05:28 PM PDT> <Error> <Store> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328289> <BEA-280061> <The persistent store "pfProliferationJMSStore" could not be deployed: weblogic.store.PersistentStoreException: Can't find JDBC DataSource portalFrameworkPoolNeverXA: javax.naming.NameNotFoundException: Unable to resolve 'portalFrameworkPoolNeverXA'. Resolved ''; remaining name 'portalFrameworkPoolNeverXA'
weblogic.store.PersistentStoreException: Can't find JDBC DataSource portalFrameworkPoolNeverXA: javax.naming.NameNotFoundException: Unable to resolve 'portalFrameworkPoolNeverXA'. Resolved ''; remaining name 'portalFrameworkPoolNeverXA'
at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:105)
at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:184)
at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:162)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:57)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
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.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
javax.naming.NameNotFoundException: Unable to resolve 'portalFrameworkPoolNeverXA'. Resolved ''; remaining name 'portalFrameworkPoolNeverXA'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1138)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:251)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:205)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:100)
at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:184)
at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:162)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:57)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
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.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Jul 30, 2008 6:05:28 PM PDT> <Warning> <Management> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328289> <BEA-141197> <The deployment of pfProliferationJMSStore failed.
weblogic.management.DeploymentException:
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:60)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
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.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
javax.naming.NameNotFoundException: Unable to resolve 'portalFrameworkPoolNeverXA'. Resolved ''; remaining name 'portalFrameworkPoolNeverXA'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1138)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:251)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:205)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:100)
at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:184)
at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:162)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:57)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
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.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Jul 30, 2008 6:05:28 PM PDT> <Error> <JMS> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328368> <BEA-040123> <Failed to start JMS Server "pfJMSServer" due to weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist.
weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:296)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:184)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
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.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Jul 30, 2008 6:05:28 PM PDT> <Warning> <Management> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328368> <BEA-141197> <The deployment of pfJMSServer failed.
weblogic.management.DeploymentException: Internalrror activating the JMS Server pfJMSServer: weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:198)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
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.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:296)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:184)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
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.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Jul 30, 2008 6:05:28 PM PDT> <Error> <Deployer> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328461> <BEA-149231> <Unable to set the activation state to true for the application 'pf-proliferation-jms'.
weblogic.application.ModuleException: ERROR: Could not activate pf-proliferation-jms!pfProliferationQueue
at weblogic.jms.backend.BEDestinationRuntimeDelegate.activate(BEDestinationRuntimeDelegate.java:238)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1717)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
at weblogic.jms.module.JMSModule.activate(JMSModule.java:332)
at weblogic.jms.module.ModuleCoordinator.activate(ModuleCoordinator.java:182)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:182)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:359)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:42)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
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.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
weblogic.messaging.kernel.KernelException: The Messaging Kernel pfJMSServer has not yet been opened
at weblogic.messaging.kernel.internal.KernelImpl.checkOpened(KernelImpl.java:191)
at weblogic.messaging.kernel.internal.DestinationImpl.activate(DestinationImpl.java:279)
at weblogic.messaging.kernel.internal.QueueImpl.activate(QueueImpl.java:1633)
at weblogic.messaging.kernel.internal.DestinationImpl.resume(DestinationImpl.java:263)
at weblogic.messaging.kernel.internal.QueueImpl.resume(QueueImpl.java:1809)
at weblogic.jms.backend.BEDestinationImpl.start(BEDestinationImpl.java:609)
at weblogic.jms.backend.BEDestinationRuntimeDelegate.activate(BEDestinationRuntimeDelegate.java:235)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1717)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
at weblogic.jms.module.JMSModule.activate(JMSModule.java:332)
at weblogic.jms.module.ModuleCoordinator.activate(ModuleCoordinator.java:182)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:182)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:359)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:42)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
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.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>I am using the default db the installation uses which is PointBase. I am not using any specific db, JDBC Datasource/Connection pool Configuration.
Just to try something different, I tried creating a domain w/ one Admin and Managed Server which uses a Cluster and I did not get any errors. From what I read, a cluster is not necessary but not sure why it works without errors w/ a cluster.
I will try commenting out the datasource from the config and see what happens and will let you know. -
Communication protocol between Admin Server and Managed Server
Hello - I am hoping someone can help me here to understand the communication protocols used in my setup.
Here is my understanding of the protocol that are used between each component.
End User <--->HTTPS<--->LoadBalancer Device<--->HTTPS<--->Web Server<---->HTTPS<--->WebLogic Server(Managed Server)<--->LDAP/JDBC<-->Data tier components
AdminServer<--->T3<--->Managed Server i.e. The communication protocol between Admin Server and Managed server is T3
The communication protocol between Managed Servers running in one cluster on two seperate machine is What?
Thank you.Hello, interesting question.
In the documentation " [cluster multicast communication|http://download.oracle.com/docs/cd/E13222_01/wls/docs90/cluster/features.html#1007001] " don't specify the used protocol to pack the information for example in a session replication.
Although in a session replication all objects must be serializable i don't think rmi protocol is used.
I hope some expert give us some light in this issue :-)
http://download.oracle.com/docs/cd/E13222_01/wls/docs90/cluster/features.html#1007001 -
Creating Weblogic domain with Admin Server and managed servers on different
I am trying to create Weblogic domain where Admin Server and managed servers on different machines. However I am unable to find any steps which would allow me to do so. The config.sh script always creates an Admin Server. Please help.
Whilst the method that Lawrence gives can result in a domain that is perfectly functional, it is a method that can result in errors as you are having to enter the same information twice. Also you will create two admin servers, as the second domain creation will have the console added to it on the renamed admin server and this will give issues.
The best method to create a domain spamming multiple physical machines, is to create the domain with all the components on the first machine. This means planning the domain and making sure all components are added once; so having the information about the domain written out is wise. Ensure that the WLS software is installed in the same path on each machine before starting.
Then copy the domain that you have created from one machine to the other, keeping the same paths. You can simply copy (I've used this method multiple times without issue) but the supported way would be to use the WLST PACK and UNPACK methods. These create and extract domains from templates. Some more information on these is given here -> http://docs.oracle.com/cd/E13179_01/common/docs100/pack/intro.html#wp1069056 -
Hello,
I need your help to fix a critical problem to start Admin server and BI server :
# ...domains/bifoundation_domain/bin/startWebLogic.sh ....
Failed with
17-Mar-2015 17:17:33 oracle.security.jps.internal.credstore.ssp.CsfWalletManager openWallet
WARNING: Opening of wallet based credential store failed. Reason java.io.IOException
Best Regards
Djams
More détails in ... /logs/AdminServer.log :
####<17-Mar-2015 17:14:16 o'clock CET> <Notice> <Log Management> <srver3.domaine.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (sel
f-tuning)'> <> <> <> <1426608856985> <BEA-170019> <The server log file /servers/bipublisher/bip11/user_projects/domains/bifoundation_domain/servers/AdminServer/logs/AdminSe
rver.log is opened. All server side log events will be written to this file.>
####<17-Mar-2015 17:14:16 o'clock CET> <Info> <Log Management> <srver3.domaine.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-
tuning)'> <> <> <> <1426608856998> <BEA-170023> <The Server Logging is initialized with Java Logging API implementation.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Diagnostics> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Defaul
t (self-tuning)'> <<WLS Kernel>> <> <> <1426608857142> <BEA-320001> <The ServerDebug service initialized successfully.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
lf-tuning)'> <<WLS Kernel>> <> <> <1426608857307> <BEA-002622> <The protocol "t3" is now configured.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
lf-tuning)'> <<WLS Kernel>> <> <> <1426608857308> <BEA-002622> <The protocol "t3s" is now configured.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
lf-tuning)'> <<WLS Kernel>> <> <> <1426608857309> <BEA-002622> <The protocol "http" is now configured.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
lf-tuning)'> <<WLS Kernel>> <> <> <1426608857309> <BEA-002622> <The protocol "https" is now configured.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
lf-tuning)'> <<WLS Kernel>> <> <> <1426608857311> <BEA-002622> <The protocol "iiop" is now configured.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
lf-tuning)'> <<WLS Kernel>> <> <> <1426608857313> <BEA-002622> <The protocol "iiops" is now configured.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
lf-tuning)'> <<WLS Kernel>> <> <> <1426608857314> <BEA-002622> <The protocol "ldap" is now configured.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
lf-tuning)'> <<WLS Kernel>> <> <> <1426608857316> <BEA-002622> <The protocol "ldaps" is now configured.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
lf-tuning)'> <<WLS Kernel>> <> <> <1426608857323> <BEA-002622> <The protocol "cluster" is now configured.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
lf-tuning)'> <<WLS Kernel>> <> <> <1426608857324> <BEA-002622> <The protocol "clusters" is now configured.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
lf-tuning)'> <<WLS Kernel>> <> <> <1426608857333> <BEA-002622> <The protocol "snmp" is now configured.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
lf-tuning)'> <<WLS Kernel>> <> <> <1426608857333> <BEA-002622> <The protocol "admin" is now configured.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
lf-tuning)'> <<WLS Kernel>> <> <> <1426608857334> <BEA-002624> <The administration protocol is "t3s" and is now configured.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <RJVM> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self
-tuning)'> <<WLS Kernel>> <> <> <1426608857380> <BEA-000570> <Network Configuration for Channel "AdminServer"
Listen Address :7001
Public Address N/A
Http Enabled true
Tunneling Enabled false
Outbound Enabled false
Admin Traffic Enabled true>
#####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1426608857449> <BEA-002609> <Channel Service initialized.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Socket> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1426608857487> <BEA-000415> <System has file descriptor limits of - soft: 4,096, hard: 4,096>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Socket> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1426608857488> <BEA-000416> <Using effective file descriptor limit of: 4,096 open sockets/files.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Socket> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1426608857489> <BEA-000406> <PosixSocketMuxer was built on Apr 24 2007 16:05:00>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Socket> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1426608857518> <BEA-000436> <Allocating 4 reader threads.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Socket> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1426608857521> <BEA-000446> <Native IO Enabled.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <IIOP> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1426608857866> <BEA-002014> <IIOP subsystem enabled.>
####<17-Mar-2015 17:14:22 o'clock CET> <Error> <Security> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1426608862432> <BEA-090892> <The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException>
####<17-Mar-2015 17:14:22 o'clock CET> <Critical> <WebLogicServer> <srver3.domaine.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1426608862434> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException
weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1398)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: oracle.security.jps.JpsRuntimeException: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:170)
at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:383)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1339)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: oracle.security.jps.JpsException: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException
Caused By: oracle.security.jps.JpsException: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException
at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPDPService(PolicyUtil.java:2984)
at oracle.security.jps.internal.policystore.PolicyUtil.getPDPService(PolicyUtil.java:3226)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:167)
at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:383)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1339)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: oracle.security.jps.service.credstore.CredStoreException: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException
at oracle.security.jps.internal.credstore.ssp.CsfWalletManager.openWallet(CsfWalletManager.java:184)
at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.doInit(SspCredentialStore.java:358)
at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.<init>(SspCredentialStore.java:176)
at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.<init>(SspCredentialStore.java:160)
at oracle.security.jps.internal.credstore.ssp.SspCredentialStoreProvider.getInstance(SspCredentialStoreProvider.java:118)
at oracle.security.jps.internal.credstore.ssp.SspCredentialStoreProvider.getInstance(SspCredentialStoreProvider.java:56)
at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.findServiceInstance(ContextFactoryImpl.java:139)
at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:170)
at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:191)
at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:132)
at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:127)
at oracle.security.jps.internal.policystore.PolicyUtil$3.run(PolicyUtil.java:2956)
at oracle.security.jps.internal.policystore.PolicyUtil$3.run(PolicyUtil.java:2950)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPDPService(PolicyUtil.java:2950)
at oracle.security.jps.internal.policystore.PolicyUtil.getPDPService(PolicyUtil.java:3226)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:167)
at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:383)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1339)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<17-Mar-2015 17:14:22 o'clock CET> <Notice> <WebLogicServer> <srver3.domaine.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1426608862461> <BEA-000365> <Server state changed to FAILED>
####<17-Mar-2015 17:14:22 o'clock CET> <Error> <WebLogicServer> <srver3.domaine.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1426608862461> <BEA-000383> <A critical service failed. The server will shut itself down>
####<17-Mar-2015 17:14:22 o'clock CET> <Notice> <WebLogicServer> <srver3.domaine.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1426608862462> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<17-Mar-2015 17:14:22 o'clock CET> <Info> <WebLoHello Djam,
Please review the following:
The FMW WebLogic Server (WLS) installation has been configured to use a non-default Java temporary files directory,
i.e. the following has been set in the WebLogic startup or setDomainEnv.sh script:
EXTRA_JAVA_PROPERTIES="-Djava.io.tmpdir=/appl/oracle/temp_java_files ${EXTRA_JAVA_PROPERTIES}"
Reference: How to Change the WebLogic Server Location for Temporary Files (Doc ID 1336002.1)
When the Middleware home was restored the directory specified by java.io.tmpdir parameter was missing,
Therefore an IOException occurred when opening the wallet and WLS was unable to initialize the OPSS successfully.
To resolve the issue re-create the directory specified by the java.io.tmp dir parameter, and make sure the owner and group access are the same as for the FMW installation.
Unable Start AdminServer: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException (Doc ID 1923395.1)
Bogdan -
OBIEE hosting on WebLogic - Admin Server vs. Managed Server
What is the difference between the two possible configurations of WebLogic: Admin Server and Managed Server?
I need to identify which one is adequate to host OBIEE Presentation Services.http://download.oracle.com/docs/cd/E14571_01/web.1111/e13716/understand_domains.htm#DOMCF115
What Is a Domain?
+An Oracle WebLogic Server administration domain is a logically related group of Oracle WebLogic Server resources. Domains include a special Oracle WebLogic Server instance called the Administration Server, which is the central point from which you configure and manage all resources in the domain. Usually, you configure a domain to include additional Oracle WebLogic Server instances called Managed Servers. You deploy Web applications, EJBs, Web Services, and other resources onto the Managed Servers and use the Administration Server for configuration and management purposes only.+
I added the emphasis on "usually". You will always have exactly one administration server for a domain. That administration server can host other applications, it's simply a question of whether or not it's a good idea to do it. If you need to scale-up your application at a later time so that more than one server would be required - deploying your application to managed servers makes this very easy as you can just add managed servers. Typically other Oracle products in Fusion Middleware have domain templates and other installer / configuration options that default to deploying their infrastructure to managed servers. Sometimes in development / resource-constrained environments people override those defaults and try and run everything on a single Admin Server. It's usually possible, but may not be the most flexible going forward. -
Setting up an admin server (win) + a managed server (linux)
I am trying to set up the following domain on weblogic 8.1 SP2:
1. An administration server (+workshop) on my local Windows box
2. A managed server running on a red hat enterprise box, that connects to the
administration server on my windows box.
I've not been able to find any documentation on this, and the installation process
is far from intuitive.
Can someone help me with a step-by-step guide? I'm not trying to do anything fancy
here ;-) Thanks!Resolution found:
Went through the config.xml file. Found that in the server tag the listen address
for the server and managed server is not there. Entered the Corresponding listen
address for both Admin and Managed server
"Henrik Pettersen" <[email protected]> wrote:
>
>
>
Thank you for the information. Just what I needed. But I am now encountering
another
problem when I try to startManagedWebLogic:
<03-Jun-2004 16:48:03 o'clock BST> <Info> <Configuration Management>
<BEA-150015>
<Connecting to the administration server http://banana:7001 to retrieve
the initial
configuration.>
<03-Jun-2004 16:48:06 o'clock BST> <Notice> <Log Management> <BEA-170019>
<The
server log file /usr/local/bea/user_projects/domains/domain/managed/managed.log
is opened. All server side log events will be written to this file.>
<03-Jun-2004 16:48:06 o'clock BST> <Emergency> <Configuration Management>
<BEA-150011>
<There was an attempt to start a managed server ( null:7001 ) using the
same address
as the admin server ( banana:7001 ).>
<03-Jun-2004 16:48:06 o'clock BST> <Emergency> <WebLogicServer> <BEA-000342>
<Unable
to initialize the server: weblogic.management.configuration.ConfigurationException:
[Configuration Management:150011]There was an attempt to start a managed
server
( null:7001 ) using the same address as the admin server ( banana:7001
).>
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.management.configuration.ConfigurationException:
[Configuration
Management:150011]There was an attempt to start a managed server ( null:7001
using the same address as the admin server ( banana:7001 ).'
Reason: weblogic.management.configuration.ConfigurationException: [Configuration
Management:150011]There was an attempt to start a managed server ( null:7001
using the same address as the admin server ( banana:7001 ).
I am trying to run Weblogic 8.1 Portal Domain on Red Hat Enterprise 3.
The Linux config file is attached. Any clues would be most appreciated.
Thank you for your help.
Henrik
"Michael Zanchelli" <[email protected]> wrote:
Involving multiple machines obviously adds some complexity but for a
development
environment that you describe, you'll want to use the ConfigurationWizard
to
create domains (with the same name) on both machines. On the admin server
machine,
use the Custom path in Config Wiz to add the managed server, and onthe
managed
server machine, you can use Express mode. Start the admin server, then
use startManagedWeblogic
on the managed server machine, specifying the managed server name and
admin url
as command line args.
In a production environment, you'll likely use node manager to start
managed servers
and a domain does not need to be created on the managed server machine
in that
case.
edocs has lots of good overview information and details on using Config
Wiz.
"Henrik" <[email protected]> wrote:
I am trying to set up the following domain on weblogic 8.1 SP2:
1. An administration server (+workshop) on my local Windows box
2. A managed server running on a red hat enterprise box, that connects
to the
administration server on my windows box.
I've not been able to find any documentation on this, and the installation
process
is far from intuitive.
Can someone help me with a step-by-step guide? I'm not trying to doanything
fancy
here ;-) Thanks! -
When I go to Central Admin > Upgrade and Migration > Manage Databases Upgrade Status, I have 2 content databases which have the status:
Database is up to date, but some sites are not completely upgraded.
How can I determine which sites are not completely upgraded?Manage Databases Upgrade Status will provide you all active and offline DB details, you can get same result
using below PowerShell cmdlet.
Get-SPDatabase and Get-SPContentDatabase will provide all active database/Content DB in Farm which include Service application db, central admin DB.
Get-SPDatabase | Format-Table Name, ID
Coming back to your question, if you find that there are some site are not completely upgraded then run below command and understand the cause if issue on specific DB.
Test-SPContentDatabase WSS_ContentDB_Name
If you find any missing file issue in DB then resolve these issue to upgrade content database.
(verify all customizations referenced within the content database are also installed in the web application. This cmdlet can be issued
against a content database currently attached to the farm, or a content database that is not connected to the farm )
Use the Upgrade-SPContentDatabase cmdlet
to resume a failed database upgrade or begin a build-to-build database upgrade against a SharePoint content database
Upgrade-SPContentDatabase WSS_Content
reference:
http://technet.microsoft.com/en-us/library/ff607813(v=office.15).aspx
http://technet.microsoft.com/en-us/library/ff607941(v=office.15).aspx
If my contribution helps you, please click Mark As Answer on that post and
Vote as Helpful
Thanks, ShankarSingh(MCP) -
Is it possible to Run VM Server and VM Manager on a single machine
Hi,
I'm trying to learn VM and I downloaded both the VM Server and Manager from E-Delivery. The guide says I need two separate machines for the VM server and VM manager.
Does this mean I've to install the VM Server first and then Install VM Manager on a different machine, create the Virtual Machines and then run the Virtual Machines on the VM Server?
If I've got only one laptop, does that mean I've to install the Enterprise Linux first, install the VM Manager, create all the VM Machines I'll need from the Installation sources, then install the VM Server on the machine a fresh and run the created VM Machines on it?
I'm relatively new to Virtualization and any help would be highly appreciated.
dulaThere are other messages about running OVMM in the first VM on an OVM Server.
Yes, Oracle supports them both being on the same physical system. They even supply a template for it.
I tried to install it yesterday, but hit a resource snag. The testbed system I have available only has 2GB of memory and the OVMM template installation script aborts if the OVM Server does not have more than 2GB of memory. So my experiments for a faster DR process will have to wait for better hardware. -
Dynamically adding and removing managed servers
Hi,
I'm experimenting with adding and removing managed servers while applications are running on the cluster. I've written some scripts using weblogic.Admin to do the tasks. It seems that it's working. However, I'd like to confirm that this is supported. I also have the following questions:
1. Applications running on a cluster are automatically deployed to the newly configured managed server once it is started using startManagedWebLogic.sh. Are there any non-error situations that applications are not started automatically?
2. To remove a managed server from the cluster, I first shutdown the server gracefully and then delete the server from the domain using weblogic.Admin. Is this the recommended way to do it?
3. Anything else I need to pay attention to before adding and removing servers?
Thanks for any information and pointers.
Ming1. only if the staging mode is external.
2. yes, if the server should be permanently removed. If the server is down for short maintenance, you do not need to remove it from the cluster.
3. yes, try to avoid doing this during deployment tasks. That can be nasty.
- Anders M.
Maybe you are looking for
-
SCCM 2012 R2 - Reporting Services question
In testing SCCM 2012, I put it on a an existing remote SQL instance. This server also housed SCOM among other applications. I set up reporting services successfully and got reports working. A few months later I decided to setup and test reporting in
-
Firefox is very slow opening. Web pages load slowly. When I go to images in a Google search, the pictures take a long time to load, and when I click on an image, then the back arrow, the loading time for the previous page is very slow. When I print a
-
Airplay not detected in windows 7 itunes.
Airplay not detected on windows itunes even after windows update. Security & windows firewall not an issue. Please assist in re-installing the airplay option in my windows 7 itunes.
-
Regarding selection screens in alv.
Hi experts, SELECTION-SCREEN COMMENT 01(31) text-026 for field rastbis1. what is meant by this statement, and what is meant by 01(31) after comment.
-
Need Patchset but do not have metalink account
I install oracle for practice at home after dowloading and buying components from oracle. Can I get the patsets some other way. I need the patchset for Oracle Clinical. I heard patset 3 was the latest.