I'm using the PooledInvoker and client certificate authentication to EJBs with
mixed success. Periodically method calls fail because there is no
principal/credential passed into the login modules. I was able to duplicate
the problem with org.jboss.test.pooled.test.SSLSocketsUnitTestCase from t
I found the answer in a similar thread
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3933179
Thanks.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3937306#3937306
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply
I finally got approval from the client.
I checked out the PooledInvoker, and I think I will try that approach. Other
than providing custom socket factories, do I need to do anything special for a
server side login module to access the client cert as a credential?
What kind of configuration woul
I'm moving from a webapp using client-cert authentication to a thick client. I
need to continue using certificates for authentication. All work is performed
in EJBs, and I was considering a couple of different approaches.
1. Enable RMI+SSL for EJBs and subclass RMISSLClientSocketFactory and
That should work for my particular case. Just out of curiosity, what would one
do for 3.0 entities? Will they cause the same problem?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3917924#3917924
Reply to the post :
http://www.jboss.com/index.html?module=b
I have a EJB 3.0 SLSB in one .ear (ear1) file acting as a client to a SLSB in
another .ear (ear2). I am using issolated class loading and I have to include
the .ejb3 file from ear2 into ear1 for it to find the classes. However, when I
try to bundle the .ejb3 file from ear2 in ear1 it trys to r
Thanks for your reply. It really cleared things up for me. The reason I
thought I had to do the lookups myself using HA-JNDI is because topic lookups
failed unless I used HA-JNDI. Final question I swear, just so I'm clear.
1) Lookup up java:/JmsXA through default initial context, lookup topi
Thanks for your reply. I'm glad enlisting HAJMS in transactions is possible,
and I have successfully tested our MDB's but I'm a little confused regarding
session beans.
1. My understanding is that for JMS to be treated as a manged resource it has
to be listed in your deployment desciptor and
Is it possible to get the transaction behavior of java:/JmsXA with HAJMS?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867969#3867969
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867969
---
That worked. Thanks for the tip. I never would have made the connection with
SimplePrincipal and custom principal.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3864819#3864819
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=r
I have a custom login module that uses client certificates. It sets the
identity to a SimplePrincipal with the CN portion of the certificate. However,
in my servlet calls to request.getUserPrincipal().getName() return the entire
subject DN. I checked, and the principal is an instance of
sun.
Too bad 3.2.5 still ships with the same broken jgroups.jar from 3.2.4 despite
reporting a problem. If your having a problem getting your nodes to see each other
try upgrading to jgroups 2.2.5. It worked for me.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=
Using 3.2.4, I configured JBossMQ to use Oracle for both state and persistence
managers in the all configuration. When I deploy an ear with MDBs that are durable
subscribers to any node in the cluster it works fine, but if I deploy the same ear to
multiple nodes, I receive a javax.jms.IllegalSt
Upgrading to JGroups 2.2.5 fixed this problem.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3840174#3840174
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3840174
--
Bela,
Thanks for the response.
The cluster-service.xml I am using is the default for 3.2.3
I saved it as test.xml as suggested.
First machine output:
pegasus:/home/frdon
If I run the org.jgroups.demos.Chat program from the jgroups.jar 2.2.4 that comes with
JBoss 3.2.4 I get the same behavior. Clients on the same machine see each other, but
remote clients are not visible. Same demo with jgroups.jar 2.2.0 from JBoss 3.2.3
works. Can I use the old jar or will th
Just as a follow up. I started 3.2.4 on one machine and 3.2.3 on the other. They see
each other but complain about a version mismatch. So I'm guessing 3.2.4 is receiving
requests fine but not broadcasting correctly.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewto
I had two solaris machines clustered with 3.2.3. Moved to 3.2.4 and started an all
instance on each box. They don't see each other. I can start two instances on the
same machine and they cluster fine. The boxes both only have a single network card
(That seemed to be causing others problems).
18 matches
Mail list logo
