[JBoss JIRA] (DROOLS-1067) Oracle DB issue for findTasksByVariableAndValue
by Karel Suta (JIRA)
Karel Suta created DROOLS-1067:
----------------------------------
Summary: Oracle DB issue for findTasksByVariableAndValue
Key: DROOLS-1067
URL: https://issues.jboss.org/browse/DROOLS-1067
Project: Drools
Issue Type: Bug
Components: kie server
Affects Versions: 6.4.0.Beta2
Environment: Kie server 6.4.0-SNAPSHOT
Database - Oracle 11gR2
Reporter: Karel Suta
Assignee: Maciej Swiderski
Attachments: stacktrace.txt
Tried to run Kie server integration tests against database Oracle 11gR2. Got an error listed as attachment in test UserTaskServiceIntegrationTest.testFindTasksByVariableAndValue() .
Error is thrown when test calls: taskClient.findTasksByVariableAndValue("yoda", "_string", "john is working on it", null, 0, 10)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (DROOLS-1067) Oracle DB issue for findTasksByVariableAndValue
by Karel Suta (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1067?page=com.atlassian.jira.plugi... ]
Karel Suta updated DROOLS-1067:
-------------------------------
Labels: reported-by-qe (was: )
> Oracle DB issue for findTasksByVariableAndValue
> -----------------------------------------------
>
> Key: DROOLS-1067
> URL: https://issues.jboss.org/browse/DROOLS-1067
> Project: Drools
> Issue Type: Bug
> Components: kie server
> Affects Versions: 6.4.0.Beta2
> Environment: Kie server 6.4.0-SNAPSHOT
> Database - Oracle 11gR2
> Reporter: Karel Suta
> Assignee: Maciej Swiderski
> Labels: reported-by-qe
> Attachments: stacktrace.txt
>
>
> Tried to run Kie server integration tests against database Oracle 11gR2. Got an error listed as attachment in test UserTaskServiceIntegrationTest.testFindTasksByVariableAndValue() .
> Error is thrown when test calls: taskClient.findTasksByVariableAndValue("yoda", "_string", "john is working on it", null, 0, 10)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6277) Upgrade JGroups to 3.6.8.Final
by Paul Ferraro (JIRA)
Paul Ferraro created WFLY-6277:
----------------------------------
Summary: Upgrade JGroups to 3.6.8.Final
Key: WFLY-6277
URL: https://issues.jboss.org/browse/WFLY-6277
Project: WildFly
Issue Type: Component Upgrade
Components: Clustering
Affects Versions: 10.0.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Tracking Jira for fixes in JGroups.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6274) Please improve deployment logging
by Rick Wagner (JIRA)
Rick Wagner created WFLY-6274:
---------------------------------
Summary: Please improve deployment logging
Key: WFLY-6274
URL: https://issues.jboss.org/browse/WFLY-6274
Project: WildFly
Issue Type: Feature Request
Reporter: Rick Wagner
Assignee: Jason Greene
Wildfly attempts to deploy mal-formed artifacts and does not provide useful feedback to the user. (In fact, it provides feedback that hints that things are ok, when really they are not.)
As an example, deploying a flawed XML descriptor (targeted at no particular Wildfly subsystem) brings this:
08:30:37,675 INFO [org.jboss.as.server.deployment] (MSC service thread 1-11) JBAS015876: Starting deployment of "bogus.xml" (runtime-name: "bogus.xml")
08:30:38,085 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS015859: Deployed "bogus.xml" (runtime-name : "bogus.xml")
If the user is attempting to make use of a Wildfly subsystem (say Wildlfy-Camel) but has an unacceptable descriptor, no useful feedback is provided. The user will think their application is 'deployed' (as logged) when really it has been ignored.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months