Re: [jboss-user] [EJB 3.0 Development] - HornetQ Resource Adapter and DLQ handling
by jaikiran pai
jaikiran pai [http://community.jboss.org/people/jaikiran] replied to the discussion
"HornetQ Resource Adapter and DLQ handling"
To view the discussion, visit: http://community.jboss.org/message/537907#537907
--------------------------------------------------------------
Actually, there are 2 things to be considered here:
1) Provider specific activation config properties : As Andy says - JBM used to support some of the activation config props which are no longer valid in HornetQ. As Andy and I discussed over IRC, I'll see if EJB3 code mandates some of these properties to be available. If it does, then we will have to move it out of EJB3 (including the related documentation) to make it a JMS provider specific config.
2) The meaning/usage of DLQ : In HornetQ, there are just Dead letter Addresses. But from the point of view of a JMS client (like MDB) which are just aware of (JMS) queues and (JMS) topics, how would they subscribe to a dead letter (JMS) queue. I am still looking at the hornetq configs in AS and reading through the docs to see how the (hornetq) DLA is being setup. I guess, there needs to be some layer which sets up a (HornetQ) queue subscription to the DLA to make it look like the (JMS) DLQ.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/537907#537907]
Start a new discussion in EJB 3.0 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years, 2 months
[EJB 3.0 Development] - HornetQ Resource Adapter and DLQ handling
by Andy Taylor
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&cont...]
16 years, 2 months
Re: [jboss-user] [Performance Tuning] - java.net.SocketException: Too many open files on Red Hat lin
by Kiran Krishnamurthy
Kiran Krishnamurthy [http://community.jboss.org/people/kiranhk] replied to the discussion
"java.net.SocketException: Too many open files on Red Hat lin"
To view the discussion, visit: http://community.jboss.org/message/537892#537892
--------------------------------------------------------------
Yes.. I was able to resolve the problem. the executor was not mentioned which will close the connections/files that are open
Navigate to "jboss-5.1.0.GA/server/ottserver/deploy/jbossweb.sar" and edit server.xml as mentioned below.
Look for following xml snippet.
<Connector port="9090" address="${jboss.bind.address}" maxThreads="250" maxHttpHeaderSize="8192" emptySessionPath="true" protocol="HTTP/1.1" enableLookups="false" redirectPort="8443" acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" />
Replace this snippet with below one.
<Executor name="appThreadpool" namePrefix="activeThread-" maxThreads="150" minSpareThreads="3" maxIdleTime="30000" />
<Connector executor="appThreadpool" port="9090" address="${jboss.bind.address}" maxThreads="150" maxHttpHeaderSize="8192"
minSpareThreads="3" maxSpareThreads="20" emptySessionPath="true" protocol="HTTP/1.1"
enableLookups="false" redirectPort="8443" acceptCount="100" connectionTimeout="120000" disableUploadTimeout="true" />
Look for following xml snippet.
<Connector port="8009" address="${jboss.bind.address}" protocol="AJP/1.3" emptySessionPath="true" enableLookups="false" redirectPort="8443" />
Replace this snippet with below one.
<Connector executor="appThreadpool" port="8009" address="${jboss.bind.address}" protocol="AJP/1.3" emptySessionPath="true" enableLookups="false" redirectPort="8443" />
hope that helps.
thanks
Kiran
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/537892#537892]
Start a new discussion in Performance Tuning at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years, 2 months