Hi everyone, Since version v6.05.03 we have a problem with our monitor application.
There have been changes on hippo side, see for more info: https://issues.onehippo.com/browse/CMSSIX-123?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel#issue-tabs [Add necessary configurations and modifications to ease building a war for J2EE application containers. The changes are for Hippo revisions #10980 till #10984 and #10988] Hippo made it easier to create a Hippo 6 war, but this conflicted with our configuration. So we have reduced our own configuration, using Hippo's config instead. Nevertheless we did not succeed in making our monitoring application behave like before.... Now we get the following error on our monitoring part of the application: JMS Topic Status: NOTICE Started: 28-01-2011 12:44:29, Completed: 28-01-2011 12:44:29, State:NOT OK, Description: javax.naming.NameNotFoundException : TCPTopicConnectionFactory By changing our jboss-web.xml to not containing the resource-ref for TCPTopicConnectionFactory gives the following exception while deploying: javax.naming.NamingException: resource-ref: TCPTopicConnectionFactory has no valid JNDI binding. Check the jboss-web/resource-ref Here are some of our changed files, which cause named problems: ========================================== file:///D:/projects/hippo/cms-customized/build.properties.sample ========================================== jms.jndi.initial.factory=nl.hippo.jmsbridge.BridgeContextFactory jms.connection.factory=TCPTopicConnectionFactory ========================================== file:///D:/projects/hippo/cms-customized/config/jboss-web.xml ========================================== <resource-ref> <res-ref-name>TCPTopicConnectionFactory</res-ref-name> <jndi-name>java:x.tcf</jndi-name> </resource-ref> ========================================== file:///D:/projects/hippo/cms-customized/config/resources.xweb ========================================== We removed this resource-ref on our side, because this is now delivered by hippo <resource-ref> <description>JMS Connection Factory</description> <res-ref-name>TCPTopicConnectionFactory</res-ref-name> <res-type>javax.jms.TopicConnectionFactory</res-type> <res-auth>Container</res-auth> </resource-ref> ========================================== activemq-jms-ds.xml ========================================== <tx-connection-factory> <jndi-name>x.tcf</jndi-name> <xa-transaction/> <track-connection-by-tx/> <connection-definition>javax.jms.TopicConnectionFactory</connection-definition> <rar-name>activemq-ra.rar</rar-name> <ServerUrl>failover:tcp://jmsbrokerhost:13083?trace=false&keepAlive=true&connectionTimeout=0</ServerUrl> <min-pool-size>1</min-pool-size> <max-pool-size>200</max-pool-size> <blocking-timeout-millis>30000</blocking-timeout-millis> <idle-timeout-minutes>3</idle-timeout-minutes> </tx-connection-factory> What are we doing wrong? Regards, Gerrie Rijsdijk Met vriendelijke groet, Gerrie Rijsdijk ANWB P&I/Business Applicatie Management/Online 088-2698135 ********************************************************************************************** Disclaimer E-mail wordt door ANWB niet gebruikt voor het aangaan van externe verplichtingen. Deze e-mail is uitsluitend bestemd voor geadresseerde(n). Indien deze e-mail onverhoopt niet voor u is bestemd dan verzoeken wij u vriendelijk contact op te nemen met de afzender en daarna het bericht te vernietigen. Deze e-mail mag niet worden doorgestuurd, openbaar gemaakt of verveelvoudigd worden zonder de toestemming van de afzender. ANWB betracht grote zorgvuldigheid bij het verzenden van e-mails. ANWB kan echter niet garanderen dat deze e-mail juist, volledig, tijdig en virusvrij wordt overgebracht. In een dergelijk geval is ANWB op geen enkele wijze aansprakelijk voor enige schade, direct dan wel indirect, in welke vorm dan ook. ANWB B.V. ********************************************************************************************** ******************************************** Hippocms-dev: Hippo CMS 6 development public mailinglist Searchable archives can be found at: MarkMail: http://hippocms-dev.markmail.org Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
