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.
I'm using netbeans-trunk-nightly-200910170201-ml-java-solaris-sparc.sh. I'm trying to run a standalone application client jar. To do this, I've always built the project, defined the run properties (command line arguments), then selected Run. When I do this now, NB first deploys the jar, apparently -- if I type "asadmin list-components" after a short time, it shows up, and it also appears under Services->Servers->GlassFish v3 Domain->Applications. But the application never runs. The back-and-forth bar saying "Deploying [appname]" keeps on going, indicating that the process is hanging. The Run process in the Output window displays the following (eventually): init: deps-jar: compile: library-inclusion-in-archive: dist: pre-run-deploy: Distributing /home/chaase/NetBeansProjects/producer/dist/producer.jar to [GlassFish v3 Domain] /home/chaase/NetBeansProjects/producer/nbproject/build-impl.xml:573: Deployment error: Deployment timeout has exceeded. See the server log for details. BUILD FAILED (total time: 20 minutes 0 seconds) NB doesn't seem to know that the jar has deployed. If I try again with the Run command, NB tries to deploy it again. I see the following in the window where I started NB: WARNING [glassfish-eecommon]: Deployment plan not supported in GlassfishConfiguration.save() WARNING [glassfish]: No object found matching applications.application.*.context-root%%%EOL%%% WARNING [org.netbeans.modules.j2ee.deployment.devmodules.spi.J2eeModuleProvider]: Accessing instance property through org.netbeans.modules.j2ee.deployment.devmodules.spi.J2eeModuleProvider is pointing to a missing API or a bad design of the module WARNING [org.netbeans.modules.j2ee.deployment.devmodules.spi.J2eeModuleProvider]: Accessing instance property through org.netbeans.modules.j2ee.deployment.devmodules.spi.J2eeModuleProvider is pointing to a missing API or a bad design of the module I have to exit out of NB to kill the process.
Vince, sounds like server plugin side. Pass back if not yours. Thanks.
I ran a simple client with no problem in a recently built pull of web-main on solaris. I am using v3 b69. please attach a zip of the troublesome project. what jdk are you using? Update?
I was using b68, which comes with the NB nightly I was using. I'll start using the latest, which now has b69. Also I should mention that my client apps are JMS applications and need to start the JMSRA. The appclient command does this nowadays. When the clients are bundled in an EAR, everything works fine in NB, too. I'll attach a zip that contains both the producer and consumer JMS apps, so that if it works you don't end up with a lot of stray messages. You need a JMS connection factory and a queue or topic to run them. (Queue is simpler.) asadmin create-jms-resource --restype javax.jms.Queue --property Name=PhysicalQueue jms/Queue asadmin create-jms-resource --restype javax.jms.ConnectionFactory jms/ConnectionFactory
Created attachment 89980 [details] zip file containing 2 client JMS apps
Forgot to mention -- I'm using jdk1.6.0_16.
Forgot to mention you also need to set the Run properties for the examples -- for producer, queue 3 and for synchconsumer, queue Basically, you are following the instructions in http://java.sun.com/javaee/5/docs/tutorial/doc/bncfa.html#bncfb, "A Simple Example of Synchronous Message Receives".
I can confirm that the problem occurs in netbeans-dev-200910230201 with glassfish-v3-b69, just as with the previous builds.
I'm attaching another server log from trying to deploy a client this morning using the latest 10/23 NB build on Windows, with the GF b69 that comes with it. This is an error I used to see a lot running from the command line in GF, but I haven't seen it for a while. The deployment seems to have succeeded, but the back-and-forth Deploying ... bar is still going on. [#|2009-10-23T14:16:48.312-0400|SEVERE|glassfish|javax.enterprise.system.contain er.appclient.org.glassfish.appclient.server.core|_ThreadID=30;_ThreadName=Thread -1;|ACDEPL105: Error starting the adapter to serve static system-level content java.io.FileNotFoundException: C:\Program%20Files\glassfish-v3-b69\glassfish\mod ules\gf-client.jar (The system cannot find the path specified) at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.<init>(ZipFile.java:114) at java.util.jar.JarFile.<init>(JarFile.java:133) at java.util.jar.JarFile.<init>(JarFile.java:97) at org.glassfish.appclient.server.core.jws.JWSAdapterManager.getGFClient ModuleClassPath(JWSAdapterManager.java:555) Another issue I have seen is an ORB bug that keeps being fixed and then broken again. The telltale indicator in the server log for this one is a hang after this message. This is a GF issue and not a NetBeans one. Oct 23, 2009 2:05:02 PM com.sun.jts.CosTransactions.DefaultTransactionService identify_ORB INFO: jts.startup_msg
Created attachment 90018 [details] server.log from Windows, renamed winserver.log
I should mention that there is an ORB bug in several GF builds this week that prevents any app client from running. The GF build that doesn't have this bug is the second one from 10/20, the version of glassfish-v3-b69-10_20_2009.zip that is currently at http://download.java.net/glassfish/v3/nightly/. It was fixed in this build but has cropped up again in the 10/22 nightly. I filed an issue. However, when I try to deploy an appclient in NetBeans using the 10/20 GF build, I still get the hang after the "Initializing..." message. So the NB problem is apparently not related to the ORB bug.
OK. The additional info helped me reproduce the issue.
http://hg.netbeans.org/web-main/rev/81552b028615
Integrated into 'main-golden', will be available in build *200910241428* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/81552b028615 User: Vince Kraemer <vkraemer@netbeans.org> Log: #175137: deployment could 'hang' if there are absolutely no web apps on a server.