[JBoss JIRA] (DROOLS-831) KIE Execution Server is not able to find the Maven repository
by Roger Martínez (JIRA)
Roger Martínez created DROOLS-831:
-------------------------------------
Summary: KIE Execution Server is not able to find the Maven repository
Key: DROOLS-831
URL: https://issues.jboss.org/browse/DROOLS-831
Project: Drools
Issue Type: Bug
Components: docker images
Affects Versions: 6.2.0.Final
Environment: ALL
Reporter: Roger Martínez
Assignee: Roger Martínez
In a non-Docker installation of the KIE execution server, the user must configure the Maven settings file to specify where the Maven repository for the artifacts is located.
As Docker images are immutable, this configuration must be specified at runtime using environment variables when the container starts.
This feature is not implemented on latest image tag and it's mandatory for being able to use the external Maven repository.
This bug is reported from community feedback:
"I'm trying out the docker images for the workbench-showcase and the execution-showcase. Fresh install. I'm using -p 8080:8080 for the wb and 8081:8080 for the exec. WB runs fine and I can build and deploy the mortgage project. Exec runs fine and I can access using REST. I can register the exec server fine. Mortgage container creates fine. Starting the container produces this error on the exec docker:
987 ERROR [org.kie.server.services.rest.KieServerRestImpl] (default task-5) Error creating container 'Test1' for module 'mortgages:mortgages:0.0.1': java.lang.RuntimeException: Cannot find KieModule: mortgages:mortgages:0.0.1
Should this work out of the box?"
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (WFLY-4847) STOMP logging does not work
by Ville Skyttä (JIRA)
[ https://issues.jboss.org/browse/WFLY-4847?page=com.atlassian.jira.plugin.... ]
Ville Skyttä commented on WFLY-4847:
------------------------------------
With the dependency in place, connection closed warnings do get logged properly:
{code}
19:53:01,495 WARN [org.hornetq.core.protocol.stomp] (Thread-88) HQ222068: connection closed org.hornetq.core.protocol.stomp.StompConnection@51881e0
{code}
...and unsupported version connects get a proper error response:
{code}
$ nc localhost 61613
CONNECT
accept-version:2.0
^@
ERROR
message:HQ339002: Stomp versions not supported: 2.0
version:2.0
content-type:text/plain
Supported protocol version are v1.0 v1.1 v1.2
{code}
> STOMP logging does not work
> ---------------------------
>
> Key: WFLY-4847
> URL: https://issues.jboss.org/browse/WFLY-4847
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 9.0.0.CR2
> Reporter: Ville Skyttä
> Assignee: Jason Greene
>
> STOMP errors do not get logged at all, for example "HQ222068: connection closed ..." on unclean connection close.
> Also, apparently due to the same root cause (or at least fixed by the same fix), for example connecting with an unsupported STOMP version just hangs instead of responding with the ERROR frame.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (WFLY-4847) STOMP logging does not work
by Ville Skyttä (JIRA)
[ https://issues.jboss.org/browse/WFLY-4847?page=com.atlassian.jira.plugin.... ]
Ville Skyttä updated WFLY-4847:
-------------------------------
Description:
STOMP errors do not get logged at all, for example "HQ222068: connection closed ..." on unclean connection close.
Also, apparently due to the same root cause (or at least fixed by the same fix), for example connecting with an unsupported STOMP version just hangs instead of responding with the ERROR frame.
was:
STOMP errors do not get logged at all, for example "HQ222068: connection closed ..." on unclean shutdown.
Also, apparently due to the same root cause (or at least fixed by the same fix), for example connecting with an unsupported STOMP version just hangs instead of responding with the ERROR frame.
> STOMP logging does not work
> ---------------------------
>
> Key: WFLY-4847
> URL: https://issues.jboss.org/browse/WFLY-4847
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 9.0.0.CR2
> Reporter: Ville Skyttä
> Assignee: Jason Greene
>
> STOMP errors do not get logged at all, for example "HQ222068: connection closed ..." on unclean connection close.
> Also, apparently due to the same root cause (or at least fixed by the same fix), for example connecting with an unsupported STOMP version just hangs instead of responding with the ERROR frame.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (WFLY-4847) STOMP logging does not work
by Ville Skyttä (JIRA)
Ville Skyttä created WFLY-4847:
----------------------------------
Summary: STOMP logging does not work
Key: WFLY-4847
URL: https://issues.jboss.org/browse/WFLY-4847
Project: WildFly
Issue Type: Bug
Affects Versions: 9.0.0.CR2
Reporter: Ville Skyttä
Assignee: Jason Greene
STOMP errors do not get logged at all, for example "HQ222068: connection closed ..." on unclean shutdown.
Also, apparently due to the same root cause (or at least fixed by the same fix), for example connecting with an unsupported STOMP version just hangs instead of responding with the ERROR frame.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (WFCORE-785) Improve capability related error messages
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-785?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFCORE-785:
------------------------------------
Fix Version/s: 2.0.0.Beta1
(was: 2.0.0.CR1)
> Improve capability related error messages
> -----------------------------------------
>
> Key: WFCORE-785
> URL: https://issues.jboss.org/browse/WFCORE-785
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: Brian Stansberry
> Fix For: 2.0.0.Beta1
>
>
> When operation handlers request non-existent capabilities, the error messages aren't particularly helpful. For example:
> /"WFLYCTL0158: Operation handler failed: java.lang.IllegalStateException: WFLYCTL0364: Capability 'org.wildfly.data-source.invalid' is unknown."
> This is largely because it's the CapabilityRegistry that throws the exceptions, and it doesn't have much context about why the capability is needed to use in a better error message.
> Likely solutions are:
> 1) If CapabilityRegistryImpl has more context than is being used, look into using it.
> 2) Provide more context to CapabilityRegistry (I don't much like this one; providing parameters to a call only for use in a failure message is smelly to me.)
> 3) Use a custom exception type when the capability is missing, instead of ISE, and have OperationContextImpl catch that and add contextual information.
> I expect 3) is the likely solution.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (WFCORE-785) Improve capability related error messages
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-785:
---------------------------------------
Summary: Improve capability related error messages
Key: WFCORE-785
URL: https://issues.jboss.org/browse/WFCORE-785
Project: WildFly Core
Issue Type: Enhancement
Components: Domain Management
Reporter: Brian Stansberry
Fix For: 2.0.0.CR1
When operation handlers request non-existent capabilities, the error messages aren't particularly helpful. For example:
/"WFLYCTL0158: Operation handler failed: java.lang.IllegalStateException: WFLYCTL0364: Capability 'org.wildfly.data-source.invalid' is unknown."
This is largely because it's the CapabilityRegistry that throws the exceptions, and it doesn't have much context about why the capability is needed to use in a better error message.
Likely solutions are:
1) If CapabilityRegistryImpl has more context than is being used, look into using it.
2) Provide more context to CapabilityRegistry (I don't much like this one; providing parameters to a call only for use in a failure message is smelly to me.)
3) Use a custom exception type when the capability is missing, instead of ISE, and have OperationContextImpl catch that and add contextual information.
I expect 3) is the likely solution.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (WFLY-462) Eliminate the threads subsystem
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-462?page=com.atlassian.jira.plugin.s... ]
Tomaz Cerar resolved WFLY-462.
------------------------------
Fix Version/s: 10.0.0.Alpha4
9.0.0.CR2
(was: 10.0.0.Beta1)
Resolution: Done
Threads subsystem was changed to only run in domain controller to allow support for legacy host controllers management.
there ware additional steps done to make it easier for resources from threads subsystem to be easier reused in other parts of the server
> Eliminate the threads subsystem
> -------------------------------
>
> Key: WFLY-462
> URL: https://issues.jboss.org/browse/WFLY-462
> Project: WildFly
> Issue Type: Task
> Reporter: David Lloyd
> Assignee: Tomaz Cerar
> Fix For: 10.0.0.Alpha4, 9.0.0.CR2
>
>
> The threads subsystem should be eliminated, and instead the individual consuming subsystems should utilize common code from the jboss-as-threads module to define and manage thread pools within their own configuration models.
> Subtasks for affected subsystems.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months