is RemoteContext thread-safe?
maxim.ivanov May 8, 2015 12:01 PMHi!
Strange exception catched in WF 8.2.0 by me. One of backend servers use caching for InitialContext. I know InitialContext is declared as not thread-safe thing but i see threads locking in HaRemoteNamingStore sources and no reasons for threading problems in RemoteContext
What can be reason for this exception? i can't reproduce it, because it's "floating error". I can connect to server via telnet manually without any problems while have this exception in app.
Someone experienced with problem like this?
javax.naming.CommunicationException: Failed to connect to any server. Servers tried: [remote://ws1.oem.kabra.ru:4447 (java.nio.channels.ClosedByInterruptException)]
at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:244)
at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:135)
at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:272)
at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:87)
at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:129)
at javax.naming.InitialContext.lookup(InitialContext.java:417)
at ru.laximo.wsoem.agent.services.facades.AgentServiceLocator.lookupService(AgentServiceLocator.java:72)
at ru.laximo.wsoem.agent.services.facades.AgentServiceLocator.lookupPropertyManager(AgentServiceLocator.java:52)
at ru.laximo.wsoem.agent.services.facades.AgentServiceLocator.lookupPropertyManager(AgentServiceLocator.java:87)
at ru.laximo.wsoem.agent.services.legacy.CommandTask.listQuickDetail(CommandTask.java:349)
at ru.laximo.wsoem.agent.services.legacy.CommandTask.call(CommandTask.java:150)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)