[JBoss JIRA] (JGRP-1864) UDP unable to bind to ephemeral port: port out of range:65536
by Ion Savin (JIRA)
[ https://issues.jboss.org/browse/JGRP-1864?page=com.atlassian.jira.plugin.... ]
Ion Savin commented on JGRP-1864:
---------------------------------
Hi Bela,
The issue appears on one of the CI machines:
http://ci.infinispan.org/viewLog.html?buildId=10213&tab=buildResultsDiv&b...
added some log message for the exception:
{noformat}
2014-07-30 11:26:28,477 | TRACE | ion(3)-127.0.0.1 | UDP | org.apache.log4j.Category 856 | 66 - org.jgroups - 3.5.0.Beta9 | failed to create ephemeral port: 16239 on /fe80:0:0:0:f816:3eff:fe3b:55a9%2
java.net.BindException: Cannot assign requested address
at java.net.PlainDatagramSocketImpl.bind0(Native Method)[:1.7.0_65]
at java.net.AbstractPlainDatagramSocketImpl.bind(AbstractPlainDatagramSocketImpl.java:95)[:1.7.0_65]
at java.net.DatagramSocket.bind(DatagramSocket.java:376)[:1.7.0_65]
at java.net.DatagramSocket.<init>(DatagramSocket.java:231)[:1.7.0_65]
at java.net.DatagramSocket.<init>(DatagramSocket.java:284)[:1.7.0_65]
at org.jgroups.util.DefaultSocketFactory.createDatagramSocket(DefaultSocketFactory.java:62)
at org.jgroups.protocols.UDP.createEphemeralDatagramSocket(UDP.java:477)
at org.jgroups.protocols.UDP.createSockets(UDP.java:359)
at org.jgroups.protocols.UDP.start(UDP.java:264)
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)
at org.infinispan.remoting.transport.jgroups.JGroupsTransport.start(JGroupsTransport.java:191)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.7.0_65]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)[:1.7.0_65]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.7.0_65]
at java.lang.reflect.Method.invoke(Method.java:606)[:1.7.0_65]
at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:168)
at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:869)
at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:638)
at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:627)
at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:530)
at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:221)
at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:563)
at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:529)
at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:409)
at org.infinispan.persistence.jpa.JpaConfigurationTest.testConfigBuilder(JpaConfigurationTest.java:52)
at org.infinispan.it.osgi.persistence.jpa.JpaConfigurationTest.testConfigBuilder(JpaConfigurationTest.java:27)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.7.0_65]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)[:1.7.0_65]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.7.0_65]
at java.lang.reflect.Method.invoke(Method.java:606)[:1.7.0_65]
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)[102:org.ops4j.pax.tipi.junit:4.11.0.1]
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at org.ops4j.pax.exam.invoker.junit.internal.ContainerTestRunner.runChild(ContainerTestRunner.java:67)
at org.ops4j.pax.exam.invoker.junit.internal.ContainerTestRunner.runChild(ContainerTestRunner.java:37)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)[102:org.ops4j.pax.tipi.junit:4.11.0.1]
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)[102:org.ops4j.pax.tipi.junit:4.11.0.1]
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)[102:org.ops4j.pax.tipi.junit:4.11.0.1]
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)[102:org.ops4j.pax.tipi.junit:4.11.0.1]
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)[102:org.ops4j.pax.tipi.junit:4.11.0.1]
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)[102:org.ops4j.pax.tipi.junit:4.11.0.1]
at org.junit.runner.JUnitCore.run(JUnitCore.java:160)
at org.junit.runner.JUnitCore.run(JUnitCore.java:138)
at org.ops4j.pax.exam.invoker.junit.internal.JUnitProbeInvoker.invokeViaJUnit(JUnitProbeInvoker.java:124)
at org.ops4j.pax.exam.invoker.junit.internal.JUnitProbeInvoker.findAndInvoke(JUnitProbeInvoker.java:97)
at org.ops4j.pax.exam.invoker.junit.internal.JUnitProbeInvoker.call(JUnitProbeInvoker.java:73)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.7.0_65]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)[:1.7.0_65]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.7.0_65]
at java.lang.reflect.Method.invoke(Method.java:606)[:1.7.0_65]
at org.ops4j.pax.exam.rbc.internal.RemoteBundleContextImpl.remoteCall(RemoteBundleContextImpl.java:80)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.7.0_65]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)[:1.7.0_65]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.7.0_65]
at java.lang.reflect.Method.invoke(Method.java:606)[:1.7.0_65]
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:322)[:1.7.0_65]
at sun.rmi.transport.Transport$1.run(Transport.java:177)[:1.7.0_65]
at sun.rmi.transport.Transport$1.run(Transport.java:174)[:1.7.0_65]
at java.security.AccessController.doPrivileged(Native Method)[:1.7.0_65]
at sun.rmi.transport.Transport.serviceCall(Transport.java:173)[:1.7.0_65]
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:556)[:1.7.0_65]
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:811)[:1.7.0_65]
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:670)[:1.7.0_65]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_65]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_65]
at java.lang.Thread.run(Thread.java:745)[:1.7.0_65]
{noformat}
the process wasn't running with -Djava.net.preferIPv4Stack=true
> 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)
11 years, 9 months
[JBoss JIRA] (WFLY-3607) jsr356: OnError always called on page reload
by Jeanfrancois Arcand (JIRA)
[ https://issues.jboss.org/browse/WFLY-3607?page=com.atlassian.jira.plugin.... ]
Jeanfrancois Arcand commented on WFLY-3607:
-------------------------------------------
I use 8.1.0.Final. Which version that was fixed so I can confirm? Thanks
> jsr356: OnError always called on page reload
> --------------------------------------------
>
> Key: WFLY-3607
> URL: https://issues.jboss.org/browse/WFLY-3607
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Reporter: Jeanfrancois Arcand
> Assignee: Stuart Douglas
> Priority: Minor
>
> When I reload (F5) with Chrome, any jsr356's Handler will be called with
> {noformat}
> 11:24:30,815 ERROR [org.atmosphere.container.JSR356Endpoint] (default I/O-3) : java.nio.channels.ClosedChannelException
> at io.undertow.server.protocol.framed.AbstractFramedChannel.receive(AbstractFramedChannel.java:260)
> at io.undertow.websockets.core.AbstractReceiveListener.handleEvent(AbstractReceiveListener.java:20)
> at io.undertow.websockets.core.AbstractReceiveListener.handleEvent(AbstractReceiveListener.java:15)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) [xnio-api-3.2.2.Final.jar:3.2.2.Final]
> at io.undertow.server.protocol.framed.AbstractFramedChannel$FrameReadListener.handleEvent(AbstractFramedChannel.java:632)
> at io.undertow.server.protocol.framed.AbstractFramedChannel$FrameReadListener.handleEvent(AbstractFramedChannel.java:618)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) [xnio-api-3.2.2.Final.jar:3.2.2.Final]
> at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) [xnio-api-3.2.2.Final.jar:3.2.2.Final]
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:87) [xnio-nio-3.2.2.Final.jar:3.2.2.Final]
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:539) [xnio-nio-3.2.2.Final.jar:3.2.2.Final]
> {noformat}
> Tomcat and Jetty won't invoke onError, so I'm curious to learn why Wildfly call onError.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (DROOLS-569) Property reactivity prevents index update
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-569?page=com.atlassian.jira.plugin... ]
Mario Fusco updated DROOLS-569:
-------------------------------
Labels: backport-to-6.0.x (was: )
> Property reactivity prevents index update
> -----------------------------------------
>
> Key: DROOLS-569
> URL: https://issues.jboss.org/browse/DROOLS-569
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Mario Fusco
> Assignee: Mario Fusco
> Labels: backport-to-6.0.x
> Fix For: 6.2.0.Beta1
>
>
> When a property is part of the pattern matching it can anyway be excluded from the property reactivity with a negative watch. Anyway if the property is also indexed this implies that when the fact is modified it skips not only the modification propagation (as requested) but also the update of the corresponding index causing an inconsistency.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (DROOLS-569) Property reactivity prevents index update
by Mario Fusco (JIRA)
Mario Fusco created DROOLS-569:
----------------------------------
Summary: Property reactivity prevents index update
Key: DROOLS-569
URL: https://issues.jboss.org/browse/DROOLS-569
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Mario Fusco
Assignee: Mario Fusco
When a property is part of the pattern matching it can anyway be excluded from the property reactivity with a negative watch. Anyway if the property is also indexed this implies that when the fact is modified it skips not only the modification propagation (as requested) but also the update of the corresponding index causing an inconsistency.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (DROOLS-568) Module dependencies missing from brms and bpms layers to support remote runtime engines
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-568?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on DROOLS-568:
------------------------------------------------
Kris Verlaenen <kverlaen(a)redhat.com> changed the Status of [bug 1124885|https://bugzilla.redhat.com/show_bug.cgi?id=1124885] from NEW to ASSIGNED
> Module dependencies missing from brms and bpms layers to support remote runtime engines
> ---------------------------------------------------------------------------------------
>
> Key: DROOLS-568
> URL: https://issues.jboss.org/browse/DROOLS-568
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: JBoss EAP 6.3
> Reporter: David Ward
> Assignee: Jeremy Lindop
>
> Regarding artifacts:
> org.kie:kie-eap-distributions-brms-layer::6.1.0.CR2
> org.kie:kie-eap-integration-brms:brms-layer:6.0.2-redhat-7
> org.kie:kie-eap-distributions-bpms-layer::6.1.0.CR2
> org.kie:kie-eap-integration-bpms:bpms-layer:6.0.2-redhat-7
> And these modules:
> modules/system/layers/brms/org/kie/main/module.xml
> modules/system/layers/bpms/org/kie/main/module.xml
> There are missing libraries needed to support the remote rest and jms runtime engine factories (and associated builders):
> org.kie.services.client.api.RemoteJmsRuntimeEngineFactory/Builder
> org.kie.services.client.api.RemoteRestRuntimeEngineFactory/Builder
> Including at least these resource-roots:
> org.kie.remote:kie-services-client
> org.kie.remote:kie-services-jaxb
> and this dependency module:
> org.jboss.resteasy:resteasy-jackson-provider
> (Although still validating other possible dependencies.)
> Without having all the necessary libraries included and dependencies linked, using the RemoteRuntimeEngines via kie-services-client is not possible.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (DROOLS-568) Module dependencies missing from brms and bpms layers to support remote runtime engines
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-568?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated DROOLS-568:
-------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1124885
> Module dependencies missing from brms and bpms layers to support remote runtime engines
> ---------------------------------------------------------------------------------------
>
> Key: DROOLS-568
> URL: https://issues.jboss.org/browse/DROOLS-568
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: JBoss EAP 6.3
> Reporter: David Ward
> Assignee: Jeremy Lindop
>
> Regarding artifacts:
> org.kie:kie-eap-distributions-brms-layer::6.1.0.CR2
> org.kie:kie-eap-integration-brms:brms-layer:6.0.2-redhat-7
> org.kie:kie-eap-distributions-bpms-layer::6.1.0.CR2
> org.kie:kie-eap-integration-bpms:bpms-layer:6.0.2-redhat-7
> And these modules:
> modules/system/layers/brms/org/kie/main/module.xml
> modules/system/layers/bpms/org/kie/main/module.xml
> There are missing libraries needed to support the remote rest and jms runtime engine factories (and associated builders):
> org.kie.services.client.api.RemoteJmsRuntimeEngineFactory/Builder
> org.kie.services.client.api.RemoteRestRuntimeEngineFactory/Builder
> Including at least these resource-roots:
> org.kie.remote:kie-services-client
> org.kie.remote:kie-services-jaxb
> and this dependency module:
> org.jboss.resteasy:resteasy-jackson-provider
> (Although still validating other possible dependencies.)
> Without having all the necessary libraries included and dependencies linked, using the RemoteRuntimeEngines via kie-services-client is not possible.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (WFLY-3692) Update testsuite xslt scripts to be version independent
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-3692?page=com.atlassian.jira.plugin.... ]
Paul Ferraro closed WFLY-3692.
------------------------------
Resolution: Duplicate Issue
Duplicate of WFLY-3575
> Update testsuite xslt scripts to be version independent
> -------------------------------------------------------
>
> Key: WFLY-3692
> URL: https://issues.jboss.org/browse/WFLY-3692
> Project: WildFly
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Clustering
> Affects Versions: 8.1.0.Final
> Reporter: Paul Ferraro
> Assignee: Radoslav Husar
> Fix For: 9.0.0.Beta1
>
>
> We use a number of xslt scripts to transform server configuration for our tests. While some of these scripts are written in a subsystem version independent way, not all are. We should fix this so that new subsystem versions don't require changes to these files.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (DROOLS-568) Module dependencies missing from brms and bpms layers to support remote runtime engines
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-568?page=com.atlassian.jira.plugin... ]
Edson Tirelli updated DROOLS-568:
---------------------------------
Assignee: Jeremy Lindop (was: Mark Proctor)
> Module dependencies missing from brms and bpms layers to support remote runtime engines
> ---------------------------------------------------------------------------------------
>
> Key: DROOLS-568
> URL: https://issues.jboss.org/browse/DROOLS-568
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: JBoss EAP 6.3
> Reporter: David Ward
> Assignee: Jeremy Lindop
>
> Regarding artifacts:
> org.kie:kie-eap-distributions-brms-layer::6.1.0.CR2
> org.kie:kie-eap-integration-brms:brms-layer:6.0.2-redhat-7
> org.kie:kie-eap-distributions-bpms-layer::6.1.0.CR2
> org.kie:kie-eap-integration-bpms:bpms-layer:6.0.2-redhat-7
> And these modules:
> modules/system/layers/brms/org/kie/main/module.xml
> modules/system/layers/bpms/org/kie/main/module.xml
> There are missing libraries needed to support the remote rest and jms runtime engine factories (and associated builders):
> org.kie.services.client.api.RemoteJmsRuntimeEngineFactory/Builder
> org.kie.services.client.api.RemoteRestRuntimeEngineFactory/Builder
> Including at least these resource-roots:
> org.kie.remote:kie-services-client
> org.kie.remote:kie-services-jaxb
> and this dependency module:
> org.jboss.resteasy:resteasy-jackson-provider
> (Although still validating other possible dependencies.)
> Without having all the necessary libraries included and dependencies linked, using the RemoteRuntimeEngines via kie-services-client is not possible.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months