[JBoss JIRA] Created: (JBRULES-2244) MVEL raising errors for declared types when there is a package import (import x.y.x.*)
by Edson Tirelli (JIRA)
MVEL raising errors for declared types when there is a package import (import x.y.x.*)
--------------------------------------------------------------------------------------
Key: JBRULES-2244
URL: https://jira.jboss.org/jira/browse/JBRULES-2244
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler, drools-core
Affects Versions: 5.0.1.FINAL, 5.0.0.FINAL
Reporter: Edson Tirelli
Assignee: Edson Tirelli
Fix For: 5.1.0.M1
The following DRL:
===================================================
package org.drools.examples.broker
import org.drools.examples.broker.model.*;
declare Statistics
symbol : String @key()
average : double
end
rule "Setup statistics"
when
$c : Company( $s : symbol )
not( Statistics( symbol == $s ) )
then
Statistics s = new Statistics();
s.symbol = $s;
insert( s );
end
===================================================
Generates the error:
-----------------------------
BuildError: Unable to build expression for 'consequence': Failed to compile: 1 compilation error(s):
- (1,10) unqualified type in strict mode for: Statistics ' Statistics s = new Statistics();
s.symbol = $s;
insert( s );
' broker.drl drools-examples-fusion/src/main/rules line 42 Drools Error
-----------------------------
But if we change the import to:
===================================================
import org.drools.examples.broker.model.Company
import org.drools.examples.broker.model.StockTick
import org.drools.examples.broker.model.SuddenDropEvent
===================================================
Everything works just fine.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] (AS7-4276) setting default-interface to crap makes AS completely non-responsive
by Heiko Rupp (JIRA)
Heiko Rupp created AS7-4276:
-------------------------------
Summary: setting default-interface to crap makes AS completely non-responsive
Key: AS7-4276
URL: https://issues.jboss.org/browse/AS7-4276
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.1.Final
Reporter: Heiko Rupp
Assignee: Brian Stansberry
[standalone@localhost:9999 socket-binding-group=standard-sockets] /:read-children-names(type=interface)
'type' is not found among the supported properties: [child-type]
[standalone@localhost:9999 socket-binding-group=standard-sockets] /:read-children-names(child-type=interface)
{
"outcome" => "success",
"result" => [
"management",
"public",
"unsecure"
]
}
[standalone@localhost:9999 socket-binding-group=standard-sockets] :write-attribute(name=default-interface,value=non-existing-crap)
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
[standalone@localhost:9999 socket-binding-group=standard-sockets] /:reload
{
"outcome" => "success",
"response-headers" => {"process-state" => "reload-required"}
}
[standalone@localhost:9999 socket-binding-group=standard-sockets] :read-attribute(name=default-interface)
Failed to perform read-operation-description to validate the request: java.net.ConnectException: JBAS012144: Could not connect to remote://localhost:9999. The connection timed out
console says:
17:27:25,358 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.network.non-existing-crap (missing) dependents: [service jboss.socket-binding-manager]
17:27:25,366 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.0.0.Beta1 (AS 7.1.0.Final-redhat-1) started (with errors) in 5676ms - Started 116 of 206 services (43 services failed or missing dependencies, 46 services are passive or on-demand)
No ports are open. User has to shut down the server, edit standalone.xml and try again.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] (JBRULES-3403) drools-camel-server-5.3.x.Final.war - strict web application container complains about web.xml
by Nicholas DiPiazza (JIRA)
Nicholas DiPiazza created JBRULES-3403:
------------------------------------------
Summary: drools-camel-server-5.3.x.Final.war - strict web application container complains about web.xml
Key: JBRULES-3403
URL: https://issues.jboss.org/browse/JBRULES-3403
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-camel
Affects Versions: 5.3.1.Final, 5.3.0.Final
Environment: Problem reproduces in WebLogic 10.x, maybe more?
Reporter: Nicholas DiPiazza
Assignee: Mark Proctor
Priority: Minor
Seems like "strict" J2EE containers require the <servlet>'s <display-name> to come before <servlet-name>, in particular WebLogic requires this.
If this:
<servlet>
<servlet-name>CXFServlet</servlet-name>
<display-name>CXF Servlet</display-name>
<servlet-class>
org.apache.cxf.transport.servlet.CXFServlet
</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
were changed to this:
<servlet>
<display-name>CXF Servlet</display-name>
<servlet-name>CXFServlet</servlet-name>
<servlet-class>
org.apache.cxf.transport.servlet.CXFServlet
</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
the 5.3.0.Final and 5.3.1.Final drools-camel war files would be one step towards deploying with no changes out-of-the-box on WebLogic 10.x.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] (JBRULES-3268) Support for varargs needed
by Martin A (Created) (JIRA)
Support for varargs needed
--------------------------
Key: JBRULES-3268
URL: https://issues.jboss.org/browse/JBRULES-3268
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-core
Affects Versions: 5.3.0.Final
Reporter: Martin A
Assignee: Mark Proctor
Priority: Minor
I have a method such as:
/*
* determines if any of the events passed as parameter has occurred
*/
public boolean hasAnyEventOccurred(String... events) {
for (String s : events) {
if (hasEventOccurred(s)) {
return true;
}
}
return false;
}
However in rules I can't call it like that:
hasAnyEventOccurred("event1", "event2", "event3"), I have to workaround as so: hasAnyEventOccurred(new String[] {"event1", "event2", "event3"})
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] Created: (JBRULES-1801) drools-ant-4.0.7, DroolsCompilerAntTask, classloader mixup leads to ClassCastException if drools-compiler.jar part of classpathref
by Juergen none (JIRA)
drools-ant-4.0.7, DroolsCompilerAntTask, classloader mixup leads to ClassCastException if drools-compiler.jar part of classpathref
----------------------------------------------------------------------------------------------------------------------------------
Key: JBRULES-1801
URL: https://jira.jboss.org/jira/browse/JBRULES-1801
Project: JBoss Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-ant
Affects Versions: 4.0.7
Reporter: Juergen none
Assignee: Mark Proctor
drools-4.0.7:
Original error in build.xml:
/home/juergen/workspace/eclipse/kusss-dev/build.xml:777: RuleBaseTask failed: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java'
Traceback to:
org.drools.compiler.PackageBuilderConfiguration, line 154+:
Class cls = classLoader.loadClass( dialectClass );
DialectConfiguration dialectConf = (DialectConfiguration) cls.newInstance();
cls is org.drools.rule.builder.dialect.java.JavaDialectConfiguration, but loaded via classloader given in drools compile ant task property classpathref, while DialectConfiguration is loaded via ant tool classpath used for taskdef
-->
java.lang.ClassCastException: org.drools.rule.builder.dialect.java.JavaDialectConfiguration
interim fix:
make sure drools-compiler.jar is not in classpath of classloaderref
suggested fix:
Class cls = DialectConfiguration.class.getClassLoader().loadClass( dialectClass );
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] (AS7-4214) Operation rolled back using rollback-across-groups rollout plan returns success
by Dominik Pospisil (JIRA)
Dominik Pospisil created AS7-4214:
-------------------------------------
Summary: Operation rolled back using rollback-across-groups rollout plan returns success
Key: AS7-4214
URL: https://issues.jboss.org/browse/AS7-4214
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.2.Final
Reporter: Dominik Pospisil
Assignee: Brian Stansberry
If there are multiple server groups involved in management operation and one group fails and the rollback of the other groups is forced by using rollback-across-groups rollout plan the operation still return success. I think that in such situation the operation should return failure as the operation is not executed on any of the servers.
Example of the outcome of a operation which failed on main-one and main-three and was rolled back on main-two and test-one:
[CLI-out] {
[CLI-out] "outcome" => "success",
[CLI-out] "result" => undefined,
[CLI-out] "server-groups" => {
[CLI-out] "main-server-group" => {
[CLI-out] "main-one" => {
[CLI-out] "host" => "master",
[CLI-out] "response" => {
[CLI-out] "outcome" => "failed",
[CLI-out] "failure-description" => {"JBAS014671: Failed services" => {"jboss.web.connector.test-http" => "org.jboss.msc.service.StartException in service jboss.web.connector.test-http: JBAS018007: Error starting web connector"}},
[CLI-out] "rolled-back" => true,
[CLI-out] "response-headers" => {"process-state" => "restart-required"}
[CLI-out] }
[CLI-out] },
[CLI-out] "main-two" => {
[CLI-out] "host" => "master",
[CLI-out] "response" => {
[CLI-out] "outcome" => "failed",
[CLI-out] "rolled-back" => true
[CLI-out] }
[CLI-out] },
[CLI-out] "main-three" => {
[CLI-out] "host" => "slave",
[CLI-out] "response" => {
[CLI-out] "outcome" => "failed",
[CLI-out] "result" => undefined,
[CLI-out] "failure-description" => {"JBAS014671: Failed services" => {"jboss.web.connector.test-http" => "org.jboss.msc.service.StartException in service jboss.web.connector.test-http: JBAS018007: Error starting web connector"}},
[CLI-out] "rolled-back" => true
[CLI-out] }
[CLI-out] }
[CLI-out] },
[CLI-out] "test-server-group" => {"test-one" => {
[CLI-out] "host" => "master",
[CLI-out] "response" => {
[CLI-out] "outcome" => "failed",
[CLI-out] "rolled-back" => true
[CLI-out] }
[CLI-out] }}
[CLI-out] }
[CLI-out] }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] Created: (JBRULES-2384) Unable to process deployment descriptor for context'/drools-server'
by Megha Shetty (JIRA)
Unable to process deployment descriptor for context'/drools-server'
-------------------------------------------------------------------
Key: JBRULES-2384
URL: https://jira.jboss.org/jira/browse/JBRULES-2384
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: All
Environment: windows
Reporter: Megha Shetty
Assignee: Mark Proctor
I am getting the following error when i am trying to deploy drools-server.war through jboss.
Unable to process deployment descriptor for context'/drools-server'
Following is the complete log when i am starting the jboss server
JAVA_HOME is not set. Unexpected results may occur.
Set JAVA_HOME to the directory of your local JDK to avoid this message.
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: E:\Eclipse Europa\jboss-4.2.3.GA
JAVA: java
JAVA_OPTS: -Dprogram.name=run.bat -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcIn
terval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
CLASSPATH: E:\Eclipse Europa\jboss-4.2.3.GA\bin\run.jar
===============================================================================
14:35:43,295 INFO [Server] Starting JBoss (MX MicroKernel)...
14:35:43,295 INFO [Server] Release ID: JBoss [Trinity] 4.2.3.GA (build: SVNTag=
JBoss_4_2_3_GA date=200807181417)
14:35:43,295 INFO [Server] Home Dir: E:\Eclipse Europa\jboss-4.2.3.GA
14:35:43,295 INFO [Server] Home URL: file:/E:/Eclipse Europa/jboss-4.2.3.GA/
14:35:43,295 INFO [Server] Patch URL: null
14:35:43,295 INFO [Server] Server Name: default
14:35:43,295 INFO [Server] Server Home Dir: E:\Eclipse Europa\jboss-4.2.3.GA\se
rver\default
14:35:43,311 INFO [Server] Server Home URL: file:/E:/Eclipse Europa/jboss-4.2.3
.GA/server/default/
14:35:43,311 INFO [Server] Server Log Dir: E:\Eclipse Europa\jboss-4.2.3.GA\ser
ver\default\log
14:35:43,311 INFO [Server] Server Temp Dir: E:\Eclipse Europa\jboss-4.2.3.GA\se
rver\default\tmp
14:35:43,311 INFO [Server] Root Deployment Filename: jboss-service.xml
14:35:43,482 INFO [ServerInfo] Java version: 1.6.0,Sun Microsystems Inc.
14:35:43,482 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.6.0-b105,S
un Microsystems Inc.
14:35:43,498 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
14:35:43,857 INFO [Server] Core system initialized
14:35:45,670 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083
/
14:35:45,670 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour
ce:jboss-log4j.xml
14:35:46,513 INFO [TransactionManagerService] JBossTS Transaction Service (JTA
version) - JBoss Inc.
14:35:46,513 INFO [TransactionManagerService] Setting up property manager MBean
and JMX layer
14:35:46,701 INFO [TransactionManagerService] Starting recovery manager
14:35:46,748 INFO [TransactionManagerService] Recovery manager started
14:35:46,748 INFO [TransactionManagerService] Binding TransactionManager JNDI R
eference
14:35:50,263 INFO [EJB3Deployer] Starting java:comp multiplexer
14:35:51,607 INFO [NativeServerConfig] JBoss Web Services - Native
14:35:51,622 INFO [NativeServerConfig] jbossws-3.0.1-native-2.0.4.GA (build=200
803312044)
14:35:52,466 INFO [Embedded] Catalina naming disabled
14:35:52,575 INFO [AprLifecycleListener] The Apache Tomcat Native library which
allows optimal performance in production environments was not found on the java
.library.path: C:\WINDOWS\system32;.;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32
;C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
14:35:52,607 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0
.1-8080
14:35:52,607 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-80
09
14:35:52,607 INFO [Catalina] Initialization processed in 147 ms
14:35:52,607 INFO [StandardService] Starting service jboss.web
14:35:52,607 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1.GA
14:35:52,638 INFO [Catalina] Server startup in 24 ms
14:35:52,794 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-w
eb.deployer/ROOT.war/
14:35:53,560 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/
http-invoker.sar/invoker.war/
14:35:53,669 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../deploy/
jbossws.sar/jbossws-context.war/
14:35:53,732 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../
deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
14:35:54,153 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../dep
loy/management/console-mgr.sar/web-console.war/
14:35:54,513 INFO [MailService] Mail Service bound to java:/Mail
14:35:54,669 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jboss-ha-local-jdbc.rar
14:35:54,763 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jboss-ha-xa-jdbc.rar
14:35:54,856 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jboss-local-jdbc.rar
14:35:54,935 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jboss-xa-jdbc.rar
14:35:55,544 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jms/jms-ra.rar
14:35:55,716 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/mail-ra.rar
14:35:55,903 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/quartz-ra.rar
14:35:55,903 INFO [QuartzResourceAdapter] start quartz!!!
14:35:55,950 INFO [SimpleThreadPool] Job execution threads will use class loade
r of thread: main
14:35:55,950 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
14:35:55,966 INFO [RAMJobStore] RAMJobStore initialized.
14:35:55,966 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzSchedule
r' initialized from default resource file in Quartz package: 'quartz.properties'
14:35:55,966 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
14:35:55,966 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUS
TERED started.
14:35:56,966 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb
oss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
14:35:57,200 INFO [A] Bound to JNDI name: queue/A
14:35:57,200 INFO [B] Bound to JNDI name: queue/B
14:35:57,200 INFO [C] Bound to JNDI name: queue/C
14:35:57,200 INFO [D] Bound to JNDI name: queue/D
14:35:57,200 INFO [ex] Bound to JNDI name: queue/ex
14:35:57,216 INFO [testTopic] Bound to JNDI name: topic/testTopic
14:35:57,216 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
14:35:57,216 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
14:35:57,216 INFO [testQueue] Bound to JNDI name: queue/testQueue
14:35:57,231 INFO [UILServerILService] JBossMQ UIL service available at : /127.
0.0.1:8093
14:35:57,263 INFO [DLQ] Bound to JNDI name: queue/DLQ
14:35:57,341 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb
oss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
14:35:57,794 INFO [TomcatDeployer] deploy, ctxPath=/drools-guvnor, warUrl=.../d
eploy/drools-guvnor.war/
14:36:08,965 INFO [TomcatDeployer] deploy, ctxPath=/drools-server, warUrl=.../d
eploy/drools-server.war/
14:36:09,012 WARN [config] Unable to process deployment descriptor for context
'/drools-server'
14:36:09,371 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../dep
loy/jmx-console.war/
14:36:09,496 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8
080
14:36:09,512 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
14:36:09,512 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBos
s_4_2_3_GA date=200807181417)] Started in 26s:201ms
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months