[JBoss JIRA] (WFLY-7353) CDI bean-discovery-mode does not default to "annotated"
by Martin Kouba (JIRA)
[ https://issues.jboss.org/browse/WFLY-7353?page=com.atlassian.jira.plugin.... ]
Martin Kouba reassigned WFLY-7353:
----------------------------------
Assignee: Martin Kouba (was: Stuart Douglas)
> CDI bean-discovery-mode does not default to "annotated"
> -------------------------------------------------------
>
> Key: WFLY-7353
> URL: https://issues.jboss.org/browse/WFLY-7353
> Project: WildFly
> Issue Type: Feature Request
> Components: CDI / Weld
> Affects Versions: 10.0.0.Final
> Environment: EAP 7.0.2
> Reporter: Teresa Miyar
> Assignee: Martin Kouba
> Labels: support
> Attachments: demo-war-2.zip
>
>
> bean-discovery-mode does not default to "annotated" when you have a beans.xml version 1.1 without setting the discovery mode. That means that the bean without annotation gets injected.
> To reproduce:
> Download attached war, run into EAP 7.0.2, point browser to demo-war/servlet, check logs
> result:
> I see the log from bean call
> expected result:
> either WFLYCTL0184: New missing/unsatisfied dependencies on startup, or null pointer exception when accessing the servlet.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-7354) Custom NameService by sun.net.spi.nameservice.provider.n doesn't work on WildFly
by Osamu Nagano (JIRA)
Osamu Nagano created WFLY-7354:
----------------------------------
Summary: Custom NameService by sun.net.spi.nameservice.provider.n doesn't work on WildFly
Key: WFLY-7354
URL: https://issues.jboss.org/browse/WFLY-7354
Project: WildFly
Issue Type: Bug
Components: Class Loading
Affects Versions: 10.1.0.Final
Reporter: Osamu Nagano
Assignee: David Lloyd
Attachments: nameserviceProviderTest.zip
System property {{sun.net.spi.nameservice.provider.<n>}} allows a user to customize a NameService. It works on a standalone java, which is using JBoss Modules, if {{services="import"}} is added on sun.jdk module dependency and the sun.jdk module has the following additional dependencies.
{code}
<path name="sun/net/spi/nameservice"/>
<path name="sun/net/spi/nameservice/dns"/>
{code}
Though it doesn't work as a web application which has the same module path and the same dependency in jboss-deployment-structure.xml.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-7353) CDI bean-discovery-mode does not default to "annotated"
by Teresa Miyar (JIRA)
[ https://issues.jboss.org/browse/WFLY-7353?page=com.atlassian.jira.plugin.... ]
Teresa Miyar updated WFLY-7353:
-------------------------------
Security: (was: Security Issue)
> CDI bean-discovery-mode does not default to "annotated"
> -------------------------------------------------------
>
> Key: WFLY-7353
> URL: https://issues.jboss.org/browse/WFLY-7353
> Project: WildFly
> Issue Type: Feature Request
> Components: CDI / Weld
> Affects Versions: 10.0.0.Final
> Environment: EAP 7.0.2
> Reporter: Teresa Miyar
> Assignee: Stuart Douglas
> Labels: support
> Attachments: demo-war-2.zip
>
>
> bean-discovery-mode does not default to "annotated" when you have a beans.xml version 1.1 without setting the discovery mode. That means that the bean without annotation gets injected.
> To reproduce:
> Download attached war, run into EAP 7.0.2, point browser to demo-war/servlet, check logs
> result:
> I see the log from bean call
> expected result:
> either WFLYCTL0184: New missing/unsatisfied dependencies on startup, or null pointer exception when accessing the servlet.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-7352) XNIO bridge for Artemis doesn't work with newer versions of Netty and Artemis.
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFLY-7352?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil moved JBEAP-6518 to WFLY-7352:
------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-7352 (was: JBEAP-6518)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JMS
(was: ActiveMQ)
Affects Version/s: (was: 7.1.0.DR6)
> XNIO bridge for Artemis doesn't work with newer versions of Netty and Artemis.
> ------------------------------------------------------------------------------
>
> Key: WFLY-7352
> URL: https://issues.jboss.org/browse/WFLY-7352
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Priority: Blocker
>
> Test scenario:
> 1. Start server EAP 7.1.0.DR6 (with Artemis 1.4.0) with queue InQueue and OutQueue. Configure non-exclusive divert from InQueue to OutQueue.
> 2. Send large message to InQueue with scheduled delivery 10 seconds
> 3. Start consumer on OutQueue with receive timeout 1000ms and check that NO message was received
> 4. Start consumer on InQueue with receive timeout 1000ms and check that NO message was received
> 5. Start consumer on InQueue with receive timeout 11000ms and check that message is received
> 6. Start consumer on OutQueue with receive timeout 11000ms and check that message is received
> Result:
> Sometimes happens that consumer in step 3. receives a message. By checking trace logs, consumer in step 3. was receiving message 9664ms instead of ~1000ms.
> In attachment is trace log from client and server and test log with client thread dump during ~10s receive.
> Investigation:
> In the moment when client tries to receive a message there is send SessionForceConsumerDelivery packet by client:
> {code}
> 15:07:07,589 Thread-11 INFO [org.jboss.qa.artemis.test.messages.JmsMessagesTestCase$ReceiveThread:474] Start message comsumption from original queue with receive timeout 1000ms
> 15:07:07,590 Thread-11 TRACE [org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl:386] org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl@332729ad{consumerContext=ActiveMQConsumerContext{id=0}, queueName=jms.queue.OutQueue}:: receive(1000)
> 15:07:07,590 Thread-11 TRACE [org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl:191] org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl@332729ad{consumerContext=ActiveMQConsumerContext{id=0}, queueName=jms.queue.OutQueue}::receive(1000, false)
> 15:07:08,591 Thread-11 TRACE [org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl:370] org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl@332729ad{consumerContext=ActiveMQConsumerContext{id=0}, queueName=jms.queue.OutQueue}::Returning null
> 15:07:08,591 Thread-11 TRACE [org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl:392] org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl@332729ad{consumerContext=ActiveMQConsumerContext{id=0}, queueName=jms.queue.OutQueue}:: receive(1000) -> null, trying again with receive(0)
> 15:07:08,591 Thread-11 TRACE [org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl:191] org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl@332729ad{consumerContext=ActiveMQConsumerContext{id=0}, queueName=jms.queue.OutQueue}::receive(0, true)
> 15:07:08,592 Thread-11 TRACE [org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl:301] org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl@332729ad{consumerContext=ActiveMQConsumerContext{id=0}, queueName=jms.queue.OutQueue}::Forcing delivery
> 15:07:08,593 Thread-11 TRACE [org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl:248] Sending packet nonblocking PACKET(SessionForceConsumerDelivery)[type=78, channelID=11, packetObject=SessionForceConsumerDelivery, consumerID=0, sequence=0] on channeID=11
> 15:07:08,604 Thread-11 TRACE [org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl:286] Writing buffer for channelID=11
> {code}
> Response from server comes ~10s later - it's packet SessionReceiveMessage:
> {code}
> 15:07:17,250 Thread-0 (ActiveMQ-client-netty-threads-1138697171) TRACE [org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl:354] handling packet PACKET(SessionReceiveMessage)[type=75, chan
> nelID=11, packetObject=SessionReceiveMessage, message=ClientMessageImpl[messageID=44, durable=false, address=jms.queue.OutQueue,userID=null,properties=TypedProperties[_hornetq.forced.delivery.seq=0]], consumerID
> =0, deliveryCount=0]
> {code}
> in the mean time client is waiting on - ---org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.receive(ClientConsumerImpl.java:261):
> {noformat}
> wait(Long.MAX_VALUE);
> {noformat}
> and is waiting for notify. From server log I can see that SessionReceiveMessage was send at:
> {code}
> 15:07:08,621 TRACE [org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl] (Thread-18 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$2@39cb2b3a-1512482465)) Sending packet nonblocking PACKET(SessionReceiveMessage)[type=75, channelID=11, packetObject=SessionReceiveMessage, message=ServerMessage[messageID=44,durable=false,userID=null,priority=0, bodySize=50, timestamp=0,expiration=0, durable=false, address=jms.queue.OutQueue,properties=TypedProperties[_hornetq.forced.delivery.seq=0]]@1525441837, consumerID=0, deliveryCount=0] on channeID=11
> 15:07:08,633 TRACE [org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl] (Thread-18 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$2@39cb2b3a-1512482465)) Writing buffer for channelID=11
> {code}
> but it wasn't flushed and for some reason is actually send ~10s later with the large message:
> {code}
> 15:07:17,236 TRACE [org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl] (Thread-27 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$2@39cb2b3a-1512482465)) Sending pa
> cket nonblocking PACKET(SessionReceiveLargeMessage)[type=76, channelID=11, packetObject=SessionReceiveLargeMessage, consumerID=0, deliveryCount=1, largeMessageSize=409605, message=LargeServerMessage[messageID=40
> ,durable=true,userID=1befe4c2-920f-11e6-9ae8-3ca9f4349bfc,priority=4, timestamp=Fri Oct 14 15:07:07 CEST 2016,expiration=0, durable=true, address=jms.queue.OutQueue,properties=TypedProperties[__AMQ_CID=1bdc35af-
> 920f-11e6-9ae8-3ca9f4349bfc,_AMQ_SCHED_DELIVERY=1476450437224,_AMQ_ORIG_ADDRESS=jms.queue.InQueue,_AMQ_ORIG_MESSAGE_ID=36,counter=0,_AMQ_DUPL_ID=16c2be09-573a-4e02-a369-6a36c2f32fbd,_AMQ_LARGE_SIZE=409605]]@1994
> 218683] on channeID=11
> 15:07:17,246 TRACE [org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl] (Thread-27 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$2@39cb2b3a-1512482465)) Writing bu
> ffer for channelID=11
> 15:07:17,247 TRACE [org.xnio.nio.selector] (default I/O-1) Selected on sun.nio.ch.EPollSelectorImpl@61ea580a
> 15:07:17,247 TRACE [org.xnio.nio] (default I/O-1) Running task io.netty.channel.AbstractChannelHandlerContext$WriteAndFlushTask@5c93c5d7
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-1837) manual module testoutput is a bit disturbing NPE and dependencies missing
by Carlo de Wolf (JIRA)
[ https://issues.jboss.org/browse/WFLY-1837?page=com.atlassian.jira.plugin.... ]
Carlo de Wolf resolved WFLY-1837.
---------------------------------
Resolution: Out of Date
This bug has been filed against a WildFly version that is no longer in use.
If you would still like to see this bug fixed and are able to reproduce it against the latest version of WildFly, you are encouraged change the 'version' and reopen the bug.
> manual module testoutput is a bit disturbing NPE and dependencies missing
> -------------------------------------------------------------------------
>
> Key: WFLY-1837
> URL: https://issues.jboss.org/browse/WFLY-1837
> Project: WildFly
> Issue Type: Task
> Components: Test Suite
> Affects Versions: 8.0.0.Alpha3
> Reporter: Bartosz Baranowski
> Assignee: Carlo de Wolf
>
> Manual testmodule shows a lot of NPEs and dependency issues:
> {noformat}
> [org.jboss.as.ejb3] (EJB default - 2) JBAS014249: Error invoking method public abstract void org.jboss.as.test.manualmode.ejb.shutdown.RemoteLatch.testDone() on bean named LatchBean for appname modulename dep1 distinctname : java.lang.NullPointerException
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.invokeMethod(MethodInvocationMessageHandler.java:322)
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$100(MethodInvocationMessageHandler.java:70)
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:203)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_25]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_25]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> 13:06:07,613 ERROR [org.jboss.as.ejb3] (EJB default - 2) JBAS014250: Could not write method invocation failure for method public abstract void org.jboss.as.test.manualmode.ejb.shutdown.RemoteLatch.testDone() on bean named LatchBean for appname modulename dep1 distinctname due to: java.io.IOException: Stream is closed
> at org.xnio.streams.BufferPipeOutputStream.closed(BufferPipeOutputStream.java:58) [xnio-api-3.1.0.CR3.jar:3.1.0.CR3]
> at org.xnio.streams.BufferPipeOutputStream.checkClosed(BufferPipeOutputStream.java:64) [xnio-api-3.1.0.CR3.jar:3.1.0.CR3]
> at org.xnio.streams.BufferPipeOutputStream.write(BufferPipeOutputStream.java:90) [xnio-api-3.1.0.CR3.jar:3.1.0.CR3]
> at org.jboss.remoting3.remote.OutboundMessage.write(OutboundMessage.java:252)
> at java.io.DataOutputStream.write(DataOutputStream.java:107) [rt.jar:1.7.0_25]
> at org.jboss.as.ejb3.remote.protocol.AbstractMessageHandler$1.write(AbstractMessageHandler.java:217)
> at org.jboss.marshalling.OutputStreamByteOutput.write(OutputStreamByteOutput.java:56)
> at org.jboss.marshalling.SimpleDataOutput.shallowFlush(SimpleDataOutput.java:328)
> at org.jboss.marshalling.river.RiverMarshaller.writeString(RiverMarshaller.java:1451)
> at org.jboss.marshalling.river.RiverMarshaller.writeNewSerializableClass(RiverMarshaller.java:1362)
> at org.jboss.marshalling.river.RiverMarshaller.writeSerializableClass(RiverMarshaller.java:1345)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:883)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1063)
> at org.jboss.marshalling.river.RiverObjectOutputStream.defaultWriteObject(RiverObjectOutputStream.java:159)
> at java.lang.Throwable.writeObject(Throwable.java:984) [rt.jar:1.7.0_25]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_25]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_25]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25]
> at org.jboss.marshalling.reflect.SerializableClass.callWriteObject(SerializableClass.java:180)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1007)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:998)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:998)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:998)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:885)
> at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:62)
> at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:119)
> at org.jboss.as.ejb3.remote.protocol.AbstractMessageHandler.writeException(AbstractMessageHandler.java:112)
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$400(MethodInvocationMessageHandler.java:70)
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:213)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_25]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_25]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> Caused by: an exception which occurred:
> in field suppressedExceptions
> in object java.lang.NullPointerException@18e5c476
> {noformat}
> {noformat}
> 13:01:23,032 ERROR [org.jboss.as.controller.management-operation] (pool-2-thread-1) JBAS014612: Operation ("add") failed - address: ([
> ("host" => "master"),
> ("core-service" => "management"),
> ("management-interface" => "http-interface")
> ]): java.lang.NullPointerException
> at org.jboss.as.host.controller.operations.HttpManagementAddHandler.installHttpManagementServices(HttpManagementAddHandler.java:137) [wildfly-host-controller-8.0.0.Alpha4-SNAPSHOT.jar:8.0.0.Alpha4-SNAPSHOT]
> at org.jboss.as.host.controller.operations.HttpManagementAddHandler.performRuntime(HttpManagementAddHandler.java:97) [wildfly-host-controller-8.0.0.Alpha4-SNAPSHOT.jar:8.0.0.Alpha4-SNAPSHOT]
> at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:75) [wildfly-controller-8.0.0.Alpha4-SNAPSHOT.jar:8.0.0.Alpha4-SNAPSHOT]
> {noformat}
> {noformat}
> 13:01:23,493 ERROR [org.jboss.as.controller.management-operation] (pool-2-thread-1) JBAS014613: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("management-interface" => "native-interface")
> ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => [
> "jboss.remoting.authentication_provider.management is missing [jboss.server.path.\"jboss.server.temp.dir\"]",
> "jboss.remoting.endpoint.management.management.operation.handler is missing [jboss.as.server-controller]",
> "jboss.remoting.endpoint.management.channel.management is missing [jboss.remoting.endpoint.management.shutdown.executor]",
> "jboss.remoting.server.management is missing [jboss.binding.management-native, jboss.socket-binding-manager]"
> ]}
> 13:01:23,494 INFO [org.jboss.as.controller] (pool-2-thread-1) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.as.server-controller (missing) dependents: [service jboss.remoting.endpoint.management.management.operation.handler]
> service jboss.binding.management-native (missing) dependents: [service jboss.remoting.server.management]
> service jboss.remoting.endpoint.management.shutdown.executor (missing) dependents: [service jboss.remoting.endpoint.management.channel.management]
> service jboss.server.path."jboss.server.temp.dir" (missing) dependents: [service jboss.remoting.authentication_provider.management]
> service jboss.socket-binding-manager (missing) dependents: [service jboss.remoting.server.management]
> 13:01:23,495 INFO [org.jboss.as.server] (pool-2-thread-1) JBAS015888: Creating http management service using socket-binding (management-http)
> 13:01:23,496 ERROR [org.jboss.as.controller.management-operation] (pool-2-thread-1) JBAS014612: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("management-interface" => "http-interface")
> ]): org.jboss.msc.service.ServiceNotFoundException: Service service jboss.server.environment not found
> at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:668) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> at org.jboss.as.controller.OperationContextImpl$OperationContextServiceRegistry.getRequiredService(OperationContextImpl.java:1068) [wildfly-controller-8.0.0.Alpha4-SNAPSHOT.jar:8.0.0.Alpha4-
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-1837) manual module testoutput is a bit disturbing NPE and dependencies missing
by Carlo de Wolf (JIRA)
[ https://issues.jboss.org/browse/WFLY-1837?page=com.atlassian.jira.plugin.... ]
Carlo de Wolf reassigned WFLY-1837:
-----------------------------------
Assignee: Carlo de Wolf (was: JBoss SET)
> manual module testoutput is a bit disturbing NPE and dependencies missing
> -------------------------------------------------------------------------
>
> Key: WFLY-1837
> URL: https://issues.jboss.org/browse/WFLY-1837
> Project: WildFly
> Issue Type: Task
> Components: Test Suite
> Affects Versions: 8.0.0.Alpha3
> Reporter: Bartosz Baranowski
> Assignee: Carlo de Wolf
>
> Manual testmodule shows a lot of NPEs and dependency issues:
> {noformat}
> [org.jboss.as.ejb3] (EJB default - 2) JBAS014249: Error invoking method public abstract void org.jboss.as.test.manualmode.ejb.shutdown.RemoteLatch.testDone() on bean named LatchBean for appname modulename dep1 distinctname : java.lang.NullPointerException
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.invokeMethod(MethodInvocationMessageHandler.java:322)
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$100(MethodInvocationMessageHandler.java:70)
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:203)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_25]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_25]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> 13:06:07,613 ERROR [org.jboss.as.ejb3] (EJB default - 2) JBAS014250: Could not write method invocation failure for method public abstract void org.jboss.as.test.manualmode.ejb.shutdown.RemoteLatch.testDone() on bean named LatchBean for appname modulename dep1 distinctname due to: java.io.IOException: Stream is closed
> at org.xnio.streams.BufferPipeOutputStream.closed(BufferPipeOutputStream.java:58) [xnio-api-3.1.0.CR3.jar:3.1.0.CR3]
> at org.xnio.streams.BufferPipeOutputStream.checkClosed(BufferPipeOutputStream.java:64) [xnio-api-3.1.0.CR3.jar:3.1.0.CR3]
> at org.xnio.streams.BufferPipeOutputStream.write(BufferPipeOutputStream.java:90) [xnio-api-3.1.0.CR3.jar:3.1.0.CR3]
> at org.jboss.remoting3.remote.OutboundMessage.write(OutboundMessage.java:252)
> at java.io.DataOutputStream.write(DataOutputStream.java:107) [rt.jar:1.7.0_25]
> at org.jboss.as.ejb3.remote.protocol.AbstractMessageHandler$1.write(AbstractMessageHandler.java:217)
> at org.jboss.marshalling.OutputStreamByteOutput.write(OutputStreamByteOutput.java:56)
> at org.jboss.marshalling.SimpleDataOutput.shallowFlush(SimpleDataOutput.java:328)
> at org.jboss.marshalling.river.RiverMarshaller.writeString(RiverMarshaller.java:1451)
> at org.jboss.marshalling.river.RiverMarshaller.writeNewSerializableClass(RiverMarshaller.java:1362)
> at org.jboss.marshalling.river.RiverMarshaller.writeSerializableClass(RiverMarshaller.java:1345)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:883)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1063)
> at org.jboss.marshalling.river.RiverObjectOutputStream.defaultWriteObject(RiverObjectOutputStream.java:159)
> at java.lang.Throwable.writeObject(Throwable.java:984) [rt.jar:1.7.0_25]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_25]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_25]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25]
> at org.jboss.marshalling.reflect.SerializableClass.callWriteObject(SerializableClass.java:180)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1007)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:998)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:998)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:998)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:885)
> at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:62)
> at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:119)
> at org.jboss.as.ejb3.remote.protocol.AbstractMessageHandler.writeException(AbstractMessageHandler.java:112)
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$400(MethodInvocationMessageHandler.java:70)
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:213)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_25]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_25]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> Caused by: an exception which occurred:
> in field suppressedExceptions
> in object java.lang.NullPointerException@18e5c476
> {noformat}
> {noformat}
> 13:01:23,032 ERROR [org.jboss.as.controller.management-operation] (pool-2-thread-1) JBAS014612: Operation ("add") failed - address: ([
> ("host" => "master"),
> ("core-service" => "management"),
> ("management-interface" => "http-interface")
> ]): java.lang.NullPointerException
> at org.jboss.as.host.controller.operations.HttpManagementAddHandler.installHttpManagementServices(HttpManagementAddHandler.java:137) [wildfly-host-controller-8.0.0.Alpha4-SNAPSHOT.jar:8.0.0.Alpha4-SNAPSHOT]
> at org.jboss.as.host.controller.operations.HttpManagementAddHandler.performRuntime(HttpManagementAddHandler.java:97) [wildfly-host-controller-8.0.0.Alpha4-SNAPSHOT.jar:8.0.0.Alpha4-SNAPSHOT]
> at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:75) [wildfly-controller-8.0.0.Alpha4-SNAPSHOT.jar:8.0.0.Alpha4-SNAPSHOT]
> {noformat}
> {noformat}
> 13:01:23,493 ERROR [org.jboss.as.controller.management-operation] (pool-2-thread-1) JBAS014613: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("management-interface" => "native-interface")
> ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => [
> "jboss.remoting.authentication_provider.management is missing [jboss.server.path.\"jboss.server.temp.dir\"]",
> "jboss.remoting.endpoint.management.management.operation.handler is missing [jboss.as.server-controller]",
> "jboss.remoting.endpoint.management.channel.management is missing [jboss.remoting.endpoint.management.shutdown.executor]",
> "jboss.remoting.server.management is missing [jboss.binding.management-native, jboss.socket-binding-manager]"
> ]}
> 13:01:23,494 INFO [org.jboss.as.controller] (pool-2-thread-1) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.as.server-controller (missing) dependents: [service jboss.remoting.endpoint.management.management.operation.handler]
> service jboss.binding.management-native (missing) dependents: [service jboss.remoting.server.management]
> service jboss.remoting.endpoint.management.shutdown.executor (missing) dependents: [service jboss.remoting.endpoint.management.channel.management]
> service jboss.server.path."jboss.server.temp.dir" (missing) dependents: [service jboss.remoting.authentication_provider.management]
> service jboss.socket-binding-manager (missing) dependents: [service jboss.remoting.server.management]
> 13:01:23,495 INFO [org.jboss.as.server] (pool-2-thread-1) JBAS015888: Creating http management service using socket-binding (management-http)
> 13:01:23,496 ERROR [org.jboss.as.controller.management-operation] (pool-2-thread-1) JBAS014612: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("management-interface" => "http-interface")
> ]): org.jboss.msc.service.ServiceNotFoundException: Service service jboss.server.environment not found
> at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:668) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> at org.jboss.as.controller.OperationContextImpl$OperationContextServiceRegistry.getRequiredService(OperationContextImpl.java:1068) [wildfly-controller-8.0.0.Alpha4-SNAPSHOT.jar:8.0.0.Alpha4-
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (DROOLS-1340) IndexOutOfBoundsException when using query with 2 entry points
by Tibor Zimányi (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1340?page=com.atlassian.jira.plugi... ]
Tibor Zimányi updated DROOLS-1340:
----------------------------------
Description:
Sometimes, when using query with 2 entry points along with fireUntilHalt, the method getQueryResults fails with IndexOutOfBoundsException. See stacktrace here [1]. This was observed first in Jenkins environment running existing test QueryCepFireUntilHaltTest.withResultTest from drools repository. I managed to reproduce it locally looping the test with this code [2].
[1] http://pastebin.com/BBPsGty9
[2] http://pastebin.com/47y1dh1W
was:
Sometimes, when using query with 2 entry points along with fireUntilHalt, the method getQueryResults fails with IndexOutOfBoundsException. See stacktrace here [1]. This was observed first in Jenkins environment running existing test QueryCepFireUntilHaltTest.withResultTest from drools repository. I managed to reproduce it locally looping the test with this code:
@Test
public void testBla() {
for (int i = 0; i < 10000; i++) {
prepare();
try {
withResultTest();
} finally {
cleanup();
}
}
}
[1] http://pastebin.com/BBPsGty9
> IndexOutOfBoundsException when using query with 2 entry points
> --------------------------------------------------------------
>
> Key: DROOLS-1340
> URL: https://issues.jboss.org/browse/DROOLS-1340
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.5.0.Final
> Reporter: Tibor Zimányi
> Assignee: Mario Fusco
> Labels: reported-by-qe
>
> Sometimes, when using query with 2 entry points along with fireUntilHalt, the method getQueryResults fails with IndexOutOfBoundsException. See stacktrace here [1]. This was observed first in Jenkins environment running existing test QueryCepFireUntilHaltTest.withResultTest from drools repository. I managed to reproduce it locally looping the test with this code [2].
> [1] http://pastebin.com/BBPsGty9
> [2] http://pastebin.com/47y1dh1W
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (DROOLS-1340) IndexOutOfBoundsException when using query with 2 entry points
by Tibor Zimányi (JIRA)
Tibor Zimányi created DROOLS-1340:
-------------------------------------
Summary: IndexOutOfBoundsException when using query with 2 entry points
Key: DROOLS-1340
URL: https://issues.jboss.org/browse/DROOLS-1340
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 6.5.0.Final
Reporter: Tibor Zimányi
Assignee: Mario Fusco
Sometimes, when using query with 2 entry points along with fireUntilHalt, the method getQueryResults fails with IndexOutOfBoundsException. See stacktrace here [1]. This was observed first in Jenkins environment running existing test QueryCepFireUntilHaltTest.withResultTest from drools repository. I managed to reproduce it locally looping the test with this code:
@Test
public void testBla() {
for (int i = 0; i < 10000; i++) {
prepare();
try {
withResultTest();
} finally {
cleanup();
}
}
}
[1] http://pastebin.com/BBPsGty9
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (DROOLS-1339) NPE happens in TupleSetsImpl.setNextTuple()
by Hiroko Miura (JIRA)
Hiroko Miura created DROOLS-1339:
------------------------------------
Summary: NPE happens in TupleSetsImpl.setNextTuple()
Key: DROOLS-1339
URL: https://issues.jboss.org/browse/DROOLS-1339
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 6.4.0.Final
Reporter: Hiroko Miura
Assignee: Mario Fusco
Priority: Critical
In customer's performance test case, NPE happens in TupleSetsImpl.setNextTuple() with the following stack.
java.lang.NullPointerException
at org.drools.core.common.TupleSetsImpl.setNextTuple(TupleSetsImpl.java:352)
at org.drools.core.common.TupleSetsImpl.removeInsert(TupleSetsImpl.java:168)
at org.drools.core.phreak.RuleNetworkEvaluator.deleteChildLeftTuple(RuleNetworkEvaluator.java:729)
at org.drools.core.phreak.RuleNetworkEvaluator.unlinkAndDeleteChildLeftTuple(RuleNetworkEvaluator.java:721)
at org.drools.core.phreak.PhreakNotNode.doRightUpdates(PhreakNotNode.java:343)
at org.drools.core.phreak.PhreakNotNode.doNode(PhreakNotNode.java:74)
at org.drools.core.phreak.RuleNetworkEvaluator.switchOnDoBetaNode(RuleNetworkEvaluator.java:524)
at org.drools.core.phreak.RuleNetworkEvaluator.evalBetaNode(RuleNetworkEvaluator.java:505)
at org.drools.core.phreak.RuleNetworkEvaluator.evalNode(RuleNetworkEvaluator.java:341)
at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:301)
at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:136)
at org.drools.core.phreak.AddRemoveRule.forceFlushLeftTuple(AddRemoveRule.java:692)
at org.drools.core.phreak.AddRemoveRule.flushLeftTupleIfNecessary(AddRemoveRule.java:629)
at org.drools.core.reteoo.NotNode.assertObject(NotNode.java:161)
at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateAssertObject(CompositeObjectSinkAdapter.java:494)
at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:384)
at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:134)
at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateAssertObject(CompositeObjectSinkAdapter.java:494)
at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:384)
at org.drools.core.reteoo.ObjectTypeNode.propagateAssert(ObjectTypeNode.java:304)
at org.drools.core.phreak.PropagationEntry$Insert.execute(PropagationEntry.java:132)
at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:82)
at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:72)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.flushPropagations(StatefulKnowledgeSessionImpl.java:2053)
at org.drools.core.phreak.RuleExecutor.fire(RuleExecutor.java:128)
at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:74)
at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:960)
at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1303)
at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1241)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1336)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1327)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1308)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (DROOLS-1338) NPE happens in TupleSetsImpl.setNextTuple()
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1338?page=com.atlassian.jira.plugi... ]
Mario Fusco commented on DROOLS-1338:
-------------------------------------
[~hiroko] Where can I find a reproducer for this issue?
> NPE happens in TupleSetsImpl.setNextTuple()
> -------------------------------------------
>
> Key: DROOLS-1338
> URL: https://issues.jboss.org/browse/DROOLS-1338
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.4.0.Final
> Reporter: Hiroko Miura
> Assignee: Mario Fusco
> Priority: Critical
> Labels: support
>
> In customer's performance test case, NPE happens in TupleSetsImpl.setNextTuple() with the following stack.
> java.lang.NullPointerException
> at org.drools.core.common.TupleSetsImpl.setNextTuple(TupleSetsImpl.java:352)
> at org.drools.core.common.TupleSetsImpl.removeInsert(TupleSetsImpl.java:168)
> at org.drools.core.phreak.RuleNetworkEvaluator.deleteChildLeftTuple(RuleNetworkEvaluator.java:729)
> at org.drools.core.phreak.RuleNetworkEvaluator.unlinkAndDeleteChildLeftTuple(RuleNetworkEvaluator.java:721)
> at org.drools.core.phreak.PhreakNotNode.doRightUpdates(PhreakNotNode.java:343)
> at org.drools.core.phreak.PhreakNotNode.doNode(PhreakNotNode.java:74)
> at org.drools.core.phreak.RuleNetworkEvaluator.switchOnDoBetaNode(RuleNetworkEvaluator.java:524)
> at org.drools.core.phreak.RuleNetworkEvaluator.evalBetaNode(RuleNetworkEvaluator.java:505)
> at org.drools.core.phreak.RuleNetworkEvaluator.evalNode(RuleNetworkEvaluator.java:341)
> at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:301)
> at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:136)
> at org.drools.core.phreak.AddRemoveRule.forceFlushLeftTuple(AddRemoveRule.java:692)
> at org.drools.core.phreak.AddRemoveRule.flushLeftTupleIfNecessary(AddRemoveRule.java:629)
> at org.drools.core.reteoo.NotNode.assertObject(NotNode.java:161)
> at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateAssertObject(CompositeObjectSinkAdapter.java:494)
> at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:384)
> at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:134)
> at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateAssertObject(CompositeObjectSinkAdapter.java:494)
> at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:384)
> at org.drools.core.reteoo.ObjectTypeNode.propagateAssert(ObjectTypeNode.java:304)
> at org.drools.core.phreak.PropagationEntry$Insert.execute(PropagationEntry.java:132)
> at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:82)
> at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:72)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.flushPropagations(StatefulKnowledgeSessionImpl.java:2053)
> at org.drools.core.phreak.RuleExecutor.fire(RuleExecutor.java:128)
> at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:74)
> at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:960)
> at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1303)
> at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1241)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1336)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1327)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1308)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months