[JBoss JIRA] (JBRULES-3312) Clearify sliding windows behaviour regarding literal and non-literal values
by Markus Merder (Created) (JIRA)
Clearify sliding windows behaviour regarding literal and non-literal values
---------------------------------------------------------------------------
Key: JBRULES-3312
URL: https://issues.jboss.org/browse/JBRULES-3312
Project: Drools
Issue Type: Patch
Security Level: Public (Everyone can see)
Affects Versions: 5.3.0.Final
Reporter: Markus Merder
Assignee: Mark Proctor
Priority: Optional
Regarding JBRULES-2823: I don't know how to supply a patch for the fusion user guide, so I'll just type here:
To the orginal:
"For instance, if the user wants to consider only the last 10 IBM Stock Ticks, independent of how old they are, the pattern would look like this:
StockTick( company == "IBM" ) over window:length( 10 )
As you can see, the pattern is similar to the one presented in the previous section, but instead of using window:time to define the sliding window, it uses window:length."
you should append the following to clearify:
"Be aware that only literal conditions are applied before the window is applied. So the following rule would consider only the IBM stock ticks WITHIN ALL last 10 stock ticks:
@company : Company(name == "IBM")
StockTick( company == @company ) over window:length( 10 )
"
--
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-3307) Multi Byte Character filename garbled in HTTP response
by Morgan Daniel (JIRA)
Morgan Daniel created AS7-3307:
----------------------------------
Summary: Multi Byte Character filename garbled in HTTP response
Key: AS7-3307
URL: https://issues.jboss.org/browse/AS7-3307
Project: Application Server 7
Issue Type: Bug
Components: Server, Web
Affects Versions: 7.1.0.CR1b
Environment: Server Setup:
Windows Server 2008 R2 Standard
Java 6 SE Update 30
TorqueBox 2.0.0.beta2
JBoss AS 7.1.0.CR1b (Standalone configuration)
JRuby 1.6.5.1
Redmine 1.3.0
Client Setup:
WinXP SP3
Firefox 9.0.1
Reporter: Morgan Daniel
Assignee: Jason Greene
When downloading a file from a Rails app through a web browser, the "Content-Disposition" in the HTTP response contains a garbled filename.
Adding the following configuration to "standalone.xml" did not resolve the issue.
{code:xml}
<property name="org.apache.catalina.connector.URI_ENCODING" value="UTF-8"/>
<property name="org.apache.catalina.connector.USE_BODY_ENCODING_FOR_QUERY_STRING" value="true"/>
{code}
The issue does not occur with a JRuby + WEBrick Server + Rails App server configuration.
--
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] (JGRP-1414) Synchronizing on 'members' MessageDispatcher.cast() is a contention point
by Manik Surtani (JIRA)
Manik Surtani created JGRP-1414:
-----------------------------------
Summary: Synchronizing on 'members' MessageDispatcher.cast() is a contention point
Key: JGRP-1414
URL: https://issues.jboss.org/browse/JGRP-1414
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.2
Reporter: Manik Surtani
Assignee: Bela Ban
Attachments: TreeSet.png
MessageDispatcher.cast() synchronizes on {{members}} and copies it to a local collection if {{null}} is passed in as your destination list. This is a contention point if you have many concurrent threads attempting to cast() to the entire cluster, as they start queueing up at this point.
Guarding {{members}} with a ReadWriteLock is probably a better approach, allowing {{members}} to be read safely and concurrently.
However, since {{members}} is protected, I am not sure of the implications around this. But then again, there is no guarantee that subclasses/extensions synchronize on {{members}} anyway.
--
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] (JASSIST-148) StackOverflowError when using $sig and $class in call to static method
by Wanja Gayk (Created) (JIRA)
StackOverflowError when using $sig and $class in call to static method
----------------------------------------------------------------------
Key: JASSIST-148
URL: https://issues.jboss.org/browse/JASSIST-148
Project: Javassist
Issue Type: Bug
Affects Versions: 3.15.0-GA
Environment: Runtime Enviroment:
Java SE 6 Update 30 (64 bit)
also reproduced with:
Java SE 7 Update 2 (64 bit)
Compiler:
Eclipse Indigo (Version: 3.7.1, Build id: M20110909-1335).
Operating System
Windows 7 Professional (64 bit)
CPU:
Intel Core i7 860 (2,8 GHz)
Reporter: Wanja Gayk
Assignee: Shigeru Chiba
Using $sig or $class as method parameter in "insertBefore"-expressions throws a StackOverflowError when the target is a static method.
Calling nonstatic methods works like expected.
Stack/Log-Traces:
When using $sig:
instrumenting class: de/plush/brix/instrumentation/Main (995 bytes)
instrumenting class: javassist/runtime/Desc (3280 bytes)
Exception in thread "main" java.lang.StackOverflowError
at javassist.runtime.Desc.getParams(Desc.java)
at javassist.runtime.Desc.getParams(Desc.java)
at javassist.runtime.Desc.getParams(Desc.java)
[...]
When using $class:
instrumenting class: de/plush/brix/instrumentation/Main (995 bytes)
instrumenting class: javassist/runtime/Desc (3280 bytes)
Exception in thread "main" java.lang.StackOverflowError
at javassist.runtime.Desc.getClazz(Desc.java)
at javassist.runtime.Desc.getClazz(Desc.java)
[...]
--
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-3297) NumberFormatException during host-controller startup if the example of host.xml is used
by Wolf-Dieter Fink (JIRA)
Wolf-Dieter Fink created AS7-3297:
-------------------------------------
Summary: NumberFormatException during host-controller startup if the example of host.xml is used
Key: AS7-3297
URL: https://issues.jboss.org/browse/AS7-3297
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Wolf-Dieter Fink
Assignee: Brian Stansberry
If a host-controller should be started and connected do a remote domain-controller the example did not work.
<remote host="${jboss.domain.master.address}" port="${jboss.domain.master.port:9999}"/>
Nevertheless whether the properties are given or not the following exception occour:
[Host Controller] Caused by: java.lang.NumberFormatException: For input string: "${jboss.domain.master.port:9999}"
[Host Controller] at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) [:1.6.0_22]
[Host Controller] at java.lang.Integer.parseInt(Integer.java:470) [:1.6.0_22]
[Host Controller] at java.lang.Integer.valueOf(Integer.java:570) [:1.6.0_22]
[Host Controller] at org.jboss.as.host.controller.parsing.HostXml.parseRemoteDomainController(HostXml.java:756) [jboss-as-host-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
[Host Controller] at org.jboss.as.host.controller.parsing.HostXml.parseDomainController(HostXml.java:716) [jboss-as-host-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
The check of HostXml.parseRemoteDomainController checks hard whether the port is an Integer value
--
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-3139) add-user.sh script error: ModuleNotFoundException: Module org.jboss.as.domain-add-user:main is not found
by Hendy Irawan (Created) (JIRA)
add-user.sh script error: ModuleNotFoundException: Module org.jboss.as.domain-add-user:main is not found
--------------------------------------------------------------------------------------------------------
Key: AS7-3139
URL: https://issues.jboss.org/browse/AS7-3139
Project: Application Server 7
Issue Type: Bug
Components: CLI
Affects Versions: 7.1.0.CR1
Environment: Linux Mint 12 (Ubuntu Oneiric 11.10) 64-bit
Linux annafi 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
java version "1.7.0_147-icedtea"
OpenJDK Runtime Environment (IcedTea7 2.0) (7~b147-2.0-0ubuntu0.11.10.1)
OpenJDK 64-Bit Server VM (build 21.0-b17, mixed mode)
Reporter: Hendy Irawan
Assignee: Alexey Loubyansky
When I access localhost:9990 it says I need to create a user.
But while doing so :
ceefour@annafi:~/jboss-as-7.1.0.CR1/bin$ ./add-user.sh
org.jboss.modules.ModuleNotFoundException: Module org.jboss.as.domain-add-user:main is not found
at org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:121)
at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:245)
at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:194)
at org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:97)
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:176)
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:172)
at org.jboss.modules.Main.main(Main.java:311)
--
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-3042) IPv6: Invalid redirect to Admin console (wrong IP address)
by Dustin Kut Moy Cheung (JIRA)
[ https://issues.jboss.org/browse/AS7-3042?page=com.atlassian.jira.plugin.s... ]
Dustin Kut Moy Cheung edited comment on AS7-3042 at 1/13/12 10:48 AM:
----------------------------------------------------------------------
Heiko: was it really fixed? I tried what Pavel described [connect to http://[::1]:8080, then click on Administration Console] and it still redirected me to http://[::1]:9990/console [and I got a "Unable To Connect" error]
[Tested in latest nightly build of JBoss-AS7]
Thanks for your help!
was (Author: dcheung):
Heiko: was it really fixed? I tried what Pavel described [connect to http://[::1]:8080, then click on Administration Console] and it still redirected me to http://[::1]:9990/console [and I got a "Unable To Connect" error]
Thanks for your help!
> IPv6: Invalid redirect to Admin console (wrong IP address)
> ----------------------------------------------------------
>
> Key: AS7-3042
> URL: https://issues.jboss.org/browse/AS7-3042
> Project: Application Server 7
> Issue Type: Bug
> Components: Console, Web
> Affects Versions: 7.1.0.Beta1b
> Reporter: Pavel Janousek
> Assignee: Heiko Braun
> Priority: Blocker
>
> This issue is some derivation from AS7-3040. Lets imagine starting server like this:
> {code}./standalone.sh -Djava.net.preferIPv4Stack=false -Djboss.bind.address=::1{code}
> So by default the admin/management is bound to _::ffff:127.0.0.1:9990_ and _::ffff:127.0.0.1:9999_, but it isn't accessible from Web WelcomePage at _::1:8080_ because the URL is specified as: {code}<a href="/console">{code} and so the next request is http://[::1]:8080/console which redirect requester to http://[::1]:9990, but there isn't any console because it is here - http://[::ffff:127.0.0.1]:9990.
> This is not good as it could lead to integration issues between components (X trying to connect to Y on ::1; Y listening on ::ffff:127.0.0.1).
--
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-3042) IPv6: Invalid redirect to Admin console (wrong IP address)
by Dustin Kut Moy Cheung (JIRA)
[ https://issues.jboss.org/browse/AS7-3042?page=com.atlassian.jira.plugin.s... ]
Dustin Kut Moy Cheung commented on AS7-3042:
--------------------------------------------
Heiko: was it really fixed? I tried what Pavel described [connect to http://[::1]:8080, then click on Administration Console] and it still redirected me to http://[::1]:9990/console [and I got a "Unable To Connect" error]
Thanks for your help!
> IPv6: Invalid redirect to Admin console (wrong IP address)
> ----------------------------------------------------------
>
> Key: AS7-3042
> URL: https://issues.jboss.org/browse/AS7-3042
> Project: Application Server 7
> Issue Type: Bug
> Components: Console, Web
> Affects Versions: 7.1.0.Beta1b
> Reporter: Pavel Janousek
> Assignee: Heiko Braun
> Priority: Blocker
>
> This issue is some derivation from AS7-3040. Lets imagine starting server like this:
> {code}./standalone.sh -Djava.net.preferIPv4Stack=false -Djboss.bind.address=::1{code}
> So by default the admin/management is bound to _::ffff:127.0.0.1:9990_ and _::ffff:127.0.0.1:9999_, but it isn't accessible from Web WelcomePage at _::1:8080_ because the URL is specified as: {code}<a href="/console">{code} and so the next request is http://[::1]:8080/console which redirect requester to http://[::1]:9990, but there isn't any console because it is here - http://[::ffff:127.0.0.1]:9990.
> This is not good as it could lead to integration issues between components (X trying to connect to Y on ::1; Y listening on ::ffff:127.0.0.1).
--
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