Re: [jboss-user] [Beginner's Corner] - EJB3 SSL tutorial
by Andrew Gronosky
Andrew Gronosky [http://community.jboss.org/people/agronosky] replied to the discussion
"EJB3 SSL tutorial"
To view the discussion, visit: http://community.jboss.org/message/533974#533974
--------------------------------------------------------------
Actually, I wrote a bit too soon when I said it worked perfectly. It works when the client and the server are running on the same host, but I run into problems when I run the client from a different host.
On the client side, I updated jndi.properties to point to the JNDI service on the server. I verified that the same jndi.properties do work for non-SSL EJBS (using the stateless session bean example from the tutorials) so it's not a basic connectivity problem.
There's something I'm still missing here... I've tried making my own certs/keystores using the exact host names, but it didn't seem to help.
[java] Exception in thread "main" javax.naming.NamingException: Could not dereference object [Root exception is org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [sslsocket://0.0.0.0:3843/]]
[java] at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1504)
[java] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
[java] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
[java] at javax.naming.InitialContext.lookup(InitialContext.java:409)
[java] at org.jboss.tutorial.ssl.client.Client.main(Client.java:45)
[java] Caused by: org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [sslsocket://0.0.0.0:3843/]
[java] at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:776)
[java] at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:165)
[java] at org.jboss.remoting.Client.invoke(Client.java:1724)
[java] at org.jboss.remoting.Client.invoke(Client.java:629)
[java] at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
[java] at org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invoke(IsLocalProxyFactoryInterceptor.java:72)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
[java] at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
[java] at $Proxy0.createProxyBusiness(Unknown Source)
[java] at org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFactory.createProxy(SessionProxyObjectFactory.java:129)
[java] at org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSessionProxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
[java] at org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectInstance(ProxyObjectFactory.java:158)
[java] at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:321)
[java] at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
[java] at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1496)
[java] ... 4 more
[java] Caused by: java.net.ConnectException: Connection refused
[java] at java.net.PlainSocketImpl.socketConnect(Native Method)
[java] at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:310)
[java] at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:174)
[java] at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:163)
[java] at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:384)
[java] at java.net.Socket.connect(Socket.java:542)
[java] at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:570)
[java] at org.jboss.remoting.transport.sslsocket.SSLSocketClientInvoker.connect(SSLSocketClientInvoker.java:243)
[java] at org.jboss.remoting.transport.sslsocket.SSLSocketClientInvoker.createSocket(SSLSocketClientInvoker.java:186)
[java] at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:1089)
[java] at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:762)
[java] at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:165)
[java] at org.jboss.remoting.Client.invoke(Client.java:1724)
[java] at org.jboss.remoting.Client.invoke(Client.java:629)
[java] at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
[java] at org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invoke(IsLocalProxyFactoryInterceptor.java:72)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
[java] at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
[java] at $Proxy0.createProxyBusiness(Unknown Source)
[java] at org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFactory.createProxy(SessionProxyObjectFactory.java:129)
[java] at org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSessionProxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
[java] at org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectInstance(ProxyObjectFactory.java:158)
[java] at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:321)
[java] at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
[java] at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1496)
[java] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
[java] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
[java] at javax.naming.InitialContext.lookup(InitialContext.java:409)
[java] at org.jboss.tutorial.ssl.client.Client.main(Client.java:45)
[java] at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:72)
[java] ... 15 more
[java] Java Result: 1
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/533974#533974]
Start a new discussion in Beginner's Corner at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years, 3 months
[JBoss Cache] - Is jgroup.jar needed while running jboss cache inside Jboss with default configuration?
by Mady kaba
Mady kaba [http://community.jboss.org/people/bateka] created the discussion
"Is jgroup.jar needed while running jboss cache inside Jboss with default configuration?"
To view the discussion, visit: http://community.jboss.org/message/533958#533958
--------------------------------------------------------------
We are having troubles using jboss cache inside jboss running the default configuration.
We are seeing the following messages from two diffentents JBoss Server instances developpment and staging.
Both instances are running the default config where an application including jgroup.jar lib package in a war file inside an ear File deployed on each Server. The Server should not build a cluster. But they seems trying to discover each other.
My questions are the following:
1 Is it possible to run jboss cache with the default JBoss configuration?
2 Is the jgroup.jar lib needed to run a non clustered(non cluster enabled) JBoss Server instance?
3 How to avoid the that the staging and the production instances build a cluster?
Developmment Node
2010-03-22 20:51:12,905 WARN [org.jgroups.protocols.pbcast.GMS] GMS flush by coordinator at 192.168.218.39:33149 failed
2010-03-22 20:51:24,969 WARN [org.jgroups.protocols.pbcast.GMS] GMS flush by coordinator at 192.168.218.39:33149 failed
2010-03-22 20:51:37,033 WARN [org.jgroups.protocols.pbcast.GMS] GMS flush by coordinator at 192.168.218.39:33149 failed
2010-03-22 20:51:49,097 WARN [org.jgroups.protocols.pbcast.GMS] GMS flush by coordinator at 192.168.218.39:33149 failed
Staging Node
2010-03-19 13:25:34,812 WARN [org.jgroups.protocols.pbcast.GMS] GMS flush by coordinator at 192.168.218.39:33149 failed
2010-03-19 13:25:39,816 WARN [org.jgroups.protocols.pbcast.GMS] 192.168.218.39:33149 failed to collect all ACKs (1) for mcasted view [192.168.218.39:33149|18] [192.168.218.39:33149, 192.168.218.41:33141] after 5000ms, missing ACKs from [192.168.218.41:33141] (received=[192.168.218.39:33149, 192.168.218.40:33145]), local_addr=192.168.218.39:33149
2010-03-19 13:35:42,761 WARN [org.jgroups.protocols.pbcast.GMS] Merge aborted. Merge leader did not get MergeData from all subgroup coordinators [192.168.218.39:33149, 192.168.218.40:33164]
Thank you
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/533958#533958]
Start a new discussion in JBoss Cache at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years, 3 months