runServer is broken on trunk...

[clebert.suconic]

As part of my merge and work on paging on trunk, I'm trying to run the server, perfSender.. etc.


ant runServer is broken:

runServer:
 [java] 15:34:48,145 ERROR @main [AbstractKernelController] Error installing to Configured: name=Main state=Instantiated
 [java] java.lang.IllegalArgumentException: No such property host for bean org.jboss.messaging.core.config.impl.FileConfiguration available [journalSyncTransactional, packetConfirmationBatchSize, bindingsDirectory, requireDestinations, interceptorClassNames, journalMinFiles, createJournalDir, createBindingsDir, class, securityEnabled, journalFileSize, journalType, securityInvalidationInterval, journalMaxAIO, configurationUrl, connectionScanPeriod, pagingDirectory, callTimeout, backup, scheduledThreadPoolMaxSize, acceptorInfos, journalSyncNonTransactional, JMXManagementEnabled, journalDirectory, clustered]
 [java] at org.jboss.beans.info.plugins.AbstractBeanInfo.getProperty(AbstractBeanInfo.java:160)
 [java] at org.jboss.beans.info.plugins.AbstractBeanInfo.getProperty(AbstractBeanInfo.java:237)
 [java] at org.jboss.kernel.plugins.dependency.AbstractKernelControllerContext.get(AbstractKernelControllerContext.java:226)
 [java] at org.jboss.beans.metadata.plugins.AbstractDependencyValueMetaData.getValue(AbstractDependencyValueMetaData.java:171)

I had to add the property host on ConfigurationImpl to make the server start.

I could make it start, but then perfSender/perfListener is not working. The JNDI is refusing the connection:

 [java] at org.jboss.jms.example.PerfExample.runSender(PerfExample.java:128)
 [java] at org.jboss.jms.example.PerfExample.main(PerfExample.java:102)
 [java] Caused by: javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused]]
 [java] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:276)
 [java] at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1572)
 [java] ... 6 more

[timfox]

This is not fixed in trunk.

Remoting configuration like host, port etc is now specific to the transport (see config).

The old jndi server was assuming to use the same old host attribute for its own server (which no longer exists).

The jndi server host/port config is now separate - we can't really assume that they're the same anyway. Also I renamed the "Main" bean to "JNDIServer" to make it clearer what it is.

Since we allow system property substitution, the user could use ${host.name} (or whatever it is called these days) to use the same host value for jndi server and transport config if they wanted.

[timfox]

"timfox" wrote:
This is not fixed in trunk.

I meant this is *now* fixed in trunk ;)

It's amazing how much difference a single letter can make.