-
Enhancement
-
Resolution: Done
-
Major
-
4.0.23.Final
XNIO logging here can be vague:
WARN |(XNIO-1 task-9)|[org.xnio.future]| XNIO001003: Running IoFuture notifier org.jboss.ejb.protocol.remote.RemoteEJBReceiver$1@40e800e3 failed
java.lang.OutOfMemoryError: Java heap space
at org.jboss.marshalling.util.IdentityIntMap.resize(IdentityIntMap.java:163)
at org.jboss.marshalling.util.IdentityIntMap.put(IdentityIntMap.java:142)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:919)
at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1082)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1040)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1019)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1019)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:920)
at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1082)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1040)
It'd help if there was more info besides the generic RemoteEJBReceiver$1@ so one could discern what this related to. For instance, if possible logging something more like 'method name of bean named Hello for appname modulename ejb-client distinctname'
This customer is migrating from EAP 4.3, which had operations in a single thread. They liked this for the ease of correlating relevant events. With current logging from such forked XNIO tasks, making correlations to other threads or calls is harder.
- is blocked by
-
-
- Resolved
-
- is cloned by
-
-
- Closed
-
- is incorporated by
-
WFLY-12615 Upgrade jboss-ejb-client to 4.0.25.Final
-
- Closed
-
- is related to
-
-
- Resolved
-
