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.
Enterprise Pack Installer states warnings encountered during install but states installation completed successfully. Errors from log file from AM CONFIGURATION PHASE: Error 1: [2007/03/20 10:44:03]: stopping the AS domain. Location = C:\Sun\AppServer [2007/03/20 10:44:03]: executing command: C:\Sun\AppServer\bin\asadmin.bat stop-domain domain1, in directory: C:\Sun\AppServer [2007/03/20 10:44:04]: [stdout]: The domain (domain1) isn't running. [2007/03/20 10:44:04]: [stderr]: CLI157 Could not stop the domain domain1. [2007/03/20 10:44:04]: [return]: 0 Error 2: [2007/03/20 10:44:18]: deploying AM war file [2007/03/20 10:44:18]: writing file: C:\Sun\AppServer\asadminTmp19765.tmp [2007/03/20 10:44:19]: executing command: C:\Sun\AppServer\bin\asadmin.bat deploy --host localhost --port 4848 --user admin --passwordfile C:\Sun\AppServer\asadminTmp19765.tmp C:\Sun\AppServer\addons\amserver\amserver.war, in directory: C:\Sun\AppServer [2007/03/20 10:45:28]: [stderr]: Mar 20, 2007 10:45:28 AM com.sun.appserv.management.client.ProxyFactory getInstance [2007/03/20 10:45:28]: [stderr]: SEVERE: ProxyFactory.getInstance: Failure trying to create a new ProxyFactory: java.io.IOException: "Unable to connect to admin-server. Please check if the server is up and running and that the host and port provided are correct." [2007/03/20 10:45:28]: [stderr]: com.sun.enterprise.admin.jmx.remote.comm.ServletConnection.handleException (ServletConnection.java:215) [2007/03/20 10:45:28]: [stderr]: com.sun.enterprise.admin.jmx.remote.comm.ServletConnection.receive (ServletConnection.java:119) [2007/03/20 10:45:28]: [stderr]: com.sun.enterprise.admin.jmx.remote.comm.MBeanServerMessageConductor.invoke (MBeanServerMessageConductor.java:62) [2007/03/20 10:45:28]: [stderr]: com.sun.enterprise.admin.jmx.remote.internal.RemoteMBeanServerConnection.getAttr ibute(RemoteMBeanServerConnection.java:284) [2007/03/20 10:45:28]: [stderr]: com.sun.appserv.management.util.jmx.JMXUtil.getMBeanServerID(JMXUtil.java:110) [2007/03/20 10:45:28]: [stderr]: com.sun.appserv.management.client.ProxyFactory.getInstance (ProxyFactory.java:424) [2007/03/20 10:45:28]: [stderr]: com.sun.appserv.management.client.ProxyFactory.getInstance (ProxyFactory.java:388) [2007/03/20 10:45:28]: [stderr]: com.sun.enterprise.deployment.client.DeployAction.run(DeployAction.java:193) [2007/03/20 10:45:28]: [stderr]: java.lang.Thread.run(Thread.java:619) [2007/03/20 10:45:28]: [stderr]: CLI171 Command deploy failed : Deployment of application failed - java.io.IOException: Unable to connect to admin-server. Please check if the server is up and running and that the host and port provided are correct. [2007/03/20 10:45:28]: [return]: 0 Netbeans IDE will start after installation, you can create new enterprise project, however the project will not build and you receive the following Sun application server errors: SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper. sgmt.service_initialized DPL5400:Exception occurred : error in opening zip file. ADM1079: Initialization of AMX MBeans successful After which the build "hangs" for a bit and then you're presented with an authentication failed unable to connect to admin-server pop-up box. Default login information from installer used during install: admin/adminadmin Thank you in advance for any assistance.
Created attachment 39712 [details] Installation Log File
Chris, Are have any firewall running? Could you please try to switch it temporary off and try to reinstall the Enterprise Pack? Could you please also check Java Proxy Settings and Default Browser (IE) proxy settings for any strange things? At least, the "localhost" connection should not be via proxy but the direct one. Thanks, Dmitry
Hi Dmitry, Thank you for the quick reply. My system runs both the standard Windows firewall and McAfee's Firewall. Both were disabled for installation and I'll be leaving them disabled for the interim while the ticket is open. No proxy server is being used but I have double checked the Java settings and the internet settings just in case something was wrong there. There are two internet connections setup on the machine: 1) MSN - No proxy being used and 2) Internet(1) - No proxy being used. From the Java Control Panel the network settings are set as: Use Browser Settings. I double checked the browser settings (IE7 version 7.0.5730.11) and they are referencing the 2 internet connections MSN and Internet(1). Please let me know if you need any additional system information or OS specifics. I really appreciate your help on this.
I`m cc-ing vidhya from Access Manager team. Vidhya, any ideas about the issue?
Additional System info: OS: Microsoft Windows XP Professional 5.1.2600 Service Pack 2, Build 2600 Computer: Dell Optiplex 170L 2992 Mhz, Physical Memory 1,024 MB, Avail Phys Memory 513.03 MB, Total Virtual Memory 2.00 GB, Page File Space 2.41 GB, Hard Drive 74.46 GB with 62.69 GB free. The system is set up with three user accounts: Mine (Admin) and two regular users. Neither user was logged in during installation attempts. Running Java SE Runtime Environment 6. I uninstalled everything last night, rebooted, and re-installed again. I encountered the same errors. If there is any other info that I can provide, please let me know.
Found part of the culprit this morning by going into Control Panel- >Administrative Tools->Computer Management->Services and Applications->Services McAfee's Privacy Service is running a McAfee Proxy Service automatically. There is no reference to this proxy service within McAfee's Security Center and the only way to find it is by viewing services. You have to stop the McAfee's Privacy Service and then stop the McAfee's Proxy Service, change properties on both of those services from the automatic startup to a manual startup. Additionally, even though you disable the firewall via the McAfee Security Center, the Personal Firewall service is still running. I manually stopped that service as well prior to another installation attempt. Once you do that, you can successfully install the Enterprise Pack. The installation wizard for NetBeans Enterprise Pack 5.5 has successfully installed the selected components. The components are installed in the following locations: C:\Program Files\netbeans-5.5 C:\Sun\AppServer C:\Sun\AppServer\addons C:\Sun\AppServer\addons\amserver For details about the newly installed and preinstalled components, see the configuration data file: C:\Program Files\netbeans-5.5\configuration-data.txt Click Finish to exit the wizard. After successful install, I loaded the IDE and successfully created new sample project: command-submissions1. The project built and deployed successfully, however I am still receiving the following error message when the server starts up: SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper. sgmt.service_initialized DPL5400:Exception occurred : error in opening zip file. Any idea what the zip file error is all about?
Chris, At it is written in the Release Notes: http://www.netbeans.org/community/releases/55/entpack_relnotes.html Secure Web Services Access Manager is not supported for Java version 1.6. Description: Access Manager is not supported for Java version 1.6. Workaround: Use Java 1.5.x to run the Access Manager. So I guess that is actually your case.
Thanks. My mistake, I jumped the gun with the installation page's link to the release notes system requirements: Required Software NetBeans Enterprise Pack 5.5 runs on the Java SE Development Kit 5.0 Update 9 or higher (JDK 5.0, version 1.5.0_09 or higher), which consists of the Java Runtime Environment plus developer tools for compiling, debugging, and running applications written in the Java language. Sun Java System Application Server Platform Edition 9 Update 1 has been tested with JDK 5.0 update 6. For Solaris, Windows, and Linux, you can download the JDK for your platform from http://java.sun.com/javase/downloads/index.jsp There's no mention in that section that aspects of the pack wouldn't work on 6. I thought I was good to go since 6 is higher than 1.5.0_09. Perhaps an update to that portion of the document would be helpful. Or provide a link from that section to the portion of the release notes addressing the different AM system requirements. Even the JDK link provided in that section takes you straight to 6 downloads. Makes it cumbersome for someone to newly acquire the correct software. I've uninstalled Java 6 and I am now downloading jdk-1_5_0_11-nb-5_5-win-ml.exe I probably won't be able to install until tomorrow but then I should be able to provide whether or not I'm still seeing any installation errors. Thank you for your help.
I have reinstalled the new downloads per my last message. The install was successful as it was under 6, I was able to successfully create, build and deploy new project command-submissions2 as I was under 6. I still receive the following server message as I did with 6: SEC1002: Security Manager is OFF. ADM0001:MBeanServer initialized successfully SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper. sgmt.service_initialized DPL5400:Exception occurred : error in opening zip file. ADM1079: Initialization of AMX MBeans successful So I guess this brings me back to the question of any idea what the zip file is about? This doesn't appear to be a fatal error under either the 6 or 5 installs as I was experiencing when McAfee's wonderful services were running (McAfee's Proxy Service, McAfee's Privacy Service, and the Security Center disabled Personal Firewall Service), but without knowing what this zip file contains and what the server is trying to do with it, I am not certain if I'm going to run into any future development issues. I appreciate any information that you can either provide or link me to about this zip file. As a side note, when you don't have 6 installed, the enterprise pack will present you with the screen that states it is not able to find any compatible JDK versions and that it recommends JDK 6. I manually directed the install to 5 Update 11 and the install went on just fine. If I had not been working directly with you, I would have taken the install message at its face value that the JDK 5 Update 11 was not compatible and I would have aborted the install to get JDK 6 becuase of that install message. The conflicting information being presented as to which software is required for this pack really makes what should be a simple install procedure into a discouraging process. I've downgraded the Priority on this ticket to a P3 since I have been able to successfully install and I don't feel the zipfile message is a P1 at this time as I can't immediately see any negative impacts from the failure of that zipfile to unzip. I would like for the ticket to remain open until the zipfile message is resolved or a workaround provided. I'd like to proceed with development under this latest install unless you think the zipfile message is severe enough to postpone development, in which case, please reset the severity to P1. I do appreciate your time involved with this issue.
It doesn't seem like Access Manager related at all.
I would agree, Vidhya. I'm pretty confident that it is an Application Server issue now that I have been able to successfully install the enterprise pack. So far I've been building enterprise beans in our business project and getting successful builds. Deployments with sample projects prior to beginning work on our own application all deployed successfully. So far I haven't hit any glitches that seem to be related to the zip file error but the error does occur each time the Sun Java System Application Server 9.0 starts up. The server log doesn't contain the name of the zip file it is trying to open so it makes it difficult for me to assess whether or not this is even an issue at all anymore. I'd just feel more comfortable if someone more familiar with this software would be able to identify what this zip file is, what files are contained within it, and what problems I may expect from the zipfile not opening. A work around to getting the zipfile to open would be the optimum resolution at this time.
Since this issue is no longer relevant, closing as WONTFIX. Please file further issues against the NBI-based installer.