[JBoss JIRA] (WFLY-12188) What's the difference of the READ_TIMEOUT in ejb3 subsystem vs. remoting subsystem
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-12188?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFLY-12188:
-----------------------------------------
[~jbaesner] [~flavia.rainone] [~gtedorst] This sounds to me like a duplicate of WFLY-11911. The READ_TIMEOUT setting in the ejb3 subsystem was cruft that had no effect.
> What's the difference of the READ_TIMEOUT in ejb3 subsystem vs. remoting subsystem
> ----------------------------------------------------------------------------------
>
> Key: WFLY-12188
> URL: https://issues.jboss.org/browse/WFLY-12188
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 17.0.0.Final
> Reporter: Joerg Baesner
> Assignee: Flavia Rainone
> Priority: Major
>
> What's the difference of the {{READ_TIMEOUT}} in _ejb3_ subsystem vs. _remoting_ subsystem? See:
> {code}
> <remote connector-ref="http-remoting-connector" thread-pool-name="default">
> <channel-creation-options>
> <option name="READ_TIMEOUT" value="${prop.remoting-connector.read.timeout:20}" type="xnio"/>
> <option name="MAX_OUTBOUND_MESSAGES" value="1234" type="remoting"/>
> </channel-creation-options>
> </remote>
> {code}
> {code}
> <subsystem xmlns="urn:jboss:domain:remoting:4.0">
> <endpoint/>
> <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm">
> <!-- server-side configuration -->
> <properties>
> <property name="org.jboss.remoting3.RemotingOptions.HEARTBEAT_INTERVAL" value="5000"/>
> <property name="KEEP_ALIVE" value="true"/>
> <property name="READ_TIMEOUT" value="10000"/>
> <property name="WRITE_TIMEOUT" value="10000"/>
> </properties>
> </http-connector>
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-4186) Guided Rules does not output parenthesis in DRL
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4186?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4186:
--------------------------------
Fix Version/s: 7.24.0.Final
> Guided Rules does not output parenthesis in DRL
> -----------------------------------------------
>
> Key: DROOLS-4186
> URL: https://issues.jboss.org/browse/DROOLS-4186
> Project: Drools
> Issue Type: Bug
> Components: Guided Template Editor
> Environment: RHDM 7.3
> Reporter: Karina Varela
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools, guided_rule_editor
> Fix For: 7.24.0.Final
>
>
> The Guided Rule is omitting one parenthesis from the generated DRL source. This behavior only happens on LHS.
> No errors are raised on the server logs.
> Expected source code:
> {code:java}
> Silverware( type in ("Spoon", "Spoon (fancy)") )
> {code}
> Generated source code:
> {code:java}
> Silverware( type in ("Spoon", "Spoon (fancy") )
> {code}
> h3. Acceptance test
> Set up column with *is contained in* operator and type value
> - a, b ,c (/)
> - (a, b, c) (/)
> - a(), b(), c() (/)
> - (a(), b(), c()) (/)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (JBEE-204) JAX-RS FactoryFinder failing resolution using ServiceLoader with secMgr enabled
by Alessio Soldano (Jira)
Alessio Soldano created JBEE-204:
------------------------------------
Summary: JAX-RS FactoryFinder failing resolution using ServiceLoader with secMgr enabled
Key: JBEE-204
URL: https://issues.jboss.org/browse/JBEE-204
Project: JBoss JavaEE Spec APIs
Issue Type: Bug
Reporter: Alessio Soldano
Assignee: Alessio Soldano
>From JBEAP-17069:
When the security manager is enabled the resteasy client initialization fails with the following exception:
{noformat}
ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /resteasy/SampleServlet: java.lang.RuntimeException: java.lang.ClassNotFoundException: org.glassfish.jersey.client.JerseyClientBuilder from [Module "javax.ws.rs.api" version 1.0.1.Final-redhat-00001 from local module loader @69d9c55 (finder: local module finder @13a57a3b (roots: /opt/jboss/jboss-eap-7.2/modules,/opt/jboss/jboss-eap-7.2/modules/system/layers/base/.overlays/layer-base-jboss-eap-7.2.1.CP,/opt/jboss/jboss-eap-7.2/modules/system/layers/base))]
at javax.ws.rs.client.ClientBuilder.newBuilder(ClientBuilder.java:132)
at com.redhat.sample.SampleServlet.processRequest(SampleServlet.java:29)
at com.redhat.sample.SampleServlet.doGet(SampleServlet.java:48)
...
Caused by: java.lang.ClassNotFoundException: org.glassfish.jersey.client.JerseyClientBuilder from [Module "javax.ws.rs.api" version 1.0.1.Final-redhat-00001 from local module loader @69d9c55 (finder: local module finder @13a57a3b (roots: /opt/jboss/jboss-eap-7.2/modules,/opt/jboss/jboss-eap-7.2/modules/system/layers/base/.overlays/layer-base-jboss-eap-7.2.1.CP,/opt/jboss/jboss-eap-7.2/modules/system/layers/base))]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:255)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at javax.ws.rs.client.FactoryFinder.newInstance(FactoryFinder.java:120)
at javax.ws.rs.client.FactoryFinder.find(FactoryFinder.java:227)
at javax.ws.rs.client.ClientBuilder.newBuilder(ClientBuilder.java:96)
... 52 more
{noformat}
It seems that the issue is that the internal resteasy class is not found and the default {{org.glassfish.jersey.client.JerseyClientBuilder}} is tried but fails.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months