Failed to stop Managed Weblogic server ..
Hello,
I use Weblogic in OBIEE, i try to stop managed weblogic server but it's failed, can you help me to undestand and fix this issue :
> /servers/bipublisher/bip11/user_projects/domains/bifoundation_domain/bin/stopManagedWebLogic.sh bi_server1 t3://srv-reporting-4.ppd.domaine.com:7001
logs :
SVR_GRP =
Stopping Weblogic Server...
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Please enter your username :weblogic
Please enter your password :
Connecting to t3://srv-reporting-4.ppd.domaine.com:7001 with userid weblogic ...
The CompatabilityMBeanServer is not initialized properly.
This might happen if the CompatabilityMBeanServer is
disabled via the JMXMBean.
To view the root cause exception use dumpStack()
WLST detected that the RuntimeMBeanServer is not enabled. This
might happen if the RuntimeMBeanServer is disabled via the JMXMBean.
Please ensure that this MBeanServer is enabled. Online WLST cannot
function without this MBeanServer.
This Exception occurred at Tue Feb 17 17:29:34 CET 2015.
java.lang.NullPointerException
at java.util.StringTokenizer.<init>(StringTokenizer.java:182)
at java.util.StringTokenizer.<init>(StringTokenizer.java:219)
at weblogic.utils.StringUtils.splitCompletely(StringUtils.java:119)
at weblogic.socket.utils.ProxyUtils.getProxySocket(ProxyUtils.java:178)
at weblogic.socket.utils.ProxyUtils.getClientProxy(ProxyUtils.java:223)
at weblogic.socket.SocketMuxer.newClientSocket(SocketMuxer.java:381)
at weblogic.socket.ChannelSocketFactory.createSocket(ChannelSocketFactory.java:86)
at weblogic.socket.BaseAbstractMuxableSocket.createSocket(BaseAbstractMuxableSocket.java:133)
at weblogic.rjvm.t3.MuxableSocketT3.newSocketWithRetry(MuxableSocketT3.java:214)
at weblogic.rjvm.t3.MuxableSocketT3.connect(MuxableSocketT3.java:383)
at weblogic.rjvm.t3.ConnectionFactoryT3.createConnection(ConnectionFactoryT3.java:34)
at weblogic.rjvm.ConnectionManager.createConnection(ConnectionManager.java:1784)
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1424)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:443)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:321)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:254)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:345)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:178)
at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:84)
at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:338)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)
at weblogic.management.scripting.WLSTHelper.lookupMBeanServerConnection(WLSTHelper.java:678)
at weblogic.management.scripting.WLSTHelper.initRuntimeServerConnection(WLSTHelper.java:398)
at weblogic.management.scripting.WLSTHelper.initConnections(WLSTHelper.java:315)
at weblogic.management.scripting.WLSTHelper.connect(WLSTHelper.java:203)
at weblogic.management.scripting.WLScriptContext.connect(WLScriptContext.java:61)
at weblogic.management.scripting.utils.WLSTUtil.initializeOnlineWLST(WLSTUtil.java:147)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.python.core.PyReflectedFunction.__call__(Unknown Source)
at org.python.core.PyMethod.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.core.PyObject.invoke(Unknown Source)
at org.python.pycode._pyx4.connect$1(<iostream>:16)
at org.python.pycode._pyx4.call_function(<iostream>)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyFunction.__call__(Unknown Source)
at org.python.pycode._pyx15.f$0(/servers/bipublisher/bip11/user_projects/domains/bifoundation_domain/shutdown.py:6)
at org.python.pycode._pyx15.call_function(/servers/bipublisher/bip11/user_projects/domains/bifoundation_domain/shutdown.py)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyCode.call(Unknown Source)
at org.python.core.Py.runCode(Unknown Source)
at org.python.util.PythonInterpreter.execfile(Unknown Source)
at weblogic.management.scripting.WLST.main(WLST.java:124)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.WLST.main(WLST.java:29)
Problem invoking WLST - Traceback (innermost last):
File "/servers/bipublisher/bip11/user_projects/domains/bifoundation_domain/shutdown.py", line 6, in ?
File "<iostream>", line 22, in connect
File "<iostream>", line 646, in raiseWLSTException
WLSTException: Error occured while performing connect : "Cannot connect to WLST."
Use dumpStack() to view the full stacktrace
Regards
Djms
Hi
Check that you are able to ping or telnet the machine srv-reporting-4.ppd.domaine.com from the Admin Server machine .
As from the Error message its not able to conenct to the machine and the port number .
WLSTException: Error occured while performing connect : "Cannot connect to WLST
Check the network connectivity and then try to stop the managed Server it will stop.
Hope it helps
Similar Messages
-
Deploying ADF application to a managed weblogic server - ADF security error
Hi,
Our group has written an ADF web application, which we are attempting to deploy to a managed weblogic server. Thus far, we have been unsuccessful. The application does successfully deploy to the AdminServer. Our setup:
Weblogic version is 10.3.0. Domain name is adf_domain. We have installed the ADF (ADF version is 11.1.1.0.0), JSTL(1.2.0.1), and JSF(1.2.7.1) runtime libraries, and they are targeted to both the admin server AND the managed server, which is called CollabServer. This server communicates with the node manager and can be started and stopped via the admin console successfully. The AdminServer is on port 7101, and the CollabServer is on port 7104. We are not using 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>
<context-root>orc</context-root>
</web>
</module>
</application>
weblogic-application.xml (as taken from the ear file):
<?xml version = '1.0' encoding = 'windows-1252'?>
<weblogic-application 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">
<listener>
<listener-class>oracle.security.jps.wls.listeners.JpsApplicationLifecycleListener</listener-class>
</listener>
<library-ref>
<library-name>adf.oracle.domain</library-name>
</library-ref>
</weblogic-application>
weblogic.xml (as taken from the war file):
<?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="http://ww
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>
<role-name>valid-users</role-name>
<principal-name>users</principal-name>
</security-role-assignment>
<library-ref>
<library-name>jstl</library-name>
<specification-version>1.2</specification-version>
</library-ref>
<library-ref>
<library-name>jsf</library-name>
<specification-version>1.2</specification-version>
</library-ref>
</weblogic-web-app>
As I said, there are no deployment errors when we deploy to the admin server. However, we always see the following errors when deploying to the managed server:
java.lang.ClassNotFoundException: oracle.security.jps.wls.listeners.JpsApplicationLifecycleListener
etc.
This error occurs when deploying via the <wldeploy> ant task included with weblogic, and when deploying the application manually via the admin console.
So I removed this from weblogic-application.xml:
<listener>
<listener-class>oracle.security.jps.wls.listeners.JpsApplicationLifecycleListener</listener-class>
</listener>
Which resolved the initial error (I assume there is some sort of bug that causes this workaround to be necessary). The next error is this:
java.lang.ClassNotFoundException: oracle.adf.share.security.authentication.AuthenticationServlet
Again, we don't get this error when deploying to the AdminServer - ONLY the managed server CollabServer.
web.xml:
<servlet>
<servlet-name>adfAuthentication</servlet-name>
<servlet-class>oracle.adf.share.security.authentication.AuthenticationServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>adfAuthentication</servlet-name>
<url-pattern>/adfAuthentication/*</url-pattern>
</servlet-mapping>
I then added some adf jar files to the ear file, finally get this error message:
java.lang.ClassNotFoundException: oracle.adf.share.jsp.ADFLibUtils
Any ideas on how to resolve this? Thanks.
Edited by: user10451099 on Apr 15, 2009 12:10 PMDan,
thanks fro reminding me :-)
Here are the steps we had to take to get a managed WLS to run an adf application without copying any jar in the domain/lib directory:
1. you still have to install the adf runtime to any server you want the adf application to deploy to
2. open the admin console, select the managed server, and select the 'server start' tab in configutation settings.
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 to the classpath edit box you have to change '/u01/bea/' with your bea home. The classpath should be on one line without the 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 to the 'Arguments' edit box. As with the calsspath change '/u01/bea' to your bea home and change the domain name (in our case 'naa_qs') to your domain name. change the managementuser and passwort to your needs. As whith the classpath I put some CR/LF into the code section to make it readable.
5. save the changes and restart the server
Essentially all we copied the arguments from the admin server start script in addition to adding the class path.
Timo -
Trouble starting managed weblogic server on another machine in acluster
Hi,
I was having trouble starting managed weblogic server on another machine in a cluster from the command prompt
I have following setup:
1) BEA weblogic is installed on 2 machines - local machine A with ip address 172.17.2.219 and another machine B with ip address 172.17.2.201
2)node manager is running on both machines
3)An admin server myserver on the local machine at port 7001
4)In the admin tree under Machines a new machine is created 'Machine1' with Node manager Listen Address: 172.17.2.201
5) The managed server 'BEAServerMan1 ' instance is created with listen Address 172.17.2.201 and port 7705. This Server is assigened to Machine1. The server also belongs to a cluster 'Cluster1' where the 172.17.2.201:7705 is part of the Cluster Address.
I can start 'BEAServerMan1 from http://172.17.2.16:7001/console/
But I am unable to start BEAServerMan1 from the console using the command :
startManagedWebLogic BEAServerMan1 http://172.17.2.219:7001
startManagedWebLogic.sh BEAServerMan1 http://172.17.2.219:7001
CLASSPATH=/opt/BEA/j2sdk1.4.1_03/lib/tools.jar:/opt/BEA/weblogic81/server/lib/weblogic_sp.jar:/opt/BEA/weblogic81/server/lib/weblogic.jar:/opt/BEA/weblogic81/server/lib/ojdbc14.jar::/opt/BEA/weblogic81/common/eval/pointbase/lib/pbserver44.jar:/opt/BEA/weblogic81/common/eval/pointbase/lib/pbclient44.jar:/opt/BEA/j2sdk1.4.1_03/jre/lib/rt.jar:/opt/BEA/weblogic81/server/lib/webservices.jar:/opt/BEA/j2sdk1.4.1_03/bin:/opt/BEA/j2sdk1.4.1_03:/opt/BEA/j2re1.4.1_03/bin:/opt/BEA/j2re1.4.1_03:/opt/BEA/j2sdk1.4.1_03/lib/tools.jar:/opt/oracle/OraHome1/jdbc/lib/classes111.jar:/opt/oracle/OraHome1/jdbc/lib/nls_charset11.jarx:/opt/BEA/user_projects/domains/mydomain/myserver/stage/_appsdir_dyn_ear/dyn.war:/opt/BEA/user_projects/domains/mydomain/./myserver/.wlnotdelete/extract/myserver__appsdir_dyn_ear_dyn/jarfiles/WEB-INF/lib/dspjspTaglib1_036773.jar:/usr/bin/j2re1_3_1_11/bin:/usr/bin/j2sdk1_3_1_11/bin:/usr/bin/j2sdk1_3_1_11:/usr/bin/j2sdk1_3_1_11/lib/tools.jar
PATH=/opt/BEA/weblogic81/server/bin:/opt/BEA/j2sdk1.4.1_03/jre/bin:/opt/BEA/j2sdk1.4.1_03/bin:/opt/BEA/j2sdk1.4.1_03/bin:/opt/BEA/j2sdk1.4.1_03:/opt/BEA/j2re1.4.1_03/bin:/opt/BEA/j2re1.4.1_03:/opt/BEA/ATG6.2.0/home/bin:/usr/xpg4/bin:/opt/bmc/Patrol3/Solaris28-sun4/bin:/usr/bin::/usr/openwin/bin:/bin:/usr/ucb:/usr/local/sbin:/usr/dt/bin:/opt/RICHPse/bin:/usr/bin/j2re1_3_1_11/bin:/usr/bin/j2sdk1_3_1_11/bin
* 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 *
<13-Jan-2005 3:22:20 o'clock PM EST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.4.1_03-b02 from Sun Microsystems Inc.>
<13-Jan-2005 3:22:21 o'clock PM EST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://172.17.2.219:7001 to check if there exists a running admin server at this URL.>
<13-Jan-2005 3:22:22 o'clock PM EST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<13-Jan-2005 3:22:22 o'clock PM EST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP1 Fri Jun 20 23:06:40 PDT 2003 271009
WebLogic XMLX Module 8.1 SP1 Fri Jun 20 23:06:40 PDT 2003 271009>
<13-Jan-2005 3:22:22 o'clock PM EST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://172.17.2.219:7001 to retrieve the initial configuration.>
<13-Jan-2005 3:22:27 o'clock PM EST> <Notice> <Log Management> <BEA-170019> <The server log file /opt/BEA/user_projects/domains/mydomain/BEAServerMan1 /BEAServerMan1 .log is opened. All server side log events will be written to this file.>
<13-Jan-2005 3:22:37 o'clock PM EST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<13-Jan-2005 3:22:38 o'clock PM EST> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "BEAServerMan1 " for domain "mydomain">
<13-Jan-2005 3:22:50 o'clock PM EST> <Notice> <Cluster> <BEA-000138> <Listening for announcements from cluster Cluster1 on 237.0.0.1:7001.>
<13-Jan-2005 3:22:50 o'clock PM EST> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of Cluster1.>
<13-Jan-2005 3:23:24 o'clock PM EST> <Emergency> <WebLogicServer> <BEA-000350> <Unable to create a server socket on Channel Default for: 172.17.2.201, port: 7705. java.net.BindException: Cannot assign requested address Perhaps the address 172.17.2.201 is incorrect or another process is using port 7705.>
<13-Jan-2005 3:23:24 o'clock PM EST> <Emergency> <Security> <BEA-090085> <Server failed to bind to the configured port. The port may already be used by another process.>
<13-Jan-2005 3:23:24 o'clock PM EST> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: Server failed to bind to the requested port. See preceeding log message for details.>
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.server.ServerLifecycleException: Server failed to bind to the requested port. See preceeding log message for details.'
Reason: Server failed to bind to the requested port. See preceeding log message for details.
***************************************************************************Hi
i am also facing the same problem.kindly reply for th solution if you got.
D:\bea1\user_projects_cluster\mydomain>startManagedWebLogic server2 10.16.96.21:
7001
D:\bea1\user_projects_cluster\mydomain>echo off
CLASSPATH=d:\bea1\jdk131_03\lib\tools.jar;d:\bea1\weblogic700\server\lib\weblogi
c_sp.jar;d:\bea1\weblogic700\server\lib\weblogic.jar;F:\bea\weblogic81\server\li
b;D:\;c:\
PATH=.;d:\bea1\weblogic700\server\bin;d:\bea1\jdk131_03\bin;E:\oracle\product\10
.2.0\client_1\bin;C:\Program Files\Common Files\NetSarang;C:\WINDOWS\system32;C:
\WINDOWS;C:\WINDOWS\System32\Wbem;F:\bea\jdk142_05\bin;C:\PROGRA~1\IBM\CLIENT~1;
C:\PROGRA~1\IBM\CLIENT~1\Shared;C:\PROGRA~1\IBM\CLIENT~1\Emulator;
* 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 *
D:\bea1\user_projects_cluster\mydomain>"d:\bea1\jdk131_03\bin\java" -hotspot -Xm
s32m -Xmx200m -Dweblogic.security.SSL.trustedCAKeyStore=d:\bea1\weblogic700\serv
er\lib\cacerts -Dweblogic.Name="server2" -Dbea.home="d:\bea1" -Dweblogic.managem
ent.username= -Dweblogic.management.password= -Dweblogic.management.server="10.1
6.96.21:7001" -Dweblogic.ProductionModeEnabled= -Djava.security.policy="d:\bea1\
weblogic700\server\lib\weblogic.policy" weblogic.Server
<Sep 20, 2007 1:47:13 PM IST> <Info> <Security> <090065> <Getting boot identity
from user.>
Enter username to boot WebLogic server:weblogic
Enter password to boot WebLogic server:
Starting WebLogic Server...
Connecting to http://10.16.96.21:7001...
<Sep 20, 2007 1:47:25 PM IST> <Notice> <Security> <090082> <Security initializin
g using realm myrealm.>
<Sep 20, 2007 1:47:25 PM IST> <Notice> <WebLogicServer> <000328> <Starting WebLo
gic Managed Server "server2" for domain "mydomain">
Starting Cluster Service...
<Sep 20, 2007 1:47:46 PM IST> <Notice> <Cluster> <000138> <Listening for announc
ements from cluster mycluster on 237.0.0.1:7777>
<Sep 20, 2007 1:47:46 PM IST> <Notice> <Cluster> <000133> <Waiting to synchroniz
e with other running members of mycluster>
<Sep 20, 2007 1:48:16 PM IST> <Notice> <Cluster> <000134> <Discovered and synchr
onized with 1 other running members of mycluster>
<Sep 20, 2007 1:48:17 PM IST> <Emergency> <WebLogicServer> <000350> <Unable to c
reate a server socket on Channel Default for: 10.16.96.24/10.16.96.24, port: 900
1. java.net.BindException: Cannot assign requested address: JVM_Bind Perhaps the
address 10.16.96.24/10.16.96.24 is incorrect or another process is using port 9
001.>
<Sep 20, 2007 1:48:18 PM IST> <Emergency> <Security> <090085> <Server failed to
bind to any port such that it is not reachable from the console.>
<Sep 20, 2007 1:48:18 PM IST> <Emergency> <WebLogicServer> <000342> <Unable to i
nitialize the server: Fatal initialization exception>
The WebLogic Server did not start up properly.
Reason: Fatal initialization exception
D:\bea1\user_projects_cluster\mydomain>goto finish
D:\bea1\user_projects_cluster\mydomain>ENDLOCAL
D:\bea1\user_projects_cluster\mydomain>ENDLOCAL
D:\bea1\user_projects_cluster\mydomain> -
Stop of Weblogic Server- WLS_Forms !
Hi all,
I m working on Forms/reports 11gr2 64-bit with Weblogic Server 10.3.6.
To stop of Weblogic Server - WSL_Forms/Reports, it has two option;
1. Stop Weblogic Server - WLS_FORMS (option under Classic Instance/Form Services)., which asks for username & password,process successfully without
any error/message, but actually Forms are not stopped, what does it mean. So I use second option.
2. Close button of Start Weblogic Server - WLS_FORMS window, which doesn't ask for username & password and suddenly stops it.
(same in case of REPORTS)
Is there any difference and which option is better ?
Thanks.
TekMilan.Hi Roberto!
First thing is that I want to stop my managed weblogic server.
Secondly,I have two options to stop my WLS_FORMS or WLS_REPORTS;
1. No, path is $WLHOME/domains/ClassicDomain/bin/stopManagedWebLogic.cmd.
it runs successfully, but doesn't stop my FORMS.
2. Yes, Windows (of above script) menu option to stop WLS_Forms.
it stops FORMS suddenly & successfully without asking for username/password ?
I m using 2. option successfully without any problem.
I want to know about the followings;
-- Is 2.option is ok ?
-- Why FORMS are now stopped by above 1. option ?
Thanks/Regards.
Milan -
Multicast Exception when starting a managed weblogic server.
I receive a Multicast Exception when i try to start a managed weblogic server from the same machine on which my admin server is running.
when i try to start a managed server from another machine then it does not allow me to do so.
please help,
Manish.
see Sanjeev Chopra's response on 10/25/00 , subject named "
weblogic.admin.host -- missing
property"...
Kumar
John Kelvie wrote:
I am having the same problem...any suggestions?
"Srividhya" <[email protected]> wrote in message
news:3a107849$[email protected]..
Hi All,
While starting the weblogic managed server, i get the following error:
Starting WebLogic Server ....
<Mon Nov 13 17:50:12 EST 2000> <Warning> <Management> <Unrecognizedproperty: ad
min.host>
<Mon Nov 13 17:50:15 EST 2000> <Error> <Configuration Management> <Errorconnect
ing to admin server and initializing admin home: admin URL:t3://kerala:7001
javax.naming.ServiceUnavailableException. Root exception isjava.rmi.NoSuchObje
ctException: The object identified by [3] could not because found. Eitherit was
has not been exported or it has been collected by the distributed garbagecolle
ctor.
atweblogic.rmi.internal.OIDManager.getServerReference(OIDManager.java:3
78)
atweblogic.jndi.WLInitialContextFactoryDelegate.newLocalContext(WLIniti
alContextFactoryDelegate.java:306)
atweblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialCon
textFactoryDelegate.java:261)
atweblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:230)
at weblogic.jndi.Environment.getContext(Environment.java:129)
atweblogic.jndi.Environment.getInitialContext(Environment.java:112)
atweblogic.management.Admin.initializeRemoteAdminHome(Admin.java:712)
at weblogic.management.Admin.start(Admin.java:295)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:357)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
at weblogic.Server.main(Server.java:32)
On the admin server, it does not give any error.
What could be the reason?
Regards,
Srividhya -
Failed to start Oracle Weblogic Server node in 11g
Hello friends,
I have a problem starting the Weblogic Server node Oracle 11g (10.3.5).
Any suggestions to solve the problem
Logs----------------------------------------------------------------------------------
<Nov 3, 2011 12:33:03 PM> <INFO> <NodeManager> <Server output log file is '/opt/middleware/user_projects/domains/DomainOWL/servers/Server01/logs/Server01.out'>
<Nov 3, 2011 12:33:07 PM PET> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Nov 3, 2011 12:33:07 PM PET> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Nov 3, 2011 12:33:11 PM PET> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 19.1-b02 from Sun Microsystems Inc.>
<Nov 3, 2011 12:33:18 PM PET> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<Nov 3, 2011 12:33:24 PM PET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Nov 3, 2011 12:33:24 PM PET> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Nov 3, 2011 12:33:25 PM PET> <Notice> <Log Management> <BEA-170019> <The server log file /opt/middleware/user_projects/domains/DomainOWL/servers/Server01/logs/Server01.log is opened. All server side log events will be written to this file.>
<Nov 3, 2011 12:33:25 PM PET> <Warning> <NodeManager> <BEA-300043> <Node manager native library not found - server process id not saved.>
<Nov 3, 2011 12:33:26 PM PET> <Error> <Socket> <BEA-000438> <Unable to load performance pack. Using Java I/O instead. Please ensure that a native performance library is in: '"/opt/jdk1.6.0/jre/lib/sparcv9/server:/opt/jdk1.6.0/jre/lib/sparcv9:/opt/jdk1.6.0/jre/../lib/sparcv9:/opt/middleware/patch_wls1035/profiles/default/native:/opt/middleware/patch_ocp360/profiles/default/native:/opt/middleware/wlserver_10.3/server/native/solaris/sparc64:/opt/middleware/wlserver_10.3/server/native/solaris/sparc64:/opt/middleware/wlserver_10.3/server/native/solaris/sparc64/oci920_8:/usr/jdk/packages/lib/sparcv9:/lib/64:/usr/lib/64"'
>
<Nov 3, 2011 12:33:37 PM PET> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Nov 3, 2011 12:33:40 PM PET> <Warning> <Store> <BEA-280101> <The persistent file store "_WLS_Server01" is forced to use buffered I/O and so may have significantly degraded performance. Either the OS/hardware environment does not support the chosen write policy or the native wlfileio library is missing. See store open log messages for the requested and final write policies. See the documentation on store synchronous write policy configuration for advice.>
<Nov 3, 2011 12:33:49 PM PET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Nov 3, 2011 12:33:49 PM PET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Nov 3, 2011 12:33:56 PM PET> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<Nov 3, 2011 12:33:56 PM PET> <Notice> <Cluster> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>
<Nov 3, 2011 12:33:56 PM PET> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of oimClusterT.>
<Nov 3, 2011 12:34:26 PM PET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Nov 3, 2011 12:34:27 PM PET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<Nov 3, 2011 12:34:27 PM PET> <Notice> <Cluster> <BEA-000162> <Starting "async" replication service with remote cluster address "null">
<Nov 3, 2011 12:34:31 PM PET> <Notice> <Security> <BEA-090171> <Loading the identity certificate and private key stored under the alias DemoIdentity from the jks keystore file /opt/middleware/wlserver_10.3/server/lib/DemoIdentity.jks.>
<Nov 3, 2011 12:34:31 PM PET> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/middleware/wlserver_10.3/server/lib/DemoTrust.jks.>
<Nov 3, 2011 12:34:31 PM PET> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/jdk1.6.0/jre/lib/security/cacerts.>
<Nov 3, 2011 12:34:33 PM PET> <Alert> <Security> <BEA-090152> <Demo trusted CA certificate is being used in production mode: [
Version: V3
Subject: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
Key: SunPKCS11-Solaris RSA public key, 512 bits (id 58638024, session object)
modulus: 9550192877869244258838480703390456015046425375252278279190673063544122510925482179963329236052146047356415957587628011282484772458983977898996276815440753
public exponent: 65537
Validity: [From: Thu Mar 21 15:12:27 PET 2002,
To: Tue Mar 22 15:12:27 PET 2022]
Issuer: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
SerialNumber: [ 33f10648 fcde0deb 4199921f d64537f4]
Certificate Extensions: 1
[1]: ObjectId: 2.5.29.15 Criticality=true
KeyUsage [
Key_CertSign
Algorithm: [MD5withRSA]
Signature:
0000: 9D 26 4C 29 C8 91 C3 A7 06 C3 24 6F AE B4 F8 82 .&L)......$o....
0010: 80 4D AA CB 7C 79 46 84 81 C4 66 95 F4 1E D8 C4 .M...yF...f.....
0020: E9 B7 D9 7C E2 23 33 A4 B7 21 E0 AA 54 2B 4A FF .....#3..!..T+J.
0030: CB 21 20 88 81 21 DB AC 90 54 D8 7D 79 63 23 3C .! ..!...T..yc#<
] The system is vulnerable to security attacks, since it trusts certificates signed by the demo trusted CA.>
<Nov 3, 2011 12:34:33 PM PET> <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.>
<Nov 3, 2011 12:34:33 PM PET> <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.>
<Nov 3, 2011 12:34:34 PM PET> <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.>
<Nov 3, 2011 12:34:34 PM PET> <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.>
<Nov 3, 2011 12:34:34 PM PET> <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.>
<Nov 3, 2011 12:34:34 PM PET> <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.>
<Nov 3, 2011 12:34:34 PM PET> <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.>
<Nov 3, 2011 12:34:34 PM PET> <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.>
<Nov 3, 2011 12:34:34 PM PET> <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.>
<Nov 3, 2011 12:34:34 PM PET> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure" is now listening on 192.168.1.10:7006 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Nov 3, 2011 12:34:34 PM PET> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.1.10:7005 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Nov 3, 2011 12:34:34 PM PET> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "Server01" for domain "DomainOWL" running in Production Mode>
Exception in thread "[STANDBY] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632)
at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:217)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Exception in thread "[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
Exception in thread "[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
Exception in thread "[ACTIVE] ExecuteThread: '14' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
Exception in thread "[ACTIVE] ExecuteThread: '16' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
<Nov 3, 2011 12:36:27 PM PET> <Error> <HTTP> <BEA-101020> <[ServletContext@15375304[app:bea_wls_deployment_internal module:bea_wls_deployment_internal.war path:/bea_wls_deployment_internal spec-version:null]] Servlet failed with Exception
java.lang.OutOfMemoryError: PermGen space
>
Exception in thread "[ACTIVE] ExecuteThread: '13' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
Exception in thread "Timer-1" java.lang.OutOfMemoryError: PermGen space
Exception in thread "[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
<Nov 3, 2011 12:36:53 PM PET> <Error> <HTTP> <BEA-101020> <[ServletContext@15375304[app:bea_wls_deployment_internal module:bea_wls_deployment_internal.war path:/bea_wls_deployment_internal spec-version:null]] Servlet failed with Exception
java.lang.OutOfMemoryError: PermGen space
>
<Nov 3, 2011 12:36:24 PM PET> <Error> <Socket> <BEA-000405> <Uncaught Throwable in processSockets
java.lang.OutOfMemoryError: PermGen space.
java.lang.OutOfMemoryError: PermGen space
>
<Nov 3, 2011 12:36:33 PM PET> <Error> <JMX> <BEA-149501> <An exception occurred while registering the MBean com.bea:Name=idmAdminServerT,Type=Server at property WebService.
java.lang.OutOfMemoryError: PermGen space
>
Exception in thread "[ACTIVE] ExecuteThread: '21' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
Exception in thread "[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
Exception in thread "[ACTIVE] ExecuteThread: '24' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
java.lang.OutOfMemoryError: PermGen space
Exception in thread "[ACTIVE] ExecuteThread: '17' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
Exception in thread "[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
Exception in thread "[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
<Nov 3, 2011 12:37:16 PM PET> <Warning> <Socket> <BEA-000402> <There are: 5 active sockets, but the maximum number of socket reader threads allowed by the configuration is: 4. You may want to alter your configuration.>
Exception in thread "[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
Exception in thread "[ACTIVE] ExecuteThread: '15' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
Exception in thread "[ACTIVE] ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
Exception in thread "[ACTIVE] ExecuteThread: '25' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
<Nov 3, 2011 12:39:41 PM PET> <Error> <HTTP> <BEA-101216> <Servlet: "CoordinatorPortTypeServlethttp" failed to preload on startup in Web application: "wls-wsat.war".
java.lang.OutOfMemoryError: PermGen space
>
<Nov 3, 2011 12:42:32 PM PET> <Error> <HTTP> <BEA-101017> <[ServletContext@15375304[app:bea_wls_deployment_internal module:bea_wls_deployment_internal.war path:/bea_wls_deployment_internal spec-version:null]] Root cause of ServletException.
java.lang.OutOfMemoryError: PermGen space
>
<Nov 3, 2011 12:43:15 PM PET> <Error> <HTTP> <BEA-101017> <[ServletContext@15375304[app:bea_wls_deployment_internal module:bea_wls_deployment_internal.war path:/bea_wls_deployment_internal spec-version:null]] Root cause of ServletException.
java.lang.OutOfMemoryError: PermGen space
>
<Nov 3, 2011 12:43:26 PM PET> <Error> <Socket> <BEA-000405> <Uncaught Throwable in processSockets
java.lang.OutOfMemoryError: PermGen space.
java.lang.OutOfMemoryError: PermGen space
>
Exception in thread "[ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
java.lang.OutOfMemoryError: PermGen space
Exception in thread "[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
java.lang.OutOfMemoryError: PermGen space
Exception in thread "[STANDBY] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
<Nov 3, 2011 12:45:53 PM PET> <Error> <HTTP> <BEA-101017> <[ServletContext@15375304[app:bea_wls_deployment_internal module:bea_wls_deployment_internal.war path:/bea_wls_deployment_internal spec-version:null]] Root cause of ServletException.
java.lang.OutOfMemoryError: PermGen space
>
Exception in thread "[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
Exception in thread "[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
Exception in thread "[ACTIVE] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
java.lang.OutOfMemoryError: PermGen space
Exception in thread "[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
Exception in thread "[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
Exception in thread "weblogic.timers.TimerThread" java.lang.OutOfMemoryError: PermGen space
Thanks<Nov 4, 2011 11:42:08 AM PET> <Error> <Socket> <BEA-000405> <Uncaught Throwable in processSockets
java.lang.OutOfMemoryError: PermGen space.
java.lang.OutOfMemoryError: PermGen space
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632)
at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
Truncated. see log file for complete stacktrace
>
<Nov 4, 2011 11:42:34 AM PET> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.OutOfMemoryError: PermGen space
java.lang.OutOfMemoryError: PermGen space
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2427)
at java.lang.Class.getDeclaredMethod(Class.java:1935)
at java.io.ObjectStreamClass.getInheritableMethod(ObjectStreamClass.java:1349)
at java.io.ObjectStreamClass.access$2200(ObjectStreamClass.java:52)
Truncated. see log file for complete stacktrace
>
The WebLogic Server encountered a critical failure
Reason: PermGen space
Exception in thread "[ACTIVE] ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
Exception in thread "main" java.lang.OutOfMemoryError: PermGen space
Exception in thread "[ACTIVE] ExecuteThread: '14' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
Exception in thread "[ACTIVE] ExecuteThread: '15' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
Exception in thread "[ACTIVE] ExecuteThread: '25' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
Exception in thread "[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
Exception in thread "[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
<Nov 4, 2011 11:44:08 AM PET> <Warning> <Socket> <BEA-000402> <There are: 5 active sockets, but the maximum number of socket reader threads allowed by the configuration is: 4. You may want to alter your configuration.>
Exception in thread "[ACTIVE] ExecuteThread: '27' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
Exception in thread "[ACTIVE] ExecuteThread: '21' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
Exception in thread "[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
Exception in thread "[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
Exception in thread "[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
<Nov 4, 2011 11:44:43 AM PET> <Error> <Socket> <BEA-000405> <Uncaught Throwable in processSockets
java.lang.OutOfMemoryError: PermGen space.
java.lang.OutOfMemoryError: PermGen space
I made the change and continue with the same problem, you can tell me which file should make this change, very grateful -
**** ASSERTION FAILED **** Error while starting WebLogic Server 7.0
Hi,
I am getting following error while starting WebLogic Server 7.0 for the first
time. Can anybody help me it this?
Error is:
==================================================
Enter username to boot WebLogic server:system
Enter password to boot WebLogic server:
Starting WebLogic Server...
<May 9, 2003 4:27:47 PM IST> <Notice> <Management> <140005> <Loading configurati
on C:\bea\user_projects\mydomain\.\config.xml>
<May 9, 2003 4:28:04 PM IST> <Notice> <Security> <090082> <Security initializing
using realm myrealm.>
<May 9, 2003 4:28:04 PM IST> <Notice> <WebLogicServer> <000327> <Starting WebLogic
Admin Server "myserver" for domain "m
ydomain">
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot intialize
Resource Manager Connection Factory resour
ces because could not get JNDI context: javax.naming.ServiceUnavailableException
[Root exception is java.net.UnknownHost
Exception: Unknown protocol: 'JNP'] ]
at weblogic.j2ee.RMCFactoryDeployer.<init>(RMCFactoryDeployer.java:50)
at weblogic.j2ee.J2EEService.initialize(J2EEService.java:93)
at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
<May 9, 2003 4:28:14 PM IST> <Emergency> <WebLogicServer> <000342> <Unable to
initialize the server: Fatal initializatio
n exception
Throwable: weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot
intialize Resource Manager Connection Fac
tory resources because could not get JNDI context: javax.naming.ServiceUnavailableException
[Root exception is java.net.
UnknownHostException: Unknown protocol: 'JNP'] ]
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot intialize
Resource Manager Connection Factory resour
ces because could not get JNDI context: javax.naming.ServiceUnavailableException
[Root exception is java.net.UnknownHost
Exception: Unknown protocol: 'JNP'] ]
at weblogic.j2ee.RMCFactoryDeployer.<init>(RMCFactoryDeployer.java:50)
at weblogic.j2ee.J2EEService.initialize(J2EEService.java:93)
at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
>
==================================================I don't know what could cause this error.
I would suggest you take this upto [email protected]
Kumar
Ajay Jadhav wrote:
Hi,
I am getting following error while starting WebLogic Server 7.0 for the first
time. Can anybody help me it this?
Error is:
==================================================
Enter username to boot WebLogic server:system
Enter password to boot WebLogic server:
Starting WebLogic Server...
<May 9, 2003 4:27:47 PM IST> <Notice> <Management> <140005> <Loading configurati
on C:\bea\user_projects\mydomain\.\config.xml>
<May 9, 2003 4:28:04 PM IST> <Notice> <Security> <090082> <Security initializing
using realm myrealm.>
<May 9, 2003 4:28:04 PM IST> <Notice> <WebLogicServer> <000327> <Starting WebLogic
Admin Server "myserver" for domain "m
ydomain">
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot intialize
Resource Manager Connection Factory resour
ces because could not get JNDI context: javax.naming.ServiceUnavailableException
[Root exception is java.net.UnknownHost
Exception: Unknown protocol: 'JNP'] ]
at weblogic.j2ee.RMCFactoryDeployer.<init>(RMCFactoryDeployer.java:50)
at weblogic.j2ee.J2EEService.initialize(J2EEService.java:93)
at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
<May 9, 2003 4:28:14 PM IST> <Emergency> <WebLogicServer> <000342> <Unable to
initialize the server: Fatal initializatio
n exception
Throwable: weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot
intialize Resource Manager Connection Fac
tory resources because could not get JNDI context: javax.naming.ServiceUnavailableException
[Root exception is java.net.
UnknownHostException: Unknown protocol: 'JNP'] ]
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot intialize
Resource Manager Connection Factory resour
ces because could not get JNDI context: javax.naming.ServiceUnavailableException
[Root exception is java.net.UnknownHost
Exception: Unknown protocol: 'JNP'] ]
at weblogic.j2ee.RMCFactoryDeployer.<init>(RMCFactoryDeployer.java:50)
at weblogic.j2ee.J2EEService.initialize(J2EEService.java:93)
at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
================================================== -
Hi,
We have Weblogic and SOA server installed and is in non-clustered (Standalone Environment).
We are in process to stop and start the env, what follow below steps.
1) Stop Managed Server via console.
2) Stop Admin server using stopWeblogic.sh
Is this the right approach or do we need to follow different?
Also, do we need to touch node manager ?
Regards
KumarHi Kumar,
Yes , You can follow the process which you have shared ie
1) Stop Managed Server via console.
2) Stop Admin server using stopWeblogic.sh
Once stopping All the managed servers and admin server..try this command
ps -ef|grep weblogic
This will show if there are any other weblogic process running on the server.
(Stop the node manager as well)
For starting the env
*1)Start the weblogic Admin server using startWeblogic.sh*
*2)As ur starting the managed server through console,start the node manager-->Startnodemanger.sh* check from the console whether its reachable or not
*3)Start the all managed servers from front end.*
You can even follow the below Oracle Document for the same..
http://docs.oracle.com/cd/E11035_01/wls100/server_start/server_startTOC.html
Regards
Fabian -
PL/SQL Web Service fails when deployed to WebLogic server
I have a web service generated via JDeveloper from a PL/SQL package. It runs fine both when tested in JDeveloper and when the WAR file is manually deployed to the Integrated WebLogic Server. However, when the WAR file is deployed to our actual WebLogic server, it fails. Other existing web services that were not generated with the JDeveloper wizard work correctly. I am having trouble finding any references to this type of issue to solve it. Are there any ideas what might be causing the WSDL to fail?
References:
* JDeveloper 11.1.1.6.
* No proxies are involved.
* The PLSQL package is a basic function that returns varchar2 input fed in by one parameter:
create or replace package body pkg_ws_test as
function test_me (p_anything_in varchar2)
return varchar2 is
begin
return p_anything_in;
end test_me;
end pkg_ws_test;
* Top of error stack is as follows:
oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: WSDLException: faultCode=OTHER_ERROR: Failed to read WSDL from http://svr:8892/wsTest2-getSame-context-root/TestMePort?wsdl: HTTP connection error code is 500 at oracle.sysman.emSDK.webservices.wsdlparser.ParsedWSDLFactoryImpl.getParsedWSDL(ParsedWSDLFactoryImpl.java:157) at oracle.sysman.emSDK.webservices.wsdlparser.ParsedWSDLFactoryImpl.getParsedWSDL(ParsedWSDLFactoryImpl.java:87) at oracle.sysman.emas.model.wsmgt.WSTestModel.init(WSTestModel.java:325) at
...Hi,
The below error trace you've provided doesn't confirm that Weblogic server has thrown the error.
oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: WSDLException: faultCode=OTHER_ERROR: Failed to read WSDL from http://svr:8892/wsTest2-getSame-context-root/TestMePort?wsdl: HTTP connection error code is 500 at oracle.sysman.emSDK.webservices.wsdlparser.ParsedWSDLFactoryImpl.getParsedWSDL(ParsedWSDLFactoryImpl.java:157) at oracle.sysman.emSDK.webservices.wsdlparser.ParsedWSDLFactoryImpl.getParsedWSDL(ParsedWSDLFactoryImpl.java:87) at oracle.sysman.emas.model.wsmgt.WSTestModel.init(WSTestModel.java:325) at
Please paste complete stacktrace of the error to check and also include the caused by section in the error.
Thanks,
Vijaya -
Starting the managed weblogic server
Hi All,
While starting the weblogic managed server, i get the following error:
Starting WebLogic Server ....
<Mon Nov 13 17:50:12 EST 2000> <Warning> <Management> <Unrecognized property: ad
min.host>
<Mon Nov 13 17:50:15 EST 2000> <Error> <Configuration Management> <Error connect
ing to admin server and initializing admin home: admin URL: t3://kerala:7001
javax.naming.ServiceUnavailableException. Root exception is java.rmi.NoSuchObje
ctException: The object identified by [3] could not because found. Either it was
has not been exported or it has been collected by the distributed garbage colle
ctor.
at weblogic.rmi.internal.OIDManager.getServerReference(OIDManager.java:3
78)
at weblogic.jndi.WLInitialContextFactoryDelegate.newLocalContext(WLIniti
alContextFactoryDelegate.java:306)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialCon
textFactoryDelegate.java:261)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:230)
at weblogic.jndi.Environment.getContext(Environment.java:129)
at weblogic.jndi.Environment.getInitialContext(Environment.java:112)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:712)
at weblogic.management.Admin.start(Admin.java:295)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:357)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
at weblogic.Server.main(Server.java:32)
>
On the admin server, it does not give any error.
What could be the reason?
Regards,
Srividhyasee Sanjeev Chopra's response on 10/25/00 , subject named "
weblogic.admin.host -- missing
property"...
Kumar
John Kelvie wrote:
I am having the same problem...any suggestions?
"Srividhya" <[email protected]> wrote in message
news:3a107849$[email protected]..
Hi All,
While starting the weblogic managed server, i get the following error:
Starting WebLogic Server ....
<Mon Nov 13 17:50:12 EST 2000> <Warning> <Management> <Unrecognizedproperty: ad
min.host>
<Mon Nov 13 17:50:15 EST 2000> <Error> <Configuration Management> <Errorconnect
ing to admin server and initializing admin home: admin URL:t3://kerala:7001
javax.naming.ServiceUnavailableException. Root exception isjava.rmi.NoSuchObje
ctException: The object identified by [3] could not because found. Eitherit was
has not been exported or it has been collected by the distributed garbagecolle
ctor.
atweblogic.rmi.internal.OIDManager.getServerReference(OIDManager.java:3
78)
atweblogic.jndi.WLInitialContextFactoryDelegate.newLocalContext(WLIniti
alContextFactoryDelegate.java:306)
atweblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialCon
textFactoryDelegate.java:261)
atweblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:230)
at weblogic.jndi.Environment.getContext(Environment.java:129)
atweblogic.jndi.Environment.getInitialContext(Environment.java:112)
atweblogic.management.Admin.initializeRemoteAdminHome(Admin.java:712)
at weblogic.management.Admin.start(Admin.java:295)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:357)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
at weblogic.Server.main(Server.java:32)
On the admin server, it does not give any error.
What could be the reason?
Regards,
Srividhya -
Failed EAR deployment in WebLogic Server - Unexpected exception caught
Hello
I have a problem when deployment EAR file in WebLogic server, my application use KODO for persistence.
This error only occurs when deployment from EAR file, when deployment from simple webapp directory the error not occurs.
In properties variable load attributes of database connection from jdo.properties file
PersistenceManagerFactory pmf = JDOHelper.getPersistenceManagerFactory(properties);
javax.jdo.JDOFatalInternalException: Unexpected exception caught.
at javax.jdo.JDOHelper.invokeGetPersistenceManagerFactoryOnImplementation(JDOHelper.java:1193)
at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:808)
at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:701)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:376)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:82)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1616)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2761)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:889)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:333)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:139)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:815)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1222)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:433)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
NestedThrowablesStackTrace:
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at javax.jdo.JDOHelper$16.run(JDOHelper.java:1965)
at java.security.AccessController.doPrivileged(Native Method)
at javax.jdo.JDOHelper.invoke(JDOHelper.java:1960)
at javax.jdo.JDOHelper.invokeGetPersistenceManagerFactoryOnImplementation(JDOHelper.java:1166)
at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:808)
at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:701)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:376)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:82)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1616)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2761)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:889)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:333)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:139)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:815)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1222)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:433)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Caused by: <1.0.0-SNAPSHOT-SNAPSHOT fatal internal error> org.apache.openjpa.util.InternalException: There was an error when invoking the static getInstance method on the named factory class "kodo.jdb
c.kernel.KodoJDBCBrokerFactory". See the nested exception for details.
at org.apache.openjpa.kernel.Bootstrap.getBrokerFactory(Bootstrap.java:93)
at kodo.jdo.PersistenceManagerFactoryImpl.getPersistenceManagerFactory(PersistenceManagerFactoryImpl.java:41)
at kodo.jdbc.runtime.JDBCPersistenceManagerFactory.getPersistenceManagerFactory(JDBCPersistenceManagerFactory.java:22)
... 52 more
Thanks for help.I managed to resolve the issue myself. Here are the details, in case anyone is interested:
I modified the weblogic-application.xml (present under my application EAR>META-INF folder) to include org.hibernate.* and javax.persistence.* packages. Restarted the servers and redeployed the EAR (exploded). I don't see the errors anymore and the deployment was successful.
<prefer-application-packages>
<package-name>org.hibernate.*</package-name>
<package-name>javax.persistence.*</package-name>
</prefer-application-packages> -
How to install a managed weblogic server ?
Hello,
I am new to weblogic server installation.
I have spent a few days reading the installation document.
I have installed a default server successfully, and I want to install a new
machine
running as a managed server.
The BEA installation guide didn't explain clearly how a new managed is to be
installed.
Do I need to use the same procedure: download the installer from bea
website, then
create a bea home directory on the new machine, and create a new product
directory
on the new machine ?
What about the license on the new managed server ? Do I need a separate
license.bea
installed on the new managed server ? Since I need a new managed server, it
should
have its own BEA home directory, its own product directory, and it own
license.
Am I right on this ?
Thank you for any information that can help me.
Regards,
Frank HsuFrank,
You will need to install the software on each machine, unless you are using NFS
mounts. Each machine will need its own license, and the entries can be in the
same license.bea file that is shared across all machines.
Thanks,
Simon
Cheng Chung Hsu wrote:
Hello,
I am new to weblogic server installation.
I have spent a few days reading the installation document.
I have installed a default server successfully, and I want to install a new
machine
running as a managed server.
The BEA installation guide didn't explain clearly how a new managed is to be
installed.
Do I need to use the same procedure: download the installer from bea
website, then
create a bea home directory on the new machine, and create a new product
directory
on the new machine ?
What about the license on the new managed server ? Do I need a separate
license.bea
installed on the new managed server ? Since I need a new managed server, it
should
have its own BEA home directory, its own product directory, and it own
license.
Am I right on this ?
Thank you for any information that can help me.
Regards,
Frank Hsu -
Problem in starting Managed weblogic server
Hi,
I have Weblogic 8.1 with SP4 in production mode with admin server(port :7001) & managed server(port:7004) configured as a Windows services.
so when ever i Restarted the windows service of the managed server. The ear previously got deployed is not getting Redeployed once the service is up again
My requirement is if i stop and start the service for the Managed server the ear which is ther in that should be deployed so can this happen with weblogic
it is throwing an exception as
javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://10.1.134.117:7004: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination]at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:47)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:636)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:306)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:239)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
can any one help me out
regards
SudhakarAny solutions for this?
-
Stop managed server without node manager and admin server
What are the commonly used ways to stop managed Weblogic server without node manager running and without administration server running?
(I have only one solution: on the managed server startup dump process ID to a file, and then when I want to stop it, send a signal to this process ID and kill JVM. But it seems not very clean way.)
(The managed server is started when both node manager and admin server are down, and I provide boot.properties of admin server to the managed server to start.)
UPDATED: And I don't want to start neither admin server, nor node manager even temporarily.
Edited by: user12163080 on Jun 24, 2010 4:40 AMHai,
I read the Oracle weblogic wlst script document without Admin server you cannot connect the managed server through the WLST script. see the below lines
"The start command starts Managed Servers or clusters in a domain using Node Manager.
To use the start command, WLST must be connected to a running Administration Server.
To start Managed Servers without requiring a running Administration Server, use the
nmStart command with WLST connected to Node Manager."
"You shut down a server to which WLST is connected by entering the shutdown command
without any arguments.
When connected to a Managed Server instance, you only use the shutdown command to shut
down the Managed Server instance to which WLST is connected; you cannot shut down another
server while connected to a Managed Server instance.
WLST uses Node Manager to shut down a Managed Server. When shutting down a Managed
Server, Node Manager must be running.
In the event of an error, the command returns"
They are two option if you are using adminserver then we can stop the any Managed server.
The option is if you are using the nodemanager without admin server we can stop the any Managed server.
The last final solution to kill the particular Managed server pid.
Regards,
S.vinoth babu -
Error on installing Oracle Identity Manager 9.1.0.1 in WebLogic Server 11g
Hello friends.
Can you help solve this case:
I installed Oracle 9.1.0.1 on Oracle Identity Manager Weblogic Server 11g, completing the installation with the following errors: attach the log so I can guide the solution.
link of the complete log
http://textbin.com/1c824
Part of the log**************************************
With the Partitioning, OLAP, Data Mining and Real Application Testing options".>
####<Sep 30, 2011 4:23:04 PM PET> <Info> <JDBC> <idm9> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1317417784538> <BEA-001517> <Connection Pool "xlXADS" using Driver: "Oracle JDBC driver", Version: "11.2.0.2.0".>
####<Sep 30, 2011 4:23:18 PM PET> <Info> <Common> <idm9> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1317417798143> <BEA-000628> <Created "30" resources for pool "xlXADS", out of which "30" are available and "0" are unavailable.>
####<Sep 30, 2011 4:23:18 PM PET> <Info> <JDBC> <idm9> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1317417798147> <BEA-001124> <Created Connection Pool named xlXADS.>
####<Sep 30, 2011 4:23:24 PM PET> <Error> <Store> <idm9> <AdminServer> <[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1317417804279> <BEA-280061> <The persistent store "AdminServer_OIM_JDBCSTORE" could not be deployed: weblogic.store.PersistentStoreException: Can't find JDBC DataSource jdbc/xlDS: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
weblogic.store.PersistentStoreException: Can't find JDBC DataSource jdbc/xlDS: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:107)
at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:186)
at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:164)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:59)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:240)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188)
at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492)
at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
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:411)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:102)
at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:186)
at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:164)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:59)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:187)
at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:491)
at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:137)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<Sep 30, 2011 4:23:24 PM PET> <Warning> <Management> <idm9> <AdminServer> <[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1317417804321> <BEA-141197> <The deployment of AdminServer_OIM_JDBCSTORE failed.
weblogic.management.DeploymentException:
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:62)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188)
at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492)
at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
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:411)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:102)
at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:186)
at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:164)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:59)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:187)
at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:491)
at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:137)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<Sep 30, 2011 4:23:24 PM PET> <Error> <JMS> <idm9> <AdminServer> <[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1317417804381> <BEA-040123> <Failed to start JMS Server "AdminServer_OIM_JMSSERVER" due to weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist.
weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist
at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:313)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:200)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:240)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188)
at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492)
at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<Sep 30, 2011 4:23:24 PM PET> <Warning> <Management> <idm9> <AdminServer> <[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1317417804385> <BEA-141197> <The deployment of AdminServer_OIM_JMSSERVER failed.
weblogic.management.DeploymentException: Internalrror activating the JMS Server AdminServer_OIM_JMSSERVER: weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:215)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188)
at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492)
at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist
at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:313)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:200)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:240)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188)
at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492)
at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
ThanksHi Kevin,
Make your suggestion, delete the domain and reinstall Oracle Identity Manager, the result was the same error, this happens when I start the xlStartServer.sh
Exception in thread "QuartzWorkerThread-2" java.lang.OutOfMemoryError: PermGen space
at java.lang.reflect.Proxy.defineClass0(Native Method)
at java.lang.reflect.Proxy.getProxyClass(Proxy.java:504)
at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:581)
at com.thortech.xl.dataaccess.tcDataBaseClient.bindToInstance(Unknown Source)
at com.thortech.xl.dataaccess.tcDataBaseClient.<init>(Unknown Source)
at com.thortech.xl.server.tcDataBaseClient.<init>(Unknown Source)
at com.thortech.xl.client.dataobj.tcDataBaseClient.<init>(Unknown Source)
at com.thortech.xl.scheduler.core.quartz.QuartzWrapper$TaskExecutionAction.run(Unknown Source)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.security.Security.runAs(Security.java:41)
at Thor.API.Security.LoginHandler.weblogicLoginSession.runAs(Unknown Source)
at com.thortech.xl.scheduler.core.quartz.QuartzWrapper.execute(Unknown Source)
at org.quartz.core.JobRunShell.run(JobRunShell.java:178)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:477)
CJava HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
^CJava HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
Exception in thread "QuartzScheduler_NON_CLUSTERED_MisfireHandler" java.lang.OutOfMemoryError: PermGen space
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
java.lang.OutOfMemoryError: PermGen space
^CJava HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
Exception in thread "[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
java.lang.OutOfMemoryError: PermGen space
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
Thanks
Edited by: JLK on Oct 2, 2011 11:35 PM
Edited by: JLK on Oct 2, 2011 11:37 PM
Maybe you are looking for
-
I am using Adobe X Standard to create PDF documents from Word (version 2010). I have a hyperlink in the footer in the word document. After conversion to PDF this link does not work. I have seen forums and they say that this bug was fixed in Adobe 7,
-
Document Class not work when I shift my MovieClip to 2nd Frame.
Hello, All my content is at 1st frame of my FLA file...and I'm using Document Class... When I try to shift my content to 2nd frame, so I can use 1st frame for preloader.. but its not working... This is my document class... Basically at 1st frame I'm
-
I have been trying to update itunes but i keep getting a runtime error. i have been working on this for 2 hours and cannot find anything in the community to help
-
Error Startup screen Flash on a Mac has an error
Hi there, I have a problem by starting Flash 8. When the startup-screen appears I see after a few secounds the flash logo on white ground in the upper left corner. Is that maybe a problem with the xml content on the startup page? ... I use a mac with
-
Complex problem: 802.11n, Bluetooth, Iphone 4 and Magic pheripherals...
Hi folks, My hardware: - Macbook Pro with Apple LED Cinema Display - Magic Mouse, Trackpad and Wireless Keyboard - Time Capsule as WiFi Router - Apple TV - Iphone 4 - Airport Express as WiFi printer connection My problem: - As known, time machine bac