[JBoss Messaging] - Re: Bridge - Foreign Message (ActiveMQ -> JbossMessaging)
by aslak
| <connection-factories>
|
| <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
| name="jboss.mq:service=JMSProviderLoader,name=ActiveMQJMSProvider">
| <attribute name="ProviderName">ActiveMQJMSProvider</attribute>
| <attribute name="ProviderAdapterClass">
| org.jboss.jms.jndi.JNDIProviderAdapter
| </attribute>
| <!-- The combined connection factory -->
| <attribute name="FactoryRef">ConnectionFactory</attribute>
| <!-- The queue connection factory -->
| <attribute name="QueueFactoryRef">ConnectionFactory</attribute>
| <!-- The topic factory -->
| <attribute name="TopicFactoryRef">ConnectionFactory</attribute>
| <attribute name="Properties">
| java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory
| java.naming.provider.url=tcp://xx.xx.xx.xx:61616
| queue.inbound=OM.from
| queue.outbound=OM.to
| </attribute>
|
| </mbean>
| </connection-factories>
|
|
| <mbean code="org.jboss.jms.server.bridge.BridgeService"
| name="com.nordpool:service=Bridge,name=BridgeFromOM"
| xmbean-dd="xmdesc/Bridge-xmbean.xml">
|
| <attribute name="SourceProviderLoader">jboss.mq:service=JMSProviderLoader,name=ActiveMQJMSProvider</attribute>
|
| <attribute name="TargetProviderLoader">jboss.messaging:service=JMSProviderLoader,name=JMSProvider</attribute>
|
| <attribute name="SourceDestinationLookup">inbound</attribute>
|
| <attribute name="TargetDestinationLookup">topic/npmq.in</attribute>
|
| <attribute name="SourceUsername">xx</attribute>
|
| <attribute name="SourcePassword">xx</attribute>
|
| <attribute name="TargetUsername">xx/attribute>
|
| <attribute name="TargetPassword">xx</attribute>
|
| <attribute name="QualityOfServiceMode">0</attribute>
|
| <attribute name="Selector"></attribute>
|
| <attribute name="MaxBatchSize">1</attribute>
|
| <attribute name="MaxBatchTime">1</attribute>
|
| <attribute name="SubName"></attribute>
|
| <attribute name="ClientID"></attribute>
|
| <attribute name="FailureRetryInterval">1000</attribute>
|
| <attribute name="MaxRetries">2</attribute>
|
| </mbean>
|
Messaging Bridge:
source -> ActiveMQ queue via ActiveMQJMSProvider configured to talk to the ActiveMQServer
target -> JbossTopic on JbossMessaging
1. The bridges source consumer receives a ActiveMQMessage from the ActiveMQProvider
2. The bridge tries to send the message to the target JbossProducer.
3. The JbossProducer figures out it is a foreign message and converts the message to a JbossMessage. The JbossProducers target JbossDestination is lost in the translation. (to be correct, the ActiveMQDestination is set on the JbossMessage and the ServerConnection failes casting it.)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4072507#4072507
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4072507
18Â years, 9Â months
[Installation, Configuration & DEPLOYMENT] - OutOfMemoryError on Windows
by scauwe
Hi all,
jboss: 4.0.5.GA
Windows 2000
Java: 1.4.2_06
I have a java application running inside jboss. It needs to process a big XML file (it contains +10000 'records'; 1 record = about 30 nodes).
I keep on getting an OutOfMemoryError while looping over the records.
If i print out the total memory and free memory, I can see that the free memory is going down, but is still more then enough.
I start the appserver with 1 gig (-Xms1024m -Xmx1024m) on a 2 gig machine.
I output the memory every 250 records:
| Record #:0
| Total:1061814272
| Free:954701144
| Record #:250
| Total:1061814272
| Free:951648552
| Record #:500
| Total:1061814272
| Free:949005224
| Record #:750
| Total:1061814272
| Free:944648768
| Record #:1000
| Total:1061814272
| Free:944296160
| Record #:1250
| Total:1061814272
| Free:941645368
| Record #:1500
| Total:1061814272
| Free:938858208
| Record #:1750
| Total:1061814272
| Free:936897856
| Record #:2000
| Total:1061814272
| Free:934571512
| Record #:2250
| Total:1061814272
| Free:931946416
| Record #:2500
| Total:1061814272
| Free:929656872
| Record #:2750
| Total:1061814272
| Free:926362056
| Record #:3000
| Total:1061814272
| Free:922550760
| java.lang.OutOfMemoryError
|
So, it seems that it is not a memory issue. What else can cause an OutOfMemory on Windows? I know about the native thread issue on Linux, but I never heard of that on Windows.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4072505#4072505
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4072505
18Â years, 9Â months
[Messaging, JMS & JBossMQ] - Re: JMSSecurityException when trying to subscribe to a tempo
by hicks
You really are a helpful person aren't you?
In practice, most of us don't live and breathe JBoss, as you obviously do. It's one of many technologies we use in the course of our jobs. With the tight time schedules of most software projects, we can't usually afford the luxury of becoming intimately familiar with every product we come into contact with. Bearing that in mind, I asked a simple question which an obvious 'God' of JBoss like yourself could answer in an instant without too much thought. I asked the question to avoid spending a lot of time poring over the documentation. I searched the forum and found no answer to my question, so I asked.
And as for doing my research, this forum is itself a resource. I just hoped to find a quick answer to help me solve a problem and save some time. Sorry if I was mistaken and caused offense.
Speaking of time, I've already wasted more than I should here.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4072503#4072503
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4072503
18Â years, 9Â months
[Persistence, JBoss/CMP, Hibernate, Database] - BatchedTooManyRowsAffectedException: SqlServer trigger
by whafrog
Hi, I'm having a problem with a legacy app that uses SQLServer 2000 that we're converting to EJB3. One of the tables has a trigger on it to record audit changes. However, the way the trigger and the audit repository work is, it creates a new record for each changed field in the target table. Two fields are always updated (last update time, and user) so changing even one field causes hibernate to think three records were updated instead of the expected one record.
I get the following exception:
org.hibernate.jdbc.BatchedTooManyRowsAffectedException: Batch update returned unexpected row count from update [0]; actual row count: 3; expected: 1
I think the hibernate engine is using @@rowcount to get the number of updated rows, but the trigger messes this up.
The database folks aren't much interested in changing their auditing practice :-( so I'm wondering if there's a way to change the hibernate configuration to deal with this.
Any suggestions? TIA,
Jon
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4072501#4072501
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4072501
18Â years, 9Â months