[JBoss Messaging] - DurableMessagesGoesToDLQAfterRestart
by Rickard Dahl
Rickard Dahl [http://community.jboss.org/people/rickard%40rdahl.se] created the discussion
"DurableMessagesGoesToDLQAfterRestart"
To view the discussion, visit: http://community.jboss.org/message/536317#536317
--------------------------------------------------------------
Hi,
I really need help on how to solve this problem! How do I get the expected behavior? Can it be done? Is it a bug?
*Short problem description:*
After restarting JBoss, pending messages on a durable topic will be put on DLQ. This is NOT what I expect. I want them to stay on the topic even after a restart.
*Background to my problem:*
I have a topic and two durable subscribers (two MDB's). One of the subscribers will try to deliver messages to a web service, which _can_ be offline. In that case, the MDB will throw an exception and the message will be redelivered later.
The problem is that when the web service is offline and I restart JBoss, all pending messages on the topic will be put on DLQ.
By default, the MDB will run 16 sessions in parallell, and these will stay "durable" even after a restart.
*An example:*
Before restart
- I publish 56 messages to the topic
- The web service is offline
- Subscriber 1 (the "web service" one) now has 56 pending messages
- Subscriber 2: 56 successfully processed messages, 0 pending messages
- DLQ: 0 pending messages
Result after the restart:
- Subscriber 1 (the "web service" one) now has 16 pending messages
- Subscriber 2: 0 pending messages
- DLQ: 40 pending messages
*My setup:*
- JBoss 4.2.3
- JBoss Messaging 1.4.4 (have also tried with 1.4.2 with the same result)
- Using a MSSQL database for persistance
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/536317#536317]
Start a new discussion in JBoss Messaging at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years
[JBoss Messaging] - DurableMessagesGoesToDLQAfterRestart
by Rickard Dahl
Rickard Dahl [http://community.jboss.org/people/rickard%40rdahl.se] created the discussion
"DurableMessagesGoesToDLQAfterRestart"
To view the discussion, visit: http://community.jboss.org/message/536312#536312
--------------------------------------------------------------
Hi,
Short problem description: After restarting JBoss, pending messages on a durable topic will be put on DLQ. I expect them to stay on the topic even after a restart.
Background to my problem:
I have a topic and two durable subscribers (two MDB's). One of the subscribers will try to deliver messages to a web service, which _can_ be offline. In this case, the MDB will throw an exception. By doing like this, the message will be delivered when the web service comes up again.
By default, the MDB will run 16 sessions in parallell.
The problem is that when the web service is offline and I restart JBoss, all pending messages will be put on DLQ.
After the restart, ther is still 16 messages in
An example:
- I publish 56 messages to the topic
- The web service is offline
- Subscriber 1 (the "web service" one) now has 56 pending messages
- Subscriber 2: 56 successfully processed messages, 0 pending messages
- DLQ: 0 pending messages
Result after the restart:
- Subscriber 1 (the "web service" one) now has 16 pending messages
- Subscriber 2: 0 pending messages
- DLQ: 40 pending messages
My setup:
- JBoss 4.2.3
- JBoss Messaging 1.4.4 (have also tried with 1.4.2 with the same result)
- Using a MSSQL database for persistance
Note that the problem is NOT that the max number of retries has been reached since the MDB's have a LARGE numer of retries set with annotation "dlqMaxRetries" + each onMessage() takes a ouple of sec because of the web service call.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/536312#536312]
Start a new discussion in JBoss Messaging at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years
Re: [jboss-user] [jBPM] - JPDL feature request
by Koen Aers
Koen Aers [http://community.jboss.org/people/koen.aers%40jboss.com] replied to the discussion
"JPDL feature request"
To view the discussion, visit: http://community.jboss.org/message/536288#536288
--------------------------------------------------------------
This is a very interesting discussion guys! I like the svg approach of rendering the image, it is a lot cleaner than saving the image with the process. What about the performance though? Do you perform this xslt transformation to svg on the fly each time before rendering? Doesn't that take a lot of time?
As for the 'g' attribute, this looks like it does because it has always been our focus to keep the jpdl xml concise and readable. As you might know the graphical info even used to be in another file in jBPM 3, with other drawbacks. Even if it would be advisable, it would be very difficult to split the 'g' attribute at this time because of backward compatibility issues and complications with the tools. We will be moving towards BPMN2 anyway for the next generation of jBPM (jBPM 5) and that standard is focused on diagrams and interchange of them.
In the meantime, feel free to continue to suggest and contribute jBPM 4 improvements.
Cheers,
Koen
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/536288#536288]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years
Re: [jboss-user] [JCA Development] - JcaXAResourceRecovery
by Scott Marlow
Scott Marlow [http://community.jboss.org/people/smarlow%40redhat.com] replied to the discussion
"JcaXAResourceRecovery"
To view the discussion, visit: http://community.jboss.org/message/536287#536287
--------------------------------------------------------------
I would consider re-engineering the codebase from MBEAN based to MC, to be out of scope for AS 5.x. As that could destabilize the code base and impact existing deployments in a negative way. The idea of minimizing risk when applying code changes to released versions of a product/project is an old idea that still makes sense (IMHO).
At the moment, we are still figuring out the larger challenge of integrating as strongly as possible, with the xa recovery mechanism. Well, Jesper has a design in place but we are trying to apply that to the existing code still and it is challenging (there are a lot of moving parts to deal with). If we didn't have enough challenges already, we could probably figure out a way to re-engineer (safely) from a MBEAN approach to MC.
Perhaps we should have this discussion on the phone if there is still disagreement. If all involved are willing to speak in person, that would be fine with me too. Might not be a bad idea to have a few phone meetings to discuss how things are going anyway (if you guys want that :-).
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/536287#536287]
Start a new discussion in JCA Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years
[JBoss Portal] - Configuring the header.jsp
by Tridib Das
Tridib Das [http://community.jboss.org/people/tridib197779] created the discussion
"Configuring the header.jsp"
To view the discussion, visit: http://community.jboss.org/message/536278#536278
--------------------------------------------------------------
Hi All,
I have modified the header.jsp and created my own .war file.
But still i have to modify the jboss-service.xml(\server\default\deploy\jboss-portal.sar\META-INF)
<mbean
code="org.jboss.portal.core.aspects.controller.PageCustomizerInterceptor"
name="portal:service=Interceptor,type=Command,name=PageCustomizer"
xmbean-dd=""
xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean">
<xmbean/>
<attribute name="TargetContextPath">/portal-core</attribute>
<attribute name="HeaderPath">/WEB-INF/jsp/header/header.jsp</attribute>
<attribute name="TabsPath">/WEB-INF/jsp/header/tabs.jsp</attribute>
<!-- Overrides the value of core.login.namespace in config.xml -->
<!-- attribute name="LoginNamespace">dashboard</attribute -->
<depends
optional-attribute-name="Config"
proxy-type="attribute">portal:service=ServerConfig</depends>
<depends
optional-attribute-name="PortalAuthorizationManagerFactory"
proxy-type="attribute">portal:service=PortalAuthorizationManagerFactory</depends>
<depends
optional-attribute-name="PortalObjectContainer"
proxy-type="attribute">portal:container=PortalObject</depends>
</mbean>
Without modifying the file , if there is any work around to solve the problem.
Please reply.
Thanks
Tridib
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/536278#536278]
Start a new discussion in JBoss Portal at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years