- This topic has 15 replies, 5 voices, and was last updated 18 years, 2 months ago by
Geoff.
-
AuthorPosts
-
Oscar A. RamirezMemberI am trying to start Sun Java System App Server 8 from within Eclipse. I get the following error:
[#|2004-10-25T14:19:16.048-0400|INFO|sun-appserver-pe8.1|javax.enterprise.system.core|_ThreadID=10;|IdentityManager Data: User:null|#]
Has anyone experienced a similar issue? If so, how did you get around it?
Any help would be appreciated.
Oscar Ramirez
October 26, 2004 at 9:13 am #218309
Riyad KallaMemberIs this Server 8 or 8.1? If its 8.1 then you need to apply the new quickfix we just released that added a new 8.1 connector: http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-4498.html
October 27, 2004 at 7:46 pm #218420
nat101MemberHi. I have the same problem. I do have both quickfixes installed.
Please note, that deployment does work, but I cannot start/stop from within the ide. I think that it might need an additional argument in the connector setup, but I don’t know.Here is the console output:
Starting Sun Java System Application Server Platform Edition 8.0.0_01 (build b08-fcs) ... 27/10/2004 20:25:17 com.sun.enterprise.server.PEMain main SEVERE: Could not start S1AS PE 8 Server : Null or zero length argument
Thanks;
-nat
ps. Does this forum software allow me to include a [local] jpg in a post?October 29, 2004 at 8:24 am #218507
nat101MemberAny news on this?
Thanks
-natOctober 29, 2004 at 10:20 am #218510
Riyad KallaMembernat can you provide me a link to Sun App Server that you are using, I’m going to install it now and test it.
October 29, 2004 at 11:03 am #218511
nat101MemberOk. http://java.sun.com/j2ee/1.4/download.html#sdk
The top half of the page is a beta of the next version.
If you scroll down about half page you get the the 8.1 (current) June 15th version. This is the guy we are talking about.TA
-natOctober 29, 2004 at 11:25 am #218513
Riyad KallaMemberOk so this file: sjsas_pe-8_0_0_01-windows.exe
Note in your post you said 8.1, but I think you meant 8.0 Update 1 (8.1 required a new connector that was added by QF 2)
October 29, 2004 at 12:17 pm #218525
nat101MemberI call it 8.1 (although there is no such animal) because MyEclipse calls it 8.1.
In my post (3rd message) on this thread, the version is clear: 8.0.0_01 (build b08-fcs).-nat
October 29, 2004 at 1:40 pm #218535
Riyad KallaMemberbecause MyEclipse calls it 8.1.
Actually MyEclipse calls it 8.0, the 8.1 connector is for the Beta because they signifigantly changed their launching architecture between 8.0 and Beta… are you trying to use the 8.1 connector to start 8.0 Update 1? Please try using the 8.0 connector, that is most likely the problem.
October 29, 2004 at 2:06 pm #218536
nat101MemberOh.
I did try the 8.0 connector first, but that gave me tons of errors, so I thought that the 8.0 connector was for 8.0 pre update 1 only. (Maybe it is.)
Here are some of the errors with the 8.0 connector.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 java.util.logging.ErrorManager: 0: Error In getLogService recursive call into SystemOutandErrhandler java.lang.RuntimeException: recursivecall at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream.flush(SystemOutandErrHandler.java:189) at java.io.PrintStream.write(PrintStream.java:260) at sun.nio.cs.StreamEncoder$ConverterSE.implFlushBuffer(StreamEncoder.java:236) ...... java.util.logging.ErrorManager: 0: Error In getLogService java.util.logging.ErrorManager: 0: Error In getLogService java.util.logging.ErrorManager: 0: Error In getLogService java.util.logging.ErrorManager: 0: Error In getLogService java.util.logging.ErrorManager: 0: Error In getLogService java.util.logging.ErrorManager: 0: Error In getLogService java.util.logging.ErrorManager: 0: Error In getLogService java.util.logging.ErrorManager: 0: Error In getLogService java.util.logging.ErrorManager: 0: Error In getLogService java.lang.NullPointerException at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigModel(ServerBeansFactory.java:58) at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigBean(ServerBeansFactory.java:95) at com.sun.enterprise.server.logging.ServerLogManager.getLogService(ServerLogManager.java:281)
The dump goes on and on and on…..
Maybe we do need 3 connectors; 8.0, 8.0 update 1, and 8.1.
Have a nice weekend;
-natOctober 29, 2004 at 3:25 pm #218544
Riyad KallaMembernat,
I think something is incorrect with your install, I just installed the version I stated above, which you confirmed was correct, went into the App Server 8 settings, use the following settings:
and here is the output:
Starting Sun Java System Application Server Platform Edition 8.0.0_01 (build b08-fcs) …
[#|2004-10-29T13:22:28.848-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_04] from [Sun Microsystems Inc.]|#][#|2004-10-29T13:22:29.958-0700|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-10-29T13:22:30.192-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-10-29T13:22:32.520-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-10-29T13:22:32.520-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-10-29T13:22:32.536-0700|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-10-29T13:22:36.458-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-10-29T13:22:37.989-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies…|#]
[#|2004-10-29T13:22:38.286-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-10-29T13:22:39.864-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-10-29T13:22:39.926-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Selecting file [C:\Java\AppServer\lib\install\applications\MEjbApp.ear] for autodeployment|#]
[#|2004-10-29T13:22:39.942-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Selecting file [C:\Java\AppServer\lib\install\applications\__ejb_container_timer_app.ear] for autodeployment|#]
[#|2004-10-29T13:22:39.942-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ C:\Java\AppServer\lib\install\applications\MEjbApp.ear ] for autodeployment.|#]
[#|2004-10-29T13:22:41.567-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC – START of EJBC for [MEjbApp]|#]
[#|2004-10-29T13:22:41.583-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans …|#]
[#|2004-10-29T13:22:41.645-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Compiling RMI-IIOP code …|#]
[#|2004-10-29T13:22:49.755-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC – END of EJBC for [MEjbApp]|#]
[#|2004-10-29T13:22:49.801-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.stream.out|_ThreadID=10;| role is admin-role class class java.lang.String|#]
[#|2004-10-29T13:22:50.536-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.stream.out|_ThreadID=10;|
role is admin-role class class java.lang.String|#][#|2004-10-29T13:22:50.864-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 10484 msec, Total EJB Compiler Module Time: 8188 msec, Portion spent EJB Compiling: 78%
Breakdown of EJBC Module Time: Total Time for EJBC: 8188 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 8094 msec (98%), JAX-RPC Generation: 15 msec (0%),
|#][#|2004-10-29T13:22:50.864-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = MEjbApp|#]
[#|2004-10-29T13:22:51.051-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent — deploy MEjbApp]|#]
[#|2004-10-29T13:22:51.630-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-10-29T13:22:51.645-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2004-10-29T13:22:51.676-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : C:\Java\AppServer\lib\install\applications\MEjbApp.ear.|#]
[#|2004-10-29T13:22:51.676-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ C:\Java\AppServer\lib\install\applications\__ejb_container_timer_app.ear ] for autodeployment.|#]
[#|2004-10-29T13:22:52.411-0700|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-10-29T13:22:57.473-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans …|#]
[#|2004-10-29T13:22:57.473-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC – END of EJBC for [__ejb_container_timer_app]|#]
[#|2004-10-29T13:22:57.661-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 5906 msec, Total EJB Compiler Module Time: 5062 msec, Portion spent EJB Compiling: 85%
Breakdown of EJBC Module Time: Total Time for EJBC: 5062 msec, CMP Generation: 1656 msec (32%), Java Compilation: 3125 msec (61%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
|#][#|2004-10-29T13:22:57.676-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = __ejb_container_timer_app|#]
[#|2004-10-29T13:22:57.723-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent — deploy __ejb_container_timer_app]|#]
[#|2004-10-29T13:22:58.536-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-10-29T13:22:58.536-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-10-29T13:22:58.551-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2004-10-29T13:22:58.583-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : C:\Java\AppServer\lib\install\applications\__ejb_container_timer_app.ear.|#]
[#|2004-10-29T13:22:58.630-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-10-29T13:22:58.973-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [/web1]|#]
[#|2004-10-29T13:22:59.270-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [/asadmin]|#]
[#|2004-10-29T13:22:59.270-0700|WARNING|sun-appserver-pe8.0.0_01|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-10-29T13:22:59.317-0700|INFO|sun-appserver-pe8.0.0_01|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-10-29T13:22:59.333-0700|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-10-29T13:22:59.348-0700|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-10-29T13:22:59.536-0700|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server-PE-8.0|#]
[#|2004-10-29T13:23:06.005-0700|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-10-29T13:23:08.411-0700|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-10-29T13:23:08.473-0700|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-10-29T13:23:08.723-0700|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-10-29T13:23:08.723-0700|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-10-29T13:23:08.786-0700|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-10-29T13:23:08.817-0700|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-10-29T13:23:09.083-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Java\AppServer\imq\bin].|#]
[#|2004-10-29T13:23:09.098-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1099081389098|#]
[#|2004-10-29T13:23:09.098-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-10-29T13:23:09.098-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
October 31, 2004 at 1:33 pm #218581
nat101MemberYes! Right you are.
In the ‘server name’ field, I had entered a random name. I didn’t realize that I had to leave it as ‘server’.
I changed it to ‘server’ and all works now, including debugging.
Thanks;
-nat
ps. What is this ‘server’ field all about?October 31, 2004 at 6:24 pm #218588
Scott AndersonParticipantps. What is this ‘server’ field all about?
It is literally the name you gave to your sever when you created the domain. The default name is ‘server’, and that’s why this works.
Of course, with proper configuration of your domain, you can change the name to whatever you like.November 4, 2004 at 12:57 pm #218878
Oscar A. RamirezMemberI got diverted to other items and did not come back to check on an answer. This worked. I had downloaded 8.1, and the new plug-in worked like a charm.
Thanks a lot for your help.
Oscar
November 4, 2004 at 12:59 pm #218879
Riyad KallaMemberGlad it is working, thank you for closing the loop.
-
AuthorPosts