[JBoss Messaging] - Re: JBoss Messaging RA configuration
by ataylor
No i wanted to implement a JBoss messaging client talking to a JBM clustered server without installing a Jboss Messaging implementation on the server (just throwing jboss-messaging.jar in the lib dir).
JBM must be installed and configured on the server.
But I solved this part using remote JNDI lookup on the cluster. What is not mentioned in the documentation is that you need in fact also libs from the cluster configuration (the all configuration) in a non clustered JBoss Appserver (the message producer). At least jbossha.jar.
| Perhaps it was a bad idea to do this with JCA.
I'm still a little unclear as to what you are doing here. Are you looking up the connection factory, if this is the case then JBM must be installed.
But how can i configure the remote queue as administered object just like the examples on JBoss ActiveMQ and JBoss WebsphereMQ examples.
Can you direct me at these examples and maybe i'll be able to grasp exactly what you are trying to achieve.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129429#4129429
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4129429
18 years, 2 months
[JBoss jBPM] - simple question
by mryilauer
I understand jdpl, know how to create, unit test, deploy, and debug a process.
I created a process with a timer in it that works.
Now, all I want to do is create a class that gets a process instance from that same db that that console sees (public), starts it up in the engine, so that I can see my printlns in the console when the timer goes off every 30 seconds.
What must I do to the cfg files so that when I get the jbpmContext and use it to get a process, I am getting it from the right db schema and starting it up in the right server?
It seems all I can manage to do is pull back the graph and walk it in my code, but not launch it in the server.
Obviously, my code is running in the eclipse Jbpm jvm and the server is running in its own jvm, so it seems I am missing something obvious and fundamental like, how to connect to the server using webservices.
Any help without excessively nasty rtfm comments would be appreciated since I keep rtfm and yet still manage to stay in the dark on this simple, essential issue.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129425#4129425
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4129425
18 years, 2 months
[Messaging, JMS & JBossMQ] - DLQConfig isn't considered while Deployment
by hlins
Hi @all.
I want to use a special dlq for my application. Therefor according to the JBoss wiki I used the
jboss.xml
| <jboss>
| <enterprise-beans>
| <message-driven>
| <ejb-name<OrderQueueMDB</ejb-name>
| <destination-jndi-name>queue/OrderQueue</destination-jndi-name>
| <mdb-user>order</mdb-user>
| <mdb-passwd>nerdy</mdb-passwd>
| <configuration-name>OrderQueueMDBConfig</configuration-name </message-driven>
| </enterprise-beans>
|
| <invoker-proxy-bindings>
| <invoker-proxy-binding>
| <name>order-message-driven-bean</name>
| <invoker-mbean>default</invoker-mbean>
| <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
| <proxy-factory-config>
| <JMSProviderAdapterJNDI>DefaultJMSProvider</JMSProviderAdapterJNDI>
| <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
| <MaximumSize>1</MaximumSize>
| <MaxMessages>1</MaxMessages>
| <MDBConfig>
| <ReconnectIntervalSec>10</ReconnectIntervalSec>
| <DLQConfig>
| <DestinationQueue>queue/OrderDLQ</DestinationQueue>
| <MaxTimesRedelivered>10</MaxTimesRedelivered>
| <TimeToLive>0</TimeToLive>
| <DLQUser>order</DLQUser>
| <DLQPassword>nerdy</DLQPassword>
| </DLQConfig>
| </MDBConfig>
| </proxy-factory-config>
| </invoker-proxy-binding>
| </invoker-proxy-bindings>
|
| <container-configurations>
| <container-configuration extends="Standard Message Driven Bean">
| <container-name>OrderQueueMDBConfig</container-name>
| <invoker-proxy-binding-name>order-message-driven-bean</invoker-proxy-binding-name>
| <container-interceptors>
| <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor>
| <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor>
| <interceptor>org.jboss.ejb.plugins.RunAsSecurityInterceptor</interceptor>
| <!-- CMT -->
| <interceptor transaction="Container">org.jboss.ejb.plugins.TxInterceptorCMT</interceptor>
| <interceptor transaction="Container">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
| <interceptor transaction="Container">org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor</interceptor>
| <!-- BMT -->
| <interceptor transaction="Bean">org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor</interceptor>
| <interceptor transaction="Bean">org.jboss.ejb.plugins.MessageDrivenTxInterceptorBMT</interceptor>
| <interceptor transaction="Bean">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
| <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor>
| </container-interceptors>
| <instance-pool>org.jboss.ejb.plugins.MessageDrivenInstancePool</instance-pool>
| <instance-cache></instance-cache>
| <persistence-manager></persistence-manager>
| </container-configuration>
| </container-configurations>
| </jboss>
|
and the ejb-jar.xml
| <message-driven>
|
| <description>Receiver for DslOrder Queue messages</description>
|
| <ejb-name>DslOrderQueueMDB</ejb-name>
|
| <ejb-class>de.schlund.j2ee.tools.genericmdb.GenericMDB</ejb-class>
| <messaging-type>javax.jms.MessageListener</messaging-type>
| <transaction-type>Container</transaction-type>
|
| <message-destination-type>javax.jms.Queue</message-destination-type>
| <activation-config>
| <activation-config-property>
| <activation-config-property-name>destinationType</activation-config-property-name>
| <activation-config-property-value>javax.jms.Queue</activation-config-property-value>
| </activation-config-property>
| </activation-config>
| </message-driven>
|
But during deployment the following error occurs:
ERROR [org.jboss.resource.adapter.jms.inflow.JmsActivation] Unable to reconnect org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@60c384(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter(a)136b8d7 destination=queue/OrderQueue isTopic=false tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=order pass=<not shown> maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler
DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5)
javax.jms.JMSSecurityException: User: null is NOT authenticated
at org.jboss.mq.security.SecurityManager.authenticate(SecurityManager.java:230)
at org.jboss.mq.security.ServerSecurityInterceptor.authenticate(ServerSecurityInterceptor.java:66)
at org.jboss.mq.server.TracingInterceptor.authenticate(TracingInterceptor.java:613)
at org.jboss.mq.server.JMSServerInvoker.authenticate(JMSServerInvoker.java:172)
at org.jboss.mq.il.jvm.JVMServerIL.authenticate(JVMServerIL.java:165)
at org.jboss.mq.Connection.authenticate(Connection.java:1067)
at org.jboss.mq.Connection.(Connection.java:252)
at org.jboss.mq.Connection.(Connection.java:323)
at org.jboss.mq.SpyConnection.(SpyConnection.java:116)
at org.jboss.mq.SpyConnectionFactory.internalCreateConnection(SpyConnectionFactory.java:137)
at org.jboss.mq.SpyConnectionFactory.createQueueConnection(SpyConnectionFactory.java:108)
at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setupDLQConnection(AbstractDLQHandler.java:137)
at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setup(AbstractDLQHandler.java:83)
at org.jboss.resource.adapter.jms.inflow.dlq.JBossMQDLQHandler.setup(JBossMQDLQHandler.java:48)
at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDLQ(JmsActivation.java:369)
at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:315)
at org.jboss.resource.adapter.jms.inflow.JmsActivation.handleFailure(JmsActivation.java:259)
at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:639)
at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:756)
at java.lang.Thread.run(Thread.java:619)
As far as i see, the dlq config wasn't used. (see the highlighted text in the error message!)
I've any idea, where to search the error. Maybe it's an issue of the EJB Deployer.
I've used nearly the same config with EJB 2.1 and no errors.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129424#4129424
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4129424
18 years, 2 months
[JBossCache] - Concurrency issue in OrderedSynchronizationHandler (2.0.0GA
by fungrim
Hi,
Two issues/questions regarding OrderedSynchronizationHandler.
1) The "instances" member is not synchronized
OrderedSynchronizationHandler seems to have an unguarded static HashMap member called "instances". This is a potentional crash issue. On one of our instances (in a four member cluster) with medium high load (aprox 1500 transaction per second), the CPU flat-lined on 200% with 21 threads caught and spinning in HashMap.get(Object) as called from OrderedSynchronizationHandler.getInstance(Transaction). I'll copy a typical stack trace below.
2) The "instances" member is static
This is more of a question. If several caches are run within the same VM/ClassLoader they will all share the "instances" member. This seems fairly inefficient, especially if the map in question needs to be synchronized as per #1.
Below is a typical, slightly trunctated, stack trace for issue #1.
"Incoming Thread,TableSpace,172.16.0.2:8786" daemon prio=1 tid=0x097e9208 nid=0x14de runnable [0x83228000..0x83229030]
| at java.util.HashMap.get(HashMap.java:346)
| at org.jboss.cache.interceptors.OrderedSynchronizationHandler.getInstance(OrderedSynchronizationHandler.java:50)
| at org.jboss.cache.interceptors.TxInterceptor.registerHandler(TxInterceptor.java:901)
| at org.jboss.cache.interceptors.TxInterceptor.handleRemotePrepare(TxInterceptor.java:246)
| at org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java:100)
| at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
| at org.jboss.cache.interceptors.CacheMgmtInterceptor.invoke(CacheMgmtInterceptor.java:123)
| at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
| at org.jboss.cache.interceptors.InvocationContextInterceptor.invoke(InvocationContextInterceptor.java:62)
| at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
| at com.cubeia.space.cache.HaltableInterceptor.invoke(HaltableInterceptor.java:32)
| at org.jboss.cache.CacheImpl.invokeMethod(CacheImpl.java:3939)
| at org.jboss.cache.CacheImpl._replicate(CacheImpl.java:2853)
|
What say you?
/Lars J. Nilsson
Cubeia Ltd, UK Fillial
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129420#4129420
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4129420
18 years, 2 months
[JBoss Messaging] - Re: Messaging Cluster scenarios
by ataylor
My question related to this:
| - Would I need the shared DB even if I use these clustered post-offices to host non-persistent (non-durable) subscriptions, that is, is it used to manage the cluster information as well?
| - Is it OK to use HSQLDB or Derby if the above is not true?
You need to use a shared database for clustering, HSQLDB is not usable for a clustered configuration.
2. Recovery from a cluster restart
| Since Jboss messaging relies on a clustered ConnectionFactory registered in a clustered JNDI to provide the failover mechanism, would the client need to re-lookup JNDI and reopen connections and sessions to get back in business?
No, this will all be handled transparently by the client.
Please let me know if posting this via JBoss Network subscription will help me in getting the answers.
yes, we're just having a busy week. :)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129419#4129419
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4129419
18 years, 2 months