Unable to get the jca-config example to work| JBoss.org Content Archive (Read Only)

15. Re: Unable to get the jca-config example to work

mantaroesg Sep 29, 2009 5:01 PM (in response to mantaroesg)

It's a valid VPN IP address... unless VPN wouldn't work.

Windows IP Configuration

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : home
IP Address. . . . . . . . . . . . : 192.168.1.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1

PPP adapter Mantaro VPN:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 172.17.5.13
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :

16. Re: Unable to get the jca-config example to work

timfox Sep 29, 2009 5:25 PM (in response to mantaroesg)

The cannot bind exception is just coming from the JDK- it saying that's not a valid ip address for the machine.

17. Re: Unable to get the jca-config example to work

timfox Sep 29, 2009 5:28 PM (in response to mantaroesg)

Here's what you should do:

Post your configuration from both machines, that should include:

hornetq-configuration.xml
ra.xml
your MDB configuration

for *both machines*

Please use ip addresses and don't user system property substitution.

I.e. don't do:

<param key="hornetq.remoting.netty.host" value="${hornetq.remoting.netty.host:jboss}" type="String"/>

do:

<param key="hornetq.remoting.netty.host" value="a.b.c.d" type="String"/>

where a.b.c.d is your ip address.

Then hopefully someone can spot the problem in your config.

18. Re: Unable to get the jca-config example to work

timfox Sep 29, 2009 5:32 PM (in response to mantaroesg)

Also please post the exact errors you get (if any) with the config you're going to post, including full stack trace.

19. Re: Unable to get the jca-config example to work

timfox Sep 29, 2009 5:41 PM (in response to mantaroesg)

btw subnet mask 255.255.255.255 is odd - this is the kind of thing you would have if you had a single computer on a home broadband ADSL connection - are you sure you're not trying to use that connection by mistake?

20. Re: Unable to get the jca-config example to work

timfox Sep 29, 2009 5:48 PM (in response to mantaroesg)

Also please try replicating issue using a normal (i.e. non VPN) network with the two computers connected, to rule out the possibility of a windows network issue (like I say 255.255.255.255 is weird)

21. Re: Unable to get the jca-config example to work

mantaroesg Sep 30, 2009 12:36 AM (in response to mantaroesg)

Thank you, Tim. I really appreciate your help.

On the windows side, I cleaned up all the extra profiles under $JBOSS_HOME/server and reinstalled HornetQ beta5. Under example/javaee/jca-config, ant deploy was successful. I add one line for remote host in the hornetq-configuration.xml and it reads as follows

<configuration xmlns="urn:hornetq"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="urn:hornetq /schema/hornetq-configuration.xsd">

 <bindings-directory>${jboss.server.data.dir}/messaging/bindings</bindings-directory>

 <journal-directory>${jboss.server.data.dir}/messaging/journal</journal-directory>

 <large-messages-directory>${jboss.server.data.dir}/messaging/largemessages</large-messages-directory>

 <paging-directory>${jboss.server.data.dir}/messaging/paging</paging-directory>

 <!-- Connectors -->
 <connectors>
 <connector name="netty">
 <factory-class>org.hornetq.integration.transports.netty.NettyConnectorFactory</factory-class>
 </connector>

 <connector name="in-vm">
 <factory-class>org.hornetq.core.remoting.impl.invm.InVMConnectorFactory</factory-class>
 </connector>

 </connectors>

 <!-- Acceptors -->
 <acceptors>
 <!-- In VM acceptor -->
 <acceptor name="in-vm">
 <factory-class>org.hornetq.core.remoting.impl.invm.InVMAcceptorFactory</factory-class>
 <param key="hornetq.remoting.invm.serverid" value="0" type="Integer"/>
 </acceptor>

 <!-- Netty TCP Acceptor -->
 <acceptor name="netty">
 <factory-class>org.hornetq.integration.transports.netty.NettyAcceptorFactory</factory-class>
 <param key="hornetq.remoting.netty.host" value="172.17.2.124" type="String"/>
 <param key="hornetq.remoting.netty.port" value="${hornetq.remoting.netty.port:5445}" type="Integer"/>
 </acceptor>
 </acceptors>

 <security-settings>
 <security-setting match="jms.queue.#">
 <permission type="consume" roles="guest,publisher"/>
 <permission type="send" roles="guest,publisher"/>
 </security-setting>
 </security-settings>


</configuration>

I cut and pasted that IP address and successfully ping'ed that IP. I did ant undeploy then ant deploy, and got Failed to bind error. The following is captured output:

Buildfile: build.xml

validate-jboss:

profile.check:

copy-profile:
 [mkdir] Created dir: c:\jboss\server\jca-config-example-profile
 [copy] Copying 319 files to c:\jboss\server\jca-config-example-profile
 [copy] Copied 119 empty directories to 19 empty directories under c:\jboss\server\jca-config-example-profile

copy-resources:

init:

compile:

jar:

war:

ear:

deploy:
 [copy] Copying 2 files to c:\jboss\server\jca-config-example-profile\deploy\hornetq.sar
 [copy] Copying 1 file to c:\jboss\server\jca-config-example-profile\deploy
 [exec] ===============================================================================
 [exec]
 [exec] JBoss Bootstrap Environment
 [exec]
 [exec] JBOSS_HOME: c:\jboss
 [exec]
 [exec] JAVA: C:\Program Files\Java\jdk1.6.0_10\bin\java
 [exec]
 [exec] JAVA_OPTS: -Dprogram.name=run.bat -server -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
 [exec]
 [exec] CLASSPATH: c:\jboss\bin\run.jar
 [exec]
 [exec] ===============================================================================
 [exec]
 [exec] 23:58:56,546 INFO [ServerImpl] Starting JBoss (Microcontainer)...
 [exec] 23:58:56,546 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.1.GA (build: SVNTag=JBoss_5_0_1_GA date=200902232048)
 [exec] 23:58:56,562 INFO [ServerImpl] Bootstrap URL: null
 [exec] 23:58:56,562 INFO [ServerImpl] Home Dir: C:\jboss
 [exec] 23:58:56,562 INFO [ServerImpl] Home URL: file:/C:/jboss/
 [exec] 23:58:56,562 INFO [ServerImpl] Library URL: file:/C:/jboss/lib/
 [exec] 23:58:56,562 INFO [ServerImpl] Patch URL: null
 [exec] 23:58:56,562 INFO [ServerImpl] Common Base URL: file:/C:/jboss/common/
 [exec] 23:58:56,562 INFO [ServerImpl] Common Library URL: file:/C:/jboss/common/lib/
 [exec] 23:58:56,562 INFO [ServerImpl] Server Name: jca-config-example-profile
 [exec] 23:58:56,562 INFO [ServerImpl] Server Base Dir: C:\jboss\server
 [exec] 23:58:56,562 INFO [ServerImpl] Server Base URL: file:/C:/jboss/server/
 [exec] 23:58:56,562 INFO [ServerImpl] Server Config URL: file:/C:/jboss/server/jca-config-example-profile/conf/
 [exec] 23:58:56,562 INFO [ServerImpl] Server Home Dir: C:\jboss\server\jca-config-example-profile
 [exec] 23:58:56,562 INFO [ServerImpl] Server Home URL: file:/C:/jboss/server/jca-config-example-profile/
 [exec] 23:58:56,562 INFO [ServerImpl] Server Data Dir: C:\jboss\server\jca-config-example-profile\data
 [exec] 23:58:56,562 INFO [ServerImpl] Server Library URL: file:/C:/jboss/server/jca-config-example-profile/lib/
 [exec] 23:58:56,562 INFO [ServerImpl] Server Log Dir: C:\jboss\server\jca-config-example-profile\log
 [exec] 23:58:56,562 INFO [ServerImpl] Server Native Dir: C:\jboss\server\jca-config-example-profile\tmp\native
 [exec] 23:58:56,562 INFO [ServerImpl] Server Temp Dir: C:\jboss\server\jca-config-example-profile\tmp
 [exec] 23:58:56,562 INFO [ServerImpl] Server Temp Deploy Dir: C:\jboss\server\jca-config-example-profile\tmp\deploy
 [exec] 23:58:57,656 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/C:/jboss/server/jca-config-example-profile/conf/bootstrap.xml
 [exec] 23:58:58,656 INFO [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.plugins.cache.CombinedVFSCache]
 [exec] 23:58:58,656 INFO [VFSCacheFactory] Using VFSCache [CombinedVFSCache[real-cache: null]]
 [exec] 23:58:59,203 INFO [CopyMechanism] VFS temp dir: C:\jboss\server\jca-config-example-profile\tmp
 [exec] 23:58:59,203 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled.
 [exec] 23:59:01,578 INFO [ServerInfo] Java version: 1.6.0_10,Sun Microsystems Inc.
 [exec] 23:59:01,578 INFO [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_10-b33)
 [exec] 23:59:01,578 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 11.0-b15,Sun Microsystems Inc.
 [exec] 23:59:01,578 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
 [exec] 23:59:01,687 INFO [JMXKernel] Legacy JMX core initialized
 [exec] 23:59:06,328 INFO [ProfileServiceImpl] Loading profile: jca-config-example-profile from: org.jboss.system.server.profileservice.repository.SerializableDeploymentRepository@ca6ae(root=C:\jboss\server, key=org.jboss.profileservice.spi.ProfileKey@ae672562[domain=default,server=default,name=jca-config-example-profile])
 [exec] 23:59:06,328 INFO [ProfileImpl] Using repository:org.jboss.system.server.profileservice.repository.SerializableDeploymentRepository@ca6ae(root=C:\jboss\server, key=org.jboss.profileservice.spi.ProfileKey@ae672562[domain=default,server=default,name=jca-config-example-profile])
 [exec] 23:59:06,328 INFO [ProfileServiceImpl] Loaded profile: ProfileImpl@85e57{key=org.jboss.profileservice.spi.ProfileKey@ae672562[domain=default,server=default,name=jca-config-example-profile]}
 [exec] 23:59:09,796 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
 [exec] 23:59:20,312 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
 [exec] 23:59:20,312 INFO [NativeServerConfig] 3.0.5.GA
 [exec] 23:59:32,109 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@6821348{vfszip:/C:/jboss/server/jca-config-example-profile/deploy/jca-config-example.ear/jca-config-example.jar/}
 [exec] 23:59:32,109 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@6821348{vfszip:/C:/jboss/server/jca-config-example-profile/deploy/jca-config-example.ear/jca-config-example.jar/}
 [exec] 23:59:32,828 ERROR [STDERR] Sep 29, 2009 11:59:32 PM org.hornetq.core.logging.Logger info
 [exec] INFO: Loading server configuration from vfsfile:/C:/jboss/server/jca-config-example-profile/deploy/hornetq.sar/hornetq-configuration.xml
 [exec] 23:59:36,640 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:1090/jmxconnector
 [exec] 23:59:36,984 INFO [MailService] Mail Service bound to java:/Mail
 [exec] 23:59:40,046 ERROR [STDERR] Sep 29, 2009 11:59:40 PM org.hornetq.core.logging.Logger info
 [exec] INFO: live server is starting..
 [exec] 23:59:40,078 ERROR [STDERR] Sep 29, 2009 11:59:40 PM org.hornetq.core.logging.Logger warn
 [exec] WARNING: It has been detected that the cluster admin user and password which are used to replicate management operation from one node to the other have not been changed from the installation default. Please see the HornetQ user guide for instructions on how to do this.
 [exec] 23:59:40,187 ERROR [STDERR] Sep 29, 2009 11:59:40 PM org.hornetq.core.logging.Logger info
 [exec] INFO: AIO journal selected
 [exec] 23:59:40,203 ERROR [STDERR] Sep 29, 2009 11:59:40 PM org.hornetq.core.logging.Logger warn
 [exec] WARNING: AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal
 [exec] 23:59:40,312 ERROR [STDERR] Sep 29, 2009 11:59:40 PM org.hornetq.core.logging.Logger info
 [exec] INFO: Deploying vfsfile:/C:/jboss/server/jca-config-example-profile/deploy/hornetq.sar/hornetq-configuration.xml for AddressSettingsDeployer
 [exec] 23:59:40,531 ERROR [STDERR] Sep 29, 2009 11:59:40 PM org.hornetq.core.logging.Logger info
 [exec] INFO: Deploying vfsfile:/C:/jboss/server/jca-config-example-profile/deploy/hornetq.sar/hornetq-configuration.xml for SecurityDeployer
 [exec] 23:59:41,500 ERROR [STDERR] Sep 29, 2009 11:59:41 PM org.hornetq.core.logging.Logger info
 [exec] INFO: Deploying vfsfile:/C:/jboss/server/jca-config-example-profile/deploy/hornetq.sar/hornetq-configuration.xml for QueueDeployer
 [exec] 23:59:41,656 ERROR [STDERR] Sep 29, 2009 11:59:41 PM org.hornetq.core.logging.Logger info
 [exec] INFO: Deploying vfsfile:/C:/jboss/server/jca-config-example-profile/deploy/hornetq.sar/hornetq-jms.xml for JMSServerDeployer
 [exec] 23:59:42,312 ERROR [AbstractKernelController] Error installing to Start: name=JMSServerManager state=Create
 [exec] org.jboss.netty.channel.ChannelException: Failed to bind to: /172.17.2.124:5445
 [exec] at org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:298)
 [exec] at org.hornetq.integration.transports.netty.NettyAcceptor.startServerChannels(NettyAcceptor.java:314)
 [exec] at org.hornetq.integration.transports.netty.NettyAcceptor.start(NettyAcceptor.java:295)
 [exec] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl.start(RemotingServiceImpl.java:199)
 [exec] at org.hornetq.core.server.impl.HornetQServerImpl.start(HornetQServerImpl.java:288)
 [exec] at org.hornetq.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:146)
 [exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 [exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 [exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 [exec] at java.lang.reflect.Method.invoke(Method.java:597)
 [exec] at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59)
 [exec] at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150)
 [exec] at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
 [exec] at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:241)
 [exec] at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47)
 [exec] at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:109)
 [exec] at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:70)
 [exec] at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:221)
 [exec] at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54)
 [exec] at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42)
 [exec] at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
 [exec] at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
 [exec] at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
 [exec] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
 [exec] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
 [exec] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
 [exec] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
 [exec] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
 [exec] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:774)
 [exec] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540)
 [exec] at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:121)
 [exec] at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:51)
 [exec] at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
 [exec] at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
 [exec] at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
 [exec] at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
 [exec] at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
 [exec] at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178)
 [exec] at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
 [exec] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
 [exec] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
 [exec] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
 [exec] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
 [exec] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
 [exec] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
 [exec] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
 [exec] at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
 [exec] at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:698)
 [exec] at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304)
 [exec] at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205)
 [exec] at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405)
 [exec] at org.jboss.Main.boot(Main.java:209)
 [exec] at org.jboss.Main$1.run(Main.java:547)
 [exec] at java.lang.Thread.run(Thread.java:619)
 [exec] Caused by: java.net.BindException: Cannot assign requested address: bind
 [exec] at sun.nio.ch.Net.bind(Native Method)
 [exec] at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
 [exec] at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
 [exec] at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.bind(NioServerSocketPipelineSink.java:155)
 [exec] at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.handleServerSocket(NioServerSocketPipelineSink.java:107)
 [exec] at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk(NioServerSocketPipelineSink.java:81)
 [exec] at org.jboss.netty.channel.Channels.bind(Channels.java:653)
 [exec] at org.jboss.netty.channel.AbstractChannel.bind(AbstractChannel.java:177)
 [exec] at org.jboss.netty.bootstrap.ServerBootstrap$Binder.channelOpen(ServerBootstrap.java:344)
 [exec] at org.jboss.netty.channel.Channels.fireChannelOpen(Channels.java:197)
 [exec] at org.jboss.netty.channel.socket.nio.NioServerSocketChannel.<init>(NioServerSocketChannel.java:87)
 [exec] at org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory.newChannel(NioServerSocketChannelFactory.java:149)
 [exec] at org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory.newChannel(NioServerSocketChannelFactory.java:97)
 [exec] at org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:282)
 [exec] ... 53 more
 [exec] 23:59:42,484 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
 [exec] 23:59:42,828 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
 [exec] 23:59:42,828 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
 [exec] 23:59:43,312 INFO [TransactionManagerService] Initializing recovery manager
 [exec] 23:59:43,625 INFO [TransactionManagerService] Recovery manager configured
 [exec] 23:59:43,625 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
 [exec] 23:59:43,671 INFO [TransactionManagerService] Starting transaction recovery manager
 [exec] 23:59:44,921 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
 [exec] 23:59:44,921 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
 [exec] 23:59:44,921 INFO [StandardService] Starting service jboss.web
 [exec] 23:59:44,937 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.2.GA
 [exec] 23:59:45,062 INFO [Catalina] Server startup in 291 ms
 [exec] 23:59:45,109 INFO [TomcatDeployment] deploy, ctxPath=/web-console
 [exec] 23:59:46,687 INFO [TomcatDeployment] deploy, ctxPath=/invoker
 [exec] 23:59:46,953 INFO [TomcatDeployment] deploy, ctxPath=/jbossws
 [exec] 23:59:47,187 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss/server/jca-config-example-profile/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
 [exec] 23:59:47,265 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss/server/jca-config-example-profile/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
 [exec] 23:59:47,531 INFO [RARDeployment] Required license terms exist, view vfsfile:/C:/jboss/server/jca-config-example-profile/deploy/jms-ra.rar/META-INF/ra.xml
 [exec] 23:59:47,562 ERROR [STDERR] Sep 29, 2009 11:59:47 PM org.hornetq.core.logging.Logger info
 [exec] INFO: HornetQ resource adaptor started
 [exec] 23:59:47,640 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
 [exec] 23:59:47,671 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss/server/jca-config-example-profile/deploy/mail-ra.rar/META-INF/ra.xml
 [exec] 23:59:47,718 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss/server/jca-config-example-profile/deploy/quartz-ra.rar/META-INF/ra.xml
 [exec] 23:59:47,906 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
 [exec] 23:59:47,968 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
 [exec] 23:59:47,968 INFO [RAMJobStore] RAMJobStore initialized.
 [exec] 23:59:47,968 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
 [exec] 23:59:47,968 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
 [exec] 23:59:47,968 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
 [exec] 23:59:48,812 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
 [exec] 23:59:49,281 INFO [TomcatDeployment] deploy, ctxPath=/
 [exec] 23:59:49,562 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console
 [exec] 23:59:50,859 INFO [JBossASKernel] Created KernelDeployment for: jca-config-example.jar
 [exec] 23:59:50,859 INFO [JBossASKernel] installing bean: jboss.j2ee:ear=jca-config-example.ear,jar=jca-config-example.jar,name=MDB_QueueA,service=EJB3
 [exec] 23:59:50,859 INFO [JBossASKernel] with dependencies:
 [exec] 23:59:50,859 INFO [JBossASKernel] and demands:
 [exec] 23:59:50,859 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
 [exec] 23:59:50,859 INFO [JBossASKernel] and supplies:
 [exec] 23:59:50,859 INFO [JBossASKernel] jndi:null
 [exec] 23:59:50,859 INFO [JBossASKernel] Class:javax.jms.MessageListener
 [exec] 23:59:50,859 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=jca-config-example.ear,jar=jca-config-example.jar,name=MDB_QueueA,service=EJB3) to KernelDeployment of: jca-config-example.jar
 [exec] 23:59:51,000 INFO [EJBContainer] STARTED EJB: org.hornetq.javaee.example.server.MDBQueueA ejbName: MDB_QueueA
 [exec] 23:59:51,515 INFO [TomcatDeployment] deploy, ctxPath=/jca-config-example
 [exec] 23:59:51,625 WARN [config] Unable to process deployment descriptor for context '/jca-config-example'
 [exec] 23:59:54,421 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
 [exec]
 [exec] DEPLOYMENTS IN ERROR:
 [exec] Deployment "JMSServerManager" is in error due to the following reason(s): java.net.BindException: Cannot assign requested address: bind
 [exec]
 [exec] 23:59:54,437 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
 [exec] 23:59:54,484 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
 [exec] 23:59:54,515 INFO [ServerImpl] JBoss (Microcontainer) [5.0.1.GA (build: SVNTag=JBoss_5_0_1_GA date=200902232048)] Started in 57s:937ms

On the Linux Side, I also reinstalled HornetQ beta5 and added one line for host in the hornetq-configuration.xml under connector. It reads as follows:

<configuration xmlns="urn:hornetq"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="urn:hornetq /schema/hornetq-configuration.xsd">

 <bindings-directory>${jboss.server.data.dir}/messaging/bindings</bindings-directory>

 <journal-directory>${jboss.server.data.dir}/messaging/journal</journal-directory>

 <large-messages-directory>${jboss.server.data.dir}/messaging/largemessages</large-messages-directory>

 <paging-directory>${jboss.server.data.dir}/messaging/paging</paging-directory>

 <!-- Connectors -->
 <connectors>
 <connector name="netty">
 <factory-class>org.hornetq.integration.transports.netty.NettyConnectorFactory</factory-class>
 <param key="hornetq.remoting.netty.host" value="172.17.5.13" type="String"/>
 <param key="hornetq.remoting.netty.port" value="${hornetq.remoting.netty.port:5445}" type="Integer"/>
 </connector>

 <connector name="in-vm">
 <factory-class>org.hornetq.core.remoting.impl.invm.InVMConnectorFactory</factory-class>
 </connector>

 </connectors>

 <!-- Acceptors -->
 <acceptors>
 <!-- In VM acceptor -->
 <acceptor name="in-vm">
 <factory-class>org.hornetq.core.remoting.impl.invm.InVMAcceptorFactory</factory-class>
 <param key="hornetq.remoting.invm.serverid" value="0" type="Integer"/>
 </acceptor>

 <!-- Netty TCP Acceptor -->
 <acceptor name="netty">
 <factory-class>org.hornetq.integration.transports.netty.NettyAcceptorFactory</factory-class>
 <param key="hornetq.remoting.netty.port" value="${hornetq.remoting.netty.port:5445}" type="Integer"/>
 </acceptor>
 </acceptors>

 <security-settings>
 <security-setting match="jms.queue.#">
 <permission type="consume" roles="guest,publisher"/>
 <permission type="send" roles="guest,publisher"/>
 </security-setting>
 </security-settings>


</configuration>

I started deploy and deploy2 in 2 separate windows, no errors. from a third windows, I did ant run, both Queue A and Queue B got the messages.

The Linux side seemed to work fine. The problem seemed to be a binding problem.

with netstat -anp|grep 5445 command on Linux, it seemed no 0.0.0.0 was bound to port 5445. Could this be the problem?

[root@jboss jca-config]# netstat -anp |grep 5445
tcp 0 0 127.0.0.1:5445 0.0.0.0:* LISTEN 1953/java
tcp 0 0 127.0.0.1:5445 127.0.0.1:54901 ESTABLISHED 1953/java
tcp 0 0 127.0.0.1:5445 127.0.0.1:54900 ESTABLISHED 1953/java
tcp 0 0 127.0.0.1:5445 127.0.0.1:54903 ESTABLISHED 1953/java
tcp 0 0 127.0.0.1:5445 127.0.0.1:54902 ESTABLISHED 1953/java
tcp 0 0 127.0.0.1:5445 127.0.0.1:54897 ESTABLISHED 1953/java
tcp 0 0 127.0.0.1:5445 127.0.0.1:54899 ESTABLISHED 1953/java
tcp 0 0 127.0.0.1:5445 127.0.0.1:54898 ESTABLISHED 1953/java
tcp 0 0 127.0.0.1:5445 127.0.0.1:54904 ESTABLISHED 1953/java
tcp 0 0 127.0.0.1:54902 127.0.0.1:5445 ESTABLISHED 2005/java
tcp 0 0 127.0.0.1:54903 127.0.0.1:5445 ESTABLISHED 2005/java
tcp 0 0 127.0.0.1:54900 127.0.0.1:5445 ESTABLISHED 2005/java
tcp 0 0 127.0.0.1:54901 127.0.0.1:5445 ESTABLISHED 2005/java
tcp 0 0 127.0.0.1:54898 127.0.0.1:5445 ESTABLISHED 2005/java
tcp 0 0 127.0.0.1:54899 127.0.0.1:5445 ESTABLISHED 2005/java
tcp 0 0 127.0.0.1:54897 127.0.0.1:5445 ESTABLISHED 2005/java
tcp 0 0 127.0.0.1:54904 127.0.0.1:5445 ESTABLISHED 2005/java
[root@jboss jca-config]#

I added -b 0.0.0.0 in build.xml and common/build.xml after run.sh -c ... but still got the same list...

22. Re: Unable to get the jca-config example to work

timfox Sep 30, 2009 4:34 AM (in response to mantaroesg)

"mantaroesg" wrote:
Thank you, Tim. I really appreciate your help.

On the windows side, I cleaned up all the extra profiles under $JBOSS_HOME/server and reinstalled HornetQ beta5. Under example/javaee/jca-config, ant deploy was successful. I add one line for remote host in the hornetq-configuration.xml and it reads as follows
<configuration xmlns="urn:hornetq"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="urn:hornetq /schema/hornetq-configuration.xsd">
 ...
snip
...

 
 <acceptor name="netty">
 <factory-class>org.hornetq.integration.transports.netty.NettyAcceptorFactory</factory-class>
 <param key="hornetq.remoting.netty.host" value="172.17.2.124" type="String"/>
 <param key="hornetq.remoting.netty.port" value="${hornetq.remoting.netty.port:5445}" type="Integer"/>
 </acceptor>
 </acceptors>


</configuration>
I cut and pasted that IP address and successfully ping'ed that IP. I did ant undeploy then ant deploy, and got Failed to bind error. The following is captured output:
 [exec] 23:59:42,312 ERROR [AbstractKernelController] Error installing to Start: name=JMSServerManager state=Create
 [exec] org.jboss.netty.channel.ChannelException: Failed to bind to: /172.17.2.124:5445

It's hardly surprising it won't bind to that address, since that machine doesn't have that ip address!

I think you're misunderstanding what an acceptor and connector is.

On your Windows machine you are telling it to *listen* for *incoming connections* on the address 172.17.2.124 and port 5445

That means it will create a Java ServerSocket (see Java sockets tutorial) on that address. The Windows machine must have that address - but it seems to me you have given it the address of the other machine.

The user manual has a good description of this, but let me clarify it further, let's say you have two machines A and B

A has an ip address of 1.2.3.4 (yes I know that's not a good ip address but this is just for the sake of illustration) and B has an ip address of 5.6.7.8

If you want machine A to connect to machine B, then you

a) Create an acceptor on machine A that specifies the bind address 1.2.3.4 - note this is the address of machine A, not the address of machine B! This tells Java to create a server socket listening for incoming connections on address A.

b) Create a connector on machine B that specifies the connect address 1.2.3.4- note this is also the adress of machine A, not of machine B!

This tells machine B to create a TCP connection to the destination address which is 1.2.3.4 - the address of the other machine. At the other end machine A must be listening on that server socket for a TCP connection to be made.

In your config you seem to have configured everything back to front.

To sum up, acceptors do what it says on the tin, they "accept" connections from other machines, they need to be configured with the local adress they are listening on.

Connectors, make "connections" to other nodes - they need to be configured with the destination they are connecting to.

Hope that helps clear things up.

Like I mentioned before, please read the connectors/acceptors chapter in the user manual. All this info is present there.

I'd also recommend the Java sockets tutorial - which gives you some low level understanding of Java sockets.

http://java.sun.com/docs/books/tutorial/networking/sockets/

Basically our layer wraps that.

Hope that helps.

23. Re: Unable to get the jca-config example to work

mantaroesg Sep 30, 2009 9:08 AM (in response to mantaroesg)

Thank you, Tim. I think I am getting closer...

I want the queue in my dell box (IP 172.17.5.12. it changes each time I log into VPN, that is the first thing I check) to receive messages so I have acceptor and connector all pointed to this IP.

on dell:

<!-- Acceptors -->
 <acceptors>
 <!-- In VM acceptor -->
 <acceptor name="in-vm">
 <factory-class>org.hornetq.core.remoting.impl.invm.InVMAcceptorFactory</factory-class>
 <param key="hornetq.remoting.invm.serverid" value="0" type="Integer"/>
 </acceptor>

 <!-- Netty TCP Acceptor -->
 <acceptor name="netty">
 <factory-class>org.hornetq.integration.transports.netty.NettyAcceptorFactory</factory-class>
 <param key="hornetq.remoting.netty.host" value="172.17.5.12" type="String"/>
 <param key="hornetq.remoting.netty.port" value="${hornetq.remoting.netty.port:5445}" type="Integer"/>
 </acceptor>
 </acceptors>

On Linux box (both under both server and server2 of jca-config)

<!-- Connectors -->
 <connectors>
 <connector name="netty">
 <factory-class>org.hornetq.integration.transports.netty.NettyConnectorFactory</factory-class>
 <param key="hornetq.remoting.netty.host" value="172.17.5.12" type="String"/>
 <param key="hornetq.remoting.netty.port" value="${hornetq.remoting.netty.port:5446}" type="Integer"/>
 </connector>

 <connector name="in-vm">
 <factory-class>org.hornetq.core.remoting.impl.invm.InVMConnectorFactory</factory-class>
 </connector>

 </connectors>

I started all these 3 "servers" (I had tried in difference orders) server then server2 on Linux first then server on dell and vice versa. No errors. When I ran ant deploy against server2 on linux, like before, both server and server2 on Linux got messages, but not on dell.

I tried to run server on dell first then only starting server2 on linux. I got the following error:

[exec] 04:05:42,580 INFO [SessionSpecContainer] Starting jboss.j2ee:ear=jca-config-example2.ear,jar=jca-config-example2.jar,name=StatelessSender,service=EJB3
 [exec] 04:05:42,596 INFO [EJBContainer] STARTED EJB: org.hornetq.javaee.example.server2.StatelessSender ejbName: StatelessSender
 [exec] 04:05:42,719 ERROR [STDERR] Sep 30, 2009 4:05:42 AM org.hornetq.core.logging.Logger error
 [exec] SEVERE: Unabler to start activation
 [exec] HornetQException[errorCode=2 message=Unable to connect to server using configuration org-hornetq-integration-transports-netty-NettyConnectorFactory]
 [exec] at org.hornetq.core.client.impl.ConnectionManagerImpl.createSession(ConnectionManagerImpl.java:290)
 [exec] at org.hornetq.core.client.impl.ClientSessionFactoryImpl.createSessionInternal(ClientSessionFactoryImpl.java:976)
 [exec] at org.hornetq.core.client.impl.ClientSessionFactoryImpl.createSession(ClientSessionFactoryImpl.java:721)
 [exec] at org.hornetq.ra.HornetQResourceAdapter.createSession(HornetQResourceAdapter.java:1322)
 [exec] at org.hornetq.ra.inflow.HornetQActivation.setupSession(HornetQActivation.java:342)
 [exec] at org.hornetq.ra.inflow.HornetQActivation.setup(HornetQActivation.java:289)
 [exec] at org.hornetq.ra.inflow.HornetQActivation$SetupActivation.run(HornetQActivation.java:498)
 [exec] at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:213)
 [exec] at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
 [exec] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 [exec] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 [exec] at java.lang.Thread.run(Thread.java:619)
 [exec] 04:05:42,738 INFO [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:
 [exec]
 [exec] jca-config-example2/StatelessSender/remote - EJB3.x Default Remote Business Interface
 [exec] jca-config-example2/StatelessSender/remote-org.hornetq.javaee.example.server2.StatelessSenderService - EJB3.x Remote Business Interface
 [exec]
 [exec] 04:05:42,852 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8180
 [exec] 04:05:42,885 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-0.0.0.0-8109
 [exec] 04:05:42,900 INFO [ServerImpl] JBoss (Microcontainer) [5.0.1.GA (build: SVNTag=JBoss_5_0_1_GA date=200902232048)] Started in 58s:561ms

also tried to start server2 on linux first, got the same error.

I thought the connector on server2 (linux) is pointed to dell not localhost, and didn't expect server (linux) to be receiving messages..

I must have missed something...

24. Re: Unable to get the jca-config example to work

mantaroesg Sep 30, 2009 4:03 PM (in response to mantaroesg)

I don't think this is related to VPN or windows. I had tried to have both hosts in the same LAN and both on Linux. I got the same results.

25. Re: Unable to get the jca-config example to work

mantaroesg Sep 30, 2009 10:25 PM (in response to mantaroesg)

Cut and pasted the port wrong. I was using port 5446 for both connector and acceptor. Still nothing showed up at the remote host.