[JBoss-user] [Messaging, JMS & JBossMQ] - Re: JMS JDBC Persistence and server restart.
Interesting so are you saying if you have a Topic in jboss i.e. topic/testTopic
that a MessageDrivenBean implements MessageDrivenBean, MessageListener. Will
not be activated. Big question is will it work in jboss 4.0.1?
I have been banging my head why my MessageDrivenBean onMessage() method is
never called. I publish to the topic/testTopic but the Bean is never called.
First i publish with this:
Topic topic =
(Topic)initialContext.lookup(MessageSubscriberBean.TOPIC_JNDI_NAME);
TopicConnection connection = null;
TopicSession session = null;
TopicPublisher publisher = null;
try {
connection = openTopicConnection();
session = connection.createTopicSession(false,
TopicSession.AUTO_ACKNOWLEDGE);
publisher = session.createPublisher(topic);
MessageCreator creator = new ObjectMessageCreator(message);
publisher.publish(creator.getMessage(session),
Message.DEFAULT_DELIVERY_MODE,priority,Message.DEFAULT_TIME_TO_LIVE);
} catch(JMSException e) {
throw new KVException(e);
} finally {
closeTopicPublisher(publisher);
closeSession(session);
closeConnection(connection);
}
Then the MDB config is here with a basic bean:
[CDATA[]]
Test Topic Bean
TestTopic
com.message.MessageSubscriberBean
Container
Auto-acknowledge
javax.jms.Topic
NonDurable
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3944421#3944421
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3944421
---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS & JBossMQ] - Re: JMS JDBC Persistence and server restart.
Dear Forum Readers and Adrian! If you followed this thread thoughtfully perhaps you have conclusions similar to mine - as follows: The Professional Open Source Company (henceforth referenced as JBOSS) did not provide any official and detailed descriptions or how-to's about durable descriptions and topics or making messages persistent. There are lot of sources available on the web however most of them are outdated and/or contradicting each other - especially for newbies, like us. We continously failed to persist or messages under 4.0.1 AS so as a last resort we tried to get some help from the official JBOSS forum. Although my posts did not have any allusions that this was a Jboss bug (which it actually turned out to be) I was rewarded with a uniquely hostile behaviour from Adrian: anonymous wrote : The stuff you have posted does not show anything. It is just some xml out of context. | ... | All I have seen so far in this post in lots of assertions with the usual | "IT DOES NOT WORK". So show me what it IS doing. . So this was the point where my project leader (henceforth referenced as mormota) came into the picture. He tried to shepherd to flow of this conversation into a constructive tunnel. (It's very funny how this good-cop, bad-coop scenario works and what a scientific degree could mean...) As time passed our developer team succesfully provided an unambigous evidence that there is a bug in the JMS handling of JBOSS and a bug report has been posted (http://jira.jboss.com/jira/browse/JBAS-1351?page=comments#action_12315048) , which was rejected firstly, however Adrian in his last post admitted that right now the 4.0.1 version is incapable of providing topic management corresponding to the EJB 2.1 recommendation. Actually that part of code could have never worked. We are working for a large telecommunication company. We, like most informatical projects have limited time and developer resources. Still it was our task to provide a detailed test-case so that JBOSS finally could accept that it is not our defect or laziness that causes the problem. Adrian, please help me! Help me to explain my costumer that JBOSS AS is the definite open source target platform that could be recommended because the thorough testing and open support! Help me to make them understand that JBOSS is not a bad and risky choice! I'will be here, waiting for your answer. Regards: Frank-15 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3864325#3864325 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3864325 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS & JBossMQ] - Re: JMS JDBC Persistence and server restart.
Thanks for your test case, the answer is trivial.
I cannot spell.
The problem is in JMSContainerInvoker
| - activationConfig =
getActivationConfigProperty("subscriptionDurablity");
| + activationConfig =
getActivationConfigProperty("subscriptionDurability");
|
You can workaround the problem using the old fashioned configuration in
ejb-jar.xml
| Durable
|
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3864184#3864184
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3864184
---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS & JBossMQ] - Re: JMS JDBC Persistence and server restart.
You don't need to modify the ra.xml You modify jms-ds.xml (or whatever you are using) | 10001 | Setting strict to false means you have unportable code (won't work in other appservers). Strict == false is for use outside a J2EE application server. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3864177#3864177 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3864177 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS & JBossMQ] - Re: JMS JDBC Persistence and server restart.
"[EMAIL PROTECTED]" wrote : You obviously have some skills since you claim a
Phd.
|
| For us to help you we need enough information (supplying a simple mdb jar
| that demostrates your problem would be one solution).
|
| Debugging (show us what you are doing):
| http://www.jboss.org/index.html?module=bb&op=viewtopic&t=43573
| Post the logging for the MDB startup (i.e. when it makes the construction)
| and JBossMQ.
| Including what happens at the send to JBossMQ.
|
| Checking your Config (minimum):
| Show your ejb-jar.xml/jboss.xml with the full context, i.e. the entire MDB
|
| jbossmq-state.xml (no longer used)
| http://www.jboss.org/wiki/Wiki.jsp?page=ConfigJBossMQState
|
| Just adding:
|
| | public void onMessage(Message m)
| | {
| | System.out.println(m);
| | ...
| |
| will show me a lot of information, i.e. the message properties (like
persistence
| and the subscription id).
Unfortunately, the skills required for a PhD are somewhat different from the
skills required to achieve our desired goal: topic persistency. But with your
help, I hope we can solve this problem.
First of all, the MDB simply prints the actual Message parameter value, as you
requested.
The ejb-jar.xml:
|
| http://java.sun.com/xml/ns/j2ee";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd";>
| Beans
|
|
| TestServiceBean
| com.test.msg.TestServiceHome
| com.test.msg.TestService
| com.test.msg.TestServiceBean
| Stateful
| Container
|
|
| jms/TestConnectionFactory
| javax.jms.TopicConnectionFactory
| Container
| Shareable
|
|
|
| jms/TestTopic
| javax.jms.Topic
|
|
|
|
|
|
|
| TimerBean
| com.test.msg.TimerLocalHome
| com.test.msg.TimerLocal
| com.test.msg.TimerHome
| com.test.msg.TimerRemote
|
| com.test.msg.TimerBean
| Stateless
| Container
|
|
| ejb/TestEntityFacade
| Session
| com.test.msg.TestEntityFacadeHome
| com.test.msg.TestEntityFacade
|
|
|
|
|
| TestTopicMDBBean
| com.test.msg.TestTopicMDBBean
| javax.jms.MessageListener
| Container
| javax.jms.Topic
|
| TestDestination
|
|
|
subscriptionDurability
|
Durable
|
|
|
clientId
|
DurableSubscriberExample
|
|
|
subscriptionName
|
MySubscriptionName
|
|
|
|
| ejb/TestEntityFacade
| Session
| com.test.msg.TestEntityFacadeHome
| com.test.msg.TestEntityFacade
|
|
|
|
| MessageEntryBean
| com.test.msg.TestEntityLocalHome
| com.test.msg.TestEntityLocal
| com.test.msg.TestEntityBean
| Container
| java.lang.String
| false
| 2.x
| MessageEntryBean
|
| no description
| networkServerId
|
|
| no description
| segmentCount
|
|
| no description
| profileName
|
|
| no description
| sentDate
|
|
| no description
| messageId
|
|
| no description
| deliveryStatus
|
| networkServerId
|
|
|
|
|
|
| findMessageBySentDate
|
| java.util.Date
|
|
| select object(a) from MessageEntryBean as a where
a.sentDate < ?1
|
|
|
|
|
|
| [CDATA[Session facade for TestEntityBean.]]
|
| TestEntityFacade
| com.test.msg.TestEntityFacadeHome
| com.test.msg.TestEntityFacade
| com.test.msg.TestEntityFacadeBean
| Stateless
| Container
|
| ejb/TestEntity
| Entity
| com.test.msg.TestEntityLocalHome
| com.test.msg.TestEntityLocal
| test.jar#MessageEntryBean
|
|
|
|
|
|
|
|
|
|
|
| TimerBean
| ejbTimeout
|
| javax.ejb.Timer
|
|
| RequiresNew
|
|
|
| TestDestination
|
|
|
TestTimerDestinatio
[JBoss-user] [Messaging, JMS & JBossMQ] - Re: JMS JDBC Persistence and server restart.
"[EMAIL PROTECTED]" wrote : FAQ:
http://www.jboss.org/wiki/Wiki.jsp?page=WhatIsTheCorrectWayToMakeADurableSubscription
|
| Preconfigured clients ids (for the testsuite) from
deploy/jms/hsqldb-jdbc-state-service.xml:
|
| | POPULATE.TABLES.03 = INSERT INTO JMS_USERS (USERID, PASSWD,
CLIENTID) VALUES ('john', 'needle', 'DurableSubscriberExample')
| |
|
|
|
I seems to me that we could solve the problem. We have modified our code and
hacked the jms-ra.rar as well.
Regarding our code, we added the following to the message producer:
connection.setClientID("10001");
So, we do the following in the producer:
| connection = connectionFactory.createTopicConnection("guest","guest"); //
previously we used createTopicConnection(void)
| connection.start();
| connection.setClientID("10001"); // new line
| session = connection.createTopicSession(true, 0);
| session.createDurableSubscriber((Topic)topic,"MySubscriptionName");
// new line
| publisher = session.createProducer(topic);
| publisher.setDeliveryMode(DeliveryMode.PERSISTENT);
|
However, when we tried to set the client identifier, JBoss thrown
IllegalStateException claiming that "This method is not applicatable in JMS
resource adapter".
Thereafter, we looked into the source code of method
JmsSessionFactoryImpl.setClientID(String), which actually throws the exception.
Here it is:
| public void setClientID(String cID)
| throws JMSException
| {
| if(mcf.isStrict())
| throw new IllegalStateException("This method is not
applicatable in JMS resource adapter");
| checkClosed();
| if(clientID != null)
| {
| throw new IllegalStateException("Cannot change client id");
| } else
| {
| clientID = cID;
| return;
| }
| }
|
Okay, we realized that the corresponding ManagedConnectionFactory (mcf) has to
be strict. Unfortunately, according to the JMX console the mcf is obviously
strict.
After some research on the web, we learnt that we can configure this attribute
in ra.xml located in jms-ra.rar.
Well, this finding was followed by some minimal hacking, which resulted in the
following modified ra.xml:
|
|
|
|
| http://java.sun.com/xml/ns/j2ee";
|xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
|xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
|http://java.sun.com/xml/ns/j2ee/connector_1_5.xsd";
|version="1.5">
|
|JBoss JMS Resource Adapter
|JMS Adapter
|
|JBoss, Inc
|JMS 1.1 Server
|4.0
|
|
|
| COPYRIGHT AND PERMISSION NOTICE
| Copyright (c) 2004 JBoss, Inc
| This is released under the terms of the LGPL.
| See gnu.org for details.
|
| true
|
|
|
|
org.jboss.resource.adapter.jms.JmsResourceAdapter
|
|
|
|
org.jboss.resource.adapter.jms.JmsManagedConnectionFactory
|
| The jndi name of the provider of connection
factories
|
JmsProviderAdapterJNDI
| java.lang.String
|
java:DefaultJMSProvider
|
|
|The default session type
|
SessionDefaultType
|java.lang.String
|
javax.jms.Topic
|
|
| The user name used to login to the jms
server
| UserName
| java.lang.String
|
|
|
| The password used to login to the jms
server
| Password
|
java.lang.String
|
|
|
| The client id for this connection
factory
| ClientID
|
java.lang.String
|
|
|
| Strict
|
java.lang.Boolean
|false
|
|
org.jboss.resource.adapter.jms.JmsConnectionFactory
|
org.jboss.resource.adapter.jms.JmsConnectionFactoryImpl
| javax.jms.Session
|
org.jboss.resource.adapter.jms.JmsSession
|
| XATransaction
|
|
BasicPassword
|
javax.resource.spi.security.PasswordCredential
|
| false
|
|
|
|
|
|
javax.jms.MessageListener
|
|
org.jboss.resource.adapter.jms.inflow.JmsActivationSpec
|
|
destination
|
|
|
[JBoss-user] [Messaging, JMS & JBossMQ] - Re: JMS JDBC Persistence and server restart.
If you find something wrong with the WIKI docs, feel free to correct it or at least point it out. Anybody can update the WIKI which is both a good thing and bad thing. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863121#3863121 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3863121 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS & JBossMQ] - Re: JMS JDBC Persistence and server restart.
FAQ:
http://www.jboss.org/wiki/Wiki.jsp?page=WhatIsTheCorrectWayToMakeADurableSubscription
Preconfigured clients ids (for the testsuite) from
deploy/jms/hsqldb-jdbc-state-service.xml:
| POPULATE.TABLES.03 = INSERT INTO JMS_USERS (USERID, PASSWD, CLIENTID)
VALUES ('john', 'needle', 'DurableSubscriberExample')
|
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863120#3863120
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3863120
---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS & JBossMQ] - Re: JMS JDBC Persistence and server restart.
You obviously have some skills since you claim a Phd.
For us to help you we need enough information (supplying a simple mdb jar
that demostrates your problem would be one solution).
Debugging (show us what you are doing):
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=43573
Post the logging for the MDB startup (i.e. when it makes the construction)
and JBossMQ.
Including what happens at the send to JBossMQ.
Checking your Config (minimum):
Show your ejb-jar.xml/jboss.xml with the full context, i.e. the entire MDB
jbossmq-state.xml (no longer used)
http://www.jboss.org/wiki/Wiki.jsp?page=ConfigJBossMQState
Just adding:
| public void onMessage(Message m)
| {
| System.out.println(m);
| ...
|
will show me a lot of information, i.e. the message properties (like persistence
and the subscription id).
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863119#3863119
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3863119
---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS & JBossMQ] - Re: JMS JDBC Persistence and server restart.
According to the JMX console, despite all efforts I am still unable to create durable subscriptions. I've searched through several web documents however there are serious discrepancies between different solutions. It is not clear (diffrent sources suggest different things) whether the jbossmq-state.xml (the one in the conf directory) should contain TopicName or simply Topic attribute in the DurableSubscriptions section, I tried both without success. I am even not sure if users are supposed to change the .xml file in question (it is included in the docs library but not in the default server configuration.) | | 10001 | dur1 | MessagingTopic | | In connection with jboss.xml I've found that giving mdb-client-id attribute (which again has been suggested by several sources) results in a conflict between the ejb-jar.xml (the AS says that the client-id has been given) so I put it into a comment section (actually I don't really know what the mdb-subcription-id tag means, I couldn't found any descripiton. | OutboundProxyBean | jms/MessagingTopic | john |needle | |mySubscription | Using the 'guest' client in the ejb-jar.xml and the code segment above, viewing the DestinationManager service at jmx-console, the subscription-id is always 1 (not the 10001 value I set). Actually, the difference between client-id and subscription-id is not clear. Again I have to say, any help would be appreciated: Frank-15 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863077#3863077 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3863077 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS & JBossMQ] - Re: JMS JDBC Persistence and server restart.
Hi Adrian, I'm afraid, the tone of the posts of this forum tend to turn to an undesired direction. In our project we experienced the same problems. We are new to JBoss (we used other application servers in the previous projects), so could you please provide us the names of the relavant XMLs and (if possible) some sample Java code and the required XML configurations. Besides, could you please provide us some URLs of the relevant docs. I suppose we read the necessary docs, but you might be right, and like Frank-15, we did not read enough. Thanks in advance, Attila Ulbert, PhD View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862856#3862856 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862856 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS & JBossMQ] - Re: JMS JDBC Persistence and server restart.
No it makes it Durable. The stuff you have posted does not show anything. It is just some xml out of context. It does not prove you have that xml in the right place, that you actually deployed that xml, etc. If you want to see the subscription use the JMX console. Find your topic in jboss.mq.destinations and then list the subscriptions. All I have seen so far in this post in lots of assertions with the usual "IT DOES NOT WORK". So show me what it IS doing. I am not going to guess or go through 20 questions trying to get the information out of you. For the 10,000th time, use "READ THIS FIRST". It explains the kind of information we need to help you. In fact, enabling the logging will probably mean you can help yourself because you will see exactly what subscription it is creating in the JMS server and what is happening to the sent messages, including whether JBossMQ thinks they are persistent. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862792#3862792 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862792 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS & JBossMQ] - Re: JMS JDBC Persistence and server restart.
Sorry, but I don't really get what you mean. According to your post the following code, which I've quoted in my previous writing means that the topic subscription is configured to be NonDurable? subscriptionDurability | Durable If so, please provide me detailed description how to make a Topic durable. Thank you in advance: Frank-15 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862769#3862769 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862769 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS & JBossMQ] - Re: JMS JDBC Persistence and server restart.
What you describe is what is expected. If you send a persistent message to a NonDurable topic subscription there is little point persisting the message since the topic subscription will vanish (including all the messages contained within it) on a server crash or client disconnection. For Topics, only the combination of a persistent message sent to a DURABLE topic subscription is reliable. You can find this put succintly on the WIKI: "Guaranteed Delivery using persistent messages and durable subscriptions." View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862763#3862763 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862763 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS & JBossMQ] - Re: JMS JDBC Persistence and server restart.
In this post I will provide a detailed description of the different settings applied to solve the persistency problems. 1. According to EJB 2.1 Standard I set the receiver MDB to Durable and give clientId and subscriptionName properties in the ejb-jar.xml. (Actually I set guestimate values to latter two attributes.) | | subscriptionDurability | Durable | | | clientId | 10001 | | | subscriptionName | dur1 | | 2. I changed the security settings in the xml containing Topic descriptions. | jboss.mq:service=DestinationManager | jboss.mq:service=SecurityManager | - | | - | | | | | | | jms/MessagingTopic | 3. As provided in my previous posts, I set everything in connection with message sending to PERSISTENT. 4. I do not have any additional components (like IBM-MSMQ Series, etc.) installed on my system. Can it be a possibble problem source? Any further help would be greatly appreciated: Frank-15 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862759#3862759 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862759 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS & JBossMQ] - Re: JMS JDBC Persistence and server restart.
Well it sounds strange to me. I've set container-managed transactions for my receiver MessageDrivenBean and it seems to process the messages well (no exception occurs, etc.) Still, those messages left unprocessed (most possibbly due to heavy load) got persisted only by temporary means. So my question is still: how can you truly persist your JMS messages under JBOSS 4.0.1? Frank-15 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862708#3862708 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862708 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS & JBossMQ] - Re: JMS JDBC Persistence and server restart.
Looks like the associated message transaction is still open (not commited). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862677#3862677 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862677 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS & JBossMQ] - Re: JMS JDBC Persistence and server restart.
Actually, I set everything to DeliveryMode.PERSISTENT before sending the message (as follows): Destination topic = (Destination) ctx.lookup(MyJndiName); | MessageProducer publisher = session.createProducer(topic); | publisher.setDeliveryMode(DeliveryMode.PERSISTENT); | | ... | | objMsg = MySession.createObjectMessage(); | objMsg.setObject(MyMessageObject); | objMsg.setJMSDeliveryMode(DeliveryMode.PERSISTENT); | | ... | | publisher.send(objMsg, DeliveryMode.PERSISTENT, MyPriority, javax.jms.Message.DEFAULT_TIME_TO_LIVE); Still, my messages got persisted with a 'T' mark in the opcode column of JMS_MESSAGES. Any further help would be greatly appreciated. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862571#3862571 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862571 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS & JBossMQ] - Re: JMS JDBC Persistence and server restart.
Then sender of the message chooses whether or not its persistent across server restarts. It is not controlled by the message cache or pm. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862037#3862037 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862037 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
