JBossDeveloper

Please don't misinterpret my questions. I am just trying to get an idea of what our strategy is with ESB in terms of what you are going to require from JCA. It was not meant to be an assertion or condemnation of what you are, or are not, using currently.

Geez, you guys are quite the sensitive bunch huh?

"weston.price@jboss.com" wrote:
Please don't misinterpret my questions. I am just trying to get an idea of what our strategy is with ESB in terms of what you are going to require from JCA. It was not meant to be an assertion or condemnation of what you are, or are not, using currently.

Geez, you guys are quite the sensitive bunch huh?

"kurt.stam@jboss.com" wrote:
Well I'm back :). And it seems to me that this much-a-do about nothing. Like I said before we are not transactional on this release and we are not using JCA for this release. As far as Weston's question goes, we probably want JCA support in the MC going forward, so we can use that, in combination with JBossTS - like Mark just said.

I tested the jbossesb-4.0RC1 HelloWorld quickstart with JBoss Messaging installed in JBoss-4.0.5. To get it to work I had to:

1) Change the queue definitions in esb-quickstart-service.xml to use JBoss Messaging queues, e.g.,


<loader-repository>jboss.messaging:loader=ScopedLoaderRepository
<loader-repository-config>java2ParentDelegation=false</loader-repository-config>
</loader-repository>
<mbean code="org.jboss.jms.server.destination.Queue"
name="jboss.messaging.destination:service=Queue,name=quickstart_helloworld_Request"
xmbean-dd="xmdesc/Queue-xmbean.xml">
<depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer


2) Copied the jboss-messaging-client.jar to JBoss-4.0.5.GA/client and added the following to the helloworld_embedded_reg/build.xml classpath






Is the plan to release the ESB with examples that out-of-the-box use JBossMQ or JBoss Messaging?

Oops, the XML snippets did not post:

1) Change the queue definitions in esb-quickstart-service.xml to use JBoss Messaging queues, e.g.,

<server>
<loader-repository>jboss.messaging:loader=ScopedLoaderRepository
 <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
</loader-repository>
<mbean code="org.jboss.jms.server.destination.Queue"
 name="jboss.messaging.destination:service=Queue,name=quickstart_helloworld_Request"
 xmbean-dd="xmdesc/Queue-xmbean.xml">
 <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
</mbean>

 <fileset dir="${jbosshome.dir}/server/ps/deploy/jboss-aop-jdk50.deployer">
 <include name="jboss-aop-jdk50.jar"/>
 </fileset>

Next I tried to deploy ESB to JBoss 4.0.5.GA and Oracle (previous test was running ESB standalone). I got my datasources created, tables created in Oracle and publisher inserted, and jboss-messaging-client.jar into the lib directory (so that is is available to the ESB), listeners and gateways copied over, but get an exception when trying to go to the registry. Looking in the log, I see:

2006-12-13 20:57:24,625 INFO [org.jboss.soa.esb.services.registry.RegistryException] Going to load null

I have tried to trace through the source code to see how this value is pulled from a properties file, but cannot find the properties file anywhere?

What am I missing here?

Thanks.

That's a registry error. If you are using Oracle, did you setup the tables needed by juddi? You can find the sql under install/registry/sql i think.

Yes, I did set up the tables. That oracle sql script ran fine. For the script to insert the data I used the one for Hypersonic, it worked as well with Oracle. I have my datasources set up also.

From the log it appears that the RegistryFactory cannot read the property that holds the name of the Registry service, and is using null instead. Does this sound reasonable, or do you think it is somehow related to my database setup?

Thx

Here is a snippet from the log:

2006-12-14 08:22:40,171 DEBUG [org.jboss.jms.server.endpoint.ServerConnectionEndpoint] ConnectionEndpoint[-2147483646] started
2006-12-14 08:22:40,171 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@e7f6eb, cl=org.jboss.mx.loading.HeirarchicalLoaderRepository3$CacheClassLoader@131cd12{ url=null ,addedOrder=0}
2006-12-14 08:22:40,171 DEBUG [org.jboss.jms.client.JBossSession] attempting to create consumer for destination:JBossQueue[B]
2006-12-14 08:22:40,187 DEBUG [org.jboss.jms.server.security.SecurityMetadataStore] No SecurityMetadadata was available for B, using default security config
2006-12-14 08:22:40,187 DEBUG [org.jboss.jms.server.endpoint.ServerSessionEndpoint] creating consumer for JBossQueue[B], selector null, subscription null
2006-12-14 08:22:40,187 DEBUG [org.jboss.jms.server.endpoint.ServerConsumerEndpoint] ConsumerEndpoint[-2147483644] constructed
2006-12-14 08:22:40,218 DEBUG [org.jboss.jms.server.ServerPeer] ServerPeer [server.0] caching consumer -2147483644
2006-12-14 08:22:40,218 DEBUG [org.jboss.jms.server.endpoint.ServerSessionEndpoint] created and registered ConsumerEndpoint[-2147483644]
2006-12-14 08:22:40,468 DEBUG [org.jboss.soa.esb.listeners.message.EsbListenerController] About to sleep 26141
2006-12-14 08:22:40,468 DEBUG [org.jboss.soa.esb.listeners.message.JmsQueueListener] run() method of JmsQueueListener started on thread Thread-27
2006-12-14 08:22:40,468 INFO [org.jboss.soa.esb.services.registry.RegistryException] Going to load null
2006-12-14 08:22:40,468 DEBUG [org.jboss.soa.esb.common.Factory] Using the Context ClassLoader
2006-12-14 08:22:40,468 FATAL [org.jboss.soa.esb.listeners.message.JmsQueueListener] Could not register service Invocation exception. null
org.jboss.soa.esb.services.registry.RegistryException: Invocation exception. null
at org.jboss.soa.esb.services.registry.RegistryFactory.getRegistry(RegistryFactory.java:49)
at org.jboss.soa.esb.listeners.message.EsbListenerController.register(EsbListenerController.java:571)
at org.jboss.soa.esb.listeners.message.JmsQueueListener.run(JmsQueueListener.java:87)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NullPointerException
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:242)
at org.jboss.soa.esb.common.Factory.getClassForName(Factory.java:47)
at org.jboss.soa.esb.services.registry.RegistryFactory.getRegistry(RegistryFactory.java:43)
... 3 more
2006-12-14 08:23:06,609 INFO [org.jboss.soa.esb.services.registry.RegistryException] Going to load null
2006-12-14 08:23:06,968 INFO [org.jboss.soa.esb.listeners.message.EsbListenerController] Reloading parameters _____________________________________________________
2006-12-14 08:23:08,671 DEBUG [org.jboss.soa.esb.common.Factory] Using the Context ClassLoader
2006-12-14 08:23:08,671 WARN [org.jboss.soa.esb.listeners.message.JmsQueueListener] Could not un register service Invocation exception. null
2006-12-14 08:23:08,687 WARN [org.jboss.soa.esb.listeners.message.AbstractListener] Attribute maxThreads has not been set. Action pipeline will be processed by only one thread
2006-12-14 08:23:08,687 INFO [org.jboss.soa.esb.listeners.message.JmsQueueListener] Reading value for destination-name
2006-12-14 08:23:08,687 INFO [org.jboss.soa.esb.listeners.message.JmsQueueListener] Reading value for service-category
2006-12-14 08:23:08,687 INFO [org.jboss.soa.esb.listeners.message.JmsQueueListener] Reading value for service-name
2006-12-14 08:23:08,687 DEBUG [org.jboss.jms.client.remoting.MessageCallbackHandler] MessageCallbackHandler[-2147483644] closing
2006-12-14 08:23:08,687 DEBUG [org.jboss.soa.esb.listeners.message.JmsQueueListener] No value specified for: message-selector - All messages in queue will be received by this listener
2006-12-14 08:23:08,687 INFO [org.jboss.soa.esb.listeners.message.JmsQueueListener] Reading value for jndi-type
2006-12-14 08:23:08,687 INFO [org.jboss.soa.esb.listeners.message.JmsQueueListener] Reading value for jndi-URL
2006-12-14 08:23:08,687 INFO [org.jboss.soa.esb.listeners.message.JmsQueueListener] Reading value for connection-factory
2006-12-14 08:23:08,687 DEBUG [org.jboss.jms.client.container.ClosedInterceptor] ClosedInterceptor.ClientConsumerDelegate[-2147483644] closed
2006-12-14 08:23:08,703 DEBUG [org.jboss.jms.client.remoting.JMSRemotingConnection] JMSRemotingConnection[socket://10.84.0.4:4457/?clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.server.remoting.JMSWireFormat&serializationtype=jboss&socket.check_connection=false&unmarshaller=org.jboss.jms.server.remoting.JMSWireFormat] created
2006-12-14 08:23:08,703 DEBUG [org.jboss.remoting.transport.socket.SocketServerInvoker] ServerInvoker (org.jboss.remoting.transport.socket.SocketServerInvoker@1c330aa) added client callback handler org.jboss.jms.client.remoting.DummyCallbackHandler@7a6c34 with session id of a2c04-eb4k4s-evpbmlgb-1-evpbnrj3-d+a2c04-eb4k4s-evpbmlgb-1-evpbnrj3-e and callback handle object of null.
2006-12-14 08:23:08,703 DEBUG [org.jboss.jms.server.ServerPeer] ServerPeer [server.0] removing consumer -2147483644

I think the issue is that the jbossesb-properties from the helloworld example did not get deployed. I must have missed this step.

Yes, that was the problem. THe jbossesb-properties was not deployed. How should this file be deployed? In the conf directory, or as part of the SAR?

If the former, the QuickStart.pdf should be updated to direct the user to copy it to conf.