[jboss-user] [JBoss Messaging Users] - Qeustion on transactions and restarting the Server
Hi Howard! I have problems to explain the following problem: (JBM1.4 build 7798 with OderingGroup enabled via CF) (But I think OG has nothing to do with it) I have a consumer which get one message transacted like this | ... | @Resource(mappedName="java:/JmsXA") | private ConnectionFactory cf; | ... | Connection connection = cf.createConnection(); | connection.start(); | ... | Session session = connection.createSession(true, Session.SESSION_TRANSACTED); | MessageConsumer consumer = session.createConsumer(m_queue); | Message msg = consumer.receive(2); | Now I do the following: - Message is received - While I handle the message (in the transaction) i kill the Server (real kill) After I restart my server my consumer will NOT get the same message again. It gets the next one. If I look into the jbm_msg_ref I see one message with Transaction_ID 41157221480464402 and state "-" and one entry in the tx table. As I can see this message stays there forever. Whats the problem or the reason here? In my case this message must be retried again until the maxdeliverycount is reached and then the next must be delivered. So in my case this scrambles my order. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4253527#4253527 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4253527 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging Users] - Re: paging problem with orderingGroup enabled
Sorry. next message because I can not edit previous once :-) I just debugged to the code and while it handles and then stops the promptDelivery is never true! So this could not be the Problem. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252597#4252597 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252597 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging Users] - Re: paging problem with orderingGroup enabled
forgot to say Using build 7797 and set OrderingGroup via the ConnectionFactory on both servers. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252591#4252591 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252591 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging Users] - Re: paging problem with orderingGroup enabled
Hi Howard. OrderingGroup Names are not changed anymore. But if I do my testcases in my testenvironment the handling still stops!! I have 2000 Messages on Server A On Server B I have a bridge which pulls messages from A to B My queues are configured to fullsize=20 page und downcache=5. Then: - I start up my 2 servers. - The Bridge on B starts sending messages from A to B. - I add extra messages via a testclient to the queues on A and/or B - Then the Bridge stops pulling messages from A to B. (I think because of added message on A) - And also my message handler stops handling the pulled messages from the local queue on B. (because of extra message on B?!) I tried to restart the bridge (stop/start) but this has no effect! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252590#4252590 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252590 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging Users] - Re: paging problem with orderingGroup enabled
I also saw this wron check. But I had no idea what promptDelivery is all about so I have not followed it. Anyway. What do you think of the timeline? Do you have to fix other bugs first? I dont wanna have a concrete date. Just an hint to plan my release cycles too. THX View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252381#4252381 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252381 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging Users] - Re: paging problem with orderingGroup enabled
Ok... And please also make sure that those added messages while handling the paged messages added at the end of the queue. So preserve message order also in case of paging. Thx... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252274#4252274 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252274 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging Users] - Re: paging problem with orderingGroup enabled
Hi Howard! I investigated my problem more deeply. First I have to say, that the OrderingGroup of bridged messages are overwritten by the setting in the connection factory. Not that nice I think. So I send a message with ordering group G1 to a Queue. This message is bridged to another server where ordering group attributes are set at the connection factory to group GDefault. Then the messages have the group GDefault iso G1. Bug or a feature :-) ? Second: I have added some tracing to the OrderingGroupMonitor to see what is registered and what completed. While my server starts up it loaded the first 20 paged messages and adds them to the OrderingGroupMonitor. Then it starts handling the messages and calls completed on the Monitor, which removed the ref from the group. After 5 messages are handled the JDBCPersistenceManager loads the next 5 paged messages and adds them. That behaviour is fine! But if a message is added to the queue (new message comes in) which have the same orderinggroup, this is registered too on the Monitor. But the message itself is added to the DownCache. This seams to be a bug or? If a message is added to a "full" queue which is paged then this should not be registered to the monitor, or? Maybe this is the reason, why the delivery stops The behaviour you can see below: | 20 times registering: | | 11:28:50,359 TRACE @main [org.jboss.messaging.core.impl.OrderingGroupMonitor] restistered MID '41154740253458432' for OrdGrp 'IMSDefaultGroup' and Destination 'incomingSyncRequests' | 11:28:50,359 TRACE @main [org.jboss.messaging.core.impl.OrderingGroupMonitor] restistered MID '41154740257849345' for OrdGrp 'IMSDefaultGroup' and Destination 'incomingSyncRequests' | 11:28:50,359 TRACE @main [org.jboss.messaging.core.impl.OrderingGroupMonitor] restistered MID '41154740259258370' for OrdGrp 'IMSDefaultGroup' and Destination 'incomingSyncRequests' | 11:28:50,359 TRACE @main [org.jboss.messaging.core.impl.OrderingGroupMonitor] restistered MID '41154740260470787' for OrdGrp 'IMSDefaultGroup' and Destination 'incomingSyncRequests' | 11:28:50,359 TRACE @main [org.jboss.messaging.core.impl.OrderingGroupMonitor] restistered MID '41154740261191684' for OrdGrp 'IMSDefaultGroup' and Destination 'incomingSyncRequests' | 11:28:50,359 TRACE @main [org.jboss.messaging.core.impl.OrderingGroupMonitor] restistered MID '41154740262076421' for OrdGrp 'IMSDefaultGroup' and Destination 'incomingSyncRequests' | 11:28:50,359 TRACE @main [org.jboss.messaging.core.impl.OrderingGroupMonitor] restistered MID '41154740262600710' for OrdGrp 'IMSDefaultGroup' and Destination 'incomingSyncRequests' | 11:28:50,359 TRACE @main [org.jboss.messaging.core.impl.OrderingGroupMonitor] restistered MID '41154740263747591' for OrdGrp 'IMSDefaultGroup' and Destination 'incomingSyncRequests' | 11:28:50,359 TRACE @main [org.jboss.messaging.core.impl.OrderingGroupMonitor] restistered MID '41154740264697864' for OrdGrp 'IMSDefaultGroup' and Destination 'incomingSyncRequests' | 11:28:50,359 TRACE @main [org.jboss.messaging.core.impl.OrderingGroupMonitor] restistered MID '41154740265484297' for OrdGrp 'IMSDefaultGroup' and Destination 'incomingSyncRequests' | 11:28:50,359 TRACE @main [org.jboss.messaging.core.impl.OrderingGroupMonitor] restistered MID '41154740267089930' for OrdGrp 'IMSDefaultGroup' and Destination 'incomingSyncRequests' | 11:28:50,359 TRACE @main [org.jboss.messaging.core.impl.OrderingGroupMonitor] restistered MID '41154740268236811' for OrdGrp 'IMSDefaultGroup' and Destination 'incomingSyncRequests' | 11:28:50,359 TRACE @main [org.jboss.messaging.core.impl.OrderingGroupMonitor] restistered MID '41154740269252620' for OrdGrp 'IMSDefaultGroup' and Destination 'incomingSyncRequests' | 11:28:50,359 TRACE @main [org.jboss.messaging.core.impl.OrderingGroupMonitor] restistered MID '41154740270006285' for OrdGrp 'IMSDefaultGroup' and Destination 'incomingSyncRequests' | 11:28:50,359 TRACE @main [org.jboss.messaging.core.impl.OrderingGroupMonitor] restistered MID '41154740270530574' for OrdGrp 'IMSDefaultGroup' and Destination 'incomingSyncRequests' | 11:28:50,359 TRACE @main [org.jboss.messaging.core.impl.OrderingGroupMonitor] restistered MID '41154740272136207' for OrdGrp 'IMSDefaultGroup' and Destination 'incomingSyncRequests' | 11:28:50,359 TRACE @main [org.jboss.messaging.core.impl.OrderingGroupMonitor] restistered MID '41154740273217552' for OrdGrp 'IMSDefaultGroup' and Destination 'incomingSyncRequests' | 11:28:50,359 TRACE @main [org.jboss.messaging.core.impl.OrderingGroupMonitor] restistered MID '41154740274888721' for OrdGrp 'IMSDefaultGroup' and Destination 'incomingSyncRequests' | 11:28:50,359 TRACE @main [org.jboss.messaging.core.impl.OrderingGroupMonitor] restistered MID '41154740275707922' for OrdGrp 'IMSDefaultGroup' and Destination 'incomingSyncRequests' | 11:28:50,359 TRACE @main [org.jboss.m
[jboss-user] [JBoss Messaging Users] - paging problem with orderingGroup enabled
Hi Howard!
I solved the orderinggroup handling by using one group and enabled it via
connectionfactory.
But now after my Server starts up and reloads the paged messages it stops after
the first set of messages are received.
Means:
To Test I have set fullsize to 20 and pagesize and downcache to 5.
My queue has 2000 messages.
After I received the first 20 messages the system stops. The database still
contains messages and while debugging I also see that each 5 consumed messages
the JDBCPersistenceManager.getPagedReferenceInfos() is called to load and add
the next paged messages. I also saw that the internal messageRef List contains
these reloaded messages.
But still, after the 20th message the consuming stops.
I first thought that its because of my self written transaction aware consumer
that also receives message in order. But after I refactored this back to
MessageDrivenBean the same error occurs.
My setup:
Queue:
|
|
| jboss.messaging:service=ServerPeer
|
|20
|5
|5
|
|
MDB:
| @MessageDriven(activationConfig = {
| @ActivationConfigProperty(propertyName = "destinationType", propertyValue =
"javax.jms.Queue"),
| @ActivationConfigProperty(propertyName = "destination", propertyValue =
IMConstants.QUEUE_INCOMINGSYNCREQUESTS),
| @ActivationConfigProperty(propertyName = "maxSession", propertyValue = "1"),
| @ActivationConfigProperty(propertyName = "maxMessages", propertyValue =
"1") })
| public class GlobalMessageDispatcherBean implements MessageListener {
|
|
CF:
|
| jboss.messaging:service=ServerPeer
| jboss.messaging:service=Connector,transport=sslbisocket
| jboss.messaging:service=PostOffice
|
|
|
| /ConnectionFactory
| /XAConnectionFactory
| java:/ConnectionFactory
| java:/XAConnectionFactory
|
|
| true
| IMSDefaultGroup
|
|
Maybe it has to do with this singleton MDB configuration but it should work
with it too, or?
Using JBM 1.4.5 build 7766
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251996#4251996
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251996
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging Users] - Re: enableOrderingGroup() not available inside ejb3 Bean an
Hi Howard! I know! But that is not the question. I think the wrapper should not provide other methods than the JMS Spec says. Maybe there should be a way to get the delegate. But from the JBM Usage perspective. Is there a way to use orderinggroup the programatic way with JBM enlist in the ongoing transaction? What if I use the XAConnectionFactory iso JmsXA? Any other ideas? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251883#4251883 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251883 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging Users] - enableOrderingGroup() not available inside ejb3 Bean an JmsX
Hi!
Any hint on this?
I testest OrderingGroup on 1.4.5 (build 7766) with a client like this:
| Connection connection = getConnection();
| Session session = connection.createSession(false,
Session.AUTO_ACKNOWLEDGE);
| JBossMessageProducer sender = (JBossMessageProducer)
session.createProducer(queue);
| sender.enableOrderingGroup("Group1");
|
The Connection Factory is fetched using
| Hashtable env = new Hashtable();
| env.put(Context.INITIAL_CONTEXT_FACTORY,
"org.jnp.interfaces.NamingContextFactory");
| env.put(Context.URL_PKG_PREFIXES,
"org.jboss.naming:org.jnp.interfaces");
| env.put(Context.PROVIDER_URL, "localhost:22099");
|
| InitialContext ic = new InitialContext(env);
| cf = (ConnectionFactory) ic.lookup("ConnectionFactory");
| queue = (Queue) ic.lookup("/queue/testQueue");
| ic.close();
|
It works perfect.
Now I want to migrate this to my ejb3 beans which sends messages but uses
transactions.
I am using:
| @Resource(mappedName="java:/JmsXA")
| private ConnectionFactory cf;
|
| ...
|
| Connection connection = cf.createConnection();
| connection.start();
|
| Session session = connection.createSession(true,
Session.SESSION_TRANSACTED);
| JBossMessageProducer sender = (JBossMessageProducer)
session.createProducer(queue);
| sender.enableOrderingGroup("Group1");
|
|
This gives a class cast exception because createProducer returns
org.jboss.resource.adapter.jms.JmsMessageProducer and not JBossMessageProducer.
The JBossMessageProducer is part of JmsMessageProducer but I can not get it.
I want to use more than one ordering group so it would be nice to be able to
set it via the producer.
Any hint how I can handle it with transaction support?
At pdf Userguide page 21 it says regarding JmsXA
"JMS XA Resource adapter, use this to get transacted JMS in beans"
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251785#4251785
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251785
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging Users] - Re: Ordering Group and Queue-FullSize reload problem
SORRY! Forget last post. I had still an old messaging jar in my lib dir. So if you have this kind of error just replace the messaging.jar to the right version :-) And by the way... The bugfix solved the bug also on my side. Thx!! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251516#4251516 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251516 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging Users] - Re: Ordering Group and Queue-FullSize reload problem
Hi Howard! Sorry I am late. I have just retested the problem with 1.4.5. Build 7766. I have the same DB entries while my last tests. Some page ords are filled some still NULL. While I restart the Server I got: | 15:22:26,843 INFO [TestMessageHandlerBean] Got:125 mID:ID:JBM-618ec024-cadb-486e-8d82-cf0315dbd522 | 15:22:26,875 INFO [TestMessageHandlerBean] Got:126 mID:ID:JBM-66160cb6-f743-4af5-a6d3-d1e592d20695 | 15:22:26,968 INFO [TestMessageHandlerBean] Got:127 mID:ID:JBM-b3f619b1-7a8a-43aa-9d4c-478addf3e647 | 15:22:27,031 INFO [TestMessageHandlerBean] Got:128 mID:ID:JBM-095a71b7-b8f9-420a-ae46-64027453e110 | 15:22:27,046 ERROR [ChannelSupport] Queue[15919140/2/176-testQueue] Failed to deliver | java.lang.IllegalStateException: Didn't load expected number of references, loaded: 36 expected: 50 | at org.jboss.messaging.core.impl.JDBCPersistenceManager.getPagedReferenceInfos(JDBCPersistenceManager.java:914) | at org.jboss.messaging.core.impl.PagingChannelSupport.loadPagedReferences(PagingChannelSupport.java:253) | at org.jboss.messaging.core.impl.PagingChannelSupport.checkLoad(PagingChannelSupport.java:361) | at org.jboss.messaging.core.impl.PagingChannelSupport.removeFirstInMemory(PagingChannelSupport.java:345) | at org.jboss.messaging.core.impl.ChannelSupport.deliverInternal(ChannelSupport.java:725) | at org.jboss.messaging.core.impl.MessagingQueue.deliverInternal(MessagingQueue.java:506) | at org.jboss.messaging.core.impl.ChannelSupport.deliver(ChannelSupport.java:380) | at org.jboss.jms.server.endpoint.ServerSessionEndpoint$2.run(ServerSessionEndpoint.java:1574) | at org.jboss.messaging.util.OrderedExecutorFactory$ChildExecutor.run(OrderedExecutorFactory.java:120) | at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) | at java.lang.Thread.run(Thread.java:619) | 15:22:27,093 INFO [TestMessageHandlerBean] Got:129 mID:ID:JBM-f819aaf8-e16b-4af4-957a-60ccd986aa20 | 15:22:27,093 ERROR [ChannelSupport] Queue[15919140/2/176-testQueue] Failed to deliver | java.lang.IllegalStateException: Didn't load expected number of references, loaded: 36 expected: 50 | at org.jboss.messaging.core.impl.JDBCPersistenceManager.getPagedReferenceInfos(JDBCPersistenceManager.java:914) | at org.jboss.messaging.core.impl.PagingChannelSupport.loadPagedReferences(PagingChannelSupport.java:253) | at org.jboss.messaging.core.impl.PagingChannelSupport.checkLoad(PagingChannelSupport.java:361) | at org.jboss.messaging.core.impl.PagingChannelSupport.removeFirstInMemory(PagingChannelSupport.java:345) | at org.jboss.messaging.core.impl.ChannelSupport.deliverInternal(ChannelSupport.java:725) | at org.jboss.messaging.core.impl.MessagingQueue.deliverInternal(MessagingQueue.java:506) | at org.jboss.messaging.core.impl.ChannelSupport.deliver(ChannelSupport.java:380) | at org.jboss.jms.server.endpoint.ServerSessionEndpoint$2.run(ServerSessionEndpoint.java:1574) | at org.jboss.messaging.util.OrderedExecutorFactory$ChildExecutor.run(OrderedExecutorFactory.java:120) | at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) | at java.lang.Thread.run(Thread.java:619) | 15:22:27,140 ERROR [ChannelSupport] Queue[15919140/2/176-testQueue] Failed to deliver | java.lang.IllegalStateException: Didn't load expected number of references, loaded: 36 expected: 50 | at org.jboss.messaging.core.impl.JDBCPersistenceManager.getPagedReferenceInfos(JDBCPersistenceManager.java:914) | at org.jboss.messaging.core.impl.PagingChannelSupport.loadPagedReferences(PagingChannelSupport.java:253) | at org.jboss.messaging.core.impl.PagingChannelSupport.checkLoad(PagingChannelSupport.java:361) | at org.jboss.messaging.core.impl.PagingChannelSupport.removeFirstInMemory(PagingChannelSupport.java:345) | at org.jboss.messaging.core.impl.ChannelSupport.deliverInternal(ChannelSupport.java:725) | at org.jboss.messaging.core.impl.MessagingQueue.deliverInternal(MessagingQueue.java:506) | at org.jboss.messaging.core.impl.ChannelSupport.deliver(ChannelSupport.java:380) | at org.jboss.jms.server.endpoint.ServerSessionEndpoint$2.run(ServerSessionEndpoint.java:1574) | at org.jboss.messaging.util.OrderedExecutorFactory$ChildExecutor.run(OrderedExecutorFactory.java:120) | at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) |
[jboss-user] [JBoss Messaging] - Re: Bridge Stuck after reconnect
Of course. You are right. 2 Queues on Server A 2 Queues on Server B (Liberte2) Both Bridges are deployed on Server A. One send data from local Queue on A to Remote Queue on B (the outgoing thing) One send data from remote Queue on B to local Queue on A (the incommin thing) I used the SSL Bisocket configuration like in the example. I have not changed any setting there. It only happens if the servers are under heavy load. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241605#4241605 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241605 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Bridge Stuck after reconnect
Using 1.4.4 GA I have 2 Servers where messages are bridged from 2 Queues via 2 bridges. Server A Server B outgoing >>---OutgoingBridge_Liberte2--->> local_outgoing incoming <<---IncomingBridge_Liberte2---<< local_incoming Sometimes the messages stuck at the Server B site: Before that happens the bridge losts the connection and reconnects. Here are the logs: 13:49:37,942 WARN [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.preparefailed] [com.arjuna.ats.internal.jta.resources.arjunacore.preparefailed] XAResourceRecord.prepare - prepare failed with exception XAException.XA_RETRY | 13:49:37,942 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_36] - BasicAction.End() - prepare phase of action-id a046bd8:bcc:4a4c98a3:2fdbb failed. | 13:49:37,942 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_38] - Action Aborting | 13:49:38,223 WARN [org.jboss.jms.server.bridge.Bridge] jboss.messaging:name=OutgoingBridge_Liberte2,service=Bridge Failed to send + acknowledge batch, closing JMS objects | javax.transaction.RollbackException: [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] Can't commit because the transaction is in aborted state | at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commit(TransactionImple.java:255) | at org.jboss.jms.server.bridge.Bridge.sendBatchXA(Bridge.java:1322) | at org.jboss.jms.server.bridge.Bridge.sendBatch(Bridge.java:1382) | at org.jboss.jms.server.bridge.Bridge.access$2000(Bridge.java:68) | at org.jboss.jms.server.bridge.Bridge$BatchTimeChecker.run(Bridge.java:1648) | at java.lang.Thread.run(Unknown Source) | 13:49:38,426 WARN [org.jboss.remoting.Client] unable to remove remote callback handler: Can not remove callback listener from target server with id of a42z60-xlstvn-fwne1cca-1-fwne21xq-27+a42z60-xlstvn-fwne1cca-1-fwne21y6-2a as it does not exist as a registered callback listener. | 13:49:38,442 ERROR [org.jboss.jms.client.container.ClosedInterceptor] ClosedInterceptor.ClientSessionDelegate[c2-mb22enwf-1-acc1enwf-nvtslx-06z24a]: method getXAResource() did not go through, the interceptor is CLOSED | 13:49:38,442 WARN [org.jboss.jms.server.bridge.Bridge] jboss.messaging:name=OutgoingBridge_Liberte2,service=Bridge Will retry after a pause of 1 ms | 13:49:49,598 INFO [org.jboss.jms.server.bridge.Bridge] jboss.messaging:name=OutgoingBridge_Liberte2,service=Bridge Succeeded in reconnecting to servers | After that I have some messages in the incoming. And it seams that the incomming bridge is not working anymore. After I restarted the bridges and the Queues it starts bridging again. See log: | 14:00:17,266 INFO [Aeos.BridgeGeneratorServiceImpl] Stopping bridge 'jboss.messaging:name=IncommingBridge_Liberte2,service=Bridge'. | 14:00:18,688 WARN [org.jboss.remoting.Client] unable to remove remote callback handler: Can not remove callback listener from target server with id of a42z60-xlstvn-fwne1cca-1-fwne1zkn-1f+a42z60-xlstvn-fwne1cca-1-fwne21ij-1m as it does not exist as a registered callback listener. | 14:00:18,688 INFO [Aeos.BridgeGeneratorServiceImpl] Stopping bridge 'jboss.messaging:name=OutgoingBridge_Liberte2,service=Bridge'. | | ... see that the Warning is on the incoming bridge. | | 14:01:45,250 INFO [Aeos.BridgeGeneratorServiceImpl] Started bridge jboss.messaging:name=IncommingBridge_Liberte2,service=Bridge. Source: /queue/local_incomingSyncRequests Target: /queue/incomingSyncRequests | 14:01:45,968 INFO [Aeos.BridgeGeneratorServiceImpl] Started bridge jboss.messaging:name=OutgoingBridge_Liberte2,service=Bridge. Source: /queue/outgoingSyncRequests_Liberte2 Target: /queue/local_outgoingSyncRequests | After restarting the 2 Bridges the messages are send again... I use a self written BridgeGeneratorServiceImpl that dynamically configures and starts the Bridge. The transport is ssl. Any Idea why the message stuck after this connection error at the other bridge? Greets View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241479#4241479 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241479 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Ordering Group and Queue-FullSize reload problem
Hi Howard! Sorry... But its not fixed :-( I can reproduce the same issue with the latest branch version (from tomorrow) I know... its had to reproduce but it happens only if not all messages have a page_ord set while killing the server. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240581#4240581 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240581 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Ordering Group and Queue-FullSize reload problem
Of course I can! But I am overscheduled so I think I can try it not before Monday next week! I keep you informed! Thx Howard for quick support! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239299#4239299 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239299 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Ordering Group and Queue-FullSize reload problem
Howard! Here more analysis! I can see that the order is scambled. But this has nothing to do with the ordered load of the messages. It has to do with updating the Page_ORD. The above error can be reproduced if you kill the server before all Page_Ord`s are updated. So before UpdatePageOrderRunner().executeWithRetry(); finishes. Then I see in my database this! | ORD numbers not real numbers | | ORD PAGE_ORD | 1 NULL | 2 NULL | | 24 NULL | 25 25 | 26 26 | ... | 84 84 | 85 NULL | 86 NULL | ... | 115 NULL | As you can see after Ord 85 the page_ord was not yet set! Then I restart the server and while starting the QueueService the load() method is called. This results in calling loadFromStart() at the JDBC PersistenceManager. I don't know why but after the first call it loads 50 unpaged messages to the Queue(pageOrd=NULL) and updated one (the last one) to 85. ?!? So the ord message 115 has now page_ord 85.?? Then I stopped debugging. So it seams that setting the right page_ord numbers is not handled well if the system has not set the numbers for the newest messages! Hope this helps to reproduce the Bug View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238734#4238734 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238734 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Ordering Group and Queue-FullSize reload problem
Hi Howard! Again me with a JBM OrderingGroup BUG. Using newest Build of 1.4.5 (7304) My test scenario: - Client adds 500 Messages (Text with incrementing number) to a Queue. - The Queue is set to 50 | 25 | 25 - The handler is slower than the producer. - On receiving side I see well ordered messages. like: ... | 14:20:12,234 INFO [TestMessageHandlerBean] Got:176 mID:ID:JBM-475cc9ad-cbf7-4039-9fb5-8edf19d3d3c1 | 14:20:12,250 INFO [TestMessageHandlerBean] Got:177 mID:ID:JBM-f9f56a49-5d82-453a-80c7-9d850d090f73 | 14:20:12,265 INFO [TestMessageHandlerBean] Got:178 mID:ID:JBM-657effd8-3099-47bc-887c-fd4289009635 | ... But if I kill jboss while it handles the 500 messages (lets say at message 100) and restart it I see the following: The rest(400) of the 500 Messages are in the Queue! While starting jboss up the messaging system reloads the messages from the database. I can see that inside the table the first 50 messages have page_ord null and the others incrementing numbers. Then it starts handling by continue at the last message. 101, 102, 103 and so on. But while reloading messages after the fullsize barrier the order is scambled. On my first test only one message/number was missing which was handled then after message 500 My second test all messages are fine and in order My third test results in: ... | 14:20:16,265 INFO [TestMessageHandlerBean] Got:208 mID:ID:JBM-c3d5eaa5-01aa-48de-b37d-f193f203fb49 | 14:20:16,296 INFO [TestMessageHandlerBean] Got:209 mID:ID:JBM-b0e4841c-4acb-487d-9c89-d0fa7045bb7e | 14:20:16,328 INFO [TestMessageHandlerBean] Got:210 mID:ID:JBM-1a451bc1-c8a6-43f8-9bb6-e070fff2942a | 14:20:16,343 INFO [TestMessageHandlerBean] Got:492 mID:ID:JBM-64b01947-59fb-4404-8e3a-3cae255fb91f | 14:20:16,343 ERROR [TestMessageKeeper] Number sequence is not ok. Expected 211 but was:492 | 14:20:16,359 ERROR [TestMessageKeeper] Resetting to:492 | 14:20:16,375 INFO [TestMessageHandlerBean] Got:493 mID:ID:JBM-018565ac-4ed3-453c-84fb-14b7251062a4 | 14:20:16,421 INFO [TestMessageHandlerBean] Got:494 mID:ID:JBM-cfc1f42b-6c5d-4309-8e71-d3c39cd91866 | 14:20:16,453 INFO [TestMessageHandlerBean] Got:495 mID:ID:JBM-2f052b3a-e2c7-4c58-9615-b3bd299e8d9f | 14:20:16,468 INFO [TestMessageHandlerBean] Got:496 mID:ID:JBM-42841e9f-cd32-4aa9-89d7-d0232edc9987 | 14:20:16,500 INFO [TestMessageHandlerBean] Got:497 mID:ID:JBM-aaf28cb8-6f1c-4e86-aac6-cee850440801 | 14:20:16,531 INFO [TestMessageHandlerBean] Got:498 mID:ID:JBM-cdfac31d-3b21-497a-8e44-c649c4aead0c | 14:20:16,531 INFO [TestMessageHandlerBean] Got:499 mID:ID:JBM-3a2226c1-6375-49b9-baed-ca1945b41e02 | 14:20:16,562 INFO [TestMessageHandlerBean] Got:500 mID:ID:JBM-0e720c52-1eb9-4b77-9596-9d78e31031ff | 14:20:16,578 INFO [TestMessageHandlerBean] Got:211 mID:ID:JBM-20ccaeca-f409-455a-b3b4-69519fd065e2 | 14:20:16,578 ERROR [TestMessageKeeper] Number sequence is not ok. Expected 501 but was:211 | 14:20:16,578 ERROR [TestMessageKeeper] Resetting to:211 | 14:20:16,640 INFO [TestMessageHandlerBean] Got:212 mID:ID:JBM-67d13844-da4b-4a75-a78c-707e7c1b0d9e | 14:20:16,718 INFO [TestMessageHandlerBean] Got:213 mID:ID:JBM-84831294-f9d5-431d-982d-38994135c978 | 14:20:16,765 INFO [TestMessageHandlerBean] Got:214 mID:ID:JBM-e99d350a-f824-42a8-9536-d265a0babc9b | 14:27:34,453 INFO [TestMessageHandlerBean] Got:215 mID:ID:JBM-41c58e16-fda5-449f-b508-a7c65f1f3d6e | ... So it seams that the order is not garanteed anymore if the size of the queue exceeds the FullSize setting. Is this a BUG? By the way. I tested this Rollback Bug of OrderingGroup. This works now perferct! Good (and fast) Job :-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238469#4238469 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238469 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: OrderingGroup and Transaction Rollback
Thx for explanation. But still, why is my message after the rollback not the next message, which is delivered by the JMS System. I still have this reproduceable: 1, Rollbackmsg(first try) , 2, 3 , Rollbackmsg(second try), ... , Rollbackmsg(last try) ( simplified: A, B, C, D, B, B, B, B, B) behaviour instead of the expected: 1, Rollbackmsg(first try), Rollbackmsg(second try), ... , Rollbackmsg(last try), 2, 3 ( simplified: A, B, B, B, B, B, B, C, D ) I think is must have something to do with this session.close() call which removes the reference from the Orderinggroup Can you explain? Bug or Feature :-)? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236174#4236174 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4236174 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Bridge stop should stop failureHandler too
Hi. JB 4.2.3 with JBM 144 I noticed that if I stop the bridge using jmx the failure handler still trying to solve the error. To be more exact. I start jboss but the bridge destination node is not there. I stop the bridge but this call tells me Bridge is already stopped. But still the retry handler tries to get a connection to the remote server each interval (in my case 10 seconds). It would be nice to add a "shouldstart" flag which is checked at the failureHandlers. A stop should always also stop the FailureHandlers and the Batchtime checker. A start again should start them of course :-) Greet Markus View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236036#4236036 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4236036 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: OrderingGroup and Transaction Rollback
Hi!
Ok. Here is my method which receives the message from the queue.
There is also a slowdown feature but this can be ignored here.
The method is called at a statefull sessionbean with CMT so a transaction is
just started.
| Session session = null;
| Connection conn = null;
| MessageConsumer consumer = null;
| try {
| conn = getConnection();
| boolean transacted = true;
| session = conn.createSession(transacted,
Session.SESSION_TRANSACTED);
|
| consumer = session.createConsumer(m_queue);
|
| Logger.debug(this, "blocking to receive message from queue");
|
| // keep waittime small to ensure handling inside the transaction
| Message msg = consumer.receive(2);
| if (msg != null) {
| // get deliverycount of the message. If it is the first
time the count is 1
| int redeliveryCount =
msg.getIntProperty("JMSXDeliveryCount");
| if (redeliveryCount > 1) {
| // at least the second retry so wait to slow consuming
down
| // in ms: 10, 20, 40, 80, 102400 (at the 10
delivery)
| long waittime = (long) (10 * Math.pow(2,
redeliveryCount));
| Logger.info(this, "Redelivery is slowed down. Waittime
(ms):" + waittime);
| try {
| Thread.sleep(waittime);
| }
| catch (InterruptedException e) {
| // ignore
| }
| }
| // HERE the message is delegated to a handler. see expl.
below
| jmsMessageHandler.handleMessage(msg);
| }
| }
| catch (JMSException e) {
| throw new RuntimeException("Problems handling message.", e);
| }
| finally {
| if (consumer != null)
| try {
| consumer.close();
| }
| catch (Exception ignore) {
| }
| if (session != null)
| try {
| session.close();
| }
| catch (Exception ignore) {
| }
| if (conn != null)
| try {
| conn.close();
| }
| catch (Exception ignore) {
| }
| }
|
So I open a connection, create a transacted session and receive ONE message.
Then I delegate the message to a handler. In the final I close the resources.
The handler just uses:
private SessionContext ctx;
and then calls ctx.setRollbackOnly();
When I debug I see that the first message is delivered. The
OrderingGroup.markSending() is called and the handler handles the message.
Then while the transaction is commited the unregister is called.
Now comes the failing message where the transaction is marked as rollback only.
While the session is closed in the final block the unregister method is called
again!! So the message is removedfrom the linked list!
Stack trace:
OrderingGroup.unregister(MessageReference) line: 121
| OrderingGroupMonitor.unmarkSending(MessageReference) line: 178
| MessagingQueue(ChannelSupport).cancelInternal(MessageReference) line: 609
| MessagingQueue(PagingChannelSupport).cancelInternal(MessageReference) line:
323
| MessagingQueue(ChannelSupport).cancel(Delivery) line: 328
| SimpleDelivery.cancel() line: 110
| ServerSessionEndpoint.cancelDeliveryInternal(Cancel) line: 1643
| ServerSessionEndpoint.cancelDelivery(Cancel) line: 456
|
SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$cancelDelivery$aop(Cancel)
line: 145
| SessionAdvised$cancelDelivery_2980985335510575813.invokeNext() line: not
available
| ServerLogInterceptor.invoke(Invocation) line: 105
| SessionAdvised$cancelDelivery_2980985335510575813.invokeNext() line: not
available
| SessionAdvised.cancelDelivery(Cancel) line: not available
| SessionCancelDeliveryRequest.serverInvoke() line: 84
| JMSServerInvocationHandler.invoke(InvocationRequest) line: 143
| SSLBisocketServerInvoker(ServerInvoker).invoke(InvocationRequest) line: 862
| ServerThread.processInvocation(SocketWrapper) line: 609
| ServerThread.dorun() line: 421
| ServerThread.run() line: 174
|
What I see in OrderingGroupMonitor is that unmarksending AND messageCompleted
has more or less the same code? Can this be right?
Both call:
OrderingGroup group = orderingGroups.get(grpName);
if (group != null)
{
group.unregister(ref);
}
Greets
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236007
[jboss-user] [JBoss Messaging] - OrderingGroup and Transaction Rollback
Hi!
I just tested the new function ordering group of 1.4.4.GA because I want to
replace my own ordering keeper implementation.
But What I see is that is does not work with transaction rolled back:
What I have done:
I add 4 Messages:
| Connection connection = getConnection();
| Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
| JBossMessageProducer sender = (JBossMessageProducer)
session.createProducer(queue);
| sender.enableOrderingGroup("testordergrp");
|
| TextMessage msg1 = session.createTextMessage("1");
| TextMessage msg2 = session.createTextMessage("Ordergrp -
shouldrollback");
| TextMessage msg3 = session.createTextMessage("2");
| TextMessage msg4 = session.createTextMessage("3");
| sender.send(msg1);
| sender.send(msg2);
| sender.send(msg3);
| sender.send(msg4);
| closeConnection(connection);
|
Those messages are added to the testqueue and as I also see they are added to
the LinkedList in the OrderingGroup.class. So this seems to be fine.
On my server I have a service which starts a consumeSingle() method from an
Statefull Session bean ( This method bean call automatically creates the XA
Transaction). Inside this consumeSingle() method I now receive one message! and
delegate it.
| conn = getConnection();
| boolean transacted = true;
| session = conn.createSession(transacted, Session.SESSION_TRANSACTED);
|
| consumer = session.createConsumer(m_queue);
|
| // keep waittime small to ensure handling inside the transaction
| Message msg = consumer.receive(2);
|
| // now delegate this message to the right handler
|
The second message causes an error so the tx is rolled back.
In the old implementation the Message was also rolled back to the queue and the
JMSXDeliveryCount was increased by one.
Next time consumeSingle() method was called this previous message was received
again and again until it was moved to DLQ.
But with the new version and the orderinggroup on this behaviour changed?!?.
The second Message is still delivered as the second message but after the
rollback first the other messages are delivered and at the end the second one
again??
My server log:
|
| INFO [TestMessageHandlerBean] Got:1
mID:ID:JBM-7228da24-988e-44e9-b1d5-36af6e220d3e
| INFO [TestMessageHandlerBean] Got:Ordergrp - shouldrollback
mID:ID:JBM-03e2198d-2e5d-490b-8631-56d596c689fe
| ERROR [TestMessageHandlerBean] Error: Rollback because:For input string:
"Ordergrp - shouldrollback"
| INFO [TestMessageHandlerBean] Got:2
mID:ID:JBM-89bc4425-68f6-476e-abbf-b55938d36dca
| INFO [TestMessageHandlerBean] Got:3
mID:ID:JBM-973afa1d-824a-4557-a316-9e9c1d6c9ed2
| INFO [TestMessageHandlerBean] Got:Ordergrp - shouldrollback
mID:ID:JBM-03e2198d-2e5d-490b-8631-56d596c689fe
| ERROR [TestMessageHandlerBean] Error: Rollback because:For input string:
"Ordergrp - shouldrollback"
| INFO [TestMessageHandlerBean] Got:Ordergrp - shouldrollback
mID:ID:JBM-03e2198d-2e5d-490b-8631-56d596c689fe
| ERROR [TestMessageHandlerBean] Error: Rollback because:For input string:
"Ordergrp - shouldrollback"
| INFO [TestMessageHandlerBean] Got:Ordergrp - shouldrollback
mID:ID:JBM-03e2198d-2e5d-490b-8631-56d596c689fe
| ERROR [TestMessageHandlerBean] Error: Rollback because:For input string:
"Ordergrp - shouldrollback"
| INFO [TestMessageHandlerBean] Got:Ordergrp - shouldrollback
mID:ID:JBM-03e2198d-2e5d-490b-8631-56d596c689fe
| ERROR [TestMessageHandlerBean] Error: Rollback because:For input string:
"Ordergrp - shouldrollback"
| INFO [TestMessageHandlerBean] Got:Ordergrp - shouldrollback
mID:ID:JBM-03e2198d-2e5d-490b-8631-56d596c689fe
| ERROR [TestMessageHandlerBean] Error: Rollback because:For input string:
"Ordergrp - shouldrollback"
| INFO [TestMessageHandlerBean] Got:Ordergrp - shouldrollback
mID:ID:JBM-03e2198d-2e5d-490b-8631-56d596c689fe
| ERROR [TestMessageHandlerBean] Error: Rollback because:For input string:
"Ordergrp - shouldrollback"
| INFO [TestMessageHandlerBean] Got:Ordergrp - shouldrollback
mID:ID:JBM-03e2198d-2e5d-490b-8631-56d596c689fe
| ERROR [TestMessageHandlerBean] Error: Rollback because:For input string:
"Ordergrp - shouldrollback"
|
Can you explain this? Does the orderingGroup does not work if a transaction is
rolled back?
Just for the history info:
I don't think that my own solution has something to do with this. I simply
receive() one message inside a transaction. This "service" just makes sure that
only one message is handles by one consumer at a time. I first had a singleton
MDB solution for this but the internal handling of message also queues at least
2 messages before delegating them to the MDB. So I had also problems with
ordering and rollback there too...
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4235208#4235208
Reply to the post :
http://www.jboss.org/inde
[jboss-user] [JBoss Messaging] - Re: Behavior with selector and fullSize cache
Hi ! Thx for explanation. But this basics I know already. I did the test with a limit of 50 and added a lot of messages for x y and z to my queue. I also undeployed all bridges. Then I deploy bridge x. All messages in the memory which contains the header property destination=x are bridged then. Some messages are reloaded but after a short time the memory queue contains only messages for y and z. The messages which are paged to db for x are NOT delivered. If I then deploy Bridge Y some messages of Y and (because of reload) some X are bridged. Then the Queue stopped again because only Z messages are in the memory queue. If I deploy Z the queue is completely bridged to all destinations. This behaviour of course makes sense! Paged messages are somehow invisible for the JMS system. But I think there should be a section in the bridge documentation (user guide) or somewhere else which points to this behaviour. Otherwise users maybe wonder why the queue "stops". I my case I think I have to create onle queue per destination. Otherwise I can not prevent memory problems if one or more destinations are not reachable. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4233492#4233492 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4233492 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Behavior with selector and fullSize cache
Hi! I am using one of the latest versions of the 1_4 branch We are using one queue where multiple bridges/clients consume/transport messages using a selector. Try to visualize it: :-) Queue A Bridge X fetch messages with selector destnode=X Bridge Y fetch messages with selector destnode=Y Bridge Z fetch messages with selector destnode=Z The business logic always create one message per destinationnode with the header property destnode set to X,Y or Z The messages in the queue are added in a sequence like: a(x),a(y),a(z), b(x),b(y),b(z), Our messages are really big. from 20k to 20 megabyte so we want to limit the fullSize from default 20 to 100 or similar. What happens now if destination X is not reachable for a longer time. What implications does this fullSize setting have then. This means that all message with destination (x) can not be delivered for that offline time. The messages in the queue then should look like this a(X),b(x),c(x),t(x),t(y),t(z) Lets say we set it to 100 and there are 120 (x) messages in the queue. If we now add 3 new messages for x,y and z, does this now mean that the y and z message is not cached in the memoryqueue. Are those messages then delivered? And if so is each message then fetched from the database? to summarize: What happens is I use a selector and set the fulSize setting to a very low value. THX for a short explanation! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4233312#4233312 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4233312 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB/JBoss] - Re: set TransactionTimeout during Runtime
Have you solved it? I have a similar issue but I don't want to increase the timeout for the 97% mainstream handling like you Greets View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4233281#4233281 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4233281 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge error because of network problems also influences
Just found the related Bug for that ping time: https://jira.jboss.org/jira/browse/JBMESSAGING-1487 But as I said only the non ssl file were updated. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222308#4222308 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222308 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge error because of network problems also influences
PROBLEMS SOLVED: 1. Message stuck issue I solved it with my workaround with this force remote setting! But I think it is related to this error: https://jira.jboss.org/jira/browse/JBMESSAGING-1456 which is fixed now. 2. Connection error! I am using the SSLBisocketInvoker and used the example configuration. This example configuration has not changed over the last versions! As I saw now is that the standard remoting bisocket invoker has changed a lot. For example there are new configurations like: |1 |5000 If you miss them the defaults are 2 seconds periode and 1 second timeout. This one second is too short on utilized systems and slower remote networks!! Howard, Tim there are more parameters in the default NON-SSL configuration that have changed. Can you please validate which one are also applicable on the ssl invoker and then update the ssl configuration example at remoting-sslbisocket-service.xml?? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222305#4222305 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222305 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge error because of network problems also influences
Howard. I did some more tests with this "message stuck after reconnect" problem. First a correction of my test. In step 5 I said restarting the bridge or the server A solves the problem. But this is not true. Only after I restartet the message sending server B restarts sending the messages to A. So it seams somehow that the messages are "send" to the wrong/old connection... I also continued testing and I can NOT reproduce it if I use the settings: true But without this force remote its easy to reproduce it in my system. If I disconnect the Network cable longer that 3 Seconds the reconnect works. But in cases of shorter disconnects like 1 second I see this problem. One hint maybe: As you know I have 2 bridges deployed. One for each direction. So the above testbridge BtoA and one AtoB. At this short disconnect I only see Errors on A related to the AtoB Bridge BUT NOT from this other bridge. Maybe this Bridge still thinks that the connection is fine but in the end it isn't because of the short network disconnect?!? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220141#4220141 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220141 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: JMS Bridge, Remote Connection Lost
Hi! I was to fast. With the definition of ipadresses and names in the windows hosts file it does not happen 3-5 seconds after the cannection is established but it happens from time to time. Can I configure this check more robust. Means check and if it seams to be an error check once again after a time before really decide that the remote site is not there anymore? Greets View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219891#4219891 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4219891 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: JMS Bridge, Remote Connection Lost
It seems that we have fixed this issue but I don't know why After I added the hostnames and ipadresses of all servers and nodes to the host file of the root server X I have not seen the error anymore. The question is why is the DNS lookup the problem. Is it to slow? Can you see anything from the logs? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219799#4219799 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4219799 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge error because of network problems also influences
Hi Howard. I think I have to solve this connection Lost issue first. I have added a Topic in the remoting forum for that too: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219740#4219740 Maybe this influence was no influence... Maybe it was just the side effect of this connection lost error. I also have tried the forceRemote setting with no effect. The biggest issue in my situation is that it happens so often but also that the messages are stuck after the reconnect. This has to do with Jira entry https://jira.jboss.org/jira/browse/JBMESSAGING-1543 I think. My test is simple: 1. start 2 servers A and B on different machines. 2. deploy a bridge on A which pull messages from B to A 3. unplug network cable --> result connection lost error: my reconnect time is 50 seconds 4. after 50 seconds the reconnect Bridge message occurs 5. add messages to the queue on A. Those are not transfered unless I restart the bridge via jmx or restart the server View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219757#4219757 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4219757 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: forceRemote timeout Problems
Thx Ron! with isParam="true" jms is working again. But unfortunately it has not solved my main issue. I have created a new Topic here so others can find it faster if its related: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219740#4219740 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219743#4219743 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4219743 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - JMS Bridge, Remote Connection Lost
I already asked a lot in JBM Forum but currently they have not find the issue.
I use this thread to summarize a short remoting issue. Maybe you guys knows
that these stack traces are all about.
In general I have 2 so called JMS brides deployed on Server X which bridge JMS
Messages from Server A to X and the second one X to A.
So 2 Queues, on each side. the Communication is triggered from X were the
bridge is deployed.
At X I get the Error:
| 09:57:05,624 WARN [Bridge]
jboss.messaging:name=IncommingBridge_ArcDeSeine,service=Bridge Detected failure
on connection
| javax.jms.JMSException: Failure on underlying remoting connection
| at
org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:102)
| at
org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:641)
|
Looking at the debug messages for more Detail I see:
| 09:57:02,624 DEBUG [org.jboss.remoting.ConnectionValidator]
ConnectionValidator[null, pingPeriod=2000 ms] connection retries: null
| 09:57:02,624 DEBUG [org.jboss.remoting.ConnectionValidator]
ConnectionValidator[SocketClientInvoker[9520f7, sslbisocket://nvc1216:24457],
pingPeriod=2000 ms] started
| 09:57:02,687 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] Added url:
file:/C:/AEOS-IMServer/IMServer/jboss/server/imserver/tmp/aopdynclasses/ucl1109316119710502160/?dynamic=true,
to ucl: org.jboss.mx.loading.unifiedclassload...@1ecdec0{ url=null
,addedOrder=13}
| 09:57:02,968 INFO [org.jboss.jms.server.bridge.Bridge]
jboss.messaging:name=IncommingBridge_ArcDeSeine,service=Bridge Succeeded in
connecting to servers
| 09:57:05,624 DEBUG [org.jboss.remoting.ConnectionValidator]
ConnectionValidator[SocketClientInvoker[1eebefb, sslbisocket://nvc1217:4457],
pingPeriod=2000 ms]'s connections is invalid
| 09:57:05,624 DEBUG [org.jboss.remoting.InvokerRegistry] removed
SocketClientInvoker[1eebefb, sslbisocket://nvc1217:4457] from registry
| 09:57:05,624 DEBUG
[org.jboss.remoting.transport.socket.MicroSocketClientInvoker]
SocketClientInvoker[1eebefb, sslbisocket://nvc1217:4457] disconnecting ...
| 09:57:05,624 WARN [org.jboss.jms.server.bridge.Bridge]
jboss.messaging:name=IncommingBridge_ArcDeSeine,service=Bridge Detected failure
on connection
| javax.jms.JMSException: Failure on underlying remoting connection
| at
org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:102)
| at
org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:641)
| 09:57:05,624 DEBUG [org.jboss.remoting.transport.socket.SocketWrapper]
ClientSocketWrapper[f9e396[SSL_RSA_WITH_RC4_128_MD5:
Socket[addr=nvc1217.nedap.local/10.4.107.217,port=4457,localport=1444]].f9e396]
closing
| 09:57:05,624 DEBUG [org.jboss.remoting.transport.socket.SocketWrapper]
ClientSocketWrapper[1953319[SSL_RSA_WITH_RC4_128_MD5:
Socket[addr=nvc1216.nedap.local/10.4.107.216,port=24457,localport=1437]].1953319]
closing
| 09:57:05,624 DEBUG [org.jboss.remoting.transport.socket.SocketWrapper]
ClientSocketWrapper[4de269[SSL_RSA_WITH_RC4_128_MD5:
Socket[addr=nvc1216.nedap.local/10.4.107.216,port=24457,localport=1438]].4de269]
closing
| 09:57:05,624 DEBUG [org.jboss.remoting.ConnectionValidator]
ConnectionValidator[SocketClientInvoker[1eebefb, sslbisocket://nvc1217:4457],
pingPeriod=2000 ms] stopped, returning true
| 09:57:05,624 DEBUG [org.jboss.remoting.ConnectionValidator]
org.jboss.remoting.connectionvalidator$waitonconnectionchecktimert...@14b6f24
detected connection failure: stopping LeasePinger
| 09:57:05,624 DEBUG [org.jboss.remoting.LeasePinger]
LeasePinger[SocketClientInvoker[7edb0f,
sslbisocket://nvc1217:4457](a42z60-hxurji-fsimy06l-1-fsin0nkm-4e)] setting
disconnect timeout to: -1
| 09:57:05,624 DEBUG [org.jboss.remoting.transport.socket.ServerThread]
WorkerThread#1[10.4.107.216:1438] closing socketWrapper:
ServerSocketWrapper[16dc700[SSL_RSA_WITH_RC4_128_MD5:
Socket[addr=/10.4.107.216,port=1438,localport=24457]].16dc700]
| 09:57:05,624 DEBUG [org.jboss.jms.server.remoting.ServerSocketWrapper]
cannot write CLOSING byte
| java.net.SocketException: Connection closed by remote host
| at com.sun.net.ssl.internal.ssl.SSLSocketImpl.checkWrite(Unknown Source)
| at com.sun.net.ssl.internal.ssl.AppOutputStream.write(Unknown Source)
| at java.io.BufferedOutputStream.flushBuffer(Unknown Source)
| at java.io.BufferedOutputStream.flush(Unknown Source)
| at java.io.DataOutputStream.flush(Unknown Source)
| at
org.jboss.jms.server.remoting.ServerSocketWrapper.close(ServerSocketWrapper.java:74)
| at
org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:520)
| at
org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:173)
| 09:57:05,624 DEBUG [org.jboss.remoting.transport.so
[jboss-user] [Remoting] - forceRemote timeout Problems
Hi!
I am using JBM with remoting 222sp11brew and I have some error while using the
bridge. see
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218858#4218858)
It is relatetd t the fact that I loose the connections to other JMS Servers.
Gao Howard said that I should try use the forceRemote property.
I have tried it but I receive timeouts then.
In the end the whole JMS is not working anymore.
He then adviced me to ask here in parallel if someone can explain this stack
trace :-)
the error is:
Caused by: org.jboss.remoting.ConnectionFailedException: Timed out trying to
create control socket
| at
org.jboss.remoting.transport.bisocket.BisocketClientInvoker.handleConnect(BisocketClientInvoker.java:272)
| at
org.jboss.remoting.MicroRemoteClientInvoker.connect(MicroRemoteClientInvoker.java:263)
| at org.jboss.remoting.Client.connect(Client.java:1528)
| at org.jboss.remoting.Client.connect(Client.java:468)
| at
org.jboss.remoting.callback.ServerInvokerCallbackHandler.connect(ServerInvokerCallbackHandler.java:161)
| at
org.jboss.remoting.ServerInvoker.getCallbackHandler(ServerInvoker.java:1863)
| at
org.jboss.remoting.ServerInvoker.handleInternalInvocation(ServerInvoker.java:1497)
| at
org.jboss.remoting.transport.bisocket.BisocketServerInvoker.handleInternalInvocation(BisocketServerInvoker.java:643)
| at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:853)
| at
org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:101)
|
| at org.jboss.remoting.Client.invoke(Client.java:1640)
| at org.jboss.remoting.Client.addCallbackListener(Client.java:1709)
| at org.jboss.remoting.Client.addListener(Client.java:927)
| at
org.jboss.jms.client.remoting.JMSRemotingConnection.addInvokerCallbackHandler(JMSRemotingConnection.java:259)
|
By the way! I am using an SSL Bisocket connector from the the jbm sslbisocket
example configuration.
|
|
|
|
| org.jboss.jms.wireformat.JMSWireFormat
| org.jboss.jms.wireformat.JMSWireFormat
| jms
| false
| ${jboss.bind.address}
| 24457
| org.jboss.jms.client.remoting.ClientSocketWrapper
| org.jboss.jms.server.remoting.ServerSocketWrapper
| jboss.messaging:service=ServerSocketFactory,type=SSL
| 1
| 214748364
| 10
| org.jboss.jms.server.remoting.DirectThreadPool
| true
| 1
| 0
| 10
| 200
| 1
|
|
|
| org.jboss.jms.server.remoting.JMSServerInvocationHandler
|
|
|
| jboss.messaging:service=ServerSocketFactory,type=SSL
|
|
|
| jboss.messaging:service=SocketBuilder,type=SSL
|
|
|
| true
|
|
|
|
Any ideas??
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218871#4218871
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218871
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: MessagingXAResourceRecovery can not reconnect
I forgot to say: JB 4.2.3 JBM 1.4.2.SP1 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218169#4218169 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218169 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: MessagingXAResourceRecovery can not reconnect
Hi! Have you solved that issue? I have the same behavior with my bridges. I have multiple nodes connected to one "root" node via bridges. In that root node all bridges are configured and usinf remoteProviderLoaders. I have added them on the jta configuration like: | | | | If I now kill one node and restart it, the bridges are reconnecting but I get the same warnings like you: | ... | 10:53:42,625 INFO [Bridge] jboss.messaging:name=IncommingBridge_NodeB,service=Bridge Succeeded in reconnecting to servers | 10:55:35,953 WARN [loggerI18N] [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException, XAException.XAER_RMFAIL | 10:57:46,234 WARN [loggerI18N] [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException, XAException.XAER_RMFAIL | 10:59:56,515 WARN [loggerI18N] [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException, XAException.XAER_RMFAIL | 11:02:06,890 WARN [loggerI18N] [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException, XAException.XAER_RMFAIL | ... | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218166#4218166 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218166 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge error because of network problems also influences
Hi Howard!
I did some tests over the weekend.
I added
true
or
true
to my invoker configuration (see below)
But this results in timeouts while getting connections so bridge or in general
JMS does not work then:
| Caused by: org.jboss.remoting.ConnectionFailedException: Timed out trying
to create control socket
| at
org.jboss.remoting.transport.bisocket.BisocketClientInvoker.handleConnect(BisocketClientInvoker.java:272)
| at
org.jboss.remoting.MicroRemoteClientInvoker.connect(MicroRemoteClientInvoker.java:263)
| at org.jboss.remoting.Client.connect(Client.java:1528)
| at org.jboss.remoting.Client.connect(Client.java:468)
| at
org.jboss.remoting.callback.ServerInvokerCallbackHandler.connect(ServerInvokerCallbackHandler.java:161)
| at
org.jboss.remoting.ServerInvoker.getCallbackHandler(ServerInvoker.java:1863)
| at
org.jboss.remoting.ServerInvoker.handleInternalInvocation(ServerInvoker.java:1497)
| at
org.jboss.remoting.transport.bisocket.BisocketServerInvoker.handleInternalInvocation(BisocketServerInvoker.java:643)
| at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:853)
| at
org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:101)
| at org.jboss.remoting.Client.invoke(Client.java:1640)
| at org.jboss.remoting.Client.addCallbackListener(Client.java:1709)
| at org.jboss.remoting.Client.addListener(Client.java:927)
| at
org.jboss.jms.client.remoting.JMSRemotingConnection.addInvokerCallbackHandler(JMSRemotingConnection.java:259)
|
By the way! I am using an SSL Bisocket connector from the the sslbisocket
example configuration.
This is my remoting-bisocket-service.xml:
|
|
|
|
|
| org.jboss.jms.wireformat.JMSWireFormat
| org.jboss.jms.wireformat.JMSWireFormat
| jms
| false
| ${jboss.bind.address}
| 24457
| org.jboss.jms.client.remoting.ClientSocketWrapper
| org.jboss.jms.server.remoting.ServerSocketWrapper
| jboss.messaging:service=ServerSocketFactory,type=SSL
| 1
| 214748364
| 10
| org.jboss.jms.server.remoting.DirectThreadPool
| true
| 1
| 0
| 10
| 200
| 1
|
|
|
| org.jboss.jms.server.remoting.JMSServerInvocationHandler
|
|
|
| jboss.messaging:service=ServerSocketFactory,type=SSL
|
|
|
| jboss.messaging:service=SocketBuilder,type=SSL
|
|
|
| true
|
|
|
|
What should we do now?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218145#4218145
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218145
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge error because of network problems also influences
I will try it on monday. Currently I try to get my IPMA-Level D certificate and I am back at my client on monday. I will keep you informend in this thread! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217145#4217145 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217145 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge error because of network problems also influences
Does https://jira.jboss.org/jira/browse/JBMESSAGING-1456 is maybe an explanation why the bridges/connections are influencing each other?? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216144#4216144 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216144 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge error because of network problems also influences
Hi Howard. Yes... I thing this is related to the message not bridges issue... But whats about the main issue, that other bridges are influenced by problems of another?? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215363#4215363 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215363 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge error because of network problems also influences
I try to add a img to explain the setup: [img]http://markuslutum.de/jboss/bridgeproblem.jpg[/img] View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215361#4215361 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215361 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge error because of network problems also influences
Hi Howard! No sorry... not easy to explain :-) All 6 Bridges are deployed on X X is our so called root server which do the message processing and delegates the messages to the other nodes. A, B and C are our nodes/instances which only uses local queues. Each node has an incoming and an outgoing queue. X has 3 JMSProviderLoader configured. One for each node. The example: | | RemoteJMSProvider_AeosA | org.jboss.jms.jndi.JNDIProviderAdapter | | /XAConnectionFactory | | /XAConnectionFactory | | /XAConnectionFactory | | java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory | java.naming.factory.url.pkgs=org.jnp.interfaces | java.naming.provider.url=localhost:2099 | | | Because there are 3 Nodes I have 3 Bridges for the incoming queue and 3 Bridges for the outgoing queue on instance X. On X there are also only 2 queues. The incoming bridges are sending all messages from "ABC incoming" to "X incoming". The Outgoing bridges uses selectors to only fetch the node (ABC) related messages out of the outgoing queue of X. In production we only have remote nodes. Currently 8 nodes and one root server X. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215311#4215311 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215311 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge error because of network problems also influences
another hint.. Maybe helps. I have no Idea what this means. If i stop the bridge which seems to hang and start it again I got some strange messages in my logfile: | 12:04:33,640 WARN [ClientConsumer] Timed out waiting for last delivery 4 got 1 | 12:04:33,843 WARN [LeasePinger] LeasePinger[SocketClientInvoker[6d7809, sslbisocket://OVSPC186:34457](4p7222-46h04s-frx8po6g-1-frx8uqso-3l)] tried to remove lease for client with session ID 4p7222-46h04s-frx8po6g-1-frx8vzo4-4t, but no such lease was found | 12:04:33,890 INFO [BridgeService] Stopped bridge BridgeService | 12:05:16,671 INFO [BridgeService] Started bridge BridgeService. Source: /queue/local_incomingSyncRequests Target: /queue/incomingSyncRequests | Then the messages are transported again View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215214#4215214 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215214 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge error because of network problems also influences
And the last issue that the messages are NOT delivered anymore after the queue has reconnected is also true. Now this happens on C which were never stopped but lost connection while B has restarted. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215185#4215185 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215185 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge error because of network problems also influences
Hi Tim! Sorry... forget my last mail! My fault. One Server was startet 2 times or at least the old output was shown so I thought the serverpeers are the same. BUT THEY DON'T . 4 Servers 4 ServerPeers. Behaviour retested and still happens Have not tested this A SourceListener Issue yet But I definatly see the crahing connections on none related bridges like my first posts. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215164#4215164 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215164 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge error because of network problems also influences
Hi Tim A What a stupid beginner error! Someone else changed the configuration scripts which creates the deployment files and I have not checked it because it worked before. Ok now I can explain most of the errors. I have to retest. Results are postet to this thread sorry for time stealing View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215159#4215159 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215159 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge error because of network problems also influences
I also noticed then that in this case above where the message bridge is reconnected no messages are send anymore. I debugged in the code because I first thought that the BatchTimeChecker was failing. But this works fine. I also see that the message list was empty. Then I created a new message on instance A and checked if the Bridge$SourceListener.onMessage() is called. BUT IT ISN'T! What in hell is the problem :-) >From outside it seems that the Bridge is working but the messages are not >received by the Message Bridge! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215155#4215155 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215155 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge error because of network problems also influences
Some further test: I also tried to kill instance A, so a local instance. Then also C is influenced once. After my 50s retrytime the bridge to C is back again. (no, C is not the problem. It also happes the other way round) After restarting instance A the connection from X to A is reestablished but then it failed 2 time again with messages like the example above. Between the reconnect and disconnect it always took around 3 seconds: | 09:44:41,421 INFO [Bridge] jboss.messaging:name=OutgoingBridge_AEOSA,service=Bridge Succeeded in reconnecting to servers | 09:44:44,437 WARN [Bridge] jboss.messaging:name=OutgoingBridge_AEOSA,service=Bridge Detected failure on connection | javax.jms.JMSException: Failure on underlying remoting connection | at org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:102) | at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:641) | 09:44:44,484 ERROR [ClosedInterceptor] ClosedInterceptor.ClientSessionDelegate[c7-xv1z6xrf-1-k6dr6xrf-d1wvvl-2227p4]: method getXAResource() did not go through, the interceptor is CLOSED | 09:44:44,484 WARN [loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.rollbackxaerror] [com.arjuna.ats.internal.jta.resources.arjunacore.rollbackxaerror] XAResourceRecord.rollback - xa error XAException.XAER_NOTA | 09:44:44,484 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_54] - Top-level abort of action -5601fdfe:82d:49af8f92:ea received TwoPhaseOutcome.FINISH_ERROR from | 09:44:44,484 WARN [loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.rollbackxaerror] [com.arjuna.ats.internal.jta.resources.arjunacore.rollbackxaerror] XAResourceRecord.rollback - xa error XAException.XAER_NOTA | 09:44:44,484 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_54] - Top-level abort of action -5601fdfe:82d:49af8f92:ea received TwoPhaseOutcome.FINISH_ERROR from | 09:44:44,484 WARN [Bridge] jboss.messaging:name=OutgoingBridge_AEOSA,service=Bridge Will retry after a pause of 5 ms | 09:45:34,609 INFO [Bridge] jboss.messaging:name=OutgoingBridge_AEOSA,service=Bridge Succeeded in reconnecting to servers | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215139#4215139 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215139 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Bridge error because of network problems also influences oth
Hi Tim, Hi Howard. Its me again and I a remoting problem. I am using JBM 1.4.2.GA.SP1 with remoting SP11Brew. I have 4 Jboss 4.2.3GA instances A B C X (non clustered) A C and X are running on the same machine (OVSPC186) using different ports (development) B is running on a different one. (NVC1218) On X I have configured 2 Bridges to each other instance where one is sending data to the instance and the other one receives data from the instance. So I have 6 Bridges deployed on X. Bridge QOS level set to 2 means XA. The whole system works fine sending messages around. Now a strange thing happens: I kill the remote instance B or unplug network cable to simulate network errors. Then the expected thing happens. The bridges to B detect the erros and retry in my defined time of 50s. BUT somehow also the other bridges crashing now. I would assume that they are NOT influenced on that B instance problem. When I kill the local instance A or C I never saw this behavior. This is reproduceable and I thing I have noticed that while I have tested the upgrade from 1.4.0.SP3 to 1.4.0.SP3.CP04 ( in production I am using 1.4.0.SP3 ) The stacktraces and output of the logger: Detection of instance B problems | 09:09:43,546 WARN [Bridge] jboss.messaging:name=OutgoingBridge_AeosB,service=Bridge Detected failure on connection | javax.jms.JMSException: Failure on underlying remoting connection | at org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:102) | at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:641) | 09:09:49,515 ERROR [SocketClientInvoker] Got marshalling exception, exiting | java.net.SocketException: Connection reset | at java.net.SocketInputStream.read(SocketInputStream.java:168) | at com.sun.net.ssl.internal.ssl.InputRecord.readFully(InputRecord.java:293) | at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:331) | at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:789) | at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:746) | at com.sun.net.ssl.internal.ssl.AppInputStream.read(AppInputStream.java:75) | at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) | at java.io.BufferedInputStream.read(BufferedInputStream.java:237) | at java.io.FilterInputStream.read(FilterInputStream.java:66) | at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:988) | at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:621) | at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:422) | at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:133) | at org.jboss.remoting.ConnectionValidator.doCheckConnectionWithLease(ConnectionValidator.java:548) | at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:328) | at java.util.TimerThread.mainLoop(Timer.java:512) | at java.util.TimerThread.run(Timer.java:462) | 09:09:49,578 ERROR [SocketClientInvoker] Got marshalling exception, exiting | java.net.SocketException: Connection reset | at java.net.SocketInputStream.read(SocketInputStream.java:168) | at com.sun.net.ssl.internal.ssl.InputRecord.readFully(InputRecord.java:293) | at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:331) | at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:789) | at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:746) | at com.sun.net.ssl.internal.ssl.AppInputStream.read(AppInputStream.java:75) | at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) | at java.io.BufferedInputStream.read(BufferedInputStream.java:237) | at java.io.FilterInputStream.read(FilterInputStream.java:66) | at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:988) | at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:621) | at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:422) | at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:133) | at org.jboss.remoting.LeasePinger.stopPing(LeasePinger.java:93) | at org.jboss.remoting.MicroRemoteClientInvoker.terminateLease(MicroRemoteClientInvoker.java:353) | at org.jboss.remoting.ConnectionValidator$WaitOnConnectionCheckTimerTask.run(ConnectionValidator.java:693)
[jboss-user] [JBoss Messaging] - Re: DetectDuplicates does not work??
typo corrections: Point 2: --> Messages are processed NOW at the target. NOT makes no sense :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206853#4206853 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4206853 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - DetectDuplicates does not work??
Hi! Non clustered environment!! 2 Servers Messaging between them I am using a bridge with a remoteproviderloader. I uses QOS 2 ( transacted mode ) I just upgraded to 1.4.2 GA No I have read in the docs than maybe QOS 1 (dups allowed) with detectduplicates set to true is enough. So I made a test. At the Bridge I added a breakpoint at Bridge.sendBatchNonTransacted(). Then I did (or the Bridge did ) the following steps: 1. the Bridge sends the messages to the target. 2. the target session is commited ---> Messages are processed not at the target 3. NOW I KILL THE SERVER WITH THE BRIDGE ---> means the messages are not acknowledged on the source 4. I restared the server with the bridge 5. Messages are send again which is ok I think 6. BUT NOW the receiving server accepts the messages. I debugged into the code and the JDBCPersistenManager.cacheID detects the duplicate and updates the idcache. BUT nothing more? I thought that detectduplicates means that the duplicate message is dropped on the server if already received once?!? Is this wrong? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206852#4206852 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4206852 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: JBMESSAGING-999 problem in cp04 and 1.4.1GA
As I just saw this is also not fixed/reintroduced in JBM 1.4.1 GA. Can someone reopen this bug? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193668#4193668 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193668 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - JBMESSAGING-999 problem in cp04
Hi folks! As I can see the Bug http://jira.jboss.com/jira/browse/JBMESSAGING-999 is back again in CP04. It was fixed in SP1 but now its back?!? Short summary: If you startup a bridge with a remote jms provider and the network is not there or remote server is not started yet, it does no failover. Reason is line 323/4 of BridgeService which makes a jndi lookup: Destination targetDest = (Destination)icTarget.lookup(targetDestinationLookup); Can this be fixed in cp05? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189734#4189734 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4189734 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge stops working after IOException
Hi Tim! Not yet. How stable is this last version? We have a customer who used our beta software in production. We need to upgrade our software anyway so I plan to upgrade JBM also. Can I use the Version 1.4.0 SP3 CP03 with jboss 4.2.1 GA? I saw in jira that a lot of remoting and bridge stuff was fixed in cp02. Or are these releases for a special server/configuration? Or should I build from svn directly? Which Tag/Branch? thx in advance Markus View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189199#4189199 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4189199 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Bridge stops working after IOException
I have 2 physical servers A and B (jboss 4.2.3 with jbm 1.4.0SP3). Messages are transfered with QOS 2 using a bridge between those servers. Bridge is deployed on A and messages are transfered from B to A. Sometimes it happens that the bridge stops working. I think is has to do with heavy machine load or short network failures. On B I can see the following stacktrace: | 10:38:48,750 ERROR [org.jboss.remoting.transport.socket.SocketClientInvoker] Got marshalling exception, exiting | java.io.IOException: Connection reset by peer: socket write error | at java.net.SocketOutputStream.socketWrite0(Native Method) | at java.net.SocketOutputStream.socketWrite(Unknown Source) | at java.net.SocketOutputStream.write(Unknown Source) | at com.sun.net.ssl.internal.ssl.OutputRecord.writeBuffer(Unknown Source) | at com.sun.net.ssl.internal.ssl.OutputRecord.write(Unknown Source) | at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(Unknown Source) | at com.sun.net.ssl.internal.ssl.AppOutputStream.write(Unknown Source) | at java.io.BufferedOutputStream.flushBuffer(Unknown Source) | at java.io.BufferedOutputStream.flush(Unknown Source) | at java.io.DataOutputStream.flush(Unknown Source) | at org.jboss.jms.wireformat.ClientDelivery.write(ClientDelivery.java:93) | at org.jboss.jms.wireformat.JMSWireFormat.write(JMSWireFormat.java:237) | at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedWrite(MicroSocketClientInvoker.java:945) | at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:586) | at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:418) | at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) | at org.jboss.remoting.Client.invoke(Client.java:1634) | at org.jboss.remoting.Client.invoke(Client.java:548) | at org.jboss.remoting.Client.invokeOneway(Client.java:598) | at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallback(ServerInvokerCallbackHandler.java:826) | at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallbackOneway(ServerInvokerCallbackHandler.java:697) | at org.jboss.jms.server.endpoint.ServerSessionEndpoint.performDelivery(ServerSessionEndpoint.java:1432) | at org.jboss.jms.server.endpoint.ServerSessionEndpoint.handleDelivery(ServerSessionEndpoint.java:1344) | at org.jboss.jms.server.endpoint.ServerConsumerEndpoint.handle(ServerConsumerEndpoint.java:322) | at org.jboss.messaging.core.impl.RoundRobinDistributor.handle(RoundRobinDistributor.java:119) | at org.jboss.messaging.core.impl.MessagingQueue$DistributorWrapper.handle(MessagingQueue.java:582) | at org.jboss.messaging.core.impl.ClusterRoundRobinDistributor.handle(ClusterRoundRobinDistributor.java:79) | at org.jboss.messaging.core.impl.ChannelSupport.deliverInternal(ChannelSupport.java:606) | at org.jboss.messaging.core.impl.MessagingQueue.deliverInternal(MessagingQueue.java:505) | at org.jboss.messaging.core.impl.ChannelSupport$InMemoryCallback.afterCommit(ChannelSupport.java:935) | at org.jboss.messaging.core.impl.tx.Transaction.commit(Transaction.java:228) | at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendTransaction(ServerConnectionEndpoint.java:490) | at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.org$jboss$jms$server$endpoint$advised$ConnectionAdvised$sendTransaction$aop(ConnectionAdvised.java:101) | at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$sendTransaction_N326865078927536.invokeNext(ConnectionAdvised$sendTransaction_N326865078927536.java) | at org.jboss.jms.server.container.SecurityAspect.handleSendTransaction(SecurityAspect.java:195) | at sun.reflect.GeneratedMethodAccessor144.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) | at java.lang.reflect.Method.invoke(Unknown Source) | at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121) | at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$sendTransaction_N326865078927536.invokeNext(ConnectionAdvised$sendTransaction_N326865078927536.java) | at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105) | at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$sendTransaction_N326865078927536.invokeNext(ConnectionAdvised$sendTransaction_N326865078927536.java) | at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.sendTransaction(ConnectionAdvised.java) | at org.jboss.jms.wireformat.ConnectionSendTransactionRequest.serverInvoke(ConnectionSendTransactionRequest.java:82) | at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(
[jboss-user] [JBoss Messaging] - Re: Messages stuck in Queue using the Bridge - Transaction i
Hi! I still have this issue? Any idea? Currently the productive system is not working correct anymore. So the pressure to solve it is big. Greets A desperate programmer View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185921#4185921 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185921 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: View payload and header data in the table
Thx! Does anyone know a configurable web application (war) which can be used to monitor jms queues. I used hermesJMS a bit but I am searching for a web based solution. Thx for hints. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183158#4183158 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183158 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - View payload and header data in the table
Hi out there! I have to debug some data of my jbm application. For that I have to read the data in payload and header column of the jbm_msg table. (from the dlq) Is this possible with sql? Or does those blobs contain serialized/crypted objects? My payload is a TextMessage. Greets. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183128#4183128 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183128 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Profiling with eclipse causes Connection Factory Problem
Hmm. That is possible but I am using not special configurations. I am using the default ganymede eclipse IDE with the provided TPTP profiler. I keep trying but for now I use "yourkid" which works. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169867#4169867 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169867 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Profiling with eclipse causes Connection Factory Problems
I try to profile my Jboss Server. While starting up the start of the ConnectionFactory fails: | 13:06:20,546 INFO [ServerPeer] JBoss Messaging 1.4.0.SP3 server [2] started | 13:06:21,421 ERROR [ExceptionUtil] [EMAIL PROTECTED] startService | java.lang.ExceptionInInitializerError | at org.jboss.jms.server.connectionfactory.ConnectionFactoryJNDIMapper.registerConnectionFactory(ConnectionFactoryJNDIMapper.java:177) | at org.jboss.jms.server.connectionfactory.ConnectionFactory.startService(ConnectionFactory.java:201) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) | at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:597) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:995) | at $Proxy0.start(Unknown Source) | at org.jboss.system.ServiceController.start(ServiceController.java:417) | at org.jboss.system.ServiceController.start(ServiceController.java:435) | at org.jboss.system.ServiceController.start(ServiceController.java:435) | at org.jboss.system.ServiceController.start(ServiceController.java:435) | at org.jboss.system.ServiceController.start(ServiceController.java:435) | at org.jboss.system.ServiceController.start(ServiceController.java:435) | at org.jboss.system.ServiceController.start(ServiceController.java:435) | at org.jboss.system.ServiceController.start(ServiceController.java:435) | at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:597) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy4.start(Unknown Source) | at org.jboss.deployment.SARDeployer.start(SARDeployer.java:304) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:597) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy37.start(Unknown Source) | at org.jboss.deployment.XSLSubDeployer.start(XSLSubDeployer.java:197) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) | at sun.reflect.GeneratedMethodAccessor52.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:597) | at org.jboss
[jboss-user] [JBoss Messaging] - Messages stuck in Queue using the Bridge - Transaction issue
Hi again! JMB 1.4.0.SP3 on Jboss 4.2.3 I have 2 Servers A and B. On B I have 3 Bridges configured which pulls and pushes messages from and to A. If I kill B and restart it or im I break the network connection I have the Problem that some messages are stuck in the Queues on A and B. The Bridge is no longer transport them. Also my ejb3 slsb does not consume the messages. | session = conn.createSession(true, Session.SESSION_TRANSACTED); | consumer = session.createConsumer(m_queue); | Message msg = (Message) consumer.receive(2); | I get log messages like: On B every 2 minutes (where the Bridges are deployed) | 11:13:45,890 WARN [loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] Could not find new XAResource to use for recovering non-serializable XAResource < 131075, 27, 25, 1-a046baa:7f1:489c0041:a420a046baa:7f1:489c0041:a459 | and on A once: | 10:32:38,109 WARN [SimpleConnectionManager] ConnectionManager[16269c] cannot look up remoting session ID a42z4q-bfwpc7-fjmiug2o-1-fjmiv15t-26 | 10:32:38,109 WARN [SimpleConnectionManager] A problem has been detected with the connection to remote client a42z4q-bfwpc7-fjmiug2o-1-fjmiv15t-26, jmsClientID=null. It i | s possible the client has exited without closing its connection(s) or the network has failed. All connection resources corresponding to that client process will now be re | moved. | The Messages in JBM_MSG_REF have state "+" and "-" and there are transactions assigned in transaction_id. Restarting servers has no effect. What happened and how can I solve this? What does this message state mean? Thx. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169532#4169532 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169532 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bug or feature? Modifying the payload and redelivery...
Yes! You are right! That's it. I fixed it via creating a copy of my ObjectMessage Payload. I can remove my fix then if patch is part of next GA or SP release :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162611#4162611 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162611 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Bug or feature? Modifying the payload and redelivery...
Hi! Don't know if this is a bug or feature. I am using a plain consumer (MessageConsumer.receiver(long)) in an transacted session inside a sessionbean. So JTA is used. (1.4.0SP3) I receive my payload and reuse it in my backend. There it fills a List with other objects. Then I rollback my transaction or throw an runtime exception. My database instance increases the delivery_count and the message is received again in a new transaction. I expect a new payload object but no, its the already changed one. Is this a bug or a feature? What says the spec? :-) Greets View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162554#4162554 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162554 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - best practice for JTA based consuming and delegating
Hi all! I am a little confused. I have to receive messages from a local queue and have to delegate this to some business logic (Session Beans) (which persists data in a DB); I have to ensure that the message order is preserved, also in case of rollbacks or exceptions. I also have to ensure that the consuming and the business logic is handles in one transaction. My first idea was to receive messages via a MDB but in case of setRollbackOnly() the MDB container does not retry the same message so order is scrambled. Then I thought to create a Service which starts a plain receiver which uses jmsXA Connectionfactory to create a transacted receive. Message by Message. My question. Does this also starts a JTA transaction where my called Sessionbeans later enlist to? Or must I start a transaction by hand? I am searching for the best practice to receive messages and process them by my ejb3 session and entitybeans in one transaction. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161973#4161973 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161973 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Again Message Order and MDB
Hi again... Yes I know that the spec says nothing about order. But still this behavior is strange. The pool size is set via annotations: @ActivationConfigProperty(propertyName="maxSession", propertyValue="1"), @ActivationConfigProperty(propertyName="maxMessages", propertyValue="1") }) I just wonder why its always twisting with 2 messages instead of 3 or 5 or any higher number. If I can force this to 1 consumer its exacly what my customer need. :-) Greets View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159525#4159525 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159525 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Again Message Order and MDB
Hi! Its mee again. I spend arround 5 hours now digging in JBM code to find out why my system behaves as it does. Testenvironment: - One local persistent Queue with a lot of messages in. - An EJB3 MDB attached to the Queue using maxSession and maxMessages set to 1 - redelivery is set to MDBs default (5 think) - JBM 1.4.0 SP3 on 4.2.1 GA To test Logic errors and the ways JBM handles exceptions I set context.setRollbackOnly() while handling the messages in my MDB onMessage() method. What I thought is this behaviour of Message A B C: A -> fail A -> fail A -> fail A -> fail A -> fail -> DLQ B -> fail B -> fail B -> fail B -> fail B -> fail -> DLQ and so on But what happens is always a handling of 2 messages: A -> fail B -> fail A -> fail B -> fail A -> fail B -> fail A -> fail B -> fail A -> fail -> DLQ B -> fail -> DLQ C -> fail D -> fail C -> fail D -> fail and so on... While debugging and tracing I see that the ClientConsumer calls removeFirst() on the BasicPriorityLinkedList from 2 Threads and in twisting manner the addFirst() and removeFirst() which lead in this A,B,A,B order. What can I do to have this handling? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159467#4159467 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159467 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Redelivery order
Hi szhigunov! I made some tests with the restart of the queues but I can not see it working. Can you quickly tell me what you have done? I did: - At MDB Level I catch exception while handling Message A. - Then I call context.setRollbackOnly() - Then I get the MBeanserver and stop and start my Queue. But next handled message is not the rolled back on (A) . Its another one (B) and the rolled back is handled later. Thx for help! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4158331#4158331 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4158331 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Redelivery order
Hi! Long Time ago I asked the same question. There is a feature request under: http://jira.jboss.com/jira/browse/JBMESSAGING-1151 for this! I have the same problem and my customer wants to put the System life in a month. So I am very interested in solutions ( or feature request implementation ) :-) Greets View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157907#4157907 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157907 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Bridge MaxBatchTime does not work with 1.4.0.SP3
Hi JBM Team! After upgrading from 1.4.0.GA to SP3 i have a problem that some messages stays in the source queue instead of been bridged to the destination. My bridge connects a local queue with a remote queue and uses an selector. The settings: | 2 | | DEST_NODE='AEOS C' | | 5 | | 1000 | I noticed that sometime 1 or 3 messages stays there. They are nor timing out after 1000 ms. If I add again some messages to the source the missing once are sended. I never had this behavior with the older version. Any Ideas? Bug? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4152604#4152604 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4152604 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: FIFO Ordering also if Rollback (Retry)?
Ok! Requested ... http://jira.jboss.com/jira/browse/JBMESSAGING-1151 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104508#4104508 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104508 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: FIFO Ordering also if Rollback (Retry)?
Thx Tim! I saw the Jira entry http://jira.jboss.com/jira/browse/JBAS-2444 about the ordering issu and a Link to Messaging. But anyway. Does your explanaition mean that after a NACK/Transaction Rollback of my single JBM Consumer the Message is put back to the queue and is retried after the set time? Example: Lets assume message A, B and C in the Queue. All with same prio and a single consumer. Retry Interval is set to 20 seconds. Needed behaviour consume A (ok) consume B (NOK/Transaction roll back) consume B again after 20 sec (NOK/Transaction roll back) consume B again after 20 sec (Now processing is OK- Commit) consume C The behaviour with my singleton MDB is currently: consume A (ok) consume B (NOK/Transaction roll back) consume C consume B again after 20 sec (NOK/Transaction roll back) consume B again after 20 sec (Now processing is OK- Commit) Greets Markus View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104422#4104422 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104422 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - FIFO Ordering also if Rollback (Retry)?
Hi again! At our project the order of the messages is important. For that we configured the listener (MDB) as a SingletonMDB (maxMessages and maxSession is set to "1"). But in cases of a (network or handling) failure the message is marked as retry. New messages which arrived in between are processed BEFORE the other message retries. So the order is scrambled. Is it possible to configure a real FIFO also in case of retry? I think the order issue is a common requirement. I only want to stop the queue processing as long as the message can be delivered or I decide via timeToLive or in my code that this message can be dropped. Is this already possible or is this in the pipeline/feature request? Greets Markus Lutum / Germany PS: I do not want to discuss the design of my clients application. Its historical grown. But I want to get rid of all the self implemented Queues with persistent storage and there BUGs :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4103569#4103569 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4103569 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge under load throws IllegalStateException
Good work Tim!! With 3123 I can not reproduce this error It seems that this issue is fixt. COOL and thx!! Markus Lutum View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087079#4087079 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4087079 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge under load throws IllegalStateException
Cool... Yes! I can try it out (hopefully) if this then will help. Just tell me how I can get the fix then... Greets... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4085911#4085911 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4085911 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge under load throws IllegalStateException
Hi Tim! I don't have much time currently to create an easy testcase because of project priorities. So I have to fight fist to get more time on this (with my wife and my Boss :-) ) But meanwhile I have tested the MaxBatchTime -1 setting and shaped the problem a little. Again my setup but now only the relevant parts: - 2 Servers A and B - A should send messages to B. B processes the messages and sometimes send result to A. Technical architecture -A holds a queue Q1 which is bridged to B Bridged_Q1 -On B there is MDB processing the Messages in Bridged_Q1 and send results to Q2. -Results are bridged to A Bridged_Q2 -on A there is a MDB which stores results. So each side holds 2 queues. The bridge for both sides are deployed on A. Testsituation: about 900 Messages are waiting in Q1 When I now hotdeploy my bridge on A it starts the above processing: MaxBatchSize is always set to 2 Result: With maxBatchTime 200 or 300 I have a lot of errors. With 100 it is less!. With -1 there is no Problem anymore... It must have something to do if there are 2 directions with messages or two bridges are active at the same time for the same server. My third Server (which only send messages to A) have no bridging problem. thx again for your effords!! Markus Lutum View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4085878#4085878 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4085878 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge under load throws IllegalStateException
Will test this tomorrow View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4085422#4085422 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4085422 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge under load throws IllegalStateException
Ok! I will try to create a smaller testset. But this will take at least one week because I have to interrupt my project to fix some bugs first... thx! Markus View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083256#4083256 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083256 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge under load throws IllegalStateException
Ah I can reproduce it more often!! Is has to do with the Bridge configuration MaxBatchSize and MaxBatchTime. In my initial setup I set | 5 | | | 1000 | With this setting it fails once each 100 message (approx) I haved changed the values to MaxBatchSize 2 and MaxBatchTime 200 and it seems to happen now each 2-10 message... What do you need to test this on your side or how should I send you a TestCase. What are the testCase guidelines? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083045#4083045 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083045 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge under load throws IllegalStateException
Sorry... forget my last post the move to the MDB has nothing to do with the error and the error is still there. Damm... still trying to find out whats going on View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082894#4082894 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082894 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge under load throws IllegalStateException
My Problem is solved but maybe still some bug in the messaging. My middle server (M) also has an internal Topic. I registered some durable subscribers and because I can not use JmsXA Connectionfactory I used XAConnectionFactory. JmsXA is not possible because then I can not use setClientId() (J2ee Spec). It seems that this is the root of this error. Means using XAConnectionFactory internally with heavy load and all the other configured and described stuff. My workarround: I changed my dynamic subscriber registration via a service to one single MDB which now handles all messages. Performance loss but now it uses JTA via JmsXA and everythink works fine... Greets Markus Lutum View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082853#4082853 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082853 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge under load throws IllegalStateException
Hi again I don't know if this will help, but in those error cases the SessionAspect.handlePreDeliver() called isXAAndConsideredNonTransacted(state) which returns true because the SessionState.sessionListener is null !?! The Comment of isXAAnd sais: http://jira.jboss.org/jira/browse/JBMESSAGING-946 - To accomodate TCK and the MQ behavior we should behave as non transacted, AUTO_ACK when there is no transaction enlisted However when the Session is being used by ASF we should consider the case where we will convert LocalTX to GlobalTransactions. This function helper will ensure the condition that needs to be tested on this aspect Don't know why and what this is all about... Greets Markus View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081662#4081662 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081662 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Bridge under load throws IllegalStateException
Hi again! I have my bridge up and running. 2 servers (A and B) and a middleware server (M). on both servers there are 3 queues. The middlewareserver bridges them to its local queues. I am using QOS 2 (Transacted) Messageflow is like -A send to lokal. -Bridged from A to M -M processing and send processed to lokalQueue(M) -Message bridged from M to B -B processing message and send result to localQueue(B) -Bridged to M -result stored. When I send a lot of messages I receive a stack traces is like: | 14:41:44,250 ERROR [ClientConsumer] Failed to deliver message | java.lang.IllegalStateException: There is already a delivery set for auto ack | at org.jboss.jms.client.state.SessionState.setAutoAckInfo(SessionState.java:371) | at org.jboss.jms.client.container.SessionAspect.handlePreDeliver(SessionAspect.java:258) | at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect18.invoke(SessionAspect18.java) | at org.jboss.jms.client.delegate.ClientSessionDelegate$preDeliver_5548846795541436298.invokeNext(ClientSessionDelegate$preDeliver_5548846795541436298.java) | at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170) | at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) | at org.jboss.jms.client.delegate.ClientSessionDelegate$preDeliver_5548846795541436298.invokeNext(ClientSessionDelegate$preDeliver_5548846795541436298.java) | at org.jboss.jms.client.delegate.ClientSessionDelegate.preDeliver(ClientSessionDelegate.java) | at org.jboss.jms.client.container.ClientConsumer.callOnMessage(ClientConsumer.java:150) | at org.jboss.jms.client.container.ClientConsumer$ListenerRunner.run(ClientConsumer.java:941) | at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89) | at java.lang.Thread.run(Thread.java:619) | Its caused by the Bridge. My breakpoint stops on 3 threads related my 3 queues. One example is listed below: Variables of ClientConsumer.callOnMessage(SessionDelegate, MessageListener, String, String, boolean, MessageProxy, int, int, SessionDelegate, boolean): | sessClientSessionDelegate (id=315) | listenerBridge$SourceListener (id=508) | consumerID "a1-tcoi696f-1-l3lf696f-nkdb51-q4z24a" | queueName "local_incomingSyncRequests" | isConnectionConsumerfalse | m TextMessageProxy (id=507) | ackMode 0 | maxDeliveries 10 | connectionConsumerSession null | shouldAck true | deliveryInfoDeliveryInfo (id=367) | And SessionState Vars: | thisSessionState (id=310) | acknowledgeMode 0 | asfMessages LinkedList (id=395) | autoAckInfo DeliveryInfo (id=399) | callbackHandlersHashMap (id=403) | childrenHashSet (id=408) | clientAckList ArrayList (id=396) | currentTxId MessagingXid (id=419) | delegateClientSessionDelegate (id=315) | dupsOKBatchSize 1000 | executorClearableQueuedExecutor (id=423) | parent ConnectionState (id=425) | recoverCalled false | sessionID "91-3hmi696f-1-l3lf696f-nkdb51-q4z24a" | sessionListener null | transacted true | xa true | xaResource MessagingXAResource (id=445) | infoDeliveryInfo (id=367) | connectionConsumerSession null | consumerId "a1-tcoi696f-1-l3lf696f-nkdb51-q4z24a" | msg TextMessageProxy (id=507) | queueName "local_incomingSyncRequests" | shouldAck true | I have seen some references in the Design forum and version 1.2. Do you have an Idea? Oh forgot: I am using 1.4 cr2 and jboss 4.2.1GA.. Greets Markus Lutum View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081656#4081656 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081656 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: JMS Bridge Question
Hmmm. Strange things happen. I followed the 2 Hints and added the / and changed the provider from localhost to my local fixed IP address... ( yes, both servers are currently on one machine (for development)). And surprise... It works... So I am happy again! The interesting part is while finding out if the ip or the / or both must be set I can NOT reproduce it. With all settings it works now. Anyway... thx for reading and support View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081569#4081569 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081569 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: JMS Bridge Question
I solved my security issues by alter my securitydomain java:/jaas/messaging. Now on both sides the role guest has all rights. I added user and password for the bridges target and source and again The error previously noted is back again. To answer your question: I tried CR2 and it still gives me the same error! :-( View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080887#4080887 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080887 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: JMS Bridge Question
I did... I updated source and destination to 1.4 CR2. Now this error is gone but there is a new one. Maybe only a different log? Anyway... here is the log: | 11:21:22,640 ERROR [ResourceManager] org.jboss.jms.exception.MessagingXAException: A security exception happend! | org.jboss.jms.exception.MessagingXAException: A security exception happend! | at org.jboss.jms.tx.ResourceManager.sendTransactionXA(ResourceManager.java:641) | at org.jboss.jms.tx.ResourceManager.commit(ResourceManager.java:370) | at org.jboss.jms.tx.MessagingXAResource.commit(MessagingXAResource.java:238) | at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelOnePhaseCommit(XAResourceRecord.java:636) | at com.arjuna.ats.arjuna.coordinator.BasicAction.onePhaseCommit(BasicAction.java:2619) | at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1779) | at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:88) | at com.arjuna.ats.arjuna.AtomicAction.end(AtomicAction.java:216) | at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commit(TransactionImple.java:238) | at org.jboss.jms.server.bridge.Bridge.sendBatch(Bridge.java:1238) | at org.jboss.jms.server.bridge.Bridge.access$1700(Bridge.java:62) | at org.jboss.jms.server.bridge.Bridge$BatchTimeChecker.run(Bridge.java:1489) | at java.lang.Thread.run(Thread.java:619) | Caused by: javax.jms.JMSSecurityException: User: null is not authorized to write to destination incomingSyncRequests | at org.jboss.jms.server.container.SecurityAspect.check(SecurityAspect.java:312) | at org.jboss.jms.server.container.SecurityAspect.handleSendTransaction(SecurityAspect.java:190) | at sun.reflect.GeneratedMethodAccessor150.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:597) | at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121) | at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$sendTransaction_N326865078927536.invokeNext(ConnectionAdvised$sendTransaction_N326865078927536.java) | at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105) | at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$sendTransaction_N326865078927536.invokeNext(ConnectionAdvised$sendTransaction_N326865078927536.java) | at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.sendTransaction(ConnectionAdvised.java) | at org.jboss.jms.wireformat.ConnectionSendTransactionRequest.serverInvoke(ConnectionSendTransactionRequest.java:82) | at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:144) | at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:734) | at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:560) | at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:383) | at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:165) | at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163) | at org.jboss.remoting.Client.invoke(Client.java:1550) | at org.jboss.remoting.Client.invoke(Client.java:530) | at org.jboss.remoting.Client.invoke(Client.java:518) | at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:186) | at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:157) | at org.jboss.jms.client.delegate.ClientConnectionDelegate.org$jboss$jms$client$delegate$ClientConnectionDelegate$sendTransaction$aop(ClientConnectionDelegate.java:221) | at org.jboss.jms.client.delegate.ClientConnectionDelegate$sendTransaction_N326865078927536.invokeNext(ClientConnectionDelegate$sendTransaction_N326865078927536.java) | at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:91) | at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) | at org.jboss.jms.client.delegate.ClientConnectionDelegate$sendTransaction_N326865078927536.invokeNext(ClientConnectionDelegate$sendTransaction_N326865078927536.java) | at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170) | at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) | at org.jboss.jms.client.delegate.ClientConnectionDelegate$sendTransaction_N326865078927536.invokeNext(ClientConnectionDelegate$s
[jboss-user] [JBoss Messaging] - Re: JMS Bridge Question
Hi Tim! I think I have the same issue. I am using 2 instances of jboss 4.2.1GA with messaging 1.3 The source is a remote server (on my local machine). | | RemoteJMSProvider_A | org.jboss.jms.jndi.JNDIProviderAdapter | | XAConnectionFactory | | XAConnectionFactory | | XAConnectionFactory | | java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory | java.naming.factory.url.pkgs=org.jnp.interfaces | java.naming.provider.url=localhost:2099 | | | As you can see I am not using "java:" but the error is the same. My error only occurs if I am using "QOS_ONCE_AND_ONLY_ONCE". Settings to 1 works. On the source I get: | 14:04:59,328 ERROR [ExceptionUtil] ConnectionEndpoint[76] sendTransaction [a42z4q-jbavvr-f5z5x8i7-1-f5z7mkao-3l] | javax.jms.JMSException: Failed to route Reference[8]:RELIABLE to incomingSyncRequests | at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendMessage(ServerConnectionEndpoint.java:694) | at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.processTransaction(ServerConnectionEndpoint.java:786) | at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendTransaction(ServerConnectionEndpoint.java:456) | at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.org$jboss$jms$server$endpoint$advised$ConnectionAdvised$sendTransaction$aop(ConnectionAdvised.java:101) | at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$sendTransaction_N326865078927536.invokeNext(ConnectionAdvised$sendTransaction_N326865078927536.java) | at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105) | at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$sendTransaction_N326865078927536.invokeNext(ConnectionAdvised$sendTransaction_N326865078927536.java) | at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.sendTransaction(ConnectionAdvised.java) | at org.jboss.jms.wireformat.ConnectionSendTransactionRequest.serverInvoke(ConnectionSendTransactionRequest.java:82) | at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:141) | at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:734) | at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:560) | at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:383) | at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:165) | On my destination (where bridging is installed) I get: | 14:04:59,328 WARN [Bridge] Failed to send + acknowledge batch, closing JMS objects | javax.transaction.RollbackException: [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] Can't commit because the transaction is in aborted state | at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commit(TransactionImple.java:253) | at org.jboss.jms.server.bridge.Bridge.sendBatch(Bridge.java:1221) | at org.jboss.jms.server.bridge.Bridge.access$1600(Bridge.java:59) | at org.jboss.jms.server.bridge.Bridge$BatchTimeChecker.run(Bridge.java:1336) | at java.lang.Thread.run(Thread.java:619) | 14:04:59,359 ERROR [ClosedInterceptor] ClosedInterceptor.ClientSessionDelegate[77]: method getXAResource() did not go through, the interceptor is CLOSED | 14:04:59,359 WARN [Bridge] Will retry after a pause of 5 ms | Any Ideas? If there is already a known problem... Is there a Jira Bug filed? THX a lot! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079581#4079581 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079581 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Persistence, JBoss/CMP, Hibernate, Database] - thin driver ojdbc14.jar, Java 6 (1.6) and -Xss
Hi out there! We are using Jboss 4.x with Oracle 9 and 10. Because in the Java 5 there are some Bugs/Issues with Threads we are forced to upgrade to Java 6. We are using plain J2EE with EJB 2.0 and mostly 1.1 With Java 6 and MSSQL all works but not with Oracle. We we found the Error... It has to Do with the VM Parameter -Xss (Setting Stack Size) At JBoss we are using the Thin Driver and the newest ojdbc14.jar Configutation DS: AeosDS jdbc:oracle:thin:@NVC0534:1521:test oracle.jdbc.driver.OracleDriver 0 50 MyDatabaseRealm Oracle9i When we now start the Server without the -Xss setting all is OK. When I start up the Server with -Xss64k I get a NoClassDefFoundError ??? Stacktrace: 09:14:16,765 INFO [DbManager] Trying to get connection from datasource with name= java:/AeosDS 09:14:16,906 WARN [JBossManagedConnectionPool] Throwable while attempting to get a new connection: null java.lang.NoClassDefFoundError: oracle/jdbc/driver/OracleCallableStatement at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:169) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:568) at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFacto ry.java:151) at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnect ionPool.java:508) at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:207 ) at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java: 534) at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:396) at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:299) at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:448) at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionMan ager2.java:838) at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:102) at com.nedap.aeos.ejbutil.DbManager.getConnectionOnce(DbManager.java:174) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) ... Why the Driver change his behaviour dependend on the Xss setting? Is there a Bug on Jboss side? I Also posted this in the Oracle Tech Channel. With an older Version like the classes12.jar it works!! Greets Markus Lutum View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002151#4002151 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002151 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Messaging, JMS & JBossMQ] - Re: MDB and connection to a remote queue with transaction
"genman" wrote : BTW, if you close the connection it closes the session and
sender as well.
I know :-)
"genman" wrote :
| Anyway, what does getConnection() do? Are you using the pooled connections
at java:/JmsXA ?
It gets the connection and start it from the connectionfactory (of the remote
server) and because it is remote it looks for XAConnectionfactory.
The code:
private Connection getConnection() throws JMSException {
|
| Connection connection = null;
| try {
| connection = cf.createConnection();
| connection.start();
|
| } catch (JMSException e) {
| if (connection != null)
| try {
| connection.close();
| } catch (Exception ignore) {
| }
| throw e;
| }
| return connection;
| }
And during ejb create the remote jndi lookup for the connectionfactory is done:
public void ejbCreate() {
| try {
| //remote jndi properties like port and url
| Properties prop = IMConstants.getIMServerProperties();
|
| Context ic = new InitialContext(prop);
|
| cf = (ConnectionFactory)
ic.lookup("XAConnectionFactory");
| sendQueue = (Queue)
ic.lookup(IMConstants.QUEUE_INCOMINGSYNCREQUESTS);
| ic.close();
| } catch (Exception e) {
| throw new EJBException("Failure to get connection
factory or queue: "
| + e.getMessage(),e);
| }
| }
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997183#3997183
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997183
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Messaging, JMS & JBossMQ] - MDB and connection to a remote queue with transaction
Like
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=91589
I have the same or equal problem.
I have 2 JBoss Servers(A and B). Both 4.0.5 with Messaging 1.0.1 GA
On A I have an MDB listen on a local queue
inside the onmessage it should get the message and send a Result to a Queue on
Server B.
Inside my MDB on A I create a connection using B´s JNDI and look for
XAConnectionFactory.
I open the session like this:
session = conn.createSession(true, Session.AUTO_ACKNOWLEDGE);
But after the onMessage returns the Message is still not in the DB on B.
If I do it like
session = conn.createSession(false, Session.AUTO_ACKNOWLEDGE);
it works.
It works also, if I use TRUE and commit the session explicitly with
session.comit(); But if then an exception on A occurs I have the Message still
in A and already in B.
Question:
How can I span my JTA Transaction of Server A to include the send to B?
Now some config stuff follows:
My MDB Config:
| SyncRequestSenderMDB
| com.XXX.send.SyncRequestSenderMDB
| Container
|
|javax.jms.Queue
|
|
|
|
|
|
| SyncRequestSenderMDB
| *
|
| Required
|
|
My remote send call:
| Connection conn = null;
| MessageProducer sender = null;
| try {
|
| conn = getConnection();
| boolean transacted = true;
| session = conn
| .createSession(transacted,
Session.AUTO_ACKNOWLEDGE);
|
| sender = session.createProducer(sendQueue);
|
| TextMessage tm =
session.createTextMessage(syncMessage.getMessageAsString());
|
| sender.send(tm);
| Logger.debug(this, "Message sent to IM Server");
| // with this it will be send
| // session.commit();
|
| } catch (JMSException e) {
| throw new RuntimeException(
| "Problems sending Sync Message to IM Server
Queue.", e);
| } finally {
| if (sender != null)
| try {
| sender.close();
| } catch (Exception ignore) {
| }
| if (session != null)
| try {
| session.close();
| } catch (Exception ignore) {
| }
| if (conn != null)
| try {
| conn.close();
| } catch (Exception ignore) {
| }
| }
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995038#3995038
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995038
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: JmsXA vs XAConnectionfactory and durable topic subscript
"timfox" wrote : BTW, any reason why you're not just using MDBs? Hmm Yes! As I said I have a Topic where messages comes in. These must be processed and send to a queue for each connected system. I don't want so hardcode his so it must be self maintaining. My Idea: Have a service which starts or stops durable subscribers on a topic based on registered servers... The Order is relevant so I can only have one instance per connected Server. Any small hints how I can handle this with MDB? I would prefer this way because of DLQ handling and transactions... In the end I need a scaleable system which consumes messages from a topic and send the processed data (different for each server) to connected servers/outgoing queue (which register themself). One Idea is to have an MDB which handles the message for all servers, but this is not that scaleable, because the order is relevant so I only can have one MDB instance... "[EMAIL PROTECTED]" wrote : False Thx for this hint but I try be be spec compliant... /MDB consuming messages View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994137#3994137 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994137 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - JmsXA vs XAConnectionfactory and durable topic subscription
Hi out there!
I have problems using jmsxa on a durable topic subscription.
I am using:
JBoss 4.0.5
JBoss Messaging 1.0.1 GA
JBoss EJB3 RC9
What I need:
Inside the Container I have a Topic where messages comes in.
Via a EJB3 Service Pojo I instantiate Objects with its own thread which
register themselves as listener via createDurableSubscriber.
These Handlers get a message, process them somehow and put the result in an
outgoing queue on the same server.
In other words. I want to dynamically register topic listeners. There is one
Listener for each remote attached server which reads its data from that
outgoing queue.
The attached Servers are stored in a database so I can read the DB and create
as many subscribers as I need.
All works fine with
ic.lookup("java:/XAConnectionFactory");
But I what to use the Container Transaction to be sure everything is rolled
back if something went wrong from the topic to the queue. I mean, the storing
to the queue must be rolled back and the receiving from the queue should be
retried.
So I changed it to
ic.lookup("java:/JmsXA");
But with JmsXA I receive an error when I try to set the client ID like:
| ERROR [NodeBasedRemoteSynchronizer] Failed to create connection and session
| javax.jms.IllegalStateException: This method is not applicable inside the
application server. See the J2EE spec, e.g. J2EE1.4 Section 6.6
| at
org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.setClientID(JmsSessionFactoryImpl.java:201)
| at
com.X.NodeBasedRemoteSynchronizer.run(NodeBasedRemoteSynchronizer.java:130)
removing the set clientID method results in an other error:
Failed to create connection and session
| javax.jms.JMSException: Cannot create durable subscriber without a valid
client ID
| at
org.jboss.jms.server.endpoint.ServerSessionEndpoint.createConsumerDelegate(ServerSessionEndpoint.java:179)
| at
org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$createConsumerDelegate$aop(SessionAdvised.java:90)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
| at
org.jboss.jms.server.container.SecurityAspect.handleCreateConsumerDelegate(SecurityAspect.java:116)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at
org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:130)
| at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at
org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105)
| at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.aop.Advisor.dynamicInvoke(Advisor.java:723)
| at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:101)
| at
org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:127)
| at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:1008)
| at
org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:98)
| at org.jboss.remoting.Client.invoke(Client.java:589)
| at org.jboss.remoting.Client.invoke(Client.java:581)
| at
org.jboss.jms.client.delegate.DelegateSupport.invoke(DelegateSupport.java:111)
| at
org.jboss.jms.client.delegate.ClientSessionDelegate$createConsumerDelegate_6311124154581125663.invokeNext(ClientSessionDelegate$createConsumerDelegate_6311124154581125663.java)
| at
org.jboss.jms.client.container.StateCreationAspect.handleCreateConsumerDelegate(StateCreationAspect.java:122)
| at
org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect20.invoke(StateCreationAspect20.java)
| at
org.jboss.jms.client.delegate.ClientSessionDelegate$createConsumerDelegate_6311124154581125663.invokeNext(ClientSessionDelegate$createConsumerDelegate_6311124154581125663.java)
| at
org.jboss.jms.client.container.ConsumerAspect.handleCreateConsumerDelegate(ConsumerAspect.java:69)
| at
org.jboss.aop.advice.org.jboss.jms.client.container.ConsumerAspect19.invoke(ConsumerAspect19.java)
| at
org.jboss.jms.client.delegate.ClientSessionDelegate$createConsumerDelegate_6311124154581125663.invokeNext(ClientSessionDelegate$createConsumerDelegate_6311124154581125663.java)
| at
org.jboss.jms.client.container.ClosedIntercep
[jboss-user] [Messaging, JMS & JBossMQ] - Re: JBossMQ message persistence with SQLServer (Urgent help)
Is there a solution for this? I have the same Problems with JBoss Messaging and SQLSERVER View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988837#3988837 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988837 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: MSSQL 2000 Problem with DLQ at startup.
regarding problem 1 I changes the sql call to UPDATE_UNRELIABLE_CHANNELCOUNT=UPDATE JMS_MESSAGE SET CHANNELCOUNT = CHANNELCOUNT - 1 WHERE MESSAGEID IN (SELECT MR.MESSAGEID FROM JMS_MESSAGE_REFERENCE MR WHERE MR.RELIABLE = 'N' AND MR.CHANNELID = ?) | Still open is the DLQ problem View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3975990#3975990 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3975990 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - MSSQL 2000 Problem with DLQ at startup.
Hi out there! I am trying to use MSSQL Server 2000 with the Messaging RC5. I also use the persistence file mssql-persistence-service.xml. I have two problems: First the configuration: UPDATE_UNRELIABLE_CHANNELCOUNT=UPDATE JMS_MESSAGE M SET M.CHANNELCOUNT = M.CHANNELCOUNT - 1 WHERE M.MESSAGEID IN (SELECT MR.MESSAGEID FROM JMS_MESSAGE_REFERENCE MR WHERE MR.RELIABLE = 'N' AND MR.CHANNELID = ?) is invalid. When I put this in the query browser it reports an SQL Syntax error. I commented it out and the server startet! Second problem: Every time, when I have data in my DLQ and start the Server it reports: 2006-10-04 12:12:27,562 DEBUG [org.jboss.messaging.core.plugin.JDBCPersistenceManager] Resetting message data. This may take several minutes for large queues/subscriptions... | 2006-10-04 12:12:27,562 DEBUG [org.jboss.messaging.core.plugin.JDBCPersistenceManager] Updating all reliable references to not loaded | 2006-10-04 12:12:27,593 ERROR [org.jboss.jms.server.plugin.JDBCChannelMapper] Failed to load queue state | java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet can not re-read row data for column 7. | at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source) | at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source) | at com.microsoft.jdbc.base.BaseResultSet.validateColumnIndex(Unknown Source) | at com.microsoft.jdbc.base.BaseResultSet.getBinaryStream(Unknown Source) | at org.jboss.resource.adapter.jdbc.WrappedResultSet.getBinaryStream(WrappedResultSet.java:339) | at org.jboss.messaging.core.plugin.JDBCPersistenceManager.getBytes(JDBCPersistenceManager.java:4223) | Looking at microsoft they say: (see http://support.microsoft.com/kb/824106/en-us ) SYMPTOMS | You have a Java application that uses JDBC to retrieve a ResultSet object by using the Microsoft SQL Server 2000 Driver for JDBC. When you try to read a column in the ResultSet, you may receive the following error message: | | java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet can not re-read row data for column 1. | Note In this error message, the words "can not" are a misspelling for the word "cannot." | | The column number that the error message refers to is dependent on the schema of your ResultSet object. | Back to the top | | CAUSE | This error occurs with ResultSet objects that contain a BLOB column (for example, text, ntext, or image data types). The driver cannot return a BLOB column out of order because it does not cache all the content of BLOB data types because of size limitations. | | For any row in the ResultSet, you can read any column from left to right, and each column should be read only one time. If you try to read columns out of order, or if you re-read a column from the ResultSet, you may receive the error message that the "Symptoms" section describes. | | STATUS | This behavior is by design. So, where is the error? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3975981#3975981 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3975981 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
