WebLogic 10.0MP1 mBean managed Server restart required?

Is there somewhere an mBean that is true with indicator (or similar) when a change is made in the console (or through WLST) which requires a restart? I have searched the tree via WLST in my field and can't seem to find anything that gives me these data. I'm thinking there must be something since when an attribute such as "Turn the logfile at startup" is changed, restart is required and is stated as such in the WLS console.

Basically, what I'm trying to do is include in my script, a way to test if a reboot is required for all servers that are managed in the field, once the script 'edit domain' is executed. If reboot is required, the script will perform restart.

Appreciate the help and advice, if it's there.

Thank you
Todd

Hello.

The 'need to restart the server' is handful of wlst like this: http://edocs.bea.com/wls/docs100/config_scripting/config_WLS.html#wp1029452

"In addition: http://download-llnw.oracle.com/docs/cd/E13222_01/wls/docs92/config_scripting/reference.html#wp1153965 but I still don ' t know if an MBean is changed with this attribute, in any case, it might be sufficient for you the script I think.

Kind regards.

Aurélien.

Published by: Aurélien on 30 Jul DEHAY. 2009 09:25

Tags: Fusion Middleware

Similar Questions

How to configure WebLogic Admin Server and the managed server
Hello

I work to configure a Weblogic admin and the managed server, but fail.
Can I know the correct steps for the installation system?

TX.
Good. It might be a good idea to mark this question as answered, then.

Managed Server failed with error libOvd

Dear Experts,
I have cluster with 6 Managed server environment configured in Machine 3. Machine has Admin and 2 Managed Server, Machine B has 2 Managed Server and Machine 3 has 2 Managed server. Recently, I have restarted all the managed server. The server managed on computer A another start that all servers are STATE of shows like "FAILED_NOT_REACHABLE". After that, I refer to the journal it shows the message below

Log file:
" The Managed server fails to start with this error: "JPS-02592: item"PoolCleanupinterval"could not send ldap configuration data to libOvd for the instance of service 'identity.ldap' in the context of JPS '..." "" not planned "
The managed server fails to start with this error: "JPS-02592: failed to chase ldap config data to libOvd for instance 'identity.ldap' service in the context of JPS '..." "element" maxPoolConnectionIdleTime' does not wait
For this issue, I refer doc oracle (Doc ID 1999999.1) . but this doc not provide patch for OAM managed server for custom weblogic. I recently installed 11g Oracle HTTP Server in the path of Middleware in the Admin of Machine (Machine A)
Is this Cause Oracle HTTP Server problem? If it means, but I installed the HTTP server on the Server Admin not on Machine B and C, because the server could not start Machine B and C.
Is this bug?. Can I use this patch for the normal weblogic instead of OAM managed server
Note: I have weblogic version 10.3.6.
This cause a major problem. Please give suggestions.
Kind regards
Ove.

Hi Florent.

My hypothesis is correct. After that I installed webtier on Machine A (Server Admin), it changes some files in the Ovdlib in the House of Middleware does level not the domain level. If the Remote Machine B and C of the Machine does not have this change so that the servers in the remote computer does not start. After that I installed the webtier on machine B and C changes that happened in the Machine B and C.Then servers managed in the Machine B and C are started... Thanks for your help;

Kind regards

Ove.

Provide read permissions to others for the weblogic/Managed Server log files

Hello
We want to give read access to others under linux for all the oracle weblogic logs including the journal .out file.
We put 022 startweblogic.sh file. Set-aside are the output
----
-rw - r - r-. 1 oracle oinstall 81586 Apr 15 22:43 access.log
-rw - r - r-. 1 oracle oinstall 700087 Apr 15 22:45 DEV_Managed.log
-rw - r-. 1 oracle oinstall 20553 Apr 15 22:49 DEV_Managed.out
----
The only concern is its setting read other for access.log and DEV_Maanged.log but not for the log file of DEV_Managed.out
Please suggest what file to edit.
Thank you
Mireille

Hello

Try to also change the umask 022 startNodeManager.sh file, and then restart nodemanager, then the managed server (to rotate the log .out file and create a new using the new umask)

Kind regards

White

Nodemanager does not restart managed server after reboot of the Linux operating system
Running Linux 2.6.18, Sun JDK 1.6.0_14 and WebLogic 10.3, we have a functioning correctly nodemanager watch a single managed server. If I kill-9, the managed server, the nodemanager immediately triggers a new. If, however, restart us the box, the nodemanager will start cleanly and does not start the managed server. He seems to believe the node should be kept low and indicates its status UNKNOWN.

I saw where is a problem known on Windows boxes, easily worked around by providing the Xrs setting - for the start settings for the managed server. (Section 5 of the config doc General nodemanager.) I do not, however, where there a just as clean solution for Linux.

Things I've tried:
+ When I put the server for DEBUGGING, it shows no sign of a stop signal is received. It is dumping loads of cluster messages, etc., in the newspaper and then suddenly just log ends so he is going to die by kill-9. If the nodemanager works at this time, he might try to restart the managed server and save it somewhere as failed permanently.
+ The nodemanager saves only the INFO level and connects to evidence to decide to leave the node down. (DEBUGGING is an invalid LogLevel, so that's all I have.)
+ A signal to restart sent our AdminServer (on another Linux machine) begins the node managed through the nodemanager. Nothing unusual happens or is connected.

I'm curious to see things:
+ Is it possible to see what state the nodemanager believes the managed server to be?
+ Is there some value in some doc somewhere who could tell that the server does not have to be restarted?
+ Y at - it is not an action of customer NodeManager log? I see nothing in domain.log or AdminServer.log except when the NM is down.

Thank you

Kevin

ListenPort = 5556
ListenBacklog = 50
SecureListener = true
AuthenticationEnabled = true
NativeVersionEnabled = false
CrashRecoveryEnabled = true
JavaHome = / appl/java/jre
StartScriptEnabled = false
StopScriptEnabled = false
StartScriptName = startWebLogic.sh
StopScriptName =
LogFile=/appl/bea/wlserver_10.3/common/nodemanager/logs/nodemanager.log
LogLevel = INFO
LogLimit = 0
LogCount = 1
You can set NativeVersionEnabled to true. We have faced this in windows that was corrected by changing this property. A few notes on this program:

Faced with this interesting question in Windows 2008 environment. Managed servers were lit by the Manager of knots and it was expected that a reboot of the system after a crash, the node Manager will restore the State of the managed servers in the State it was before the accident. Node Manager is configured to run as a windows service. As a result, he started after server restart. But individual managed servers were not start-up. Interestingly, for managed servers started by the Manager of the nodes there no .lck file in the folder/data / NodeManger.

To resolve this problem always, set the following properties in the nodemanager.properties on the base of node maager directory.

CrashRecoveryEnabled = true / * this default is set to false. This must be enabled for an automatic restart after accident at work * /.

NativeVersionEnabled = true / * this is by default set to true, and it must be configured as such. If disable you this option on platforms for which weblogic provide JNI native libraries (for example in Windows 2008) then this custom create the .lck file and so node Manager cannot restart the server managed after the crash.

Note: According to the documentation official .lck files are necessary for managers to auto restart weblogic node after system crash

Official documentation:

Once the system is restarted, Node Manager checks each managed domain specified in the nodemanager.domains file to determine if there are server instances were not stopped. This is determined by the presence of all the lock files that are created by Node Manager when a WebLogic Server process is created. This lock file contains the process identifier for the WebLogic Server startup script. If the lock file exists, but the process ID is not running, Node Manager will attempt to automatically restart the server.

If the process is running, Node Manager performs an additional check to access the management running servlet in the process to verify that the process corresponding to the process ID is a WebLogic Server instance.

Once the system is restarted, Node Manager checks each managed domain specified in the nodemanager.domains file to determine if there are server instances were not stopped. This is determined by the presence of all the lock files that are created by Node Manager when a WebLogic Server process is created. This lock file contains the process identifier for the WebLogic Server startup script. If the lock file exists, but the process ID is not running, Node Manager will attempt to automatically restart the server. If the process is running, Node Manager performs an additional check to access the management running servlet in the process to verify that the process corresponding to the process ID is a WebLogic Server instance.

*/

Deploying ADF application to a managed server in weblogic - security ADF error
Hello

Our group wrote an ADF web application, we are trying to deploy on a weblogic managed server. So far, we have succumbed. The application deploys successfully to the AdminServer. Our facility:

WebLogic version is 10.3.0. Domain name is adf_domain. We installed the ADF (ADF version is 11.1.1.0.0), JSTL (1.2.0.1), and the JSF (1.2.7.1) runtime libraries and they are addressing both the server administrator AND managed server called CollabServer. This server communicates with node Manager and you will be able to be started and the console of administration successfully. The AdminServer is on 7101 port, and the CollabServer is on port 7104. We do not use SSL.

application.XML:

<? XML version = "1.0" encoding = "windows-1252"? >
< application xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance".
xsi: schemaLocation = "http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd".
version = '5' xmlns = "http://java.sun.com/xml/ns/javaee" >
< display name > OracleRetailCollaboration < / display-name >
<>module
< web >
< web - uri > orc.war < / web - uri >
ORC < context root > < / root context >
< / web >
< / module >
< / application >

WebLogic - application.XML (as taken from the ear file):

<? XML version = "1.0" encoding = "windows-1252"? >
< application weblogic xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance" xsi: schemaLocation = "http://www.bea.com/ns/weblogic/weblogic-application.xsd" xmln
s = "http://www.bea.com/ns/weblogic/weblogic-application" >
<>earpiece
oracle.security.jps.wls.listeners.JpsApplicationLifecycleListener <-listener class > < / listener class >
< / earphone >
< library-ref >
< name of the library - > adf.oracle.domain < / library name >
< / library-ref >
< / weblogic application >

WebLogic.XML (as taken from the file. War):

<? XML version = "1.0" encoding = "UTF - 8"? >
< weblogic-web-app xmlns = "http://www.bea.com/ns/weblogic/weblogic-web-app" xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance" xsi: schemaLocation = "work".
w.bea.com/NS/WebLogic/WebLogic-Web-App http://www.bea.com/ns/weblogic/weblogic-web-app/1.0/weblogic-web-app.xsd ' > '.

<>container-descriptor
< prefer-web-inf-classes > true < / prefer-web-inf-classes >
< / container-descriptor >
< security-role-assignment >
valid users - < role name > < / role name >
users of < SPN > < / main-name >
< / security role assignment >
< library-ref >
< name of the library - > jstl < / library name >
specification of the < version > 1.2 < / specification-version >
< / library-ref >
< library-ref >
JSF < library name > - < / library name >
specification of the < version > 1.2 < / specification-version >
< / library-ref >

< / weblogic-web-app >

As I said, there is no deployment errors when deploying on the management server. However, we still see the following errors when deploying to the managed server:

java.lang.ClassNotFoundException: oracle.security.jps.wls.listeners.JpsApplicationLifecycleListener
etc.

This error occurs when the deployment using the < wldeploy > Ant task included with weblogic and the deployment of the application manually using the administration console.

So I removed this WebLogic - application.xml:

<>earpiece
oracle.security.jps.wls.listeners.JpsApplicationLifecycleListener <-listener class > < / listener class >
< / earphone >

Who decided the initial error (I guess that there is some sort of bug that causes of workaround is necessary). The following error is the following:

java.lang.ClassNotFoundException: oracle.adf.share.security.authentication.AuthenticationServlet

Yet once, we do not get this error when deploying to the AdminServer - ONLY the managed server CollabServer.

Web.XML:

...
< servlet >
< name servlet - > adfAuthentication < / servlet-name >
> the servlet class < oracle.adf.share.security.authentication.AuthenticationServlet < / servlet-class >
< load-on-startup > 1 < / load-on-startup >
< / servlet >
...
< servlet-mapping >
< name servlet - > adfAuthentication < / servlet-name >
< url-pattern > /adfAuthentication / * < / url-pattern >
< / servlet-mapping >
...

I then added some jars of adf the ear file, finally get this error message:

java.lang.ClassNotFoundException: oracle.adf.share.jsp.ADFLibUtils

Any ideas on how to solve this problem? Thank you.

Published by: user10451099 on April 15, 2009 12:10
Dan,
Thanks for remind me :-)

Here are the steps we had to take to get a WLS managed to run an adf application without copying any jar in the field/lib directory:

1. you should always install the adf runtime to any server you want the adf application to deploy on

2. open the administration console, select the managed server and select the "start server" tab in the settings of trial.

3. Add
```
/u01/bea/patch_wls1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/u01/bea/patch_jdev1111/profiles/default/sys_manifest_classpath/weblogic_patch.jar:
/u01/bea/patch_cie660/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/u01/bea/jrockit_160_05/lib/tools.jar:/u01/bea/wlserver_103/server/lib/weblogic_sp.jar:
/u01/bea/wlserver_103/server/lib/weblogic.jar:/u01/bea/modules/features/weblogic.server.modules_10.3.0.0.jar:/u01/bea/wlserver_103/server/lib/webservices.jar:
/u01/bea/modules/org.apache.ant_1.6.5/lib/ant-all.jar:/u01/bea/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar:/u01/bea/jdeveloper/modules/features/adf.share_11.1.1.jar:
/u01/bea/wlserver_103/common/eval/pointbase/lib/pbclient57.jar:/u01/bea/wlserver_103/server/lib/xqrl.jar:
/u01/bea/patch_wls1030/profiles/default/sysext_manifest_classpath/weblogic_ext_patch.jar
```
the classpath box, you need to change ' / u01/bea /' with your bea home. The classpath must be on a single line without CR/LF, I put in to make it readable.

4. Add
```
-Xms256m -Xmx512m -da -Dplatform.home=/u01/bea/wlserver_103 -Dwls.home=/u01/bea/wlserver_103/server -Dweblogic.home=/u01/bea/wlserver_103/server
-Ddomain.home=/u01/bea/user_projects/domains/naa_qs -Doracle.home=/u01/bea/jdeveloper -Doracle.security.jps.config=/u01/bea/user_projects/domains/naa_qs/config/oracle/jps-config.xml
-Doracle.dms.context=OFF -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.management.discover=false -Dweblogic.management.server=http://localhost:7001
-Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=
-Dweblogic.ext.dirs=/u01/bea/patch_wls1030/profiles/default/sysext_manifest_classpath:/u01/bea/patch_jdev1111/profiles/default/sysext_manifest_classpath:/u01/bea/patch_cie660/profiles/default/sysext_manifest_classpath
-Dweblogic.management.username=weblogic -Dweblogic.management.password=******** -Dweblogic.Name=GESTIS_QS
-Djava.security.policy=/u01/bea/wlserver_103/server/lib/weblogic.policy
```
editing area of the "Arguments". As with the change of calsspath ' / u01/bea ' your home BEA and change the domain name (in our case "naa_qs") to your domain name. change the managementuser and the password to your needs. As whith the classpath I put a CR/LF in the section of code to make it readable.

5. save the changes and restart the server

Essentially, all that we have copied the arguments of the admin server start script and more to add the path of the class.

Timo

Advanced Web services addition of Weblogic for JAX - WS extending resources to new managed server

If we add a server managed additional to a weblogic domain that has been configured to support Web Services Advanced to Weblogic for the Extensions of JAX - WS in the creation of the domain, what is the right method to add the resources to the new managed server? All of these objects are created automatically when the wls_webservice_jaxws.jar is selected in the creation of the field. However, it is not possible to reuse the model to add resources to a newly added managed server.
We tried to use the wls_webservice_complete_update_utils.py to create these objects, but when this script is pointing to a single server, it seems that to create the JaxWsSafAgent and no other resource is created for the new managed server.

in the event of possible it helps someone who may have the same question, I got, I developed the following wlst script to add and configure the resources of JAX - WS Adv Svcs for a managed server newly added to an area that already has the support of the service.

###############################################################################

# Oracle documentation:

# Configure a JMS server, service agent of Store-and-forward (SAF) and store persistent on each WebLogic Server.

# In a cluster, each to a target (not the server) local migratable target.

# Host server 'default migratable target' is sufficient in most cases.

# Target JMS modules to a cluster (or single server if not not using a clustered environment).

# Create exactly a subdeployment by module.

# and fill the subdeployment with JMS servers applicable or SAF agents only, not servers.

# Target JMS destinations the subdeployment (called Advanced Targeting in the Administration Console).

# JMS destinations do not use by default the targeting option.

# The following variables are used in the table:

server_designator # specifies an ID that is generated automatically by the configuration infrastructure.

# In general, this ID is in the format auto_number.

# uniqueID specifies a unique digital ID that is generated automatically by the configuration infrastructure.

# In General, this ID is a numeric value, for example 1234.

# servername specifies the name specified by the user to the server.

# http://docs.oracle.com/cd/E23943_01/web.1111/e13758/setenv.htm#CACJHIJD

# RESOURCE NAME                                                                                                                                                                         RESOURCE TYPE

# WseeJaxwsJmsModule                                                                                                                                             JMS Module

# File WseeJaxwsFileStore_server_designator storage

# WseeJaxwsJmsServer_server_designator JMS server

# WseeJaxwsJmsServeruniqueID JMS Subdeployment

# Manager weblogic.wsee.jaxws.mdb.DispatchPolicy of work

# Service ReliableWseeJaxwsSAFAgent_server_name SAF agent

# Queue JMS WseeBufferedRequestQueue_server_designator

# Queue JMS WseeBufferedRequestErrorQueue_server_designator

# Queue JMS WseeBufferedResponseQueue_server_designator

# Queue JMS WseeBufferedResponseErrorQueue_server_designator

# WseeStore                                                                                                                                                                                      Logical store

import sys

import random

# import os

def main():

Connect ("weblogic', ' password ',' t3: / / hostname:8001")

domainType = "osb".

# change the index value to coincide with the index number of the managed server

# that needs resources, for example osb_server3 or wls_server3 would be all two use index = 3

# osb_server4 would need to index = 4, etc.

index = 3

managedServerName = domainType + '_server %s' % index

print ' managedServerName is: "+ managedServerName

print (' check if server ' + managedServerName + "exists...")

CD ('/Servers')

Server = ls('c')

If (servers.find (managedServerName)! = - 1):

Print ('Server' + managedServerName + "exists...")

# Get the Configuration Manager and check for existing session

cfgManager = getConfigManager()

Try:

cfgManager.getChanges)

Print ("failed to open an editing session. Please clear any open the locks on the configuration. ")

Print ("Please investigate the lock and try again the script. Script output. ")

Disconnect()

Exit()

except:

Edit()

startEdit()

Print ("creation WseeStore LogicalStore...")

createLogicalStore (managedServerName, 1).

Print ("WseeStore LogicalStore...")

Print ('creating JMS resources and configuration UDQs...')

createJMSResources (managedServerName, index)

print ("resources created JMS and configured UDQs... »)

Print ("activate changes...")

Activate()

Print ("enabled... changes")

print ("disconnection of AdminServer...")

Disconnect()

Print ("disconnected from AdminServer...")

Print ("Script completed successfully. Please check the changes you made. ")

Exit()

Another thing:

There are 0 =

print (managedServerName + "does not exist in this area.) Script will now stop. »)

Disconnect()

Exit()

def createLogicalStore (managedServerName, setAsDefault):

CD ('/ servers /' + managedServerName + ' / WebService /' + managedServerName + ' / WebServicePersistence /' + managedServerName + ' / ' WebServiceLogicalStores)

logicalStores = ls('c')

If (logicalStores.find ('WseeStore')! = - 1):

Print ("ERROR: LogicalStore WseeStore exist already for ' + managedServerName")

Print ("Please study. Script output. ")

cancelEdit('y')

Disconnect()

Exit()

Another thing:

CD ('/ servers /' + managedServerName + ' / WebService /' + managedServerName + ' / WebServicePersistence /' + managedServerName)

cmo.createWebServiceLogicalStore ('WseeStore')

CD ('/ servers /' + managedServerName + ' / WebService /' + managedServerName + ' / WebServicePersistence /' + managedServerName + ' / WebServiceLogicalStores/WseeStore ')

cmo.setPersistenceStrategy ('LOCAL_ACCESS_ONLY')

cmo.setRequestBufferingQueueJndiName ('weblogic.wsee.BufferedRequestQueue')

cmo.setResponseBufferingQueueJndiName ('weblogic.wsee.BufferedResponseQueue')

If setAsDefault == 1:

CD ('/ servers /' + managedServerName + ' / WebService /' + managedServerName + ' / WebServicePersistence /' + managedServerName)

cmo.setDefaultLogicalStoreName ('WseeStore')

def createJMSResources (managedServerName, index):

targetServer = jarray.array ([ObjectName ('com.bea:Name =' + managedServerName + ", Type = server '")], ObjectName)

# creating persistence store for jms Server

# NOTE: you will need to create the physical folder for the storage of files

print ('* FileStore creation ')

filestore_list = ["WseeJaxwsFileStore"]

Count = 0

limit = 1

While County<>

CD ('/Deployments')

Filestore = ls('c')

Filestore = filestore_list [count] + '_auto_ %s' % index

If (fileStores.find (filestore)! = - 1):

print ("' ERROR: Filestore ' filestore + ' already exists!")

Print ("Please study. Script output. ")

cancelEdit('y')

Disconnect()

Exit()

Another thing:

print ('* adding ' + filestore)

CD('/')

cmo.createFileStore (filestore)

CD ('/ deployments /' + filestore)

cmo.setDirectory (filestore)

objectives (", target server)

print ("Filestore" + filestore + "created")

# create file storage directory, if there is no

dir = System.getenv ('DOMAIN_HOME') + ' / ' + filestore

Try:

OS.stat (dir)

except:

OS.mkdir (dir)

Count += 1

# the server jms creation

print ('* creating WseeJaxws JMS Server "")

# create server jms WseeJaxwsJmsServer_auto_x

CD ('/JMSServers')

jmsServers = ls('c')

If (jmsServers.find (' %s '% index WseeJaxwsJmsServer_auto_)! = - 1):

print ("ERROR: WseeJaxwsJmsServer_auto_ % if % index + ' already exists!")

Print ("Please study. Script output. ")

cancelEdit('y')

Disconnect()

Exit()

Another thing:

CD('/')

cmo.createJMSServer (' %s '% index WseeJaxwsJmsServer_auto_)

CD ('/ JMSServers/WseeJaxwsJmsServer_auto_ % if % index)

cmo.setPersistentStore (getMBean ('/ deployments/WseeJaxwsFileStore_auto_ % if % index))

objectives (", target server)

targetWseeJaxwsJmsServer = jarray.array ([ObjectName ('com.bea:Name = WseeJaxwsJmsServer_auto_ % be % index + ", Type = JMSServer")], ObjectName)

print (index "WseeJaxwsJmsServer_auto_ %s" % + "created")

# creating WseeJaxwsJmsModule components

print ('* create queues: index % WseeBufferedRequestQueue_auto_ % to + ', WseeBufferedRequestErrorQueue_auto_ % if % index + ', WseeBufferedResponseQueue_auto_ % if % index + ' and WseeBufferedResponseErrorQueue_auto_ % if % index)

# check if subdeployment in WseeJaxwsJmsModule

# targeted on the new JMS server already exists

CD('/JMSSystemResources/WseeJaxwsJmsModule/SubDeployments')

wseejaxwsSubs = ls ("c", returnMap = 'true')

for wseejaxwsSub in wseejaxwsSubs:

CD ('/ JMSSystemResources/WseeJaxwsJmsModule/SubDeployments /' + wseejaxwsSub + "/ target")

existingSubTargets = ls ("c", returnMap = 'true')

for existingSubTarget in existingSubTargets:

CD ('/ JMSSystemResources/WseeJaxwsJmsModule/SubDeployments /' + wseejaxwsSub + ' / objectives /' + existingSubTarget)

If (existingSubTarget == 'WseeJaxwsJmsServer_auto_ %s' % index):

print (' ERROR: SubDeployment WseeJaxwsJmsModule ' + wseejaxwsSub + ' already exists and is intended for the %s '% index WseeJaxwsJmsServer_auto_)

Print ("Please study. Script output. ")

cancelEdit('y')

Disconnect()

Exit()

# create subdeployment in WseeJaxwsJmsModule

CD('/JMSSystemResources/WseeJaxwsJmsModule')

# Number of eight random numbers to generate and convert to string

# If the subname will conform to the standard naming convention

# using numbers beginning with four to ensure it is random in existing facilities

# and try to create some level of self-documentation to coincide with the index server

uniqueID = str (random.randrange (00000000,99999900))

subName = "%s WseeJaxwsJmsServer" % index + uniqueID

cmo.createSubDeployment (subName)

print ('SubDeployment' + subName + "created")

# create queue WseeBufferedRequestQueue_auto_x

CD('/JMSSystemResources/WseeJaxwsJmsModule/JMSResource/WseeJaxwsJmsModule/Queues')

queue = ls('c')

If (queues.find (' %s '% index WseeBufferedRequestQueue_auto_)! = - 1):

print ("ERROR: WseeBufferedRequestQueue_auto_ % if % index + ' already exists!")

Print ("Please study. Script output. ")

cancelEdit('y')

Disconnect()

Exit()

Another thing:

CD('/JMSSystemResources/WseeJaxwsJmsModule/JMSResource/WseeJaxwsJmsModule')

cmo.createQueue (' %s '% index WseeBufferedRequestQueue_auto_)

CD ('/ JMSSystemResources/WseeJaxwsJmsModule/JMSResource/WseeJaxwsJmsModule/Files/WseeBufferedRequestQueue_auto_ % if % index)

cmo.setJNDIName ('weblogic.wsee.BufferedRequestQueue_auto_ % if % index)

cmo.setSubDeploymentName (subName)

CD ('/ JMSSystemResources/WseeJaxwsJmsModule/SubDeployments /' + subName)

Set ('Targets', targetWseeJaxwsJmsServer)

print (index ' WseeBufferedRequestQueue_auto_ %s "% +" created")

# create queue WseeBufferedRequestErrorQueue_auto_x

CD('/JMSSystemResources/WseeJaxwsJmsModule/JMSResource/WseeJaxwsJmsModule/Queues')

queue = ls('c')

If (queues.find (' %s '% index WseeBufferedRequestErrorQueue_auto_)! = - 1):

print ("ERROR: WseeBufferedRequestErrorQueue_auto_ % if % index + ' already exists!")

Print ("Please study. Script output. ")

cancelEdit('y')

Disconnect()

Exit()

Another thing:

CD('/JMSSystemResources/WseeJaxwsJmsModule/JMSResource/WseeJaxwsJmsModule')

cmo.createQueue (' %s '% index WseeBufferedRequestErrorQueue_auto_)

CD ('/ JMSSystemResources/WseeJaxwsJmsModule/JMSResource/WseeJaxwsJmsModule/Files/WseeBufferedRequestErrorQueue_auto_ % if % index)

cmo.setJNDIName ('weblogic.wsee.BufferedRequestErrorQueue_auto_ % if % index)

cmo.setSubDeploymentName (subName)

CD ('/ JMSSystemResources/WseeJaxwsJmsModule/SubDeployments /' + subName)

Set ('Targets', targetWseeJaxwsJmsServer)

print (index ' WseeBufferedRequestErrorQueue_auto_ %s "% +" created")

# create queue WseeBufferedResponseQueue_auto_x

CD('/JMSSystemResources/WseeJaxwsJmsModule/JMSResource/WseeJaxwsJmsModule/Queues')

queue = ls('c')

If (queues.find (' %s '% index WseeBufferedResponseQueue_auto_)! = - 1):

print ("ERROR: WseeBufferedResponseQueue_auto_ % if % index + ' already exists!")

Print ("Please study. Script output. ")

cancelEdit('y')

Disconnect()

Exit()

Another thing:

CD('/JMSSystemResources/WseeJaxwsJmsModule/JMSResource/WseeJaxwsJmsModule')

cmo.createQueue (' %s '% index WseeBufferedResponseQueue_auto_)

CD ('/ JMSSystemResources/WseeJaxwsJmsModule/JMSResource/WseeJaxwsJmsModule/Files/WseeBufferedResponseQueue_auto_ % if % index)

cmo.setJNDIName ('weblogic.wsee.BufferedResponseQueue_auto_ % if % index)

cmo.setSubDeploymentName (subName)

CD ('/ JMSSystemResources/WseeJaxwsJmsModule/SubDeployments /' + subName)

Set ('Targets', targetWseeJaxwsJmsServer)

print (index ' WseeBufferedResponseQueue_auto_ %s "% +" created")

# create queue WseeBufferedResponseErrorQueue_auto_x

CD('/JMSSystemResources/WseeJaxwsJmsModule/JMSResource/WseeJaxwsJmsModule/Queues')

queue = ls('c')

If (queues.find (' %s '% index WseeBufferedResponseErrorQueue_auto_)! = - 1):

print ("ERROR: WseeBufferedResponseErrorQueue_auto_ % if % index + ' already exists!")

Print ("Please study. Script output. ")

cancelEdit('y')

Disconnect()

Exit()

Another thing:

CD('/JMSSystemResources/WseeJaxwsJmsModule/JMSResource/WseeJaxwsJmsModule')

cmo.createQueue (' %s '% index WseeBufferedResponseErrorQueue_auto_)

CD ('/ JMSSystemResources/WseeJaxwsJmsModule/JMSResource/WseeJaxwsJmsModule/Files/WseeBufferedResponseErrorQueue_auto_ % if % index)

cmo.setJNDIName ('weblogic.wsee.BufferedResponseErrorQueue_auto_ % if % index)

cmo.setSubDeploymentName (subName)

CD ('/ JMSSystemResources/WseeJaxwsJmsModule/SubDeployments /' + subName)

Set ('Targets', targetWseeJaxwsJmsServer)

print (index ' WseeBufferedResponseErrorQueue_auto_ %s "% +" created")

print (queues "in the created WseeJaxwsJmsModule")

# try except block is sufficient to avoid any problem if these queues

# have already been added to the queues of dist WseeJaxws

# If this is the case, the following exception is thrown:

# weblogic.descriptor.BeanAlreadyExistsException: bean already exists

Try:

print ('* addition of the queues in distributed queues)

queue_list = ['WseeBufferedRequestErrorQueue', 'WseeBufferedResponseQueue', 'WseeBufferedRequestQueue', 'WseeBufferedResponseErrorQueue']

Count = 0

limit = 4

While County<>

queue = queue_list [count] + '_auto_ %s' % index

dist_queue = "dist_" + queue_list [count] + 'sent '.

print ('* added ' queue + 'to' + dist_queue)

CD ('/ JMSSystemResources/WseeJaxwsJmsModule/JMSResource/WseeJaxwsJmsModule/DistributedQueues /' + dist_queue)

cmo.createDistributedQueueMember (tail)

CD ('/ JMSSystemResources/WseeJaxwsJmsModule/JMSResource/WseeJaxwsJmsModule/DistributedQueues /' dist_queue ' / DistributedQueueMembers /' ++ queue)

cmo.setWeight (1)

Print ("queue added to UDQ")

Count += 1

except:

Print ("an exception was encountered adding JMS queues for distributed queues '")

Print ("Please study using the thread dump information provided.'")

Print ("the script will now stop.")

cancelEdit('y')

Disconnect()

lift

# create ReliableWseeJaxwsSAFAgent

Print ("Creating ReliableWseeJaxwsSAFAgent_auto_ %s" % index + '...')

CD ('/SAFAgents')

safAgents = ls('c')

If (safAgents.find (' %s '% index ReliableWseeJaxwsSAFAgent_auto_)! = - 1):

print ("ERROR: SAFAgent ReliableWseeJaxwsSAFAgent_auto_ % index %s 'exists already for' + managedServerName")

Print ("Please study. Script output. ")

cancelEdit('y')

Disconnect()

Another thing:

CD('/')

cmo.createSAFAgent (' %s '% index ReliableWseeJaxwsSAFAgent_auto_)

CD ('/ SAFAgents/ReliableWseeJaxwsSAFAgent_auto_ % if % index)

cmo.setStore (getMBean ('/ filestore/WseeJaxwsFileStore_auto_ % if % index))

Set ('Targets', TargetServer)

cmo.setServiceType ('Both')

Print ('Created ReliableWseeJaxwsSAFAgent_auto_ %s "% index)

If __name__ == "main":

main()

Cannot start WebLogic managed server
Hello

I have a domain weblogic on a physical machine with two servers (AdminServer and osb_server1 [Managed Server]). (Weblogic 10.3.6)
I started nodeManager and registered the domain by using the command nmEnroll in WLST.
I can start "AdminServer" drawn nmStart ('AdminServer') command. AdminServer start correctly.

However, when I want to start managed server (osb_server1):
1. in the WebLogic administration console, he said:
(Warning) User is not authorized to perform operations of the lifecycle on the server osb_server1.
(Warning) All selected servers are currently in a State that is not compatible with this operation or are not associated with a Node Manager running or you are not authorized to perform the requested action. No action will be taken.

2 using the startManagedWebLogic.cmd script after you have entered the name of user and password, it returns authentication denied.
22 October 2012 10:31:21 IS > < critical > < security > < BEA-090403 > < authentication user weblogic denied >
< 22 October 2012 10:31:21 IS > < critical > < WebLogicServer > < BEA-000386 > < server subsystem failed. Reason: weblogic.security.SecurityInitializationException: authentication of user weblogic has denied.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:966)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
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)
Truncated. check the log file full stacktrace
Caused by: javax.security.auth.login.FailedLoginException: [Security: 090303] authentication failed: user weblogic weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security: 090295] caught unexpected exception
at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:251)
to com.bea.common.security.internal.service.LoginModuleWrapper$ 1.run(LoginModuleWrapper.java:110)
at java.security.AccessController.doPrivileged (Native Method)
at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
Truncated. check the log file full stacktrace
>

3 using the nmStart nodeManager command, it complains boot.properties file.

I can connect AdminServer with the same account with no problem.

Best regards

Published by: ToRRaDo on October 22, 2012 17:25
Did you reboot AdminServer after deleting the LDAP authentication provider?
I think that your managed server is always try to authenticate the user via ldap authentication provider.

Logging.XML file resets after you restart the managed server
Hi all

I modified the logging.xml file because I implemented a Logger.But ADF custom after you restart the server, SOA, logging.xml file get automatically back to the unmodified state, all this means that I modified was not.

Am I missing something?

Please suggest!
Kind regards
Shah
Hi Shah
In the EPS group, usually there is a set of Configuration files are synchronized to all of AdminServer breaks the run. A simple example is like file config.xml and some files of data sources, files, ldap, etc. Whenever we reboot the Soa or bam managed servers, they go to AdminServer and obtain a copy of these files. So, if you make any changes directly on the managed server computers, then can be is getting crushed when you restart the servers. Check the timestamp of all these files. Make the changes on the side means Admin on the machine where you have AdminServer running. If all goes well, soa/bam should get these files at startup.

Thank you
Ravi Jegga

Help, please! Windows WebLogic admin server and managed server service
Hello

I have an admin server and 2 managed servers. I want to create a windows service so that my server admin and 2 managed servers start as a windows service.

I'm following the documentation at: http://weblogic-wonders.com/weblogic/2011/02/01/weblogic-as-a-windows-service/

but I have problems understanding as the documentation lacks some important points. It says that I need to create a custom startup script.

Can someone please tell me: -.

(1) I have to create 3 different with 3 different (one for the server admin) file names and 2 for managed servers?

(2) what should be the names? I've created a script with the name startAdminServer.cmd for the administrator of the server to destination = > C:\Oracle\Middleware\user_projects\domains\base_domain\config\startup but it gives me an error when I try to run the script by saying 'the file name, directory name or volume label syntax is incorrect. "

(3) is the content of the script correct admin = >

SETLOCAL

Set DomainName = Wonders_Domain

Set USERDOMAIN_HOME = C:\BEA103\user_projects\domains\Wonders_Domain

Define SERVER_NAME = AdminServer

Set WL_HOME=C:\BEA103\wlserver_10.3

Set WLS_USER = weblogic

Set WLS_PW = weblogic

Set PRODUCTION_MODE = true

MEM_ARGS =-Xms512m-Xmx512m set

Call "% WL_HOME%\server\bin\installSvc.cmd".

ENDLOCAL

(4) after I executed the script mentioned above what are my next steps? I create a similar script as the one above for example managed servers and run them individually?

(5) after I ran all 3 scripts change the installSvc.cmd file to set a delay so that the managed servers start after the server administrator? How do I do that?

I would appreciate any assistance. Please let me know if you have any questions. I tried to explain it the best possible.

Published by: user9021545 on April 26, 2011 17:26

Published by: user9021545 on April 26, 2011 17:28

Published by: user9021545 on April 26, 2011 17:28
Hello

The post below

http://WebLogic-wonders.com/WebLogic/2011/02/01/WebLogic-as-a-Windows-service/

shows how we can make the server administrator and the server run as a windows service, referring to an area of sample called 'Wonders_Domain '.

Your questions:

(* 1) I have to create 3 different with 3 different (one for the server admin) file names and 2 for managed servers? *

Rep. : Yes, the settings of the server administrator and the managed server are different then you its recommended to have scripts for each of the servers.

(* 2) what should be the names? I've created a script with the name startAdminServer.cmd for the administrator of the server to verbal-online C:\Oracle\Middleware\user_projects\domains\base_domain\config\startup but it gives me an error when I try to run the script by saying 'the file name, directory name or volume label syntax is incorrect. " *

Rep. : The name is not important. The values contained in the script should be relevant to your area of work environment.

The values in the pasted script refers to the environment of the author, replace them with your own environment settings.

You can specify the servername, DomainName, USERDOMAIN_HOME, WL_HOME according to your environment.

Please let me know if you have any other questions.

Kind regards
Julien
http://WebLogic-wonders.com/

WebLogic Managed Server Error - JavaEE agent test failed in ODI
Hi all
Please help the mind the question below!
Versions: ODI 11.1.1 and Weblogic 11g Release1 10.3.3.
Server: Windows 2003 server, 32-bit operating system.
-> able to connect the agent independent successfully.

Question: In Weblogic, the server administrator will connect without error. But when I run the managed server 'odi_server1', we found major error that occur when connecting to the master repository. Stuck under the error log.

Help, please!

# < 23 March 2011 15:58:16 IST > < error > < hats > < admin-3fqjbc1oo > < odi_server1 > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > < 1300876096336 > < BEA-149231 > < cannot create the activation state to true for the application "oraclediagent".
weblogic.application.ModuleException: [HTTP:101216] Servlet: 'AgentServlet' failed by preloading at startup in a Web application: "oraclediagent."
ODI-1404: OracleDIAgent Agent start failed: an authentication error occurred when connecting to the master repository.
at oracle.odi.runtime.agent.servlet.AgentServlet.init(AgentServlet.java:233)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
to 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:121)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
to 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:1976)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1950)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1869)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
to weblogic.application.internal.flow.ModuleStateDriver$ 3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
to weblogic.application.internal.flow.ModuleStateDriver$ 3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
to weblogic.application.internal.BaseDeployment$ 2.next(BaseDeployment.java:1267)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
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)
to weblogic.management.deploy.internal.DeploymentAdapter$ 1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
to 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:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1514)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
to weblogic.application.internal.flow.ModuleStateDriver$ 3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
to weblogic.application.internal.flow.ModuleStateDriver$ 3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
to weblogic.application.internal.BaseDeployment$ 2.next(BaseDeployment.java:1267)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
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)
to weblogic.management.deploy.internal.DeploymentAdapter$ 1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
to 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:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

Caused by: ODI-1404: Agent OracleDIAgent start failure: an authentication error occurred when connecting to the master repository.
at oracle.odi.runtime.agent.servlet.AgentServlet.init(AgentServlet.java:233)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
to 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:121)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
to 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:1976)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1950)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1869)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
to weblogic.application.internal.flow.ModuleStateDriver$ 3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
to weblogic.application.internal.flow.ModuleStateDriver$ 3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
to weblogic.application.internal.BaseDeployment$ 2.next(BaseDeployment.java:1267)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
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)
to weblogic.management.deploy.internal.DeploymentAdapter$ 1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
to 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:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Thank you
Kenny
Hi Kenny,

This error seems to indicate that the credentials that you specified to the master repo do not work. Either ensure that the work of connecting to the pension, or rerun the installation program and specify a set known good powers it.

Kind regards
Robb Salzmann

WebLogic Portal deployment in question - managed server
Hello

I have a sample file Portal ear (default value of pointbase database) which has been developed in weblogic workshop to the
development of base domain - server admin in portal weblogic 10.3. able to test page successfully picking flow.

----

Now, I created another baseTdomain mode of production, weblogic portal 10.3 domain admin server and the servers managed in a cluster.
for this baseTdomain, I am pointing to the oracle database.
Admin Server (port: 7001) and managed servers (port: 7009) begin very well without any problems.

I exported the ear of the workshop of the domain based file on my local and trying to deploy in the
managed server.

Its not to deploy and complain... The EAR file is prepared instead of an active state.

How can I copy all the information portlet from pointbase to Oracle stuff. Am I missing something here and so, no deployment happens?

< 19 August 2009 11:44:24 AM MST > < WARNING > < Server > < BEA-002637 > < could not registries
ER a listener of disconnection due to weblogic.rmi.extensions.DisconnectMonitorUna
vailableException: could not register a DisconnectListener to [weblogic.rmi.int
Iqbal. BasicRemoteRef - hostID: '-7879092007710906947S: 192.168.1.116: [7009,7009,-]
[1, -1, -1, -1, -1]: baseT_domain:ms1', oid: '31,' channel: 'null']. >

< 19 August 2009 11:58:41 AM MST > < WARNING > < hats > < BEA-149004 > < ended in failure
detected when opening to distribute task for application 'psAppEAR '. >
< 19 August 2009 11:58:41 AM MST > < error > < Console > < BEA-240003 > < Meeting Console
The following error weblogic.application.ModuleException Ed: preparation of Exception
module: EJBModule (netuix.jar)

Unable to deploy EJB: netuix.jar ProxyPagePersistenceManager:

Exception when trying to deploy Unchecked or excluded from security policy: web
logic.security.service.ResourceCreationException: weblogic.security.spi.Resource
CreationException: [Security: 090310] cannot create the resource

Thanks for your help in advance,

Thank you
Krishna.
Hello
I'm not sure if you can ignore the warnings or not. Probably, if you do not use JMS / async Web services you can.
3 Im still not sure what port you are talking about, where you specified it? do you mean port multicast? in which case it can be the same as the admin server port (the multicast address is different), but you should use unicast I think

managed server status UNKNOWN after server restart
The use of scripts to beasvc I recorded Nodemanager AdminServer and managed server Apps as windows services. I have installation service AdminServer depend on Nodemanager and Apps to depend on the service of AdminServer. Starting services all the fines at the restart, however, in console Apps State shows UNKNOWN. If I go to windows services and manually restart this service, watch then it as running. I tried to delay the service statup Apps place at 5 minutes after AdminServer but get the same results. Any ideas where the disconnection happens?

What is happening with WL 10.3, Windows Server 2003 and 2008. Let me know if I have to paste scripts or parameters. Thank you!
For 1. Select the http tunneling. There is a workaround solution.
For 2. Check if you have the ip address specified for admin serve. If it isn't, then specify one.

How to run the managed server weblogic as windows service

Hello friends,
I want a guide step by step to run the managed server and the application via the windows service.
I am able to create admin server as a windows service. I tried a lot of managed server, but not luck.
Please help me to solve it.

Hello

Here am attached the script to create a windows service for p6 service I used for my management environment.

SETLOCAL

Set DomainName = P6EPPM

Set USERDOMAIN_HOME = C:\Oracle\Middleware\user_projects\domains\P6EPPM

Define SERVER_NAME = P6

Set PRODUCTION_MODE = true

Set ADMIN_URL =http://p6eppmdev:7001

CD % USERDOMAIN_HOME %

call %USERDOMAIN_HOME%\bin\setDomainEnv.cmd

call "C:\Oracle\Middleware\wlserver_10.3\server\bin\installSvc.cmd".

ENDLOCAL

I hope it will work for you.

Try this and updated the forum.

Concerning

Kumar

WebLogic managed server passes to the State of alert
When I start the managed server, it's OK health... When I connect to n log in the administration console after a while it turns on alert... How can I see what's the caveat?
In the area of system status, you can click on the warning, and open the tree for the server that is showing the warning.

You can also click health, control tab of the server in question (environment, servers, server in question)

WebLogic 10.0MP1 mBean managed Server restart required?

Similar Questions

Maybe you are looking for