[JBoss JIRA] (AS7-3061) Can't create periodic rotating file handler in CLI or console
by Stan Silvert (Created) (JIRA)
Can't create periodic rotating file handler in CLI or console
-------------------------------------------------------------
Key: AS7-3061
URL: https://issues.jboss.org/browse/AS7-3061
Project: Application Server 7
Issue Type: Bug
Components: Logging
Affects Versions: 7.1.0.Beta1b
Reporter: Stan Silvert
Assignee: James Perkins
CLI command:{noformat}
/subsystem=logging/periodic-rotating-file-handler=periodicrotating/:add(name=periodicrotating,level=INFO,file={"path" => "myfoo.log", "relative-to" => "jboss.server.log.dir"})
{noformat}
CLI error:{noformat}
[standalone@localhost:9999 /] /subsystem=logging/periodic-rotating-file-handler=periodicrotating/:add(name=periodicrotating,level=INFO,file={"path" => "myfoo.log", "relat
ive-to" => "jboss.server.log.dir"})
{
"outcome" => "failed",
"failure-description" => {"JBAS014671: Failed services" => {"jboss.logging.handler.periodicrotating" => "org.jboss.msc.service.StartException in service jboss.logging
.handler.periodicrotating: Failed to start service"}},
"rolled-back" => true,
"response-headers" => {"process-state" => "reload-required"}
}
{noformat}
In server console:{noformat}
15:04:29,303 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.logging.handler.periodicrotating: org.jboss.msc.service.S
tartException in service jboss.logging.handler.periodicrotating: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1780) [jboss-msc-1.0.1.GA.jar:]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_29]
Caused by: java.lang.NullPointerException
at java.text.SimpleDateFormat.<init>(SimpleDateFormat.java:493) [:1.6.0_29]
at java.text.SimpleDateFormat.<init>(SimpleDateFormat.java:475) [:1.6.0_29]
at org.jboss.logmanager.handlers.PeriodicRotatingFileHandler.setSuffix(PeriodicRotatingFileHandler.java:119) [jboss-logmanager-1.2.0.GA.jar:]
at org.jboss.as.logging.handlers.file.PeriodicRotatingFileHandlerService.start(PeriodicRotatingFileHandlerService.java:74)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:]
... 3 more
{noformat}
--
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
14 years, 3 months
[JBoss JIRA] (JBRULES-3367) Planner: score calculation with plain old Java
by Geoffrey De Smet (JIRA)
Geoffrey De Smet created JBRULES-3367:
-----------------------------------------
Summary: Planner: score calculation with plain old Java
Key: JBRULES-3367
URL: https://issues.jboss.org/browse/JBRULES-3367
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-planner
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
Provide an plain old java alternative to score calculations, so the user has choice (= freedom):
- A) Drools score calculation (default). Does incremental calculation automatically, without extra code.
- B) Java non-incremental score calculation. Very easy to reuse existing score code, but not fast.
- C) Java incremental score calculation. Requires incremental boilerplate code, but experiments show that in some use cases (with little rules) it can be a 100 times faster than A) with drools 5.3. Note that undo-then and JIT compiling might change that number drastically in future drools versions.
--
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
14 years, 3 months
[JBoss JIRA] (JBRULES-3288) Sliding time window ignored when using @timestamp and pseudo clock
by Colin Webber (Created) (JIRA)
Sliding time window ignored when using @timestamp and pseudo clock
------------------------------------------------------------------
Key: JBRULES-3288
URL: https://issues.jboss.org/browse/JBRULES-3288
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core (fusion)
Affects Versions: 5.3.0.Final
Environment: Mac OSX 10.6.8
Reporter: Colin Webber
Assignee: Mark Proctor
When using a custom @timestamp together with PSEUDO clock, all events are accumulated rather than just those within the window:time period. I have tried using long (millisecond) and java.util.Date without success.
==================================
declare SimpleObject
@role(event)
@timestamp(customTime)
@expires(10m)
end;
rule "honour custom timestamp"
when
$avgVal : Number (longValue > 0) from accumulate ( SimpleObject($valueLng : valueLong ) over window:time (10s) from entry-point "SimpleEP", average ( $valueLng ) )
then
System.out.println("avg: " + $avgVal);
end
---------------------------------------
import java.util.Date;
public class SimpleObject {
private long customTime;
public long valueLong;
public SimpleObject(Date customTime, long valueLong) {
this.customTime = customTime.getTime();
this.valueLong = valueLong;
}
public long getCustomTime() {
return customTime;
}
public void setCustomTime(long customTime) {
this.customTime = customTime;
}
public long getValueLong() {
return valueLong;
}
public void setValueLong(long valueLong) {
this.valueLong = valueLong;
}
}
------------ Trivial Spock/Groovy unit test ----------------
@IgnoreRest
def "should honour custom timestamp"() {
when:
use (TimeCategory) {
def now = new Date()
simpleEp.insert(new SimpleObject(now, 100))
ksession.fireAllRules()
clock.advanceTime( 5, TimeUnit.SECONDS );
ksession.fireAllRules()
simpleEp.insert(new SimpleObject(5.seconds.from.now, 90))
ksession.fireAllRules()
clock.advanceTime( 5, TimeUnit.SECONDS );
ksession.fireAllRules()
simpleEp.insert(new SimpleObject(10.seconds.from.now, 80))
ksession.fireAllRules()
clock.advanceTime( 5, TimeUnit.SECONDS );
ksession.fireAllRules()
simpleEp.insert(new SimpleObject(15.seconds.from.now, 70))
ksession.fireAllRules()
clock.advanceTime( 5, TimeUnit.SECONDS );
ksession.fireAllRules()
simpleEp.insert(new SimpleObject(20.seconds.from.now, 60))
ksession.fireAllRules()
clock.advanceTime( 5, TimeUnit.SECONDS );
ksession.fireAllRules()
simpleEp.insert(new SimpleObject(25.seconds.from.now, 50))
ksession.fireAllRules()
clock.advanceTime( 5, TimeUnit.SECONDS );
ksession.fireAllRules()
}
then:
1 == 1 // no assertions - we're examining the stdout.
}
==================================
OUTPUT (INCORRECT - all values are included for each evalutation):
avg: 100.0
avg: 95.0
avg: 90.0
avg: 85.0
avg: 80.0
avg: 75.0
Note that when commenting out the @timestamp tag the output changes to the following (correct) output:
avg: 100.0
avg: 95.0
avg: 90.0
avg: 85.0
avg: 80.0
avg: 75.0
avg: 70.0
avg: 65.0
avg: 60.0
avg: 55.0
avg: 50.0
Also note that when using the REALTIME clock with Thread.sleep the output is correct.
--
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
14 years, 3 months
[JBoss JIRA] (JBRULES-3336) Could not parse knowledge when using 'not contains' in a parentheses leading a '!'
by Miles Wen (Created) (JIRA)
Could not parse knowledge when using 'not contains' in a parentheses leading a '!'
----------------------------------------------------------------------------------
Key: JBRULES-3336
URL: https://issues.jboss.org/browse/JBRULES-3336
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.3.0.Final
Environment: jdk 1.6u27 drools 5.3.0 final
Reporter: Miles Wen
Assignee: Mark Proctor
This code could not be parsed correctly:
rule "out"
when
Msg(!(set not contains "test"))
then
end
I tried a few simple situations and found that when using 'not contains' operator in a '!' leading parentheses triggers this problem. If no '!' prefixing the parentheses,the program works like a charm...
The example above seemed so stupid(you can use a 'contains' operator instead), but this is the simplest toy example.And this problem would be looked more important if you want to write some logic like this:
Msg(!(set not contains "test" || !bool && string == "hello"))
--
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
14 years, 3 months
[JBoss JIRA] (JBRULES-3342) Incorrect/Misleading Expert Documentation For Drools XML Language
by Justin Holmes (JIRA)
Justin Holmes created JBRULES-3342:
--------------------------------------
Summary: Incorrect/Misleading Expert Documentation For Drools XML Language
Key: JBRULES-3342
URL: https://issues.jboss.org/browse/JBRULES-3342
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-docs-expert
Affects Versions: 5.4.0.Beta1, 5.3.1.Final, 5.2.0.Final, 5.1.1.FINAL, 5.0.1.FINAL
Environment: None - this a documentation issue
Reporter: Justin Holmes
Assignee: Mark Proctor
The Drools XML language "...has not been developed since drools 4.0, and is considered a deprecated feature." However, the docs for 5.x versions of Drools clearly state, "All the features are available with XML that are available to DRL." As such,the docs need to be updated to reflect the current state of the XML language so users are not mislead.
A simple yellow Warning box at the beginning of the XML section stating that the XML hasn't been developed since 4.0 and is consider deprecated will be enough to properly inform users. Removing the "All features..." would be useful as well.
I'm planning to provided a pull request in the next week or so.do
--
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
14 years, 3 months
[JBoss JIRA] (AS7-3755) JSR88 deployment causes errors because of invalid paths
by Wolfgang Knauf (JIRA)
Wolfgang Knauf created AS7-3755:
-----------------------------------
Summary: JSR88 deployment causes errors because of invalid paths
Key: AS7-3755
URL: https://issues.jboss.org/browse/AS7-3755
Project: Application Server 7
Issue Type: Bug
Components: JSR88
Affects Versions: 7.1.0.CR1
Reporter: Wolfgang Knauf
Assignee: Thomas Diesler
I observed two problems when performing JSR88 deployment. Though they are at completely different places, it seems they both have the same root cause: a JSR88 module name, which contains the path to the temp dir, seems to be treated a a file name later.
First observation is this error message when deploying the EAR file attached to #AS7-3474 :
21:24:44,781 ERROR [org.jboss.as.ejb3] (MSC service thread 1-3) JBAS014132: Could not create directory C:\temp\jboss-as-7.1.0.Final-SNAPSHOT\standalone\data\timer-service-data\file:\C:\DOCUME~1\Knuffi\LOCALS~1\Temp\Stateless.StatelessEJB.GeometricModelBean to persist EJB timers.
I don't know whether this breaks something, I just noticed the error message.
And the second problem happened when deploying a small Struts2 sample:
21:23:10,875 FATAL [org.apache.jasper.EmbeddedServletOptions] (MSC service thread 1-4) The scratchDir you specified: C:\temp\jboss-as-7.1.0.Final-SNAPSHOT\standalone\tmp\work\jboss.web\default-host\file:_C:_DOCUME~1_Knuffi_LOCALS~1_Temp_StrutsBasics is unusable.
The path is different, but the problem seems to be the same (here ":" is not removed from the path name). This caused a failed deployment, thus is is really a problem.
I posted the second error plus a small sample (including my famous JSR88 deployer client ;-)) in the JBossWeb forum, but did not receive a reply up to now. See here for the sample: https://community.jboss.org/thread/194841
--
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
14 years, 3 months
[JBoss JIRA] Created: (JBAS-8778) Problem with deployment order of EAR and JMS queues
by Frank Langelage (JIRA)
Problem with deployment order of EAR and JMS queues
---------------------------------------------------
Key: JBAS-8778
URL: https://issues.jboss.org/browse/JBAS-8778
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Deployers, JMS (HornetQ)
Affects Versions: 6.0.0.Final
Reporter: Frank Langelage
Assignee: Ales Justin
Our application deployed as one EAR file contains two MDB.
The queues are defined in $JBOSS_HOME/deploy/hornetq/mbi2e-lafr-sb2000-ipc-hornetq-jms.xml:
<?xml version="1.0" encoding="UTF-8"?>
<configuration xmlns="urn:hornetq"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:hornetq /schema/hornetq-jms.xsd">
<queue name="mbi2e-lafr-sb2000-ipc/MessageDistributorQueue">
<entry name="queue/mbi2e-lafr-sb2000-ipc/MessageDistributorQueue"/>
</queue>
<queue name="mbi2e-lafr-sb2000-ipc/SalesOrderImportQueue">
<entry name="queue/mbi2e-lafr-sb2000-ipc/SalesOrderImportQueue"/>
</queue>
</configuration>
If I first startup JBossAS, already including the queue definitions shown above, and then deploy my ear file everything is fine. No Errors.
But if I bounce and restart the engine after that, with everything deployed, I get Warnings and Errors.
Right after the start of the MDB listening on the 'MessageDistributorQueue' I get this:
11:48:58,754 WARN [HornetQActivation] Failure in HornetQ activation org.hornetq.ra.inflow.HornetQActivationSpec(ra=org.hornetq.ra.HornetQResourceAdapter@1fe97f9 destination=queue/mbi2e-lafr-sb2000-ipc/MessageDistributorQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15): HornetQException[errorCode=105 message=Unable to validate user: null for check type CONSUME for address jms.queue.mbi2e-lafr-sb2000-ipc/MessageDistributorQueue]
at org.hornetq.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:287) [:]
at org.hornetq.core.client.impl.ClientSessionImpl.internalCreateConsumer(ClientSessionImpl.java:1556) [:]
at org.hornetq.core.client.impl.ClientSessionImpl.createConsumer(ClientSessionImpl.java:447) [:]
at org.hornetq.core.client.impl.ClientSessionImpl.createConsumer(ClientSessionImpl.java:392) [:]
at org.hornetq.core.client.impl.DelegatingSession.createConsumer(DelegatingSession.java:201) [:]
at org.hornetq.ra.inflow.HornetQMessageHandler.setup(HornetQMessageHandler.java:165) [:]
at org.hornetq.ra.inflow.HornetQActivation.setup(HornetQActivation.java:291) [:]
at org.hornetq.ra.inflow.HornetQActivation$SetupActivation.run(HornetQActivation.java:573) [:]
at org.jboss.resource.work.WorkWrapper.run(WorkWrapper.java:172) [:6.0.1-SNAPSHOT]
at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33) [:2.0.0.CR7]
at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:801) [:2.0.0.CR7]
at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45) [:2.0.0.CR7]
at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:821) [:2.0.0.CR7]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_23]
at org.jboss.threads.JBossThread.run(JBossThread.java:122) [:2.0.0.CR7]
And then a few more times during the further startup process I see this:
11:49:00,759 INFO [HornetQActivation] Attempting to reconnect org.hornetq.ra.inflow.HornetQActivationSpec(ra=org.hornetq.ra.HornetQResourceAdapter@1fe97f9 destination=queue/mbi2e-lafr-sb2000-ipc/MessageDistributorQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15)
11:49:00,998 ERROR [HornetQActivation] Unable to reconnect org.hornetq.ra.inflow.HornetQActivationSpec(ra=org.hornetq.ra.HornetQResourceAdapter@1fe97f9 destination=queue/mbi2e-lafr-sb2000-ipc/MessageDistributorQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15): HornetQException[errorCode=105 message=Unable to validate user: null for check type CONSUME for address jms.queue.mbi2e-lafr-sb2000-ipc/MessageDistributorQueue]
at org.hornetq.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:287) [:]
at org.hornetq.core.client.impl.ClientSessionImpl.internalCreateConsumer(ClientSessionImpl.java:1556) [:]
at org.hornetq.core.client.impl.ClientSessionImpl.createConsumer(ClientSessionImpl.java:447) [:]
at org.hornetq.core.client.impl.ClientSessionImpl.createConsumer(ClientSessionImpl.java:392) [:]
at org.hornetq.core.client.impl.DelegatingSession.createConsumer(DelegatingSession.java:201) [:]
at org.hornetq.ra.inflow.HornetQMessageHandler.setup(HornetQMessageHandler.java:165) [:]
at org.hornetq.ra.inflow.HornetQActivation.setup(HornetQActivation.java:291) [:]
at org.hornetq.ra.inflow.HornetQActivation.handleFailure(HornetQActivation.java:539) [:]
at org.hornetq.ra.inflow.HornetQActivation$SetupActivation.run(HornetQActivation.java:577) [:]
at org.jboss.resource.work.WorkWrapper.run(WorkWrapper.java:172) [:6.0.1-SNAPSHOT]
at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33) [:2.0.0.CR7]
at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:801) [:2.0.0.CR7]
at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45) [:2.0.0.CR7]
at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:821) [:2.0.0.CR7]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_23]
at org.jboss.threads.JBossThread.run(JBossThread.java:122) [:2.0.0.CR7]
At the very end of the startup process connect succeeds:
2010-12-28 11:49:09,133 INFO [org.hornetq.ra.inflow.HornetQActivation.info] (pool-1-thread-2) Attempting to reconnect org.hornetq.ra.inflow.HornetQActivationSpec(ra=org.hornetq.ra.HornetQResourceAdapter@1fe97f9 destination=queue/mbi2e-lafr-sb2000-ipc/SalesOrderImportQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15)
2010-12-28 11:49:09,156 INFO [org.hornetq.ra.inflow.HornetQActivation.info] (pool-1-thread-1) Attempting to reconnect org.hornetq.ra.inflow.HornetQActivationSpec(ra=org.hornetq.ra.HornetQResourceAdapter@1fe97f9 destination=queue/mbi2e-lafr-sb2000-ipc/MessageDistributorQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15)
2010-12-28 11:49:09,236 INFO [org.apache.coyote.http11.Http11Protocol.start] (Thread-2) Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
2010-12-28 11:49:09,241 INFO [org.apache.coyote.http11.Http11Protocol.start] (Thread-2) Starting Coyote HTTP/1.1 on http-0.0.0.0-8443
2010-12-28 11:49:09,243 INFO [org.jboss.bootstrap.impl.base.server.AbstractServer.run] (Thread-2) JBossAS [6.0.1.SNAPSHOT "Neo"] Started in 3m:57s:688ms
2010-12-28 11:49:09,259 INFO [org.hornetq.ra.inflow.HornetQActivation.info] (pool-1-thread-1) Reconnected with HornetQ
2010-12-28 11:49:09,292 INFO [org.hornetq.ra.inflow.HornetQActivation.info] (pool-1-thread-2) Reconnected with HornetQ
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months