For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 3 replies, 2 voices, and was last updated 21 years, 11 months ago by
Riyad Kalla.
-
AuthorPosts
-
Riyad KallaMemberOriginally sent via PM
——————————-I have the following settings for Sun App Server 8 set in MyEclipse. I just installed the app server and used all default settings. I can’t get the server to start up. Any suggestions?
Sun One Server: Enable
Home Directory: C:\Sun\AppServer
Configuration Directory: C:\Sun\AppServer\config
Server Name: server1
Domain Name: domain1
Domain Directory: C:\Sun\AppServer\domains\domain1
Optional Program Arguments:Sun JDK name: j2sdk1.4.1_02
Sun One Launch Mode: Debug mode
Prepended dir to classpath: C:\Sun\AppServer\lib
When I try and start Sun AS the first few lines in the console are as follows:
Starting Sun Java System Application Server Platform Edition 8.0.0_01 (build b08-fcs) …
java.util.logging.ErrorManager: 0: Error In getLogService java.util.logging.ErrorManager: 0: Error In getLogService
recursive call into SystemOutandErrhandler
java.lang.RuntimeException: recursivecallSee attached server.log if needed.
September 9, 2004 at 11:55 pm #214925
Riyad KallaMemberI was unable to reproduce this locally. I installed Sun app server to default location, went into the connector settings and set the following values:
Home Directory: C:\Sun\AppServer
Configuration Directory: C:\Sun\AppServer\config
Server Name: server
Domain Name: domain1
Domain Directory: C:\Sun\AppServer\domains\domain1
Option Program Arguments: <none>This is the startup log for comparison sake:
Starting Sun Java System Application Server Platform Edition 8.0 (build b57-fcs) …
[#|2004-09-09T21:50:24.303-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_04] from [Sun Microsystems Inc.]|#][#|2004-09-09T21:50:25.756-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-09-09T21:50:25.959-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-09-09T21:50:28.990-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-09-09T21:50:29.022-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-09-09T21:50:29.115-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-09-09T21:50:32.709-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-09-09T21:50:34.397-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies…|#]
[#|2004-09-09T21:50:34.772-0700|INFO|sun-appserver-pe8.0|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-09-09T21:50:36.319-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-09-09T21:50:36.381-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Selecting file [C:\Sun\AppServer\lib\install\applications\MEjbApp.ear] for autodeployment|#]
[#|2004-09-09T21:50:36.397-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Selecting file [C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear] for autodeployment|#]
[#|2004-09-09T21:50:36.397-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ C:\Sun\AppServer\lib\install\applications\MEjbApp.ear ] for autodeployment.|#]
[#|2004-09-09T21:50:37.990-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC – START of EJBC for [MEjbApp]|#]
[#|2004-09-09T21:50:38.006-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans …|#]
[#|2004-09-09T21:50:38.209-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Compiling RMI-IIOP code …|#]
[#|2004-09-09T21:50:45.053-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC – END of EJBC for [MEjbApp]|#]
[#|2004-09-09T21:50:45.069-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.stream.out|_ThreadID=10;| role is admin-role class class java.lang.String|#]
[#|2004-09-09T21:50:45.240-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.stream.out|_ThreadID=10;|
role is admin-role class class java.lang.String|#][#|2004-09-09T21:50:45.537-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 8718 msec, Total EJB Compiler Module Time: 7063 msec, Portion spent EJB Compiling: 81%
Breakdown of EJBC Module Time: Total Time for EJBC: 7063 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 6844 msec (96%), JAX-RPC Generation: 172 msec (2%),
|#][#|2004-09-09T21:50:45.553-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = MEjbApp|#]
[#|2004-09-09T21:50:45.740-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent — deploy MEjbApp]|#]
[#|2004-09-09T21:50:46.319-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-09-09T21:50:46.319-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2004-09-09T21:50:46.365-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : C:\Sun\AppServer\lib\install\applications\MEjbApp.ear.|#]
[#|2004-09-09T21:50:46.365-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear ] for autodeployment.|#]
[#|2004-09-09T21:50:47.194-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC – START of EJBC for [__ejb_container_timer_app]|#]
[#|2004-09-09T21:50:51.084-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans …|#]
[#|2004-09-09T21:50:51.084-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC – END of EJBC for [__ejb_container_timer_app]|#]
[#|2004-09-09T21:50:51.272-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 4828 msec, Total EJB Compiler Module Time: 3890 msec, Portion spent EJB Compiling: 80%
Breakdown of EJBC Module Time: Total Time for EJBC: 3890 msec, CMP Generation: 1547 msec (39%), Java Compilation: 2234 msec (57%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
|#][#|2004-09-09T21:50:51.272-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = __ejb_container_timer_app|#]
[#|2004-09-09T21:50:51.319-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent — deploy __ejb_container_timer_app]|#]
[#|2004-09-09T21:50:52.131-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-09-09T21:50:52.131-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-09-09T21:50:52.131-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2004-09-09T21:50:52.162-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear.|#]
[#|2004-09-09T21:50:52.178-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-09-09T21:50:52.490-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [/web1]|#]
[#|2004-09-09T21:50:52.834-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [/asadmin]|#]
[#|2004-09-09T21:50:52.834-0700|WARNING|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2004-09-09T21:50:52.881-0700|INFO|sun-appserver-pe8.0|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-09-09T21:50:52.912-0700|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-09-09T21:50:52.912-0700|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-09-09T21:50:53.115-0700|INFO|sun-appserver-pe8.0|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server-PE-8.0|#]
[#|2004-09-09T21:50:59.850-0700|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-09-09T21:51:03.334-0700|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-09-09T21:51:03.381-0700|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-09-09T21:51:03.694-0700|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-09-09T21:51:03.709-0700|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-09-09T21:51:03.772-0700|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-09-09T21:51:03.803-0700|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-09-09T21:51:04.194-0700|INFO|sun-appserver-pe8.0|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Sun\AppServer\imq\bin].|#]
[#|2004-09-09T21:51:04.209-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1094791864209|#]
[#|2004-09-09T21:51:04.209-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-09-09T21:51:04.225-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
The only difference I see is that my server name is “server” and yours was “server1”. Can you try and see if that makes a difference?
September 10, 2004 at 12:09 am #214928
joegaberMemberThank you, I had the server name as server1. It starts ok now. By the way, would you happen to have a sample build file for deploying to either Sun AS or Weblogic I could use as a starter?
September 10, 2004 at 12:14 am #214929
Riyad KallaMemberJoe,
If you are asking in general for an ant build file that does this, no I don’t have one handy. If you are asking about how MyEclipse does deployment for these servers, it doesn’t use Ant, its our own custom deployment.I just wasn’t clear why you were asking so I wanted to clarify incase that helps.
I’m glad its starting now.
-
AuthorPosts
