|
History
| Log In
|
|
|
|
Thanks a lot, James.
I'm not familiar with maven usage and I'm getting an error I don't know the cause of: Downloading: http://ibiblio.org/maven2//directory-shared/ldap-common/0.9.1/ldap- Project ID: directory-shared:ldap-common Reason: Error getting POM for 'directory-shared:ldap-common' from the repository Thanks. I've updated my local svn copy this morning, and have seen that the ldap-common version have been bumped up to 0.9.2. But now, I'm running into a different problem:
... Missing: Try downloading the file manually from the project website. Then, install it using the command: Path to dependency: ---------- for artifact: from the specified remote repositories: I tried to follow the intructions into the error, downloaded a version of plexus-archiver and got this new error: C:\src\activemq\trunk>mvn install:install-file -DgroupId=org.codehaus.plexus -Da Project ID: org.apache.activemq:activemq-core [0] 'dependencies.dependency.version' is missing for org.apache.activemq:activemq-jaas Reason: Failed to validate POM [INFO] ------------------------------------------------------------------------ at org.codehaus.classworlds.Launcher.main(Launcher.java:375) At this stage, I don't know if this error is produced by a wrong setup of maven (I just followed the instructions in the ActiveMQ website (running maven 2.0.4)) or is something related with activemq itself. Any hint? Thanks. I've avoided the previous problem launching 'mvn install:install-file ...' outside of the activemq directory. This way I reached compiling activemq-core, but it failed with this error:
Downloading: http://repo1.maven.org/maven2/ant/ant/1.6.2/ant-1.6.2.jar at org.codehaus.classworlds.Launcher.main(Launcher.java:375) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) It seems that JmsConnector.java is one of the modified files for the fix we're on. Anyway, I don't know what that qdox.parser is expecting to find, the java code looks fine to me, and making a diff against the previous svn version of the file at that point is only finding some cosmetic changes. Waiting for help. Previous error was produced by bug: https://issues.apache.org/activemq/browse/AMQ-901
Checking todays svn trunk version finished with a successful compilation. However, reconnection seems not to work. The scenario is as follows: ===Scenario #1===
===Scenario #2===
Furthermore, after restarting the activeMQ broker with non delivered messages in the bridged queue, can lead to lose those messages. Regards This patch fixes what appears to be a bug in the origional fix. I have not yet been able to test it, as I have not yet setup a system to reproduce the problem, but can someone try it out?
Thanks. I have come across this issue in an attempt to use the JMS to JMS bridge in version 4.1.1.
I am trying to bridge ActiveMQ to Websphere MQ and I am running the bridge in its own process and everything connects and works properly. The remote Websphere MQ broker is being shutdown every night for backups and when this occurs the bridge does not see the disconnect of the remote broker. I performed a netstat of the socket connections to see if the bridge was still attempting a connection and found that the socket connections to the remote broker are in a CLOSE_WAIT state. If you have any ideas or wish to try a test I am willing to do what every is needed to resolve this issue. Thanks, William I'm currently trying out a similar issue bridging ActiveMQ to Sun CAPS, but is struggling.
Could you share some light and tell me how you hav configured the "#REMOTE" element in the XML-file. br It was a little tricked, perhaps caused by my ignorance, but I didn't find a suitable way to directly create a bean for the sunmq broker, as broker hostname and port are configured using a common method: setProperty.
So, I had to write a simple wrapper to adapt it to have standard setters. like this: package es.tid.planb.spci.sunmq; import com.sun.messaging.ConnectionFactory; public class ConnectionFactoryBean extends com.sun.messaging.QueueConnectionFactory public void setBrokerHostName( String hostname ) public void setBrokerHostPort( String port ) public String getBrokerHostName() public String getBrokerHostPort() } And then, use it in a bean like this: <bean id="REMOTE" Regards. Alf,
Here is the bridge settings that I am using for Websphere MQ. <jmsQueueConnector name="bridge-test-request" <jmsQueueConnector name="bridge-test-response" <bean id="remoteFactory" I hope this helps. Thx, Thanks, that really helped me a lot!
I was now able to create a simple wrapper similar to yours and managed finally to make i all work. public class connectionFactoryWrapper extends com.stc.jms.client.STCQueueConnectionFactory { public connectionFactoryWrapper() throws JMSException { super("localhost", 18007); }.... Then the bridging works only one way, namely from AMQ to JCAPS. ERROR DestinationBridge - failed to forward message on attempt: 1 reason: java.lang.ClassCastException: org.apache.activemq.command.ActiveMQQueue message: com.stc.jms.message.STCTextMessage@1e22632 The problem seems to be the STCTextMessage class, is it possible to handle this in some way? Regards I think you don't need to wrap STCQueueConnectionFactory, as it provides a constructor with the required arguments, and spring is able to handle that directly. That is not the case for imq, that doesn't have such a constructor neither the required setters. It should be enough for you to use:
<bean id="REMOTE" About the error you get, it seems you're trying to handle directly a STC message implementation using AMQ. That's not the right way. The bridge should automatically convert incoming messages to the AMQ native types. You shouldn't need to use directly the STC nor AMQ Message classes, just ask for java.jmx.Message or javax.jms.TextMessage to your consumers. The AMQ broker will redirect incoming messages from the bridged foreign broker to your | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bug
Open
Major
JMS to JMS Bridge never reconnects under remote broker restarts.
Grab the latest code here...
http://incubator.apache.org/activemq/source.html
then build it...
http://incubator.apache.org/activemq/building.html