JUDDI Lookups Causing OOM Errors
colsona Jan 29, 2007 12:01 PMI am getting a new problem where the ESB fails to deploy my listeners due to an out of memory problem or registyry unavailable problem. It appears the registry is in a circular lookup loop causing it to lookup the registry 30 -40 times at server startup just to deploy two message listeners. My ESB configuration is below:
<?xml version = "1.0" encoding = "UTF-8"?> <jbossesb parameterReloadSecs="60" xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.0.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <providers> <provider name="TestFile"> <bus busid="test-file"/> </provider> <fs-provider name="ProcessFile"> <fs-bus busid="proc-file"/> </fs-provider> </providers> <services> <service is-gateway="true" name="FileListeningService" description="Service that listens for files coming in" category="FileEvent" target-service-category="FileEvent" target-service-name="FileProcessingService" service-class="com.spss.esb.ESBSpecificFilePoller"> <listeners> <listener busidref="test-file" maxThreads="1" name="testFileListener" > <property name="fileLocation" value="C:\\FileTest\\testfile"></property> <property name="poll-frequency-seconds" value="10"></property> </listener> </listeners> </service> <service is-gateway="false" name="FileProcessingService" description="Service that queues files for processing" category="FileEvent" > <listeners> <fs-listener busidref="proc-file" maxThreads="1" name="FileProcessListener"> <fs-message-filter directory="c:\\FileTest\" input-suffix="-ready" error-directory="c:\\FileTest\\inError" post-delete="false" post-directory="c:\\FileTest\\processed" /> </fs-listener> </listeners> <actions> <action name="CreateFileMessage" class="com.spss.esb.CreateFileMessage" process="receivedFile"/> </actions> </service> </services> </jbossesb>
Here is sample server log. This block of log message is rep[eated over and over again at server startup.
2007-01-29 10:55:52,006 INFO [org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl] Service name: FileEventProcessing:FileProcessingService 2007-01-29 10:55:52,006 INFO [org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl] Description: null 2007-01-29 10:55:52,006 INFO [org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl] Key id: 894530E0-AB2E-11DB-B9ED-E96072EB4716 2007-01-29 10:55:52,006 ERROR [org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl] Found 3 Services, while expecting only one by the name of FileProcessingService in category FileEvent 2007-01-29 10:55:52,084 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@258c74, cl=org.jboss.mx.loading.HeirarchicalLoaderRepository3$CacheClassLoader@f7ba93{ url=null ,addedOrder=0} 2007-01-29 10:55:52,193 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@258c74, cl=org.jboss.mx.loading.HeirarchicalLoaderRepository3$CacheClassLoader@1b88599{ url=null ,addedOrder=0} 2007-01-29 10:55:52,271 INFO [STDOUT] BindingTemplate=<xml-fragment serviceKey="894530E0-AB2E-11DB-B9ED-E96072EB4716" xmlns="urn:uddi-org:api_v2"><description/> <accessPoint URLType="other">%3C%3Fxml+version%3D%221.0%22+encoding%3D%22UTF-8%22%3F%3E%0A%3Cwsa%3AFrom%3E%0A++++%3Cwsa%3AAddress%3Efile%3A%2Fc%3A%2FFileTest%2F%3C%2Fwsa%3AAddress%3E%0A++++%3Cwsa%3AReferenceProperties%3E%0A++++++++%3Cwsarjaddr%3AinputSuffix+xmlns%3Awsarjaddr%3D%22http%3A%2F%2Fschemas.arjuna.com%2Fws%2F2004%2F06%2Fwsarjaddr%22%3E-ready%3C%2Fwsarjaddr%3AinputSuffix%3E%0A++++++++%3Cwsarjaddr%3AerrorDelete+xmlns%3Awsarjaddr%3D%22http%3A%2F%2Fschemas.arjuna.com%2Fws%2F2004%2F06%2Fwsarjaddr%22%3Etrue%3C%2Fwsarjaddr%3AerrorDelete%3E%0A++++++++%3Cwsarjaddr%3AerrorDir+xmlns%3Awsarjaddr%3D%22http%3A%2F%2Fschemas.arjuna.com%2Fws%2F2004%2F06%2Fwsarjaddr%22%3E%2Fc%3A%2FFileTest%2F%3C%2Fwsarjaddr%3AerrorDir%3E%0A++++++++%3Cwsarjaddr%3AerrorSuffix+xmlns%3Awsarjaddr%3D%22http%3A%2F%2Fschemas.arjuna.com%2Fws%2F2004%2F06%2Fwsarjaddr%22%3E.esbERROR%3C%2Fwsarjaddr%3AerrorSuffix%3E%0A++++++++%3Cwsarjaddr%3ApostDelete+xmlns%3Awsarjaddr%3D%22http%3A%2F%2Fschemas.arjuna.com%2Fws%2F2004%2F06%2Fwsarjaddr%22%3Efalse%3C%2Fwsarjaddr%3ApostDelete%3E%0A++++++++%3Cwsarjaddr%3ApostDir+xmlns%3Awsarjaddr%3D%22http%3A%2F%2Fschemas.arjuna.com%2Fws%2F2004%2F06%2Fwsarjaddr%22%3Ec%3A%5C%5CFileTest%5C%5Cprocessed%3C%2Fwsarjaddr%3ApostDir%3E%0A++++++++%3Cwsarjaddr%3ApostSuffix+xmlns%3Awsarjaddr%3D%22http%3A%2F%2Fschemas.arjuna.com%2Fws%2F2004%2F06%2Fwsarjaddr%22%3E.esbDone%3C%2Fwsarjaddr%3ApostSuffix%3E%0A++++++++%3Cwsarjaddr%3Atype+xmlns%3Awsarjaddr%3D%22http%3A%2F%2Fschemas.arjuna.com%2Fws%2F2004%2F06%2Fwsarjaddr%22%3Eurn%3Ajboss%3Aesb%3Aepr%3Atype%3Afile%3C%2Fwsarjaddr%3Atype%3E%0A++++%3C%2Fwsa%3AReferenceProperties%3E%0A%3C%2Fwsa%3AFrom%3E%0A</accessPoint> </xml-fragment> 2007-01-29 10:55:52,287 INFO [org.apache.ws.scout.transport.LocalTransport] Calling org.apache.juddi.registry.local.PublishService#publish locally 2007-01-29 10:55:52,287 INFO [org.apache.juddi.registry.local.Registry] Loading jUDDI configuration. 2007-01-29 10:55:52,303 INFO [org.apache.juddi.registry.local.Registry] Resources loaded from: C:\jboss-4.0.5.GA-Golden\server\default\conf/juddi.properties 2007-01-29 10:55:52,303 INFO [org.apache.juddi.registry.local.Registry] Initializing jUDDI components. 2007-01-29 10:55:52,303 INFO [org.apache.juddi.util.Loader] Using the Context ClassLoader 2007-01-29 10:55:52,318 INFO [org.apache.juddi.util.Loader] Using the Context ClassLoader 2007-01-29 10:55:52,318 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@258c74, cl=org.jboss.mx.loading.HeirarchicalLoaderRepository3$CacheClassLoader@19d142f{ url=null ,addedOrder=0} 2007-01-29 10:55:52,459 INFO [org.apache.juddi.datastore.jdbc.JDBCDataStore] Generated token 'authToken:3228F9E0-AFB1-11DB-A3B8-A3694CB31F04' for user: 'jbossesb/JBoss ESB User' 2007-01-29 10:55:52,475 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@258c74, cl=org.jboss.mx.loading.HeirarchicalLoaderRepository3$CacheClassLoader@a488b9{ url=null ,addedOrder=0} 2007-01-29 10:55:52,521 INFO [org.apache.ws.scout.transport.LocalTransport] Calling org.apache.juddi.registry.local.PublishService#publish locally 2007-01-29 10:55:52,521 INFO [org.apache.juddi.registry.local.Registry] Loading jUDDI configuration. 2007-01-29 10:55:52,521 INFO [org.apache.juddi.registry.local.Registry] Resources loaded from: C:\jboss-4.0.5.GA-Golden\server\default\conf/juddi.properties 2007-01-29 10:55:52,521 INFO [org.apache.juddi.registry.local.Registry] Initializing jUDDI components. 2007-01-29 10:55:52,600 INFO [org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl] javax.xml.registry.infomodel.ServiceBinding successfully saved 2007-01-29 10:55:52,600 INFO [org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl] Saved Key=324A6490-AFB1-11DB-A3B8-9CFE37AB8BEF 2007-01-29 10:55:52,615 DEBUG [org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl] Going to query the registry for name pattern [FileEvent, FileProcessingService] 2007-01-29 10:55:52,615 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@258c74, cl=org.jboss.mx.loading.HeirarchicalLoaderRepository3$CacheClassLoader@133d68a{ url=null ,addedOrder=0} 2007-01-29 10:55:52,615 INFO [org.apache.ws.scout.transport.LocalTransport] Calling org.apache.juddi.registry.local.InquiryService#inquire locally 2007-01-29 10:55:52,631 INFO [org.apache.juddi.registry.local.Registry] Loading jUDDI configuration. 2007-01-29 10:55:52,631 INFO [org.apache.juddi.registry.local.Registry] Resources loaded from: C:\jboss-4.0.5.GA-Golden\server\default\conf/juddi.properties 2007-01-29 10:55:52,631 INFO [org.apache.juddi.registry.local.Registry] Initializing jUDDI components.
Is there something in my configuration causing this redundancy. It seemed to work for a week without problem and these issues turned up and got worse.
Asa