NetBeans build 201206140001
JDK 7u3 32-bit
I have an EAR project that I can run on Glassfish 3.1.1 without any trouble using build 201206100001. But using the same project and same IDE user directory with build 201206140001, I get the error below.
The server log contains nothing of interest. In fact, when invoking run on the EAR with Glassfish already running, nothing is added to the server log.
Error writing request body to server
The module has not been deployed.
See the server log for details.
The IDE's messages.log contains the following additional info about the error writing request:
INFO [glassfish]: Error writing request body to server
java.io.IOException: Error writing request body to server
[catch] at org.netbeans.modules.glassfish.common.CommandRunner.handleSend(CommandRunner.java:808)
I am still experiencing this with NetBeans IDE 7.2 RC1 (Build 201206141830). Specifically for Maven-based projects though. Ant-based ones run without problems.
Please, provide more details - steps to reproduce, sample project, server version, JDK version, operating system. I tried the following and it works for me:
- open new project wizard
- choose "Maven|Enterprise Application" and finish the wizard
- add session bean with business method to -ejb sub project
- build main project
- run -ear project. It opens browser at wrong address (bug 215454) but deployment is successful.
Product Version: NetBeans IDE 7.2 (Build 201207101812)
Java: 1.7.0_06-ea; Java HotSpot(TM) 64-Bit Server VM 23.2-b08
System: Windows 7 version 6.1 running on amd64; Cp1250; en_US (nb)
GlassFish Server Open Source Edition 18.104.22.168 (build 4)
I think I finally figured out why I am seeing this and nobody else. :) I followed the steps exactly as in comment 3, and it failed. But first, here is my configuration:
Product Version: NetBeans IDE 7.2 (Build 201206291011)
Java: 1.7.0_05; Java HotSpot(TM) Client VM 23.1-b03
System: Windows 7 version 6.1 running on x86; Cp1252; en_ZA (nb)
I set a password for the admin user of my local GlassFish domain a while ago, because I was testing remotely deploying from our build server and that requires a non-empty password. And initially I could still run the app as before (with NetBeans build 201206100001 and earlier). But from build 201206150001 onwards that never worked again. Until I just set my admin user's password back to an empty string!
So, to reproduce this issue, first set a password for the admin user in GlassFish, (re)start the IDE to make sure that the new credentials will be used, and then try again to deploy. :)
I tried it but I still can't reproduce. I did:
- changed admin password
- stopped GlassFish domain
- restarted IDE
- deployed EAR - IDE asked for username and password and then it was successfully deployed. I tried also GlassFish 3.1.1 (12) and it is the same.
Interesting. Try running the IDE on a 32-bit JVM with the 32-bit launcher?
Something else that might be related, is if I start GlassFish from the IDE, restart the IDE and then start GlassFish again, I get this exception in the Java DB Database Process output window:
Could not listen on port 1527 on host localhost:
java.net.BindException: Address already in use: JVM_Bind
And that makes me think that it might have something to do with running a 32-bit IDE on an otherwise 64-bit system.
Still the same with 1.7.0_03; Java HotSpot(TM) Client VM 22.1-b02. BindException from Java DB doesn't seem to be related.
Well then I give up... :)
Created attachment 123494 [details]
netbeans messages.log file showing setup and zip exceptions
Log file showing zip error when trying to deploy maven project to a glassfish 3.1.1 server. Will also attach screen shot of the error in NB 7.2. Will also show the same operation succeeding in NB 7.1.
Created attachment 123497 [details]
Screenshot NB72 FAIL Deploy
Screen shot showing what happens when trying to deploy EAR.
Created attachment 123498 [details]
Netbeans 7.1 successfully deploys same code to the same server.
Just to show it isn't the code causing an issue, I took a screen shot of NB 7.1 being able to successfully deploy the same code to the same server. So this is a Netbeans 7.2 issue.
The last two NB releases 7.1.2 and 7.2 seem to be falling down severely with Maven. Or maybe Maven with artifactory. But it works for me with 7.1 although NB is kludgey due to previously mentioned issues (known confirmed bug).
Looking at earlier comments I tried to redeploy after setting an empty password for the Glassfish appserver and it didn't help.
The blank password appeared to work for a while and then stopped working again. Hopefully with a second person experiencing this we can gather enough information to really find the cause.
Please provide more information such as operating system and JDK version?
With NetBeans development build 201208200933, I get this additional information from the server log. Whether it is the cause or another problem entirely I don't know.
SEVERE: Exception while deploying the app [file:_C:_Projects_CoreFreight_Backend_core-backend_core-backend-ear_] : Expected to find an expanded directory for submodule core-backend-web-3.0-SNAPSHOT.war but found a JAR. If this is a directory deployment be sure to expand all submodules.
I don't see "Error writing request body to server" any more though.
@theshowmecanuck: Can you try development build 201209020001? I just installed it, and I was able to run my application without problems.
I'm downloading it. I'll install later today. Under some serious time constraints right now, so can't try for too long, have to use what works. :) But I'll see if I can spare a couple minutes. After the last two failed upgrades (for me) I am leery of spending any time on it right now. Besides I did have a chance to look at how they moved the maven stuff around in this latest version and I don't like it at all. But like I said, I'll give it a go. Just not a long one. :)
Ok, installed 201209020001 on Kubuntu Linux 12.04. It runs the project. Nice improvement, good work whoever is responsible.
Unfortunately it has another bug that makes it unusable by me for now. I filed the bug from the IDE and added some additional information via the web.
This new bug is filed as Bug 217762
Verified with build 201209020001.