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.
CASA editor produce a blank (trivial) <throttling> entry in jbi.xml When open up a comp app in CASA, and edit the QoS Node on one of the partner link, and go to the section "Throttling Extension", activate the input cursor in the input field "MaxConcurrencyLimit" but does not type any number in it, just hit return to confirm. that will cause a trivial throttling entry in the jbi.xml for the comp app. <throttling xmlns="http://www.sun.com/jbi/qos/throttling" maximumConcurrencyLimit=""/> the issue is: this will cause the current BaseMessagingChannel in qos.jar stop doing the redelivery ... this can be fixed on either the design time (CASA editor) or runtime (BaseMessagingChannel in qos.jar), but preferrably, when there is no meaningful values specified in "Throttling Extension" of the CASA partner link QoS editor, do not generate the trivial entry.
In the latest build, the reported behavior is not reproducible. It's true that once you enter a maximumConcurrencyLimit number and hit return, it's not easy to clear the throttling entry, even if you clear the maximumConcurrencyLimit number in the property sheet. To clear the throttling entry altoghether, right click the connection (not on the QoS icon) and select "Clear QoS"->"Throttling" from the context menu.
tested on 1110 capsr6u1 build. as this is p3, it will probably not get into this release even if you fix it immediately. i still see the same problem as described. after clicking on the maxconcurrencyLimit field but not supplying any value, then rebuild & the throttling entry now appears in jbi.xml as described: <throttling xmlns="http://www.sun.com/jbi/qos/throttling" maximumConcurrencyLimit=""/> note this is after selecting a redirection endpoint. the whole jbi.xml is as follows: <?xml version="1.0" encoding="UTF-8" standalone="no"?> <jbi xmlns="http://java.sun.com/xml/ns/jbi" xmlns:ns1="http://localhost/Synchronous/Synchronous" xmlns:ns2="http://enterprise.netbeans.org/bpel/Synchronous/Synchronous" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.0" xsi:schemaLocation="http://java.sun.com/xml/ns/jbi ./jbi.xsd"> <service-assembly> <identification> <name>SoapSampleApplication</name> <description>Represents the Service Assembly of SoapSampleApplication</description> </identification> <service-unit> <identification> <name>SoapSampleApplication-SoapSample</name> <description>Represents this Service Unit</description> </identification> <target> <artifacts-zip>SoapSample.jar</artifacts-zip> <component-name>sun-bpel-engine</component-name> </target> </service-unit> <service-unit> <identification> <name>SoapSampleApplication-sun-http-binding</name> <description>Represents this Service Unit</description> </identification> <target> <artifacts-zip>sun-http-binding.jar</artifacts-zip> <component-name>sun-http-binding</component-name> </target> </service-unit> <connections> <connection> <consumer endpoint-name="port1" service-name="ns1:service1"/> <provider endpoint-name="partnerlinktyperole1_myRole" service-name="ns2:Synchronous"/> </connection> </connections> <connections xmlns="http://www.sun.com/jbi/qos"> <connection> <consumer endpoint-name="port1" service-name="ns1:service1"/> <provider endpoint-name="partnerlinktyperole1_myRole" service-name="ns2:Synchronous"/> <redelivery xmlns="http://www.sun.com/jbi/qos/redelivery"> <on-failure> <redirect xmlns:ns1="http://enterprise.netbeans.org/bpel/Synchronous/Synchronous" endpoint-name="partnerlinktyperole1_myRole" operation="operation1" service-name="ns2:Synchronous"/> </on-failure> </redelivery> <throttling xmlns="http://www.sun.com/jbi/qos/throttling" maximumConcurrencyLimit=""/> </connection> </connections> </service-assembly> </jbi>