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.
Reproduced with build 200802060003. To reproduce the bug: - install GlassFish so it would use ports 8089, 8189, 4849 instead of 8080, 8181, 4848 respectively - create TRS sample app; - deploy and test it. 3 of 4 tests fail due to differences in port configuration.
Vladimir, we should look at this and decide whether we can easily fix it or not.
We can use a token variable, let it be _HttpPort_ for HTTP port instead of hardcoded default value 8080 in wsdl files. This token must be certainly specified before deployment. It is unclear when and how it should be done: wsdl files which should be changed live in EJB and BPEL modules. Application server is set in EJB and Comp projects. What should be done if user change server in one project only? What we should do if no application server in IDE? I think that this issue is too risky for implementation. TRS is *sample* and we can add information in our tutorials and guidelines that TRS *must* be run on Application server with default http port 8080. Note that 8080 is default HTTP port for the JavaEE web services. I'm voting not to touch TRS at all. QA, please, specify *detailed* algorithm how and when default http port 8080 should be changed in all cases (application server is changed, is absent etc.)
The whole idea of sample is they should work smoothly with default configurations. The ability to work with non-default configurations is usefull but not mandatory. Will try to fix it for FCS. Decreasing to P3.
If the product is installed with nondefault values of used ports, BPEL samples should be configured accordingly. The values are known and set while the product is being installed. The other cases such as the app server is reconfigured after the installation or is missing, are not considered here.
Can you please provide API to get the host and port of the GlassFish application server?
There is an api - issue 133751. GF part of the work - issue 136264.
none of these TM values are valid at this point
Vince, does this issue still exist ? If not, can you please close it ? thanks
looks like this issue is fixed.
Reproducible with NetBeans IDE Dev (Build 200903030229)
API is already there as mentioned...
Vladimir, please take a look.
related: j2eeserver module
The issue is not BPEL samples specific, the samples don't contain any server configuration. The root is in compapp.projects.jbi module: Details: <Concurrent test thread 0> did not complete. Success rate 0/1 ) 14.08.2009 14:54:56 com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection post SEVERE: SAAJ0010: Unable to read response java.lang.NullPointerException at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:438) at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:214) at java.security.AccessController.doPrivileged(Native Method) at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:185) at org.netbeans.modules.compapp.catd.util.Util.sendMessage(Util.java:422) at org.netbeans.modules.compapp.catd.ConfiguredTest$ConcurrentTestSendOnlyRunnable.run(ConfiguredTest.java:1887) at java.lang.Thread.run(Thread.java:619) com.sun.xml.messaging.saaj.SOAPExceptionImpl: java.security.PrivilegedActionException: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to read response: null at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:191) at org.netbeans.modules.compapp.catd.util.Util.sendMessage(Util.java:422) at org.netbeans.modules.compapp.catd.ConfiguredTest$ConcurrentTestSendOnlyRunnable.run(ConfiguredTest.java:1887) at java.lang.Thread.run(Thread.java:619) Caused by: java.security.PrivilegedActionException: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to read response: null at java.security.AccessController.doPrivileged(Native Method) at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:185) ... 3 more Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to read response: null at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:448) at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:214) ... 5 more CAUSE: java.security.PrivilegedActionException: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to read response: null at java.security.AccessController.doPrivileged(Native Method) at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:185) at org.netbeans.modules.compapp.catd.util.Util.sendMessage(Util.java:422) at org.netbeans.modules.compapp.catd.ConfiguredTest$ConcurrentTestSendOnlyRunnable.run(ConfiguredTest.java:1887) at java.lang.Thread.run(Thread.java:619) Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to read response: null at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:448) at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:214) ... 5 more CAUSE: java.security.PrivilegedActionException: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to read response: null at java.security.AccessController.doPrivileged(Native Method) at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:185) at org.netbeans.modules.compapp.catd.util.Util.sendMessage(Util.java:422) at org.netbeans.modules.compapp.catd.ConfiguredTest$ConcurrentTestSendOnlyRunnable.run(ConfiguredTest.java:1887) at java.lang.Thread.run(Thread.java:619) Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to read response: null at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:448) at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:214) ... 5 more