10:04 p.m.
Synchronize access to static maps in MarshalFactory
---------------------------------------------------
Key: JBREM-1072
URL: https://jira.jboss.org/jira/browse/JBREM-1072
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.5.0.SP2 (Flounder) , 2.2.2.SP10
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.2.2.SP11, 2.5.0.SP3 (Flounder)
Users have experienced the exception
org.jboss.remoting.marshal.InvalidMarshallingResource: Can not find a valid marshaller for
data type: serializable
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:79)
at org.jboss.remoting.Client.invoke(Client.java:1634)
at org.jboss.remoting.Client.invoke(Client.java:548)
at
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:67)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107)
This is strange, since a marshaller for the datatype "serializable" is hardcoded
in org.jboss.remoting.marshal.MarshalFactory. However, access to the static Map
marshallers is not synchronized, so it's possible that one subsystem is adding a
marshaller (e.g., EJB2, JBossMessaging) at the same time that EJB3 is trying to extract a
marshaller. The same observation applies to unmarshallers.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:01 a.m.
New subject: [JBoss JIRA] Updated: (JBREM-1072) Synchronize access to static maps in MarshalFactory
[
https://jira.jboss.org/jira/browse/JBREM-1072?page=com.atlassian.jira.plu...
]
Ron Sigal updated JBREM-1072:
-----------------------------
Attachment: jboss-remoting.jar
Attached jboss-remoting.jar in which the Maps in MarshalFactory are synchronized.
jboss-remoting.jar identifies itself:
$ java -jar jboss-remoting.jar
JBossRemoting Version 2.2.2.SP10+JBREM-1041+1042+1045+1050+1052+1055+1056+1069+1070+1072
Synchronize access to static maps in MarshalFactory
---------------------------------------------------
Key: JBREM-1072
URL: https://jira.jboss.org/jira/browse/JBREM-1072
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.2.2.SP10, 2.5.0.SP2 (Flounder)
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.2.2.SP11, 2.5.0.SP3 (Flounder)
Attachments: jboss-remoting.jar
Users have experienced the exception
org.jboss.remoting.marshal.InvalidMarshallingResource: Can not find a valid marshaller
for data type: serializable
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:79)
at org.jboss.remoting.Client.invoke(Client.java:1634)
at org.jboss.remoting.Client.invoke(Client.java:548)
at
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:67)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107)
This is strange, since a marshaller for the datatype "serializable" is
hardcoded in org.jboss.remoting.marshal.MarshalFactory. However, access to the static Map
marshallers is not synchronized, so it's possible that one subsystem is adding a
marshaller (e.g., EJB2, JBossMessaging) at the same time that EJB3 is trying to extract a
marshaller. The same observation applies to unmarshallers.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:34 p.m.
New subject: [JBoss JIRA] Closed: (JBREM-1072) Synchronize access to static maps in MarshalFactory
[
https://jira.jboss.org/jira/browse/JBREM-1072?page=com.atlassian.jira.plu...
]
Ron Sigal closed JBREM-1072.
----------------------------
Resolution: Done
There are no special unit tests, but no unusual problems have been detected in any test
suite runs.
Synchronize access to static maps in MarshalFactory
---------------------------------------------------
Key: JBREM-1072
URL: https://jira.jboss.org/jira/browse/JBREM-1072
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.2.2.SP10, 2.5.0.SP2 (Flounder)
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.2.2.SP11, 2.5.0.SP3 (Flounder)
Attachments: jboss-remoting.jar
Users have experienced the exception
org.jboss.remoting.marshal.InvalidMarshallingResource: Can not find a valid marshaller
for data type: serializable
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:79)
at org.jboss.remoting.Client.invoke(Client.java:1634)
at org.jboss.remoting.Client.invoke(Client.java:548)
at
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:67)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107)
This is strange, since a marshaller for the datatype "serializable" is
hardcoded in org.jboss.remoting.marshal.MarshalFactory. However, access to the static Map
marshallers is not synchronized, so it's possible that one subsystem is adding a
marshaller (e.g., EJB2, JBossMessaging) at the same time that EJB3 is trying to extract a
marshaller. The same observation applies to unmarshallers.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:10 p.m.
New subject: [JBoss JIRA] Commented: (JBREM-1072) Synchronize access to static maps in MarshalFactory
[
https://jira.jboss.org/jira/browse/JBREM-1072?page=com.atlassian.jira.plu...
]
Ron Sigal commented on JBREM-1072:
----------------------------------
Changes commited to 2.2 and 2.x branches.
Synchronize access to static maps in MarshalFactory
---------------------------------------------------
Key: JBREM-1072
URL: https://jira.jboss.org/jira/browse/JBREM-1072
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.2.2.SP10, 2.5.0.SP2 (Flounder)
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.2.2.SP11, 2.5.0.SP3 (Flounder)
Attachments: jboss-remoting.jar
Users have experienced the exception
org.jboss.remoting.marshal.InvalidMarshallingResource: Can not find a valid marshaller
for data type: serializable
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:79)
at org.jboss.remoting.Client.invoke(Client.java:1634)
at org.jboss.remoting.Client.invoke(Client.java:548)
at
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:67)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107)
This is strange, since a marshaller for the datatype "serializable" is
hardcoded in org.jboss.remoting.marshal.MarshalFactory. However, access to the static Map
marshallers is not synchronized, so it's possible that one subsystem is adding a
marshaller (e.g., EJB2, JBossMessaging) at the same time that EJB3 is trying to extract a
marshaller. The same observation applies to unmarshallers.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:57 a.m.
New subject: [JBoss JIRA] Commented: (JBREM-1072) Synchronize access to static maps in MarshalFactory
[
https://jira.jboss.org/jira/browse/JBREM-1072?page=com.atlassian.jira.plu...
]
roirex commented on JBREM-1072:
-------------------------------
This is not solved completly, at least I still get the error with 2.2.2.SP11 (from svn).
However I think I can see the reason (or maybe I created my client wrong?).
In org.jboss.remoting.MicroRemoteClientInvoker the method:
private String getDataType()
changes a member variable "dataType", but if MicroRemoteClientInvoker is shared
between threads (which it is in my client) the method can some times return
"null". The exception might still say "Can not find a valid marshaller for
data type: serializable" because getDataType() is then called again, this time
returning the correct value.
At least, stop caching the value, fixed my client.
Synchronize access to static maps in MarshalFactory
---------------------------------------------------
Key: JBREM-1072
URL: https://jira.jboss.org/jira/browse/JBREM-1072
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.2.2.SP10, 2.5.0.SP2 (Flounder)
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.2.2.SP11, 2.5.0.SP3 (Flounder)
Attachments: jboss-remoting.jar
Users have experienced the exception
org.jboss.remoting.marshal.InvalidMarshallingResource: Can not find a valid marshaller
for data type: serializable
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:79)
at org.jboss.remoting.Client.invoke(Client.java:1634)
at org.jboss.remoting.Client.invoke(Client.java:548)
at
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:67)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107)
This is strange, since a marshaller for the datatype "serializable" is
hardcoded in org.jboss.remoting.marshal.MarshalFactory. However, access to the static Map
marshallers is not synchronized, so it's possible that one subsystem is adding a
marshaller (e.g., EJB2, JBossMessaging) at the same time that EJB3 is trying to extract a
marshaller. The same observation applies to unmarshallers.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:15 p.m.
New subject: [JBoss JIRA] Commented: (JBREM-1072) Synchronize access to static maps in MarshalFactory
[
https://jira.jboss.org/jira/browse/JBREM-1072?page=com.atlassian.jira.plu...
]
Ron Sigal commented on JBREM-1072:
----------------------------------
Eureka! How did I miss it? Thanks, roirex!
See JBREM-1109 " Eliminate race in MicroRemoteClientInvoker.getDataType()".
Synchronize access to static maps in MarshalFactory
---------------------------------------------------
Key: JBREM-1072
URL: https://jira.jboss.org/jira/browse/JBREM-1072
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.2.2.SP10, 2.5.0.SP2 (Flounder)
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.2.2.SP11, 2.5.0.SP3 (Flounder)
Attachments: jboss-remoting.jar
Users have experienced the exception
org.jboss.remoting.marshal.InvalidMarshallingResource: Can not find a valid marshaller
for data type: serializable
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:79)
at org.jboss.remoting.Client.invoke(Client.java:1634)
at org.jboss.remoting.Client.invoke(Client.java:548)
at
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:67)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107)
This is strange, since a marshaller for the datatype "serializable" is
hardcoded in org.jboss.remoting.marshal.MarshalFactory. However, access to the static Map
marshallers is not synchronized, so it's possible that one subsystem is adding a
marshaller (e.g., EJB2, JBossMessaging) at the same time that EJB3 is trying to extract a
marshaller. The same observation applies to unmarshallers.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5733
days inactive
5812
days old
jboss-remoting-issues@lists.jboss.org
5 comments
2 participants
participants (2)
-
roirex (JIRA) -
Ron Sigal (JIRA)