[jboss-user] [JBoss Messaging] - Re: JMS Connections not getting released after upgrading to JBoss 6.0.1
Andy Taylor [https://community.jboss.org/people/ataylor] created the discussion "Re: JMS Connections not getting released after upgrading to JBoss 6.0.1" To view the discussion, visit: https://community.jboss.org/message/806406#806406 -- This is the JBoss messaging project forum, you need to raise this on the AS forum. -- Reply to this message by going to Community [https://community.jboss.org/message/806406#806406] Start a new discussion in JBoss Messaging at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2042] ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JNDI and Naming] - Re: timeouts on jndi calls (jnp.timeout & jnp.sotimeout)
Andy Taylor [http://community.jboss.org/people/ataylor] created the discussion "Re: timeouts on jndi calls (jnp.timeout & jnp.sotimeout)" To view the discussion, visit: http://community.jboss.org/message/600671#600671 -- No I didn't, i think it can still be a problem with any client tho, maybe one of the AS developers could comment! -- Reply to this message by going to Community [http://community.jboss.org/message/600671#600671] Start a new discussion in JNDI and Naming at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2083] ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Remoting] - Re: bind options
Andy Taylor [http://community.jboss.org/people/ataylor] created the discussion "Re: bind options" To view the discussion, visit: http://community.jboss.org/message/573643#573643 -- the JBM src looks up the remoting connector service and logs the info from there. Howard, do you know what version of remoting Pete needs to look at to debug? -- Reply to this message by going to Community [http://community.jboss.org/message/573643#573643] Start a new discussion in JBoss Remoting at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2050] ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JNDI and Naming] - timeouts on jndi calls (jnp.timeout & jnp.sotimeout)
Andy Taylor [http://community.jboss.org/people/ataylor] created the discussion "timeouts on jndi calls (jnp.timeout & jnp.sotimeout)" To view the discussion, visit: http://community.jboss.org/message/549274#549274 -- Ive been playing around with the time outs on client jndi lookups (we want to set these for HornetQ JMS bridges) and have found that the timeouts i was setting weren't being used. After debugging i found that the following was happening //psuedo code 1. Create socket 2. socket.setsotimeout(sotimeout) 3. socket.connect(timeout) 4. marshall Naming Server stub 5. cache server 6. invoke lookup on server using RMI subsequent calls use the cached server which means that the timeouts are only actually used in the initial marshalling of the server stub, all subsuquent calls to the naming server will use what ever default timeouts are set on the RMI implementation. My question is this, should the jndi code handle setting these same parameters on the rmi layer or is it up to the client code to do it. I actually tried setting the sun rmi params but it had no effect. -- Reply to this message by going to Community [http://community.jboss.org/message/549274#549274] Start a new discussion in JNDI and Naming at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2083] ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0 Development] - HornetQ Resource Adapter and DLQ handling
Andy Taylor [http://community.jboss.org/people/ataylor] created the discussion "HornetQ Resource Adapter and DLQ handling" To view the discussion, visit: http://community.jboss.org/message/537904#537904 -- Theres currently an issue with DLQ handling in the HornetQ resource Adapter. Basically we ignore the DLQ settings in the Activation spec. These were only added because there is some code that calls these and sets these with defaults, but basically they are no ops. The problem is that these methods dont really make sense in a HornetQ context, for instance one seting is for the providers JNDI, but in our RA code we dont use JNDI at all, this is so our RA will work with any container. Also we dont have the notion of a DLQ we have a dead letter address which could have n queues bound to it. As far as I can see there are the following solutions. 1. We change the activation spec to have HornetQ specific settings. This means however that apps being migrated will have to be ported. 2. We keep the same spec and handle this at th ejb3 layer. 3. We keep the same spec but change our RA to somehow handle this, altho it would be a huge hack and we dont really want to do this. thoughts guys, any other possible solutions. P.S Jaikirin is looking in the ejb3 code to see where these defaults are set as this would need changing too -- Reply to this message by going to Community [http://community.jboss.org/message/537904#537904] Start a new discussion in EJB 3.0 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2030] ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
