facebook

J2EE Q42004 Beta App Server connector

  1. MyEclipse IDE
  2.  > 
  3. Installation, Configuration & Updates
Viewing 12 posts - 16 through 27 (of 27 total)
  • Author
    Posts
  • #217373 Reply

    Scott,

    I understand your concerns, but on the other hand not fixing this for the beta essentially puts ME users in the position of either not using the beta or giving up debug mode inside of eclipse for the server. But I think there is a rather simple solution. If you can give me exactly the command strings that you use to start and stop the server, then I can build a filter to insert into sun’s asadmin command that translates your command into the new syntax. I will be happy to post this script. I will base the filter on perl, so I think most developers will be able to use it if they want.

    – joel

    #217405 Reply

    I gave this a go, but it looks like you do not use the asadmin command. Seems that you are calling the Java class directly to start/stop. Yes I guess that makes sense since you want to connect the debugger to the jvm. Did not think that through up front.

    So it looks like there is no way to get this going without ME doing some code changes. Would you even consider a special quick fix for those of us who need tihs?

    Thanks,
    Joel

    #217411 Reply

    Scott Anderson
    Participant

    Joel,

    The problem we have supporting beta code is that it’s beta code. That is, we might spend a bunch of time issuing a quickfix and then the next beta won’t work with the new fix, etc, etc. Additionally, changing the connector also runs the risk of breaking it for everyone that is using it with the released version of the server, so it’s not that simple to assess the risk and decide if it’s worth it or not. So, as a general rule we only support production releases.

    That said, I’ll see if I can get someone to look into it and if the fix appears relatively trivial we might be able to do something.

    #217431 Reply

    Scott,

    Here is what I have ascertained from looking at it. As far as starting and stopping the server is concered, which I think is all the ME plugin worries about, the commands have changed from “start” to “start_domain” and “stop” to “stop_domain”. I believe that you will break the functionality agains SJSAS 8.0 if you simply change these. What is needed is either a new server profile for 8.1 or a flag on the preferences of the existing profile to indicate that you are launching against 8.1. I think that this is the extent of the modifications, but of course I can not be certain without your code.

    Btw, IMHO, it was pretty silly of Sun not to keep the old commands working for a bit and clearly mark them as deprecated.

    – joel

    #217454 Reply

    Scott Anderson
    Participant

    Joel,

    Thanks for the additional research. I’ll look into that shortly and see if it’s the case. We’ve also contacted our technical contact at Sun directly to see if he can shed some light onto what changed. However, if that’s all it is, we should be able to do something to get a quickfix out for it before 3.8.3’s released.

    #217500 Reply

    Scott Anderson
    Participant

    Joel,

    I tried out the Sun 8 2004Q4 beta by downloading it here: http://java.sun.com/j2ee/1.4/download.html

    I then configured the Sun 8 connector like the following:

    I then started it successfully with JDK 1.4.1 and got the following output:

    Starting Sun Java System Application Server Platform Edition 8.0 (build b57-fcs) …
    [#|2004-10-12T17:35:01.024-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.1_02] from [Sun Microsystems Inc.]|#]

    [#|2004-10-12T17:35:03.498-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]

    [#|2004-10-12T17:35:03.838-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]

    [#|2004-10-12T17:35:08.245-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]

    [#|2004-10-12T17:35:08.275-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]

    [#|2004-10-12T17:35:08.305-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]

    [#|2004-10-12T17:35:13.893-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]

    [#|2004-10-12T17:35:17.217-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies…|#]

    [#|2004-10-12T17:35:18.149-0500|INFO|sun-appserver-pe8.0|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]

    [#|2004-10-12T17:35:20.492-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]

    [#|2004-10-12T17:35:22.445-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]

    [#|2004-10-12T17:35:23.827-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]

    [#|2004-10-12T17:35:23.827-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]

    [#|2004-10-12T17:35:24.007-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]

    [#|2004-10-12T17:35:24.498-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [/web1]|#]

    [#|2004-10-12T17:35:24.878-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [/asadmin]|#]

    [#|2004-10-12T17:35:24.888-0500|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-10-12T17:35:24.909-0500|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-10-12T17:35:24.939-0500|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]

    [#|2004-10-12T17:35:24.939-0500|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]

    [#|2004-10-12T17:35:25.289-0500|INFO|sun-appserver-pe8.0|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server-PE-8.0|#]

    [#|2004-10-12T17:35:33.671-0500|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-10-12T17:35:36.355-0500|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]

    [#|2004-10-12T17:35:36.495-0500|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]

    [#|2004-10-12T17:35:36.876-0500|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]

    [#|2004-10-12T17:35:36.886-0500|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]

    [#|2004-10-12T17:35:37.026-0500|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]

    [#|2004-10-12T17:35:37.036-0500|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]

    [#|2004-10-12T17:35:37.817-0500|INFO|sun-appserver-pe8.0|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\dev\appservers\SunJSASPE8\imq\bin].|#]

    [#|2004-10-12T17:35:37.857-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1097620537857|#]

    [#|2004-10-12T17:35:37.887-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]

    [#|2004-10-12T17:35:37.887-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]

    I then verified it worked by externally launching the Sun admin console. Everything looked fine. To shut it down I used the connector and got the following output:

    [#|2004-10-12T17:36:53.796-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|sending notification to server…server|#]

    [#|2004-10-12T17:36:58.213-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Server shutdown complete.|#]

    So, for me the connector is working fine on this new release with no changes from what we shipped in 3.8.2″ alt=””>

    #217522 Reply

    Scott,

    I am not sure where you went wrong, but you are not running the 8.1 beta. If you look at the top of the log output that you posted you will see that is says

    Starting Sun Java System Application Server Platform Edition 8.0 (build b57-fcs

    If you were running the beta this would be:

    Starting Sun Java System Application Server Platform Edition 8.1 (build b28-beta) …

    Please check what you installed.

    Thanks,
    Joel

    #217528 Reply

    Scott Anderson
    Participant

    Joel,

    Can you post a link to the download page so that I be sure I get the correct version if the one I posted is not correct?

    #217532 Reply

    Scott,

    The link in your previous post http://java.sun.com/j2ee/1.4/download.html is correct. That is why I do not understand why you do not have the proper version. If you select from the Separate Bundles option, then the file that you down load should be sjsas_pe-8_2004Q4-beta-windows.exe if you you are on windows. The downloaded files for the other platforms have similar names starting with sjsas_pe-8_2004Q4-beta. Does this help?

    – joel

    #217534 Reply

    Scott Anderson
    Participant

    Joel,

    Nevermind. I found the issue and replicated the problem. It’s actually much more than the start/stop commands, unfortunately.
    It looks like they’ve changed the launch model substantially.

    #217535 Reply

    Sigh…that does not sound promissing. 😥

    #217537 Reply

    Scott Anderson
    Participant

    We’ll see. We’ve got some other connector work slated so we might be able to give it a look, especially if the Sun guys get back to us.

Viewing 12 posts - 16 through 27 (of 27 total)
Reply To: J2EE Q42004 Beta App Server connector

You must be logged in to post in the forum log in