[Design of EJB 3.0] - Re: EJBTHREE-786
by bill.burke＠jboss.com
I keep saying this to you....
I know the intention of the specification. We can challenge any TCK test based on knowledge of this intention. IIRC, the spec says *nothing* about requiring an EJB 3.0 reference to be castable or narrowable to EJBObject. This is just something *JBoss* threw in.
Also, it is *impossible* to know what interface was invoked upon if a set of interfaces of the same type (remote/local) have a method of the same signature.
The implementation of this, BTW, is very easy. Have knowledge on whether the method was invoked remotely or locally or through web services. Save the method hash transferred through the web layer. When somebody invokes getInvokedBusinessInterface, take this information and match the method hash to the appropriate interface. First one wins.
Why are we overengineering for this case?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4090423#4090423
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4090423
17 years, 3 months
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Need Notification when message is dropped due to max siz
by jwilker
Hi, Thanks for your response.
Unfortunately, no exception appears to be thrown when topic messages are dropped due to MaxSize.
Here's the relevant code from ServerConnectionEndpoint (1.4.0.GA), where the stack is sitting on the topic posteOffice.route() call which doesn't result in an exception.
else if (dest.isQueue())
{
if (!postOffice.route(ref, new JMSCondition(true, dest.getName()), tx))
{
throw new JMSException("Failed to route " + ref + " to " + dest.getName());
}
}
else
{
postOffice.route(ref, new JMSCondition(false, dest.getName()), tx);
}
Interesting, the queue case looks to result in an exception, where the topic case doesn't.
Any idea as to why?
------------------------------------------------------
Also, here's the full stack trace:
MessagingQueue(ChannelSupport).handleInternal(DeliveryObserver, MessageReference, Transaction, boolean) line: 598
MessagingQueue(ChannelSupport).handle(DeliveryObserver, MessageReference, Transaction) line: 144
MessagingPostOffice.routeInternal(MessageReference, Condition, Transaction, boolean, Set) line: 2124
MessagingPostOffice.route(MessageReference, Condition, Transaction) line: 478
ServerConnectionEndpoint.sendMessage(JBossMessage, Transaction, boolean) line: 710
ServerSessionEndpoint.send(JBossMessage, boolean) line: 343
SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$send$aop(JBossMessage, boolean) line: 80
SessionAdvised$send_6145266547759487588.invokeNext() line: not available
SecurityAspect.handleSend(Invocation) line: 157
GeneratedMethodAccessor78.invoke(Object, Object[]) line: not available
DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25
Method.invoke(Object, Object...) line: 585
PerInstanceAdvice.invoke(Invocation) line: 121
SessionAdvised$send_6145266547759487588.invokeNext() line: not available
ServerLogInterceptor.invoke(Invocation) line: 105
SessionAdvised$send_6145266547759487588.invokeNext() line: not available
JBossMessagingServerInterceptor.handleSessionSend(Invocation) line: 183
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4090386#4090386
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4090386
17 years, 3 months