[jboss-jira] [JBoss JIRA] Commented: (JBAS-6991) Still issue in 5.1.0.GA <database>-persistence-service.xml is dependent on ChannelFactory even on NonClustered

[Andreas Schreiber (JIRA)]

    [ https://jira.jboss.org/browse/JBAS-6991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12537606#action_12537606 ] 

Andreas Schreiber commented on JBAS-6991:
-----------------------------------------

In the JBoss Forum Tim Fox wrote:
"If clustered is set to false, then none of the cluster related attributes should be parsed - that is the way it used to work.
I believe Clebert added ChannelFactory at a later date. If ChannelFactory is being parsed when clustered = false then that's a bug."

That means the XML file parser should be changed to fix this bug in the first place, not only the XML files. 

> Still issue in 5.1.0.GA <database>-persistence-service.xml is dependent on ChannelFactory even on NonClustered
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-6991
>                 URL: https://jira.jboss.org/browse/JBAS-6991
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JMS (HornetQ)
>    Affects Versions: JBossAS-5.1.0.GA
>         Environment: Windows 2003 Server
>            Reporter: Jeff Wexler
>            Assignee: Howard Gao
>            Priority: Minor
>
> https://jira.jboss.org/jira/browse/JBAS-6333 appears to still be open in 5.1.0.GA even though it was reported as fixed in JBossAS-5.1.0.Beta1 and JBAS - 6333 was closed.
> I recognize that I may have misunderstood the intentions of the developers on JBAS - 6333 for each user to find the instructions on the workaround here and make the changes themselves rather than for the workaround to be incorporated in the scripts in docs/examples/jms? If that was the intention, I would propose that it would be better to make the change in the scripts rather than requiring the users to find the work around and make the change themselves.
> I did not see how to re-open JBAS - 6333 and thus am creating a new issue in jira.
> The change to 
> <attribute name="ChannelFactoryName">jboss.jgroups:service=ChannelFactory</attribute> 
> instead of 
> <depends optional-attribute-name="ChannelFactoryName">jboss.jgroups:service=ChannelFactory</depends> 
> is still not in docs/examples/jms/postgresql-persistence-service.xml 
> I just manually made the change to avert the Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "Configured") errors. 
> However, other encountered other messaging errors when running the booking example using postgresql and thus commented out the attribute name="ChannelFactoryName">jboss.jgroups:service=ChannelFactory statement.
> Perhaps, this statement should be commented out in the original <database>-persistence-service.xml files?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira