[JBoss JIRA] (JBRULES-3579) scala case class, Option field and mvel : unable to resolve method using strict-mode
by david crosson (JIRA)
david crosson created JBRULES-3579:
--------------------------------------
Summary: scala case class, Option field and mvel : unable to resolve method using strict-mode
Key: JBRULES-3579
URL: https://issues.jboss.org/browse/JBRULES-3579
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler
Affects Versions: 5.4.0.Final, 5.3.1.Final, 5.3.2.Final
Environment: scala 2.9.2, java hotspot 1.6.0_33
Reporter: david crosson
Assignee: Mark Proctor
case class Address(street:String, town:String, country:String)
case class Home(someone:Someone, address:Option[Address])
rule "Who live at London"
when
$someone:Someone($name:name)
Home(someone == $someone, address.isDefined, address.get.town == "London")
then
insert(new InformationRequest($someone, $name+" lives in London"))
end
address.get is seen as a java.lang.Object, not an "Address". The reported error is :
$ sbt run
[info] Loading project definition from /home/dcr/dev-new/scala-drools-dummy-project/project
[info] Set current project to ScalaDroolsDummyProject (in build file:/home/dcr/dev-new/scala-drools-dummy-project/)
[info] Running dummy.Dummy
Unable to Analyse Expression address.get.town:
[Error: unable to resolve method using strict-mode: java.lang.Object.town()]
[Near : {... address.get.town ....}]
^
[Line: 61, Column: 49] : [Rule name='Who live at London']
Although I've set mvel strict to false :
System.setProperty("drools.dialect.mvel.strict", "false")
--
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, 7 months
[JBoss JIRA] (AS7-5687) CLI crashes with OutOfMemoryError when logging exceptions in CommandContext.handleSafe()
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/AS7-5687?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse commented on AS7-5687:
---------------------------------------
Yes that is the correct response assuming no user admin with password admin has been added to the properties files.
> CLI crashes with OutOfMemoryError when logging exceptions in CommandContext.handleSafe()
> ----------------------------------------------------------------------------------------
>
> Key: AS7-5687
> URL: https://issues.jboss.org/browse/AS7-5687
> Project: Application Server 7
> Issue Type: Bug
> Components: CLI
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Josef Cacek
> Assignee: Alexey Loubyansky
> Priority: Critical
> Labels: eap601-qe-triage
>
> CLI crashes with OutOfMemoryError if the authentication fails.
> {code}
> jcacek@jcacek-nb:~/Testing/jboss-eap-6.0.1.ER2/bin$ ./jboss-cli.sh
> You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
> [disconnected /] connect
> Authenticating against security realm: ManagementRealm
> Username: admin
> Password:
> java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Arrays.java:2882)
> at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:100)
> at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:390)
> at java.lang.StringBuilder.append(StringBuilder.java:119)
> at org.jboss.as.cli.impl.CommandContextImpl.handleSafe(CommandContextImpl.java:551)
> at org.jboss.as.cli.impl.CommandContextImpl.interact(CommandContextImpl.java:1113)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:243)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.modules.Module.run(Module.java:270)
> at org.jboss.modules.Main.main(Main.java:294)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-5687) CLI crashes with OutOfMemoryError when logging exceptions in CommandContext.handleSafe()
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/AS7-5687?page=com.atlassian.jira.plugin.s... ]
Alexey Loubyansky commented on AS7-5687:
----------------------------------------
Now, that OOME is fixed, the message is "Unable to authenticate against controller at localhost:9999: Authentication failed: all available authentication mechanisms failed"
Which is expected, right? (for username 'admin' and password 'admin').
> CLI crashes with OutOfMemoryError when logging exceptions in CommandContext.handleSafe()
> ----------------------------------------------------------------------------------------
>
> Key: AS7-5687
> URL: https://issues.jboss.org/browse/AS7-5687
> Project: Application Server 7
> Issue Type: Bug
> Components: CLI
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Josef Cacek
> Assignee: Alexey Loubyansky
> Priority: Critical
> Labels: eap601-qe-triage
>
> CLI crashes with OutOfMemoryError if the authentication fails.
> {code}
> jcacek@jcacek-nb:~/Testing/jboss-eap-6.0.1.ER2/bin$ ./jboss-cli.sh
> You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
> [disconnected /] connect
> Authenticating against security realm: ManagementRealm
> Username: admin
> Password:
> java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Arrays.java:2882)
> at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:100)
> at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:390)
> at java.lang.StringBuilder.append(StringBuilder.java:119)
> at org.jboss.as.cli.impl.CommandContextImpl.handleSafe(CommandContextImpl.java:551)
> at org.jboss.as.cli.impl.CommandContextImpl.interact(CommandContextImpl.java:1113)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:243)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.modules.Module.run(Module.java:270)
> at org.jboss.modules.Main.main(Main.java:294)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (JGRP-1522) NAKACK / NAKACK2: flushBecomeServerQueue() might trigger sending of message on unconnected channel
by Bela Ban (JIRA)
Bela Ban created JGRP-1522:
------------------------------
Summary: NAKACK / NAKACK2: flushBecomeServerQueue() might trigger sending of message on unconnected channel
Key: JGRP-1522
URL: https://issues.jboss.org/browse/JGRP-1522
Project: JGroups
Issue Type: Bug
Affects Versions: 3.2
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 3.2
Attachments: tmp.log
If become_server_queue_size in NAKACK{2} is > 0, both protocols buffer messages sent before is_server=true, and replay them when the first view is received or when a BECOME_SERVER event is received.
There are 2 issues associated with this:
#1 When flushing the become_server_queue, we should never call up(Event) directly (use the thread pool). [This is not the issue that's causing this though]
#2 When the queue is flushed on the first view change, this might trigger messages to be delivered to the application, which in turn might send messages (all on the same thread, because of #1). As the channel is yet unconnected, the message send will trigger an exception, which causes the JOIN to fail !
SOLUTION:
- Flush become_server_queue in a separate task (good practice to do this on a separate thread anyway !)
- Only flush the become_server_queue when receiving a BECOME_SERVER event, *not* when receiving the first view change
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-5687) CLI crashes with OutOfMemoryError when logging exceptions in CommandContext.handleSafe()
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/AS7-5687?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse commented on AS7-5687:
---------------------------------------
Anything you want me to look into Alexey?
> CLI crashes with OutOfMemoryError when logging exceptions in CommandContext.handleSafe()
> ----------------------------------------------------------------------------------------
>
> Key: AS7-5687
> URL: https://issues.jboss.org/browse/AS7-5687
> Project: Application Server 7
> Issue Type: Bug
> Components: CLI
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Josef Cacek
> Assignee: Alexey Loubyansky
> Priority: Critical
> Labels: eap601-qe-triage
>
> CLI crashes with OutOfMemoryError if the authentication fails.
> {code}
> jcacek@jcacek-nb:~/Testing/jboss-eap-6.0.1.ER2/bin$ ./jboss-cli.sh
> You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
> [disconnected /] connect
> Authenticating against security realm: ManagementRealm
> Username: admin
> Password:
> java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Arrays.java:2882)
> at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:100)
> at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:390)
> at java.lang.StringBuilder.append(StringBuilder.java:119)
> at org.jboss.as.cli.impl.CommandContextImpl.handleSafe(CommandContextImpl.java:551)
> at org.jboss.as.cli.impl.CommandContextImpl.interact(CommandContextImpl.java:1113)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:243)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.modules.Module.run(Module.java:270)
> at org.jboss.modules.Main.main(Main.java:294)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-5687) CLI crashes with OutOfMemoryError when authentication fails
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/AS7-5687?page=com.atlassian.jira.plugin.s... ]
Alexey Loubyansky moved JBPAPP-10126 to AS7-5687:
-------------------------------------------------
Project: Application Server 7 (was: JBoss Enterprise Application Platform)
Key: AS7-5687 (was: JBPAPP-10126)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: 7.1.3.Final (EAP)
(was: EAP 6.0.1 ER 2)
Component/s: CLI
(was: Consoles)
Security: (was: Public)
Docs QE Status: (was: NEW)
> CLI crashes with OutOfMemoryError when authentication fails
> -----------------------------------------------------------
>
> Key: AS7-5687
> URL: https://issues.jboss.org/browse/AS7-5687
> Project: Application Server 7
> Issue Type: Bug
> Components: CLI
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Josef Cacek
> Assignee: Alexey Loubyansky
> Priority: Critical
> Labels: eap601-qe-triage
>
> CLI crashes with OutOfMemoryError if the authentication fails.
> {code}
> jcacek@jcacek-nb:~/Testing/jboss-eap-6.0.1.ER2/bin$ ./jboss-cli.sh
> You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
> [disconnected /] connect
> Authenticating against security realm: ManagementRealm
> Username: admin
> Password:
> java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Arrays.java:2882)
> at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:100)
> at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:390)
> at java.lang.StringBuilder.append(StringBuilder.java:119)
> at org.jboss.as.cli.impl.CommandContextImpl.handleSafe(CommandContextImpl.java:551)
> at org.jboss.as.cli.impl.CommandContextImpl.interact(CommandContextImpl.java:1113)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:243)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.modules.Module.run(Module.java:270)
> at org.jboss.modules.Main.main(Main.java:294)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-5687) CLI crashes with OutOfMemoryError when logging exceptions in CommandContext.handleSafe()
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/AS7-5687?page=com.atlassian.jira.plugin.s... ]
Alexey Loubyansky updated AS7-5687:
-----------------------------------
Summary: CLI crashes with OutOfMemoryError when logging exceptions in CommandContext.handleSafe() (was: CLI crashes with OutOfMemoryError when authentication fails)
> CLI crashes with OutOfMemoryError when logging exceptions in CommandContext.handleSafe()
> ----------------------------------------------------------------------------------------
>
> Key: AS7-5687
> URL: https://issues.jboss.org/browse/AS7-5687
> Project: Application Server 7
> Issue Type: Bug
> Components: CLI
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Josef Cacek
> Assignee: Alexey Loubyansky
> Priority: Critical
> Labels: eap601-qe-triage
>
> CLI crashes with OutOfMemoryError if the authentication fails.
> {code}
> jcacek@jcacek-nb:~/Testing/jboss-eap-6.0.1.ER2/bin$ ./jboss-cli.sh
> You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
> [disconnected /] connect
> Authenticating against security realm: ManagementRealm
> Username: admin
> Password:
> java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Arrays.java:2882)
> at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:100)
> at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:390)
> at java.lang.StringBuilder.append(StringBuilder.java:119)
> at org.jboss.as.cli.impl.CommandContextImpl.handleSafe(CommandContextImpl.java:551)
> at org.jboss.as.cli.impl.CommandContextImpl.interact(CommandContextImpl.java:1113)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:243)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.modules.Module.run(Module.java:270)
> at org.jboss.modules.Main.main(Main.java:294)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months