-
Bug
-
Resolution: Done
-
Critical
-
7.1.0.DR14
-
None
Properties properties = new Properties(); properties.put("org.jboss.ejb.client.scoped.context", "true"); properties.put(Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming"); properties.put("remote.connections", "main"); properties.put("remote.connection.main.host", "127.0.0.1"); properties.put("remote.connection.main.port", "8080"); properties.put("invocation.timeout", "1"); InitialContext ejbCtx = new InitialContext(properties);
The invocation.timeout property doesn't have any effect when invoking EJBs.
- is blocked by
-
JBEAP-10600 Upgrade EJB client to 4.0.0.Beta27
- Closed
- is cloned by
-
EJBCLIENT-218 Scoped EJB client context ignores invocation.timeout property
- Resolved
- relates to
-
EJBCLIENT-365 EJB client - env property takes not effect when value is an Integer rather than String
- Resolved
-
WFNC-56 Naming client - env property takes no effect when value is an Integer rather than String
- Resolved
-
JBEAP-18495 (7.2.z) EJBCLIENT-365 - EJB client - env property takes not effect when value is an Integer rather than String
- Closed
-
JBEAP-18496 (7.2.z) WFNC-56 - Naming client - env property takes no effect when value is an Integer rather than String
- Closed
-
JBEAP-18499 (7.3.z) EJBCLIENT-365 - EJB client - env property takes not effect when value is an Integer rather than String
- Closed
-
JBEAP-18501 (7.3.z) WFNC-56 - Naming client - env property takes no effect when value is an Integer rather than String
- Closed