Weblogic start arguments

Hi evreybody,
Anyone can help me the rôle of these arguments in weblogic start :
-jrockit -Djava.compiler=NONE
what is the impact if i put
-jrockit -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=10092,server=y,suspend=n -Djava.compiler=NONE
instead of
-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=10092,server=y,suspend=n
many thanks of your help

1. wrong forum
2. check this: https://community.oracle.com/thread/1523053

Similar Messages

Weblogic Admin server - Configuration/Server Start/Arguments ignored?

Hi,
I'm trying to specify a http proxy for a WebLogic Admin Server in order for an application to access external resources. I've placed the settings into the "Server Configuration / Server Start / Arguments", and verified that they have been saved into the config/config.xml file for that domain:
<server-start>
<arguments>-Dhttp.proxyHost=[XXXX] -Dhttp.proxyPort=8080</arguments>
<password-encrypted>[XXXX]</password-encrypted>
</server-start>
However, no matter how I start the server, these settings are ignored despite that the documentation states these should be added to the java command line.
starting weblogic with Java version:
java version "1.6.0_19"
Java(TM) SE Runtime Environment (build 1.6.0_19-b04)
Java HotSpot(TM) 64-Bit Server VM (build 16.2-b04, mixed mode)
Starting WLS with line:
C:\PROGRA~1\Java\JDK16~1.0_1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=256m -Dweblogic.Name=AdminServer -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Xverify:none -da -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1032\profiles\default\sysext_manifest_classpath weblogic.Server
As a test I created a new managed server in the same domain, specifying the same startup properties, and they were picked up during startup.
If I manually place the settings into the bin/setDomainEnv.cmd batch file for the domain they are also picked up and work.
Is there an undocumented restriction on Admin Servers that they ignore the "Server Start / Arguments" setting, or is there something else I can check as to why this is not working?
Many thanks,
- Micha.

Umm... I already pasted the relevant snippet out of the config.xml, but following is the entire file. The startup arguments, as specified in the admin console, are:
-Dhttp.proxyHost=[XXXXXXXX] -Dhttp.proxyPort=8080
which matches what is saved in the config.xml.
<?xml version='1.0' encoding='UTF-8'?>
<domain xmlns="http://xmlns.oracle.com/weblogic/domain" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/security/xacml http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator/1.0/passwordvalidator.xsd http://xmlns.oracle.com/weblogic/domain http://xmlns.oracle.com/weblogic/1.0/domain.xsd http://xmlns.oracle.com/weblogic/security http://xmlns.oracle.com/weblogic/1.0/security.xsd http://xmlns.oracle.com/weblogic/security/wls http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.xsd">
<name>wls_starter</name>
<domain-version>10.3.2.0</domain-version>
<security-configuration>
<name>wls_starter</name>
<realm>
<sec:authentication-provider xsi:type="wls:default-authenticatorType"></sec:authentication-provider>
<sec:authentication-provider xsi:type="wls:default-identity-asserterType">
<sec:active-type>AuthenticatedUser</sec:active-type>
</sec:authentication-provider>
<sec:role-mapper xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
<sec:authorizer xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
<sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
<sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
<sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
<sec:name>myrealm</sec:name>
<sec:password-validator xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator" xsi:type="pas:system-password-validatorType">
<sec:name>SystemPasswordValidator</sec:name>
<pas:min-password-length>8</pas:min-password-length>
<pas:min-numeric-or-special-characters>1</pas:min-numeric-or-special-characters>
</sec:password-validator>
</realm>
<default-realm>myrealm</default-realm>
<credential-encrypted>[XXXXXXXXXX]</credential-encrypted>
<node-manager-username>weblogic</node-manager-username>
<node-manager-password-encrypted>[XXXXXXXX]</node-manager-password-encrypted>
</security-configuration>
<server>
<name>AdminServer</name>
<max-http-message-size>-1</max-http-message-size>
<ssl>
<enabled>false</enabled>
</ssl>
<log>
<file-name>logs/AdminServer.log</file-name>
<rotation-type>bySize</rotation-type>
<number-of-files-limited>true</number-of-files-limited>
<file-count>7</file-count>
<file-min-size>500</file-min-size>
<rotate-log-on-startup>true</rotate-log-on-startup>
<logger-severity>Trace</logger-severity>
<logger-severity-properties></logger-severity-properties>
<log-file-severity>Info</log-file-severity>
<stdout-severity>Info</stdout-severity>
<domain-log-broadcast-severity>Notice</domain-log-broadcast-severity>
<memory-buffer-severity>Debug</memory-buffer-severity>
<log4j-logging-enabled>false</log4j-logging-enabled>
<redirect-stdout-to-server-log-enabled>false</redirect-stdout-to-server-log-enabled>
<domain-log-broadcaster-buffer-size>1</domain-log-broadcaster-buffer-size>
</log>
<machine>[XXXXXXXXXX]</machine>
<listen-port>8080</listen-port>
<listen-port-enabled>true</listen-port-enabled>
<web-server>
<frontend-http-port>0</frontend-http-port>
<frontend-https-port>0</frontend-https-port>
<keep-alive-enabled>true</keep-alive-enabled>
<keep-alive-secs>30</keep-alive-secs>
<https-keep-alive-secs>60</https-keep-alive-secs>
<post-timeout-secs>30</post-timeout-secs>
<max-post-size>-1</max-post-size>
<send-server-header-enabled>false</send-server-header-enabled>
<wap-enabled>false</wap-enabled>
<accept-context-path-in-get-real-path>false</accept-context-path-in-get-real-path>
</web-server>
<listen-address></listen-address>
<java-compiler>javac</java-compiler>
<tunneling-enabled>false</tunneling-enabled>
<tunneling-client-ping-secs>45</tunneling-client-ping-secs>
<tunneling-client-timeout-secs>40</tunneling-client-timeout-secs>
<server-start>
<arguments>-Dhttp.proxyHost=[XXXXXXXX] -Dhttp.proxyPort=8080</arguments>
<password-encrypted>[XXXXXXX]</password-encrypted>
</server-start>
<server-life-cycle-timeout-val>30</server-life-cycle-timeout-val>
<startup-timeout>0</startup-timeout>
<graceful-shutdown-timeout>30</graceful-shutdown-timeout>
<ignore-sessions-during-shutdown>false</ignore-sessions-during-shutdown>
<client-cert-proxy-enabled>false</client-cert-proxy-enabled>
</server>
<embedded-ldap>
<name>wls_starter</name>
<credential-encrypted>[XXXXXXXXXX]</credential-encrypted>
</embedded-ldap>
<configuration-version>10.3.2.0</configuration-version>
<app-deployment>
<name>[XXXXXXXXXX]</name>
<target>AdminServer</target>
<module-type>ear</module-type>
<source-path>[XXXXXXXXXX]</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<app-deployment>
<name>[XXXXXXXXXX]</name>
<target>AdminServer</target>
<module-type>ear</module-type>
<source-path>[XXXXXXXXXX]</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<app-deployment>
<name>[XXXXXXXXXX]</name>
<target>AdminServer</target>
<module-type>ear</module-type>
<source-path>[XXXXXXXXXX]</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<app-deployment>
<name>[XXXXXXXXXX]</name>
<target>AdminServer</target>
<module-type>ear</module-type>
<source-path>[XXXXXXXXXX]</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<machine>
<name>[XXXXXXXXXX]</name>
</machine>
<jms-server>
<name>WseeJmsServer</name>
<target>AdminServer</target>
<persistent-store>WseeFileStore</persistent-store>
</jms-server>
<jms-server>
<name>[XXXXXXXXXX]</name>
<target>AdminServer</target>
<persistent-store>WseeFileStore</persistent-store>
</jms-server>
<self-tuning>
<work-manager>
<name>weblogic.wsee.mdb.DispatchPolicy</name>
<target>AdminServer</target>
</work-manager>
</self-tuning>
<file-store>
<name>WseeFileStore</name>
<directory>WseeFileStore</directory>
<target>AdminServer</target>
</file-store>
<jms-system-resource>
<name>WseeJmsModule</name>
<target>AdminServer</target>
<sub-deployment>
<name>BEA_JMS_MODULE_SUBDEPLOYMENT_WSEEJMSServer</name>
<target>WseeJmsServer</target>
</sub-deployment>
<descriptor-file-name>jms/wseejmsmodule-jms.xml</descriptor-file-name>
</jms-system-resource>
<jms-system-resource>
<name>[XXXXXXXXXX]</name>
<target>AdminServer</target>
<sub-deployment>
<name>[XXXXXXXXXX]</name>
<target>[XXXXXXXXXX]</target>
</sub-deployment>
<descriptor-file-name>[XXXXXXXXXX]</descriptor-file-name>
</jms-system-resource>
<admin-server-name>AdminServer</admin-server-name>
<jdbc-system-resource>
<name>[XXXXXXXXXX]</name>
<target>AdminServer</target>
<descriptor-file-name>[XXXXXXXXXX]</descriptor-file-name>
</jdbc-system-resource>
<saf-agent>
<name>ReliableWseeSAFAgent</name>
<target>AdminServer</target>
<store>WseeFileStore</store>
</saf-agent>
</domain>

Server start arguments ignored when starting managed server

Hi
We have configured a bunch of arguments for the managed server through the Admin Console in the Server->Start Arguments
However those arguments are not picked up when we are starting the managed server.
We are using a shell script to start the managed server using the weblogic.Admin class functionality.
If the arguments are set in the JAVA_OPTIONS of setDomainEnv.sh, then they are picked up when starting the managed server.
The nodemanager is configured with startScriptEnabled=true and startscript set to startWeblogic.sh.
This is the scenario in Weblogic 10.0.0.
Can anybody please explain why the arguments are not picked up?
We tried the same arguments in Weblogic 10.2 and the arguments are picked up even if they are not configured in setDomainEnv.sh
Is the difference in behavior because of the difference in versions?
Edited by: user1030647 on Aug 29, 2010 12:26 AM

Thanks Jay for the immediate responses.
The thing I am worried about is it seems the behavior in Weblogic 10.0.2 seems to be in consistent with the behavior in Weblogic 10.0.0.
In Weblogic 10.0.2, even if the JAVA_OPTIONS in setDomainEnv.sh do not include the paramaters that are set in "Server Start->Arguments", when starting the managed servers, they are picked up as can be seen from the managed server log files.
However, in Weblogic 10.0.0, it seems that these options are not picked up when they are configured in "Server Start->Arguments". Only when they are configured in setDomainEnv.sh are they picked up.
Do you have any info which points to this discrepancy?

Printing all messages when WEBLOGIC starts in its log file

Hello i am following all these steps
Step 1. Copy log4j-1.2.9.jar & wllog4j.jar under domain_root/lib folder.
Step 2. Create log4j.xml and drop it under domain_root folder. If you have log4j.xml inside the application(EAR/WAR), I would recommend to move outside EAR/WAR as
changing severity (log level) would require re-deployment. To avoid this, we can move log4j.xml into domain root folder but again the server needs to be bounced.
But there is a fix.
Step 3. Login to weblogic server console. Go to Servers -> Admin Server-> Logging.
Click on advanced mode. Change the logging implementation from JDK to Log4J.
Click save.
Step 4. Activate changes. Re-start the admin server.
This should enable log4j and should write logging into log file mentioned in log4j.xml or properties file.
Hang on! There is a catch here. Say now I want to change the log level from DEBUG into WARN or ERROR.
How do i do?
We go to log4j.xml and change the level.
Now how does this change take into effect? It needs bouncing of the server.
I have given below sample log4j.xml for your reference...
log4j.xml:
<?xml version="1.0" encoding="UTF-8" ?><!DOCTYPE log4j:configuration SYSTEM
"log4j.dtd">
<log4j:configuration>
<appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern"
value="%d [%t] %-5p %c - %m%n"/>
</layout>
</appender>
<appender name="FILE" class="org.apache.log4j.RollingFileAppender">
<param name="File" value="/log/myApp.log"/>
<param name="Append" value="true"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d{ISO8601} %t %-5p %c{2} - %m%n"/>
</layout>
</appender>
<logger name="org.apache">
<level value="WARN"/>
</logger>
<logger name="org.springframework">
<level value="WARN"/>
</logger>
<root>
<level value="DEBUG"/>
<appender-ref ref="FILE"/>

</root>
</log4j:configuration>
I Followed all these steps , but finally i am getting an empty file myApp.log at specified destination , i want all log messages inside that file when WEBLOGIC starts , so what needs to be done for that

I guess the issue here is that somehow the log4j configurations are not getting picked up.
Please try adding the LOG4j configurations explicitly onto the classpath:-
set LOG4J_CONFIG_FILE=log4j.xml
set SAVE_JAVA_OPTIONS=%JAVA_OPTIONS% -Dlog4j.configuration=%LOG4J_CONFIG_FILE%
@REM set SAVE_CLASSPATH=%CLASSPATH%
set SAVE_CLASSPATH=%CLASSPATH%;C:\Oracle\Middleware\user_projects\domains\base_domain\config
-Sandeep

Common weblogic start/stop script

Hi,
We have Weblogic 8.1 on Solaris 8. We have lot of domains in the user_projects. Instead of shutting down and starting up each domain everytime. I would like to have a common weblogic start and stop script for all the domains. so that when I execute the script all the weblogic instances in each domain should be stopped or started up automatically.
I think lot of people would have implemented this. I appreciate if someone can help me in achieving this.
Thanks,
Vani

In /etc/rc3.d (all the files in this script are executed at the time of server boot) you can keep a script called S99weblogic and add below line that file,
#!/bin/ksh
su - wladmin -c "/etc/init.d/start_weblogic.sh start"
and in /etc/init.d you can write script start_weblogic.sh, as below
#!/bin/ksh
case "$1" in
'start')
# for admin server
if [ -f <init log path>/startadmin.log ]
then
print -n "\t\n\n deleting <init log path>/startadmin.log\n\n"
/usr/xpg4/bin/rm -rf <init log path>/startadmin.log
fi
### like above do for manged servers logs also ( if you have different script formats for admin and managed servers) and startadmin.log contains paths to all the admin server scripts)
# boot logs when the instances are started which will contains error while the instances are started
if [ -f init log path/boot.err.log ]
then
print -n "\t\n\n deleting init log path/boot.err.log\n\n"
/usr/xpg4/bin/rm -rf init log path/boot.err.log
#contians the list of domains in your physical or virtual server
if [ -f init log path/domain_list.log ]
then
print -n "\t\n\n deleting init log path/domain_list.log\n\n"
/usr/xpg4/bin/rm -rf init log path/domain_list.log
#list all domain names in domain_list.log
#use below command to find all the domians scripts home, for weblogic 8 in ur physical server
# for weblogic 8
ls -d <path to user projects untill scripts home>/* > inint log path/domain_list.log
#if ur domain are scattered then append other domains also -for weblogic 9.x, 10.x.........
ls -d <path to user projects untill scripts home>/*/bin >> initn log path/domain_list.log
# get start up sctiprs
for file in `/usr/bin/cat init log path/domain_list.log`
do
ls $file/startadm*.sh >> init log path/startadmin.log
ls $file/startwl*.sh >> init log path/startmgd.log
fi
done
#start startup scritps
for file in `/usr/bin/cat init log path/startadmin.log`
do
cd `/usr/bin/dirname $file`
nohup $file >> init log path/boot.err.log 2>&1 &
#do the same for manged server sctips
done

Remote start arguments and nodemanager

Hi,
if we provide the value '-ms96m -mx128m' for 'Arguments' under <domain>-Servers-<server>-Configuration-Remote
Start we get the following error:
<BaseProcessControl: saving process id of Weblogic Managed server 'condor-1',
pid: 16388>
Error occurred during initialization of VM
Incompatible initial and maximum heap sizes specified
Child exited
Without any arguments the server starts with the heap-configuration of the nodemanager.
How do we have to provide a different setting?
Btw. we had to change the startNodeManager.sh-script to get things running. Without
exporting CLASSPATH and PATH we were unable to start java with an ld.so.1-error.
Regards,
Christian
WLS 6.1sp1, Solaris 2.6

Hi,
if we provide the value '-ms96m -mx128m' for 'Arguments' under <domain>-Servers-<server>-Configuration-Remote
Start we get the following error:
<BaseProcessControl: saving process id of Weblogic Managed server 'condor-1',
pid: 16388>
Error occurred during initialization of VM
Incompatible initial and maximum heap sizes specified
Child exited
Without any arguments the server starts with the heap-configuration of the nodemanager.
How do we have to provide a different setting?
Btw. we had to change the startNodeManager.sh-script to get things running. Without
exporting CLASSPATH and PATH we were unable to start java with an ld.so.1-error.
Regards,
Christian
WLS 6.1sp1, Solaris 2.6

Weblogis start error

C:\bea\user_projects\domains\oim10g>startWebLogic.cmd
JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=
48m -XX:MaxPermSize=128m
WLS Start Mode=Development
CLASSPATH=;C:\bea\patch_wlw1030\profiles\default\sys_manifest_classpath\weblogic
patch.jar;C:\bea\patchwls1030\profiles\default\sys_manifest_classpath\weblogic
patch.jar;C:\bea\patchcie660\profiles\default\sys_manifest_classpath\weblogic_
patch.jar;C:\bea\JDK160~1\lib\tools.jar;C:\bea\WLSERV~1.3\server\lib\weblogic_sp
.jar;C:\bea\WLSERV~1.3\server\lib\weblogic.jar;C:\bea\modules\features\weblogic.
server.modules_10.3.0.0.jar;C:\bea\WLSERV~1.3\server\lib\webservices.jar;C:\bea\
modules\ORGAPA~1.5/lib/ant-all.jar;C:\bea\modules\NETSFA~1.0_1/lib/ant-contrib.j
ar;;C:\bea\WLSERV~1.3\common\eval\pointbase\lib\pbclient57.jar;C:\bea\WLSERV~1.3
\server\lib\xqrl.jar;;
PATH=C:\bea\patch_wlw1030\profiles\default\native;C:\bea\patch_wls1030\profiles\
default\native;C:\bea\patch_cie660\profiles\default\native;C:\bea\WLSERV~1.3\ser
ver\native\win\32;C:\bea\WLSERV~1.3\server\bin;C:\bea\modules\ORGAPA~1.5\bin;C:\
bea\JDK160~1\jre\bin;C:\bea\JDK160~1\bin;C:\OraHome_1\jdk\jre\bin\client;C:\OraH
ome_1\bin;C:\OraHome_1\jlib;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\W
bem;C:\Program Files\Java\jdk1.6.0_10\bin;C:\bea\WLSERV~1.3\server\native\win\32
\oci920_8
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
starting weblogic with Java version:
java version "1.6.0_05"
Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode)
Starting WLS with line:
C:\bea\JDK160~1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -
XX:PermSize=48m -XX:MaxPermSize=128m -Xverify:none -da -Dplatform.home=C:\bea
\WLSERV~1.3 -Dwls.home=C:\bea\WLSERV~1.3\server -Dweblogic.home=C:\bea\WLSERV~1.
3\server -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testCo
nsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\bea\patch_wlw1030\profil
es\default\sysext_manifest_classpath;C:\bea\patch_wls1030\profiles\default\sysex
t_manifest_classpath;C:\bea\patch_cie660\profiles\default\sysext_manifest_classp
ath -Dweblogic.Name=AdminServer -Djava.security.policy=C:\bea\WLSERV~1.3\server\
lib\weblogic.policy weblogic.Server
<Jan 31, 2010 3:25:31 AM EST> <Notice> <WebLogicServer> <BEA-000395> <Following
extensions directory contents added to the end of the classpath:
C:\bea\user_projects\domains\oim10g\lib\log4j-1.2.8.jar;C:\bea\user_projects\dom
ains\oim10g\lib\mbeantypes\XL10SecurityProviders.jar;C:\bea\user_projects\domain
s\oim10g\lib\nexaweb-common.jar>
<Jan 31, 2010 3:25:31 AM EST> <Info> <WebLogicServer> <BEA-000377> <Starting Web
Logic Server with Java HotSpot(TM) Client VM Version 10.0-b19 from Sun Microsyst
ems Inc.>
<Jan 31, 2010 3:25:31 AM EST> <Info> <Management> <BEA-141107> <Version: WebLogi
c Server 10.3 Fri Jul 25 16:30:05 EDT 2008 1137967 >
<Jan 31, 2010 3:25:33 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to STARTING>
<Jan 31, 2010 3:25:33 AM EST> <Info> <WorkManager> <BEA-002900> <Initializing se
lf-tuning thread pool>
<Jan 31, 2010 3:25:33 AM EST> <Notice> <Log Management> <BEA-170019> <The server
log file C:\bea\user_projects\domains\oim10g\servers\AdminServer\logs\AdminServ
er.log is opened. All server side log events will be written to this file.>
<Jan 31, 2010 3:25:39 AM EST> <Error> <Security> <BEA-090870> <The realm "myreal
m" failed to be loaded: weblogic.security.service.SecurityServiceException: java
.lang.NoClassDefFoundError: com/thortech/util/logging/Logger.
weblogic.security.service.SecurityServiceException: java.lang.NoClassDefFoundErr
or: com/thortech/util/logging/Logger
at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(
Unknown Source)
at weblogic.security.service.CSSWLSDelegateImpl.initialize(Unknown Sourc
e)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.In
itializeServiceEngine(Unknown Source)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.in
itializeRealm(Unknown Source)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.lo
adRealm(Unknown Source)
Truncated. see log file for complete stacktrace
java.lang.NoClassDefFoundError: com/thortech/util/logging/Logger
at com.thortech.xl.security.wl.XellerateAuthenticationProviderImpl.<clin
it>(XellerateAuthenticationProviderImpl.java:73)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at com.bea.common.security.internal.legacy.service.SecurityProviderImpl.
init(SecurityProviderImpl.java:51)
at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(S
erviceEngineImpl.java:363)
Truncated. see log file for complete stacktrace
java.lang.ClassNotFoundException: com.thortech.util.logging.Logger
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
Truncated. see log file for complete stacktrace
>
<Jan 31, 2010 3:25:39 AM EST> <Notice> <Security> <BEA-090082> <Security initial
izing using security realm myrealm.>
<Jan 31, 2010 3:25:39 AM EST> <Critical> <WebLogicServer> <BEA-000362> <Server f
ailed. Reason:
There are 1 nested errors:
weblogic.security.service.SecurityServiceRuntimeException: [Security:090399]Secu
rity Services Unavailable
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.do
BootAuthorization(Unknown Source)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.in
itialize(Unknown Source)
at weblogic.security.service.SecurityServiceManager.initialize(Unknown S
ource)
at weblogic.security.SecurityService.start(SecurityService.java:141)
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)
>
<Jan 31, 2010 3:25:39 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to FAILED>
<Jan 31, 2010 3:25:39 AM EST> <Error> <WebLogicServer> <BEA-000383> <A critical
service failed. The server will shut itself down>
<Jan 31, 2010 3:25:39 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to FORCE_SHUTTING_DOWN>
C:\bea\user_projects\domains\oim10g>

You need to use the domains/<domain>/bin/xlStartWLS.cmd and not the startWebLogic.cmd file. The xlStartWLS one will contain all the updated libraries used when starting OIM.
-Kevin

Weblogic starting in ADMIN mode for Epmserver0...11.1.2.3 version

Hi All,
I have installed Hyperion 11.1.2.3 version with sql server 2008. after configuration .. services are up and running.But i'm unable to login to worskpace/shared services.
i tried login to weblogic. under servers epmserver0 in running in ADMIN mode...insted of runnin mode.
also EPMA services are not starting...
Can anyone give me the solution for this 2 issues...
Regards,
Ravi

user9060912 wrote:
Hello hyperionEPM...
Firstly thank you very much for your help.
I haven't check the forum due some prob... pls dnt says like this... i have marked helpful for your post.
once again thank you hyperionEPM.
One more thing... please try to help the people if you know the answer and dont expect anything from them.they will automatically do this.
and about my questions analysis ... please don't do like this to anyone.
thanks for you big big help...I am not here to fight, so relax... :)
Sorry to say but you shouldn't be saying all this...After all points encourage users on the forum to answer to your queries..
Thanks,
hyperionEPM

Weblogic starting in production mode LINUX x86

I am having a problem when creating a new weblogic 10.3.3 domain. I created this domain in development mode yet when i try and start the domain the admin server always starts in Production mode?
Does anyone know why this is happening as i've check the weblogic console and it shows that the domain is set to development. Below is the message recieved on start up of the admin server:
<Warning> <Management> <BEA-141274> <Production mode has specified at the command line via the weblogic.ProductionModeEnabled system property. This system property overrides the development mode setting contained in config.xml. However, the console and WLST show the attribute values and defaults that correspond to the development mode specified in config.xml.>
Thanks for your help in advance.

I have the same problem during the start of Oracle Identity Manager 11G...Admin Server and Managed Server on different machines...
####<Dec 2, 2010 5:25:17 PM MSK> <Error> <Security> <asoim.sgp.gazprom.ru> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <1291299917129> <BEA-090892> <The dynamic loading of the OPSS java security policy provider class oracle.security.jps.internal.policystore.JavaPolicyProvider failed due to problem inside OPSS java security policy provider. Exception was thrown when loading or setting the JPSS policy provider. Enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01538: The default policy provider was not found.>
####<Dec 2, 2010 5:25:17 PM MSK> <Critical> <WebLogicServer> <asoim.sgp.gazprom.ru> <oim_server1> <main> <<WLS Kernel>> <1291299917132> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The dynamic loading of the OPSS java security policy provider class oracle.security.jps.internal.policystore.JavaPolicyProvider failed due to problem inside OPSS java security policy provider. Exception was thrown when loading or setting the JPSS policy provider. Enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01538: The default policy provider was not found.
weblogic.security.SecurityInitializationException: The dynamic loading of the OPSS java security policy provider class oracle.security.jps.internal.policystore.JavaPolicyProvider failed due to problem inside OPSS java security policy provider. Exception was thrown when loading or setting the JPSS policy provider. Enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01538: The default policy provider was not found.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1394)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
at weblogic.security.SecurityService.start(SecurityService.java:141)
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: oracle.security.jps.JpsRuntimeException: JPS-01538: The default policy provider was not found.
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:273)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:265)
at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:136)
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:1312)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
at weblogic.security.SecurityService.start(SecurityService.java:141)
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: oracle.security.jps.JpsException: JPS-01538: The default policy provider was not found.
at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:705)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:271)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:265)
at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:136)
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:1312)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
at weblogic.security.SecurityService.start(SecurityService.java:141)
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: oracle.security.jps.JpsException: JPS-01514: The default context is missing in jps-config.xml.
at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:665)
at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:650)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:650)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:271)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:265)
at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:136)
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:1312)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
at weblogic.security.SecurityService.start(SecurityService.java:141)
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: oracle.security.jps.service.credstore.CredStoreException: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException: PKI-02002: Unable to open the wallet. Check password.
at oracle.security.jps.internal.credstore.ssp.CsfWalletManager.openWallet(CsfWalletManager.java:177)
at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.doInit(SspCredentialStore.java:218)
at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.<init>(SspCredentialStore.java:140)
at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.<init>(SspCredentialStore.java:127)
at oracle.security.jps.internal.credstore.ssp.SspCredentialStoreProvider.getInstance(SspCredentialStoreProvider.java:115)
at oracle.security.jps.internal.credstore.ssp.SspCredentialStoreProvider.getInstance(SspCredentialStoreProvider.java:53)
and help???

BEA-012036 Too Many Files | Weblogic Start Up for EJB deployment

Trying to deploy EAR with EJB module inside. I am seeing the below error intermittently while deploying and now starting the weblogic server .
There is already an EAR deployed with all the Shared Libraries under APP-INF/lib. I deployed a new EAR with all the similar common shared libraries ( APP-INF/lib jar files ) packaged inside this new file.
<Apr 28, 2009 7:45:18 PM EDT> <Error> <EJB> <BEA-012036> <Compiling generated EJB classes produced the following Java compiler error message:
/prod/xxxx/prd/server/dev_xxxx/servers/mt_crd_180_15001/cache/EJBCompilerCache/f6yuykfqdn7i/com/test/xxx/ejb/rtmschema/CreditserviceSessionEjb_f0jmmq_Impl.java:17: error while writing com.test.xxx.ejb.rtmschema.CreditserviceSessionEjb_f0jmmq_Impl: /prod/xxxx/prd/server/dev_xxxx/servers/mt_crd_180_15001/cache/EJBCompilerCache/f6yuykfqdn7i/com/test/xxx/ejb/rtmschema/CreditserviceSessionEjb_f0jmmq_Impl.class (Too many open files)
(source unavailable)
1 error
>
<Apr 28, 2009 7:45:19 PM EDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'xxx-ear-ejb4' due to error weblogic.application.ModuleException: Exception preparing module: EJBModule(xxx-ejbschema-service.jar)
Unable to deploy EJB: xxx-ejbschema-service.jar from xxx-ejbschema-service.jar:
There are 1 nested errors:
java.io.IOException: Compiler failed executable.exec:
/prod/xxxx/prd/server/dev_xxxx/servers/mt_crd_180_15001/cache/EJBCompilerCache/f6yuykfqdn7i/com/test/xxx/ejb/rtmschema/CreditserviceSessionEjb_f0jmmq_Impl.java:17: error while writing com.test.xxx.ejb.rtmschema.CreditserviceSessionEjb_f0jmmq_Impl: /prod/xxxx/prd/server/dev_xxxx/servers/mt_crd_180_15001/cache/EJBCompilerCache/f6yuykfqdn7i/com/test/xxx/ejb/rtmschema/CreditserviceSessionEjb_f0jmmq_Impl.class (Too many open files)
(source unavailable)
1 error
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:340)
at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:343)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:533)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:500)
at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:476)
at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:798)
at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:701)
at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1234)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:372)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:137)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
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.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
weblogic.application.ModuleException: Exception preparing module: EJBModule(xxx-ejbschema-service.jar)
Unable to deploy EJB: xxx-ejbschema-service.jar from xxx-ejbschema-service.jar:
There are 1 nested errors:
java.io.IOException: Compiler failed executable.exec:
/prod/xxxx/prd/server/dev_xxxx/servers/mt_crd_180_15001/cache/EJBCompilerCache/f6yuykfqdn7i/com/test/xxx/ejb/rtmschema/CreditserviceSessionEjb_f0jmmq_Impl.java:17: error while writing com.test.xxx.ejb.rtmschema.CreditserviceSessionEjb_f0jmmq_Impl: /prod/xxxx/prd/server/dev_xxxx/servers/mt_crd_180_15001/cache/EJBCompilerCache/f6yuykfqdn7i/com/test/xxx/ejb/rtmschema/CreditserviceSessionEjb_f0jmmq_Impl.class (Too many open files)
(source unavailable)
1 error
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:340)
at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:343)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:533)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:500)
at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:476)
at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:798)
at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:701)
at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1234)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:372)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:137)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
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.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:399)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
Truncated. see log file for complete stacktrace
java.io.IOException: Compiler failed executable.exec:
/prod/xxxx/prd/server/dev_xxxx/servers/mt_crd_180_15001/cache/EJBCompilerCache/f6yuykfqdn7i/com/test/xxx/ejb/rtmschema/CreditserviceSessionEjb_f0jmmq_Impl.java:17: error while writing com.test.xxx.ejb.rtmschema.CreditserviceSessionEjb_f0jmmq_Impl: /prod/xxxx/prd/server/dev_xxxx/servers/mt_crd_180_15001/cache/EJBCompilerCache/f6yuykfqdn7i/com/test/xxx/ejb/rtmschema/CreditserviceSessionEjb_f0jmmq_Impl.class (Too many open files)
(source unavailable)
1 error
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:340)
at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:343)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:533)
Truncated. see log file for complete stacktrace
Thanks
Abhi

Put only files which needs to be 'shared' ( e.g persistent store files for jms, jta transaction store etc) on the network drive .. put all other files including logs on the local disk.. see if that makes a difference..
NAS is slower than other storage setups like SAN and DAS...

Weblogic starting error

Hi,
Getting the following error while starting the examples weblogic server. Please help
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
starting weblogic with Java version:
java version "1.6.0_05"
Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
BEA JRockit(R) (build R27.6.1-20-104573-1.6.0_05-20081016-1236-windows-ia32, com
piled mode)
Starting WLS with line:
C:\bea\JROCKI~1\bin\java -jrockit 512m -Xverify:none -da -Dplatform.home=C:\
bea\WLSERV~1.3 -Dwls.home=C:\bea\WLSERV~1.3\server -Dweblogic.home=C:\bea\WLSERV
~1.3\server -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.tes
tConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\bea\patch_wlw1030\pro
files\default\sysext_manifest_classpath;C:\bea\patch_wls1030\profiles\default\sy
sext_manifest_classpath;C:\bea\patch_cie670\profiles\default\sysext_manifest_cla
sspath;C:\bea\patch_alsb1031\profiles\default\sysext_manifest_classpath -Dweblog
ic.Name=examplesServer -Djava.security.policy=C:\bea\WLSERV~1.3\server\lib\weblo
gic.policy weblogic.Server
Exception in thread "Main Thread" java.lang.NoClassDefFoundError: 512m
Stopping PointBase server...
PointBase server stopped.

Hi,
Please open your sservers startScript "startWebLogic.cmd" and then change *512m* to -Xmx512m
As you are using exampleServer....you may find this entry inside "setExamplesEnv.cmd" or "startWebLogicEx.cmd" or inside "startWebLogic.cmd" as well...
Thanks
Jay SenSharma

Weblogic Start script fails while Loading trusted certificates from jks

Hi,
I have a Weblogic Portal 10.3.2 installation on a Solaris Unix box. There is one Admin server and two Managed servers. I am trying to deploy an EJB based application on one of the Managed servers. Note that this application has been working fine in the Weblogic 9.2 environment.
When the Managed Server is started, I get the below messages in the Weblogic console log. We have an internal SSO authentication system, which is integrated with this application. When this integration is removed, we are able to login to the application without any issues. When it is turned on, the redirection from SSO to the application fails - most likely because of the below SSL related errors.
I have accessed the below link and accordingly set the property -Dweblogic.ssl.JSSEEnabled=true. But it didn't help.
http://justasg.blogspot.com/2012/04/tlsssl-certificate-errors-and-warnings.html
Please let me know if you have any suggestions.
<Jun 4, 2012 4:51:59 PM MEST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /data/applications/norkom/BEA103/wlserver_10.3/server/lib/DemoTrust.jks.>
<Jun 4, 2012 4:51:59 PM MEST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/jdk1.6.0_32/jre/lib/security/cacerts.>
<Jun 4, 2012 4:51:59 PM MEST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=Entrust Root Certification Authority - G2,OU=(c) 2009 Entrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Entrust\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Jun 4, 2012 4:51:59 PM MEST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Jun 4, 2012 4:51:59 PM MEST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Jun 4, 2012 4:51:59 PM MEST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Jun 4, 2012 4:51:59 PM MEST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Jun 4, 2012 4:51:59 PM MEST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Jun 4, 2012 4:51:59 PM MEST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Jun 4, 2012 4:51:59 PM MEST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Jun 4, 2012 4:51:59 PM MEST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Jun 4, 2012 4:51:59 PM MEST> <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "DefaultSecure[1]". The address 127.0.0.1 might be incorrect or another process is using port 7022: java.net.BindException: Address already in use.>
<Jun 4, 2012 4:51:59 PM MEST> <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "DefaultSecure". The address 10.228.12.24 might be incorrect or another process is using port 7022: java.net.BindException: Address already in use.>
<Jun 4, 2012 4:51:59 PM MEST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 10.228.12.24:7020 for protocols iiop, t3, ldap, snmp, http.>
<Jun 4, 2012 4:51:59 PM MEST> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 127.0.0.1:7020 for protocols iiop, t3, ldap, snmp, http.>
<Jun 4, 2012 4:51:59 PM MEST> <Notice> <WebLogicServer> <BEA-000332> <Started WebLogic Managed Server "NCA_Server" for domain "norkom" running in Development Mode>
<Jun 4, 2012 4:52:01 PM MEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Jun 4, 2012 4:52:01 PM MEST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<WSEE:27>Warning: JMS queue 'weblogic.wsee.DefaultQueue' is not found, as a result, Web Service async responses via jms transport is not supported. If the target service uses JMS transport, the responses will not be able to come back.<JmsQueueListener.connect:287>
<WSEE:27>Warning: JMS queue 'weblogic.wsee.DefaultQueue' is not found, as a result, Web Service async responses via jms transport is not supported. If the target service uses JMS transport, the responses will not be able to come back.<JmsQueueListener.connect:287>
<WSEE:27>Warning: JMS queue 'weblogic.wsee.DefaultQueue' is not found, as a result, Web Service async responses via jms transport is not supported. If the target service uses JMS transport, the responses will not be able to come back.<JmsQueueListener.connect:287>
<WSEE:27>Warning: JMS queue 'weblogic.wsee.DefaultQueue' is not found, as a result, Web Service async responses via jms transport is not supported. If the target service uses JMS transport, the responses will not be able to come back.<JmsQueueListener.connect:287>
<WSEE:27>Warning: JMS queue 'weblogic.wsee.DefaultQueue' is not found, as a result, Web Service async responses via jms transport is not supported. If the target service uses JMS transport, the responses will not be able to come back.<JmsQueueListener.connect:287>
<WSEE:27>Warning: JMS queue 'weblogic.wsee.DefaultQueue' is not found, as a result, Web Service async responses via jms transport is not supported. If the target service uses JMS transport, the responses will not be able to come back.<JmsQueueListener.connect:287>
Note: We have another Solaris Unix box, with the same installation of Weblogic with the same SSO redirection, but another EJB application is deployed. Also, there is no Managed and the application is deployed on the Admin server itself. But when the server is started, I don't see any attempts to load any certificates and also there are no issues.
So either please suggest how this certificate loading can be rectified or suggest a way to disable the certificate loading (if at all its an option).
Please let me know if you need any further details.

Firstly,
938767 wrote:
<Jun 4, 2012 4:51:59 PM MEST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/jdk1.6.0_32/jre/lib/security/cacerts.>
<Jun 4, 2012 4:51:59 PM MEST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=Entrust Root Certification Authority - G2,OU=(c) 2009 Entrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Entrust\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>I don't think that this will be your problem... Unless you are actually using some of those certificates you can ignore those messages.
But the following looks suspicious, I guess 7022 is your SSL port...
<Jun 4, 2012 4:51:59 PM MEST> <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "DefaultSecure[1]". The address 127.0.0.1 might be incorrect or another process is using port 7022: java.net.BindException: Address already in use.>
<Jun 4, 2012 4:51:59 PM MEST> <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "DefaultSecure". The address 10.228.12.24 might be incorrect or another process is using port 7022: java.net.BindException: Address already in use.>Hope that helps.
Cheers,
Vlad
Give points - it is good etiquette to reward an answerer points (5 - helpful; 10 - correct) for their post if they answer your question. If you think this answer is helpful, please consider giving points.

Problem to weblogic start managed server "OraSDP"

Hi all,
first, sorry if this location is not correct to this thread.
I have a problem when I start a weblogic managed server, which indicates there is an error to check a QueueConnectionFactory into JNDI.
The log of this error is next:
<16-feb-2011 13H35' CET> <Warning> <Connector> <BEA-190110> <Resource Adapter is calling BootstrapContext.createTimer() and allocating a Timer Thread that is not managed by WebLogic Server. This may adversely impact the performance/operation of WebLogic Server.>
<16-feb-2011 13H35' CET> <Error> <oracle.sdp.messaging.util> <SDP-25716> <Se ha producido un error al consultar QueueConnectionFactory en JNDI, saltando: [OraSDPM/QueueConnectionFactory, OraSDPM/Queues/OraSDPMDriverDefSndQ1] >
<16-feb-2011 13H35' CET> <Error> <oracle.sdp.messaging.util> <SDP-25700> <Se ha obtenido una excepción inesperada.
javax.naming.NameNotFoundException: While trying to lookup 'OraSDPM.QueueConnectionFactory' didn't find subcontext 'OraSDPM'. Resolved ''; remaining name 'OraSDPM/QueueConnectionFactory'
     at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
     at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247)
     at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
     at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
     at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
     at javax.naming.InitialContext.lookup(InitialContext.java:392)
     at oracle.sdpinternal.messaging.util.MessagingUtil.getQueueInfoList(MessagingUtil.java:1093)
     at oracle.sdpinternal.messaging.driver.DriverHelper.<init>(DriverHelper.java:189)
     at oracle.sdp.messaging.driver.DriverResourceAdapterBase.start(DriverResourceAdapterBase.java:300)
     at weblogic.connector.security.layer.AdapterLayer.start(AdapterLayer.java:980)
     at weblogic.connector.common.RAInstanceManager.initialize(RAInstanceManager.java:1185)
     at weblogic.connector.common.RAInstanceManager.<init>(RAInstanceManager.java:352)
     at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.java:197)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:507)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
     at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
     at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:141)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
     at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
     at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
     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: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)
>
Anyone knows how can I resolve this error?..
Regards.
PD: Sorry, but there is sentences in Spanish language.

Hi, here you can see my config.xml and a xml file which are in the $DOMAIN_HOME/config/jms/ folder. I have split the config.xml in several parts because it exceeds the maximun length.
Config.xml part I:
<?xml version='1.0' encoding='UTF-8'?>
<domain xmlns="http://xmlns.oracle.com/weblogic/domain" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/security/xacml http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator/1.0/passwordvalidator.xsd http://xmlns.oracle.com/weblogic/domain http://xmlns.oracle.com/weblogic/1.0/domain.xsd http://xmlns.oracle.com/weblogic/security http://xmlns.oracle.com/weblogic/1.0/security.xsd http://xmlns.oracle.com/weblogic/security/wls http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.xsd">
<name>npnode2</name>
<domain-version>10.3.3.0</domain-version>
<security-configuration>
<name>npnode2</name>
<realm>
<sec:authentication-provider xsi:type="wls:default-authenticatorType">
<wls:use-retrieved-user-name-as-principal>true</wls:use-retrieved-user-name-as-principal>
</sec:authentication-provider>
<sec:authentication-provider xsi:type="wls:default-identity-asserterType">
<sec:active-type>AuthenticatedUser</sec:active-type>
</sec:authentication-provider>
<sec:role-mapper xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
<sec:authorizer xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
<sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
<sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
<sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
<sec:name>myrealm</sec:name>
<sec:password-validator xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator" xsi:type="pas:system-password-validatorType">
<sec:name>SystemPasswordValidator</sec:name>
<pas:min-password-length>8</pas:min-password-length>
<pas:min-numeric-or-special-characters>1</pas:min-numeric-or-special-characters>
</sec:password-validator>
</realm>
<default-realm>myrealm</default-realm>
<credential-encrypted>{AES}TvOXKMlehQtZcaRHQ/gQVlgYjxTmuP2CzlEJz9qrFh3uR07iZ+i8EGIA07v0wMPvmzqZi1A2iurkHF8xJHrn+4jPlQsyhKeRHIATxpxFScUXcGm/6ap/gt78jMklop90</credential-encrypted>
<node-manager-username>weblogic</node-manager-username>
<node-manager-password-encrypted>{AES}UPT4LnwZgpkqKzgV/1Li+OoD2dj2d/J7kG4dELlPPoi=</node-manager-password-encrypted>
</security-configuration>
<server>
<name>AdminServer</name>
<listen-address></listen-address>
<server-diagnostic-config>
<name>AdminServer</name>
<diagnostic-context-enabled>true</diagnostic-context-enabled>
</server-diagnostic-config>
</server>
<server>
<name>soa_server1</name>
<ssl>
<name>soa_server1</name>
<listen-port>8002</listen-port>
</ssl>
<machine>LocalMachine</machine>
<listen-port>8001</listen-port>
<listen-address></listen-address>
<server-diagnostic-config>
<name>soa_server1</name>
<diagnostic-context-enabled>true</diagnostic-context-enabled>
</server-diagnostic-config>
</server>
<embedded-ldap>
<name>npnode2</name>
<credential-encrypted>{AES}wcwM9xWQy3NNzRzOEYbyOJq9JAPOo9HGL6EOylMeseZhLZLidXviUnNstKZbrnsu</credential-encrypted>
</embedded-ldap>
<configuration-version>10.3.3.0</configuration-version>
<app-deployment>
<name>FMW Welcome Page Application#11.1.0.0.0</name>
<target>AdminServer</target>
<module-type>ear</module-type>
<source-path>/opt/Oracle/Middleware/oracle_common/modules/oracle.jrf_11.1.1/fmw-welcome.ear</source-path>
<deployment-order>5</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>DMS Application#11.1.1.1.0</name>
<target>AdminServer,soa_server1</target>
<module-type>war</module-type>
<source-path>/opt/Oracle/Middleware/oracle_common/modules/oracle.dms_11.1.1/dms.war</source-path>
<deployment-order>5</deployment-order>
<security-dd-model>CustomRoles</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>wsil-wls</name>
<target>AdminServer,soa_server1</target>
<module-type>ear</module-type>
<source-path>/opt/Oracle/Middleware/oracle_common/modules/oracle.webservices_11.1.1/wsil-wls.ear</source-path>
<deployment-order>5</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>FileAdapter</name>
<target>soa_server1</target>
<module-type>rar</module-type>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/soa/connectors/FileAdapter.rar</source-path>
<deployment-order>321</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>DbAdapter</name>
<target>soa_server1</target>
<module-type>rar</module-type>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/soa/connectors/DbAdapter.rar</source-path>
<deployment-order>322</deployment-order>
<plan-dir xsi:nil="true"></plan-dir>
<plan-path>/opt/Oracle/Middleware/Oracle_SOA1/soa/Plan.xml</plan-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>JmsAdapter</name>
<target>soa_server1</target>
<module-type>rar</module-type>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/soa/connectors/JmsAdapter.rar</source-path>
<deployment-order>323</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>AqAdapter</name>
<target>soa_server1</target>
<module-type>rar</module-type>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/soa/connectors/AqAdapter.rar</source-path>
<deployment-order>324</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>FtpAdapter</name>
<target>soa_server1</target>
<module-type>rar</module-type>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/soa/connectors/FtpAdapter.rar</source-path>
<deployment-order>325</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>SocketAdapter</name>
<target>soa_server1</target>
<module-type>rar</module-type>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/soa/connectors/SocketAdapter.rar</source-path>
<deployment-order>326</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>MQSeriesAdapter</name>
<target>soa_server1</target>
<module-type>rar</module-type>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/soa/connectors/MQSeriesAdapter.rar</source-path>
<deployment-order>327</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>OracleAppsAdapter</name>
<target>soa_server1</target>
<module-type>rar</module-type>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/soa/connectors/AppsAdapter.rar</source-path>
<deployment-order>328</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>OracleBamAdapter</name>
<target>soa_server1</target>
<module-type>rar</module-type>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/soa/connectors/OracleBamAdapter.rar</source-path>
<deployment-order>329</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>wsm-pm</name>
<target>soa_server1</target>
<module-type>ear</module-type>
<source-path>/opt/Oracle/Middleware/oracle_common/modules/oracle.wsm.pm_11.1.1/wsm-pm.ear</source-path>
<deployment-order>5</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>usermessagingserver</name>
<target>soa_server1</target>
<module-type>ear</module-type>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/communications/applications/sdpmessagingserver.ear</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>usermessagingdriver-email</name>
<target>soa_server1</target>
<module-type>ear</module-type>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/communications/applications/sdpmessagingdriver-email.ear</source-path>
<deployment-order>200</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>usermessagingdriver-xmpp</name>
<module-type>ear</module-type>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/communications/applications/sdpmessagingdriver-xmpp.ear</source-path>
<deployment-order>202</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>usermessagingdriver-smpp</name>
<module-type>ear</module-type>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/communications/applications/sdpmessagingdriver-smpp.ear</source-path>
<deployment-order>203</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>usermessagingdriver-voicexml</name>
<module-type>ear</module-type>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/communications/applications/sdpmessagingdriver-voicexml.ear</source-path>
<deployment-order>204</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>em</name>
<target>AdminServer</target>
<module-type>ear</module-type>
<source-path>/opt/Oracle/Middleware/user_projects/applications/npnode2/em.ear</source-path>
<deployment-order>400</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>soa-infra</name>
<target>soa_server1</target>
<module-type>ear</module-type>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/soa/applications/soa-infra-wls.ear</source-path>
<deployment-order>350</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>worklistapp</name>
<target>soa_server1</target>
<module-type>ear</module-type>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/soa/applications/worklist-wls.ear</source-path>
<deployment-order>312</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>b2bui</name>
<target>soa_server1</target>
<module-type>ear</module-type>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/soa/applications/soa-infra-b2bui-wls.ear</source-path>
<deployment-order>313</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>DefaultToDoTaskFlow</name>
<target>soa_server1</target>
<module-type>ear</module-type>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/soa/applications/DefaultToDoTaskFlow.ear</source-path>
<deployment-order>314</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>composer</name>
<target>soa_server1</target>
<module-type>ear</module-type>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/soa/applications/soa-composer.ear</source-path>
<deployment-order>315</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<library>
<name>oracle.jrf.system.filter</name>
<target>AdminServer,soa_server1</target>
<source-path>/opt/Oracle/Middleware/oracle_common/modules/oracle.jrf_11.1.1/system-filters.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.wsm.seedpolicies#[email protected]</name>
<target>AdminServer,soa_server1</target>
<source-path>/opt/Oracle/Middleware/oracle_common/modules/oracle.wsm.policies_11.1.1/wsm-seed-policies.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.jsp.next#[email protected]</name>
<target>AdminServer,soa_server1</target>
<source-path>/opt/Oracle/Middleware/oracle_common/modules/oracle.jsp_11.1.1/ojsp.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.dconfig-infra#[email protected]</name>
<target>AdminServer,soa_server1</target>
<source-path>/opt/Oracle/Middleware/oracle_common/modules/oracle.dconfig-infra_11.1.1.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>orai18n-adf#[email protected]</name>
<target>AdminServer,soa_server1</target>
<source-path>/opt/Oracle/Middleware/oracle_common/modules/oracle.nlsgdk_11.1.0/orai18n-adf.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>adf.oracle.domain#[email protected]</name>
<target>AdminServer,soa_server1</target>
<module-type>ear</module-type>
<source-path>/opt/Oracle/Middleware/oracle_common/modules/oracle.adf.model_11.1.1/adf.oracle.domain.ear</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.adf.dconfigbeans#[email protected]</name>
<target>AdminServer,soa_server1</target>
<source-path>/opt/Oracle/Middleware/oracle_common/modules/oracle.adf.dconfigbeans_11.1.1.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.adf.management#[email protected]</name>
<target>AdminServer,soa_server1</target>
<module-type>war</module-type>
<source-path>/opt/Oracle/Middleware/oracle_common/modules/oracle.adf.management_11.1.1/adf-management.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>adf.oracle.domain.webapp#[email protected]</name>
<target>AdminServer,soa_server1</target>
<module-type>war</module-type>
<source-path>/opt/Oracle/Middleware/oracle_common/modules/oracle.adf.view_11.1.1/adf.oracle.domain.webapp.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>jsf#[email protected]</name>
<target>AdminServer,soa_server1</target>
<module-type>war</module-type>
<source-path>/opt/Oracle/Middleware/wlserver_10.3/common/deployable-libraries/jsf-1.2.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>jstl#[email protected]</name>
<target>AdminServer,soa_server1</target>
<module-type>war</module-type>
<source-path>/opt/Oracle/Middleware/wlserver_10.3/common/deployable-libraries/jstl-1.2.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>UIX#[email protected]</name>
<target>AdminServer,soa_server1</target>
<module-type>war</module-type>
<source-path>/opt/Oracle/Middleware/oracle_common/modules/oracle.uix_11.1.1/uix11.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>ohw-rcf#[email protected]</name>
<target>AdminServer,soa_server1</target>
<module-type>war</module-type>
<source-path>/opt/Oracle/Middleware/oracle_common/modules/oracle.help_5.0/ohw-rcf.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>ohw-uix#[email protected]</name>
<target>AdminServer,soa_server1</target>
<module-type>war</module-type>
<source-path>/opt/Oracle/Middleware/oracle_common/modules/oracle.help_5.0/ohw-uix.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.pwdgen#[email protected]</name>
<target>AdminServer,soa_server1</target>
<source-path>/opt/Oracle/Middleware/oracle_common/modules/oracle.pwdgen_11.1.1/pwdgen.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.rules#[email protected]</name>
<target>AdminServer,soa_server1</target>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.rules_11.1.1/rules.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.webcenter.composer#[email protected]</name>
<target>AdminServer</target>
<module-type>war</module-type>
<source-path>/opt/Oracle/Middleware/oracle_common/webcenter/modules/oracle.webcenter.framework_11.1.1/oracle.webcenter.composer.war</source-path>
<deployment-order>300</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.webcenter.skin#[email protected]</name>
<target>AdminServer</target>
<module-type>ear</module-type>
<source-path>/opt/Oracle/Middleware/oracle_common/webcenter/modules/oracle.portlet.server_11.1.1/oracle.webcenter.skin.ear</source-path>
<deployment-order>300</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.soa.workflow.wc#[email protected]</name>
<target>AdminServer,soa_server1</target>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.workflow_11.1.1/oracle.soa.workflow.wc.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.soa.rules_editor_dc.webapp#[email protected]</name>
<target>AdminServer,soa_server1</target>
<module-type>war</module-type>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.rules_editor_dc.webapp_11.1.1/oracle.soa.rules_editor_dc.webapp.war</source-path>
<deployment-order>306</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.soa.rules_dict_dc.webapp#[email protected]</name>
<target>AdminServer,soa_server1</target>
<module-type>war</module-type>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.rules_dict_dc.webapp_11.1.1/oracle.soa.rules_dict_dc.webapp.war</source-path>
<deployment-order>306</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.bpm.mgmt#[email protected]</name>
<target>AdminServer</target>
<source-path>/opt/Oracle/Middleware/oracle_common/bpm/modules/oracle.bpm.mgmt_11.1.1/oracle.bpm.bpmn-em-tools.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>emai</name>
<target>AdminServer</target>
<module-type>war</module-type>
<source-path>/opt/Oracle/Middleware/oracle_common/sysman/archives/applications/11_1_1_0_0_emai.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.sdp.messaging#[email protected]</name>
<target>AdminServer,soa_server1</target>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/communications/modules/oracle.sdp.messaging_11.1.1/sdpmessaging.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.sdp.client#[email protected]</name>
<target>AdminServer,soa_server1</target>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/communications/modules/oracle.sdp.client_11.1.1/sdpclient.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>emas</name>
<target>AdminServer</target>
<module-type>war</module-type>
<source-path>/opt/Oracle/Middleware/oracle_common/sysman/archives/applications/11_1_1_0_0_emas.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>emcore</name>
<target>AdminServer</target>
<module-type>war</module-type>
<source-path>/opt/Oracle/Middleware/oracle_common/sysman/archives/applications/11_1_1_0_0_emcore.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.soa.bpel#[email protected]</name>
<target>AdminServer,soa_server1</target>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.bpel_11.1.1/oracle.soa.bpel.jar</source-path>
<deployment-order>301</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.soa.worklist#[email protected]</name>
<target>AdminServer,soa_server1</target>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.worklist_11.1.1/oracle.soa.worklist.jar</source-path>
<deployment-order>302</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.soa.workflow#[email protected]</name>
<target>AdminServer,soa_server1</target>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.workflow_11.1.1/oracle.soa.workflow.jar</source-path>
<deployment-order>303</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.soa.mediator#[email protected]</name>
<target>AdminServer,soa_server1</target>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.mediator_11.1.1/oracle.soa.mediator.jar</source-path>
<deployment-order>304</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.soa.composer.webapp#[email protected]</name>
<target>AdminServer,soa_server1</target>
<module-type>war</module-type>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.composer.webapp_11.1.1/oracle.soa.composer.webapp.war</source-path>
<deployment-order>306</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.soa.ext#[email protected]</name>
<target>AdminServer,soa_server1</target>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.ext_11.1.1/oracle.soa.ext.jar</source-path>
<deployment-order>307</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.soa.b2b#[email protected]</name>
<target>AdminServer,soa_server1</target>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.b2b_11.1.1/oracle.soa.b2b.jar</source-path>
<deployment-order>308</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.soa.worklist.webapp#[email protected]</name>
<target>AdminServer,soa_server1</target>
<module-type>war</module-type>
<source-path>/opt/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.worklist.webapp_11.1.1/oracle.soa.worklist.webapp.war</source-path>
<deployment-order>309</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<machine>
<name>LocalMachine</name>
<node-manager>
<name>LocalMachine</name>
<listen-address>localhost</listen-address>
</node-manager>
</machine>
<jms-server>
<name>SOAJMSServer</name>
<target>soa_server1</target>
<persistent-store>SOAJMSFileStore</persistent-store>
</jms-server>
<jms-server>
<name>UMSJMSServer</name>
<target>soa_server1</target>
<persistent-store>UMSJMSFileStore</persistent-store>
</jms-server>
<jms-server>
<name>JMSSGPMC</name>
<target>soa_server1</target>
<persistent-store>FileStore-0</persistent-store>
<hosting-temporary-destinations>true</hosting-temporary-destinations>
<temporary-template-resource xsi:nil="true"></temporary-template-resource>
<temporary-template-name xsi:nil="true"></temporary-template-name>
<message-buffer-size>-1</message-buffer-size>
<paging-file-locking-enabled>true</paging-file-locking-enabled>
<expiration-scan-interval>30</expiration-scan-interval>
</jms-server>
<self-tuning>
<work-manager>
<name>wm/SOAWorkManager</name>
<target>soa_server1</target>
</work-manager>
</self-tuning>
<shutdown-class>
<name>JOC-Shutdown</name>
<target>AdminServer,soa_server1</target>
<deployment-order>150</deployment-order>
<class-name>oracle.ias.cache.Shutdown</class-name>
</shutdown-class>
<shutdown-class>
<name>DMSShutdown</name>
<target>AdminServer,soa_server1</target>
<deployment-order>150</deployment-order>
<class-name>oracle.dms.wls.DMSShutdown</class-name>
</shutdown-class>
<startup-class>
<name>JRF Startup Class</name>
<target>AdminServer,soa_server1</target>
<deployment-order>110</deployment-order>
<class-name>oracle.jrf.wls.JRFStartup</class-name>
<failure-is-fatal>false</failure-is-fatal>
<load-before-app-deployments>true</load-before-app-deployments>
<load-before-app-activation>true</load-before-app-activation>
</startup-class>
<startup-class>
<name>JPS Startup Class</name>
<target>AdminServer,soa_server1</target>
<deployment-order>115</deployment-order>
<class-name>oracle.security.jps.wls.JpsWlsStartupClass</class-name>
<failure-is-fatal>false</failure-is-fatal>
<load-before-app-deployments>true</load-before-app-deployments>
<load-before-app-activation>true</load-before-app-activation>
</startup-class>

Weblogic starting admin server automatically

Hello,
I have deployed a weblogic server on one of my company servers and i do not want to start and stop the admin server everytime i log in. Also, I have adf libraires installed along with the weblogic server. I created a windows service by running the installSvc.cmd file located at => C:\oracle\Middleware\wlserver_10.3\server\bin . Before running the installSvc.cmd command i edited the file by adding the following lines =>
set DOMAIN_NAME=base_domain
set USERDOMAIN_HOME=C:\Oracle\Middleware\user_projects\domains\base_domain
set SERVER_NAME=AdminServer
set WLS_USER=weblogic
set WLS_PW=welcome1
set PRODUCTION_MODE=true
After i install this service i go to servoces and start this service.
Now the issue i run into is that when i go to the admin console i see some of the adf libraries STATUS as "failed" and even when i deploy an adf app the status is failed. This doesnt hapen when i start the admin server from the gui mode by going to Start > user projects > base domain > start admin server or by starting the server from the command line with the command startWeblogic.cmd . How do i create a service so that i dont hv to start the server everytime when i log in to my server(box) which has the weblogic server .
I am in a tight deadline and any help will be greatly appreciated!

What errors are the libraries getting?
Is the classpath the same between the service case and the start from menu case? Look at the server stdout or at the logs and the classpath system property?

Weblogic start issue

Hi all,
I am new to Weblogic and i am trying to start it on Solaris server. It tells me that port is already in use. How can i find the port that is available?
Please help
JAK

jakSun8 wrote:
Hi all,
I am new to Weblogic and i am trying to start it on Solaris server. It tells me that port is already in use. What port did you set up to listen on? The default, 7001?
How can i find the port that is available?Does "netstat -a" work in a Unix shell, too? That's how I see what's running on a Windows machine. As I recall, the command is the same in Unix, but I'm not certain.
%

Weblogic start arguments

Similar Messages

Maybe you are looking for