[JBoss Messaging] - JNP message queues through SSH tunnels
by cameronjones
Hey guys,
I'm trying to setup remote access to jboss message queues using hermes and putty but for some reason hermes has a problem with it.
I've setup a tunnel in putty to re-route the jnp service to the same localhost port but hermes keeps complaining with the error "No message, linked exception is null". Without the tunnel setup it times out which leads me to believe that it can connect through the tunnel but that there's some other issue at work. I followed all of the directions in the tuturial at http://www.hermesjms.com/demos/jboss_config.html
Here's the config i'm using:
loader jboss
providerURL jnp://localhost:1099
initialContextFactory org.jnp.interfaces.NamingContextFactory
urlPkgPrefixes org.jnp.interfaces:org.jboss.naming
securityCredentials admin
securityPrincipal admin
And here's my jndi.properties config:
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.provider.url=jnp://localhost:1099
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
I should note that the message queues are up and runnning and my app is fully deployed and working so it can't be a problem with the actual configuration of the jms server.
I'm not sure if this is the right place to ask this question or if i should direct it to the hermes site but since i'm trying to access a jnp resource i thought it could be jboss specific. Has anyone else done this before or can anyone suggest what i should look into to try and get this to work?
Thanks,
Cam
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967227#3967227
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967227
19 years, 8 months
[EJB 3.0] - Problem with lazy initialization - no session or session was
by korg
Hi,
previously we used hibernate to manage our transactions and we were responsible of closing sessions in our session beans, so we closed it only when the thread that called the session bean was killed. this way, it was possible for another bean (in another deployed package in jboss) to retrieve entity bean and access fields that were lazy initialized.
We changed our way of doing things to use EJB EntityManager, but since then it's impossible to access fields that have been lazy initialized. I have entity beans and session beans deployed in a .ejb3 file and business logic beans in another .ejb3 file. One of my BL bean calls a session bean to retrieve a list of entities and when I try to access fields that are lazy initialized, I get the folowing error:
org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: com.cardinal.dal.entity.infrastructure.PhysicalLocation.a
ppAccessDeviceVws, no session or session was closed
I read somewhere that this is the case when I try to access those fields outside of the classloader boundaries, so I tried to deploy my application in an ear file containing all my .ejb3 files and everything required. When I deploy it, I still get the same exception mentionned above.
Is there a way to access lazy initialized entities outside of my session beans? Is there a way to tell JBoss "hey, this application is in the same class loader than this one", so the session would remain open?
Thx a lot for help!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967226#3967226
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967226
19 years, 8 months