-
1. Re: max Number of Services reached !
hauch Mar 10, 2009 8:13 AM (in response to andreas.h)Hi Andreas,
Default is 20.
You can change this in jbossesb.sar/jbossesb.properties.xml:<property name="org.jboss.soa.esb.jms.connectionPool" value="20"/>
-
2. Re: max Number of Services reached !
tfennelly Mar 10, 2009 8:34 AM (in response to andreas.h)Andreas... are you seeing any errors in your server.log? The jms.connectionPool setting is specific to JMS. Sounds like this is a more general issue, right?
-
3. Re: max Number of Services reached !
andreas.h Mar 11, 2009 5:38 AM (in response to andreas.h)3-11 10:35:36,574 INFO [org.quartz.core.QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
2009-03-11 10:35:37,158 INFO [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)] Started in 1m:38s:562ms
2009-03-11 10:36:53,917 INFO [org.jboss.soa.esb.client.ServiceInvoker] Unresponsive EPR: JMSEpr [ PortReference < <wsa:Address jms://chzgws19.int.belleriveconsulting.com:1099/queue/esbchannel/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : chzgws19.int.belleriveconsulting.com:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties
Thanks for the replies
This is the output i got
jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] for message: header: [ To: JMSEpr [ PortReference < <wsa:Address jms://chzgws19.int.belleriveconsulting.com:1099/queue/esbchannel/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : chzgws19.int.belleriveconsulting.com:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] ] -
4. Re: max Number of Services reached !
andreas.h Mar 11, 2009 5:55 AM (in response to andreas.h)
IT is S.O.L.V.E.D !!
Thanks guys for the help, the increasing of the connection pool did the job
I'll send a Toblerone ( Swiss Chocolat )
Cheers from Switzerland