Apache Tomcat 5.5.20 could not start

Hi experts,
i have the following problem by starting TomCat. I have install BO Enterprise XI 3.0.
Before getting this problem it was very difficult to start the Server. I had to click at least five Minutes till the server starts.
Now it is not starting anymore.
SIA ist working without problem.
Could you please help?
Thank you in Advance
Cheers

I'm evaluating Crystal reports server 2008 in Windows 2003 R2 server (4Gb Ram). When upgrading Win 2003 to SP2 Tomcat service couldn't start.
"C:\Archivos de programa\Business Objects\Tomcat55\bin\tomcat5.exe" //RS//BOE120Tomcat -requestreport 8000
According to
http://www.forumtopics.com/busobj/viewtopic.php?p=554540&sid=112a146801723064a073894175a24404
http://commons.apache.org/daemon/procrun.html
I changed XX:MaxPermSize at HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Procrun 2.0\BOE120Tomcat\Parameters\Java\Options
-Djava.library.path=C:\WINDOWS\system32\;C:\Archivos de programa\Business Objects\BusinessObjects Enterprise 12.0\win32_x86\
-Dcatalina.base=C:\Archivos de programa\Business Objects\Tomcat55\
-Dcatalina.home=C:\Archivos de programa\Business Objects\Tomcat55\
-Djava.endorsed.dirs=C:\Archivos de programa\Business Objects\Tomcat55\common\endorsed\
-Dbobj.enterprise.home=C:\Archivos de programa\Business Objects\BusinessObjects Enterprise 12.0\
-Xrs
-XX:MaxPermSize=50m
-Dbusinessobjects.olap.bin=
-Dbusinessobjects.olap.stylesheets=C:\Archivos de programa\Business Objects\OLAP Intelligence 12.0\stylesheets\
-Djava.awt.headless=true
nothing happened. It seemed --JvmMx was the parameter (jvmMx key?). It was 1024 then I set it to 128
tomcat service starts successfully again
Edited by: asaidel on Jun 17, 2009 11:19 PM

Similar Messages

Sun J2EE 1.4 Server domain could not start (org/apache/common/launcher/..)

I am having problem with starting Sun J2EE Server 1.4. I had no problem with starting and stopping the server until today. I was not able to figure out what the problem is. I have tried reinstallation but did not work either. I also have reinstalled my J2SDK, but did not fix the problem. I am using J2SDK1.4.2_03 on Windows 2003 Server. Before the problem occured, I was working on a simple JMS applcation and trying to connect to J2EE server from a standalone JMS client at different machine. I am not sure what really caused the problem, but uninstalling it and reinstalling it does not change anything.
Here is my error message when I do start-domain domain1 at asadmin mode:
asadmin> start-domain domain1
Starting Domain domain1, please wait.
Log redirected to C:\Sun\AppServer\domains\domain1\logs\server.log.
abnormal subprocess termination: Detailed Message:Error: org/apache/commons/launcher/LaunchFilter
CLI156 Could not start the domain domain1.
I have tried to start it by using startserv.bat at domain1 directory and also the desktop shortcut Start Default Domain. Nothing works. I'do apprecited it if you can share any ideas or suggestions regarding this issue.
Thank you in advance.

I made some changes to my enviroment variables and added jar files to the J2SDK <<J2SDK_HOME>>/jre/lib/ext folder in order to run the standalone JMS client.
Here is my classpath settings:
.;C:\Sun\AppServer\lib\j2ee.jar;
C:\Sun\AppServer\lib\appserv-admin.jar;
C:\Sun\AppServer\lib\appserv-rt.jar;
C:\Sun\AppServer\lib\appserv-rt.jar;
C:\Sun\AppServer\lib\appserv-ext.jar;
C:\Sun\AppServer\lib\install\applications\jmsra\imq.jar;
C:\Sun\AppServer\lib\install\applications\jmsra\imqadmin.jar;
C:\Sun\AppServer\lib\install\applications\jmsra\imqjmsra.jar;
C:\Sun\AppServer\lib\install\applications\jmsra\imqutil.jar;
C:\Sun\AppServer\imq\lib\fscontext.jar;C:\J2EE\tutorial\j2eetutorial14\examples\ejb\simplemessage\SimpleMSGAppClient.jar
I also have added appserv-rt.jar, appserv-rt.jar, appserv-ext.jar, imq.jar, imqadmin.jar, imqjmsra.jar, and imqutil.jar in the <<J2SDK_HOME>>/jre/lib/ext/ folder. I know they were redundant but just wanted to make sure. Can any of these be causing the problem?
Again, thank you and let me know if you need any other info.

Could not start Tomcat 6 on XP

Hi,
I have installed Apache Tomcat 6 in my Windows XP.
When I try to start it from Control Panel-->Administrative tools-->Services I'm getting the following error.
"Windows Could not start Apache Tomcat on Local Computer. For more information, review the System Event Log.
If this is a non-Microsoft service vendor, and refer to service specific error code 0. "
Could anyone help me in this.
Thanks in advance.

Hi,
Working with Tomcat often, I seem to come across the same issue again and again so I created a file to remind me ''all the moving parts'' in tomcat.
I am using Sun role manager as an example. Hope this helps.
--Change the imagepath in the registry
HKEY_LOCAL_MACHINE --> SYSTEM --> CurrentControlSet --> Services --> Tomcat5 --> ImagePath
Change the Value data
-- Typically it will be C:\Program Files\Sun Role Manager\SRM-4.1\tomcat55\bin\tomcat5.exe //RS//Tomcat5
Click ok
--Change the log file
C:\Program Files\Sun Role Manager\SRM-4.1\tomcat55\bin\tomcat5w.exe
logging tab
Log path: C:\Program Files\Sun Role Manager\SRM-4.1\tomcat55\logs
--Change the path to the new jvm.dll file
C:\Program Files\Sun Role Manager\SRM-4.1\tomcat55\bin\tomcat5w.exe
Java Tab -->
Java Virtual Machine: C:\Program Files\Sun Role Manager\SRM-4.1\jre1.5\bin\client\jvm.dll
Make sure the Java Classpath is correct
Start Apache
Daniel

Tomcat Solaris 9 distribution will not start

I downloaded SOLARIS 9 and installed it on my SUN BLADE 100. I looked for and found TOMCAT, a version came with the SOLARIS 9 operating environment. I tried to start TOMCAT, startup.sh, I could not get TOMCAT to start. Here is the output from catalina.out.
Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/catalina/startup/Bootstrap
Any help is certainly appreciated.
Michael
[email protected]

You have to add the tomcat/lib/Bootstrap.jar to your classpath.

CLI156 Could not start the domain domain1

I installed successfully the Appserver on desktop, but when I try to start it from laptop, comes the message below. Both are w2k and 512 memory.
Environment:
C:\>set
ALLUSERSPROFILE=C:\Documents and Settings\All Users
APPDATA=C:\Documents and Settings\Luis Araujo\Application Data
CommonProgramFiles=C:\Program Files\Common Files
COMPUTERNAME=LAQA
ComSpec=C:\WINNT\system32\cmd.exe
HOMEDRIVE=C:
HOMEPATH=\
J2EE_HOME=C:\\Sun\\AppServer
LOGONSERVER=\\LAQA
NUMBER_OF_PROCESSORS=1
OS=Windows_NT
Os2LibPath=C:\WINNT\system32\os2\dll;
Path=C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;C:\WINNT\system32\nls;C:\WINNT\system32\nls\ENGLISH;C:\Program Files\C
ommon Files\Autodesk Shared\;C:\Sun\AppServer\bin;C:\Sun\AppServer\jdk\bin;C:\Sun\AppServer\lib
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 6 Model 8 Stepping 10, GenuineIntel
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=080a
ProgramFiles=C:\Program Files
PROMPT=$P$G
SystemDrive=C:
SystemRoot=C:\WINNT
TEMP=C:\DOCUME~1\LUISAR~1\LOCALS~1\Temp
TMP=C:\DOCUME~1\LUISAR~1\LOCALS~1\Temp
USERDOMAIN=LAQA
USERNAME=db2admin
USERPROFILE=C:\Documents and Settings\Luis Araujo
windir=C:\WINNT
Prompt message:
Domain domain1 failed to startup. Please check the server log for more details.
CLI156 Could not start the domain domain1.
Press any key to continue . . .
Server.log:
Starting J2EE(TM) Application Server 1.4 Developer Release (build b44-dr) ...
[#|2004-01-03T06:36:00.436-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun Microsystems Inc.]|#]
[#|2004-01-03T06:36:04.612-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-01-03T06:36:05.283-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-01-03T06:36:07.587-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating Engine server|#]
[#|2004-01-03T06:36:08.037-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-01-03T06:36:08.057-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-01-03T06:36:08.087-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-01-03T06:36:14.306-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-01-03T06:36:30.510-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-01-03T06:36:32.042-0200|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-01-03T06:36:35.046-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-01-03T06:36:39.062-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-01-03T06:36:39.072-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-01-03T06:36:39.903-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Selecting file [C:\Sun\AppServer\lib\install\applications\MEjbApp.ear] for autodeployment|#]
[#|2004-01-03T06:36:40.023-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ C:\Sun\AppServer\lib\install\applications\MEjbApp.ear ] for autodeployment.|#]
[#|2004-01-03T06:36:44.860-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [MEjbApp]|#]
Remote message: Processing beans ....
[#|2004-01-03T06:36:45.121-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5108: EJBC - Generated code for remote home and EJBObject implementations for [MEjbApp]|#]
Remote message: Compiling wrapper code ....
Compilation failed: com.sun.ejb.codegen.ProcessExecutorException: Process timed out.
Timeout was 60,000 msecs
Attempted command: C:\Sun\AppServer\jdk\bin\javac.exe -extdirs C:\Sun\AppServer\jdk/jre/lib/ext;C:\Sun\AppServer\domains\domain1/lib/ext -g -d C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp -classpath C:\Sun\AppServer\lib\commons-launcher.jar;C:\Sun\AppServer\jdk\lib\tools.jar;C:\Sun\AppServer\lib\activation.jar;C:\Sun\AppServer\lib\admin-cli.jar;C:\Sun\AppServer\lib\appserv-admin.jar;C:\Sun\AppServer\lib\appserv-cmp.jar;C:\Sun\AppServer\lib\appserv-ext.jar;C:\Sun\AppServer\lib\appserv-jstl.jar;C:\Sun\AppServer\lib\appserv-rt.jar;C:\Sun\AppServer\lib\appserv-upgrade.jar;C:\Sun\AppServer\lib\commons-logging.jar;C:\Sun\AppServer\lib\j2ee-svc.jar;C:\Sun\AppServer\lib\j2ee.jar;C:\Sun\AppServer\lib\jax-qname.jar;C:\Sun\AppServer\lib\jaxr-api.jar;C:\Sun\AppServer\lib\jaxr-impl.jar;C:\Sun\AppServer\lib\jaxrpc-api.jar;C:\Sun\AppServer\lib\jaxrpc-impl.jar;C:\Sun\AppServer\lib\mail.jar;C:\Sun\AppServer\lib\relaxngDatatype.jar;C:\Sun\AppServer\lib\saaj-api.jar;C:\Sun\AppServer\lib\saaj-impl.jar;C:\Sun\AppServer\lib\xsdlib.jar;C:\Sun\AppServer\jdk/lib/tools.jar;C:\Sun\AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:\Sun\AppServer\imq\lib/imq.jar;C:\Sun\AppServer\imq\lib/jaxm-api.jar;C:\Sun\AppServer\imq\lib/imqadmin.jar;C:\Sun\AppServer\imq\lib/imqutil.jar;C:\Sun\AppServer\imq\lib/fscontext.jar;C:\Sun\AppServer\imq\lib/providerutil.jar;C:\Sun\AppServer/lib/ant/lib/ant.jar;C:\Sun\AppServer/pointbase/lib/pbclient.jar;C:\Sun\AppServer/pointbase/lib/pbembedded.jar;C:\Sun\AppServer/pointbase/lib/pbclient.jar;C:\Sun\AppServer/pointbase/lib/pbembedded.jar;C:\Sun\AppServer\domains\domain1\lib\classes;C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp;C:\Sun\AppServer\domains\domain1\applications\j2ee-apps\MEjbApp\mejb_jar;C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp;C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp @C:\Documents and Settings\Luis Araujo\Local Settings\Temp\681e45_f9dae089d50000_29515.s1a
Output from command:
     at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:361)
     at com.sun.ejb.codegen.IASEJBC.compileAndRmic(IASEJBC.java:210)
     at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:1144)
     at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:326)
     at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:196)
     at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:277)
     at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:163)
     at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:105)
     at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:128)
     at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:79)
     at com.sun.enterprise.deployment.phasing.DeploymentService.executePhases(DeploymentService.java:216)
     at com.sun.enterprise.deployment.phasing.DeploymentService.deploy(DeploymentService.java:152)
     at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:270)
     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.MBeanHelper.invokeOperationInBean(MBeanHelper.java:266)
     at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:268)
     at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:212)
     at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:218)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:808)
     at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:781)
     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.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
     at $Proxy1.invoke(Unknown Source)
     at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:468)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:364)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:343)
     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:282)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:217)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:171)
     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: com.sun.ejb.codegen.JavaCompilerException: com.sun.ejb.codegen.ProcessExecutorException: Process timed out.
Timeout was 60,000 msecs
Attempted command: C:\Sun\AppServer\jdk\bin\javac.exe -extdirs C:\Sun\AppServer\jdk/jre/lib/ext;C:\Sun\AppServer\domains\domain1/lib/ext -g -d C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp -classpath C:\Sun\AppServer\lib\commons-launcher.jar;C:\Sun\AppServer\jdk\lib\tools.jar;C:\Sun\AppServer\lib\activation.jar;C:\Sun\AppServer\lib\admin-cli.jar;C:\Sun\AppServer\lib\appserv-admin.jar;C:\Sun\AppServer\lib\appserv-cmp.jar;C:\Sun\AppServer\lib\appserv-ext.jar;C:\Sun\AppServer\lib\appserv-jstl.jar;C:\Sun\AppServer\lib\appserv-rt.jar;C:\Sun\AppServer\lib\appserv-upgrade.jar;C:\Sun\AppServer\lib\commons-logging.jar;C:\Sun\AppServer\lib\j2ee-svc.jar;C:\Sun\AppServer\lib\j2ee.jar;C:\Sun\AppServer\lib\jax-qname.jar;C:\Sun\AppServer\lib\jaxr-api.jar;C:\Sun\AppServer\lib\jaxr-impl.jar;C:\Sun\AppServer\lib\jaxrpc-api.jar;C:\Sun\AppServer\lib\jaxrpc-impl.jar;C:\Sun\AppServer\lib\mail.jar;C:\Sun\AppServer\lib\relaxngDatatype.jar;C:\Sun\AppServer\lib\saaj-api.jar;C:\Sun\AppServer\lib\saaj-impl.jar;C:\Sun\AppServer\lib\xsdlib.jar;C:\Sun\AppServer\jdk/lib/tools.jar;C:\Sun\AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:\Sun\AppServer\imq\lib/imq.jar;C:\Sun\AppServer\imq\lib/jaxm-api.jar;C:\Sun\AppServer\imq\lib/imqadmin.jar;C:\Sun\AppServer\imq\lib/imqutil.jar;C:\Sun\AppServer\imq\lib/fscontext.jar;C:\Sun\AppServer\imq\lib/providerutil.jar;C:\Sun\AppServer/lib/ant/lib/ant.jar;C:\Sun\AppServer/pointbase/lib/pbclient.jar;C:\Sun\AppServer/pointbase/lib/pbembedded.jar;C:\Sun\AppServer/pointbase/lib/pbclient.jar;C:\Sun\AppServer/pointbase/lib/pbembedded.jar;C:\Sun\AppServer\domains\domain1\lib\classes;C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp;C:\Sun\AppServer\domains\domain1\applications\j2ee-apps\MEjbApp\mejb_jar;C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp;C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp @C:\Documents and Settings\Luis Araujo\Local Settings\Temp\681e45_f9dae089d50000_29515.s1a
Output from command:
     at com.sun.ejb.codegen.Compiler.compile(Compiler.java:76)
     at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:353)
     ... 44 more
Caused by: com.sun.ejb.codegen.ProcessExecutorException: Process timed out.
Timeout was 60,000 msecs
Attempted command: C:\Sun\AppServer\jdk\bin\javac.exe -extdirs C:\Sun\AppServer\jdk/jre/lib/ext;C:\Sun\AppServer\domains\domain1/lib/ext -g -d C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp -classpath C:\Sun\AppServer\lib\commons-launcher.jar;C:\Sun\AppServer\jdk\lib\tools.jar;C:\Sun\AppServer\lib\activation.jar;C:\Sun\AppServer\lib\admin-cli.jar;C:\Sun\AppServer\lib\appserv-admin.jar;C:\Sun\AppServer\lib\appserv-cmp.jar;C:\Sun\AppServer\lib\appserv-ext.jar;C:\Sun\AppServer\lib\appserv-jstl.jar;C:\Sun\AppServer\lib\appserv-rt.jar;C:\Sun\AppServer\lib\appserv-upgrade.jar;C:\Sun\AppServer\lib\commons-logging.jar;C:\Sun\AppServer\lib\j2ee-svc.jar;C:\Sun\AppServer\lib\j2ee.jar;C:\Sun\AppServer\lib\jax-qname.jar;C:\Sun\AppServer\lib\jaxr-api.jar;C:\Sun\AppServer\lib\jaxr-impl.jar;C:\Sun\AppServer\lib\jaxrpc-api.jar;C:\Sun\AppServer\lib\jaxrpc-impl.jar;C:\Sun\AppServer\lib\mail.jar;C:\Sun\AppServer\lib\relaxngDatatype.jar;C:\Sun\AppServer\lib\saaj-api.jar;C:\Sun\AppServer\lib\saaj-impl.jar;C:\Sun\AppServer\lib\xsdlib.jar;C:\Sun\AppServer\jdk/lib/tools.jar;C:\Sun\AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:\Sun\AppServer\imq\lib/imq.jar;C:\Sun\AppServer\imq\lib/jaxm-api.jar;C:\Sun\AppServer\imq\lib/imqadmin.jar;C:\Sun\AppServer\imq\lib/imqutil.jar;C:\Sun\AppServer\imq\lib/fscontext.jar;C:\Sun\AppServer\imq\lib/providerutil.jar;C:\Sun\AppServer/lib/ant/lib/ant.jar;C:\Sun\AppServer/pointbase/lib/pbclient.jar;C:\Sun\AppServer/pointbase/lib/pbembedded.jar;C:\Sun\AppServer/pointbase/lib/pbclient.jar;C:\Sun\AppServer/pointbase/lib/pbembedded.jar;C:\Sun\AppServer\domains\domain1\lib\classes;C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp;C:\Sun\AppServer\domains\domain1\applications\j2ee-apps\MEjbApp\mejb_jar;C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp;C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp @C:\Documents and Settings\Luis Araujo\Local Settings\Temp\681e45_f9dae089d50000_29515.s1a
Output from command:
     at com.sun.ejb.codegen.ProcessRunner.makeTimeoutException(ProcessExecutor.java:348)
     at com.sun.ejb.codegen.ProcessExecutor.execute(ProcessExecutor.java:140)
     at com.sun.ejb.codegen.Compiler.runProcess(Compiler.java:165)
     at com.sun.ejb.codegen.JavaCompiler.javacCompile(JavaCompiler.java:128)
     at com.sun.ejb.codegen.JavaCompiler.internal_compile(JavaCompiler.java:65)
     at com.sun.ejb.codegen.Compiler.compile(Compiler.java:67)
     ... 45 more
[#|2004-01-03T06:37:46.269-0200|WARNING|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|Deployment Error
com.sun.enterprise.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- Compilation failed: com.sun.ejb.codegen.ProcessExecutorException: Process timed out.
Timeout was 60,000 msecs
Attempted command: C:\Sun\AppServer\jdk\bin\javac.exe -extdirs C:\Sun\AppServer\jdk/jre/lib/ext;C:\Sun\AppServer\domains\domain1/lib/ext -g -d C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp -classpath C:\Sun\AppServer\lib\commons-launcher.jar;C:\Sun\AppServer\jdk\lib\tools.jar;C:\Sun\AppServer\lib\activation.jar;C:\Sun\AppServer\lib\admin-cli.jar;C:\Sun\AppServer\lib\appserv-admin.jar;C:\Sun\AppServer\lib\appserv-cmp.jar;C:\Sun\AppServer\lib\appserv-ext.jar;C:\Sun\AppServer\lib\appserv-jstl.jar;C:\Sun\AppServer\lib\appserv-rt.jar;C:\Sun\AppServer\lib\appserv-upgrade.jar;C:\Sun\AppServer\lib\commons-logging.jar;C:\Sun\AppServer\lib\j2ee-svc.jar;C:\Sun\AppServer\lib\j2ee.jar;C:\Sun\AppServer\lib\jax-qname.jar;C:\Sun\AppServer\lib\jaxr-api.jar;C:\Sun\AppServer\lib\jaxr-impl.jar;C:\Sun\AppServer\lib\jaxrpc-api.jar;C:\Sun\AppServer\lib\jaxrpc-impl.jar;C:\Sun\AppServer\lib\mail.jar;C:\Sun\AppServer\lib\relaxngDatatype.jar;C:\Sun\AppServer\lib\saaj-api.jar;C:\Sun\AppServer\lib\saaj-impl.jar;C:\Sun\AppServer\lib\xsdlib.jar;C:\Sun\AppServer\jdk/lib/tools.jar;C:\Sun\AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:\Sun\AppServer\imq\lib/imq.jar;C:\Sun\AppServer\imq\lib/jaxm-api.jar;C:\Sun\AppServer\imq\lib/imqadmin.jar;C:\Sun\AppServer\imq\lib/imqutil.jar;C:\Sun\AppServer\imq\lib/fscontext.jar;C:\Sun\AppServer\imq\lib/providerutil.jar;C:\Sun\AppServer/lib/ant/lib/ant.jar;C:\Sun\AppServer/pointbase/lib/pbclient.jar;C:\Sun\AppServer/pointbase/lib/pbembedded.jar;C:\Sun\AppServer/pointbase/lib/pbclient.jar;C:\Sun\AppServer/pointbase/lib/pbembedded.jar;C:\Sun\AppServer\domains\domain1\lib\classes;C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp;C:\Sun\AppServer\domains\domain1\applications\j2ee-apps\MEjbApp\mejb_jar;C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp;C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp @C:\Documents and Settings\Luis Araujo\Local Settings\Temp\681e45_f9dae089d50000_29515.s1a
Output from command:
     at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:361)
     at com.sun.ejb.codegen.IASEJBC.compileAndRmic(IASEJBC.java:210)
     at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:1144)
     at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:326)
     at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:196)
     at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:277)
     at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:163)
     at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:105)
     at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:128)
     at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:79)
     at com.sun.enterprise.deployment.phasing.DeploymentService.executePhases(DeploymentService.java:216)
     at com.sun.enterprise.deployment.phasing.DeploymentService.deploy(DeploymentService.java:152)
     at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:270)
     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.MBeanHelper.invokeOperationInBean(MBeanHelper.java:266)
     at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:268)
     at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:212)
     at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:218)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:808)
     at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:781)
     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.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
     at $Proxy1.invoke(Unknown Source)
     at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:468)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:364)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:343)
     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:282)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:217)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:171)
     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)
|#]
[#|2004-01-03T06:37:46.269-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 65565 msec, Total EJB Compiler Module Time: 0 msec, Portion spent EJB Compiling: 0%|#]
[#|2004-01-03T06:37:46.309-0200|SEVERE|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|No local string defined|#]
[#|2004-01-03T06:37:46.319-0200|SEVERE|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|No local string defined
com.sun.enterprise.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- Compilation failed: com.sun.ejb.codegen.ProcessExecutorException: Process timed out.
Timeout was 60,000 msecs
Attempted command: C:\Sun\AppServer\jdk\bin\javac.exe -extdirs C:\Sun\AppServer\jdk/jre/lib/ext;C:\Sun\AppServer\domains\domain1/lib/ext -g -d C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp -classpath C:\Sun\AppServer\lib\commons-launcher.jar;C:\Sun\AppServer\jdk\lib\tools.jar;C:\Sun\AppServer\lib\activation.jar;C:\Sun\AppServer\lib\admin-cli.jar;C:\Sun\AppServer\lib\appserv-admin.jar;C:\Sun\AppServer\lib\appserv-cmp.jar;C:\Sun\AppServer\lib\appserv-ext.jar;C:\Sun\AppServer\lib\appserv-jstl.jar;C:\Sun\AppServer\lib\appserv-rt.jar;C:\Sun\AppServer\lib\appserv-upgrade.jar;C:\Sun\AppServer\lib\commons-logging.jar;C:\Sun\AppServer\lib\j2ee-svc.jar;C:\Sun\AppServer\lib\j2ee.jar;C:\Sun\AppServer\lib\jax-qname.jar;C:\Sun\AppServer\lib\jaxr-api.jar;C:\Sun\AppServer\lib\jaxr-impl.jar;C:\Sun\AppServer\lib\jaxrpc-api.jar;C:\Sun\AppServer\lib\jaxrpc-impl.jar;C:\Sun\AppServer\lib\mail.jar;C:\Sun\AppServer\lib\relaxngDatatype.jar;C:\Sun\AppServer\lib\saaj-api.jar;C:\Sun\AppServer\lib\saaj-impl.jar;C:\Sun\AppServer\lib\xsdlib.jar;C:\Sun\AppServer\jdk/lib/tools.jar;C:\Sun\AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:\Sun\AppServer\imq\lib/imq.jar;C:\Sun\AppServer\imq\lib/jaxm-api.jar;C:\Sun\AppServer\imq\lib/imqadmin.jar;C:\Sun\AppServer\imq\lib/imqutil.jar;C:\Sun\AppServer\imq\lib/fscontext.jar;C:\Sun\AppServer\imq\lib/providerutil.jar;C:\Sun\AppServer/lib/ant/lib/ant.jar;C:\Sun\AppServer/pointbase/lib/pbclient.jar;C:\Sun\AppServer/pointbase/lib/pbembedded.jar;C:\Sun\AppServer/pointbase/lib/pbclient.jar;C:\Sun\AppServer/pointbase/lib/pbembedded.jar;C:\Sun\AppServer\domains\domain1\lib\classes;C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp;C:\Sun\AppServer\domains\domain1\applications\j2ee-apps\MEjbApp\mejb_jar;C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp;C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp @C:\Documents and Settings\Luis Araujo\Local Settings\Temp\681e45_f9dae089d50000_29515.s1a
Output from command:
     at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:361)
     at com.sun.ejb.codegen.IASEJBC.compileAndRmic(IASEJBC.java:210)
     at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:1144)
     at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:326)
     at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:196)
     at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:277)
     at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:163)
     at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:105)
     at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:128)
     at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:79)
     at com.sun.enterprise.deployment.phasing.DeploymentService.executePhases(DeploymentService.java:216)
     at com.sun.enterprise.deployment.phasing.DeploymentService.deploy(DeploymentService.java:152)
     at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:270)
     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.MBeanHelper.invokeOperationInBean(MBeanHelper.java:266)
     at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:268)
     at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:212)
     at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:218)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:808)
     at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:781)
     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.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
     at $Proxy1.invoke(Unknown Source)
     at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:468)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:364)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:343)
     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:282)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:217)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:171)
     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)
|#]
[#|2004-01-03T06:37:46.329-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Autodeploy failed : C:\Sun\AppServer\lib\install\applications\MEjbApp.ear.|#]
[#|2004-01-03T06:38:03.483-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-01-03T06:38:04.955-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-01-03T06:38:06.988-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-01-03T06:38:07.038-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-01-03T06:38:07.119-0200|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-01-03T06:38:07.119-0200|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-01-03T06:38:07.409-0200|INFO|j2ee-appserver1.4|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: J2EETM 1.4 Application Server|#]
[#|2004-01-03T06:38:53.896-0200|INFO|j2ee-appserver1.4|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-01-03T06:38:56.249-0200|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-01-03T06:38:56.359-0200|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-01-03T06:38:56.980-0200|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-01-03T06:38:56.990-0200|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-01-03T06:38:57.080-0200|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-01-03T06:38:57.100-0200|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-01-03T06:40:59.587-0200|INFO|j2ee-appserver1.4|javax.enterprise.resource.jms|_ThreadID=10;|JMS5035: Timed out after 120000 milli

Which J2SE version are you using - is that version corrupted - looks like some of the JAXP classes are not found

The Sun Java Application Server 8.1 could not start anymore

Very incredible I was working fine from may days with Stydio Creator 2
but yesterday I run the project and it does not work anymore, please can you suggest something:
The Sun Java Application Server 8.1 could not start.
from the Output console:
C:\Sun\Creator2\SunAppServer8\bin\asadmin.bat start-domain --domaindir C:\Sun\Creator2\SunAppServer8\domains\ creator
Failed to start server localhost:4848
Deployment error: Failed to start server localhost:4848. See the server log file for details.
Exception=Deployment error: Failed to start server localhost:4848. See the server log file for details.
Deployment error: Failed to start server localhost:4848. See the server log file for details.
at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:198)
at org.netbeans.modules.j2ee.ant.Deploy.execute(Deploy.java:75)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
at org.apache.tools.ant.Project.executeTargets(Project.java:1062)
at org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:234)
at org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:242)
at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:125)
Caused by: Failed to start server localhost:4848
at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:152)
... 10 more
and in the log file:
[#|2006-02-24T11:49:51.296+0100|WARNING|sun-appserver-pe8.1_02|
javax.enterprise.system.core|_ThreadID=25;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException: [C4073]: A JMS destination limit was reached.
Too many Subscribers/Receivers for Queue :
temporary_destination://queue/192.168.0.159/3376/2 user=admin, broker=127.0.0.1:27676(2403)
     at com.sun.enterprise.jms.JmsProviderLifecycle.onTermination(JmsProviderLifecycle.java:476)
     at com.sun.enterprise.server.ApplicationServer.onTermination(ApplicationServer.java:454)
     at com.sun.enterprise.server.Shutdown.startShutdown(Shutdown.java:42)
     at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeShutdownEventListener(AdminEventMulticaster.java:1445)
     at com.sun.enterprise.admin.event.AdminEventMulticaster.handleShutdownEvent(AdminEventMulticaster.java:1434)
     at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:443)
     at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:139)
     at com.sun.enterprise.admin.server.core.channel.AdminChannelServer.sendNotification(AdminChannelServer.java:90)
     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:585)
     at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
     at sun.rmi.transport.Transport$1.run(Transport.java:153)
     at java.security.AccessController.doPrivileged(Native Method)
     at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
     at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
     at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
     at java.lang.Thread.run(Thread.java:595)
thanks

I just had the same problem this morning. I believe the app server starts and if you browser directly to your app you'd get it, but the connection between the appserver and the IDE is somehow lost. An easier solution than completely reinstalling for me was to delete the .Creator folder in my home directory (C;|Documents and Setting\<username>\.Creator) and restart Creator

Sun Java System Application Server could not start

Hi
I have installed JDK1.5 Update1 + netbeans 5.5 with the JBOSS bundle and added the Sun Java System Application Server 9.1.02.
I am creating the EJB-JMS application described at
http://www.netbeans.org/kb/55/ejb30.html
All the steps are followed properly, but while running the project i get the error
The Sun Java System Application Server could not start.
More information about the cause is in the Server log file.
Possible reasons include:
- IDE timeout: refresh the server node to see if it's running now.
- 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 Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
- Invalid installation location.
D:\MyNBProjects\EJBAPP1\nbproject\build-impl.xml:183: Deployment error:
The Sun Java System Application Server could not start.
More information about the cause is in the Server log file.
Possible reasons include:
- IDE timeout: refresh the server node to see if it's running now.
- 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 Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
- Invalid installation location.
See the server log for details.
BUILD FAILED (total time: 5 minutes 3 seconds)

Hi Roman,
Sorry for the long wait....
In the mean time I have downloaded NB6.1 (final Release) and JDK 1.6.0_04,added the sjsas-9_1_02 to NB6.1, all are in D:\javak (where previous setup of NB5.5 and jdk1.5 and SJSAS-9_1_02 is AS IS in D:\java)
Current Scenario:
Product Version: NetBeans IDE 6.1 (Build 200805300101)
Java: 1.6.0_04; Java HotSpot(TM) Client VM 10.0-b19
System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb)
Userdir: D:\Documents and Settings\kedar\.netbeans\6.1
Now, when i try to Run the SAME code i get the following error:
Created dir: D:\ProjectsNB\EJBAPP1\dist
Building jar: D:\ProjectsNB\EJBAPP1\dist\EJBAPP1.ear
post-dist:
dist:
pre-run-deploy:
Initial deploying EJBAPP1 to D:\ProjectsNB\EJBAPP1\dist\gfdeploy
Error during incremental deploy: java.lang.NullPointerException
Start registering the project's server resources
Finished registering server resources
java.lang.NullPointerException
at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeploymentFacility.getFileArchive(DirectoryDeploymentFacility.java:264)
at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeploymentFacility.initialDeploy(DirectoryDeploymentFacility.java:168)
at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeployment.initialDeploy(DirectoryDeployment.java:413)
at org.netbeans.modules.j2ee.sun.ide.j2ee.incrdeploy.DirectoryDeploymentFacade.initialDeploy(DirectoryDeploymentFacade.java:218)
at org.netbeans.modules.j2ee.deployment.impl.TargetServer.deploy(TargetServer.java:519)
at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:151)
at org.netbeans.modules.j2ee.ant.Deploy.execute(Deploy.java:104)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor112.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
at org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:277)
at org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:460)
at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:151)
java.lang.IllegalStateException: cannot find FileArchive class...
at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeploymentFacility.initialDeploy(DirectoryDeploymentFacility.java:170)
at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeployment.initialDeploy(DirectoryDeployment.java:413)
at org.netbeans.modules.j2ee.sun.ide.j2ee.incrdeploy.DirectoryDeploymentFacade.initialDeploy(DirectoryDeploymentFacade.java:218)
at org.netbeans.modules.j2ee.deployment.impl.TargetServer.deploy(TargetServer.java:519)
at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:151)
at org.netbeans.modules.j2ee.ant.Deploy.execute(Deploy.java:104)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor112.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
at org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:277)
at org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:460)
at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:151)
Deployment error:
cannot find FileArchive class...
See the server log for details.
at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:166)
at org.netbeans.modules.j2ee.ant.Deploy.execute(Deploy.java:104)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor112.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
at org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:277)
at org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:460)
at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:151)
Caused by: java.lang.IllegalStateException: cannot find FileArchive class...
at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeploymentFacility.initialDeploy(DirectoryDeploymentFacility.java:194)
at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeployment.initialDeploy(DirectoryDeployment.java:413)
at org.netbeans.modules.j2ee.sun.ide.j2ee.incrdeploy.DirectoryDeploymentFacade.initialDeploy(DirectoryDeploymentFacade.java:218)
at org.netbeans.modules.j2ee.deployment.impl.TargetServer.deploy(TargetServer.java:519)
at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:151)
... 16 more
Caused by: java.lang.IllegalStateException: cannot find FileArchive class...
at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeploymentFacility.initialDeploy(DirectoryDeploymentFacility.java:170)
... 20 more
BUILD FAILED (total time: 9 seconds)
Thanks,
Kedar.

*** WARNING: Could not start service 80 for protocol HTTP on host MyFQDN

Hi,
I m configuring an external Sap webdispatcher to point to an ICF service
I need to install it on Windows Web server where others web sites are running.
I configured a specific ip for that on the Web servers and enter the DNS name in our domain.
On the the pfl file I define :
SAPLOCALHOSTFULL=<MyFQDN>
icm/host_name_full =<MyFQDN>
and specify icm/server_port_0 = PROT=HTTP,PORT=80
Each time I m starting it I received *** WARNING: Could not start service 80 for protocol HTTP on host <MyFQDN> .........
If I m using another port (Ex:86)no problem with my FQDN.But if I m doing servername:86 it s working also.
It s seems that the webdispatcher don t care about my FQDN.
How can I have the WEBDISPATCHER pointing to this specific FQDN and not all ?
Thanks,

Hi Damien,
You problem is perfectly logical : It's not possible to have 2 programs (IIS and web dispatcher) listening together on the same 80 HTTP port.
There is no configuration that I know on the web dispatcher to tell him to listen only on one IP address.
Summary : what you want to do is not possible.
I had a similar request and I did the following.
I use a Linux box with an Apache reverse proxy to select to distribute the HTTP requests on different web dispatchers. The rules depends from the called URLs.
Regards,
Olivier

Could not start Sun Java Application Server

Hi ,
I have been using JSC for a while, now and then it reports an error " could not start sun java application server...". Does any one know why it s not able to start java application server..
Before you say anything, I have tried
1. use netstat to find any port conflicts.
2. Tried to start application server manually
3. shut down and start studio creator and then try running the project
4. shut down and start PC
unfortunately none of them helped
Only reinstalling resolved the problem. But I cant keep reinstalling very often.
Does any one know the permanent solution for this problem.
Cheers
kush

Sometimes it appears this is a timeout issue because it's taking too long to come up. As Jonathan says, undeploy can help with this (along with his other suggestions).
How many deployed projects do you see (in the server navigator you can open up the deployed server and see what's out there)?
I periodically undeploy "junk" projects that I'm not really using because they slow down the server startup (same thing happens I believe for tomcat... when the server starts it has to load them all and it takes awhile). You can undeploy from within the server navigator by drilling into the server nav and right clicking on the deployed app and choosing undeploy... or you can use the server admin tool.
hth,
v

CLI156 Could not start the domain domain1. in Application Server 8

Hi everybody!
Sorry to post this message here at Application Server 7. But I'm using the Application Server 8 along with NetBeans 4.1 early access. Suddenly, the application server stop working on my computer and now, every time I try to start the default server, I get this error message:
CLI156 Could not start the domain domain1.
With the following log:
Starting Sun Java System Application Server Platform Edition 8.0.0_01 (build b08-fcs) ...
[#|2004-12-28T22:46:39.359+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_06] from [Sun Microsystems Inc.]|#]
[#|2004-12-28T22:46:42.296+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-12-28T22:46:42.625+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-12-28T22:46:46.921+0000|ADVERTENCIA|sun-appserver-pe8.0.0_01|javax.enterprise.system.stream.err|_ThreadID=10;|log4j:WARN No appenders could be found for logger (org.apache.catalina.startup.Embedded).|#]
[#|2004-12-28T22:46:46.921+0000|ADVERTENCIA|sun-appserver-pe8.0.0_01|javax.enterprise.system.stream.err|_ThreadID=10;|
log4j:WARN Please initialize the log4j system properly.|#]
[#|2004-12-28T22:46:47.687+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-12-28T22:46:47.718+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-12-28T22:46:47.750+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-12-28T22:46:53.718+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-12-28T22:46:56.984+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-12-28T22:46:57.984+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-12-28T22:46:59.328+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-12-28T22:47:00.468+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-12-28T22:47:00.640+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Selecting file [C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear] for autodeployment|#]
[#|2004-12-28T22:47:00.640+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear ] for autodeployment.|#]
[#|2004-12-28T22:47:02.390+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [__ejb_container_timer_app]|#]
[#|2004-12-28T22:47:04.640+0000|ADVERTENCIA|sun-appserver-pe8.0.0_01|javax.enterprise.system.stream.err|_ThreadID=10;|
CharScanner; panic: ClassNotFoundException: com.sun.jdo.spi.persistence.support.ejb.ejbqlc.EJBQLLexer$EJBQLToken|#]
I'm running this application server on Windows XP, like I said, I was working with NetBeans and suddenly, the AS stop working.. I did not delete anything, I did not move anything either.
Please, does any of you have any ideas of how can I fix this issue?
Best regards!

You may try this soultion. I fixed this in my Window 2000 machine(Application Server 8) by:
1. Edit domain.xml($DEFAULT_DOAMIN/config)
2. Update the port="4702" for http-listener tag, and change to something else(e.g. 4802).
3. Save it
4. Make sure the Application Server is shut down.
5. Start the Application Server.
Hope it helps!
Ming-wei

Error: Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]

I'm using Oracle Linux 6u6. While I'm installing openstack ( 2 node set up) using packstack, I'm getting this error:
Applying 10.245.33.37_cinder.pp
10.245.33.37_keystone.pp:                         [ ERROR ]
Applying Puppet manifests                         [ ERROR ]
ERROR : Error appeared during Puppet run: 10.245.33.37_keystone.pp
Error: Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]
You will find full trace in log /var/tmp/packstack/20150327-100335-ltC8Ic/manifests/10.245.33.37_keystone.pp.log
Please check log file /var/tmp/packstack/20150327-100335-ltC8Ic/openstack-setup.log for more information
Additional information:
* A new answerfile was created in: /root/packstack-answers-20150327-100336.txt
* Time synchronization installation was skipped. Please note that unsynchronized time on server instances might be problem for some OpenStack components.
* Did not create a cinder volume group, one already existed
* File /root/keystonerc_admin has been created on OpenStack client host 10.245.33.37. To use the command line tools you need to source the file.
* To access the OpenStack Dashboard browse to http://10.245.33.37/dashboard .
Please, find your login credentials stored in the keystonerc_admin in your home directory.
Packages:
[root@slcai461 ~]# rpm -qa|grep keystone
python-keystoneclient-0.9.0-5.el6.noarch
python-keystone-2014.1.3-2.el6.noarch
openstack-keystone-2014.1.3-2.el6.noarch
[root@slcai461 ~]# rpm -qa|grep packstack
openstack-packstack-puppet-2014.1.1-0.12.dev1068.0.4.el6.noarch
openstack-packstack-2014.1.1-0.12.dev1068.0.4.el6.noarch
Log :
[root@slcai461 ~]# cat /var/tmp/packstack/20150327-100335-ltC8Ic/manifests/10.245.33.37_keystone.pp.log
Warning: Config file /etc/puppet/hiera.yaml not found, using Hiera defaults
Warning: Scope(Class[Keystone]): The sql_connection parameter is deprecated, use database_connection instead.
Warning: Scope(Class[Keystone]): token_format parameter is deprecated. Use token_provider instead.
Warning: Scope(Class[Keystone::Endpoint]): The public_address parameter is deprecated, use public_url instead.
Warning: Scope(Class[Keystone::Endpoint]): The internal_address parameter is deprecated, use internal_url instead.
Warning: Scope(Class[Keystone::Endpoint]): The admin_address parameter is deprecated, use admin_url instead.
Warning: Scope(Class[Nova::Keystone::Auth]): The cinder parameter is deprecated and has no effect.
Notice: Compiled catalog for slcai461.us.oracle.com in environment production in 1.60 seconds
Warning: The package type's allow_virtual parameter will be changing its default value from false to true in a future release. If you do not want to allow virtual packages, please explicitly set allow_virtual to false.
   (at /usr/lib/ruby/site_ruby/1.8/puppet/type.rb:816:in `set_default')
Notice: /Stage[main]/Keystone/Keystone_config[DEFAULT/admin_token]/value: value changed '[old secret redacted]' to '[new secret redacted]'
Notice: /Stage[main]/Keystone/Keystone_config[database/connection]/value: value changed '[old secret redacted]' to '[new secret redacted]'
Notice: /Stage[main]/Keystone::Db::Sync/Exec[keystone-manage db_sync]: Triggered 'refresh' from 3 events
Notice: /Stage[main]/Keystone/Exec[keystone-manage pki_setup]: Triggered 'refresh' from 2 events
Error: Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]
Wrapped exception:
Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]
Error: /Stage[main]/Keystone::Service/Service[keystone]/ensure: change from stopped to running failed: Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]
Notice: /Stage[main]/Keystone::Service/Service[keystone]: Triggered 'refresh' from 5 events
Notice: /Stage[main]/Neutron::Keystone::Auth/Keystone_service[neutron]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Neutron::Keystone::Auth/Keystone_service[neutron]: Skipping because of failed dependencies
Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[admin]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[admin]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova_ec2]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova_ec2]: Skipping because of failed dependencies
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_service[cinderv2]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_service[cinderv2]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_service[novav3]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_service[novav3]: Skipping because of failed dependencies
Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[services]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[services]: Skipping because of failed dependencies
Notice: /Stage[main]/Neutron::Keystone::Auth/Keystone_user[neutron]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Neutron::Keystone::Auth/Keystone_user[neutron]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_user[nova]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_user[nova]: Skipping because of failed dependencies
Notice: /Stage[main]/Glance::Keystone::Auth/Keystone_user[glance]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Glance::Keystone::Auth/Keystone_user[glance]: Skipping because of failed dependencies
Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_role[admin]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_role[admin]: Skipping because of failed dependencies
Notice: /Stage[main]/Glance::Keystone::Auth/Keystone_user_role[glance@services]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Glance::Keystone::Auth/Keystone_user_role[glance@services]: Skipping because of failed dependencies
Notice: /Stage[main]/Keystone::Endpoint/Keystone_service[keystone]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Endpoint/Keystone_service[keystone]: Skipping because of failed dependencies
Error: Could not prefetch keystone_endpoint provider 'keystone': Execution of '/usr/bin/keystone --os-endpoint http://127.0.0.1:35357/v2.0/ endpoint-list' returned 1: An unexpected error prevented the server from fulfilling your request. (HTTP 500)
Notice: /Stage[main]/Keystone::Endpoint/Keystone_endpoint[RegionOne/keystone]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Endpoint/Keystone_endpoint[RegionOne/keystone]: Skipping because of failed dependencies
Notice: /Stage[main]/Main/Keystone_service[cinder_v2]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Main/Keystone_service[cinder_v2]: Skipping because of failed dependencies
Notice: /Stage[main]/Main/Keystone_endpoint[RegionOne/cinder_v2]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Main/Keystone_endpoint[RegionOne/cinder_v2]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/novav3]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/novav3]: Skipping because of failed dependencies
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_service[cinder]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_service[cinder]: Skipping because of failed dependencies
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_endpoint[RegionOne/cinder]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_endpoint[RegionOne/cinder]: Skipping because of failed dependencies
Notice: /Stage[main]/Glance::Keystone::Auth/Keystone_service[glance]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Glance::Keystone::Auth/Keystone_service[glance]: Skipping because of failed dependencies
Notice: /Stage[main]/Glance::Keystone::Auth/Keystone_endpoint[RegionOne/glance]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Glance::Keystone::Auth/Keystone_endpoint[RegionOne/glance]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_user_role[nova@services]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_user_role[nova@services]: Skipping because of failed dependencies
Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_user[admin]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_user[admin]: Skipping because of failed dependencies
Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_user_role[admin@admin]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_user_role[admin@admin]: Skipping because of failed dependencies
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_user[cinder]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_user[cinder]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova_ec2]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova_ec2]: Skipping because of failed dependencies
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_endpoint[RegionOne/cinderv2]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_endpoint[RegionOne/cinderv2]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova]: Skipping because of failed dependencies
Notice: /Stage[main]/Neutron::Keystone::Auth/Keystone_user_role[neutron@services]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Neutron::Keystone::Auth/Keystone_user_role[neutron@services]: Skipping because of failed dependencies
Notice: /Stage[main]/Neutron::Keystone::Auth/Keystone_endpoint[RegionOne/neutron]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Neutron::Keystone::Auth/Keystone_endpoint[RegionOne/neutron]: Skipping because of failed dependencies
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_user_role[cinder@services]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_user_role[cinder@services]: Skipping because of failed dependencies
Notice: Finished catalog run in 3.10 seconds
Please let me know how to fix this.

This problem connected with proxy-setings.
As the first steps you should try:
       1. export system env variable:
http_proxy=http://www-proxy.ru.oracle.com:80
https_proxy=https://www-proxy.ru.oracle.com:80
no_proxy=127.0.0.1,localhost
and you can also export
    export OS_TENANT_NAME=admin
    export OS_USERNAME=admin
    export OS_PASSWORD=root
    export OS_AUTH_URL=http://<conntroller_IP>:5000/v2.0/
2. and than restart mysqld, if it is running, stop iptables and repeat installation process from beginning with the currently generated answer file
if we are exporting variable OS_PASSWORD, its value should be the same as value for CONFIG_KEYSTONE_ADMIN_PW in the currently generated answer file.
This OS_PASSWORD will be written by packstack in the /root/keystonerc_admin file and will be used as admin's password for login to Openstack dashboard.

SDM Deployment Failed--SDM could not start the J2EE cluster on the DB Host

HI,
I am trying to deploy ESS packges in EP through SDM.But while deploying I am getting this error in SDM at the start itself:-
Error: An error occured while starting a cluster instance.
Oct 14, 2008 5:14:41 PM Error: There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage
Please check if there is an appropriate running cluster instances
SDM could not start the J2EE cluster on the host SBPEPDB1! The online deployment is terminated.
There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage
I am pasting the full LOG File details:-
Oct 14, 2008 6:32:00 PM Info: Starting cluster instance processes.
Oct 14, 2008 6:32:00 PM Error: An error occured while starting a cluster instance.
Oct 14, 2008 6:32:00 PM Error: There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage . The instances, returned by MessageServer [MS host: SBPEPCI1; MS port: 3900], are :
Name:JM_T1223989073901_0_CPCAPP109
Host:SBPEPCI1
State:5
HostAddress:172.17.131.38
Name:JC_CPCAPP109_EPP_01
Host:CPCAPP109
State:5
HostAddress:172.17.131.31
Please check if there is an appropriate running cluster instances.
Oct 14, 2008 6:32:00 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 14, 2008 6:32:00 PM Error: Aborted: development component 'pcui_gp/isr/cfg'/'sap.com'/'MAIN_ERP05VAL_C'/'2515722'/'0', grouped by software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0':
SDM could not start the J2EE cluster on the host SBPEPDB1! The online deployment is terminated.
There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage .
The instances, returned by MessageServer [MS host: SBPEPCI1; MS port: 3900], are :
Name:JM_T1223989073901_0_CPCAPP109
Host:SBPEPCI1
State:5
HostAddress:172.17.131.38
Name:JC_CPCAPP109_EPP_01
Host:CPCAPP109
State:5
HostAddress:172.17.131.31
Please check if there is an appropriate running cluster instances.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Oct 14, 2008 6:32:04 PM Info: Starting to save the repository
Oct 14, 2008 6:32:05 PM Info: Finished saving the repository
Oct 14, 2008 6:32:07 PM Info: Starting: Initial deployment: Selected software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0' will be deployed.
Oct 14, 2008 6:32:07 PM Error: Aborted: software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0':
Failed deployment of SDAs:
development component 'pcui_gp/isr/cfg'/'sap.com'/'MAIN_ERP05VAL_C'/'2515722'/'0' : aborted
Please, look at error logs above for more information!
I have checked the CONFIGTOOl and the properties seem to be OK.
I tried SHUTTING DOWN all APPLICATION servers & Restarting the DEPLOYMENT,but it still Failed
Pls suggest.
Regards,
Abhijeet
I

Hi George,
Thnx for your reply.
I have stopped all Application servers and kept only the CI-DB instances running.Retried deploying the ESS packages but still getting the same error.
Have checked the Visual admin,it is not in SAFE mode,it working normally.
Have alos checked the CLUSTER Manager Property Values in both Visual Admin & Config Tool,they are alright.
About the Cluster Resources,can you pls specify what exactly do you mean by "Cluster Resources are running or not".
I think if the application servers are stopped,then the Cluster resources shudnt come into play right?? Correct me if I am wrong.
Kindly suggest what other steps I shud take.
Regards,
Abhijeet

Could not start transport control program tp while releasing the TR

Hello experts,
i have a problem if any one phase this kind of problem & if u know the solution please share to me its urgent
problem in Development system ,for this i had updated kernel , TP patch level , R3trans patch level in development and quality system , but still the problem is occurring in development system . while releasing the Transport Request this error is coming that too not in frequently some times it is happening some times it not happening ( some times its working fine )
Could not start transport control program tp
Message no. TP608 Diagnosis
There was an attempt to start the transport control program tp using the local RFC interface. An
error occurred here.
Error code: 4
RFC error text: timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'
Meaning of the error codes:
03 RFC system failure
04 RFC communication failure
System Response
The function terminates. Details about the error can be found in the trace file of the Gateway
Monitor (SMGW).
Procedure
Contact your system administrator or use report RSTPTEST to localize the error. You can then
execute the command again.
please suggest me what can i do for better , how can i resolve this issue
Thanks & Regards,
Narasimha

Hello experts ,
Last one and half month on-words we are phasing some problems on STMS
while releasing the Transport Request getting this error messages on
status-bar
1. "could not start transport control program tp"
2. while importing the TR into quality system getting this error message" RFC Error :timeout during allocate/CPIC-CALL "
3.while forwarding the TR from QAS to PRD : " RFC Error :timeout during
allocate/CPIC-CALL "
after continues refreshing,we are able to release the request and importthe request into quality system. But after some time again same problem
coming
for this we did the kernel upgrade , tp , & R3trans update and STMS RE-
Configuration etc...But no use with this we got the same problem after
finishing all these workaround , but don't know what happened after 2-3
days STMS starts working fine DEV-QAS-PRD ,
Now we are in the same problem after continues refreshing,we are able torelease the request and import the request into quality system. But after
some time again same problem coming
please suggest us what could be the reason behind this & what we can do
for better

Windows could not start the FLEXnet Licensing Service service on Local Computer Error 1068: The dependency service or group failed to start.

Today I installed Adobe Director 11.5. I received a couple of errors in the FLEXnet Licensing Service. It looks It could not start. I tried to download the Licence fix what I found on Google but that doesn't work, so I checked the 'Service' at service (windows).
It's status is empty. When I double click on the FLEXnet Licensing Service, clicked on start at the opened window and an error is coming:
Windows could not start the FLEXnet Licensing Service service on Local Computer
Error 1068: The dependency service or group failed to start.
I don't understand what it says with this message, only that it is impossible to start. However, that is not what I am trying of course, I want to start the FLEXnet Licensing Service, service.
Re-installing of the software, doesn't make any change. How can I start it so Director is also working?

Hi Don1233,
Please consider seek help at the software vendor side.
For the services didn't start, follow the suggestions posted by Elton in the thread below:
https://social.technet.microsoft.com/Forums/en-US/e35da253-f0df-41d1-8df2-b73fa54742a0/windows-could-not-start-the-flexnet-licensing-service-service-on-local-computer-error-1068-the?forum=w7itproinstall
Best regards
Michael Shao
TechNet Community Support

1)Could not start up os x 2)Only could start bootcamp 3)Tried resetting nvram 4)Could not start even in bootcamp 5)Verify disk says -. Verifying volume "Macintosh HD" Error: Live file system repair is not supported 6)Installed maverick on USB d

1) Could not start up os x
2) Only could start bootcamp
3) Tried resetting nvram
4) Could not start even in bootcamp
5) Verify disk says …. Verifying volume “Macintosh HD”
Error: Live file system repair is not supported
6) Installed maverick on USB drive
7) Boot from USB drive. Tried verifying HD: Volume header needs minor repair. The volume Recovery HD was found corrupt and needs to be repaired. Verifying volume “Macintosh HD”: Error: live file system repair is not supported.
8) The terminal code says
9) Last login: Wed Feb 11 14:09:47 on console
10) xxxx-MacBook:~ xxxx$ diskutil list
11) /dev/disk0
12) #: TYPE NAME SIZE       IDENTIFIER
13) 0:      GUID_partition_scheme *160.0 GB   disk0
14) 1: EFI EFI 209.7 MB   disk0s1
15) 2:                  Apple_HFS Macintosh HD            80.1 GB disk0s2
16) 3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
17) 4:       Microsoft Basic Data 50.0 GB    disk0s4
18) /dev/disk1
19) #: TYPE NAME SIZE       IDENTIFIER
20) 0:      GUID_partition_scheme *15.6 GB    disk1
21) 1: EFI EFI 209.7 MB   disk1s1
22) 2:                  Apple_HFS BOOT                    14.8 GB    disk1s2
23) 3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3
24) Saeedehs-MacBook:~ saeedehmirbagheri$ diskutil cs list
25) No CoreStorage logical volume groups found
26) Saeedehs-MacBook:~ saeedehmirbagheri$ sudo gpt -vv -r show /dev/disk0
27) Password:
28) gpt show: /dev/disk0: mediasize=160041885696; sectorsize=512; blocks=312581808
29) gpt show: /dev/disk0: PMBR at sector 0
30) gpt show: /dev/disk0: Pri GPT at sector 1
31) gpt show: /dev/disk0: Sec GPT at sector 312581807
32) start       size index contents
33) 0          1 PMBR
34) 1          1 Pri GPT header
35) 2         32 Pri GPT table
36) 34          6
37) 40     409600      1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
38) 409640 156394528      2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
39) 156804168    1269544      3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
40) 158073712   56853648
41) 214927360   97652736      4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
42) 312580096       1679
43) 312581775         32         Sec GPT table
44) 312581807          1         Sec GPT header
45) xxxx-MacBook:~ xxxx$ sudo fdisk /dev/disk0
46) Disk: /dev/disk0 geometry: 19457/255/63 [312581808 sectors]
47) Signature: 0xAA55
48) Starting       Ending
49) #: id cyl hd sec - cyl hd sec [     start - size]
50) ------------------------------------------------------------------------

Thank you -
I booted from external USB. The diskutil list output is from OS x booting from the USB, which shows the following:
Saeedehs-MacBook:~ saeedehmirbagheri$ diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *160.0 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS Macintosh HD            80.1 GB    disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
   4:       Microsoft Basic Data                         50.0 GB    disk0s4
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *15.6 GB    disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                  Apple_HFS BOOT                    14.8 GB    disk1s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3
Saeedehs-MacBook:~ saeedehmirbagheri$ diskutil cs list
No CoreStorage logical volume groups found
I am not able to use target disk mode because I don't have firewire/thunderbolt ports.

Apache Tomcat 5.5.20 could not start

Similar Messages

Maybe you are looking for