July 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-1864) UDP unable to bind to ephemeral port: port out of range:65536

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1864?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1864: -------------------------------- Hmm, I can still not reproduce this. So you didn't use any {{java.net.preferXXX}} system props (which defaults to IPv6). What was your JGroups config ? And did you set {{jgroups.bind_addr}} ? Seems {{bind_addr}} was set to {{127.0.0.1}} ? > UDP unable to bind to ephemeral port: port out of range:65536 > ------------------------------------------------------------- > > Key: JGRP-1864 > URL: https://issues.jboss.org/browse/JGRP-1864 > Project: JGroups > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.4.4 > Reporter: Dan Berindei > Assignee: Bela Ban > Priority: Minor > Fix For: 3.4.5, 3.5 > > > It looks like {{UDP.createEphemeralDatagramSocket()}} swallows any errors it gets while creating the socket, and throws this exception after trying to bind to all ports in the 0 - 65535 range: > {noformat} > java.lang.IllegalArgumentException: port out of range:65536 > at java.net.InetSocketAddress.checkPort(InetSocketAddress.java:143) > at java.net.InetSocketAddress.<init>(InetSocketAddress.java:185) > at java.net.DatagramSocket.<init>(DatagramSocket.java:284) > at org.jgroups.util.DefaultSocketFactory.createDatagramSocket(DefaultSocketFactory.java:62) > at org.jgroups.protocols.UDP.createEphemeralDatagramSocket(UDP.java:429) > at org.jgroups.protocols.UDP.createSockets(UDP.java:311) > at org.jgroups.protocols.UDP.start(UDP.java:216) > at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:966) > at org.jgroups.JChannel.startStack(JChannel.java:889) > at org.jgroups.JChannel._preConnect(JChannel.java:547) > at org.jgroups.JChannel.connect(JChannel.java:282) > at org.jgroups.JChannel.connect(JChannel.java:273) > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.startJGroupsChannelIfNeeded(JGroupsTransport.java:200) > {noformat} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-570) Rule inheritance fails when using or pattern binding

by Eugene Shvartsman (JIRA)

[ https://issues.jboss.org/browse/DROOLS-570?page=com.atlassian.jira.plugin... ] Eugene Shvartsman updated DROOLS-570: ------------------------------------- Attachment: tester-module.7z > Rule inheritance fails when using or pattern binding > ---------------------------------------------------- > > Key: DROOLS-570 > URL: https://issues.jboss.org/browse/DROOLS-570 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.1.Final > Environment: Windows 7 VM. Running drools using a JUnit driver > Reporter: Eugene Shvartsman > Assignee: Mark Proctor > Attachments: tester-module.7z > > > I've found a certain combination of rules (when using inheritance) that causes drools to throw the following exception: http://pastebin.com/xxq5ZtAC > The rules that cause this exception to occur can be found here: http://pastebin.com/wM6rWY8L > I've simplified my original rules down to the lowest level of detail that still throws the exception. The exception is no longer thrown if I: > 1. Don't use rule inheritance > 2. Don't have an or statement > 3. Don't reference an LHS defined variable in the RHS of ruleB -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-570) Rule inheritance fails when using or pattern binding

by Eugene Shvartsman (JIRA)

[ https://issues.jboss.org/browse/DROOLS-570?page=com.atlassian.jira.plugin... ] Eugene Shvartsman updated DROOLS-570: ------------------------------------- Affects Version/s: 6.0.1.Final > Rule inheritance fails when using or pattern binding > ---------------------------------------------------- > > Key: DROOLS-570 > URL: https://issues.jboss.org/browse/DROOLS-570 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.1.Final > Environment: Windows 7 VM. Running drools using a JUnit driver > Reporter: Eugene Shvartsman > Assignee: Mark Proctor > Attachments: tester-module.7z > > > I've found a certain combination of rules (when using inheritance) that causes drools to throw the following exception: http://pastebin.com/xxq5ZtAC > The rules that cause this exception to occur can be found here: http://pastebin.com/wM6rWY8L > I've simplified my original rules down to the lowest level of detail that still throws the exception. The exception is no longer thrown if I: > 1. Don't use rule inheritance > 2. Don't have an or statement > 3. Don't reference an LHS defined variable in the RHS of ruleB -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-570) Rule inheritance fails when using or pattern binding

by Eugene Shvartsman (JIRA)

Eugene Shvartsman created DROOLS-570: ---------------------------------------- Summary: Rule inheritance fails when using or pattern binding Key: DROOLS-570 URL: https://issues.jboss.org/browse/DROOLS-570 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Environment: Windows 7 VM. Running drools using a JUnit driver Reporter: Eugene Shvartsman Assignee: Mark Proctor I've found a certain combination of rules (when using inheritance) that causes drools to throw the following exception: http://pastebin.com/xxq5ZtAC The rules that cause this exception to occur can be found here: http://pastebin.com/wM6rWY8L I've simplified my original rules down to the lowest level of detail that still throws the exception. The exception is no longer thrown if I: 1. Don't use rule inheritance 2. Don't have an or statement 3. Don't reference an LHS defined variable in the RHS of ruleB -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2510) Add CLI command to display information about current connection.

by Claudio Miranda (JIRA)

[ https://issues.jboss.org/browse/WFLY-2510?page=com.atlassian.jira.plugin.... ] Claudio Miranda commented on WFLY-2510: --------------------------------------- Hi, what about to list all connections (CLI and GUI) ? Similar to 'w' command on linux, it could display - username - source address - login time - type of connection: GUI, CLI >From a security perspective would be good to know who are the users connected to wildfly. > Add CLI command to display information about current connection. > ---------------------------------------------------------------- > > Key: WFLY-2510 > URL: https://issues.jboss.org/browse/WFLY-2510 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: CLI > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: management_security, > Fix For: Awaiting Volunteers > > > Would be useful for a single command to display information about the current connection. > Definitely information about SSL, certificates, authenticated user, address etc... > Could also obtain other common info from server. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-546) FactType.get/set should throw specific exception (not NPE) for unknown fields

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/DROOLS-546?page=com.atlassian.jira.plugin... ] Davide Sottara commented on DROOLS-546: --------------------------------------- Sorry, this was already fixed and should have been closed Sent via the ASUS PadFone X, an AT&T 4G LTE smartphone > FactType.get/set should throw specific exception (not NPE) for unknown fields > ----------------------------------------------------------------------------- > > Key: DROOLS-546 > URL: https://issues.jboss.org/browse/DROOLS-546 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.1.0.CR1 > Reporter: Benoit Voisin > Assignee: Mario Fusco > Fix For: 6.2.0.Beta1 > > > factType.get(instance, "unknownField") is currently throwing an NPE. This gives improper information to the user/developper. > I propose that it throws a new UnknownFactFieldException giving improved information giving good hints for debugging or enabling specific exception management. > See pull request for test-case and proposed fix -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-542) Expose more Commands through the KieCommands API

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/DROOLS-542?page=com.atlassian.jira.plugin... ] Davide Sottara commented on DROOLS-542: --------------------------------------- Fixed already Sent via the ASUS PadFone X, an AT&T 4G LTE smartphone > Expose more Commands through the KieCommands API > ------------------------------------------------ > > Key: DROOLS-542 > URL: https://issues.jboss.org/browse/DROOLS-542 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 6.1.0.CR1 > Reporter: Davide Sottara > Assignee: Davide Sottara > Fix For: 6.2.0.Beta1 > > > Not all Commands are exposed by the KieCommands API interface -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-448) Traiting non-declared POJOS prevents the execution of WM actions from outside the WM

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/DROOLS-448?page=com.atlassian.jira.plugin... ] Davide Sottara commented on DROOLS-448: --------------------------------------- Fixed already Sent via the ASUS PadFone X, an AT&T 4G LTE smartphone > Traiting non-declared POJOS prevents the execution of WM actions from outside the WM > ------------------------------------------------------------------------------------ > > Key: DROOLS-448 > URL: https://issues.jboss.org/browse/DROOLS-448 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.6.0.Final, 6.0.0.Final, 6.0.1.Final, 6.1.0.Beta1 > Reporter: Davide Sottara > Assignee: Davide Sottara > Priority: Critical > Fix For: 6.2.0.Beta1 > > > When a trait is applied to non-declared bean, a transparent proxy is created and the handle is updated accordingly. However, this prevents the lookup of the handle using the original object as a key. > The proxy creation should be avoided. > See also PLANNER-229 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-122) Clean unreferenced deployments from the content repository

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-122?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration updated WFLY-122: ----------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1124689 > Clean unreferenced deployments from the content repository > ---------------------------------------------------------- > > Key: WFLY-122 > URL: https://issues.jboss.org/browse/WFLY-122 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 9.0.0.CR1 > > > The algorithm for removing unused deployments from the content repository is based on doing this as part of undeploy operation execution. This doesn't cover cases where the content is never explicitly undeployed. For example: > 1) Scanner content that is updated when the server is offline; the old content will not have been "undeployed" during shutdown, and on startup the new content will be installed. > 2) Similar issues with deployments generated from module resources (see "A Mixed Approach on https://community.jboss.org/wiki/ExtendingAS7). When the server shuts down, there is no "subsystem remove" as part of shutdown, so the content added during start will not be removed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3695) Distributed web session expiration ScheduledExecutorService leaks threads on undeploy

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-3695?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-3695: ------------------------------- Priority: Critical (was: Major) > Distributed web session expiration ScheduledExecutorService leaks threads on undeploy > ------------------------------------------------------------------------------------- > > Key: WFLY-3695 > URL: https://issues.jboss.org/browse/WFLY-3695 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 8.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > Fix For: 8.2.0.CR1, 9.0.0.Beta1 > > > The ScheduledExecutorService employed by the SessionExpirationScheduler uses shutdown() to shutdown the thread pool - however, unless we explicitly setExecuteExistingDelayedTasksAfterShutdownPolicy(false), all scheduled tasks will attempt to execute after shutdown! -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2014