[JBoss JIRA] Created: (JBAS-9127) H2 Datasource fails in domain mode
by Brian Stansberry (JIRA)
H2 Datasource fails in domain mode
----------------------------------
Key: JBAS-9127
URL: https://issues.jboss.org/browse/JBAS-9127
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Domain Management, JCA service
Reporter: Brian Stansberry
Fix For: 7.0.0.Beta2
[Server:server-one] 14:20:07,644 ERROR [org.jboss.as] (MSC service thread 1-3) JBoss AS 7.0.0.Beta2 "(TBD)" started (with errors) in 3449ms - Started 77 of 104 services (2 services failed or missing dependencies, 24 services are passive or on-demand)
[Server:server-one] Services missing dependencies:
[Server:server-one] service jboss.data-source.reference-factory.java:/H2DS
[Server:server-one] service jboss.naming.context.java.java:/H2DS
Partly this is because this is missing from domain.xml:
<drivers>
<driver module="com.h2database.h2"/>
</drivers>
But when I add that the server's don't complete startup (i.e. the server started messages are never logged) and when I ctrl-c stop the process controller, the same messages get logged.
I suspect there is a problem with the DESCRIBE operation handler.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (JBRULES-2931) Regression: unqualified type in strict mode error
by Laird Nelson (JIRA)
Regression: unqualified type in strict mode error
-------------------------------------------------
Key: JBRULES-2931
URL: https://issues.jboss.org/browse/JBRULES-2931
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.2.0.M1
Reporter: Laird Nelson
Assignee: Mark Proctor
This (stupid) rule:
rule "Testing contains"
dialect "mvel"
when
Response( $answerSelections : answerSelections )
AnswerSelection( answer.ID in (2, 3) )
# AnswerSelection( answer.ID == 2 || == 3 )
# AnswerSelection( answer.ID == 2 || answer.ID == 3 )
then
System.out.println("Testing contains activated")
end
...produces this error message:
Unable to Analyse Expression answer.ID == 2 || answer.ID == 3:
[Error: Failed to compile: 1 compilation error(s):
- (1,9) unqualified type in strict mode for: ID]
[Near : {... Unknown ....}]
^
[Line: 1, Column: 0] : [Rule name='Testing contains']
Response has a getAnswerSelections() method that returns a Collection type. AnswerSelection has a getAnswer() method that returns an Answer. Answer has a getID() method that returns an int.
This rule compiled fine under Drools 5.1.1 and 5.2.0.M1 and fails under 5.2.0-SNAPSHOT.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (JBAS-9111) SocketBinding multicast-address being parsed as integer
by Paul Ferraro (JIRA)
SocketBinding multicast-address being parsed as integer
-------------------------------------------------------
Key: JBAS-9111
URL: https://issues.jboss.org/browse/JBAS-9111
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Domain Management
Affects Versions: 7.0.0.Beta1
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Priority: Critical
Fix For: 7.0.0.Beta2
A missing break in a switch/case statement is causing the multicast-address attribute of a domain.xml socket-binding to be reparsed (i.e. it falls through to the following case condition) as an integer.
Where are the domain.xml/standalone.xml parsing unit tests?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (JBRULES-2672) Error while parsing xml with <and-constraint-connective> within <pattern>
by Veit Guna (JIRA)
Error while parsing xml with <and-constraint-connective> within <pattern>
-------------------------------------------------------------------------
Key: JBRULES-2672
URL: https://jira.jboss.org/browse/JBRULES-2672
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler
Affects Versions: 5.1.0.FINAL
Environment: Jboss 5.1.0, Drools 5.1.0, Jdk 1.6.0_14
Reporter: Veit Guna
Assignee: Mark Proctor
Hi.
I'm using drools 5.1.0 together with .xdrl files. I encountered a possible bug in the AndHandler class when
parsing the following .xdrl file:
--cut here--
<dro:pattern object-type="EMail">
<dro:and-constraint-connective>
<dro:field-constraint field-name="foo">
<dro:literal-restriction evaluator="!=" value="null"/>
</dro:field-constraint>
<dro:field-constraint field-name="foo.toLowerCase">
<dro:literal-restriction evaluator="==" value="test"/>
</dro:field-constraint>
</dro:and-constraint-connective>
</dro:pattern>
--cut here--
Parsing this seems to fail when adding the package from xml:
Caused by: org.drools.compiler.DroolsParserException: org.xml.sax.SAXParseException: <and-constraint-connective> has an invalid parent element [[Pattern: id=null; objectType=EMail]]
at org.drools.compiler.PackageBuilder.addPackageFromXml(PackageBuilder.java:304)
at org.drools.compiler.PackageBuilder.addKnowledgeResource(PackageBuilder.java:468)
... 142 more
According to the .xsd (4.0) this should be no problem. Looking at the OrHandler it seems that simply the
PatternDescr is missing from the validParents.
Also tried to disable xml validation with:
System.setProperty("drools.schema.validating","false");
but with no luck. So find attached the _very_ complex patch that adds PackageDescr to the AndHandler :).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (JBLOGGING-57) Logic for selecting a provider is too fragile
by Dan Allen (JIRA)
Logic for selecting a provider is too fragile
---------------------------------------------
Key: JBLOGGING-57
URL: https://issues.jboss.org/browse/JBLOGGING-57
Project: JBoss Logging
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.0.0.Beta4-jboss-logging
Reporter: Dan Allen
Assignee: David Lloyd
Fix For: 3.0.0.Beta5-jboss-logging
The logic used to select the logging provider is too fragile. It should never throw an exception while selecting a provider, because JDK logging is guaranteed to be available and should be the fallback choice. When JBoss Logging fails to select a provider, it causes deployment to fail, which violates my rule #1 of a logging framework (don't fail a build because of a failure to setup logging).
The fragile logic is the reason we get JBLOGGING-47.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months