[Security & JAAS/JBoss] - rmi over https
by choozie
I have an old server/client application where communication is done with rmi. My server-part is running on jboss. I create an instance of the RMIServerInvoker and then bind to the rmi registry which is then created at port 3455. This all works well and my client is able to connect to my server at rmi://my_server_ip:3544/server
But I need to secure the rmi with ssl. I think I need to tunnell the rmi over http. Everything I find when I do a search is about ejb's. I don't use ejb's. This is an old application that I just want to get running on jboss and in a secure way. What is the easies way for me to tunnell the rmi over http?
Please, please, please someone answer me! Thank you :)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3961529#3961529
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3961529
19 years, 9 months
[JBoss Messaging] - Re: Removing a MessageListener doesn't remove its associated
by davidrh
The client is running in a different JVM to the server. In our test environment, they are running on different boxes.
You are right about the cut and paste error - lost the index somewhere between Eclipse and here. This is a harness I use for testing, so I can change the number of consumers up and down. In the production application we have one queue with 10 consumers, one with 5 consumers, two with 2 consumers and 2 with one consumer.
The client application is a web app running under JBoss 4.0.4GA. We can get a list of the threads from the JMX console, and I've made our message receivers change the thread name on the first call so that we can identify the threads easily. We're not using MDBs as we want to be able to deploy our product under lighter weight app servers without the full J2EE stack.
I just had a quick try with CR3 before I left the office and it looked OK. On a couple of runs, it didn't seem to matter whether you set the message listener to null or not - it peaked at forty threads maximum. Is 40 some sort of maximum thread pool size for the number of sessions with message listeners, and is this configurable somewhere?
Will have to wait until Monday for detailed testing - we will upgrade our test environment to CR3 and await CR4.
Do you have any thoughts on how long a session should be able to stay open?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3961524#3961524
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3961524
19 years, 9 months
[EJB/JBoss] - Stateful session bean not passivated
by msdanner
In JBoss 4.0.3 SP 1 a stateful session bean is not passivated after the calling client has terminated while a bean method is being executed. Instead, server log shows the warning message
2006-07-28 10:58:21,161 WARN [org.jboss.ejb.plugins.AbstractInstanceCache] Unable to passivate due to ctx lock, id=eq69yz36-b
where eq69yz36-b is the session ID of the terminated client.
The stateful session bean's task is to execute an SQL query and return its results in 1 or more than 1 calls because there might be some 100000 resulting rows. The state of the bean is a JBoss WrappedConnection and a ResultSet that should be closed when the caller has terminated.
All of it works fine unless the caller terminates while the session bean executes the query (which may take some minutes).
What can be the cause why the bean will not get passivated?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3961520#3961520
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3961520
19 years, 9 months