Error - can't start application server
hi,
i got this error in log file!
ception: recursivecall
at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream.flush(SystemOutandErrHandler.java:189)
at java.io.PrintStream.write(PrintStream.java:260)
at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336)
at sun.nio.cs.StreamEncoder$CharsetSE.implFlushBuffer(StreamEncoder.java:404)
at sun.nio.cs.StreamEncoder.flushBuffer(StreamEncoder.java:115)
at java.io.OutputStreamWriter.flushBuffer(OutputStreamWriter.java:169)
at java.io.PrintStream.write(PrintStream.java:305)
at java.io.PrintStream.print(PrintStream.java:448)
at java.io.PrintStream.println(PrintStream.java:585)
at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingPrintStream.println(SystemOutandErrHandler.java:144)
at java.util.logging.ErrorManager.error(ErrorManager.java:76)
at com.sun.enterprise.server.logging.ServerLogManager.getLogService(ServerLogManager.java:284)
at com.sun.enterprise.server.logging.FileandSyslogHandler.publish(FileandSyslogHandler.java:266)
at java.util.logging.Logger.log(Logger.java:424)
at java.util.logging.Logger.doLog(Logger.java:446)
at java.util.logging.Logger.log(Logger.java:469)
at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream.flush(SystemOutandErrHandler.java:198)
at java.io.PrintStream.write(PrintStream.java:260)
at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336)
at sun.nio.cs.StreamEncoder$CharsetSE.implFlushBuffer(StreamEncoder.java:404)
at sun.nio.cs.StreamEncoder.flushBuffer(StreamEncoder.java:115)
at java.io.OutputStreamWriter.flushBuffer(OutputStreamWriter.java:169)
at java.io.PrintStream.write(PrintStream.java:305)
at java.io.PrintStream.print(PrintStream.java:448)
at java.io.PrintStream.println(PrintStream.java:585)
at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingPrintStream.println(SystemOutandErrHandler.java:144)
at java.util.logging.ErrorManager.error(ErrorManager.java:76)
at com.sun.enterprise.server.logging.ServerLogManager.getLogService(ServerLogManager.java:284)
at com.sun.enterprise.server.logging.ServerLogManager.reInitializeServerLoggers(ServerLogManager.java:468)
at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:119)
at com.sun.enterprise.server.PEMain.run(PEMain.java:210)
at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
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:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
java.util.logging.ErrorManager: 0: Error In getLogService java.util.logging.ErrorManager: 0: Error In getLogService
java.util.logging.ErrorManager: 0: Error In getLogService java.util.logging.ErrorManager: 0: Error In getLogService
java.util.logging.ErrorManager: 0: Error In getLogService java.util.logging.ErrorManager: 0: Error In getLogService
com.sun.enterprise.config.ConfigException: Error refreshing ConfigContext:C:\Programme\Sun\Creator\SunAppServer8\domains\creator\config\domain.xml
cause: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "context-root" is required and must be specified for element type "web-module".
at com.sun.enterprise.config.ConfigContextImpl.refresh(ConfigContextImpl.java:315)
at com.sun.enterprise.config.ConfigContextImpl.refresh(ConfigContextImpl.java:397)
at com.sun.enterprise.config.ConfigContextImpl.getRootConfigBean(ConfigContextImpl.java:192)
at com.sun.enterprise.config.ConfigBeansFactory.getConfigBeanByXPath(ConfigBeansFactory.java:36)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getServerBean(ServerBeansFactory.java:84)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigModel(ServerBeansFactory.java:57)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigBean(ServerBeansFactory.java:95)
at com.sun.enterprise.server.logging.ServerLogManager.getLogService(ServerLogManager.java:281)
at com.sun.enterprise.server.logging.FileandSyslogHandler.publish(FileandSyslogHandler.java:266)
at java.util.logging.Logger.log(Logger.java:424)
at java.util.logging.Logger.doLog(Logger.java:446)
at java.util.logging.Logger.log(Logger.java:469)
at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream.flush(SystemOutandErrHandler.java:198)
at java.io.PrintStream.write(PrintStream.java:260)
at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336)
at sun.nio.cs.StreamEncoder$CharsetSE.implFlushBuffer(StreamEncoder.java:404)
at sun.nio.cs.StreamEncoder.flushBuffer(StreamEncoder.java:115)
at java.io.OutputStreamWriter.flushBuffer(OutputStreamWriter.java:169)
at java.io.PrintStream.write(PrintStream.java:305)
at java.io.PrintStream.print(PrintStream.java:448)
at java.io.PrintStream.println(PrintStream.java:585)
at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingPrintStream.println(SystemOutandErrHandler.java:144)
at java.util.logging.ErrorManager.error(ErrorManager.java:76)
at com.sun.enterprise.server.logging.ServerLogManager.getLogService(ServerLogManager.java:284)
at com.sun.enterprise.server.logging.ServerLogManager.reInitializeServerLoggers(ServerLogManager.java:468)
at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:119)
at com.sun.enterprise.server.PEMain.run(PEMain.java:210)
at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
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:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: org.netbeans.modules.schema2beans.Schema2BeansNestedException: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "context-root" is required and must be specified for element type "web-module".
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:718)
at org.netbeans.modules.schema2beans.BaseBean.createGraph(BaseBean.java:2262)
at com.sun.enterprise.config.ConfigContextImpl.refresh(ConfigContextImpl.java:293)
... 32 more
Caused by: org.xml.sax.SAXParseException: Attribute "context-root" is required and must be specified for element type "web-module".
at org.apache.xerces.parsers.DOMParser.parse(DOMParser.java:266)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:206)
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:714)
... 34 more
please help me.
thanks, christoph
Hi Christoph,
Please take a look at the following thread:
http://swforum.sun.com/jive/thread.jspa?forumID=123&threadID=46131
The last 3 posts in this thread might be very useful for you. I hope this will be of help to you.
Cheers :-)
Similar Messages
-
Can't start Application server
Hi,
When I am to start Application server within Jdev 11.1.1.4, I have got this
Caused by: java.lang.ClassNotFoundException: weblogic.Server
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
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)
Could not find the main class: weblogic.Server. Program will exit.
Exception in thread "main" Process exited.
What can be the reasons?
Regards,
Edited by: Hua Min on Feb 13, 2012 4:08 PMHi,
Check similar issue
java.lang.NoClassDefFoundError: weblogic/Server -
New install of SJS Ent 8 on Solaris, can't start Application Server 8.1
Hello,
Appreciate in advance your help.
Just downloaded and installed SJS 8.1 on a new Sun Solaris 10 box. I'm able to run the IDE and have started the Tomcat server, but when attempting to start the SJS 8.1 application server, I get:
The Sun Java System Application Server 8.1 could not start.
More information about the cause is in the Server log file.
Possible reasons include:
- Port conflicts. (use netstat -a to detect possible port numbers already used)
- Incorrect server configuration
- Corrupted Deployed Applications
The problems are:
- There is no server.log file in the expected directory at /opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/logs
- I ran netstat -a, but could glean no useful information
- I have not modified the server configuration since the new install
- I have not deployed my application (since I can't start the server).
Forgive my ignorance since I'm not a Solaris expert. I would greatly appreciate your assistance.No difference in server.log after setting level="FINEST".
Don't know if it would help, but the contents of my server.log file follow:
[#|2006-09-25T15:39:46.485-0400|INFO|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|
/opt/sun/jstudio_ent8/jdk1.5.0_04/bin/java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/logs/server.log
-Djava.endorsed.dirs=/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/endorsed
-Djava.security.policy=/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/config/server.policy
-Djava.security.auth.login.config=/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/config/keystore.jks
-Djavax.net.ssl.trustStore=/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/config/cacerts.jks
-Djava.ext.dirs=/opt/sun/jstudio_ent8/jdk1.5.0_04/jre/lib/ext:/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/lib/ext
-Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=myDomain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=myDomain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=/opt/sun/jstudio_ent8/AppServ8.1UR2/config
-Djava.library.path=/opt/sun/jstudio_ent8/jdk1.5.0_04/jre/lib/i386/client:/opt/sun/jstudio_ent8/jdk1.5.0_04/jre/lib/i386:/opt/sun/jstudio_ent8/jdk1.5.0_04/jre/../lib/i386:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib:/usr/lib/lwp::/usr/lib
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
/opt/sun/jstudio_ent8/jdk1.5.0_04/lib/tools.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/activation.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/mail.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/admin-cli.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-admin.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-jstl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-logging.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee-svc.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jax-qname.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jaxr-api.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/dom.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jaxr-impl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jaxrpc-api.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jaxrpc-impl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/relaxngDatatype.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/saaj-api.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/saaj-impl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/xsdlib.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jmxremote.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jsf-api.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jmxremote_optional.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jsf-impl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/rmissl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/xalan.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/xercesImpl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-assemblytool_ja.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp_ja.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt_ja.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher_ja.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/deployhelp_ja.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee_ja.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-assemblytool_zh.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-assemblytool_zh_CN.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp_zh.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp_zh_CN.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt_zh.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt_zh_CN.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher_zh.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher_zh_CN.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/deployhelp_zh.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/deployhelp_zh_CN.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee_zh.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee_zh_CN.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-assemblytool_ko.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp_ko.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt_ko.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher_ko.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/deployhelp_ko.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee_ko.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-assemblytool_fr.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp_fr.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt_fr.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher_fr.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/deployhelp_fr.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee_fr.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-assemblytool_es.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp_es.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt_es.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher_es.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/deployhelp_es.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee_es.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-upgrade.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-ext.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/install/applications/jmsra/imqjmsra.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/imq/lib/jaxm-api.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/imq/lib/fscontext.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/ant/lib/ant.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/pointbase/lib/pbclient.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start|#]
I do notice that the class path references jdk1.5.0_04. When installing SJS I selected the separately installed jdk1.5.0_07. Could that be causing the problem?
You have great patience. -
Help me! Can't start application server after install
Starting J2EETM 1.4 Application Server Beta 2 ...
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][01.����.2003 15:17:53:421 CST][CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.1_04] from [Sun Microsystems Inc.]]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][01.����.2003 15:17:55:078 CST][ADM0020:Following is the information about the JMX MBeanServer used:]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][01.����.2003 15:17:55:078 CST][ADM0021:MBeanServer Implementation Name:[JMX]]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][01.����.2003 15:17:55:078 CST][ADM0022:MBeanServer Implementation Vendor:[Sun Microsystems]]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][01.����.2003 15:17:55:078 CST][ADM023:JMX Implementation Version:[1.2_r08]]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][01.����.2003 15:17:55:078 CST][ADM024:MBeanServer ID:[top02286a_1062400675000]]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][01.����.2003 15:17:55:078 CST][ADM025:MBeanServer Implementation Classname:[com.sun.jmx.mbeanserver.JmxMBeanServer]]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][01.����.2003 15:17:55:234 CST][ADM0002:System MBean initialized:[ias:type=controller]]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][01.����.2003 15:17:55:250 CST][ADM0002:System MBean initialized:[ias:type=configurator]]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][01.����.2003 15:17:55:250 CST][ADM0001:MBeanServer initialized successfully]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][01.����.2003 15:17:55:281 CST][ADM0005:Timestamp files for configuration created for:[server]]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][01.����.2003 15:17:55:281 CST][ADM0102: Starting a thread for tracking manual changes]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.resource.jms][01.����.2003 15:18:08:171 CST][JMS5023: JMS service successfully started. Instance Name = domain1_server, Home = [C:/Sun/j2eesdk1.4_beta2/imq/bin].]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][01.����.2003 15:18:08:750 CST][S1AS AVK Instrumentation disabled]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core.security][01.����.2003 15:18:08:765 CST][SEC1143: Loading policy provider com.sun.enterprise.security.provider.util.PolicyWrapper.]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core.transaction][01.����.2003 15:18:09:562 CST][JTS5014: Recoverable JTS instance, serverId = [100]]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.resource.resourceadapter][01.����.2003 15:18:31:218 CST][RAR5060: Install JDBC Datasources ...]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][01.����.2003 15:18:31:875 CST][Satisfying Optional Packages dependencies...]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][01.����.2003 15:18:32:062 CST][ADM0016:Unable to determine java home. This suggests that you are using a version of J2EE plugin incompatible with administration server.]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][01.����.2003 15:18:32:156 CST][[AutoDeploy] Enabling AutoDeployment service at :1062400712156]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][01.����.2003 15:18:32:156 CST][CORE5100:Loading system apps]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][01.����.2003 15:18:32:187 CST][Selecting file [C:\Sun\j2eesdk1.4_beta2\lib\install\applications\MEjbApp.ear] for autodeployment]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][01.����.2003 15:18:32:187 CST][Selecting file [C:\Sun\j2eesdk1.4_beta2\lib\install\applications\__ejb_container_timer_app.ear] for autodeployment]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.deployment][01.����.2003 15:18:33:359 CST][DPL5109: EJBC - START of EJBC for [MEjbApp]]>
Remote message: Processing beans ....
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.deployment][01.����.2003 15:18:33:531 CST][DPL5108: EJBC - Generated code for remote home and EJBObject implementations for [MEjbApp]]>
Remote message: Compiling wrapper code ....
Remote message: Compiling RMI-IIOP code ....
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.deployment][01.����.2003 15:18:41:687 CST][DPL5110: EJBC - END of EJBC for [MEjbApp]]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.deployment][01.����.2003 15:18:43:015 CST][Total Deployment Time: 10625 msec, Total EJB Compiler Module Time: 8328 msec, Portion spent EJB Compiling: 78%
Breakdown of EJBC Module Time: Total Time for EJBC: 8328 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 8156 msec (97%), JAX-RPC Generation: 31 msec (0%),
]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][01.����.2003 15:18:43:031 CST][ADM5606:Extracting changes to [/domain/applications/j2ee-application[@name='MEjbApp']]]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][01.����.2003 15:18:43:046 CST][ADM5604:Processing config change [Domain:add to xpath=/domain/applications
childXPath = /domain/applications/j2ee-application[@name='MEjbApp']]]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][01.����.2003 15:18:43:046 CST][ADM5604:Processing config change [update xpath=/domain/applications/j2ee-application[@name='MEjbApp']
attr=resource-type user-->system-all
attr=virtual-servers null-->server
]]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][01.����.2003 15:18:43:093 CST][ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy MEjbApp]]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][01.����.2003 15:18:43:812 CST][ApplicationLoader com.sun.enterprise.server.TomcatApplicationLoader@1e84195]>
org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces.
at org.apache.xerces.dom.CoreDocumentImpl.checkDOMNSErr(CoreDocumentImpl.java:2142)
at org.apache.xerces.dom.AttrNSImpl.setName(AttrNSImpl.java:149)
at org.apache.xerces.dom.AttrNSImpl.<init>(AttrNSImpl.java:110)
at org.apache.xerces.dom.CoreDocumentImpl.createAttributeNS(CoreDocumentImpl.java:1791)
at org.apache.xerces.dom.ElementImpl.setAttributeNS(ElementImpl.java:660)
at com.sun.enterprise.deployment.node.DeploymentDescriptorNode.setAttribute(DeploymentDescriptorNode.java:542)
at com.sun.enterprise.deployment.node.LocalizedNode.writeLocalizedMap(LocalizedNode.java:77)
at com.sun.enterprise.deployment.node.DisplayableComponentNode.writeDisplayableComponentInfo(DisplayableComponentNode.java:56)
at com.sun.enterprise.deployment.node.BundleNode.writeDescriptor(BundleNode.java:104)
at com.sun.enterprise.deployment.node.ApplicationNode.writeDescriptor(ApplicationNode.java:132)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.getDocument(J2EEDocumentBuilder.java:77)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.write(J2EEDocumentBuilder.java:120)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.descriptorToString(J2EEDocumentBuilder.java:153)
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:158)
at com.sun.enterprise.server.ApplicationLoader.createRootMBean(ApplicationLoader.java:180)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:177)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:154)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:462)
at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:429)
at com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:413)
at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:296)
at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:104)
at com.sun.enterprise.admin.server.core.mbean.config.ManagedServerInstance.multicastEvent(ManagedServerInstance.java:3553)
at com.sun.enterprise.admin.server.core.mbean.config.ManagedServerInstance.multicastEvent(ManagedServerInstance.java:3479)
at com.sun.enterprise.admin.server.core.mbean.config.ManagedServerInstance.deployJ2EEApplicationArchiveOrDirectory(ManagedServerInstance.java:792)
at com.sun.enterprise.admin.server.core.mbean.config.ManagedServerInstance.deployJ2EEApplication(ManagedServerInstance.java:695)
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:324)
at com.sun.enterprise.admin.server.core.jmx.Introspector.invokeMethodOn(Introspector.java:181)
at com.sun.enterprise.admin.server.core.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:130)
at com.sun.enterprise.admin.server.core.jmx.ASMBeanServerImpl.invoke(ASMBeanServerImpl.java:215)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:404)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:271)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:164)
at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:185)
at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:160)
at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:82)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
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:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
java.lang.IllegalArgumentException: �� newTemplate �� DOMSource ����������������������
at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:346)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.write(J2EEDocumentBuilder.java:125)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.descriptorToString(J2EEDocumentBuilder.java:153)
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:158)
at com.sun.enterprise.server.ApplicationLoader.createRootMBean(ApplicationLoader.java:180)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:177)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:154)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:462)
at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:429)
at com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:413)
at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:296)
at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:104)
at com.sun.enterprise.admin.server.core.mbean.config.ManagedServerInstance.multicastEvent(ManagedServerInstance.java:3553)
at com.sun.enterprise.admin.server.core.mbean.config.ManagedServerInstance.multicastEvent(ManagedServerInstance.java:3479)
at com.sun.enterprise.admin.server.core.mbean.config.ManagedServerInstance.deployJ2EEApplicationArchiveOrDirectory(ManagedServerInstance.java:792)
at com.sun.enterprise.admin.server.core.mbean.config.ManagedServerInstance.deployJ2EEApplication(ManagedServerInstance.java:695)
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:324)
at com.sun.enterprise.admin.server.core.jmx.Introspector.invokeMethodOn(Introspector.java:181)
at com.sun.enterprise.admin.server.core.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:130)
at com.sun.enterprise.admin.server.core.jmx.ASMBeanServerImpl.invoke(ASMBeanServerImpl.java:215)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:404)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:271)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:164)
at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:185)
at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:160)
at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:82)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
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:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][01.����.2003 15:18:43:875 CST][core.error_while_creating_jsr77_root_mbean
javax.management.MBeanException
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:165)
at com.sun.enterprise.server.ApplicationLoader.createRootMBean(ApplicationLoader.java:180)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:177)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:154)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:462)
at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:429)
at com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:413)
at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:296)
at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:104)
at com.sun.enterprise.admin.server.core.mbean.config.ManagedServerInstance.multicastEvent(ManagedServerInstance.java:3553)
at com.sun.enterprise.admin.server.core.mbean.config.ManagedServerInstance.multicastEvent(ManagedServerInstance.java:3479)
at com.sun.enterprise.admin.server.core.mbean.config.ManagedServerInstance.deployJ2EEApplicationArchiveOrDirectory(ManagedServerInstance.java:792)
at com.sun.enterprise.admin.server.core.mbean.config.ManagedServerInstance.deployJ2EEApplication(ManagedServerInstance.java:695)
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:324)
at com.sun.enterprise.admin.server.core.jmx.Introspector.invokeMethodOn(Introspector.java:181)
at com.sun.enterprise.admin.server.core.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:130)
at com.sun.enterprise.admin.server.core.jmx.ASMBeanServerImpl.invoke(ASMBeanServerImpl.java:215)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:404)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:271)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:164)
at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:185)
at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:160)
at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:82)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
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:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: java.lang.IllegalArgumentException: �� newTemplate �� DOMSource ����������������������
at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:346)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.write(J2EEDocumentBuilder.java:125)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.descriptorToString(J2EEDocumentBuilder.java:153)
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:158)
... 33 more
]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][01.����.2003 15:18:43:875 CST][core.error_while_setting_jsr77_state
javax.management.MBeanException
at com.sun.enterprise.server.MgmtMBeansManager.setState(MgmtMBeansManager.java:1072)
at com.sun.enterprise.server.MgmtMBeansManager.setApplicationState(MgmtMBeansManager.java:1028)
at com.sun.enterprise.server.ApplicationLoader.setState(ApplicationLoader.java:277)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:190)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:154)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:462)
at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:429)
at com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:413)
at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:296)
at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:104)
at com.sun.enterprise.admin.server.core.mbean.config.ManagedServerInstance.multicastEvent(ManagedServerInstance.java:3553)
at com.sun.enterprise.admin.server.core.mbean.config.ManagedServerInstance.multicastEvent(ManagedServerInstance.java:3479)
at com.sun.enterprise.admin.server.core.mbean.config.ManagedServerInstance.deployJ2EEApplicationArchiveOrDirectory(ManagedServerInstance.java:792)
at com.sun.enterprise.admin.server.core.mbean.config.ManagedServerInstance.deployJ2EEApplication(ManagedServerInstance.java:695)
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:324)
at com.sun.enterprise.admin.server.core.jmx.Introspector.invokeMethodOn(Introspector.java:181)
at com.sun.enterprise.admin.server.core.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:130)
at com.sun.enterprise.admin.server.core.jmx.ASMBeanServerImpl.invoke(ASMBeanServerImpl.java:215)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:404)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:271)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:164)
at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:185)
at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:160)
at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:82)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
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:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: javax.management.MBeanException
at com.sun.enterprise.server.MgmtMBeansManager.setState(MgmtMBeansManager.java:1065)
... 34 more
Caused by: java.lang.Exception: mbean not registered
... 35 more
]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.container.ejb][01.����.2003 15:18:44:140 CST][[**BaseContainer [2.0]**]: MEJBBean. Instantiated BaseContainer...]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core.classloading][01.����.2003 15:18:44:250 CST][LDR5010: All ejb(s) of [MEjbApp] loaded successfully!]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][01.����.2003 15:18:44:250 CST][core.error_while_setting_jsr77_state
javax.management.MBeanException
at com.sun.enterprise.server.MgmtMBeansManager.setState(MgmtMBeansManager.java:1072)
at com.sun.enterprise.server.MgmtMBeansManager.setApplicationState(MgmtMBeansManager.java:1028)
at com.sun.enterprise.server.ApplicationLoader.setState(ApplicationLoader.java:277)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:202)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:154)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:462)
at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:429)
at com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:413)
at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:296)
at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:104)
at com.sun.enterprise.admin.server.core.mbean.config.ManagedServerInstance.multicastEvent(ManagedServerInstance.java:3553)
at com.sun.enterprise.admin.server.core.mbean.config.ManagedServerInstance.multicastEvent(ManagedServerInstance.java:3479)
at com.sun.enterprise.admin.server.core.mbean.config.ManagedServerInstance.deployJ2EEApplicationArchiveOrDirectory(ManagedServerInstance.java:792)
at com.sun.enterprise.admin.server.core.mbean.config.ManagedServerInstance.deployJ2EEApplication(ManagedServerInstance.java:695)
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:324)
at com.sun.enterprise.admin.server.core.jmx.Introspector.invokeMethodOn(Introspector.java:181)
at com.sun.enterprise.admin.server.core.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:130)
at com.sun.enterprise.admin.server.core.jmx.ASMBeanServerImpl.invoke(ASMBeanServerImpl.java:215)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:404)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:271)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:164)
at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:185)
at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:160)
at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:82)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
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:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: javax.management.MBeanException
at com.sun.enterprise.server.MgmtMBeansManager.setState(MgmtMBeansManager.java:1065)
... 34 more
Caused by: java.lang.Exception: mbean not registered
... 35 more
]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][01.����.2003 15:18:44:328 CST][ADM1042:Status of event to instance:[success]]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][01.����.2003 15:19:36:375 CST][[AutoDeploy] Successfully autodeployed : C:\Sun\j2eesdk1.4_beta2\lib\install\applications\MEjbApp.ear.]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.deployment][01.����.2003 15:21:01:796 CST][DPL5109: EJBC - START of EJBC for [__ejb_container_timer_app]]>
Remote message: Processing beans ....
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.deployment][01.����.2003 15:21:34:859 CST][DPL5107: EJBC - Generated code for EJBLocalHOme, EJBLocalObject implementations for [__ejb_container_timer_app]]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.deployment][01.����.2003 15:21:34:859 CST][DPL5110: EJBC - END of EJBC for [__ejb_container_timer_app]]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.deployment][01.����.2003 15:23:00:781 CST][Total Deployment Time: 91282 msec, Total EJB Compiler Module Time: 33063 msec, Portion spent EJB Compiling: 36%
Breakdown of EJBC Module Time: Total Time for EJBC: 33063 msec, CMP Generation: 1031 msec (3%), Java Compilation: 3594 msec (10%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][01.����.2003 15:25:50:437 CST][ADM5606:Extracting changes to [/domain/applications/j2ee-application[@name='__ejb_container_timer_app']]]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][01.����.2003 15:25:50:437 CST][ADM5604:Processing config change [Domain:add to xpath=/domain/applications
childXPath = /domain/applications/j2ee-application[@name='__ejb_container_timer_app']]]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][01.����.2003 15:25:50:437 CST][ADM5604:Processing config change [update xpath=/domain/applications/j2ee-application[@name='__ejb_container_timer_app']
attr=resource-type user-->system-all
attr=virtual-servers null-->server
]]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][01.����.2003 15:25:50:468 CST][ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy __ejb_container_timer_app]]>
<[����][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][01.����.2003 15:25:50:843 CST][ApplicationLoader com.sun.enterprise.server.TomcatApplicationLoader@1927ba1]>
org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces.
at org.apache.xerces.dom.CoreDocumentImpl.checkDOMNSErr(CoreDocumentImpl.java:2142)
at org.apache.xerces.dom.AttrNSImpl.setName(AttrNSImpl.java:149)
at org.apache.xerces.dom.AttrNSImpl.<init>(AttrNSImpl.java:110)
at org.apache.xerces.dom.CoreDocumentImpl.createAttributeNS(CoreDocumentImpl.java:1791)
at org.apache.xerces.dom.ElementImpl.setAttributeNS(ElementImpl.java:660)
at com.sun.enterprise.deployment.node.DeploymentDescriptorNode.setAttribute(DeploymentDescriptorNode.java:542)
at com.sun.enterprise.deployment.node.LocalizedNode.writeLocalizedMap(LocalizedNode.java:77)
at com.sun.enterprise.deployment.node.DisplayableComponentNode.writeDisplayableComponentInfo(DisplayableComponentNode.java:56)
at com.sun.enterprise.deployment.node.BundleNode.writeDescriptor(BundleNode.java:104)
at com.sun.enterprise.deployment.node.ApplicationNode.writeDescriptor(ApplicationNode.java:132)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.getDocument(J2EEDocumentBuilder.java:77)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.write(J2EEDocumentBuilder.java:120)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.descriptorToString(J2EEDocumentBuilder.java:153)
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:158)
at com.sun.enterprise.server.ApplicationLoader.createRootMBean(ApplicationLoader.java:180)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:177)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:154)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:462)
at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeAthere is an error in either one of your web.xml files or in the server.xml..
it looks like an xml parse error..
did deploy app changes before this? or update some context stuff within server.xml?? -
Can't start application server in Netbeans
when I run the application server from the netbeans, i get this pop up message
" The Sun Java Application Server 8.1 couldnt start.
More insformation about the cause is in the server log file.
Posssible reasons include
-port conflicts.(use netstat -a to detect possible port numbers
already used by the operating system.)
-Incorrect server configuration(domain.xml to be corrected manually.)
-Corrupted Deployment Application preventing the server to start.(
this can be seen in the server.log file. In this case, domain needs to
be modified).
If anyone has any clue about the problem then please help me.
Thanks
Terenceshould I uninstall the lastest beta 2 and try another version ? I am using win xp pro.
-
Can't start application server - opmnctl startall don't work
Hi
i have installed DB and AS on the same machiine
db is 10.2.0.4.0
AS is 10.1.3.1
Linux OEL 4.8
i use the following to startup the AS
export ORACLE_HOME=/u01/app/oracle/product/10.1.3.1/OracleAS_2
export PATH=$PATH:$ORACLE_HOME/bin
export PATH=$PATH:$ORACLE_HOME/opmn/bin
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib
cd /u01/app/oracle/product/10.1.3.1/OracleAS_2/opmn/bin
./opmnctl startall
but i got the following in /u01/app/oracle/product/10.1.3.1/OracleAS_2/opmn/logs/default_group~oc4j_soa~default_group~1.log
<2009-12-30 17:28:43,470> <ERROR> <collaxa> <ProcessJob::execute> Error when connecting to http://localhost.localdomain:7777
<2009-12-30 17:28:43,471> <ERROR> <collaxa> <ProcessJob::execute> Error when connecting to http://ASRH4:7777/orabpel
<2009-12-30 17:28:43,472> <ERROR> <collaxa> <ProcessJob::execute> Error when connecting to http://192.168.25.105:7777/orabpel
<2009-12-30 17:28:43,473> <ERROR> <collaxa> <ProcessJob::execute> Error when connecting to http://localhost.localdomain:7777/orabpel
<2009-12-30 17:28:43,474> <ERROR> <collaxa> <ProcessJob::execute> Error when connecting to http://localhost:7777/orabpel
<2009-12-30 17:28:43,474> <ERROR> <collaxa> <ProcessJob::execute> Attempt (15/15
and it don't start
the db ons.config is
localport=6100
remoteport=6200
loglevel=3
the AS opmn.xml important parts are
<notification-server interface="ipv4">
<port local="7100" remote="7200" request="7003"/>
<ssl enabled="true" wallet-file="$ORACLE_HOME/opmn/conf/ssl.wlt/default"/>
</notification-server>
please any help?
Thanks
Edited by: user8803475 on Dec 29, 2009 10:54 PMHi Mr Hans,
Firewall/SELINUX are disabled
i did a "FRESH" install of AS on the same box that have the db ,
the ons.config for the db is
localport=7100
remoteport=7200
loglevel=3
but i still get this error during installation:-
opmn id=ASRH4:6200
0 of 2 processes started.
ias-instance id=as5.localhost.localdomain
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++--------------------------------------------------------------------------------ias-component/process-type/process-set:
HTTP_Server/HTTP_Server/HTTP_Server/
Error
--> Process (index=1,uid=1902257481,pid=9616)
failed to start a managed process after the maximum retry limit
Log:
/u01/app/oracle/product/10.1.3.1/OracleAS_3/opmn/logs//HTTP_Server~1.log
ias-component/process-type/process-set:
default_group/oc4jhome/default_group/
Error
--> Process (index=1,uid=1902257482,pid=9565)
time out while waiting for a managed process to start
Log:
the /etc/hosts contents are:-
192.168.25.105 localhost.localdomain localhost ASRH4
192.168.25.105 ASRH4 ASRH4 ASRH4
also running hostname command gives -> ASRH4
Please advise?
Thanks -
OBIEE 11g- unable to start application server
Dear All,
I have recently installed OBIEE 11g 11.1.1.6.0 for the first time (enterprise install)
am able to login to anaytics page and create reports, but Iam not able to connect to enterprise manger , console.
Going through various posts, i came to know i should start Application server.
which i was not able to. was getting error as
'unable to get file lock will retry'.
I tried deleting
Navigate to the path : <OBIEE HOME>/C:\Middleware\user_projects\domains\bifoundation_domain\servers\AdminServer\tmp
“AdminServer.lok” file.
it still did not start
I try doing the same for “bi_server1″ lock file. but am not able to delete this file.
It says its in use. but i did not find any Java process running.
Can you please help. how can i start my Application server on windows OS.
Appreciate your help.
thanks in advance.
AchalaFirstly we have shutdown the application for OS activity for creating mount point(related to Business)
then we where trying to start the application all the work process are running with semaphore 50 , there no such error mesg ,just the work process are hang at running state with user SAPSYS
the i have shutdown the application and clean the ipc and again i restarted the app still the same issue
Hope u understand
Thank you
Haroon -
Authentication error while connecting to application server IntegratedWebL
When I start the IntegrationWeblogicServer in JDeveloper11.1.1.3.0, the server can be started, the IntegratedWeblogicServer cann't be connected because of the authentication error.
The integrated weblogic server can be started successfully outside the Jdevelper, and I never changed the password of user weblogic.
<2010-8-24 下午02时55分17秒 CST> <Warning> <Server> <BEA-002611> <Hostname "ppan-cn.cn.oracle.com", maps to multiple IP addresses: 10.182.254.102, 192.168.174.1, 192.168.65.1>
<2010-8-24 下午02时55分17秒 CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<2010-8-24 下午02时55分17秒 CST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
User: weblogic, failed to be authenticated.
**** Authentication error while connecting to application server IntegratedWebLogicServer. Please check settings.
**** Failed to complete start-up of application server IntegratedWebLogicServer.
[Server Instance IntegratedWebLogicServer is shutting down. All applications currently running will be terminated and undeployed.]
[Forcing termination of IntegratedWebLogicServer]
taskkill /F /PID 748
Process exited.
What's wrong with the JDeveloper11.1.1.3.0? And How to fix it? Any help is appreciated in advance.
_PaulaHi Paula:
You may want to check if one of your applications has its own users and groups settings. If you define your own Application's users ang groups settings, you may need to uncheck the setting in JDeveloper ADF Security wizard to avoid overwriting the embedded WLS security settings. Otherwise, even you reset your embedded WLS or recreate it, its settings will be overwritten again once you run your application on it.
The way to reset or recreate your embedded WLS is to follow Frank's tips.
Good luck,
Alex -
Can't start report server on windows 2000
I can't start report server with error code 186, my tnsname.ora is
REP60_DUQ = Rep60_DUQ
is it error?
who can tell me how to resolve it!!!but I have add tnsnames.ora following
Rep60_REPORT_SERVER =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = REPORT_SERVER)(PORT = 1951))
then I start report server with:
/PATH_TO_REPORTSERVER/report60_server start
it still says:
REP-0186: Daemon failed to listen to port
what is problem?
any thing must be done to activate changes in
tnsnames.ora?
null -
Server Error Either the Macromedia application server(s) are unreachable or none of them has a mapping to process this request.I got this error.I installed coldfusion 8 on windows 7 64 bit.What should I do?Can't I use coldfusion?Is there any suggestion???
Yes I google before and I tried to do all advice.But there is nothing change.Can you explain or send a link for solving this?
-
Can't start http server ASControl service
Hi, I installed http server from companion cd for oracle 10.2.0.3 but when configuration assistants was setting http server give the message failed.
Now i can´t start http server service.
INFO: El asistente de configuración "OC4J Configuration Assistant" se ha ejecutado correctamente
INFO: Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe startall
Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe has failed
INFO: El asistente de configuración "Starting HTTP Server" ha fallado
*** Starting OUICA ***
Oracle Home set to C:\oracle\product\10.2.0\http_1
Configuration directory is set to C:\oracle\product\10.2.0\http_1\cfgtoollogs. All xml files under the directory will be processed
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Created a new file C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak
GRAVE: OUI-25031: Fallo de algunos asistentes de configuración. Se recomienda volver a probar los asistentes de configuración en este momento. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
1. Compruebe en el panel Detalles de la pantalla de Asistentes de Configuración los errores resultantes de los fallos.
2. Corrija los errores que causan estos fallos.
3. Seleccione los asistentes que han fallado y haga clic en el botón 'Reintentar' para volver a probarlos.
INFO: Usuario seleccionado: Sí/Aceptar
INFO: Iniciando la ejecución de los asistentes de configuración
INFO: Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe startall
Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe has failed
INFO: El asistente de configuración "Starting HTTP Server" ha fallado
*** Starting OUICA ***
Oracle Home set to C:\oracle\product\10.2.0\http_1
Configuration directory is set to C:\oracle\product\10.2.0\http_1\cfgtoollogs. All xml files under the directory will be processed
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak.1
GRAVE: OUI-25031: Fallo de algunos asistentes de configuración. Se recomienda volver a probar los asistentes de configuración en este momento. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
1. Compruebe en el panel Detalles de la pantalla de Asistentes de Configuración los errores resultantes de los fallos.
2. Corrija los errores que causan estos fallos.
3. Seleccione los asistentes que han fallado y haga clic en el botón 'Reintentar' para volver a probarlos.
INFO: Usuario seleccionado: Sí/Aceptar
INFO: Iniciando la ejecución de los asistentes de configuración
INFO: Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe startall
Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe has failed
INFO: El asistente de configuración "Starting HTTP Server" ha fallado
*** Starting OUICA ***
Oracle Home set to C:\oracle\product\10.2.0\http_1
Configuration directory is set to C:\oracle\product\10.2.0\http_1\cfgtoollogs. All xml files under the directory will be processed
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak.2
GRAVE: OUI-25031: Fallo de algunos asistentes de configuración. Se recomienda volver a probar los asistentes de configuración en este momento. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
1. Compruebe en el panel Detalles de la pantalla de Asistentes de Configuración los errores resultantes de los fallos.
2. Corrija los errores que causan estos fallos.
3. Seleccione los asistentes que han fallado y haga clic en el botón 'Reintentar' para volver a probarlos.
INFO: Usuario seleccionado: Sí/Aceptar
INFO: Iniciando la ejecución de los asistentes de configuración
INFO: Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe startall
Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe has failed
INFO: El asistente de configuración "Starting HTTP Server" ha fallado
*** Starting OUICA ***
Oracle Home set to C:\oracle\product\10.2.0\http_1
Configuration directory is set to C:\oracle\product\10.2.0\http_1\cfgtoollogs. All xml files under the directory will be processed
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak.3
GRAVE: OUI-25031: Fallo de algunos asistentes de configuración. Se recomienda volver a probar los asistentes de configuración en este momento. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
1. Compruebe en el panel Detalles de la pantalla de Asistentes de Configuración los errores resultantes de los fallos.
2. Corrija los errores que causan estos fallos.
3. Seleccione los asistentes que han fallado y haga clic en el botón 'Reintentar' para volver a probarlos.
INFO: Usuario seleccionado: Sí/Aceptar
INFO: Iniciando la ejecución de los asistentes de configuración
INFO: Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe startall
Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe has failed
INFO: El asistente de configuración "Starting HTTP Server" ha fallado
*** Starting OUICA ***
Oracle Home set to C:\oracle\product\10.2.0\http_1
Configuration directory is set to C:\oracle\product\10.2.0\http_1\cfgtoollogs. All xml files under the directory will be processed
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak.4
GRAVE: OUI-25031: Fallo de algunos asistentes de configuración. Se recomienda volver a probar los asistentes de configuración en este momento. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
1. Compruebe en el panel Detalles de la pantalla de Asistentes de Configuración los errores resultantes de los fallos.
2. Corrija los errores que causan estos fallos.
3. Seleccione los asistentes que han fallado y haga clic en el botón 'Reintentar' para volver a probarlos.
INFO: Usuario seleccionado: Sí/Aceptar
INFO: Iniciando la ejecución de los asistentes de configuración
INFO: Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe startall
Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe has failed
INFO: El asistente de configuración "Starting HTTP Server" ha fallado
*** Starting OUICA ***
Oracle Home set to C:\oracle\product\10.2.0\http_1
Configuration directory is set to C:\oracle\product\10.2.0\http_1\cfgtoollogs. All xml files under the directory will be processed
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak.5
GRAVE: OUI-25031: Fallo de algunos asistentes de configuración. Se recomienda volver a probar los asistentes de configuración en este momento. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
1. Compruebe en el panel Detalles de la pantalla de Asistentes de Configuración los errores resultantes de los fallos.
2. Corrija los errores que causan estos fallos.
3. Seleccione los asistentes que han fallado y haga clic en el botón 'Reintentar' para volver a probarlos.
INFO: Usuario seleccionado: Sí/Aceptar
INFO: Iniciando la ejecución de los asistentes de configuración
INFO: Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe startall
Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe has failed
INFO: El asistente de configuración "Starting HTTP Server" ha fallado
*** Starting OUICA ***
Oracle Home set to C:\oracle\product\10.2.0\http_1
Configuration directory is set to C:\oracle\product\10.2.0\http_1\cfgtoollogs. All xml files under the directory will be processed
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak.6
GRAVE: OUI-25031: Fallo de algunos asistentes de configuración. Se recomienda volver a probar los asistentes de configuración en este momento. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
1. Compruebe en el panel Detalles de la pantalla de Asistentes de Configuración los errores resultantes de los fallos.
2. Corrija los errores que causan estos fallos.
3. Seleccione los asistentes que han fallado y haga clic en el botón 'Reintentar' para volver a probarlos.
INFO: Usuario seleccionado: Sí/Aceptar
INFO: --------------------------------------
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolAllCommands" contiene todos los comandos que van a ejecutar los asistentes de configuración. Este archivo se puede utilizar para ejecutar los asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak.7
GRAVE: OUI-25029: Uno o más asistentes de configuración "recomendados" no han terminado correctamente. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
INFO: Usuario seleccionado: Sí/Aceptar
INFO:
*** Fin de Instalación Página***
La instalación de Oracle Database 10g Companion Products ha sido correcta, pero han fallado, se han cancelado o se han saltado algunos asistentes de configuración opcionales.
ADVERTENCIA: ¿Seguro que desea salir?
INFO: Usuario seleccionado: Sí/Aceptaruser13078324 wrote:
How ?in cmd run this
netstat -an
and search for a line like
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
The important is TCP, 80 and keyword LISTENING
Other may differ -
Starting application server from IDE
I'm trying to start the application server from an evaluation copy of
Visual Cafe 4.5 Enterprise Edition. When I choose Project -> Start
Application Server from the menu, a window briefly opens with "Start
Application Server" as its title and a logo of a spinning W. After
the W spins about one time the window close, with no error message
reported.
I would like to know what I should do in order to start the
application server (A developer's license of WebLogic is included)
from the IDE.Look at the weblogic.log file
(%BEA_HOME%\wlserver6.0\config\mydomain\logs\weblogic.log) to see if
there are any error messages printed there. If not, it is probably a
license issue in that the license.bea file must be in the CLASSPATH used
to start the app server.
Tom Ewall wrote:
I'm trying to start the application server from an evaluation copy of
Visual Cafe 4.5 Enterprise Edition. When I choose Project -> Start
Application Server from the menu, a window briefly opens with "Start
Application Server" as its title and a logo of a spinning W. After
the W spins about one time the window close, with no error message
reported.
I would like to know what I should do in order to start the
application server (A developer's license of WebLogic is included)
from the IDE. -
Why is it recommended to have a separate PeopleSoft ID for starting Application Server in PeopleSoft
HI,
Why is it recommended to have a separate PeopleSoft ID for starting Application Server in PeopleSoftHello:
You can put the JS function into the HTML Header section of the Page defintion.
<script>
function doDelete(id) {
$x('P14_DEL_ID').value=id;
doSubmit('DELETE');
</script>Define a new page process whose process point is 'On Submit: After Computations and Validations'. For the Process Source specify
Delete from <table> where key_column=:p14_del_id;Under Conditional Processing select 'Request=Expression 1'. For Expression 1 specify 'DELETE'
Hope this helps.
Varad -
I'm travelling and have had my iBook G4 connected to the free ADSL here. The computer started acting wierd, and I started troubleshooting. Realized that I had left my firewall off since doing an update with my iMac a few weeks ago.
Can't run Disk Utility - it stops about 1/3 of the way through Permissions verify and/or Permissions Repair.
Anyhow, I re-installed Norton Internet Security, updated the virus definitions and did 2 full scans. Nothing.
If I leave the computer on for more than a few hrs, and then try to start any program, I get a "Can't start application - 10810" message.
Any ideas? I figure I'll reinstall OSX when I get home in a week if nothing else.From what I've heard, the 10810 error is a non-specific error that provides no clue as to what the real problem is.
All I know is that my TiBook 800MHz OS 10.3.9 started exhibiting the same behavior several weeks ago. I've tried everything short of wiping the computer and reinstalling OSX. Disk Utility is a no go. Wondered if maybe my screen saver was the culprit, but disabling had no effect.
My problem was exascerbated by the fact that my Dock would also hang. Couldn't force quit, even using the Process Monitor. I had to do a forced shut down with the power button and restart about four times a day. I traced this problem to the desktop pictures, of all things. Turned off random cycling and the Dock hang went away. Now, at least I can use a real system shutdown/restart when applications won't launch.
It feels to me like a bug in a recent Apple software update. I wish they would track it down, because the situation is quite frustrating. -
Error occurred while starting application with EP 6.0
Hi all,
when deploy an application, I obtain this error:
===========================================================================
Deployment started Thu May 21 16:50:58 CEST 2009
===========================================================================
Starting Deployment of fgp_ita18_rassegne_iv_wsrsgst
Finished with warnings: development component 'fgp_ita18_rassegne_iv_wsrsgst'/'ferrero.com'/'local'/'20090521121654'/'0':Caught exception during application startup from SAP J2EE Engine's deploy service:java.rmi.RemoteException: Error occurred while starting application ferrero.com/fgp_ita18_rassegne_iv_wsrsgst and wait. Reason: Clusterwide exception: server ID 772336550:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: *Application ferrero.com/fgpita18_rassegne_iv_wsrsgst cannot be started. Reason: it has hard reference to resource FGP_RSGSTMP with type javax.sql.DataSource, which is not active on the server*._ at com.sap.engine.services.deploy.server.ReferenceResolver.processUsageOfComponent(ReferenceResolver.java:533) at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:346) at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:162) at com.sap.engine.services.deploy.server.application.StartTransaction.beginLocal(StartTransaction.java:141) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:356) at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:95) at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:233) at com.sap.engine.frame.core.thread.Task.run(Task.java:64) at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:83) at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:156)server ID 772336551:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application ferrero.com/fgp_ita18_rassegne_iv_wsrsgst cannot be started. Reason: it has hard reference to resource FGP_RSGSTMP with type javax.sql.DataSource, which is not active on the server. at com.sap.engine.services.deploy.server.ReferenceResolver.processUsageOfComponent(ReferenceResolver.java:533) at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:346) at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:162) at com.sap.engine.services.deploy.server.application.StartTransaction.beginLocal(StartTransaction.java:141) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:356) at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:95) at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:233) at com.sap.engine.frame.core.thread.Task.run(Task.java:64) at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:83) at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:156)server ID 712797150:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application ferrero.com/fgp_ita18_rassegne_iv_wsrsgst cannot be started. Reason: it has hard reference to resource FGP_RSGSTMP with type javax.sql.DataSource, which is not active on the server. at com.sap.engine.services.deploy.server.ReferenceResolver.processUsageOfComponent(ReferenceResolver.java:533) at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:346) at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:162) at com.sap.engine.services.deploy.server.application.StartTransaction.beginLocal(StartTransaction.java:141) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:356) at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:95) at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:233) at com.sap.engine.frame.core.thread.Task.run(Task.java:64) at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:83) at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:156)server ID 712797151:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application ferrero.com/fgp_ita18_rassegne_iv_wsrsgst cannot be started. Reason: it has hard reference to resource FGP_RSGSTMP with type javax.sql.DataSource, which is not active on the server. at com.sap.engine.services.deploy.server.ReferenceResolver.processUsageOfComponent(ReferenceResolver.java:533) at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:346) at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:162) at com.sap.engine.services.deploy.server.application.StartTransaction.begin(StartTransaction.java:136) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292) at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342) at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126) at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245) at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4712) at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4617) at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4590) at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319) at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200) at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:219) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176) (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of fgp_ita18_rassegne_iv_wsrsgst finished with Warning (Duration 98744 ms)
===========================================================================
Deployment ended Thu May 21 16:52:39 CEST 2009As per as i know this is your custom patch but not delivered by sap.Is the development done fine because it is taking as reference as some resource mentioned in the log and till that is active this deployment will not go fine.
Have you some other deployment that would be activating that resource and then this patch should be done.
Thanks
Rishi Abrol
Maybe you are looking for
-
Integrating two iviews in a single page in Portal
Hello all: I am trying to integrate two iviews into a single page, in portal, but i am able to see one iview running fine and for other iview it says serivce not found. But when i preview the iviews seperately they work fine. please suggest me if i a
-
Select-options in Dialog Programming
Hi, I am designing a custom dialog programming screen. I want to create a filed on thescreen which can allow the range of values to be entered like select-options in a report. How do I create a field which can accept range of values in dialog program
-
Calendar with Drill Down Report
Hello, Everybody. I am new to Application Express. Please any one tell me step by step how to make calendar with drill down report. Waiting for valuable reply. Thanks Rahul
-
Command-X (cut) doesn't work in finder
If I use "Finder" and I want to "cut" a file the shortcut (command X) doesn't work and in the menu(edit) "cut" is grey. I can only use drag&drop... in "textedit" it's possible to "cut" words! What's going wrong? Please help! regards soho
-
OBIEE 11g Login page customization
Hi All, I have to place the company logo in OBIEE login page background image (Blue color Background). Kindly help me to do it. Thanks, Haree