Weblogic Server config.xml

When does the Config.xml gets corrupted???. The weblogic server failed to start because of the corrupted config.xml file. I saw the config file its was empty. I replaced it with config.xml.booted and it worked fine. Can anybody explain in what circumstances does this file gets corrupted.

Hi Krishna,
Which version and service pack of Workshop and WLS 8.1 are you using ? Also can you attach the corrupt config.xml file ?
Did the server restart successfully ?
Was there anything abnormal in the last the shutdown prior to the corruption ?
Thanks
Raj

Similar Messages

Possible to add and persist elements in server config, for use by cons ext?

I'm considering what will be my obstacles if I try to write a console extension that we would use to view excerpts of an application log file, the application of which is deployed to each server in our domain(s). It doesn't log to the WebLogic server log, it writes it to an external log file (through log4j), and each server (several servers on each box) uses a slightly different path to its log file.
One issue that I'll have is getting the console extension to know what the path to the log file is. I think the best way, over all, is just to have the user enter the path in the form presented by the console extension. My problem is how to persist that setting, because I'd prefer they didn't have to enter that every time they entered the form.
Several years ago, I wrote a console extension for WL 8.1.4 which had a similar issue. I ended up simply writing the setting into a properties file inside the extension WAR. This only works (I believe) if the WAR is deployed exploded. I could do that, but I don't like that idea very much.
What would be nice is if I could "extend" the server config.xml with an additional element in the "Server" element, where I could store this information. Unfortunately, I don't see any support for doing something like that.
Another alternative I'm considering is whether it's possible to extend the "Summary of Log Files" page in "Diagnostics" with an application-specific log file, but I don't see any way to do that.

Well, I appreciate the suggestion, but it's not exactly a secret, to me at least. I've used it for human-readable things recently. It occurred to me that that might be my only option, but I certainly wasn't going to assume that. As it seems like this is likely my only option, I guess I can see some interesting conventions for dealing with this. You have to assume that the field could be written to by other code, and that code would have to make the same assumption. I guess I'd have to define a certain XML element as the root of my structure. If I find it, that region between the start and end element is mine to use and modify. If I don't find it, I'll insert my element at the end of the field value.

How to specify the webLogic server startup script to use different config.xml file ??

Hi,
I have 2 weblogic startup scripts (startWebLogic.sh and
startWebLogic_recovery.sh) for the same domain.
startWebLogic.sh uses config.xml file.
I would like to use config_recovery.xml as the configuration file for startWebLogic_recovery.sh
How would I do this ?
I am using WebLogic Server 6.1 on SunOS 5.8 / HP-UX 11.0.
Appreciate any help.
Regards
Gunaseelan Venkateswaran

I guess you're using Weblogic 6.1 with WLCS 3.5. I think you're supposed to work with one config.xml for the same domain, and not have a different config.xml.
To start up different applications or EJBs, use the "target" property to control which applications to start up for the particular instance.
YY

Weblogic 10.0 Parsing Failure in config.xml: failed to load java type

Hello,
I've just installed a Weblogic 10.0 on a Linux server and when i try to start it, by :
bash$ : sudo -u weblogic ./startWebLogic.sh
JAVA Memory arguments: -Xms256m -Xmx512m -XX:MaxPermSize=128m
WLS Start Mode=Production
CLASSPATH=:/opt/weblogic/10.0/patch_wls1002/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/weblogic/10.0/patch_cie640/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/weblogic/10.0/jdk150_15/lib/tools.jar:/opt/weblogic/10.0/weblogic10.0/server/lib/weblogic_sp.jar:/opt/weblogic/10.0/weblogic10.0/server/lib/weblogic.jar:/opt/weblogic/10.0/modules/features/weblogic.server.modules_10.0.2.0.jar:/opt/weblogic/10.0/modules/features/com.bea.cie.common-plugin.launch_2.1.2.0.jar:/opt/weblogic/10.0/weblogic10.0/server/lib/webservices.jar:/opt/weblogic/10.0/modules/org.apache.ant_1.6.5/lib/ant-all.jar:/opt/weblogic/10.0/modules/net.sf.antcontrib_1.0b2.0/lib/ant-contrib.jar::/opt/weblogic/10.0/weblogic10.0/common/eval/pointbase/lib/pbclient51.jar:/opt/weblogic/10.0/weblogic10.0/server/lib/xqrl.jar::
PATH=/opt/weblogic/10.0/weblogic10.0/server/bin:/opt/weblogic/10.0/modules/org.apache.ant_1.6.5/bin:/opt/weblogic/10.0/jdk150_15/jre/bin:/opt/weblogic/10.0/jdk150_15/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/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 *
starting weblogic with Java version:
java version "1.5.0_15"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_15-b04)
Java HotSpot(TM) Server VM (build 1.5.0_15-b04, mixed mode)
Starting WLS with line:
/opt/weblogic/10.0/jdk150_15/bin/java -server -Xms256m -Xmx512m -XX:MaxPermSize=128m -da -Dplatform.home=/opt/weblogic/10.0/weblogic10.0 -Dwls.home=/opt/weblogic/10.0/weblogic10.0/server -Dweblogic.home=/opt/weblogic/10.0/weblogic10.0/server -Dwli.home= -Dweblogic.management.discover=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/opt/weblogic/10.0/patch_wls1002/profiles/default/sysext_manifest_classpath:/opt/weblogic/10.0/patch_cie640/profiles/default/sysext_manifest_classpath -Dweblogic.security.providers.authentication.LDAPDelegatePoolSize=50 -Dweblogic.management.username=system -Dweblogic.management.password=admin9424 -Dweblogic.Name=AdminServer -Djava.security.policy=/opt/weblogic/10.0/weblogic10.0/server/lib/weblogic.policy weblogic.Server
<Jun 7, 2010 9:49:12 AM CEST> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
/opt/weblogic/10.0/weblogic10.0/platform/lib/p13n/p13n-schemas.jar:/opt/weblogic/10.0/weblogic10.0/platform/lib/p13n/p13n_common.jar:/opt/weblogic/10.0/weblogic10.0/platform/lib/p13n/p13n_system.jar:/opt/weblogic/10.0/weblogic10.0/platform/lib/p13n/wlp_services.jar:/opt/weblogic/10.0/weblogic10.0/platform/lib/wlp/netuix_common.jar:/opt/weblogic/10.0/weblogic10.0/platform/lib/wlp/netuix_schemas.jar:/opt/weblogic/10.0/weblogic10.0/platform/lib/wlp/netuix_system.jar:/opt/weblogic/10.0/weblogic10.0/platform/lib/wlp/wsrp-client.jar:/opt/weblogic/10.0/weblogic10.0/platform/lib/wlp/wsrp-common.jar>
<Jun 7, 2010 9:49:13 AM CEST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.5.0_15-b04 from Sun Microsystems Inc.>
<Jun 7, 2010 9:49:13 AM CEST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.0 MP2 Sat Apr 25 01:45:38 EDT 2009 1213942 >
i got the following error messages :
*<Jun 7, 2010 9:49:14 AM CEST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: [Management:141266]Parsing Failure in config.xml: failed to load java type corresponding to e=domain@http://www.bea.com/ns/weblogic/920/domain>*
<Jun 7, 2010 9:49:14 AM CEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Jun 7, 2010 9:49:14 AM CEST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Jun 7, 2010 9:49:14 AM CEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
If i start the server as root, it boots but i cant deploy anything.
Any idea about this behavior ?

Hi,
It is the problem in prasing the DTD of config.xml file
It look like this
<?xml version='1.0' encoding='UTF-8'?>
<domain xmlns="http://www.bea.com/ns/weblogic/920/domain" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-
instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90/security/xacml http://www.bea.com/
ns/weblogic/90/security/xacml.xsd http://www.bea.com/ns/weblogic/90/security http://www.bea.com/ns/weblogic/90/security.xsd http://www.bea.com/ns/weblogic/92
0/domain http://www.bea.com/ns/weblogic/920/domain.xsd http://www.bea.com/ns/weblogic/90/security/wls http://www.bea.com/ns/weblogic/90/security/wls.xsd">
Please change your DTD to this lines and start the server.
Regards
Ravi D

Critical WebLogicServer BEA-000362 Server failed. Reason: [Management:141266]Parsing Failure in config.xml: java.lang.AssertionError: java.lang.reflect.InvocationTargetException

Friends,
Getting below error when i restart the server.
<Dec 31, 2014 5:33:58 AM EST> <Warning> <Management> <BEA-141274> <Production mode has specified at the command line via the weblogic.ProductionModeEnabled system property. This system property overrides the development mode setting contained in config.xml. However, the console and WLST show the attribute values and defaults that correspond to the development mode specified in config.xml.>
<Dec 31, 2014 5:34:07 AM EST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: [Management:141266]Parsing Failure in config.xml: java.lang.AssertionError: java.lang.reflect.InvocationTargetException>
<Dec 31, 2014 5:34:07 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Dec 31, 2014 5:34:07 AM EST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Dec 31, 2014 5:34:07 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
I have changed the jar files path in build.properties file as its required to import new jars as part of Documentum server upgradation. But getting above errors.. Do i have to update Config.xml file or any other file.. Please suggest.

You've got a problem with a corrupted config.xml file.
Since you did not make any changes you can copy the config.xml.booted file over the corrupted config.xml.
The other option is to walk though the config.xml file and look for the problem...

OIM server crashes while Importing OIM AD connector config XML files

while installing OIM connector for Microsoft Active directory on the 2nd step of installation "Import of Connector XML Files (Using Deployment Manager)" Installation fails and OIM server crashes... my OIM server version is 11.1.1.3.0 and Connector is ActiveDirectory 9.1.1.5.0
Here is oim_server1-diagnostic log file
[2012-01-10T17:23:10.450+05:00] [oim_server1] [ERROR] [] [XELLERATE.ADAPTERS] [tid: [ACTIVE].ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: XELSYSADM] [ecid: 0000JJ7ZjsLFW7WFLz3V8A1F31xJ00006f,0] [APP: oim#11.1.1.3.0] [dcid: 80666d38c1d0770e:-122ffcd8:134c75e0aa6:-7ffd-00000000000001e9] Class/Method: tcAdpUtils/compileAdapter encounter some problems: Could not compile adapter : adpADCSMOVEGROUP
[2012-01-10T17:23:10.465+05:00] [oim_server1] [ERROR] [] [XELLERATE.ADAPTERS] [tid: [ACTIVE].ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: XELSYSADM] [ecid: 0000JJ7ZjsLFW7WFLz3V8A1F31xJ00006f,0] [APP: oim#11.1.1.3.0] [dcid: 80666d38c1d0770e:-122ffcd8:134c75e0aa6:-7ffd-00000000000001e9] Class/Method: tcAdpUtils/compileAdapter encounter some problems: Compile failed on Tue Jan 10 17:23:10 UZT 2012[[
error: Exception thrown while constructing Processor object: null
----------------SOURCE FILE
1: /* Copyright (c) 2001 - 2007, Oracle Corporation. All rights reserved.
2: */
3: package com.thortech.xl.adapterGlue.ScheduleItemEvents;
4: import com.thortech.xl.dataobj.*;
5: //import com.thortech.xl.adapterGlue.*;
6: //import com.thortech.xl.dataobj.tcDataSet;
7: import java.io.IOException;
8: import java.util.*;
9: import java.io.FileWriter;
10: import java.io.File;
11: import java.sql.Timestamp;
12: import java.text.DateFormat;
13: import com.thortech.xl.dataobj.util.tcAdapterTaskException;
14: import com.thortech.xl.dataobj.util.*;
15: import com.thortech.xl.dataobj.util.tcJarEntryClassLoader;
16: import com.thortech.xl.remotemanager.*;
17: import java.rmi.*;
18: import java.net.URL;
19: import java.lang.reflect.Constructor;
20: import java.lang.reflect.Method;
21: import java.lang.reflect.Modifier;
22: import java.lang.reflect.InvocationTargetException;
23: import java.lang.reflect.Field;
24: import java.net.*;
25:
26: public class adpADCSMOVEGROUP extends com.thortech.xl.adapterfactory.events.tcAdpEvent {
27: public adpADCSMOVEGROUP() {
28: super();
29: setEventName("ADCS Move Group");
30: }
31:
32: Hashtable ihTaskRetVals = new Hashtable();
33:
34: // Adapter Variables
35: String OrgName; // Organization Name
36: String sConfigurationLookUp; // ADParameterLookUp
37: long ADServer; // AD Server
38: String ObjectGUID; // ObjectGUID
39:
40: //Persistant Objects
41: Object ADconsObj;
42: Class clsAD;
43:
44: //Variables needed for class loader
45: String sURL;
46: URL url1;
47: URL[] aURL;
48: ClassLoader moURLClassLoader;
49: Class moTargetClass;
50: Object[] maoConstructorArgs;
51: Class[] masConParamTypes;
52: Constructor moCons;
53:
54: protected void implementation() throws Exception {
55:
56: try {
57:
58: if (! initAdapter("ADCS Move Group"))
59: return;
60:
61: // Run Time Variables
62: OrgName = getRunTimeValue("OrgName").toString();
63: sConfigurationLookUp = getRunTimeValue("sConfigurationLookUp").toString();
64: ADServer = ((Long)getRunTimeValue("ADServer")).longValue();
65: ObjectGUID = getRunTimeValue("ObjectGUID").toString();
66:
67: //Initialize persistant object "AD"
68: clsAD = Class.forName("com.thortech.xl.integration.ActiveDirectory.tcUtilADTasks");
69: maoConstructorArgs = new Object[]{getITAttrVal(ADServer, "Server Address"), getITAttrVal(ADServer, "Root Context"), getITAttrVal(ADServer, "Admin FQDN"), getITAttrVal(ADServer, "Admin Password"), getITAttrVal(ADServer, "Use SSL"), getITAttrVal(ADServer, "Port Number"), getITAttrVal(ADServer, "Invert Display Name"), "yes", sConfigurationLookUp, getDataBase()};
70: masConParamTypes = new Class[]{String.class, String.class, String.class, String.class, String.class, String.class, String.class, String.class, String.class, Class.forName("com.thortech.xl.dataaccess.tcDataProvider")};
71: moCons = clsAD.getConstructor(masConParamTypes);
72: ADconsObj = moCons.newInstance(maoConstructorArgs);
73:
74:
75: // Execute Tasks and store results in Hashtable...
76:
77: ihTaskRetVals.put("MOVEGROUP", MOVEGROUP());
78: // Output mapping for Task MOVEGROUP
79: setAdpRetVal(ihTaskRetVals.get("MOVEGROUP"), "String");
80:
81:
82: finalizeAdapter();
83:
84: } catch (tcAdapterTaskException e) {
85: e.printStackTrace();
86: updateSchItem("R", e.getMessage(), e.getReason());
87: return;
88: } catch (Exception e) {
89: e.printStackTrace();
90: updateSchItem("R", e.getMessage(), getReason("", e));
91: return;
92: }
93:
94: }
95:
96: // *** Move Group ***
97: private Object MOVEGROUP() throws Exception {
98: Object oRetVal = "";
99:
100: Object objCons;
101: String sTaskName = "Move Group";
102: try {
103:
104: System.out.println("Running Move Group");
105:
106: //This method uses persistent object "AD"
107:
108: // Initialize method
109: Class[] moMethodParmTypes = new Class[] {String.class, String.class, Class.forName("com.thortech.xl.dataaccess.tcDataProvider")};
110: Object[] moMethodParams = new Object[] {OrgName, ObjectGUID, getDataBase()};
111: Method moMethod = clsAD.getMethod("moveGroup", moMethodParmTypes);
112:
113: // Check for static method
114: if (Modifier.isStatic(moMethod.getModifiers()))
115: ADconsObj = null;
116:
117: // Invoke method
118: oRetVal = moMethod.invoke(ADconsObj, moMethodParams);
119:
120: } catch (Exception e) {
121: e.printStackTrace();
122: if (e instanceof InvocationTargetException) {
123: Throwable t = ((InvocationTargetException)e).getTargetException();
124: throw new tcAdapterTaskException("adpADCSMOVEGROUP", "Move Group", t.getMessage(), "", "");
125: } else {
126: throw new tcAdapterTaskException("adpADCSMOVEGROUP", "Move Group", e.getMessage(), "", "");
127: }
128: }
129: return returnVal(oRetVal);
130: }
131: }
----------------COMMAND LINE javac -classpath C:\Oracle\MIDDLE~1\WLSERV~1.3\server\ext\jdbc\oracle\11g\ojdbc6dms.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\user-patch.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\soa-startup.jar;;C:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_oepe1033\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_ocp353\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\JDK160~1\lib\tools.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;C:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules_10.3.3.0.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.1/lib/ant-all.jar;C:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\oracle.soa.common.adapters_11.1.1\oracle.soa.common.adapters.jar;C:\Oracle\MIDDLE~1\ORACLE~1\soa\modules\commons-cli-1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1\soa\modules\oracle.soa.mgmt_11.1.1\soa-infra-mgmt.jar;C:\Oracle\Middleware\Oracle_IDM1\oam\agent\modules\oracle.oam.wlsagent_11.1.1\oam-wlsagent.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.xdk_11.1.0\xsu12.jar;C:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules.xquery_10.3.1.0.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\db2jcc4.jar;C:\Oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\soa-infra;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\fabric-url-handler_11.1.1.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\quartz-all-1.6.5.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\oracle.soa.fabric_11.1.1\oracle.soa.fabric.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\oracle.soa.adapter_11.1.1\oracle.soa.adapter.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\oracle.soa.b2b_11.1.1\oracle.soa.b2b.jar;C:\Oracle\Middleware\Oracle_IDM1\server\lib\oim-manifest.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrf.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\derby\lib\derbyclient.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\xqrl.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-async.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-auth-client.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-auth-server.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-authz-service.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-configmbeans.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-context.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-entitymgr.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-kernel.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-pluginframework.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-utils.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-workflowservice.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-toplinksession.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlAdapterUtilities.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlAPI.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlAttestation.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlAuditor.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlAuthentication.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlBackOfficeBeans.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlBackofficeClient.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlCache.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlCrypto.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlDataObjectBeans.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlDataObjects.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlDDM.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlGenConnector.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xliGCProviders.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlInputPreprocessor.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlLogger.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlRemoteManager.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlRequestPreview.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlScheduler.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlUtils.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlVO.jar -d C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\\oracle\oim\adapters C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\\oracle\oim\adapters\adpADCSMOVEGROUP.java
[2012-01-10T17:23:14.075+05:00] [oim_server1] [NOTIFICATION] [] [oracle.iam.configservice.impl] [tid: [ACTIVE].ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: XELSYSADM] [ecid: 0000JJ7ZjsLFW7WFLz3V8A1F31xJ00006f,0] [APP: oim#11.1.1.3.0] [dcid: 80666d38c1d0770e:-122ffcd8:134c75e0aa6:-7ffd-00000000000001e9] Inside PostImport method of UserManagementPostImportForDm
[2012-01-10T17:23:14.450+05:00] [oim_server1] [ERROR] [] [oracle.iam.configservice.impl] [tid: [ACTIVE].ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: XELSYSADM] [ecid: 0000JJ7ZjsLFW7WFLz3V8A1F31xJ00006f,0] [APP: oim#11.1.1.3.0] [dcid: 80666d38c1d0770e:-122ffcd8:134c75e0aa6:-7ffd-00000000000001e9] The attribute ObjectGUID does not exist!
[2012-01-10T17:23:15.075+05:00] [oim_server1] [NOTIFICATION] [IAM-0080013] [oracle.iam.platform.kernel.impl] [tid: [ACTIVE].ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: XELSYSADM] [ecid: 0000JJ7ZjsLFW7WFLz3V8A1F31xJ00006f,0] [APP: oim#11.1.1.3.0] [dcid: 80666d38c1d0770e:-122ffcd8:134c75e0aa6:-7ffd-00000000000001e9] [arg: 30] [arg: 0] [arg: oracle.iam.platform.entitymgr.vo.EntityMetadata] [arg: MODIFY] Kernel executing default validation with process id, event id, entity and operation 30.0.oracle.iam.platform.entitymgr.vo.EntityMetadata.MODIFY
[2012-01-10T17:23:15.090+05:00] [oim_server1] [NOTIFICATION] [IAM-0080014] [oracle.iam.platform.kernel.impl] [tid: [ACTIVE].ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: XELSYSADM] [ecid: 0000JJ7ZjsLFW7WFLz3V8A1F31xJ00006f,0] [APP: oim#11.1.1.3.0] [dcid: 80666d38c1d0770e:-122ffcd8:134c75e0aa6:-7ffd-00000000000001e9] [arg: 30] [arg: 30] [arg: oracle.iam.platform.entitymgr.vo.EntityMetadata] [arg: MODIFY] [arg: /file/User.xml] Kernel executing default action handler with process id, event id, entity and operation 30.30.oracle.iam.platform.entitymgr.vo.EntityMetadata.MODIFY.entityId=/file/User.xml

There are different log handlers and loggers with different properties what are XELLRATE.DDM's properties
here is the logging.xml file
<?xml version="1.0" encoding="UTF-8"?>
<logging_configuration>
<log_handlers>
<log_handler name='console-handler' class='oracle.core.ojdl.logging.ConsoleHandler' formatter='oracle.core.ojdl.weblogic.ConsoleFormatter' level='WARNING:32'/>
<log_handler name='odl-handler' class='oracle.core.ojdl.logging.ODLHandlerFactory' filter='oracle.dfw.incident.IncidentDetectionLogFilter'>
<property name='path' value='${domain.home}/servers/${weblogic.Name}/logs/${weblogic.Name}-diagnostic.log'/>
<property name='maxFileSize' value='10485760'/>
<property name='maxLogSize' value='104857600'/>
<property name='encoding' value='UTF-8'/>
<property name='useThreadName' value='true'/>
<property name='supplementalAttributes' value='J2EE_APP.name,J2EE_MODULE.name,WEBSERVICE.name,WEBSERVICE_PORT.name,composite_instance_id,component_instance_id,composite_name,component_name'/>
</log_handler>
<log_handler name='wls-domain' class='oracle.core.ojdl.weblogic.DomainLogHandler' level="WARNING"/>
<log_handler name='owsm-message-handler' class='oracle.core.ojdl.logging.ODLHandlerFactory'>
<property name='path' value='${domain.home}/servers/${weblogic.Name}/logs/owsm/msglogging'/>
<property name='maxFileSize' value='10485760'/>
<property name='maxLogSize' value='104857600'/>
<property name='encoding' value='UTF-8'/>
<property name='supplementalAttributes' value='J2EE_APP.name,J2EE_MODULE.name,WEBSERVICE.name,WEBSERVICE_PORT.name'/>
</log_handler>
<log_handler name='em-log-handler' level='NOTIFICATION:32' class='oracle.core.ojdl.logging.ODLHandlerFactory' filter='oracle.dfw.incident.IncidentDetectionLogFilter'>
<property name='path' value='${domain.home}/servers/${weblogic.Name}/sysman/log/emoms.log'/>
<property name='format' value='ODL-Text'/>
<property name='useThreadName' value='true'/>
<property name='maxFileSize' value='5242880'/>
<property name='maxLogSize' value='52428800'/>
<property name='encoding' value='UTF-8'/>
</log_handler>
<log_handler name='em-trc-handler' level='TRACE:32' class='oracle.core.ojdl.logging.ODLHandlerFactory'>
<property name='logreader:' value='off'/>
<property name='path' value='${domain.home}/servers/${weblogic.Name}/sysman/log/emoms.trc'/>
<property name='format' value='ODL-Text'/>
<property name='useThreadName' value='true'/>
<property name='locale' value='en'/>
<property name='maxFileSize' value='5242880'/>
<property name='maxLogSize' value='52428800'/>
<property name='encoding' value='UTF-8'/>
</log_handler>
</log_handlers>
<loggers>
<logger name="" level="WARNING:1">
<handler name="odl-handler"/>
<handler name="wls-domain"/>
<handler name="console-handler"/>
</logger>
<logger name="oracle" level="NOTIFICATION:1"/>
<logger name="oracle.adf"/>
<logger name="oracle.adf.desktopintegration"/>
<logger name="oracle.adf.faces"/>
<logger name="oracle.adf.controller"/>
<logger name="oracle.adfinternal"/>
<logger name="oracle.adfinternal.controller"/>
<logger name="oracle.jbo"/>
<logger name="oracle.adfdt"/>
<logger name="oracle.adfdtinternal"/>
<logger name="oracle.bam"/>
<logger name="oracle.bam.common"/>
<logger name="oracle.bam.system"/>
<logger name="oracle.bam.middleware"/>
<logger name="oracle.bam.adc.security"/>
<logger name="oracle.bam.common.security"/>
<logger name="oracle.bam.adc.ejb.BamAdcServerBean"/>
<logger name="oracle.bam.reportcache.ejb.ReportCacheServerBean"/>
<logger name="oracle.bam.eventengine.ejb.EventEngineServerBean"/>
<logger name="oracle.bam.ems.ejb.EMSServerBean"/>
<logger name="oracle.bam.adc.api"/>
<logger name="oracle.bam.adc"/>
<logger name="oracle.bam.eventengine"/>
<logger name="oracle.bam.ems"/>
<logger name="oracle.bam.webservices"/>
<logger name="oracle.bam.web"/>
<logger name="oracle.bam.reportcache"/>
<logger name="oracle.bpm"/>
<logger name="oracle.bpm.analytics"/>
<logger name="oracle.integration"/>
<logger name="oracle.integration.platform.blocks.cluster"/>
<logger name="oracle.integration.platform.blocks.deploy.coordinator"/>
<logger name="oracle.integration.platform.blocks.event.saq"/>
<logger name="oracle.integration.platform.blocks.java"/>
<logger name="oracle.integration.platform.faultpolicy"/>
<logger name="oracle.integration.platform.testfwk"/>
<logger name="oracle.soa"/>
<logger name="oracle.soa.adapter"/>
<logger name="oracle.soa.b2b"/>
<logger name="oracle.soa.b2b.apptransport"/>
<logger name="oracle.soa.b2b.engine"/>
<logger name="oracle.soa.b2b.repository"/>
<logger name="oracle.soa.b2b.transport"/>
<logger name="oracle.soa.b2b.ui"/>
<logger name="oracle.soa.bpel"/>
<logger name="oracle.soa.bpel.console"/>
<logger name="oracle.soa.bpel.engine"/>
<logger name="oracle.soa.bpel.engine.activation"/>
<logger name="oracle.soa.bpel.engine.agents"/>
<logger name="oracle.soa.bpel.engine.bpel"/>
<logger name="oracle.soa.bpel.engine.compiler"/>
<logger name="oracle.soa.bpel.engine.data"/>
<logger name="oracle.soa.bpel.engine.delivery"/>
<logger name="oracle.soa.bpel.engine.deployment"/>
<logger name="oracle.soa.bpel.engine.dispatch"/>
<logger name="oracle.soa.bpel.engine.sensor"/>
<logger name="oracle.soa.bpel.engine.translation"/>
<logger name="oracle.soa.bpel.engine.ws"/>
<logger name="oracle.soa.bpel.engine.xml"/>
<logger name="oracle.soa.bpel.entity"/>
<logger name="oracle.soa.bpel.jpa"/>
<logger name="oracle.soa.bpel.system"/>
<logger name="oracle.soa.dvm"/>
<logger name="oracle.soa.management.facade.api"/>
<logger name="oracle.soa.mediator"/>
<logger name="oracle.soa.mediator.common"/>
<logger name="oracle.soa.mediator.common.cache"/>
<logger name="oracle.soa.mediator.common.error"/>
<logger name="oracle.soa.mediator.common.error.recovery"/>
<logger name="oracle.soa.mediator.common.message"/>
<logger name="oracle.soa.mediator.dispatch"/>
<logger name="oracle.soa.mediator.dispatch.resequencer.toplink"/>
<logger name="oracle.soa.mediator.filter"/>
<logger name="oracle.soa.mediator.instance"/>
<logger name="oracle.soa.mediator.management"/>
<logger name="oracle.soa.mediator.metadata"/>
<logger name="oracle.soa.mediator.monitor"/>
<logger name="oracle.soa.mediator.resequencer"/>
<logger name="oracle.soa.mediator.resequencer.besteffort"/>
<logger name="oracle.soa.mediator.resequencer.fifo"/>
<logger name="oracle.soa.mediator.resequencer.standard"/>
<logger name="oracle.soa.mediator.service"/>
<logger name="oracle.soa.mediator.serviceEngine"/>
<logger name="oracle.soa.mediator.transformation"/>
<logger name="oracle.soa.mediator.utils"/>
<logger name="oracle.soa.mediator.validation"/>
<logger name="oracle.soa.scheduler"/>
<logger name="oracle.soa.services.common"/>
<logger name="oracle.soa.services.identity"/>
<logger name="oracle.soa.services.notification"/>
<logger name="oracle.soa.services.rules"/>
<logger name="oracle.soa.services.rules.obrtrace"/>
<logger name="oracle.soa.services.workflow"/>
<logger name="oracle.soa.services.workflow.common"/>
<logger name="oracle.soa.services.workflow.evidence"/>
<logger name="oracle.soa.services.workflow.metadata"/>
<logger name="oracle.soa.services.workflow.persistency"/>
<logger name="oracle.soa.services.workflow.query"/>
<logger name="oracle.soa.services.workflow.report"/>
<logger name="oracle.soa.services.workflow.runtimeconfig"/>
<logger name="oracle.soa.services.workflow.soa"/>
<logger name="oracle.soa.services.workflow.task"/>
<logger name="oracle.soa.services.workflow.task.dispatch"/>
<logger name="oracle.soa.services.workflow.task.routing"/>
<logger name="oracle.soa.services.workflow.user"/>
<logger name="oracle.soa.services.workflow.verification"/>
<logger name="oracle.soa.services.workflow.worklist"/>
<logger name="oracle.soa.services.workflow.performance"/>
<logger name="oracle.soa.services.cmds"/>
<logger name="oracle.soa.wsif"/>
<logger name="oracle.soa.xref"/>
<logger name="oracle.sdp"/>
<logger name="oracle.sdpinternal"/>
<logger name="oracle.sdp.owlcs.customer"/>
<logger name="oracle.sdp.owlcs.config"/>
<logger name="oracle.sdp.owlcs.timer"/>
<logger name="oracle.sdp.messaging"/>
<logger name="oracle.sdp.messaging.client"/>
<logger name="oracle.sdp.messaging.driver"/>
<logger name="oracle.sdp.messaging.engine"/>
<logger name="oracle.sdp.messaging.parlayx"/>
<logger name="oracle.sdp.messaging.server"/>
<logger name="oracle.wsm"/>
<logger name="oracle.wsm.msg.logging" level="NOTIFICATION:1" useParentHandlers="false">
<handler name="owsm-message-handler"/>
<handler name="wls-domain"/>
</logger>
<logger name='oracle.sysman' level='NOTIFICATION:32' useParentHandlers='false'>
<handler name='em-log-handler'/>
<handler name='em-trc-handler'/>
</logger>
</loggers>
</logging_configuration>

[svn:bz-trunk] 8910: Bug: LCDS-936 - Should have better error message in servlet log if server in services-config .xml is configured to use wrong class.

Revision: 8910
Author:   [email protected]
Date:     2009-07-29 14:22:26 -0700 (Wed, 29 Jul 2009)
Log Message:
Bug: LCDS-936 - Should have better error message in servlet log if server in services-config.xml is configured to use wrong class.
QA: Yes
Doc: No
Checkintests: Pass
Ticket Links:
    http://bugs.adobe.com/jira/browse/LCDS-936
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/MessageBrokerServlet.java

After many hard working days.i finally found the error cause,i needed to make weblogic datasource also ADF doesnt work on internet explorer browser,it works on safary.hope it helps somebody

Config.xml file missing after using pack/unpack (WebLogic 12c)

Hi,
When I use the utilities pack/unpack to "copy" a domain from one physical server to another one, I end up with the config directory where there is no config.xml file while on the source physical there is of course this file.
If I use the scp command (I work under Linux) to "copy" the domain I do not encounter problem and I can start the Node Manager and the WebLogic server.
Did someone faced this situation?
How did you solved it? Or, is there something that I am missing?
Kind Regards.

Hi all!
I am having the same problem with WebLogic Workshop 8.1 SP4.
Any idea?
Thanks in advance.

Failover server (using config.xml)

Hi ,
I am using weblogic server 7.0(1) installed in solaris . I installed a new server where i need to have same configuration as like (1) .
so i directly placed the config.xml of (1) in the second server domain by changing the IP address in config.xml.
I am getting the following at the start of server..
<May 23, 2009 11:15:36 AM IST> <Notice> <Management> <140005> <Loading configuration /ICICIprud/ICICIportal/weblogicnew/user_projects/iciciprulife/./config.xml>
<May 23, 2009 11:15:37 AM IST> <Critical> <WebLogicServer> <000364> <Server failed during initialization. Exception:weblogic.management.configuration.ConfigurationException: Error parsing the configuration file: Could not perform unpadding: invalid pad byte. - with nested exception:
[com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.]
com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.
at com.rsa.jsafe.JA_PKCS5Padding.performUnpadding(JA_PKCS5Padding.java:111)
at com.rsa.jsafe.JG_BlockCipher.decryptFinal(JG_BlockCipher.java:1112)
at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:67)
at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:93)
at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:53)
at weblogic.management.internal.EncryptedData.decrypt(EncryptedData.java:45)
at weblogic.management.internal.xml.ConfigurationParser$ConfigurationHandler.parseMBeanAttributes(ConfigurationParser.java:652)
at weblogic.management.internal.xml.ConfigurationParser$ConfigurationHandler.startElement(ConfigurationParser.java:322)
at weblogic.apache.xerces.parsers.SAXParser.startElement(SAXParser.java:1348)
at weblogic.apache.xerces.validators.common.XMLValidator.callStartElement(XMLValidator.java:1299)
at weblogic.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentScanner.java:1838)
at weblogic.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XMLDocumentScanner.java:1207)
at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:399)
at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:1138)
at weblogic.management.internal.xml.ConfigurationParser.parse(ConfigurationParser.java:227)
at weblogic.management.internal.xml.XmlFileRepository.createOrLoadDomain(XmlFileRepository.java:483)
at weblogic.management.internal.xml.XmlFileRepository.bootStrapAndLoadActiveDomain(XmlFileRepository.java:354)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.java:217)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.java:202)
at weblogic.management.AdminServer.configure(AdminServer.java:196)
at weblogic.management.AdminServerAdmin.initialize(AdminServerAdmin.java:111)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:664)
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)
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: Error parsing the configuration file: Could not perform unpadding: invalid pad byte. - with nested exception:
[com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.]
at weblogic.management.internal.xml.ConfigurationParser.parse(ConfigurationParser.java:243)
at weblogic.management.internal.xml.XmlFileRepository.createOrLoadDomain(XmlFileRepository.java:483)
at weblogic.management.internal.xml.XmlFileRepository.bootStrapAndLoadActiveDomain(XmlFileRepository.java:354)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.java:217)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.java:202)
at weblogic.management.AdminServer.configure(AdminServer.java:196)
at weblogic.management.AdminServerAdmin.initialize(AdminServerAdmin.java:111)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:664)
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)
>
The WebLogic Server did not start up properly.
Exception raised:
com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.
at com.rsa.jsafe.JA_PKCS5Padding.performUnpadding(JA_PKCS5Padding.java:111)
at com.rsa.jsafe.JG_BlockCipher.decryptFinal(JG_BlockCipher.java:1112)
at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:67)
at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:93)
at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:53)
at weblogic.management.internal.EncryptedData.decrypt(EncryptedData.java:45)
at weblogic.management.internal.xml.ConfigurationParser$ConfigurationHandler.parseMBeanAttributes(ConfigurationParser.java:652)
at weblogic.management.internal.xml.ConfigurationParser$ConfigurationHandler.startElement(ConfigurationParser.java:322)
at weblogic.apache.xerces.parsers.SAXParser.startElement(SAXParser.java:1348)
at weblogic.apache.xerces.validators.common.XMLValidator.callStartElement(XMLValidator.java:1299)
at weblogic.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentScanner.java:1838)
at weblogic.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XMLDocumentScanner.java:1207)
at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:399)
at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:1138)
at weblogic.management.internal.xml.ConfigurationParser.parse(ConfigurationParser.java:227)
at weblogic.management.internal.xml.XmlFileRepository.createOrLoadDomain(XmlFileRepository.java:483)
at weblogic.management.internal.xml.XmlFileRepository.bootStrapAndLoadActiveDomain(XmlFileRepository.java:354)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.java:217)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.java:202)
at weblogic.management.AdminServer.configure(AdminServer.java:196)
at weblogic.management.AdminServerAdmin.initialize(AdminServerAdmin.java:111)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:664)
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)
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: Error parsing the configuration file: Could not perform unpadding: invalid pad byte. - with nested exception:
[com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.]
at weblogic.management.internal.xml.ConfigurationParser.parse(ConfigurationParser.java:243)
at weblogic.management.internal.xml.XmlFileRepository.createOrLoadDomain(XmlFileRepository.java:483)
at weblogic.management.internal.xml.XmlFileRepository.bootStrapAndLoadActiveDomain(XmlFileRepository.java:354)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.java:217)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.java:202)
at weblogic.management.AdminServer.configure(AdminServer.java:196)
at weblogic.management.AdminServerAdmin.initialize(AdminServerAdmin.java:111)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:664)
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)
Reason: Fatal initialization exception
Throwable: weblogic.management.configuration.ConfigurationException: Error parsing the configuration file: Could not perform unpadding: invalid pad byte. - with nested exception:
[com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.]
com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.
at com.rsa.jsafe.JA_PKCS5Padding.performUnpadding(JA_PKCS5Padding.java:111)
at com.rsa.jsafe.JG_BlockCipher.decryptFinal(JG_BlockCipher.java:1112)
at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:67)
at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:93)
at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:53)
at weblogic.management.internal.EncryptedData.decrypt(EncryptedData.java:45)
at weblogic.management.internal.xml.ConfigurationParser$ConfigurationHandler.parseMBeanAttributes(ConfigurationParser.java:652)
at weblogic.management.internal.xml.ConfigurationParser$ConfigurationHandler.startElement(ConfigurationParser.java:322)
at weblogic.apache.xerces.parsers.SAXParser.startElement(SAXParser.java:1348)
at weblogic.apache.xerces.validators.common.XMLValidator.callStartElement(XMLValidator.java:1299)
at weblogic.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentScanner.java:1838)
at weblogic.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XMLDocumentScanner.java:1207)
at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:399)
at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:1138)
at weblogic.management.internal.xml.ConfigurationParser.parse(ConfigurationParser.java:227)
at weblogic.management.internal.xml.XmlFileRepository.createOrLoadDomain(XmlFileRepository.java:483)
at weblogic.management.internal.xml.XmlFileRepository.bootStrapAndLoadActiveDomain(XmlFileRepository.java:354)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.java:217)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.java:202)
at weblogic.management.AdminServer.configure(AdminServer.java:196)
at weblogic.management.AdminServerAdmin.initialize(AdminServerAdmin.java:111)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:664)
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)
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: Error parsing the configuration file: Could not perform unpadding: invalid pad byte. - with nested exception:
[com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.]
at weblogic.management.internal.xml.ConfigurationParser.parse(ConfigurationParser.java:243)
at weblogic.management.internal.xml.XmlFileRepository.createOrLoadDomain(XmlFileRepository.java:483)
at weblogic.management.internal.xml.XmlFileRepository.bootStrapAndLoadActiveDomain(XmlFileRepository.java:354)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.java:217)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.java:202)
at weblogic.management.AdminServer.configure(AdminServer.java:196)
at weblogic.management.AdminServerAdmin.initialize(AdminServerAdmin.java:111)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:664)
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)
+ set +x
please help me to solve the above problem.
Thanks in advance,
Katheek.

This error is due to SerializedSystemIni.dat not being available. I would recommend reading up on this file, as it is important for any weblogic admin to understand its function. Check these out:
[http://connectionserver.blogspot.com/2009_05_01_archive.html|http://connectionserver.blogspot.com/2009_05_01_archive.html]
[http://e-docs.bea.com/wls/docs81/secmanage/passwords.html|http://e-docs.bea.com/wls/docs81/secmanage/passwords.html]
[http://weblogic.sys-con.com/node/42929|http://weblogic.sys-con.com/node/42929]

Running on Weblogic Server 9 with XML mappings (JPA)

We have a project with a number of persistent classes configured through XML mapping files instead of annotations because it should also work under JDK 1.4.
It works perfect as a standalone client or set up in the server with a connection specified in the persistence.xml.
However when configuring it through a resource adapter as recommended for WLS9, I'm running into problems as there seems to be no way to specify that MetaData should be taken from an XML file when it comes to the JPA edition.
Eg. I'm missing the equivalent of:
<mapping-file>com/xyz/xxx/Service.orm.xml</mapping-file>So naturally I get an Exception like:
org.apache.openjpa.persistence.ArgumentException: There is no query with the name "findServiceByName" defined for any of the known persistent classes: null.And the server log also shows:
INFO [[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'] openjpa.MetaData - Found 0 classes with metadata in 20 milliseconds.Any suggestions on how to fix or work around this without introducing annotations?
Regards
Brian Jacobsen

Yes we are using named queries as well.
WLS 9.2, Kodo 4.1.2.
There are no entries in config.xml and no persistence.xml when running as recommended under WLS9 installation in the Kodo documentation.
Everything is configured in the ra.xml for the resource adapter. But the ra.xml specification only supports specification through annotated classes for JPA as far as I can decipher, which is what I tried to describe in the original post.
Eg. kodo.MetaDataFactory supports only classes through Type. There is no way to specify the equivalent mapping through XML files. See section 6.2 Metadata Factory in the Kodo Manual.
Kind regards
Brian Jacobsen

Multiple Apex Listeners on one server trouble with apex-config.xml

I'm using 0C4J to deploy apex on a windows server. I want to be able to have multiple instances of OC4J running pointing to different databases. I've read through documentation and forum posts and this looks simple enough.
I've got one instance running at E:\OC4J and working fine. I've to added a second OC4J instance at E:\OC4J2. I've rebuilt and redeployed the apex.war file after editing web.xml to specify a new location for apex-config.xml. I'm trying to specify the config directory as E:\OC4J2\config but can't seem to get the syntax right, because it keeps picking up the default file the first OC4J instance is using.
<context-param>
<param-name>config.dir</param-name>
<param-value>E:\oc4j2\config</param-value>
</context-param>
I've tried multiple versions of the path E:\oc4j2\config, E:/oc4j2/config, /oc4j2/config, \oc4j2\config but none seem to work.
Could anybody confirm the proper syntax for specifying the path to apex-config.xml in web.xml on a windows server?
Thanks in advance

Got it working
Had the syntax right.
<context-param>
<param-name>config.dir</param-name>
<param-value>E:\oc4j2\config</param-value>
</context-param>
Issue seems to be if there is an apex-config.xml file at C:\Users\username\AppData\Local\Temp\apex it picks up on it first.
Once I had both web.xml files specified to different directories for the config file and I deleted the one at C:\Users\username\AppData\Local\Temp\apex things worked as expected.
Thanks

How to use Weblogic Server 6.1 build.xml with ant

Hi Java's
I have downloaded the latest version of BEA Weblogic server 6.1,they have changed the build.cmd to build.xml for compiling and building the ejb applications.they are telling that we have use $ant to run the build.xml but i couldn't able to do that.i'm getting "command not found error"..i'm using winnt.please help me how to use $ ant.Is it a seperate exe or batch file that i have to download ?if so where to download it.how to use it.please help.
Regards
Balaji

To use it after installation, set your path to your
<ant_installation_dir>\bin, then navigate to the diectory containing the build.xml. then follow the instructions in the weblogic documentation for running ant.

XML Beans and Weblogic Server 8.1

Hi,
Does anyone know if XML beans is shipped with Weblogic 8.x (or is it only part
of the Weblogic Workshop) ?
Thanks,
Arun

Greg,
The classes required for running these command line tools are all there, but
we have not put the script files in the version bundled with WebLogic
server. Its very likely to be part of the next service pack release.
Meanwhile, you can always run the classes from the command line, or write
your own script. For instance, the dumpxsb.cmd has the following:
set cp=
set cp=%cp%;%XMLBEANDIR%\xbean.jar
java -classpath %cp% com.bea.xbean.tool.XsbDumper %*
So you can always write this on your own, or just run the concerned class
from the command line.
Let me know if you have any further queries.
Regards,
Anurag
"Greg" <[email protected]> wrote in message news:1061965730.933286@ns1...
Hi,
Is it possible to use the version of xmlbeans bundled with workshop in a
standalone sense? Are all the command line tools there? If so can yougive
a pointer to where abouts in the Workshop download to look for this.
The reason I ask is noting the following I saw -:
Note: XQuery is currently only available with the version of XMLBeans
included with WebLogic Platform. We hope to add these capabilities to the
stand-alone version soon.
Greg
"Raj Alagumalai" <[email protected]> wrote in message
news:[email protected]..
Arun,
WebLogic Platform 8.1 GA which includes Workshop does contain an
xmlbeans
implementation.
We also have a stand alone implementation which is available on dev2dev.
Thanks
Raj Alagumalai
WebLogic Workshop Support
"Arun" <[email protected]> wrote in message
news:3f38da48$[email protected]..
Thanks. But what we have found out from BEA is that it does not shipwith Weblogic
Server. You have to download it separately.
"Dmitri Colebatch" <[email protected]> wrote:
Does anyone know if XML beans is shipped with Weblogic 8.x (or is it
only part of the Weblogic Workshop) ?yes, it is shipped in Platform 8.1 (I'm pretty sure its shipping in
Server
8.1
too). Although the version is slightly older than the version
available
on the
dev2dev site.
cheers
dim

How to make changes effect in log4j.xml without restarting weblogic server

Hi ,
I have successfully configured log4j in my weblogic server 8.1.
Everytime i made a change in log4j.xml i need to restart the server
is there any configuration or parameter to set without restarting server??
Thanks in advance,
CK

I don't think you need to restart the server, atleast I never needed to when making changes to jsp pages. You only need to restart when you make changes to java classes. Some might argue jsp is converted to servlet which is a java class.....
Try refreshing the page when you make any changes. This works for me, if it doesn't work try turning reloadable="true" in your context path in tomcat's server.xml

Problem weblogic 9.2 with quartz and log4j : url-template-config.xml

Hello,
I configure a Servlet Quartz to run when WebLogic 9.2 starts, but i have an exception, here is my log :
2009-04-15 11:52:52,424 ERROR Logger.error(): Exception while loading URL templates, /WEB-INF/url-template-config.xml
Throwable: javax.servlet.ServletException: error: The document is not a url-template-config: document element namespace mismatch expected "" got "http://www.bea.com/servers/weblogic/url-template-config/8.0"
Stack Trace:
javax.servlet.ServletException: error: The document is not a url-template-config: document element namespace mismatch expected "" got "http://www.bea.com/servers/weblogic/url-template-config/8.0"
     at org.apache.beehive.netui.core.urltemplates.URLTemplatesFactory.getTemplates(URLTemplatesFactory.java:131)
     at org.apache.beehive.netui.core.urltemplates.URLTemplateDescriptor.load(URLTemplateDescriptor.java:133)
     at org.apache.beehive.netui.pageflow.PageFlowContextListener.performInitializations(PageFlowContextListener.java:102)
     at org.apache.beehive.netui.pageflow.PageFlowActionServlet.init(PageFlowActionServlet.java:120)
     at com.bea.console.internal.ConsoleActionServlet.init(ConsoleActionServlet.java:185)
     at javax.servlet.GenericServlet.init(GenericServlet.java:256)
     at weblogic.servlet.AsyncInitServlet.initDelegate(AsyncInitServlet.java:94)
     at weblogic.servlet.AsyncInitServlet.init(AsyncInitServlet.java:78)
     at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:276)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:68)
     at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
     at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
     at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:493)
     at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1688)
     at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1665)
     at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1585)
     at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2678)
     at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:874)
     at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:326)
     at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:114)
     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:25)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:640)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:252)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:176)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:347)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.activate(DeploymentAdapter.java:50)
     at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232)
     at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:168)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
Caused by: org.apache.xmlbeans.XmlException: error: The document is not a url-template-config: document element namespace mismatch expected "" got "http://www.bea.com/servers/weblogic/url-template-config/8.0"
     at org.apache.xmlbeans.impl.store.Locale.verifyDocumentType(Locale.java:449)
     at org.apache.xmlbeans.impl.store.Locale.autoTypeDocument(Locale.java:354)
     at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1270)
     at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1254)
     at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:345)
     at org.apache.beehive.netui.core.urltemplates.schema.UrlTemplateConfigDocument$Factory.parse(Unknown Source)
     at org.apache.beehive.netui.core.urltemplates.DefaultURLTemplateFileParser.parse(DefaultURLTemplateFileParser.java:34)
     at org.apache.beehive.netui.core.urltemplates.URLTemplatesFactory.getTemplates(URLTemplatesFactory.java:118)
     ... 43 more
The problem may be a conflict with the different version. My versions are quartz-1.6.0.jar, log4j-1.2.15.jar.
When i rename the file url-template-config.xml i don't have this exception but just a log4j Warning but i don't know if it's not dangerous for my application (run with WebLogic 9.2) if i rename this file.
Can you give me a solution to remove this exception or tell me if rename this file it's not dangerous ?
Thank you,
MH.

url-template-config.xml is part of Apache Beehive. This file is used to provide a template mechanism for URL's. Is your application using Apache Beehive purposefully?
http://beehive.apache.org/docs/1.0.2/netui/apidocs/javadoc/org/apache/beehive/netui/core/urls/URLRewriterService.html
If not, you may have inadvertently added a reference to Apache Beehive when you created the application and now there are references to the Apache Beehive shared libraries in either weblogic-applicaiton.xml or weblogic.xml

Weblogic Server config.xml

Similar Messages

Maybe you are looking for