[JBoss JIRA] (WFLY-9973) WildFly 12 IIOP always requires SSL
by Ivan Straka (JIRA)
[ https://issues.jboss.org/browse/WFLY-9973?page=com.atlassian.jira.plugin.... ]
Ivan Straka updated WFLY-9973:
------------------------------
Attachment: (was: server-side.war)
> WildFly 12 IIOP always requires SSL
> -----------------------------------
>
> Key: WFLY-9973
> URL: https://issues.jboss.org/browse/WFLY-9973
> Project: WildFly
> Issue Type: Bug
> Components: IIOP
> Affects Versions: 11.0.0.Final, 12.0.0.Final
> Reporter: Ivan Straka
> Assignee: Tomasz Adamski
>
> When app deployed to WF 10.1 calls an EJB deployed to WF 12.0 via IIOP, the call will fail because WF 12.0 responds (Location Forward message - GIOP protocol) that It requires SSL even if It does not (to the best of my knowledge).
> WF 12.0 standard IIOP subystem configuration:
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:iiop-openjdk:2.0">
> <orb socket-binding="iiop"/>
> <initializers security="identity" transactions="spec"/>
> <security server-requires-ssl="false" client-requires-ssl="false"/>
> </subsystem>
> {code}
> It is observable [here|https://github.com/wildfly/wildfly/blob/10.1.0.Final/iiop-openjdk/sr...] (client side debugging). ssl.target_requires is true and ssl.target_supports is false.
> This does not happen when
> * server side is WF 10.1 - ssl.target_requires is false and ssl.target_supports is true.
> * client side is WF 12.0 - it works due to better condition at client side [here|https://github.com/wildfly/wildfly/blob/12.0.0.Final/iiop-openjdk/sr...] which results to not using SSL
> If IIOP subsystem is configured to use iiop ssl socket, It will work - EAP just does not responds correctly if ssl is not configured.
> It is possible that I have malconfigured server side EAP and I am missing something.
> Deployments used as reproducers are simple.
> client-side: simple servlet that calls an EJB
> {code:java}
> @WebServlet(urlPatterns = "/")
> public class ClientServlet extends HttpServlet {
> @Override
> protected void doGet(HttpServletRequest req, HttpServletResponse resp)
> throws ServletException, IOException {
> try {
> Context ctx = new InitialContext(new Properties());
> Object iiopObj = ctx.lookup("corbaname:iiop:127.0.0.1:3628#Bean");
> BeanHome home = (BeanHome) PortableRemoteObject.narrow(iiopObj, BeanHome.class);
> BeanRemote beanRemote = home.create();
> String string = beanRemote.invoke();
> System.out.println("Bean obtained by IIOP returned: " + string);
> resp.getWriter().append("Bean obtained by IIOP returned: ").append(string).append("\n");
> } catch (Exception e) {
> resp.getWriter().append("Calling bean failed: ");
> e.printStackTrace(resp.getWriter());
> throw new RuntimeException(e);
> }
> }
> }
> {code}
> server-side: simple EJB
> {code:java}
> public class Bean {
> public String invoke() {
> return "server side invocation: success";
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-9973) WildFly 12 IIOP always requires SSL
by Ivan Straka (JIRA)
[ https://issues.jboss.org/browse/WFLY-9973?page=com.atlassian.jira.plugin.... ]
Ivan Straka updated WFLY-9973:
------------------------------
Attachment: (was: client-side.war)
> WildFly 12 IIOP always requires SSL
> -----------------------------------
>
> Key: WFLY-9973
> URL: https://issues.jboss.org/browse/WFLY-9973
> Project: WildFly
> Issue Type: Bug
> Components: IIOP
> Affects Versions: 11.0.0.Final, 12.0.0.Final
> Reporter: Ivan Straka
> Assignee: Tomasz Adamski
>
> When app deployed to WF 10.1 calls an EJB deployed to WF 12.0 via IIOP, the call will fail because WF 12.0 responds (Location Forward message - GIOP protocol) that It requires SSL even if It does not (to the best of my knowledge).
> WF 12.0 standard IIOP subystem configuration:
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:iiop-openjdk:2.0">
> <orb socket-binding="iiop"/>
> <initializers security="identity" transactions="spec"/>
> <security server-requires-ssl="false" client-requires-ssl="false"/>
> </subsystem>
> {code}
> It is observable [here|https://github.com/wildfly/wildfly/blob/10.1.0.Final/iiop-openjdk/sr...] (client side debugging). ssl.target_requires is true and ssl.target_supports is false.
> This does not happen when
> * server side is WF 10.1 - ssl.target_requires is false and ssl.target_supports is true.
> * client side is WF 12.0 - it works due to better condition at client side [here|https://github.com/wildfly/wildfly/blob/12.0.0.Final/iiop-openjdk/sr...] which results to not using SSL
> If IIOP subsystem is configured to use iiop ssl socket, It will work - EAP just does not responds correctly if ssl is not configured.
> It is possible that I have malconfigured server side EAP and I am missing something.
> Deployments used as reproducers are simple.
> client-side: simple servlet that calls an EJB
> {code:java}
> @WebServlet(urlPatterns = "/")
> public class ClientServlet extends HttpServlet {
> @Override
> protected void doGet(HttpServletRequest req, HttpServletResponse resp)
> throws ServletException, IOException {
> try {
> Context ctx = new InitialContext(new Properties());
> Object iiopObj = ctx.lookup("corbaname:iiop:127.0.0.1:3628#Bean");
> BeanHome home = (BeanHome) PortableRemoteObject.narrow(iiopObj, BeanHome.class);
> BeanRemote beanRemote = home.create();
> String string = beanRemote.invoke();
> System.out.println("Bean obtained by IIOP returned: " + string);
> resp.getWriter().append("Bean obtained by IIOP returned: ").append(string).append("\n");
> } catch (Exception e) {
> resp.getWriter().append("Calling bean failed: ");
> e.printStackTrace(resp.getWriter());
> throw new RuntimeException(e);
> }
> }
> }
> {code}
> server-side: simple EJB
> {code:java}
> public class Bean {
> public String invoke() {
> return "server side invocation: success";
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2398) [DMN Designer] Change of function discards width of parent column
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2398?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-2398:
----------------------------------------
[~jomarko] Oh, I think I understand... the screenshot you attach illustrates the problem?
> [DMN Designer] Change of function discards width of parent column
> -----------------------------------------------------------------
>
> Key: DROOLS-2398
> URL: https://issues.jboss.org/browse/DROOLS-2398
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.7.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Minor
> Fix For: 7.7.0.Final
>
> Attachments: Screenshot from 2018-03-21 09-34-25.png
>
>
> Issue found during review of DROOLS-2368 but not sure if related, most probably not. Change of function definition discards width of parent column.
> h2. Acceptance criteria
> Recursively (to achieve 3 depth levels):
> # Declare context entry
> # Add 6 rows
> # Configure first 5 rows as: Literal, Decision Table, Function, Invocation, Relation
> # Configure the 6th row as Context and repeat with first step
> At each depth level, check other columns width is updated when:
> # Literal is
> ## updated, resized, cleared, removed
> # Decision table is
> ## updated, resized, cleared, removed
> # Function is
> ## updated, resized, cleared, removed
> # Invocation is
> ## updated, resized, cleared, removed
> # Relation is
> ## updated, resized, cleared, removed
> # Context is
> ## updated, resized, cleared, removed
> Column widths preserved after reopen (x)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2398) [DMN Designer] Change of function discards width of parent column
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2398?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-2398:
-------------------------------------
[~manstis] DROOLS-2262 is slightly different, will try to explain:
* DROOLS-2262
** if you add decision table
** increase width of input and output
** save and reopen
** The width of input and output will be reset to some default value, however all column of decision table will be visible
* DROOLS-2398
** if you add decision table
** increase width of input and output
** save and reopen
** You won't see all decision table columns, there will be rendered something with width of one column
Makes sense?
> [DMN Designer] Change of function discards width of parent column
> -----------------------------------------------------------------
>
> Key: DROOLS-2398
> URL: https://issues.jboss.org/browse/DROOLS-2398
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.7.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Minor
> Fix For: 7.7.0.Final
>
> Attachments: Screenshot from 2018-03-21 09-34-25.png
>
>
> Issue found during review of DROOLS-2368 but not sure if related, most probably not. Change of function definition discards width of parent column.
> h2. Acceptance criteria
> Recursively (to achieve 3 depth levels):
> # Declare context entry
> # Add 6 rows
> # Configure first 5 rows as: Literal, Decision Table, Function, Invocation, Relation
> # Configure the 6th row as Context and repeat with first step
> At each depth level, check other columns width is updated when:
> # Literal is
> ## updated, resized, cleared, removed
> # Decision table is
> ## updated, resized, cleared, removed
> # Function is
> ## updated, resized, cleared, removed
> # Invocation is
> ## updated, resized, cleared, removed
> # Relation is
> ## updated, resized, cleared, removed
> # Context is
> ## updated, resized, cleared, removed
> Column widths preserved after reopen (x)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2398) [DMN Designer] Change of function discards width of parent column
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2398?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-2398:
----------------------------------------
Thanks [~jomarko] I'll look into immediately. Please note that the column width preservation requirement is captured by DROOLS-2262. It requires changes to marshalling too; as we currently do not persist column widths.
> [DMN Designer] Change of function discards width of parent column
> -----------------------------------------------------------------
>
> Key: DROOLS-2398
> URL: https://issues.jboss.org/browse/DROOLS-2398
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.7.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Minor
> Fix For: 7.7.0.Final
>
> Attachments: Screenshot from 2018-03-21 09-34-25.png
>
>
> Issue found during review of DROOLS-2368 but not sure if related, most probably not. Change of function definition discards width of parent column.
> h2. Acceptance criteria
> Recursively (to achieve 3 depth levels):
> # Declare context entry
> # Add 6 rows
> # Configure first 5 rows as: Literal, Decision Table, Function, Invocation, Relation
> # Configure the 6th row as Context and repeat with first step
> At each depth level, check other columns width is updated when:
> # Literal is
> ## updated, resized, cleared, removed
> # Decision table is
> ## updated, resized, cleared, removed
> # Function is
> ## updated, resized, cleared, removed
> # Invocation is
> ## updated, resized, cleared, removed
> # Relation is
> ## updated, resized, cleared, removed
> # Context is
> ## updated, resized, cleared, removed
> Column widths preserved after reopen (x)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-9742) ClassLoader leak in JBoss Threads caused by MDBs
by Markus Dlugi (JIRA)
[ https://issues.jboss.org/browse/WFLY-9742?page=com.atlassian.jira.plugin.... ]
Markus Dlugi closed WFLY-9742.
------------------------------
Resolution: Duplicate Issue
> ClassLoader leak in JBoss Threads caused by MDBs
> ------------------------------------------------
>
> Key: WFLY-9742
> URL: https://issues.jboss.org/browse/WFLY-9742
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 11.0.0.Final
> Reporter: Markus Dlugi
> Assignee: David Lloyd
> Attachments: default-threads-tccl.png, jboss-threads-tccl-example.zip
>
>
> There is a classloader leak in JBoss Threads which is most noticable when deploying MDBs. When a new MDB is created and a new thread for the MDB is started in the JCA thread pool ("default-threads - x"), the thread will be created using the context classloader of the MDB's deployment unit. This is because [MessageDrivenComponent.activate()|https://github.com/wildfly/wildfly/blob...] sets the context classloader of the ServerService thread in order to create the MDB, and this classloader will then also be used by the child thread.
> In the default configuration, the threads in the default thread pool will not be terminated and therefore the thread will keep the reference to the classloader even when the deployment unit is undeployed. This in turn can lead to "OutOfMemoryError: Metaspace" after a couple of redeployments.
> As a workaround, we changed [JBossThreadFactory.createThread()|https://github.com/jbossas/jboss-thread...] to set the context classloader to null after a new thread has been created. While this fixes the issue for us, I am not sure whether this is a good solution for all consumers of the thread factory, or if this should be fixed in the JCA subsystem instead. That's also the reason why I opened this issue against the WildFly project instead of JBoss Threads.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-9742) ClassLoader leak in JBoss Threads caused by MDBs
by Markus Dlugi (JIRA)
[ https://issues.jboss.org/browse/WFLY-9742?page=com.atlassian.jira.plugin.... ]
Markus Dlugi commented on WFLY-9742:
------------------------------------
Fixed via JBTHR-51.
> ClassLoader leak in JBoss Threads caused by MDBs
> ------------------------------------------------
>
> Key: WFLY-9742
> URL: https://issues.jboss.org/browse/WFLY-9742
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 11.0.0.Final
> Reporter: Markus Dlugi
> Assignee: David Lloyd
> Attachments: default-threads-tccl.png, jboss-threads-tccl-example.zip
>
>
> There is a classloader leak in JBoss Threads which is most noticable when deploying MDBs. When a new MDB is created and a new thread for the MDB is started in the JCA thread pool ("default-threads - x"), the thread will be created using the context classloader of the MDB's deployment unit. This is because [MessageDrivenComponent.activate()|https://github.com/wildfly/wildfly/blob...] sets the context classloader of the ServerService thread in order to create the MDB, and this classloader will then also be used by the child thread.
> In the default configuration, the threads in the default thread pool will not be terminated and therefore the thread will keep the reference to the classloader even when the deployment unit is undeployed. This in turn can lead to "OutOfMemoryError: Metaspace" after a couple of redeployments.
> As a workaround, we changed [JBossThreadFactory.createThread()|https://github.com/jbossas/jboss-thread...] to set the context classloader to null after a new thread has been created. While this fixes the issue for us, I am not sure whether this is a good solution for all consumers of the thread factory, or if this should be fixed in the JCA subsystem instead. That's also the reason why I opened this issue against the WildFly project instead of JBoss Threads.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2398) [DMN Designer] Change of function discards width of parent column
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2398?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-2398:
-------------------------------------
Review stopped, after reopen of any decision node, the context editor is rendered with minimal width:
!Screenshot from 2018-03-21 09-34-25.png|thumbnail!
> [DMN Designer] Change of function discards width of parent column
> -----------------------------------------------------------------
>
> Key: DROOLS-2398
> URL: https://issues.jboss.org/browse/DROOLS-2398
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.7.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Minor
> Fix For: 7.7.0.Final
>
> Attachments: Screenshot from 2018-03-21 09-34-25.png
>
>
> Issue found during review of DROOLS-2368 but not sure if related, most probably not. Change of function definition discards width of parent column.
> h2. Acceptance criteria
> Recursively (to achieve 3 depth levels):
> # Declare context entry
> # Add 6 rows
> # Configure first 5 rows as: Literal, Decision Table, Function, Invocation, Relation
> # Configure the 6th row as Context and repeat with first step
> At each depth level, check other columns width is updated when:
> # Literal is
> ## updated, resized, cleared, removed
> # Decision table is
> ## updated, resized, cleared, removed
> # Function is
> ## updated, resized, cleared, removed
> # Invocation is
> ## updated, resized, cleared, removed
> # Relation is
> ## updated, resized, cleared, removed
> # Context is
> ## updated, resized, cleared, removed
> Column widths preserved after reopen (x)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month