November 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5418) start-delivery/stop-delivery operations descriptions are missing from MDB deployment in domain mode

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-5418?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-5418: ---------------------------------------- [~jmesnil] I don't have any objections to that, but I'd like to hear [~kabirkhan]'s input as he designed the JMX integration. My expectation though is when this was designed we just didn't have reliable data to distinguish the runtime-only case. *However* this change is out of scope for this JIRA. This is a general RFE for WildFly Core and needs to be handled as such. This description of this JIRA is about a bug in the main management model, unrelated to JMX. > start-delivery/stop-delivery operations descriptions are missing from MDB deployment in domain mode > --------------------------------------------------------------------------------------------------- > > Key: WFLY-5418 > URL: https://issues.jboss.org/browse/WFLY-5418 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: JBoss AS7 7.2.0.Final > Environment: JBoss EAP 6.4.3 > Reporter: Tom Ross > Assignee: Jeff Mesnil > Fix For: 10.0.0.CR4 > > > It is possible to start/stop delivery of messages to MDB in standalone mode using operations > start-delivery() and stop-delivery() on MDB deployment. > Those operations are available in domain mode but their descriptions are missing (preventing CLI autocompletion to work as expected). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1974) Socket factory not set correctly with singleton transport

by Dennis Reed (JIRA)

Dennis Reed created JGRP-1974: --------------------------------- Summary: Socket factory not set correctly with singleton transport Key: JGRP-1974 URL: https://issues.jboss.org/browse/JGRP-1974 Project: JGroups Issue Type: Bug Affects Versions: 3.2.13 Reporter: Dennis Reed Assignee: Bela Ban When using a singleton transport, the socket factory is not set correctly on startup. JChannel sets the socket factory down the stack on startup, then starts the stack. The transport protocol is substituted with a TP.ProtocolAdapter during startup (*after* the socket factory was set), so it still uses its default socket factory, and provides it to all protocols up the stack. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5449) Custom socket factory for JGroups subsystem not set correctly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-5449?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-5449: ----------------------------------------------- dereed(a)redhat.com changed the Status of [bug 1268185|https://bugzilla.redhat.com/show_bug.cgi?id=1268185] from ASSIGNED to ON_QA > Custom socket factory for JGroups subsystem not set correctly > ------------------------------------------------------------- > > Key: WFLY-5449 > URL: https://issues.jboss.org/browse/WFLY-5449 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.CR2 > Reporter: Dennis Reed > Assignee: Paul Ferraro > Priority: Blocker > Fix For: 10.0.0.CR4 > > > Wildfly's JChannelFactory tries to set a custom socket factory on the JGroups transport. > This is not the correct API to use, and it gets overwritten when the JGroups channel starts. > A custom socket factory should be set on the JChannel. > The only time the custom socket factory is currently used is if there's a race condition where two channels are started at the same time, and the custom factory is set just before the other channel uses it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1063) Creating named datagram socket throws ISE

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1063?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1063: ------------------------------------------------- dereed(a)redhat.com changed the Status of [bug 1268185|https://bugzilla.redhat.com/show_bug.cgi?id=1268185] from ASSIGNED to ON_QA > Creating named datagram socket throws ISE > ----------------------------------------- > > Key: WFCORE-1063 > URL: https://issues.jboss.org/browse/WFCORE-1063 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.0.0.CR7 > Reporter: Paul Ferraro > Assignee: Brian Stansberry > Fix For: 2.0.0.CR8 > > > The DatagramSocket createDatagramSocket(String name, SocketAddress address) method of org.jboss.as.network.SocketBindingManagerImpl creates a ManagedDatagramSocketBinding with a null name, yet registers the socket using the NamedManagedBindingRegistry. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1064) Creating named multicast socket doesn't properly register socket using name

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1064?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1064: ------------------------------------------------- dereed(a)redhat.com changed the Status of [bug 1268185|https://bugzilla.redhat.com/show_bug.cgi?id=1268185] from ASSIGNED to ON_QA > Creating named multicast socket doesn't properly register socket using name > --------------------------------------------------------------------------- > > Key: WFCORE-1064 > URL: https://issues.jboss.org/browse/WFCORE-1064 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.0.0.CR7 > Reporter: Paul Ferraro > Assignee: Brian Stansberry > Fix For: 2.0.0.CR8 > > > I'm not sure why this is, but the socket binding manager ignores the name of the multicast socket and registers the socket using the unnamed registry. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1033) ManagedDatagramSocketBinding and ManagedMulticastSocketBinding throw NPE if created with bind address

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1033?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1033: ------------------------------------------------- dereed(a)redhat.com changed the Status of [bug 1268185|https://bugzilla.redhat.com/show_bug.cgi?id=1268185] from ASSIGNED to ON_QA > ManagedDatagramSocketBinding and ManagedMulticastSocketBinding throw NPE if created with bind address > ----------------------------------------------------------------------------------------------------- > > Key: WFCORE-1033 > URL: https://issues.jboss.org/browse/WFCORE-1033 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 2.0.0.CR6 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > Fix For: 2.0.0.CR7 > > > {noformat} > &amp#27;[0m&amp#27;[31m14:51:47,114 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.jgroups.channel.ee.connector: org.jboss.msc.service.StartException in service jboss.jgroups.channel.ee.connector: java.lang.NullPointerException > at org.wildfly.clustering.jgroups.spi.service.ChannelConnectorBuilder.start(ChannelConnectorBuilder.java:96) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.NullPointerException > at org.jboss.as.network.ManagedMulticastSocketBinding.bind(ManagedMulticastSocketBinding.java:78) > at java.net.MulticastSocket.<init>(MulticastSocket.java:172) > at org.jboss.as.network.ManagedMulticastSocketBinding.<init>(ManagedMulticastSocketBinding.java:54) > at org.jboss.as.network.ManagedMulticastSocketBinding.create(ManagedMulticastSocketBinding.java:40) > at org.jboss.as.network.SocketBindingManagerImpl.createMulticastSocket(SocketBindingManagerImpl.java:82) > at org.jboss.as.clustering.jgroups.ManagedSocketFactoryNew.createMulticastSocket(ManagedSocketFactoryNew.java:127) > at org.jgroups.util.Util.createMulticastSocket(Util.java:3089) > at org.jgroups.protocols.MPING.start(MPING.java:190) > at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:965) > at org.jgroups.JChannel.startStack(JChannel.java:890) > at org.jgroups.JChannel._preConnect(JChannel.java:553) > at org.jgroups.JChannel.connect(JChannel.java:288) > at org.jgroups.JChannel.connect(JChannel.java:279) > at org.wildfly.clustering.jgroups.spi.service.ChannelConnectorBuilder.start(ChannelConnectorBuilder.java:94) > {noformat} > This is because the MulticastSocket and DatagramSocket constructors call bind(...), but the ManagedBindingRegistry is not yet set. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5449) Custom socket factory for JGroups subsystem not set correctly

by Dennis Reed (JIRA)

[ https://issues.jboss.org/browse/WFLY-5449?page=com.atlassian.jira.plugin.... ] Dennis Reed resolved WFLY-5449. ------------------------------- Resolution: Done > Custom socket factory for JGroups subsystem not set correctly > ------------------------------------------------------------- > > Key: WFLY-5449 > URL: https://issues.jboss.org/browse/WFLY-5449 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.CR2 > Reporter: Dennis Reed > Assignee: Paul Ferraro > Priority: Blocker > Fix For: 10.0.0.CR4 > > > Wildfly's JChannelFactory tries to set a custom socket factory on the JGroups transport. > This is not the correct API to use, and it gets overwritten when the JGroups channel starts. > A custom socket factory should be set on the JChannel. > The only time the custom socket factory is currently used is if there's a race condition where two channels are started at the same time, and the custom factory is set just before the other channel uses it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5449) Custom socket factory for JGroups subsystem not set correctly

by Dennis Reed (JIRA)

[ https://issues.jboss.org/browse/WFLY-5449?page=com.atlassian.jira.plugin.... ] Dennis Reed commented on WFLY-5449: ----------------------------------- The issue with FD_SOCK's socket factory still not being set in EAP 6 after backporting this is a bug in JGroups, and does not affect Wildfly. Re-closing this issue. > Custom socket factory for JGroups subsystem not set correctly > ------------------------------------------------------------- > > Key: WFLY-5449 > URL: https://issues.jboss.org/browse/WFLY-5449 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.CR2 > Reporter: Dennis Reed > Assignee: Paul Ferraro > Priority: Blocker > Fix For: 10.0.0.CR4 > > > Wildfly's JChannelFactory tries to set a custom socket factory on the JGroups transport. > This is not the correct API to use, and it gets overwritten when the JGroups channel starts. > A custom socket factory should be set on the JChannel. > The only time the custom socket factory is currently used is if there's a race condition where two channels are started at the same time, and the custom factory is set just before the other channel uses it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1301) Clear pool statistics if created < destroyed

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-1301: -------------------------------------- Summary: Clear pool statistics if created < destroyed Key: JBJCA-1301 URL: https://issues.jboss.org/browse/JBJCA-1301 Project: IronJacamar Issue Type: Bug Components: Core Affects Versions: 1.2.6.Final, 1.0.33.Final, WildFly/IronJacamar 1.3.1.Final Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: WildFly/IronJacamar 1.3.2.Final, 1.0.34.Final, 1.2.7.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-970) Missing date coercion in constraint using an instance field or a declaration

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-970?page=com.atlassian.jira.plugin... ] Mario Fusco commented on DROOLS-970: ------------------------------------ Fixed by https://github.com/droolsjbpm/drools/commit/cc9a5eab6dc5e6e2a06ace59a3d0c... > Missing date coercion in constraint using an instance field or a declaration > ---------------------------------------------------------------------------- > > Key: DROOLS-970 > URL: https://issues.jboss.org/browse/DROOLS-970 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > > Automatic String to Date coercion is not performed in case the accessed field is not a getter method but an instance field of the class as in: > {code} > public class Person { > public java.util.Date date; > } > rule x when > Person( date < "1-Jan-2000" ) // Error flagged here, if... > then ...end > {code} > or when the class has proper a getter method but the constraint is expressed with a binding declaration as in: > {code} > rule x when > Person( $date: date, $date < "1-Jan-2000" ) > then ...end > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2015