Hi everyone,
Looking again at the changed sources
https://issues.onehippo.com/browse/CMSSIX-123?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel#issue-tabs
I now also see following has been changed in /editor/project.xml:
Revision 10979 Revision 10980
<dependency> <dependency>
<id>hippo:jmsbridge</id> <id>hippo:jmsbridge</id>
<version>1.01.02</version> <version>1.01.04</version>
<properties> <properties>
<cocoon.bundle>false</cocoon.bundle>
<war.bundle>true</war.bundle> <war.bundle>true</war.bundle>
</properties> </properties>
</dependency> </dependency>
Now when I change this back to using version jmsbridge-1.01.02.jar my problem
is gone???
I don't understand why this is causing the problem nor how I can solve this?
Is there a special reason why we cannot use jmsbridge-1.01.02.jar anymore or
can we continue using this one if we prefer that?
And if so, what is the right way to override this and making sure we use
jmsbridge-1.01.02.jar instead of the newer one?
Kind regards,
Gerrie Rijsdijk
Met vriendelijke groet,
Gerrie Rijsdijk
ANWB P&I/Business Applicatie Management/Online
088-2698135
>>> Bartosz Oudekerk <[email protected]> 01-02-2011 11:09 >>>
On 31/01/11 09:46, Gerrie Rijsdijk wrote:
> 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
>
> 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
More than just these two are needed, see [0]
> ==========================================
> 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>
Perhaps try with java:comp/env
> What are we doing wrong?
That's hard to say without trying a local reproduction, if the above
suggestions don't work, please try building a war of our vanilla CMS,
using our documentation[0], see if that one will run in your setup. If
so you can compare the configuration to your customised one.
[0]
https://wiki.onehippo.com/display/CMS/Deployment+on+J2EE+Application+Containers
Kind regards,
--
Bartosz Oudekerk
.---------------------------------.---------------------------------.
| Hippo B.V. | Hippo USA Inc. |
| Oosteinde 11 | 755 Baywood Drive, 2nd floor |
| 1017 WT Amsterdam | Petaluma, CA. 94954 |
| The Netherlands | United States of America |
| Tel +31 (0)20 5224466 | +1 (877) 414 4776 |
+---------------------------------+---------------------------------+
| [email protected] | http://www.onehippo.com |
`---------------------------------^---------------------------------'
********************************************
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
**********************************************************************************************
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
