[JBoss JIRA] (DROOLS-832) Logical setters do not work with non-natively traitable beans
by Davide Sottara (JIRA)
Davide Sottara created DROOLS-832:
-------------------------------------
Summary: Logical setters do not work with non-natively traitable beans
Key: DROOLS-832
URL: https://issues.jboss.org/browse/DROOLS-832
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 6.3.0.Beta1, 6.2.0.Final, 6.1.0.Final, 6.0.0.Final, 5.6.0.Final, 5.5.0.Final
Reporter: Davide Sottara
Assignee: Mario Fusco
Fix For: 6.3.0.Beta2
By default, "logical" traitable beans maintain the consistency of a field adding logic to the setters. When using non-natively traitable beans, the additional logic is not invoked
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months
[JBoss JIRA] (DROOLS-831) KIE Execution Server is not able to find the Maven repository
by Roger Martínez (JIRA)
[ https://issues.jboss.org/browse/DROOLS-831?page=com.atlassian.jira.plugin... ]
Roger Martínez edited comment on DROOLS-831 at 6/30/15 3:52 PM:
----------------------------------------------------------------
Problem and workaround:
*****************************
The problem is that the KIE server Docker container does not have the information of the internal Maven repository for the Workbench container. In a non-docker installation, you should create your settings.xml file for the execution server specifying the workbench internal maven repository, so meanwhile, as a workaround, customer can access the KIE server container's shell (by using nsenter command) and write the settings.xml file in the container's filesystem.
NOTE: The settings.xml file created manually following this workaround approach will be removed if you remove that specific KIE server container from you docker host. If will remain as well if you stop and restart it.
was (Author: roger600):
Problem and workaround:
*****************************
The problem is that the KIE server Docker container does not have the information of the internal Maven repository for the Workbench container. In a non-docker installation, you should create your settings.xml file for the execution server specifying the workbench internal maven repository, so meanwhile, as a workaround, customer can access the KIE server container's shell (by using nsenter command) and write the settings.xml file in the container's filesystem.
> 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)
10 years, 5 months
[JBoss JIRA] (DROOLS-831) KIE Execution Server is not able to find the Maven repository
by Roger Martínez (JIRA)
[ https://issues.jboss.org/browse/DROOLS-831?page=com.atlassian.jira.plugin... ]
Roger Martínez commented on DROOLS-831:
---------------------------------------
Problem and workaround:
*****************************
The problem is that the KIE server Docker container does not have the information of the internal Maven repository for the Workbench container. In a non-docker installation, you should create your settings.xml file for the execution server specifying the workbench internal maven repository, so meanwhile, as a workaround, customer can access the KIE server container's shell (by using nsenter command) and write the settings.xml file in the container's filesystem.
> 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)
10 years, 5 months
[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)
10 years, 5 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)
10 years, 5 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)
10 years, 5 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)
10 years, 5 months