This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
In M9 installer: installation ends with error on latest screen (with [finish] button) I've got another SUNWappserver installed. That seems to be the problem (I'm not sure of course). It's a pity, that user has no option to go one step back and change the server settings (if this is the problem...). IDE is installed, but some modules weren't activated during startup... It is impossible to run uninstall script now, it says, that another installer is running and ends with error message (I haven't tried to reboot...). I'll try to install M9 Full with another server parameters to find out, if SUNWappserver caused these issues... end of log (whole log is attached): [2007-04-30 15:19:30.246]: executing command: chmod ugo+x updatetool.template , in directory: /opt/SUNWappserver_m9/updatecenter/lib/install/templates [2007-04-30 15:19:30.258]: [return]: 0 [2007-04-30 15:19:30.258]: ... command execution finished [2007-04-30 15:19:30.261]: executing command: /opt/SUNWappserver_m9/bin/asadmin create-domain --interactive=false --adminport 4848 --adminuser admin --passwordfile /opt/SUNWappserver_m9/nbi-19076.tmp --instanceport 8080 --domainproperties http.ssl.port=8181 --savemasterpassword=true domain1 , in directory: /opt/SUNWappserver_m9 [2007-04-30 15:19:30.731]: [stdout]: Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/enterprise/cli/framework/CLIMain [2007-04-30 15:19:30.787]: [return]: 1 [2007-04-30 15:19:30.787]: ... command execution finished [2007-04-30 15:19:30.789]: org.netbeans.installer.utils.exceptions.InstallationException: Failed to create the default domain [2007-04-30 15:19:30.789]: at org.netbeans.installer.products.sjsas.ConfigurationLogic.install(ConfigurationLogic.java:153) [2007-04-30 15:19:30.789]: at org.netbeans.installer.product.components.Product.install(Product.java:263) [2007-04-30 15:19:30.789]: at org.netbeans.installer.wizard.components.actions.InstallAction.execute(InstallAction.java:127) [2007-04-30 15:19:30.789]: at org.netbeans.installer.wizard.components.WizardAction$1.run(WizardAction.java:103) [2007-04-30 15:19:30.789]: Caused by: org.netbeans.installer.utils.applications.GlassFishUtils$DomainCreationException: Could not create domain - the process returned 1 [2007-04-30 15:19:30.789]: at org.netbeans.installer.utils.applications.GlassFishUtils.createDomain(GlassFishUtils.java:100) [2007-04-30 15:19:30.789]: at org.netbeans.installer.utils.applications.GlassFishUtils.createDomain(GlassFishUtils.java:67) [2007-04-30 15:19:30.789]: at org.netbeans.installer.products.sjsas.ConfigurationLogic.install(ConfigurationLogic.java:144)
Created attachment 41967 [details] installer's log
Created attachment 41969 [details] this dialog jumped out after finish button was pressed
Installation was successful after non-default port addresses were chosen during the installation wizard (application server configuration part). IDE now runs fine . So the problem is probably in another instance of application server installed...
pchytil, The real issue is the IBM`s java. Please correct me If I am wrong but IBM`s java 6 is in a preview quality (as they even call it Early Release) and there are several issues in it (you installation log confirms that) even though it is based on Sun`s jdk6u1. So, please do not use it either for installer running (specify Sun`s java using --javahome /usr/java/jdk1.6.0) and for the NetBeans IDE and Application Server configuration. I lowering the priority. AFAIK IBM`s java6 (and java5, and both BEA`s as well) are not tested either by NetBeans QA or Application Server QA.
Just a note. I`ve installed NBI together with the latest IBM`s JDK6 (java full version "J2RE 1.6.0 IBM linux build jclxi3260- 20070508_01") and default domain was created successfully (though it was not able to start at all). So we should contact application server team to gather the requirements on the JDK that AS can be run on. If they say that AS can only be run on Sun`s JDK then we would filter all available JDK so that only Sun`s jdks would be there.
Due to the information received from appserver team : Application Server/GlassFish is tested with Sun JDK for Windows, Solaris and Linux. For MacOS, they use Apple JDK. GlassFish does not work with IBM JDK and we they in the middle of a porting exercise to fix that. They have not tried porting to BEA JDK yet. So to fix the issue we`ll need to add additional requirement for JDK (together with min and max version) - its vendor. It should be "Sun Microsystems" until GlassFish would finished their porting.
Fixed. I`ve added support for jdk vendor checking in JdkLocationPanel. Now AppServer/GlassFish installation logic verify that vendor is Sun Microsystems (Apple on Mac`s).
Installation was successful after support for jdk vendor checking was added. https://spanishdictionary.cc/