Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-13175

Expressions in jboss-ejb-client.xml don't work for client-context invocation-timeout

    XMLWordPrintable

Details

    • Hide

      sample jboss-ejb-client.xml

      <?xml version="1.0" encoding="UTF-8"?>
<jboss-ejb-client xmlns="urn:jboss:ejb-client:1.2">

	<!-- only in client-context invocation-timeout value binding is not working -->
	<client-context invocation-timeout="${ejb.remote.invocation-timeout:120000}">

		<ejb-receivers exclude-local-receiver="false">
			<remoting-ejb-receiver outbound-connection-ref="remote-ejb-connection-1" connect-timeout="${ejb.remote.connect-timeout:5000}" />
		</ejb-receivers>

		<clusters>
			<cluster name="clustername" security-realm="security-realm" username="username">
				<connection-creation-options>
					<property name="org.xnio.Options.SSL_ENABLED" value="false" />
					<property name="org.xnio.Options.SASL_POLICY_NOANONYMOUS" value="false" />
					<property name="org.xnio.Options.KEEP_ALIVE" value="true"/>
					<property name="org.jboss.remoting3.RemotingOptions.HEARTBEAT_INTERVAL" value="${ejb.remote.heartbeat-interval:7500}"/>
					<property name="org.xnio.Options.READ_TIMEOUT" value="${ejb.remote.read-timeout:30000}"/>
				</connection-creation-options>
			</cluster>
		</clusters>

	</client-context>
</jboss-ejb-client>
      Show
      sample jboss-ejb-client.xml <?xml version= "1.0" encoding= "UTF-8" ?> <jboss-ejb-client xmlns= "urn:jboss:ejb-client:1.2" > <!-- only in client-context invocation-timeout value binding is not working --> <client-context invocation-timeout= "${ejb.remote.invocation-timeout:120000}" > <ejb-receivers exclude-local-receiver= "false" > <remoting-ejb-receiver outbound-connection-ref= "remote-ejb-connection-1" connect-timeout= "${ejb.remote.connect-timeout:5000}" /> </ejb-receivers> <clusters> <cluster name= "clustername" security-realm= "security-realm" username= "username" > <connection-creation-options> <property name= "org.xnio.Options.SSL_ENABLED" value= "false" /> <property name= "org.xnio.Options.SASL_POLICY_NOANONYMOUS" value= "false" /> <property name= "org.xnio.Options.KEEP_ALIVE" value= "true" /> <property name= "org.jboss.remoting3.RemotingOptions.HEARTBEAT_INTERVAL" value= "${ejb.remote.heartbeat-interval:7500}" /> <property name= "org.xnio.Options.READ_TIMEOUT" value= "${ejb.remote.read-timeout:30000}" /> </connection-creation-options> </cluster> </clusters> </client-context> </jboss-ejb-client>

    Description

      WFLY-4303 made it possible to use expressions in jboss-ejb-client.xml
      However that doesn't seem to work everywhere. We tried to make several especially timeout related properties configurable and while expressions work at most places, in the case of client-context invocation-timeout they don't and we get a java.lang.NumberFormatException for the string specified as the value of the invocation-timeout.

      Would it be possible to make the client-context invocation-timeout work with expressions as well?

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-18833 (7.3.z) Expressions in jboss-ejb-client.xml don't work for client-context invocation-timeout

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Verified
          is related to

          Feature Request - Feature requests from customers and/or users WFLY-4303 Allow expressions in jboss-ejb-client.xml if configuration jboss-descriptor-property-replacement=true

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              cfang@redhat.com Cheng Fang
              cfang@redhat.com Cheng Fang
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: