[JBoss Messaging] - Unable to create remote JMS Provider
by dimar1975
Hi all,
I'm trying to set up the JBM Bridge between two servers.
On one machine I have added the remote Provider which point to another JMS Server:
<mbean code="org.jboss.jms.jndi.JMSProviderLoader"
| name="jboss.messaging:service=JMSProviderLoader,
| name=MyRemoteJMSProvider">
| <attribute name="ProviderName">RemoteXAConnectionFactory</attribute>
| <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
|
| <attribute name="FactoryRef">XAConnectionFactory</attribute>
|
| <attribute name="QueueFactoryRef">XAConnectionFactory</attribute>
|
| <attribute name="TopicFactoryRef">XAConnectionFactory</attribute>
|
| <attribute name="Properties">java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
| java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
| java.naming.provider.url=10.2.20.246:1099
| </attribute>
| </mbean>
Then I have added the bridge configuration file :
<mbean code="org.jboss.jms.server.bridge.BridgeService"
| name="jboss.messaging:service=Bridge,name=TestBridge"
| xmbean-dd="xmdesc/Bridge-xmbean.xml">
| <depends optional-attribute-name="SourceProviderLoader">
| jboss.messaging:service=JMSProviderLoader,name=JMSProvider</depends>
| <depends optional-attribute-name="TargetProviderLoader">
| jboss.messaging:service=JMSProviderLoader,name=MyRemoteJMSProvider</depends>
| <attribute name="SourceDestinationLookup">/queue/exampleQueue1</attribute>
| <attribute name="TargetDestinationLookup">/queue/exampleQueue2</attribute>
| <attribute name="MaxBatchSize">5</attribute>
| <attribute name="MaxBatchTime">-1</attribute>
|
|
| </mbean>
however, as soon as I copy these files in the deploy folder the following error is issued:
17:37:47,803 WARN [HDScanner] Failed to process changes
| org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
|
| *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}
|
| jboss.messaging:name=TestBridge,service=Bridge
| -> jboss.messaging:name=MyRemoteJMSProvider,service=JMSProviderLoader{Create:**
| NOT FOUND Depends on 'jboss.messaging:name=MyRemoteJMSProvider,service=JMSProviderLoader' **}
|
|
| *** CONTEXTS IN ERROR: Name -> Error
|
| jboss.messaging:name=MyRemoteJMSProvider,service=JMSProviderLoader -> ** NOT FOUND Depends on 'jboss.messaging:name=MyRemoteJMSProvider,service=JMSProviderLoade
| r' **
It seems that MyRemoteJMSProvider is not found, however from the JMX console I can see that it it actually deployed......
I'm running JBoss 5.0.0 GA, is there any issue with this release ?
thanks
marco
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4229091#4229091
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4229091
17 years, 2 months
[Performance Tuning] - Re: Out of memory errors
by PeterJ
This error: "java.lang.OutOfMemoryError: unable to create new native thread" usually means that the operating system has run out of memory with which to allocate the necessary memory for a new thread. Assuming you are running a 32-bit OS or a 32-bit JVM, There are several possibilities for this.
One possibility is the OS has run out of room in its memory area (usually the upper 1GB or 2GB address space of the application). I have seen this happen is, of example, I boot Windows with the /3GB option - this options leaves only 1GB for Windows memory area which is often not sufficient to hold the handles that Windows uses to manage threads.
Another possibility is that there is insufficient memory in the app's memory area to allocate the memory required for the new thread. Depending on you OS, each thread could require 1MB or memory (and it looks like you have it set for 1MB). Considering that you are allocating a total of 1.5GB memory to the heap and permgen, that leaves not that much extra room for many threads.
So you have a few options:
a) Reduce the memory allocated to each thread. Try using -Xss768k or even -Xss512k. Usually the lowest possible value without getting a stack overflow is what you want.
b) Decrease the heap size. For example, given your current thread stack memory size, setting -Xmx=1200m would allow 80 more threads to be allocated.
c) Reduce the maximum number of threads that can be allocated. This involves both the worker threads declared in jboss-service.xml and the htttp (and related) threads declared in the server.xml file. Though this option is not always guaranteed to be effective because there are other locations where threads are created that are not governed by these limits. For example, I'm not sure where, or if, there is a limit on RMI threads, which I think is the type of thread that could not be created.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4229082#4229082
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4229082
17 years, 2 months