Don't worry, I have the angle covered. I adjusted JMSProviderLoader so that
you can configure where in JNDI to get it's connetion factories from. So
now you configure the MBean with something like:
<mbean code="org.jboss.jms.jndi.JMSProviderLoader"
name=":service=JMSProviderLoader,name=JBossMQProvider">
<attribute name="ProviderName">DefaultJMSProvider</attribute>
<attribute name="ProviderAdapterClass">
org.jboss.jms.jndi.JBossMQProvider
</attribute>
<attribute name="QueueFactoryRef">
java:/INVMXAQueueConnectionFactory
</attribute>
<attribute name="TopicFactoryRef">
java:/INVMXATopicConnectionFactory
</attribute>
</mbean>
Which means you could access a remote JBossMQ server by adjusting the
config.
>From: Peter Antman <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: [EMAIL PROTECTED]
>CC: [EMAIL PROTECTED]
>Subject: Re: [JBoss-dev] JMS thread usage
>Date: Sun, 24 Jun 2001 23:10:28 +0200 (CEST)
>
>On Fri, 22 Jun 2001, Hiram Chirino wrote:
>
> > Well, there's nothing like being embarsed to get my lazy but workin.
> >
> > I've allready commited some several changes that should reduce the
>number of
> > thread being wasted by JBossMQ. The change will have eliminated all the
>38
> > threads here:
> > --> 38: org.jbossmq.SpyConnection$1.run(SpyConnection.java:99)
> >
> > It should also significantly reduce the number of threads at :
> > --> 122: org.jbossmq.Mutex.waitLock
> >
> > And I have a feeling that I just took care of these too. There is a new
> > "INVM" IL (invocation layer) that get stored in JNDI using the
> > NonSerializable factory. If the ASF stuff is configured to use the
> > connection factorys of the INVM IL, no extra threads will be generated.
> > --> 39:
> >
>org.jbossmq.distributed.server.DistributedJMSServerOIL.run(DistributedJMSSer
> > verOIL.java:89
> > --> 38:
> >
>org.jbossmq.distributed.server.ConnectionReceiverOIL.run(ConnectionReceiverO
> > IL.java:110)
> >
> > The changes have been commited to the JBossMQ module.. I start working
>on
> > integrating with the the rest of the jboss modules so we can test to see
>If
> > what I did really did help.
>
>Hiram, you have not broken against the possibility to use MDB in a
>distributed fashion, have you? I know it would be great if ASF could work
>without socket overhead when runing in the same VM, but remember - you may
>today actually have your MDB listening on destinations in a nother server.
>
>
>//Peter
> > > Regards, > Hiram
> >
> >
> > ----- Original Message -----
> > From: "danch" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Thursday, June 21, 2001 10:57 PM
> > Subject: Re: [JBoss-dev] JMS thread usage
> >
> >
> > > Chris' nightly test runs have only been failing with these OutOfMemory
> > > exceptions for the last couple of nights. Either it was a recent
>change
> > > that caused this or a recently added test that brought it into the
>open
> > >
> > > -danch
> > >
> > > Hiram Chirino wrote:
> > >
> > > > I'm embarased.
> > > >
> > > > I'll look into it right away. Since the JMS client and server stuff
>is
> > > > running in the same VM when using ASF I should be able to get rid of
>the
> > > > socket calls and thus free up the threads that are polling the
>sockets.
> > > >
> > > > I'll also see if I can get rid of the SpySession Threads when using
>the
> > > > ASF..
> > > >
> > > > Regards,
> > > > Hiram
> > > > ----- Original Message -----
> > > > From: "Scott M Stark" <[EMAIL PROTECTED]>
> > > > To: "JBoss Dev" <[EMAIL PROTECTED]>
> > > > Sent: Thursday, June 21, 2001 8:04 PM
> > > > Subject: [JBoss-dev] JMS thread usage
> > > >
> > > >
> > > >
> > > >> I have been running the jbosstest suite off and on throughout the
>day
> > > >
> > > > against
> > > >
> > > >> a snapshot of main on linux to look into the issue people have
>reported
> > > >
> > > > concerning
> > > >
> > > >> running out of processes on linux. I am seeing a steady increase in
> > > >
> > > > threads from
> > > >
> > > >> 32 for the baseline just after startup to 229 after one interation
>of
> > the
> > > >
> > > > test suite to
> > > >
> > > >> 329 after about 10 iterations of the test suite.
> > > >>
> > > >> Clearly were leaking threads and it could be that the test code is
>not
> > > >
> > > > cleaning up
> > > >
> > > >> correctly, but I am seeing a large portion of the threads
>associated
> > with
> > > >
> > > > JMS and I
> > > >
> > > >> question why this should be. Out of the 329 threads there are 266
>JMS
> > > >
> > > > associated
> > > >
> > > >> threads.
> > >
> > >
> > > _______________________________________________
> > > Jboss-development mailing list
> > > [EMAIL PROTECTED]
> > > http://lists.sourceforge.net/lists/listinfo/jboss-development
> > >
> >
> > _______________________________________________
> > Jboss-development mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/jboss-development
> >
>
>Jobba hos oss: http://www.tim.se/weblab
>------------------------------------------------------------
>Peter Antman Technology in Media, Box 34105 100 26 Stockholm
>Systems Architect WWW: http://www.tim.se
>Email: [EMAIL PROTECTED] WWW: http://www.backsource.org
>Phone: +46-(0)8-506 381 11 Mobile: 070-675 3942
>------------------------------------------------------------
>
>
>_______________________________________________
>Jboss-development mailing list
>[EMAIL PROTECTED]
>http://lists.sourceforge.net/lists/listinfo/jboss-development
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
