March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-444) NOT conditional element is broken when used with subnetworks

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-444?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated DROOLS-444: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1072462 > NOT conditional element is broken when used with subnetworks > ------------------------------------------------------------ > > Key: DROOLS-444 > URL: https://issues.jboss.org/browse/DROOLS-444 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.Final, 6.0.1.Final > Reporter: Davide Sottara > Assignee: Mario Fusco > Priority: Critical > -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-444) NOT conditional element is broken when used with subnetworks

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-444?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-444: ---------------------------------- Assignee: Mario Fusco (was: Mark Proctor) > NOT conditional element is broken when used with subnetworks > ------------------------------------------------------------ > > Key: DROOLS-444 > URL: https://issues.jboss.org/browse/DROOLS-444 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.Final, 6.0.1.Final > Reporter: Davide Sottara > Assignee: Mario Fusco > Priority: Critical > -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1804) UDP: sending of multicasts fails after an ifdown / ifup cycle

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1804?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1804: --------------------------- Description: After an ifdown / if up cycle, sending of multicast messages over mcast_sock fails with an IOException (no such device). Sending unicast datagram packets works. SOLUTION: Catch the IOException on the send and set the interface again ({{MulticastSocket.setInterface()}}). This was confirmed to work. Perhaps count the number of failures and only reset the interface when the count exceeds a threshold was: After an ifdown / if up cycle, sending of multicast messages over mcast_sock fails with an IOException (no such device). Sending unicast datagram packets works. SOLUTION: Catch the IOException on the send and set the interface again ({{MulticastSocket.setInterface()}}). This was confirmed to work. > UDP: sending of multicasts fails after an ifdown / ifup cycle > ------------------------------------------------------------- > > Key: JGRP-1804 > URL: https://issues.jboss.org/browse/JGRP-1804 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.5 > > > After an ifdown / if up cycle, sending of multicast messages over mcast_sock fails with an IOException (no such device). Sending unicast datagram packets works. > SOLUTION: > Catch the IOException on the send and set the interface again ({{MulticastSocket.setInterface()}}). This was confirmed to work. > Perhaps count the number of failures and only reset the interface when the count exceeds a threshold -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1804) UDP: sending of multicasts fails after an ifdown / ifup cycle

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1804?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1804: --------------------------- Description: After an ifdown / if up cycle, sending / receiving of multicast messages over mcast_sock fails with an IOException (no such device). Sending / receiving unicast datagram packets works. SOLUTION: Catch the IOException on the send/receive and set the interface again ({{MulticastSocket.setInterface()}}). This was confirmed to work. Perhaps count the number of failures and only reset the interface when the count exceeds a threshold was: After an ifdown / if up cycle, sending of multicast messages over mcast_sock fails with an IOException (no such device). Sending unicast datagram packets works. SOLUTION: Catch the IOException on the send and set the interface again ({{MulticastSocket.setInterface()}}). This was confirmed to work. Perhaps count the number of failures and only reset the interface when the count exceeds a threshold > UDP: sending of multicasts fails after an ifdown / ifup cycle > ------------------------------------------------------------- > > Key: JGRP-1804 > URL: https://issues.jboss.org/browse/JGRP-1804 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.5 > > > After an ifdown / if up cycle, sending / receiving of multicast messages over mcast_sock fails with an IOException (no such device). Sending / receiving unicast datagram packets works. > SOLUTION: > Catch the IOException on the send/receive and set the interface again ({{MulticastSocket.setInterface()}}). This was confirmed to work. > Perhaps count the number of failures and only reset the interface when the count exceeds a threshold -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3061) Replace deprecated OPTIONAL dependency to MBean server in WS ServerConfigService

by Alessio Soldano (JIRA)

Alessio Soldano created WFLY-3061: ------------------------------------- Summary: Replace deprecated OPTIONAL dependency to MBean server in WS ServerConfigService Key: WFLY-3061 URL: https://issues.jboss.org/browse/WFLY-3061 Project: WildFly Issue Type: Task Security Level: Public (Everyone can see) Components: Web Services Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: 8.0.1.Final {noformat} builder.addDependency(DependencyType.OPTIONAL, MBEAN_SERVER_NAME, MBeanServer.class, serverConfig.getMBeanServerInjector()); {noformat} in org.jboss.as.webservices.service.ServerConfigService needs to be replaced. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1804) UDP: sending of multicasts fails after an ifdown / ifup cycle

by Bela Ban (JIRA)

Bela Ban created JGRP-1804: ------------------------------ Summary: UDP: sending of multicasts fails after an ifdown / ifup cycle Key: JGRP-1804 URL: https://issues.jboss.org/browse/JGRP-1804 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.5 After an ifdown / if up cycle, sending of multicast messages over mcast_sock fails with an IOException (no such device). Sending unicast datagram packets works. SOLUTION: Catch the IOException on the send and set the interface again ({{MulticastSocket.setInterface()}}). This was confirmed to work. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1804) UDP: sending of multicasts fails after an ifdown / ifup cycle

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1804?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1804: --------------------------- Forum Reference: https://sourceforge.net/p/javagroups/mailman/message/32034144/ (was: https://sourceforge.net/p/javagroups/mailman/message/32058114/) > UDP: sending of multicasts fails after an ifdown / ifup cycle > ------------------------------------------------------------- > > Key: JGRP-1804 > URL: https://issues.jboss.org/browse/JGRP-1804 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.5 > > > After an ifdown / if up cycle, sending of multicast messages over mcast_sock fails with an IOException (no such device). Sending unicast datagram packets works. > SOLUTION: > Catch the IOException on the send and set the interface again ({{MulticastSocket.setInterface()}}). This was confirmed to work. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1917) Support socket-binding attribute "client-mapping" in messaging subsystem

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-1917?page=com.atlassian.jira.plugin.... ] Jeff Mesnil resolved WFLY-1917. ------------------------------- Resolution: Rejected Preferred way to configure the messaging remote-connector is using outbound-socket-binding that allows to define the address that the client must use to connect to the server. > Support socket-binding attribute "client-mapping" in messaging subsystem > ------------------------------------------------------------------------ > > Key: WFLY-1917 > URL: https://issues.jboss.org/browse/WFLY-1917 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JMS > Affects Versions: 8.0.0.Alpha4 > Reporter: Justin Bertram > Assignee: Jeff Mesnil > > The messaging subsystem doesn't take into account the "client-mapping" attribute of the <socket-binding> when creating a <netty-connector>. This forces the user to manually configure a <connector> to support the desired behavior. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-441) drools-guvnor 5.5, declarative model, create more than one fact type, BPMN process does not load

by niraj gupta (JIRA)

[ https://issues.jboss.org/browse/DROOLS-441?page=com.atlassian.jira.plugin... ] niraj gupta commented on DROOLS-441: ------------------------------------ Thanks for update and appreciate your suggestions. I also have the same doubt that rebuilding/reloading of the package having some problem. But i am not getting exact location of the code for the fix. I tried the steps you suggested. I created 1st package like pkg1, then only one process proc1 and then build deploy. Now i created another 2nd package like pkg2, then only one declarative model like 1. | declare Mod1 2. | mid: Integer 3. | mname: String 4. | end 5. | 6. | declare Mod2 7. | bid: Integer 8. | end and save this model. but not build. now running the process execute perfectly, even modify multiple time the same process. But as soon as build the pkg2, and then update the process, it doesn't reflect new changes in the console. I am not seeing any exception, as you are telling 2nd build failure case. Also if you could help me to which build is having this fix, it would be great. Actually this fix is very important to us. Regards, Niraj > drools-guvnor 5.5, declarative model, create more than one fact type, BPMN process does not load > ------------------------------------------------------------------------------------------------ > > Key: DROOLS-441 > URL: https://issues.jboss.org/browse/DROOLS-441 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final > Environment: Tomcat 6.0.35, jBPM 5.5.Final > Reporter: niraj gupta > Assignee: Mark Proctor > Labels: drools-guvnor > > I am using ‘drools-guvnor 5.5.0.Final’ open source tool for designing the business process (BPMN2). I end up in an issue and looking for help. Following is the scenario > I created a package then process then after build, deploy execute successfully. Now I came back to guvnor and made few changes in the process. Then after same build, deploy execute successfully. But now this time I am creating a declarative model having 2 facts, also modifying business process. Then after same build, deploy execute successfully. This time modified/latest business process doesn’t load into console. This is my problem. However I trouble shoot and google following are my observations: > • I am running this application in tomcat 6.0.35 > • It works perfectly with POJO Model Jar approach. > • It works perfectly with declarative model but having single fact. > • I am not seeing any exceptions either in UI or console logs -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1156) add ability to configure local address and port on messaging subsystems connectors

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-1156?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-1156: ------------------------------ Affects Version/s: 8.0.0.Final > add ability to configure local address and port on messaging subsystems connectors > ---------------------------------------------------------------------------------- > > Key: WFLY-1156 > URL: https://issues.jboss.org/browse/WFLY-1156 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JMS > Affects Versions: 8.0.0.Final > Reporter: Andy Taylor > Assignee: Jeff Mesnil > -- 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

12 years, 2 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 March 2014