Closed glassfishrobot closed 14 years ago
glassfishrobot
commented
6 years ago glassfishrobot
commented
15 years ago @glassfishrobot Commented sanandal said: "Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1 release whose primary release driver is SailFin. This issue will be scrubbed after this release and will be given the right priority for the next release."
glassfishrobot
commented
14 years ago @glassfishrobot Commented tmueller said: The bugtraq The bugtraq bug 6591758 is marked as fix delivered. Marking this issue likewise. is marked as fix delivered. Marking this issue likewise.
glassfishrobot
commented
17 years ago @glassfishrobot Commented Was assigned to km
glassfishrobot
commented
7 years ago @glassfishrobot Commented This issue was imported from java.net JIRA GLASSFISH-3496
glassfishrobot
commented
17 years ago @glassfishrobot Commented Reported by gfbugbridge
glassfishrobot
commented
14 years ago @glassfishrobot Commented Marked as fixed on Friday, May 14th 2010, 8:18:20 am
*READ-ONLY Data from Bugtraq***** Inside SWAN :http://swsblweb1.central.sun.com:8080/CrPrint?id=6591758 Outside SWAN :http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6591758 ****READ-ONLY Data from Bugtraq Ends** *READ-ONLY Data from Bugtraq***** Description The Addon infrastructure exits without installing any components if one of the addons hits an error. Also, nothing is logged to alert the user of the problem. The user has to be looking at the start-domain commands output. This bug was hit when the latest App Platform SDK build 25 was intalled on a server that didn't have the graphics libraries installed. The portal container addon configurator currently has a dependency on a graphics class. When the domain that has the portail container installed via the addons in started for the first time on a system that doesn't have the graphics libraries installed, the addon infrastructure errors out with the error below (that isn't logged) without installing any of the other addon components.
ACTUAL ERROR 4 lines below: java_re@laforge%<143>asadmin start-domain Starting Domain domain1, please wait. Log redirected to /tmp/basler/SDK/domains/domain1/logs/server.log. Could not initialize class sun.awt.X11GraphicsEnvironment Redirecting output to /tmp/basler/SDK/domains/domain1/logs/server.log Domain domain1 is ready to receive client requests. Additional services are being started in background. Domain [domain1] is running [Sun Java System Application Server 9.1 (build b58a-rc2)] with its configuration and logs at: [/tmp/basler/SDK/domains]. Admin Console is available at http://localhost:4848. Use the same port [4848] for "asadmin" commands. User web applications are available at these URLs: [http://localhost:8080 https://localhost:8181](http://localhost:8080 https://localhost:8181). Following web-contexts are available: [/web1 /__wstx-services ]. Standard JMX Clients (like JConsole) can connect to JMXServiceURL: [service:jmx:rmi:///jndi/rmi://laforge:8686/jmxrmi] for domain management purposes. Domain listens on at least following ports for connections: [8080 8181 4848 3700 3820 3920 8686 ]. Domain does not support application server clusters and other standalone instances.
Since the initial install configures all the addons, once a error is hit, the addons are not installed. The domain will not try to re-install the components on subsequent restarts, because an empty domain-registry has already been created.
This problem is also hit is a dependecy is not statisfied in the addon hierarcy. For example, the WSRP component requires the portal-container. If the user adds the WSRP component without the portal-container, the addon infrastructure will error out without logging an exception or installing any of the other addon components.
To reproduce:
java_re@laforge%<335>asadmin start-domain domain4 Starting Domain domain4, please wait. Log redirected to /tmp/basler/SDK3/domains/domain4/logs/server.log. INFO:Access Manager is enabled and configured successfully. The operation CONFIGURE on the addon am-configurator is complete. Aug 10, 2007 10:26:52 AM com.sun.jbi.installer.JBIComponentsConfigurator configure INFO: Configuring jbi components... Aug 10, 2007 10:27:00 AM com.sun.jbi.installer.JBIComponentsConfigurator configure INFO: OpenESB JBI Components Configuration Successful The operation CONFIGURE on the addon jbi_components_configurator is complete. Fatal Exception while configuring the addon wsrp-configurator com.sun.appserv.addons.AddonFatalException: For the addon wsrp-configurator the dependent component portlet-container-configurator is not installed or missing. Redirecting output to /tmp/basler/SDK3/domains/domain4/logs/server.log Domain domain4 is ready to receive client requests. Additional services are being started in background. Domain [domain4] is running [Sun Java System Application Server 9.1 (build b58a-rc2)] with its configuration and logs at: [/tmp/basler/SDK3/domains]. Admin Console is available at http://localhost:4848. Use the same port [4848] for "asadmin" commands. User web applications are available at these URLs: [http://localhost:8080 https://localhost:8181](http://localhost:8080 https://localhost:8181). Following web-contexts are available: [/web1 /__wstx-services ]. Standard JMX Clients (like JConsole) can connect to JMXServiceURL: [service:jmx:rmi:///jndi/rmi://laforge:8686/jmxrmi] for domain management purposes. Domain listens on at least following ports for connections: [8080 8181 4848 3700 3820 3920 8686 ]. Domain does not support application server clusters and other standalone instances.
****READ-ONLY Data from Bugtraq Ends** *READ-ONLY Data from Bugtraq***** Justification Priority changed from [] to [3-Medium]Addon infrastucture should continue installing the other addon components logging any exceptions that are XXXXXX 2007-08-10 19:24:21 GMT
****READ-ONLY Data from Bugtraq Ends**
Environment
Operating System: Solaris Platform: All
Affected Versions
[9.1pe]