[Remoting] - Re: How to set ping timeout of ConnectionValidator?
by ron.sigal＠jboss.com
Hi Mark,
The InvokerLocator you see on the server side is the one that matters, and it has the desired parameters. The one you see on the client side,
| 13:11:58,759 DEBUG [Client] starting callback Connector: InvokerLocator [bisocket://10.101.110.64:1878752913/callback
| ?callbackServerHost=10.101.110.64&callbackServerPort=1878752913&callbackServerProtocol=bisocket&clientMaxPoolSize=1&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&datatype=jms&guid=a2t321s-u0b7nn-fnqgzrc3-1-fnqgzr
| xj-g&isCallbackServer=true&onewayThreadPool=org.jboss.jms.server.remoting.DirectThreadPool&serverSocketClass=org.jboss.jms.server.remoting]
|
is for the callback Connector to which the server pushes messages, which isn't related to the ConnectionValidator, and you can ignore it.
What should happen in JBossMessaging is that it sends the InvokerLocator from the server to the client, where it is used to create the necessary instances of org.jboss.remoting.Client. See, for example, the JBM class org.jboss.jms.client.remoting.JMSRemotingConnection. When the Client creates a ConnectionValidator, the ConnectionValidator uses the Client's parameters, including those from the InvokerLocator, to configure itself. See org.jboss.remoting.ConnectionValidator.start(). I don't know why your parameters aren't making it into the ConnectionValidator. One thing to try, if you don't see anything interesting in the logs, is to attach a debugger to your client. Even if Bill Burke says "debuggers are for pussies". :)
-Ron
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191955#4191955
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191955
17 years, 5 months
[Beginners Corner] - EJB3 JDNI lookup error 'communicationException'
by ravich
javax.naming.CommunicationException [Root exception is java.lang.ClassNotFoundException: org.jboss.ejb3.JBossProxy (no security manager: RMI class loader disabled)]
at my.com.infopro.icba10.kernel.util.jndi.ServiceLocator.getServiceStub(ServiceLocator.java:163)
at my.com.infopro.icba10.kernel.util.jndi.ServiceLocator.locate(ServiceLocator.java:102)
at my.com.infopro.icba10.kernel.security.auth.delegate.SecurityDelegate.getSecurityServiceRemote(SecurityDelegate.java:35)
at my.com.infopro.icba10.kernel.security.auth.delegate.SecurityDelegate.performLogin(SecurityDelegate.java:49)
at my.com.infopro.icba10.kernel.uiframework.login.LoginAction.doLogin(LoginAction.java:178)
at my.com.infopro.icba10.kernel.uiframework.login.LoginAction.keyReleased(LoginAction.java:130)
at java.awt.Component.processKeyEvent(Component.java:5449)
at javax.swing.JComponent.processKeyEvent(JComponent.java:2713)
at java.awt.Component.processEvent(Component.java:5265)
at java.awt.Container.processEvent(Container.java:1966)
at java.awt.Component.dispatchEventImpl(Component.java:3955)
at java.awt.Container.dispatchEventImpl(Container.java:2024)
at java.awt.Component.dispatchEvent(Component.java:3803)
at java.awt.KeyboardFocusManager.redispatchEvent(KeyboardFocusManager.java:1810)
at java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(DefaultKeyboardFocusManager.java:672)
at java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(DefaultKeyboardFocusManager.java:920)
at java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(DefaultKeyboardFocusManager.java:798)
at java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:636)
at java.awt.Component.dispatchEventImpl(Component.java:3841)
at java.awt.Container.dispatchEventImpl(Container.java:2024)
at java.awt.Window.dispatchEventImpl(Window.java:1778)
at java.awt.Component.dispatchEvent(Component.java:3803)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:153)
at java.awt.Dialog$1.run(Dialog.java:517)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
Caused by: javax.naming.CommunicationException [Root exception is java.lang.ClassNotFoundException: org.jboss.ejb3.JBossProxy (no security manager: RMI class loader disabled)]
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:728)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at my.com.infopro.icba10.kernel.util.jndi.ServiceLocator.getServiceStub(ServiceLocator.java:158)
... 33 more
Caused by: java.lang.ClassNotFoundException: org.jboss.ejb3.JBossProxy (no security manager: RMI class loader disabled)
at sun.rmi.server.LoaderHandler.loadProxyClass(LoaderHandler.java:531)
at java.rmi.server.RMIClassLoader$2.loadProxyClass(RMIClassLoader.java:628)
at java.rmi.server.RMIClassLoader.loadProxyClass(RMIClassLoader.java:294)
at sun.rmi.server.MarshalInputStream.resolveProxyClass(MarshalInputStream.java:238)
at java.io.ObjectInputStream.readProxyDesc(ObjectInputStream.java:1500)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1463)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1699)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at java.rmi.MarshalledObject.get(MarshalledObject.java:135)
at org.jnp.interfaces.MarshalledValuePair.get(MarshalledValuePair.java:72)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:652)
... 36 more
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191953#4191953
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191953
17 years, 5 months
[Installation, Configuration & DEPLOYMENT] - HOWTO: create self signed certificate authority and server c
by djangofan
I created a HOWTO doc for creating a self signed certificate authority and server cert for JBoss. Here is the link to my blog, which describes this:
http://codingathome.blogspot.com/
----------------
Here is the ROUGH content:
Here is how I created my own CA (certificate authority) and used it to enable SSL connectivity in Jboss Tomcat with a WILDCARD server certificate.
0. Prerequisites: The package openssl and JDK1.5+ should be installed in the machine you will use to manage your certificates or create the certificate requests.
1. c:\OpenSSL> mkdir myCA
2. cd mkdir
3. mkdir private ( note: myCA/private is the directory where our private keys are placed. Be sure that you set restrictive permissions to all your private keys so that they can be read only by the CA owner. If anyone steals your private keys, then things get really bad. )
4. mkdir certs
5. copy c:\OpenSSL\bin\openssl.cfg c:\OpenSSL\myCA\openssl.my.cfg . On line 35 or so of the new openssl.my.cfg, change the settings to the following:
[ CA_default ]dir = . # <--CHANGE THIScerts = $dir/certscrl_dir = $dir/crldatabase = $dir/index.txt#unique_subject = nonew_certs_dir = $dir/newcertscertificate = $dir/certs/myCA.crt # <--CHANGE THISserial = $dir/serial#crlnumber = $dir/crlnumbercrl = $dir/crl.pemprivate_key = $dir/private/myCA.key # <--CHANGE THISRANDFILE = $dir/private/.randx509_extensions = usr_cert
6. cd c:\OpenSSL\myCA
7. C:\OpenSSL\myCA>openssl req -config openssl.my.cfg -new -x509 -extensions v3_ca -keyout private/myCA.key -out certs/myCA.crt -days 3650 . (note: on this one, for example, when it asks you for your name you can use "mysecretCA.org". the name you choose doesn't really matter because it will be imported into a web browser as a root cert and so it doesn't need to resolve since (in this case) it validates locally and internally.)
8. cd c:\OpenSSL\myCA\certs
9. c:\OpenSSL\myCA\certs> keytool -genkey -alias tomcat -keyalg RSA -keystore my.keystore -validity 365 -storepass changeit
10. c:\OpenSSL\myCA\certs> keytool -v -certreq -alias tomcat -keystore my.keystore -file myreq.csr
11. cd c:\OpenSSL\myCA
12 c:\OpenSSL\myCA> openssl ca -config openssl.my.cfg -policy policy_anything -out certs/wildcard.crt -infiles certs/myreq.csr
13. cd C:\OpenSSL\my_jungle\myCA\certs
14. C:\OpenSSL\my_jungle\myCA\certs> keytool -import -alias root -keystore my.keystore -trustcacerts -file myCA.crt -storepass changeit
15. C:\OpenSSL\my_jungle\myCA\certs> keytool -import -alias tomcat -keystore my.keystore -trustcacerts -file wildcard.crt -storepass changeit
16. C:\OpenSSL\my_jungle\myCA\certs> keytool -list -v -keystore my.keystore
17. Finally, to load the server certificate in JBoss 4.05. Edit the server.xml file in the jboss\server\default\deploy\jbossweb-tomcat55.sar directory.
Connector port="443" address="${jboss.bind.address}" maxThreads="100" strategy="ms" maxHttpHeaderSize="8192" emptySessionPath="true" scheme="https" secure="true" clientAuth="false" compression="force" debug="0" keystoreFile="../../bin/my.keystore" keystorePass="changeit" sslProtocol = "TLS"
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191944#4191944
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191944
17 years, 5 months