[JBoss Seam] - Re: Timer issue just broke my site after a week of no issues
by modoc
I did ask on the EJB3 forum, but eventually worked it out on my own. The problem is that there is no stack trace. I don't have eclipse open atm, but basically the JBoss code catches all exceptions, wraps them in an EJBException, but doesn't include the root exception, just it's msg. So you never get access to the stack trace.
I'm going to file a JIRA bug on it, as it makes diagnosing this sort of thing almost impossible. I had to go into my code and catch NPE and log it myself, just so I could see the stack trace.
Turns out some e-mail was getting delivered based on an optional x-original-to header, with a null to: header, which blew an NPE, since I had assumed that incoming e-mail would have a to address.
It ended up being my code's fault, but the error message not only didn't indicate that at all, but also didn't provide a stack trace or other useful into, so it took a while to track down.
Sorry if my posts seemed a bit panicy, but with the amount of traffic I was getting, each time it broke, the forums got lots of negative comments, etc...
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989804#3989804
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989804
18Â years, 2Â months
[JBoss Seam] - Seam remoting not working
by crackersoul
I've cut and pasted the helloAction remoting example from the remoting chapter of seam_reference.pdf for Seam 1.0.1.GA verbatim, but it's not working.
The only change I made was:
@Scope(ScopeType.SESSION)
instead of:
@Scope(SESSION)
for the HelloAction class.
In Firefox, when I click on the Say Hello button, I get the name prompt dialog, and in the debugger, I've verified that the HelloAction.sayHello method is invoked and is passed the name I typed in the JS alert, but my JS sayHelloCallback function is never invoked.
Anybody have any ideas? Like I said, I copied the example verbatim from the ref manual, so it should work.
I'm on Mac OS X, and I'm running in Tomcat 5.5.17 with the JBoss embedded EJB3.0 server.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989802#3989802
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989802
18Â years, 2Â months
[Messaging, JMS & JBossMQ] - Changing delivery policy
by felipeal
Hi all,
First of all, sorry if this is not the right forum for posting this message - if it's not, I will repost it in the proper question.
Now, back to my question, I have the following scenario:
1.JMS Messages representing an email message are posted to a JMS queue
2.MDBs consume these (JMS) messages, sending the email to the proper destination
So far so good, but sometimes I some emails are rejected because I'm sending too many messages to a given domain. So, one cool solution for this problem was to customize the JMS provider in order to do some sort of round-robin when selecting what's the next message to be consumed (instead of the traditional 'first come, first served' approach). In this particular case, the process that create the JMS messages would add a JMS property with the SMTP domain the message belongs to, and the JMS provider would then use that property to determine which message to send next.
For instance, let's say I have 5 messages, inserted in the following order:
1 - domain X
2 - domain X
3 - domain Y
4 - domain Y
5 - domain Z
Tradicionally, these message would be consumed in the same order. But what I want is to change the order to:
1 - domain X
3 - domain Y
5 - domain Z
2 - domain X
4 - domain Y
So, my question is: is it possible to change how JBoss decides what's the next message to be delivered? If so, how do I do it? Changing some sort of invoker?
TIA for any help,
-- Felipe
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989795#3989795
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989795
18Â years, 2Â months