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.

Similar Messages

Windows 2003 Server Guest - Could not start guest after conversion

Hi,
i am trying to start a converted VM (Windows Server 2003) from VMWARE. The conversion with the VM Manager finished successful. But when i want to start the VM, i get the following error;
failed:<Exception: return=>failed:<Exception: xm create '/OVS/running_pool/94_XXX/vm.cfg'=>Error: Device 768 (vbd) could not be connected. /etc/xen/scripts/block failed; error detected. > StackTrace: File "/opt/ovs-agent-2.2/OVSXXenVM.py", line 57, in xen_start_vm run_cmd(cmd) File "/opt/ovs-agent-2.2/OVSCommons.py", line 87, in run_cmd raise Exception('%s=>%s' % (cmd, p.childerr.read())) > StackTrace: File "/opt/ovs-agent-2.2/OVSSiteVM.py", line 84, in start_vm raise e
I searched now for days with google but i found nothing about "xm create '/OVS/running_pool/94_XXX/vm.cfg'=>Error: Device 768 (vbd) could not be connected. /etc/xen/scripts/block failed; error detected." What is the device 768 (vbd)?
I'm at a loss with this, can anyone help me?
Best Regards

Hi,
of course. there is the content of the vm.cfg file.
acpi = 1
apic = 1
builder = 'hvm'
device_model = '/usr/lib/xen/bin/qemu-dm'
disk = ['file:/OVS/running_pool/94_XXX/XXX.img,hda,w',
',hdc:cdrom,r',
kernel = '/usr/lib/xen/boot/hvmloader'
memory = '1024'
name = '94_XXX'
on_crash = 'restart'
on_reboot = 'restart'
pae = 1
serial = 'pty'
timer_mode = '1'
uuid = 'f1e0d63f-a602-9018-4cf7-3b7515441c9d'
vcpus = 1
vif = ['bridge=xenbr3,mac=00:16:3E:18:90:74,type=ioemu']
vif_other_config = []
vnc = 1
vncconsole = 1
vnclisten = '0.0.0.0'
vncpasswd = 'oracle'
vncunused = 1
I hope it helps. The other systems based on Linux started without problems after conversion.

Sun Java System Portal Server 7 is not starting!!!

Hi All,
I have successfully installed Sun Java System Portal Server 7 on RHEL 4.The problem is that after installation when I tried to access the portal throught its url it give the message "Connection to the host refused".
If anyone has got idea about this problem then please let me know.All suggestions are welcome and thanx in advance.
Chirag.

After a successful install the Directory, AM servers are down. You will have to start them after the install.
Stop start the process below in the order:
Stop/Start Directory Server instance:
Stop/Start Webcontainer instance running AM Server and Portal Server
Restart Cacao /opt/SUNWcacao/bin/cacaoadm restart
If the above does not fix it, take a look at the /var/opt/SUNWportal/portals/portal1/logs/<portal-instance>/*.logs
and the webcontainer logs for more details

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.

The Sun Java System Application Server could not start

Hello All,
I downloaded the Java Pet Store example from sun's website and followed the instructions for installation. After successful installation, I tried to deploy the project and gave the following error
C:\Documents and Settings\sina\My Documents\Projects\services\nbproject\build-impl.xml:194: 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 20 seconds)
The link above points to the following line in the build-impl.xml file
<nbdeploy debugmode="false" forceRedeploy="${forceRedeploy}" clientUrlPart="${client.urlPart}" clientModuleUri="${client.module.uri}"/>
Can any one help whats wrong.An early response will be highly appreciated.
Kind Regards.
Hasnain Javed.

Hi,
Maybe you already got this fix but here is a suggestion, a snippet from the readme index,html of the petstore download
# Start the Sun Java System Application Server and the JavaDB database. To do so, open a command prompt and change directory to <javaeesdk.home>/bin and issue the following commands:
asadmin start-database
asadmin start-domain
# Change directory to <petstore.home> and enter the following commands
ant setup
ant run
This will setup, build and deploy the petstore on the application server, and then launch the application homepage in your default browser.
The "ant setup" that you run from <petstore.home> (petstore.home is the directory where petstore is installed or where you unzipped it) will populate the database wth data and setup the proper database tables etc that are used by the application.
hth,
Sean

Sun App Server 8.1 and 8.2 could not start

Hi friends, thank for various suggestions. pls i'm having problem with Sun App Server 8.1 and 8.2. I installed Portal 7 on Red Hat Enterprise Linux 3 and also Sun Portal 6 on Suse Linux 9. The problem is that App server keep giving Login exception after using them for a while. The details is given below:
after typing ./asadmin start-domain --user admin domain1. Instead of it to give me the password prompt, it threw the following exception:
INFO: SEC5046: Audit: Authentication refused for [admin]
Login Failed javax.security. auth.login.LoginException: Failed file for login admin
CL1156 could not start the domain domain1.
I always login to the O/S as root.
Any suggestion will be highly appreciated. Thanks

Thanks very much kedar.mhaswade for your suggestions.
I do not have a regular access to the Internet, I
would have gotten back earlier than this, so i'm
sorry. Anyway, i checked the content of
~/.asadminprefs and the password is not the same with
the one i'm using. I found the default password
supplied by Sun but I don't think this could be the
problem. I'm actually using the App server that is
bundled with Sun Portal 6 and 7 and so i supplied my
own password during installation and i've logged in
several times after installation. It just failed in
one of those logins and had stopped working since. I
always encountered the same problem either when using
Sun Portal 7 or 6 on Red Hat ES 3 and Suse 9
respectively.
I'm posting the content of admin-keyfile as you
requested:
admin;{SSHA}Qf/m4KEBDPojsP1mkjywE5XZA6SPh7i8WQmV/A==;a
sadmin
# Domain User and Password - Do Not Delete Entry
Above
So i will so much appreciate your help and i wouldn't
mind if you could send me your phone number. Thanks.Hi tolulike,
Even if you supplied your own password, we have this developer friendly
feature that has side effects that are at times hard to diagnose. Can you
please
- rename the .asadminprefs file and make sure that there is no .asadminprefs file in your home directory?
- attempt to start the domain.
You should be prompted for the password.
The idea is that when you've got that file and that entry AS_ADMIN_PASSWORD in your home directory, asadmin will read it
from there and you land in this (unfortunate) situation.
Obviously doing this might have some side effects with other domains. This
is because for all domains, asadmin reads this file as a last resort. So,
it might so happen that this file is actually required for functioning of your
other domains.
But now you know when this file is used, so there is no mystery (hopefully).
Let me know if this works.
Thank you.
Kedar

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

CLI156 Could not start domain domain1 error when J2ee is installed

Whenever I install J2ee 1.4 sdk the first time the application server starts and everything works fine. But when the system is restarted and the server is started again i get the above mentioned error.
Domain domina1 failed to startup. Could not start domain domain1. I have installed and uninstalled the application many times but yet I am experiencing the same error.
Please give me a solution to this error asap.
Thanks,
Poonam

Did you check server log for the exact cause of startup failure? One thing that is possible is that some of the ports associated with server listeners start being used by other processes after system restart (it seems that Windows use ports in 10xx range for remote drive mappings - so that might be one area where you might run into issues). If so, changing server port numbers might help. In any case, check logs for the exact cause of error .

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

Access Server console could not login due to disable /access policy domain

I misconfig to disable the /access policy domainn. And now the Access Server console could not login, alway loop at initial page. Identity Server console no problem.
Is there any method could enable the /access again? Customer could not accept the reinstallation due to this small problem.
Thank you.

Easiest way is to temporarily disable the webgate in the web server configuration - if it is IIS just remove the webgate from the ISAPI filters tab and restart IIS, if Apache revert back to an httpd.conf without the webgate entries.
Regards,
Colin

EAS server error: Could not connect to administration Server

Hi,
I have installed Hyperion suite in Windows server 2008 R2. It was working fine but now when i tried to login in to the EAS console, I am getting the following error:
"Server Error: Could not connect to administration server".
I tried accessing the same through the web URL and I found "404 error - file or directory not found".
I verified all my services are up and running fine. I am able to connect to the essbase sever through Excel as well as planning.
The log retireved from the HyS9eas-sysout.log file is below:
<Sep 11, 2013 7:06:56 AM JST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Sep 11, 2013 7:06:57 AM JST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Sep 11, 2013 7:06:58 AM JST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Oracle JRockit(R) Version R28.0.2-11-135406-1.6.0_20-20100624-2119-windows-x86_64 from Oracle Corporation>
<Sep 11, 2013 7:07:04 AM JST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.4.0 Fri Dec 17 20:47:33 PST 2010 1384255 >
<Sep 11, 2013 7:07:15 AM JST> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://localhost:7001.>
<Sep 11, 2013 7:07:15 AM JST> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
<Sep 11, 2013 7:07:15 AM JST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Sep 11, 2013 7:07:15 AM JST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Sep 11, 2013 7:07:16 AM JST> <Notice> <LoggingService> <BEA-320400> <The log file E:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EssbaseAdminServices0\logs\EssbaseAdminServices0.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Sep 11, 2013 7:07:16 AM JST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to E:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EssbaseAdminServices0\logs\EssbaseAdminServices0.log00410. Log messages will continue to be logged in E:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EssbaseAdminServices0\logs\EssbaseAdminServices0.log.>
<Sep 11, 2013 7:07:16 AM JST> <Notice> <Log Management> <BEA-170019> <The server log file E:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EssbaseAdminServices0\logs\EssbaseAdminServices0.log is opened. All server side log events will be written to this file.>
<Sep 11, 2013 7:07:48 AM JST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Sep 11, 2013 7:07:56 AM JST> <Warning> <JTA> <BEA-110503> <The migrator(the AdminServer for manual JTA migration policy, or the Singleton Master for automatic JTA migration policy) is not available. Will skip JTA TRS failback because isStrictOwnershipCheck is [false]. This may lead to potencial TLOG corruption if TRS of EssbaseAdminServices0 has been migrated to backup server and the backup server is accessing the TLOG of EssbaseAdminServices0. More safety can be achieved by setting isStrictOwnershipCheck to [true].>
<Sep 11, 2013 7:08:35 AM JST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Sep 11, 2013 7:08:35 AM JST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
Calling getConnection()
return weblogic.management.jmx.mbeanserver.WLSMBeanServer@9830ac
Calling getDomainConfiguration()
Calling getConnection()
return weblogic.management.jmx.mbeanserver.WLSMBeanServer@9830ac
Calling getRuntimeService()
Calling getConnection()
return weblogic.management.jmx.mbeanserver.WLSMBeanServer@9830ac
return com.bea:Name=RuntimeService,Type=weblogic.management.mbeanservers.runtime.RuntimeServiceMBean
return com.bea:Name=EPMSystem,Type=Domain
Calling getConnection()
return weblogic.management.jmx.mbeanserver.WLSMBeanServer@9830ac
Domain location is 'E:\Oracle\Middleware\user_projects\domains\EPMSystem'
Calling getRuntimeService()
return com.bea:Name=RuntimeService,Type=weblogic.management.mbeanservers.runtime.RuntimeServiceMBean
Calling getConnection()
return weblogic.management.jmx.mbeanserver.WLSMBeanServer@9830ac
Calling getConnection()
return weblogic.management.jmx.mbeanserver.WLSMBeanServer@9830ac
Calling getConnection()
return weblogic.management.jmx.mbeanserver.WLSMBeanServer@9830ac
Calling getConnection()
return weblogic.management.jmx.mbeanserver.WLSMBeanServer@9830ac
Checking E:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EssbaseAdminServices0\registry_update.xml file
EPM_ORACLE_HOME: E:\Oracle\Middleware\EPMSystem11R1
Template for EAS#11.1.2.0: E:\Oracle\Middleware\EPMSystem11R1\common\templates\applications\epm_eas_11.1.2.1.jar
Dependencies for E:\Oracle\Middleware\EPMSystem11R1\common\templates\applications\epm_eas_11.1.2.1.jar: [Oracle EPM Common, Oracle EPM Calcmgr, Oracle EPM Planning libraries, Oracle EPM EAS libraries, Oracle EPM Misc libraries, Oracle EPM Xerces libraries]
BPMUI shared webapp not referenced from EAS#11.1.2.0
Application name: EAS#11.1.2.0
Application source: eas.ear
Server name: EssbaseAdminServices0
Server port: 10080
Server SSL port: 10083
Application context: eas
Registry product type: ESSBASE_PRODUCT
Registry physical web application type: ADMIN_SERVICES_WEB_APP
weblogic.Name property is 'EssbaseAdminServices0', seems to be WebLogic mode
registry.isRegistryDatabaseCreated()true
Registry was initialized sucessfully
Executing pre custom update for EAS#11.1.2.0
EPM_ORACLE_INSTANCE: E:\Oracle\Middleware\user_projects\epmsystem1
<Sep 11, 2013 7:09:06 AM JST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'EAS [Version=11.1.2.0]' due to error java.lang.NullPointerException.
java.lang.NullPointerException
at java.io.File.<init>(File.java:222)
at com.hyperion.hit.tool.deploy.update.util.RegistryHelper.createPhysicalWebApp(RegistryHelper.java:168)
at com.hyperion.hit.tool.deploy.update.RegistryUpdater.update(RegistryUpdater.java:36)
at com.hyperion.hit.tool.deploy.update.RegistryUpdateListener.preStart(RegistryUpdateListener.java:91)
at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
Truncated. see log file for complete stacktrace
Caused By: java.lang.NullPointerException
at java.io.File.<init>(File.java:222)
at com.hyperion.hit.tool.deploy.update.util.RegistryHelper.createPhysicalWebApp(RegistryHelper.java:168)
at com.hyperion.hit.tool.deploy.update.RegistryUpdater.update(RegistryUpdater.java:36)
at com.hyperion.hit.tool.deploy.update.RegistryUpdateListener.preStart(RegistryUpdateListener.java:91)
at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
Truncated. see log file for complete stacktrace
>
<Sep 11, 2013 7:09:06 AM JST> <Emergency> <Deployer> <BEA-149259> <Server 'EssbaseAdminServices0' in cluster 'EssbaseAdminServices' is being brought up in administration state due to failed deployments.>
<Sep 11, 2013 7:09:17 AM JST> <Notice> <Cluster> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>
<Sep 11, 2013 7:09:17 AM JST> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of EssbaseAdminServices.>
<Sep 11, 2013 7:09:22 AM JST> <Warning> <Log Management> <BEA-170011> <The LogBroadcaster on this server failed to broadcast log messages to the admin server. The Admin server may not be running. Message broadcasts to the admin server will be disabled.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090171> <Loading the identity certificate and private key stored under the alias DemoIdentity from the jks keystore file E:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoIdentity.jks.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file E:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file E:\Oracle\Middleware\jrockit_160_20\jre\lib\security\cacerts.>
<Sep 11, 2013 7:09:48 AM JST> <Alert> <Security> <BEA-090152> <Demo trusted CA certificate is being used in production mode: [
Version: V3
Subject: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
Key: Sun RSA public key, 512 bits
modulus: 9550192877869244258838480703390456015046425375252278279190673063544122510925482179963329236052146047356415957587628011282484772458983977898996276815440753
public exponent: 65537
Validity: [From: Fri Mar 22 05:12:27 JST 2002,
               To: Wed Mar 23 05:12:27 JST 2022]
Issuer: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
SerialNumber: [    33f10648 fcde0deb 4199921f d64537f4]
Certificate Extensions: 1
[1]: ObjectId: 2.5.29.15 Criticality=true
KeyUsage [
Key_CertSign
Algorithm: [MD5withRSA]
Signature:
0000: 9D 26 4C 29 C8 91 C3 A7   06 C3 24 6F AE B4 F8 82 .&L)......$o....
0010: 80 4D AA CB 7C 79 46 84   81 C4 66 95 F4 1E D8 C4 .M...yF...f.....
0020: E9 B7 D9 7C E2 23 33 A4   B7 21 E0 AA 54 2B 4A FF .....#3..!..T+J.
0030: CB 21 20 88 81 21 DB AC   90 54 D8 7D 79 63 23 3C .! ..!...T..yc#<
] The system is vulnerable to security attacks, since it trusts certificates signed by the demo trusted CA.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "Default[6]" is now listening on 127.0.0.1:10080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[6]" is now listening on 127.0.0.1:10083 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "Default[7]" is now listening on 0:0:0:0:0:0:0:1:10080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[7]" is now listening on 0:0:0:0:0:0:0:1:10083 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on fe80:0:0:0:0:5efe:a0e:daee:10080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 10.14.126.11:10080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[5]" is now listening on fe80:0:0:0:0:5efe:a0e:224b:10083 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[3]" is now listening on fe80:0:0:0:0:5efe:a0e:daee:10083 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[1]" is now listening on 10.14.126.11:10083 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "Default[5]" is now listening on fe80:0:0:0:0:5efe:a0e:224b:10080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on 10.14.34.75:10080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[4]" is now listening on fe80:0:0:0:0:5efe:a0e:7e0b:10083 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure" is now listening on 10.14.218.238:10083 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 10.14.218.238:10080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[2]" is now listening on 10.14.34.75:10083 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "Default[4]" is now listening on fe80:0:0:0:0:5efe:a0e:7e0b:10080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <WebLogicServer> <BEA-000358> <Started WebLogic Independent Managed Server "EssbaseAdminServices0" for domain "EPMSystem" running in Production Mode>
<Sep 11, 2013 7:09:48 AM JST> <Warning> <JMX> <BEA-149510> <Unable to establish JMX Connectivity with the Adminstration Server AdminServer at <JMXServiceURL:null>.>
<Sep 11, 2013 7:09:48 AM JST> <Warning> <Server> <BEA-002611> <Hostname "SJ015040", maps to multiple IP addresses: 10.14.126.11, 10.14.34.75, 10.14.218.238, 0:0:0:0:0:0:0:1>
<Sep 11, 2013 7:09:53 AM JST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Sep 11, 2013 7:09:53 AM JST> <Notice> <WebLogicServer> <BEA-000360> <Server started in ADMIN mode>
HyS9eas-syserr.log is empty and I dont find anyother details from the other log files.
Kindly help me out in solving this issue.
Thanks in advance.
Regards,
Balaji P

Hi John,
Sorry for replying late.
I ran the EPM diagnostic and found EAS & APS application are failed. So as you mentioned, i tried re-deployment through EPM configurator.
But Re-configuration fails with error "An unexpected error occurred and the application will have to shut down" .
When i looked in to the Config tool.log,I got the following messages.
[2013-09-17T18:17:04.635+09:00] [EPMCFG] [TRACE] [EPMCFG-01001] [oracle.EPMCFG] [tid: 17] [ecid: 0000K4fDMY^0zkgpxC^AyW1IE1pJ000003,0:325] [SRC_CLASS: com.hyperion.hit.tool.deploy.utils.UIPortUtil] trace: Parsing server FinancialReporting0 on port 8200 from registry
[2013-09-17T18:17:04.827+09:00] [EPMINS] [ERROR] [EPMINS-00001] [oracle.EPMINS] [tid: 17] [ecid: 0000K4fDMY^0zkgpxC^AyW1IE1pJ000003,0:325] [SRC_CLASS: com.hyperion.hit.wizard.Wizard] trace: Unexpected error:[[
java.lang.NullPointerException
at com.hyperion.hit.tool.deploy.utils.UIPortUtil.<init>(UIPortUtil.java:83)
at com.hyperion.hit.tool.deploy.utils.UIPortUtil.getInstance(UIPortUtil.java:53)
at com.hyperion.config.wizard.DeploymentField.getAppServerDeploymentData(DeploymentField.java:235)
at com.hyperion.config.wizard.DeploymentField.<init>(DeploymentField.java:56)
at com.hyperion.config.wizard.impl.DeploymentForm.<init>(DeploymentForm.java:57)
at com.hyperion.config.wizard.impl.DeploymentState.initializeBeforeShowOnNext(DeploymentState.java:56)
at com.hyperion.hit.wizard.Wizard$NextClass.run(Wizard.java:522)
at java.lang.Thread.run(Thread.java:619)
Since it is similare to the Oracle konwledge base article - (Doc ID 1570293.1), I tried adding the shared service domain to the Windows host file. But i am still recieveing the same error message as above.
Appreciates your help.
Thanks & Regards,
Balaji P

App server 8.1 could not start

Encounter App server 8.1 could not start
Reason by bugger :
Port Conflict
Incorrect server config.
Corrupt depoly app.
Anyone could make to varify the actual cause. I using MS XP SP2, Norton Interent security and connect to internet while depoly to run program encountered such error.
Thing being try :
use netstat has a list of port been use, which is the cause ?
domain.xml server config. file need to be change but which one ?
or could it be corrupted depoly appl. prevent start up ?? clean and redepoly has done.
Thks
ctbeans

Hi,
Please go through the FAQ titled "Why doesn't Application Server start up" which is at :http://developers.sun.com/prodtech/javatools/jscreator/reference/faqs/technical/depsrvs/
Hope thsi helps.
RK.

Could not start domain

Dear all,
I'm experiencing a rather strange issue with the "asadmin" utility for Sun ONE Application Server 7 on Solaris 9, where the default domain "domain1" could not be found.
Whenever the command "asadmin start-domain --domain domain1" is issued, the error,
Could not start the domain.
domain1 is not a registered domainWhen I check the Sun ONE Application Server's installation directory, I found two files "domains.lck" and "domains.bin" both with 0 bytes length.
I've checked with another Sun ONE Application Server's installation directory and found that "domains.bin" is not 0 bytes in length.
Any idea on how to resolve this issue?
Thanks in advance.

Found a solution.
After uninstalling the SUN ONE Application Server, some packages must be removed as stipulated in the post with SunOne ID:7887.
The processes must be killed as well.
After that, the /opt/SUNWappserver7 directory was removed as well.
Reinstalling the application server did not cause any problems. Even the domain "domain1" was registered properly as well!
However, when starting the "domain1", the following error was found in the server.log,
[27/Jan/2004:18:25:08] INFO ( 720): CORE1116: Sun ONE Application Server 7.0.0_01
[27/Jan/2004:18:25:08] INFO ( 721): CORE3016: daemon is running as super-user
[27/Jan/2004:18:25:10] INFO ( 721): CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.4.2_02] from [Sun Microsystems Inc.]
[27/Jan/2004:18:25:10] SEVERE ( 721): CORE4007: Internal error: Unexpected Java exception thrown (unknown exception, no description), stack: java.lang.NoClassDefFoundError: com/sun/messaging/jmq/jmsclient/JMSXATopicConnectionFactoryImpl
     at com.sun.messaging.jmq.admin.jmsspi.JMSAdminFactoryImpl.getJMSAdmin(JMSAdminFactoryImpl.java:53)
     at com.sun.messaging.jmq.admin.jmsspi.JMSAdminFactoryImpl.getJMSAdmin(JMSAdminFactoryImpl.java:39)
     at com.iplanet.ias.jms.IASJmsUtil.getJMSAdminFactory(IASJmsUtil.java:99)
     at com.iplanet.ias.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:157)
     at com.iplanet.ias.server.ApplicationServer.onInitialization(ApplicationServer.java:206)
     at com.iplanet.ias.server.J2EERunner.confPreInit(J2EERunner.java:114)
[27/Jan/2004:18:25:10] SEVERE ( 721): CORE3186: Failed to set configurationAny workarounds would be greatly appreciated... Thanks!!

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

Similar Messages

Maybe you are looking for