[jboss-jira] [JBoss JIRA] (WFLY-1837) manual module testoutput is a bit disturbing NPE and dependencies missing
Bartosz Baranowski (JIRA)
jira-events at lists.jboss.org
Tue Aug 6 07:43:26 EDT 2013
[ https://issues.jboss.org/browse/WFLY-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bartosz Baranowski updated WFLY-1837:
-------------------------------------
Summary: manual module testoutput is a bit disturbing NPE and dependencies missing (was: manual module testoutput reeks of NPEs)
> 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: JBoss SET
> Fix For: 8.0.0.Alpha4
>
>
> 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 at 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 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
More information about the jboss-jira
mailing list