[JBoss JIRA] (ELY-1607) Revise cipher suites exposed by Elytron
by Justin Cook (JIRA)
[ https://issues.jboss.org/browse/ELY-1607?page=com.atlassian.jira.plugin.s... ]
Justin Cook commented on ELY-1607:
----------------------------------
[~mchoma] Adding the cipher suites without the OpenSSL name results in a successful outcome, should I include them without the OpenSSL name, with null for the OpenSSL name, or not include them?
Example:
In MechanismDatabase.properties:
TLS_PSK_WITH_ARIA_128_CBC_SHA256 = ,PSK,PSK,ARIA128,SHA256,TLSv1.2,false,HIGH,false,128,128,C0,64
Running: /subsystem=elytron/server-ssl-context=p:add(key-manager=httpsKM,cipher-suite-filter="TLS_PSK_WITH_ARIA_128_CBC_SHA256")
Results in: {"outcome" => "success"}
> Revise cipher suites exposed by Elytron
> ---------------------------------------
>
> Key: ELY-1607
> URL: https://issues.jboss.org/browse/ELY-1607
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Affects Versions: 1.4.0.Final
> Reporter: Martin Choma
> Assignee: Justin Cook
> Priority: Blocker
> Fix For: 1.4.1.CR1
>
>
> I know there have been discussed earlier we should revise/update database and defaults regularly.
> Checking few ciphersuites from java cipher suite list [1]. I have noticed:
> * Elytron is missing CHACHA20 variants introduced in rfc 7905
> * missing ciphersuites from RFC 6209
> * ...
> Please revise content of MechanismDatabase.properties
> [1] https://docs.oracle.com/javase/10/docs/specs/security/standard-names.html...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2734) [Guided Decision Table] - Zooming
by Matthew Stevens (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2734?page=com.atlassian.jira.plugi... ]
Matthew Stevens commented on DROOLS-2734:
-----------------------------------------
[~uxdlc] [~roger600]
> [Guided Decision Table] - Zooming
> ---------------------------------
>
> Key: DROOLS-2734
> URL: https://issues.jboss.org/browse/DROOLS-2734
> Project: Drools
> Issue Type: Story
> Components: Guided Decision Table Editor
> Reporter: Matthew Stevens
> Assignee: Michael Anstis
> Labels: UX, UXTeam
>
> In order to improve zoom capabilities, a first priority is to better align current capabilities across the workbench, specifically GDT and Stunner.
> *For GDT*
> Add support for Control click with mouse wheel or trackpad to zoom like Stunner.
> Add keyboard support for Control click with +/- to allow users to cycle through the different zoom levels.
> A long term solution might move these controls to the canvas, add more zoom levels, and add a slider. But aligning things is a good start.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2656) PNGs for the toolbox icons for the different connector types.
by Brian Dellascio (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2656?page=com.atlassian.jira.plugi... ]
Brian Dellascio commented on DROOLS-2656:
-----------------------------------------
[~manstis] Do all of the palette icons need toolbox versions or just the three you're showing in the screen capture?
> PNGs for the toolbox icons for the different connector types.
> -------------------------------------------------------------
>
> Key: DROOLS-2656
> URL: https://issues.jboss.org/browse/DROOLS-2656
> Project: Drools
> Issue Type: Sub-task
> Reporter: Liz Clayton
> Assignee: Brian Dellascio
> Labels: IconRequest, UX, UXTeam, VisualDesign, drools-tools
> Attachments: DROOLS-2656.png, association_toolbox.png, association_toolbox.svg, authority_requirement_toolbox.png, authority_requirement_toolbox.svg, edit.svg, info_requirement_toolbox.png, info_requirement_toolbox.svg, knowledge_requirement_toolbox.png, knowledge_requirement_toolbox.svg, toolbox_icons.png
>
>
> PNGs for the toolbox icons for the different connector types.
> Their appearance can be seen in https://www.omg.org/spec/DMN/1.1/PDF (page 30, "Association", "Information Requirement", "Knowledge Requirement" and "Authority Requirement"). They'll only be used as icons on the toolbox (see screenshot attached). Could you please also remind me of the BAPL for the new "Node" SVGs (I'll need to make PNGs of those too for the same "toolbox" purpose.. unless UX have a tool to convert SVG to PNG?)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2734) [Guided Decision Table] - Zooming
by Matthew Stevens (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2734?page=com.atlassian.jira.plugi... ]
Matthew Stevens updated DROOLS-2734:
------------------------------------
Description:
In order to improve zoom capabilities, a first priority is to better align current capabilities across the workbench, specifically GDT and Stunner.
*For GDT*
# Add support for Control click with mouse wheel or trackpad to zoom like Stunner.
# Add keyboard support for Control click with +/- to allow users to cycle through the different zoom levels.
A long term solution might move these controls to the canvas, add more zoom levels, and add a slider. But aligning things is a good start.
was:
In order to improve zoom capabilities, a first priority is to better align current capabilities across the workbench, specifically GDT and Stunner.
*For GDT*
Add support for Control click with mouse wheel or trackpad to zoom like Stunner.
Add keyboard support for Control click with +/- to allow users to cycle through the different zoom levels.
A long term solution might move these controls to the canvas, add more zoom levels, and add a slider. But aligning things is a good start.
> [Guided Decision Table] - Zooming
> ---------------------------------
>
> Key: DROOLS-2734
> URL: https://issues.jboss.org/browse/DROOLS-2734
> Project: Drools
> Issue Type: Story
> Components: Guided Decision Table Editor
> Reporter: Matthew Stevens
> Assignee: Michael Anstis
> Labels: UX, UXTeam
>
> In order to improve zoom capabilities, a first priority is to better align current capabilities across the workbench, specifically GDT and Stunner.
> *For GDT*
> # Add support for Control click with mouse wheel or trackpad to zoom like Stunner.
> # Add keyboard support for Control click with +/- to allow users to cycle through the different zoom levels.
> A long term solution might move these controls to the canvas, add more zoom levels, and add a slider. But aligning things is a good start.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2734) [Guided Decision Table] - Zooming
by Matthew Stevens (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2734?page=com.atlassian.jira.plugi... ]
Matthew Stevens updated DROOLS-2734:
------------------------------------
Labels: UX UXTeam (was: )
> [Guided Decision Table] - Zooming
> ---------------------------------
>
> Key: DROOLS-2734
> URL: https://issues.jboss.org/browse/DROOLS-2734
> Project: Drools
> Issue Type: Story
> Components: Guided Decision Table Editor
> Reporter: Matthew Stevens
> Assignee: Michael Anstis
> Labels: UX, UXTeam
>
> In order to improve zoom capabilities, a first priority is to better align current capabilities across the workbench, specifically GDT and Stunner.
> *For GDT*
> Add support for Control click with mouse wheel or trackpad to zoom like Stunner.
> Add keyboard support for Control click with +/- to allow users to cycle through the different zoom levels.
> A long term solution might move these controls to the canvas, add more zoom levels, and add a slider. But aligning things is a good start.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2734) [Guided Decision Table] - Zooming
by Matthew Stevens (JIRA)
Matthew Stevens created DROOLS-2734:
---------------------------------------
Summary: [Guided Decision Table] - Zooming
Key: DROOLS-2734
URL: https://issues.jboss.org/browse/DROOLS-2734
Project: Drools
Issue Type: Story
Components: Guided Decision Table Editor
Reporter: Matthew Stevens
Assignee: Michael Anstis
In order to improve zoom capabilities, a first priority is to better align current capabilities across the workbench, specifically GDT and Stunner.
*For GDT*
Add support for Control click with mouse wheel or trackpad to zoom like Stunner.
Add keyboard support for Control click with +/- to allow users to cycle through the different zoom levels.
A long term solution might move these controls to the canvas, add more zoom levels, and add a slider. But aligning things is a good start.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2728) UX for custom data-types modal
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-2728:
-------------------------------------
[~karreiro] [~manstis]
I think there's a disconnect (most likely mine) but I'll try to articulate again and see where I'm off.
1) It's the same thing as what I proposed originally. I checked with Roger and this widget can offer editable fields (so you could rename or retype data types). The benefit being you have a central location to Create, Edit, Delete/Remove... data types.
!simple.png|thumbnail!
2) I think the structured aspect could be covered using period delineated or likewise string formatting. It might not be 100% ideal, but I think it could be viable.
!structured.png|thumbnail!
I'm thinking the dialog should be used for the Crud actions, and the dropdown be used for simple selection. But maybe I'm still not understanding. ;) Let me know, thanks.
> UX for custom data-types modal
> -------------------------------
>
> Key: DROOLS-2728
> URL: https://issues.jboss.org/browse/DROOLS-2728
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: 2018-07-12 11.41.43 AM.gif, DROOLS-2700.png, First-draft.png, Screen Shot 2018-07-11 at 7.37.12 PM.png, Screen Shot 2018-07-12 at 9.41.34 AM.png, Screen Shot 2018-07-12 at 9.41.40 AM.png, edit.png, grid-alt.png, simple.png, structured.png, triggerDataType.png
>
>
> As a practitioner I want to be able to define Data Types(ItemDefinition) throughDMN editor UI, by:
> - selecting an existing data type
> - creating a new one
> - editing an existing data type
> - deleting an existing data type
> so that I can use this data type to make some decision.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2728) UX for custom data-types modal
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2728:
--------------------------------
Attachment: structured.png
> UX for custom data-types modal
> -------------------------------
>
> Key: DROOLS-2728
> URL: https://issues.jboss.org/browse/DROOLS-2728
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: 2018-07-12 11.41.43 AM.gif, DROOLS-2700.png, First-draft.png, Screen Shot 2018-07-11 at 7.37.12 PM.png, Screen Shot 2018-07-12 at 9.41.34 AM.png, Screen Shot 2018-07-12 at 9.41.40 AM.png, edit.png, grid-alt.png, simple.png, structured.png, triggerDataType.png
>
>
> As a practitioner I want to be able to define Data Types(ItemDefinition) throughDMN editor UI, by:
> - selecting an existing data type
> - creating a new one
> - editing an existing data type
> - deleting an existing data type
> so that I can use this data type to make some decision.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2728) UX for custom data-types modal
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2728:
--------------------------------
Attachment: simple.png
> UX for custom data-types modal
> -------------------------------
>
> Key: DROOLS-2728
> URL: https://issues.jboss.org/browse/DROOLS-2728
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: 2018-07-12 11.41.43 AM.gif, DROOLS-2700.png, First-draft.png, Screen Shot 2018-07-11 at 7.37.12 PM.png, Screen Shot 2018-07-12 at 9.41.34 AM.png, Screen Shot 2018-07-12 at 9.41.40 AM.png, edit.png, grid-alt.png, simple.png, triggerDataType.png
>
>
> As a practitioner I want to be able to define Data Types(ItemDefinition) throughDMN editor UI, by:
> - selecting an existing data type
> - creating a new one
> - editing an existing data type
> - deleting an existing data type
> so that I can use this data type to make some decision.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFWIP-27) [Artemis 2.x Upgrade] Failover does not work with HTTP conncetors/acceptors
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFWIP-27?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry commented on WFWIP-27:
---------------------------------------
FYI on some work I did and let Martyn know about last night:
I was able to do some analysis on this by adding some logging to the WF code that deals with activated/deactivated callbacks from the ActiveMQServer. Responding to those callbacks is what results in HTTPUpgradeService being started and stopped.
When it fails I'm seeing this in the logs, subsequent to activity where WF has gotten a deactivated callback and thus has stopped HTTPUpgradeService:
{code}
21:02:03,944 INFO [org.apache.activemq.artemis.core.server] (Thread-151) AMQ221039: Restarting as Replicating backup server after live restart
{code}
Presence of that message tells me SharedNothingLiveActivation is being called, invoking this code:
{code}
//if we have to many backups kept or are not configured to restart just stop, otherwise restart as a backup
activeMQServer.fail(true);
ActiveMQServerLogger.LOGGER.restartingReplicatedBackupAfterFailback();
// activeMQServer.moveServerData(replicatedPolicy.getReplicaPolicy().getMaxSavedReplicatedJournalsSize());
activeMQServer.setHAPolicy(replicatedPolicy.getReplicaPolicy());
activeMQServer.start();
{code}
It was the activeMQServer.fail(true) call that triggered the preceding deactivation and stop of HTTPUpgradeService. The problem is that call also results in ActiveMQServerImpl.activateCallbacks being cleared. As a result the ActivateCallback impl that WF has registered is gone and will never be invoked again. So WF does not get notified when the ActiveMQServer activates again and does not start the HTTPUpgradeService.
This clearing of ActiveMQServerImpl.activateCallbacks is not done in Artemis 1.5.5 so we don't see the problem there.
I won't comment re: possible solutions as that is better left to Martyn/Jeff/other experts looking at this.
> [Artemis 2.x Upgrade] Failover does not work with HTTP conncetors/acceptors
> ---------------------------------------------------------------------------
>
> Key: WFWIP-27
> URL: https://issues.jboss.org/browse/WFWIP-27
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis
> Reporter: Erich Duda
> Assignee: Jeff Mesnil
> Priority: Blocker
> Labels: activemq, feature-branch-blocker
> Attachments: clients.log, server1.log, server2.log, standalone-full-ha.xml, standalone-full-ha.xml, test.log
>
>
> Failover does not work with HTTP connectors/acceptors.
> *Scenario:*
> # There are two Wildfly servers configured as Live-Backup pair
> # There is one JMS producer and one JMS receiver which sends/receives messages
> # Live server is several times killed and restarted.
> *Expectation:* Always when the Live server is killed or restarted, clients do failover or failback.
> *Reality*: Sometimes happens that clients don't do failover.
> *Users impact:* One of basics feature of HA, failover, does not work properly.
> *Blocker* priority was set because this is regression against previous releases of Wildfly.
> *Detail description of issue*
> In the trace logs it can be seen that clients send HTTP handshake request to active backup, but the handshake fails. All checks (and logs) say that the backup is active in this time period. I tried to run the test with Netty connectors/acceptors and I didn't see this issue.
> {code:title=Backup log}
> 07:52:47,856 WARN [org.apache.activemq.artemis.core.server] (Thread-2 (ActiveMQ-IO-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@1f01f347)) AMQ222029: Could not locate page transaction 3 995, ignoring message on position PagePositionImpl [pageNr=2, messageNr=55, recordID=-1] on address=jms.queue.testQueue queue=jms.queue.testQueue
> 07:52:47,856 WARN [org.apache.activemq.artemis.core.server] (Thread-2 (ActiveMQ-IO-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@1f01f347)) AMQ222029: Could not locate page transaction 3 995, ignoring message on position PagePositionImpl [pageNr=2, messageNr=56, recordID=-1] on address=jms.queue.testQueue queue=jms.queue.testQueue
> 07:52:47,863 INFO [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=null) AMQ221005: Deleting pending large message as it was not completed: Pair[a=2147485068, b=2147485067]
> 07:52:47,863 INFO [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=null) AMQ221005: Deleting pending large message as it was not completed: Pair[a=2147485076, b=2147485075]
> 07:52:47,864 INFO [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=null) AMQ221005: Deleting pending large message as it was not completed: Pair[a=2147484450, b=2147484449]
> 07:52:47,864 INFO [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=null) AMQ221005: Deleting pending large message as it was not completed: Pair[a=2147485072, b=2147485071]
> 07:52:47,864 INFO [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=null) AMQ221005: Deleting pending large message as it was not completed: Pair[a=2147484454, b=2147484453]
> 07:52:47,866 WARN [org.apache.activemq.artemis.core.client] (activemq-discovery-group-thread-dg-group1) AMQ212034: There are more than one servers on the network broadcasting the same node id. You will see this message exactly once (per node) if a node is restarted, in which case it can be safely ignored. But if it is logged continuously it means you really do have more than one node on the same network active concurrently with the same node id. This could occur if you have a backup node active at the same time as its live node. nodeID=0dee81c9-2d9d-11e8-ba3f-cc3d825f79a4
> 07:52:47,867 INFO [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=null) AMQ221007: Server is now live
> {code}
> {code:title=Clients log}
> 07:52:49,274 Thread-80 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector:726] Remote destination: localhost/127.0.0.1:9080
> 07:52:49,274 Thread-79 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl:1040] Connector towards NettyConnector [host=localhost, port=8080, httpEnabled=false, httpUpgradeEnabled=true, useServlet=false, servletPath=/messaging/ActiveMQServlet, sslEnabled=false, useNio=true, activemqServerName=default, httpUpgradeEndpoint=acceptor] failed
> 07:52:49,275 Thread-79 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl:1081] Trying backup config = TransportConfiguration(name=connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEndpoint=acceptor&activemqServerName=default&httpUpgradeEnabled=true&port=9080&host=localhost
> 07:52:49,275 Thread-79 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector:447] Connector NettyConnector [host=localhost, port=9080, httpEnabled=false, httpUpgradeEnabled=true, useServlet=false, servletPath=/messaging/ActiveMQServlet, sslEnabled=false, useNio=true, activemqServerName=default, httpUpgradeEndpoint=acceptor] using native epoll
> 07:52:49,275 Thread-80 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector:797] Sending HTTP request DefaultHttpRequest(decodeResult: success, version: HTTP/1.1)
> GET HTTP/1.1
> host: localhost
> upgrade: activemq-remoting
> connection: upgrade
> activemqServerName: default
> httpUpgradeEndpoint: acceptor
> Sec-ActiveMQRemoting-Key: QWV3bCfgh75NjWH3pZV5Ew==
> 07:52:49,275 Thread-79 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector:601] AMQ211002: Started EPOLL Netty Connector version 4.1.16.Final to localhost:9080
> 07:52:49,275 Thread-79 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector:726] Remote destination: localhost/127.0.0.1:9080
> 07:52:49,276 Thread-79 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector:797] Sending HTTP request DefaultHttpRequest(decodeResult: success, version: HTTP/1.1)
> GET HTTP/1.1
> host: localhost
> upgrade: activemq-remoting
> connection: upgrade
> activemqServerName: default
> httpUpgradeEndpoint: acceptor
> Sec-ActiveMQRemoting-Key: P9xBwRk1eZP5QjDWjqYuIg==
> 07:52:49,276 Thread-2 (ActiveMQ-client-netty-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector$HttpUpgradeHandler:876] Received msg=DefaultHttpResponse(decodeResult: success, version: HTTP/1.1)
> HTTP/1.1 200 OK
> Connection: keep-alive
> Last-Modified: Thu, 22 Mar 2018 06:47:03 GMT
> Content-Length: 2426
> Content-Type: text/html
> Accept-Ranges: bytes
> Date: Thu, 22 Mar 2018 06:52:49 GMT
> 07:52:49,276 Thread-2 (ActiveMQ-client-netty-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector$HttpUpgradeHandler:903] AMQ214023: HTTP Handshake failed, received DefaultHttpResponse(decodeResult: success, version: HTTP/1.1)
> HTTP/1.1 200 OK
> Connection: keep-alive
> Last-Modified: Thu, 22 Mar 2018 06:47:03 GMT
> Content-Length: 2426
> Content-Type: text/html
> Accept-Ranges: bytes
> Date: Thu, 22 Mar 2018 06:52:49 GMT
> 07:52:49,276 Thread-2 (ActiveMQ-client-netty-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector$HttpUpgradeHandler:876] Received msg=DefaultHttpContent(data: PooledSlicedByteBuf(ridx: 0, widx: 829, cap: 829/829, unwrapped: PooledUnsafeDirectByteBuf(ridx: 1024, widx: 1024, cap: 1024)), decoderResult: success)
> 07:52:49,276 Thread-2 (ActiveMQ-client-netty-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector$HttpUpgradeHandler:903] AMQ214023: HTTP Handshake failed, received DefaultHttpContent(data: PooledSlicedByteBuf(ridx: 0, widx: 829, cap: 829/829, unwrapped: PooledUnsafeDirectByteBuf(ridx: 1024, widx: 1024, cap: 1024)), decoderResult: success)
> 07:52:49,277 Thread-80 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl:1040] Connector towards NettyConnector [host=localhost, port=9080, httpEnabled=false, httpUpgradeEnabled=true, useServlet=false, servletPath=/messaging/ActiveMQServlet, sslEnabled=false, useNio=true, activemqServerName=default, httpUpgradeEndpoint=acceptor] failed
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years