ObjectWeb Consortium
Search ObjectWeb Mail Archive: 

Advanced Search - Powered by Google


Mail Archive Home | proactive List | January 2005 Index

<--  Date Index  --> <--  Thread Index  -->

ProActive and JBoss 3.2.6


Hello,

I am trying to use Jboss 3.2.6 as the RMI registry for a ProActive
application but am running into issues trying get the combination work -
any help would be much appreciated.

I am currently using the HelloClient running in one JVM as my sample
application (on Win XP).

I have followed the advice given by Romain Quilici in "Re: [proactive]
ProActive & J2ee container"
(http://mail-archive.objectweb.org/proactive/2004-07/msg00009.html) and
have included the proactive.java.policy file in the startup script of
Jboss.

The behavior I see is:

The HelloClient starts and tries to start the internal RMI registry and
fails (because the Jboss registry has already attached to port 1099).

It looks like the HelloClient then tried to contact Jboss on 1099. Jboss
sees the attempt and reports an Exception writing back to HelloClient
(socket write error). The HelloClient throws a ConnectIOException
(non-JRMP server at remote endpoint). Stack traces are included below

Has anyone gotten this to work or have any insight?

Thanks in advance.

Mel Martin


-------HelloClient Output--------
 --> This ClassFileServer is reading resources from classpath 
Jini enabled 
Ibis enabled 
java.rmi.server.ExportException: Port already in use: 1099; nested
exception is: 
        java.net.BindException: Address already in use: JVM_Bind
Cannot detect an existing RMI Registry on port 1099 nor create one
e=java.rmi.server.ExportException: Port already in use: 1099; nested
exception is: 

....initial stack trace deleted.....

Could not reach/create server object
Cannot create the default Node; nested exception is: 
org.objectweb.proactive.core.ProActiveException: Error when getting the
default ProActiveRuntime; nested exception is: 
org.objectweb.proactive.core.ProActiveException: Cannot create the
RemoteProActiveRuntimeImpl; nested exception is: 
java.rmi.ConnectIOException: non-JRMP server at remote endpoint
Error when getting the default ProActiveRuntime; nested exception is: 
org.objectweb.proactive.core.ProActiveException: Cannot create the
RemoteProActiveRuntimeImpl; nested exception is: 
java.rmi.ConnectIOException: non-JRMP server at remote endpoint
Cannot create the RemoteProActiveRuntimeImpl; nested exception is: 
java.rmi.ConnectIOException: non-JRMP server at remote endpoint
java.rmi.ConnectIOException: non-JRMP server at remote endpoint
        at
sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:217)
        at
sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
        at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:313)
        at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
        at java.rmi.Naming.bind(Naming.java:111)
        at
org.objectweb.proactive.core.runtime.rmi.RemoteProActiveRuntimeImpl.regi
ster(RemoteProActiveRuntimeImpl.java:385)
        at
org.objectweb.proactive.core.runtime.rmi.RemoteProActiveRuntimeImpl.cons
truct(RemoteProActiveRuntimeImpl.java:70)
        at
org.objectweb.proactive.core.runtime.rmi.RemoteProActiveRuntimeImpl.<ini
t>(RemoteProActiveRuntimeImpl.java:76)
        at
org.objectweb.proactive.core.runtime.rmi.RemoteRuntimeFactory.createRunt
imeAdapter(RemoteRuntimeFactory.java:129)
        at
org.objectweb.proactive.core.runtime.rmi.RemoteRuntimeFactory.getProtoco
lSpecificRuntimeImpl(RemoteRuntimeFactory.java:95)
        at
org.objectweb.proactive.core.runtime.RuntimeFactory.getProtocolSpecificR
untime(RuntimeFactory.java:175)
        at
org.objectweb.proactive.core.runtime.RuntimeFactory.getDefaultRuntime(Ru
ntimeFactory.java:147)
        at
org.objectweb.proactive.core.node.NodeFactory.getDefaultNode(NodeFactory
.java:111)
        at
org.objectweb.proactive.ProActive.newActive(ProActive.java:230)
        at
org.objectweb.proactive.ProActive.newActive(ProActive.java:158)
        at
com.fgm.tracker.proactive.HelloClient.main(HelloClient.java:24) 


-------Jboss Log Output-------
2005-01-12 10:21:50,889 ERROR [org.jboss.naming.NamingService] Error
writing response
java.net.SocketException: Software caused connection abort: socket write
error
        at java.net.SocketOutputStream.socketWrite0(Native Method)
        at
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
        at
java.net.SocketOutputStream.write(SocketOutputStream.java:136)
        at
java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStrea
m.java:1639)
        at
java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(Object
OutputStream.java:1548)
        at
java.io.ObjectOutputStream.writeNonProxyDesc(ObjectOutputStream.java:114
6)
        at
java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java:1100)
        at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1
241)
        at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
        at
java.io.ObjectOutputStream.writeFatalException(ObjectOutputStream.java:1
355)
        at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:281)
        at
org.jnp.server.Main$BootstrapRequestHandler.run(Main.java:452)
        at
org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.ja
va:97)
        at
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecuto
r.java:743)
        at java.lang.Thread.run(Thread.java:534)



<--  Date Index  --> <--  Thread Index  -->

Reply via email to:

Powered by MHonArc.

Copyright © 1999-2005, ObjectWeb Consortium | contact | webmaster.