I've flipped trunk (AS5) to the latest jboss messaging/remoting combination. Let me know if you see any problems. Thanks /Dimitris - <componentref name="jboss/messaging" version="1.4.0.SP1-brew"/> + <componentref name="jboss/messaging" version="1.4.0.SP2-brew"/> ... - <componentref name="jboss/remoting" version="2.2.2.SP2"/> + <componentref name="jboss/remoting" version="2.2.2.SP3-brew"/> _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

And the all configuration is broken: ------------------------------------------------------- GMS: address is 127.0.0.1:32803 ------------------------------------------------------- 17:05:21,538 ERROR [ExceptionUtil] org.jboss.messaging.core.jmx.MessagingPostOfficeService@124aa56 startService java.lang.NullPointerException at org.jboss.messaging.core.impl.postoffice.GroupMember.start(GroupMember.java:160) at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.start(MessagingPostOffice.java:347) On Fri, 2007-12-07 at 17:02 +0100, Adrian Brock wrote: > It doesn't boot, because the XMBean description does not have this > attribute. > > 16:33:51,253 ERROR [AbstractKernelController] Error installing to > Configured: name=jboss.messaging:service=ServerPeer state=Instantiated > mode=Manual requiredState=Configured > org.jboss.deployment.DeploymentException: No Attribute found with name: > UseXAForMessagePull for jboss.messaging:service=ServerPeer, attributes: > [ProviderVersion, DefaultExpiryQueue, DefaultMaxDeliveryAttempts, > JMSProviderName, FailoverCompleteTimeout, JMSVersion, > DefaultRedeliveryDelay, StrictTck, Destinations, SecurityDomain, > FailoverStartTimeout, MessageStatistics, RecoverDeliveriesTimeout, > DefaultPreserveOrdering, DefaultSecurityConfig, > DefaultMessageCounterHistoryDayLimit, DefaultDLQ, SuckerPassword, > Instance, DefaultTopicJNDIContext, ServerPeerID, > ClusterPullConnectionFactoryName, PostOffice, PersistenceManager, > MessageCounters, ProviderMajorVersion, JMSMajorVersion, > DefaultQueueJNDIContext, JMSUserManager, JMSMinorVersion, > SupportsFailover, MessageCounterSamplePeriod, ProviderMinorVersion] > at > org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:130) > at > org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:102) > at > org.jboss.system.microcontainer.ConfigureAction.installAction(ConfigureAction.java:58) > > > On Fri, 2007-12-07 at 13:00 +0200, Dimitris Andreadis wrote: >> I've flipped trunk (AS5) to the latest jboss messaging/remoting combination. >> >> Let me know if you see any problems. >> >> Thanks >> /Dimitris >> >> - <componentref name="jboss/messaging" version="1.4.0.SP1-brew"/> >> + <componentref name="jboss/messaging" version="1.4.0.SP2-brew"/> >> ... >> - <componentref name="jboss/remoting" version="2.2.2.SP2"/> >> + <componentref name="jboss/remoting" version="2.2.2.SP3-brew"/> >> >> _______________________________________________ >> jboss-development mailing list >> jboss-development(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-development

Adrian Brock wrote: > It doesn't boot, because the XMBean description does not have this > attribute. > Yes that attribute was removed in SP2. This implies TRUNK is using the old (pre SP2) config. I.e. the upgrade to 1.4.0.SP2 was only partial done.

Tim Fox wrote: > Adrian Brock wrote: >> It doesn't boot, because the XMBean description does not have this >> attribute. >> > Yes that attribute was removed in SP2. > > This implies TRUNK is using the old (pre SP2) config. I.e. the > upgrade to 1.4.0.SP2 was only partial done. I did the upgrade by didn't know about the attribute removal. What exactly is needed?

On Fri, 2007-12-07 at 10:25 -0600, Rajesh Rajasekaran wrote: > Or now that the JBM resources are in the repository, we can modify the > AS build to pick them up directly from thirdparty than updating > jbossas/trunk/messaging/src/etc/deploy/ every time. > > NO!!!!!! Integration (including all deployment descriptors) goes in the JBossAS project.

If the messaging project wants to provide examples that's ok. But there's no way messaging can provide a working configuration in a single release that is applicable to all versions of JBoss (or other projects using messaging, e.g. ESB). > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development >

Dimitris Andreadis wrote: > > > Tim Fox wrote: >> Adrian Brock wrote: >>> It doesn't boot, because the XMBean description does not have this >>> attribute. >>> >> Yes that attribute was removed in SP2. >> >> This implies TRUNK is using the old (pre SP2) config. I.e. the >> upgrade to 1.4.0.SP2 was only partial done. > > I did the upgrade by didn't know about the attribute removal. What > exactly is needed? > I think the jboss messaging config files here need to be updated https://svn.jboss.org/repos/jbossas/trunk/messaging/src/etc/deploy/ with the ones from http://repository.jboss.com/jboss/messaging/1.4.0.SP2-brew/resources/ Or now that the JBM resources are in the repository, we can modify the AS build to pick them up directly from thirdparty than updating jbossas/trunk/messaging/src/etc/deploy/ every time.

I've said this before, but now I'll say it more strongly. There should be NO BREW RELEASES in the jboss.org releases. If the project is on jboss.org then we should use a tag from svn.jboss.org not some cvs server somewhere on a Redhat server. All patches must go downstream into the open source project first! brew is as bad as snapshot. Also all releases should come with a zip file "artificat" (i.e. something that gets downloaded into thirdparty) that is the source, not a seperate directory containing a non-portable tar.gz file that doesn't get downloaded. tar.gz only works properly on GNU/Linux distributions. JBoss is cross platform. On Fri, 2007-12-07 at 13:00 +0200, Dimitris Andreadis wrote: > I've flipped trunk (AS5) to the latest jboss messaging/remoting combination. > > Let me know if you see any problems. > > Thanks > /Dimitris > > - <componentref name="jboss/messaging" version="1.4.0.SP1-brew"/> > + <componentref name="jboss/messaging" version="1.4.0.SP2-brew"/> > ... > - <componentref name="jboss/remoting" version="2.2.2.SP2"/> > + <componentref name="jboss/remoting" version="2.2.2.SP3-brew"/> > > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development >