Nabble - JADE (Java Agent DEvelopment Framework)

RE: JadeGateway class

2009-12-18T10:07:38Z

Hi,

MalformedURLException makes me think that RMI (Jade uses Java RMI for container-to-container communication) doesn't like "PC-42C.aero.polimi.it".

I would suggest the following options:
1) Try specifying the IP address instead of the name
2) Try the automatic main detection:
p.setProperty(Profile.DETECT_MAIN, "true");
3) Try using JADE-LEAP instead of pure JADE (just substitute the jade jar files with the JadeLeap jar file). JADE-LEAP doesn't use RMI.

Bye,

Giovanni

-----Original Message-----
From: andrea.brambilla@... [mailto:andrea.brambilla@...]
Sent: giovedì 17 dicembre 2009 16.25
To: Caire Giovanni
Cc: jade-develop@...
Subject: RE: [jade-develop] JadeGateway class

Thanks Giovanni for your prompt reply.
I understood how to use the JadeGateway class and you are right, it
looks very simple, however I am afraid I am missing something else.

I tried both:

JadeGateway.init("macgateway.MACGateWayAgent",null);

and

Properties p = new Properties();
p.setProperty("port", "1099");
p.setProperty("host", "PC-42C.aero.polimi.it");
JadeGateway.init("macgateway.MACGateWayAgent",p);

but with no success, please find below the log and in attachment the
correspondent jsp. (I have already checked that the path of GlassFish
v3 Prelude Domain doesn't contain any space)

Thanks for the help,

Andrea

17-dic-2009 16.06.51 jade.core.Runtime beginContainer
INFO: ----------------------------------
This is JADE 3.7 - revision 6154 of 2009/07/01 17:34:15
downloaded in Open Source, under LGPL restrictions,
at http://jade.tilab.com/
----------------------------------------
17-dic-2009 16.06.52 jade.core.BaseService init
INFO: Service jade.core.management.AgentManagement initialized
17-dic-2009 16.06.52 jade.core.BaseService init
INFO: Service jade.core.messaging.Messaging initialized
17-dic-2009 16.06.52 jade.core.BaseService init
INFO: Service jade.core.mobility.AgentMobility initialized
17-dic-2009 16.06.53 jade.core.BaseService init
INFO: Service jade.core.event.Notification initialized
17-dic-2009 16.06.53 jade.core.AgentContainerImpl joinPlatform
GRAVE: Communication failure while joining agent platform: RMI
exception [nested java.rmi.ServerException: RemoteException occurred
in server thread; nested exception is:
java.rmi.UnmarshalException: error unmarshalling arguments;
nested exception is:
java.net.MalformedURLException: no protocol: and]
17-dic-2009 16.06.53
GRAVE: jade.core.IMTPException: RMI exception [nested
java.rmi.ServerException: RemoteException occurred in server thread;
nested exception is:
java.rmi.UnmarshalException: error unmarshalling arguments;
nested exception is:
java.net.MalformedURLException: no protocol: and]
17-dic-2009 16.06.53
GRAVE: at
jade.imtp.rmi.RMIIMTPManager$PlatformManagerAdapter.addNode(RMIIMTPManager.java:550)
17-dic-2009 16.06.53
GRAVE: at
jade.core.ServiceManagerImpl.addNode(ServiceManagerImpl.java:178)
17-dic-2009 16.06.53
GRAVE: at
jade.core.AgentContainerImpl.startNode(AgentContainerImpl.java:422)
17-dic-2009 16.06.53
GRAVE: at
jade.core.AgentContainerImpl.joinPlatform(AgentContainerImpl.java:481)
17-dic-2009 16.06.53
GRAVE: at jade.core.Runtime.createAgentContainer(Runtime.java:116)
17-dic-2009 16.06.53
GRAVE: at
jade.wrapper.gateway.JadeGateway.checkJADE(JadeGateway.java:132)
17-dic-2009 16.06.53
GRAVE: at org.apache.jsp.index_jsp._jspService(index_jsp.java
from :71)
17-dic-2009 16.06.53
GRAVE: at
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:109)
17-dic-2009 16.06.53
GRAVE: at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
17-dic-2009 16.06.53
GRAVE: at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:403)
17-dic-2009 16.06.53
GRAVE: at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:473)
17-dic-2009 16.06.53
GRAVE: at
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:366)
17-dic-2009 16.06.53
GRAVE: at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:431)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.StandardWrapperValve.preInvoke(StandardWrapperValve.java:462)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:139)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:186)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:719)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:657)
17-dic-2009 16.06.53
GRAVE: at
com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:96)
17-dic-2009 16.06.53
GRAVE: at
com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:98)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:187)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:719)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:657)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:651)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1030)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:142)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:719)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:657)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:651)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1030)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:325)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:242)
17-dic-2009 16.06.53
GRAVE: at
com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:180)
17-dic-2009 16.06.53
GRAVE: at
com.sun.grizzly.http.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:633)
17-dic-2009 16.06.53
GRAVE: at
com.sun.grizzly.http.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:570)
17-dic-2009 16.06.53
GRAVE: at
com.sun.grizzly.http.DefaultProcessorTask.process(DefaultProcessorTask.java:827)
17-dic-2009 16.06.53
GRAVE: at
com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:152)
17-dic-2009 16.06.54
GRAVE: at
com.sun.enterprise.v3.services.impl.GlassfishProtocolChain.executeProtocolFilter(GlassfishProtocolChain.java:71)
17-dic-2009 16.06.54
GRAVE: at
com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:103)
17-dic-2009 16.06.54
GRAVE: at
com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:89)
17-dic-2009 16.06.54
GRAVE: at
com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76)
17-dic-2009 16.06.54
GRAVE: at
com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:67)
17-dic-2009 16.06.54
GRAVE: at
com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:56)
17-dic-2009 16.06.54
GRAVE: at
com.sun.grizzly.util.WorkerThreadImpl.processTask(WorkerThreadImpl.java:325)
17-dic-2009 16.06.54
GRAVE: at
com.sun.grizzly.util.WorkerThreadImpl.run(WorkerThreadImpl.java:184)
17-dic-2009 16.06.54
GRAVE: Nested Exception:
17-dic-2009 16.06.54
GRAVE: java.rmi.ServerException: RemoteException occurred in server
thread; nested exception is:
java.rmi.UnmarshalException: error unmarshalling arguments;
nested exception is:
java.net.MalformedURLException: no protocol: and
17-dic-2009 16.06.54
GRAVE: at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
17-dic-2009 16.06.54
GRAVE: at sun.rmi.transport.Transport$1.run(Unknown Source)
17-dic-2009 16.06.54
GRAVE: at java.security.AccessController.doPrivileged(Native Method)
17-dic-2009 16.06.54
GRAVE: at sun.rmi.transport.Transport.serviceCall(Unknown Source)
17-dic-2009 16.06.54
GRAVE: at
sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
17-dic-2009 16.06.54
GRAVE: at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
17-dic-2009 16.06.54
GRAVE: at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source)
17-dic-2009 16.06.54
GRAVE: at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
17-dic-2009 16.06.54
GRAVE: at
java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
17-dic-2009 16.06.54
GRAVE: at java.lang.Thread.run(Unknown Source)
17-dic-2009 16.06.54
GRAVE: at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:255)
17-dic-2009 16.06.54
GRAVE: at
sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233)
17-dic-2009 16.06.54
GRAVE: at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142)
17-dic-2009 16.06.54
GRAVE: at
jade.imtp.rmi.ServiceManagerRMIImpl_Stub.addNode(Unknown Source)
17-dic-2009 16.06.54
GRAVE: at
jade.imtp.rmi.RMIIMTPManager$PlatformManagerAdapter.addNode(RMIIMTPManager.java:547)
17-dic-2009 16.06.54
GRAVE: at
jade.core.ServiceManagerImpl.addNode(ServiceManagerImpl.java:178)
17-dic-2009 16.06.54
GRAVE: at
jade.core.AgentContainerImpl.startNode(AgentContainerImpl.java:422)
17-dic-2009 16.06.54
GRAVE: at
jade.core.AgentContainerImpl.joinPlatform(AgentContainerImpl.java:481)
17-dic-2009 16.06.54
GRAVE: at jade.core.Runtime.createAgentContainer(Runtime.java:116)
17-dic-2009 16.06.54
GRAVE: at
jade.wrapper.gateway.JadeGateway.checkJADE(JadeGateway.java:132)
17-dic-2009 16.06.54
GRAVE: at org.apache.jsp.index_jsp._jspService(index_jsp.java
from :71)
17-dic-2009 16.06.54
GRAVE: at
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:109)
17-dic-2009 16.06.54
GRAVE: at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
17-dic-2009 16.06.54
GRAVE: at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:403)
17-dic-2009 16.06.54
GRAVE: at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:473)
17-dic-2009 16.06.54
GRAVE: at
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:366)
17-dic-2009 16.06.54
GRAVE: at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
17-dic-2009 16.06.54
GRAVE: at
org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:431)
17-dic-2009 16.06.54
GRAVE: at
org.apache.catalina.core.StandardWrapperValve.preInvoke(StandardWrapperValve.java:462)
17-dic-2009 16.06.54
GRAVE: at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:139)
17-dic-2009 16.06.54
GRAVE: at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:186)
17-dic-2009 16.06.54
GRAVE: at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:719)
17-dic-2009 16.06.54
GRAVE: at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:657)
17-dic-2009 16.06.54
GRAVE: at
com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:96)
17-dic-2009 16.06.54
GRAVE: at
com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:98)
17-dic-2009 16.06.54
GRAVE: at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:187)
17-dic-2009 16.06.54
GRAVE: at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:719)
17-dic-2009 16.06.55
GRAVE: at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:657)
17-dic-2009 16.06.55
GRAVE: at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:651)
17-dic-2009 16.06.55
GRAVE: at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1030)
17-dic-2009 16.06.55
GRAVE: at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:142)
17-dic-2009 16.06.55
GRAVE: at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:719)
17-dic-2009 16.06.55
GRAVE: at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:657)
17-dic-2009 16.06.55
GRAVE: at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:651)
17-dic-2009 16.06.55
GRAVE: at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1030)
17-dic-2009 16.06.55
GRAVE: at
org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:325)
17-dic-2009 16.06.55
GRAVE: at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:242)
17-dic-2009 16.06.55
GRAVE: at
com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:180)
17-dic-2009 16.06.55
GRAVE: at
com.sun.grizzly.http.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:633)
17-dic-2009 16.06.55
GRAVE: at
com.sun.grizzly.http.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:570)
17-dic-2009 16.06.55
GRAVE: at
com.sun.grizzly.http.DefaultProcessorTask.process(DefaultProcessorTask.java:827)
17-dic-2009 16.06.55
GRAVE: at
com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:152)
17-dic-2009 16.06.55
GRAVE: at
com.sun.enterprise.v3.services.impl.GlassfishProtocolChain.executeProtocolFilter(GlassfishProtocolChain.java:71)
17-dic-2009 16.06.55
GRAVE: at
com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:103)
17-dic-2009 16.06.55
GRAVE: at
com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:89)
17-dic-2009 16.06.55
GRAVE: at
com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76)
17-dic-2009 16.06.55
GRAVE: at
com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:67)
17-dic-2009 16.06.55
GRAVE: at
com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:56)
17-dic-2009 16.06.55
GRAVE: at
com.sun.grizzly.util.WorkerThreadImpl.processTask(WorkerThreadImpl.java:325)
17-dic-2009 16.06.55
GRAVE: at
com.sun.grizzly.util.WorkerThreadImpl.run(WorkerThreadImpl.java:184)
17-dic-2009 16.06.55
GRAVE: Caused by: java.rmi.UnmarshalException: error unmarshalling
arguments; nested exception is:
java.net.MalformedURLException: no protocol: and
17-dic-2009 16.06.55
GRAVE: at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
17-dic-2009 16.06.55
GRAVE: at sun.rmi.transport.Transport$1.run(Unknown Source)
17-dic-2009 16.06.55
GRAVE: at java.security.AccessController.doPrivileged(Native Method)
17-dic-2009 16.06.55
GRAVE: at sun.rmi.transport.Transport.serviceCall(Unknown Source)
17-dic-2009 16.06.55
GRAVE: at
sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
17-dic-2009 16.06.55
GRAVE: at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
17-dic-2009 16.06.55
GRAVE: at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source)
17-dic-2009 16.06.55
GRAVE: at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
17-dic-2009 16.06.55
GRAVE: at
java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
17-dic-2009 16.06.55
GRAVE: at java.lang.Thread.run(Unknown Source)
17-dic-2009 16.06.55
GRAVE: Caused by: java.net.MalformedURLException: no protocol: and
17-dic-2009 16.06.55
GRAVE: at java.net.URL.<init>(Unknown Source)
17-dic-2009 16.06.55
GRAVE: at java.net.URL.<init>(Unknown Source)
17-dic-2009 16.06.55
GRAVE: at java.net.URL.<init>(Unknown Source)
17-dic-2009 16.06.55
GRAVE: at sun.rmi.server.LoaderHandler.pathToURLs(Unknown Source)
17-dic-2009 16.06.55
GRAVE: at sun.rmi.server.LoaderHandler.loadClass(Unknown Source)
17-dic-2009 16.06.55
GRAVE: at java.rmi.server.RMIClassLoader$2.loadClass(Unknown Source)
17-dic-2009 16.06.55
GRAVE: at java.rmi.server.RMIClassLoader.loadClass(Unknown Source)
17-dic-2009 16.06.55
GRAVE: at
sun.rmi.server.MarshalInputStream.resolveClass(Unknown Source)
17-dic-2009 16.06.56
GRAVE: at java.io.ObjectInputStream.readNonProxyDesc(Unknown Source)
17-dic-2009 16.06.56
GRAVE: at java.io.ObjectInputStream.readClassDesc(Unknown Source)
17-dic-2009 16.06.56
GRAVE: at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
17-dic-2009 16.06.56
GRAVE: at java.io.ObjectInputStream.readObject0(Unknown Source)
17-dic-2009 16.06.56
GRAVE: at java.io.ObjectInputStream.readObject(Unknown Source)
17-dic-2009 16.06.56
GRAVE: at sun.rmi.server.UnicastRef.unmarshalValue(Unknown Source)
17-dic-2009 16.06.56
GRAVE: ... 10 more
17-dic-2009 16.06.56 org.apache.catalina.core.StandardWrapperValve log
GRAVE: StandardWrapperValve[jsp]: PWC1406: Servlet.service() for
servlet jsp threw exception
jade.wrapper.ControllerException: JADE startup failed.
at jade.wrapper.gateway.JadeGateway.checkJADE(JadeGateway.java:134)
at org.apache.jsp.index_jsp._jspService(index_jsp.java from :71)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:109)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:403)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:473)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:366)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at
org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:431)
at
org.apache.catalina.core.StandardWrapperValve.preInvoke(StandardWrapperValve.java:462)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:139)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:186)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:719)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:657)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:96)
at
com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:98)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:187)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:719)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:657)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:651)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1030)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:142)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:719)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:657)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:651)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1030)
at
org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:325)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:242)
at
com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:180)
at
com.sun.grizzly.http.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:633)
at
com.sun.grizzly.http.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:570)
at
com.sun.grizzly.http.DefaultProcessorTask.process(DefaultProcessorTask.java:827)
at
com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:152)
at
com.sun.enterprise.v3.services.impl.GlassfishProtocolChain.executeProtocolFilter(GlassfishProtocolChain.java:71)
at
com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:103)
at
com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:89)
at
com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76)
at
com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:67)
at
com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:56)
at
com.sun.grizzly.util.WorkerThreadImpl.processTask(WorkerThreadImpl.java:325)
at
com.sun.grizzly.util.WorkerThreadImpl.run(WorkerThreadImpl.java:184)

Def. Quota Caire Giovanni <giovanni.caire@...>:

> Hi,
>
> Using the JadeGateway is very simple:
> At servlet/JSP initialization time you should call the init() method
> specifying the properties to connect to the platform (typically main
> container host and port).
> Then whenever you need your servlet/JSP to interact with agents in
> the platform you should call the execute() method. If you use
> behaviours as parameters passed to the execute() method you don't
> need to do anything more.
> Look at the JadeGateway javadoc for details.
>
> Bye,
>
> Giovanni
>
> -----Original Message-----
> From: jade-develop-bounces@...
> [mailto:jade-develop-bounces@...] On Behalf Of
> andrea.brambilla@...
> Sent: mercoledì 16 dicembre 2009 19.08
> To: jade-develop@...
> Subject: [jade-develop] JadeGateway class
>
> Dear JADE experts,
>
> I am learning how to connect a JSP page with JADE agents and I wanted
> to start with a very simple test (just activating the JadeGateway
> through a GateWayAgent). However I keep on getting 'false' from the
> method JadeGateway.isGatewayActive(). I am stuck with this blocking
> issue so I cannot introduce any Servlet-Agent message exchange.
>
> I am using the latest version of JADE, NetBeans IDE 6.7.1 (with
> GlassFish v3 Prelude Domain). The main container is already up and
> running on the standard port 1099 and same host when deploying the jsp.
>
> I attach the index.jsp and the gateway agent I implemented.
>
> Thanks in advance for any help.
>
> Best,
>
> Andrea
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
> Questo messaggio e i suoi allegati sono indirizzati esclusivamente
> alle persone indicate. La diffusione, copia o qualsiasi altra azione
> derivante dalla conoscenza di queste informazioni sono rigorosamente
> vietate. Qualora abbiate ricevuto questo documento per errore siete
> cortesemente pregati di darne immediata comunicazione al mittente e
> di provvedere alla sua distruzione, Grazie.
>
> This e-mail and any attachments is confidential and may contain
> privileged information intended for the addressee(s) only.
> Dissemination, copying, printing or use by anybody else is
> unauthorised. If you are not the intended recipient, please delete
> this message and any attachments and advise the sender by return
> e-mail, Thanks.
>
>

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
_______________________________________________
jade-develop mailing list
jade-develop@...
https://avalon.cselt.it/mailman/listinfo/jade-develop
UNSUBSCRIBE INSTRUCTIONS AT
http://jade.tilab.com/community-mailinglist.htm

From forum: JADE - Dev

Jade with JSP

2009-12-18T03:14:25Z

HI developers ..
I'm having trouble running the examples related to agents and web pages (jsp) .. I'm having problems configuring the directories inside the web server.
If someone can help me thank ...
Thanks ......

Quer conexões de rede mais fácil? Clique e conheça o Windows 7.
_______________________________________________
jade-develop mailing list
jade-develop@...
https://avalon.cselt.it/mailman/listinfo/jade-develop
UNSUBSCRIBE INSTRUCTIONS AT
http://jade.tilab.com/community-mailinglist.htm

From forum: JADE - Dev

inform

2009-12-17T19:24:36Z

thank u

_______________________________________________
jade-develop mailing list
jade-develop@...
https://avalon.cselt.it/mailman/listinfo/jade-develop
UNSUBSCRIBE INSTRUCTIONS AT
http://jade.tilab.com/community-mailinglist.htm

From forum: JADE - Dev

JADE with JSP

2009-12-17T15:00:10Z

Hello, good evening.
I'm trying to run an agent together a web page (jsp). But I can not run configure the settings correctly ....
If someone has the same problem and that I could spend a few tips is of great value ....
Good night and thank you ....

From forum: JADE - Dev

RE: JadeGateway class

2009-12-17T07:24:47Z

Thanks Giovanni for your prompt reply.
I understood how to use the JadeGateway class and you are right, it
looks very simple, however I am afraid I am missing something else.

I tried both:

JadeGateway.init("macgateway.MACGateWayAgent",null);

and

Properties p = new Properties();
p.setProperty("port", "1099");
p.setProperty("host", "PC-42C.aero.polimi.it");
JadeGateway.init("macgateway.MACGateWayAgent",p);

but with no success, please find below the log and in attachment the
correspondent jsp. (I have already checked that the path of GlassFish
v3 Prelude Domain doesn't contain any space)

Thanks for the help,

Andrea

17-dic-2009 16.06.51 jade.core.Runtime beginContainer
INFO: ----------------------------------
This is JADE 3.7 - revision 6154 of 2009/07/01 17:34:15
downloaded in Open Source, under LGPL restrictions,
at http://jade.tilab.com/
----------------------------------------
17-dic-2009 16.06.52 jade.core.BaseService init
INFO: Service jade.core.management.AgentManagement initialized
17-dic-2009 16.06.52 jade.core.BaseService init
INFO: Service jade.core.messaging.Messaging initialized
17-dic-2009 16.06.52 jade.core.BaseService init
INFO: Service jade.core.mobility.AgentMobility initialized
17-dic-2009 16.06.53 jade.core.BaseService init
INFO: Service jade.core.event.Notification initialized
17-dic-2009 16.06.53 jade.core.AgentContainerImpl joinPlatform
GRAVE: Communication failure while joining agent platform: RMI
exception [nested java.rmi.ServerException: RemoteException occurred
in server thread; nested exception is:
java.rmi.UnmarshalException: error unmarshalling arguments;
nested exception is:
java.net.MalformedURLException: no protocol: and]
17-dic-2009 16.06.53
GRAVE: jade.core.IMTPException: RMI exception [nested
java.rmi.ServerException: RemoteException occurred in server thread;
nested exception is:
java.rmi.UnmarshalException: error unmarshalling arguments;
nested exception is:
java.net.MalformedURLException: no protocol: and]
17-dic-2009 16.06.53
GRAVE: at
jade.imtp.rmi.RMIIMTPManager$PlatformManagerAdapter.addNode(RMIIMTPManager.java:550)
17-dic-2009 16.06.53
GRAVE: at
jade.core.ServiceManagerImpl.addNode(ServiceManagerImpl.java:178)
17-dic-2009 16.06.53
GRAVE: at
jade.core.AgentContainerImpl.startNode(AgentContainerImpl.java:422)
17-dic-2009 16.06.53
GRAVE: at
jade.core.AgentContainerImpl.joinPlatform(AgentContainerImpl.java:481)
17-dic-2009 16.06.53
GRAVE: at jade.core.Runtime.createAgentContainer(Runtime.java:116)
17-dic-2009 16.06.53
GRAVE: at
jade.wrapper.gateway.JadeGateway.checkJADE(JadeGateway.java:132)
17-dic-2009 16.06.53
GRAVE: at org.apache.jsp.index_jsp._jspService(index_jsp.java
from :71)
17-dic-2009 16.06.53
GRAVE: at
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:109)
17-dic-2009 16.06.53
GRAVE: at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
17-dic-2009 16.06.53
GRAVE: at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:403)
17-dic-2009 16.06.53
GRAVE: at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:473)
17-dic-2009 16.06.53
GRAVE: at
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:366)
17-dic-2009 16.06.53
GRAVE: at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:431)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.StandardWrapperValve.preInvoke(StandardWrapperValve.java:462)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:139)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:186)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:719)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:657)
17-dic-2009 16.06.53
GRAVE: at
com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:96)
17-dic-2009 16.06.53
GRAVE: at
com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:98)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:187)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:719)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:657)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:651)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1030)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:142)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:719)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:657)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:651)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1030)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:325)
17-dic-2009 16.06.53
GRAVE: at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:242)
17-dic-2009 16.06.53
GRAVE: at
com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:180)
17-dic-2009 16.06.53
GRAVE: at
com.sun.grizzly.http.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:633)
17-dic-2009 16.06.53
GRAVE: at
com.sun.grizzly.http.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:570)
17-dic-2009 16.06.53
GRAVE: at
com.sun.grizzly.http.DefaultProcessorTask.process(DefaultProcessorTask.java:827)
17-dic-2009 16.06.53
GRAVE: at
com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:152)
17-dic-2009 16.06.54
GRAVE: at
com.sun.enterprise.v3.services.impl.GlassfishProtocolChain.executeProtocolFilter(GlassfishProtocolChain.java:71)
17-dic-2009 16.06.54
GRAVE: at
com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:103)
17-dic-2009 16.06.54
GRAVE: at
com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:89)
17-dic-2009 16.06.54
GRAVE: at
com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76)
17-dic-2009 16.06.54
GRAVE: at
com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:67)
17-dic-2009 16.06.54
GRAVE: at
com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:56)
17-dic-2009 16.06.54
GRAVE: at
com.sun.grizzly.util.WorkerThreadImpl.processTask(WorkerThreadImpl.java:325)
17-dic-2009 16.06.54
GRAVE: at
com.sun.grizzly.util.WorkerThreadImpl.run(WorkerThreadImpl.java:184)
17-dic-2009 16.06.54
GRAVE: Nested Exception:
17-dic-2009 16.06.54
GRAVE: java.rmi.ServerException: RemoteException occurred in server
thread; nested exception is:
java.rmi.UnmarshalException: error unmarshalling arguments;
nested exception is:
java.net.MalformedURLException: no protocol: and
17-dic-2009 16.06.54
GRAVE: at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
17-dic-2009 16.06.54
GRAVE: at sun.rmi.transport.Transport$1.run(Unknown Source)
17-dic-2009 16.06.54
GRAVE: at java.security.AccessController.doPrivileged(Native Method)
17-dic-2009 16.06.54
GRAVE: at sun.rmi.transport.Transport.serviceCall(Unknown Source)
17-dic-2009 16.06.54
GRAVE: at
sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
17-dic-2009 16.06.54
GRAVE: at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
17-dic-2009 16.06.54
GRAVE: at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source)
17-dic-2009 16.06.54
GRAVE: at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
17-dic-2009 16.06.54
GRAVE: at
java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
17-dic-2009 16.06.54
GRAVE: at java.lang.Thread.run(Unknown Source)
17-dic-2009 16.06.54
GRAVE: at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:255)
17-dic-2009 16.06.54
GRAVE: at
sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233)
17-dic-2009 16.06.54
GRAVE: at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142)
17-dic-2009 16.06.54
GRAVE: at
jade.imtp.rmi.ServiceManagerRMIImpl_Stub.addNode(Unknown Source)
17-dic-2009 16.06.54
GRAVE: at
jade.imtp.rmi.RMIIMTPManager$PlatformManagerAdapter.addNode(RMIIMTPManager.java:547)
17-dic-2009 16.06.54
GRAVE: at
jade.core.ServiceManagerImpl.addNode(ServiceManagerImpl.java:178)
17-dic-2009 16.06.54
GRAVE: at
jade.core.AgentContainerImpl.startNode(AgentContainerImpl.java:422)
17-dic-2009 16.06.54
GRAVE: at
jade.core.AgentContainerImpl.joinPlatform(AgentContainerImpl.java:481)
17-dic-2009 16.06.54
GRAVE: at jade.core.Runtime.createAgentContainer(Runtime.java:116)
17-dic-2009 16.06.54
GRAVE: at
jade.wrapper.gateway.JadeGateway.checkJADE(JadeGateway.java:132)
17-dic-2009 16.06.54
GRAVE: at org.apache.jsp.index_jsp._jspService(index_jsp.java
from :71)
17-dic-2009 16.06.54
GRAVE: at
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:109)
17-dic-2009 16.06.54
GRAVE: at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
17-dic-2009 16.06.54
GRAVE: at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:403)
17-dic-2009 16.06.54
GRAVE: at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:473)
17-dic-2009 16.06.54
GRAVE: at
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:366)
17-dic-2009 16.06.54
GRAVE: at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
17-dic-2009 16.06.54
GRAVE: at
org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:431)
17-dic-2009 16.06.54
GRAVE: at
org.apache.catalina.core.StandardWrapperValve.preInvoke(StandardWrapperValve.java:462)
17-dic-2009 16.06.54
GRAVE: at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:139)
17-dic-2009 16.06.54
GRAVE: at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:186)
17-dic-2009 16.06.54
GRAVE: at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:719)
17-dic-2009 16.06.54
GRAVE: at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:657)
17-dic-2009 16.06.54
GRAVE: at
com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:96)
17-dic-2009 16.06.54
GRAVE: at
com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:98)
17-dic-2009 16.06.54
GRAVE: at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:187)
17-dic-2009 16.06.54
GRAVE: at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:719)
17-dic-2009 16.06.55
GRAVE: at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:657)
17-dic-2009 16.06.55
GRAVE: at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:651)
17-dic-2009 16.06.55
GRAVE: at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1030)
17-dic-2009 16.06.55
GRAVE: at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:142)
17-dic-2009 16.06.55
GRAVE: at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:719)
17-dic-2009 16.06.55
GRAVE: at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:657)
17-dic-2009 16.06.55
GRAVE: at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:651)
17-dic-2009 16.06.55
GRAVE: at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1030)
17-dic-2009 16.06.55
GRAVE: at
org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:325)
17-dic-2009 16.06.55
GRAVE: at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:242)
17-dic-2009 16.06.55
GRAVE: at
com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:180)
17-dic-2009 16.06.55
GRAVE: at
com.sun.grizzly.http.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:633)
17-dic-2009 16.06.55
GRAVE: at
com.sun.grizzly.http.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:570)
17-dic-2009 16.06.55
GRAVE: at
com.sun.grizzly.http.DefaultProcessorTask.process(DefaultProcessorTask.java:827)
17-dic-2009 16.06.55
GRAVE: at
com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:152)
17-dic-2009 16.06.55
GRAVE: at
com.sun.enterprise.v3.services.impl.GlassfishProtocolChain.executeProtocolFilter(GlassfishProtocolChain.java:71)
17-dic-2009 16.06.55
GRAVE: at
com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:103)
17-dic-2009 16.06.55
GRAVE: at
com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:89)
17-dic-2009 16.06.55
GRAVE: at
com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76)
17-dic-2009 16.06.55
GRAVE: at
com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:67)
17-dic-2009 16.06.55
GRAVE: at
com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:56)
17-dic-2009 16.06.55
GRAVE: at
com.sun.grizzly.util.WorkerThreadImpl.processTask(WorkerThreadImpl.java:325)
17-dic-2009 16.06.55
GRAVE: at
com.sun.grizzly.util.WorkerThreadImpl.run(WorkerThreadImpl.java:184)
17-dic-2009 16.06.55
GRAVE: Caused by: java.rmi.UnmarshalException: error unmarshalling
arguments; nested exception is:
java.net.MalformedURLException: no protocol: and
17-dic-2009 16.06.55
GRAVE: at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
17-dic-2009 16.06.55
GRAVE: at sun.rmi.transport.Transport$1.run(Unknown Source)
17-dic-2009 16.06.55
GRAVE: at java.security.AccessController.doPrivileged(Native Method)
17-dic-2009 16.06.55
GRAVE: at sun.rmi.transport.Transport.serviceCall(Unknown Source)
17-dic-2009 16.06.55
GRAVE: at
sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
17-dic-2009 16.06.55
GRAVE: at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
17-dic-2009 16.06.55
GRAVE: at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source)
17-dic-2009 16.06.55
GRAVE: at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
17-dic-2009 16.06.55
GRAVE: at
java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
17-dic-2009 16.06.55
GRAVE: at java.lang.Thread.run(Unknown Source)
17-dic-2009 16.06.55
GRAVE: Caused by: java.net.MalformedURLException: no protocol: and
17-dic-2009 16.06.55
GRAVE: at java.net.URL.<init>(Unknown Source)
17-dic-2009 16.06.55
GRAVE: at java.net.URL.<init>(Unknown Source)
17-dic-2009 16.06.55
GRAVE: at java.net.URL.<init>(Unknown Source)
17-dic-2009 16.06.55
GRAVE: at sun.rmi.server.LoaderHandler.pathToURLs(Unknown Source)
17-dic-2009 16.06.55
GRAVE: at sun.rmi.server.LoaderHandler.loadClass(Unknown Source)
17-dic-2009 16.06.55
GRAVE: at java.rmi.server.RMIClassLoader$2.loadClass(Unknown Source)
17-dic-2009 16.06.55
GRAVE: at java.rmi.server.RMIClassLoader.loadClass(Unknown Source)
17-dic-2009 16.06.55
GRAVE: at
sun.rmi.server.MarshalInputStream.resolveClass(Unknown Source)
17-dic-2009 16.06.56
GRAVE: at java.io.ObjectInputStream.readNonProxyDesc(Unknown Source)
17-dic-2009 16.06.56
GRAVE: at java.io.ObjectInputStream.readClassDesc(Unknown Source)
17-dic-2009 16.06.56
GRAVE: at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
17-dic-2009 16.06.56
GRAVE: at java.io.ObjectInputStream.readObject0(Unknown Source)
17-dic-2009 16.06.56
GRAVE: at java.io.ObjectInputStream.readObject(Unknown Source)
17-dic-2009 16.06.56
GRAVE: at sun.rmi.server.UnicastRef.unmarshalValue(Unknown Source)
17-dic-2009 16.06.56
GRAVE: ... 10 more
17-dic-2009 16.06.56 org.apache.catalina.core.StandardWrapperValve log
GRAVE: StandardWrapperValve[jsp]: PWC1406: Servlet.service() for
servlet jsp threw exception
jade.wrapper.ControllerException: JADE startup failed.
at jade.wrapper.gateway.JadeGateway.checkJADE(JadeGateway.java:134)
at org.apache.jsp.index_jsp._jspService(index_jsp.java from :71)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:109)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:403)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:473)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:366)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at
org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:431)
at
org.apache.catalina.core.StandardWrapperValve.preInvoke(StandardWrapperValve.java:462)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:139)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:186)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:719)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:657)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:96)
at
com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:98)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:187)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:719)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:657)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:651)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1030)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:142)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:719)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:657)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:651)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1030)
at
org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:325)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:242)
at
com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:180)
at
com.sun.grizzly.http.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:633)
at
com.sun.grizzly.http.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:570)
at
com.sun.grizzly.http.DefaultProcessorTask.process(DefaultProcessorTask.java:827)
at
com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:152)
at
com.sun.enterprise.v3.services.impl.GlassfishProtocolChain.executeProtocolFilter(GlassfishProtocolChain.java:71)
at
com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:103)
at
com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:89)
at
com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76)
at
com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:67)
at
com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:56)
at
com.sun.grizzly.util.WorkerThreadImpl.processTask(WorkerThreadImpl.java:325)
at
com.sun.grizzly.util.WorkerThreadImpl.run(WorkerThreadImpl.java:184)

Def. Quota Caire Giovanni <giovanni.caire@...>:

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

_______________________________________________
jade-develop mailing list
jade-develop@...
https://avalon.cselt.it/mailman/listinfo/jade-develop
UNSUBSCRIBE INSTRUCTIONS AT
http://jade.tilab.com/community-mailinglist.htm

index.jsp (767 bytes) Download Attachment

From forum: JADE - Dev

R: Debian command line arguments passing

2009-12-17T03:15:58Z

Under linux, the simplest option is to quote the whole list of agent specifiers:

java -cp jade.jar jade.Boot "hello:HelloWorldAgent(arg1,arg2);anotherAgent:HelloWorldAgent(arg3,arg4)"

Otherwise, you can simply escape parentheses and semicolons with backslashes:

java -cp jade.jar jade.Boot hello:HelloWorldAgent$arg1,arg2)\;anotherAgent:HelloWorldAgent\(arg3,arg4$

Note that, in the latter case, you cannot use spaces in the list, unless you escape them too.

Cheers

Paolo

Da: jade-develop-bounces@... [mailto:jade-develop-bounces@...] Per conto di Wae Chan
Inviato: martedì 15 dicembre 2009 15.32
A: jade-develop@...
Oggetto: [jade-develop] Debian command line arguments passing

Hi all,

I need some help here, i dont know how to pass arguments in the command line in Debian, more specifically, i want to do this "Windows command" in Debian:

java jade.Boot hello:HelloWorldAgent(arg1 arg2)

Ive tried [arg1 arg2]; "arg1 arg2"... but none of them works! Thanks in advance!!!

From forum: JADE - Dev

RE: JadeGateway class

2009-12-17T02:26:05Z

Hi,

Using the JadeGateway is very simple:
At servlet/JSP initialization time you should call the init() method specifying the properties to connect to the platform (typically main container host and port).
Then whenever you need your servlet/JSP to interact with agents in the platform you should call the execute() method. If you use behaviours as parameters passed to the execute() method you don't need to do anything more.
Look at the JadeGateway javadoc for details.

Bye,

Giovanni

-----Original Message-----
From: jade-develop-bounces@... [mailto:jade-develop-bounces@...] On Behalf Of andrea.brambilla@...
Sent: mercoledì 16 dicembre 2009 19.08
To: jade-develop@...
Subject: [jade-develop] JadeGateway class

Dear JADE experts,

I am learning how to connect a JSP page with JADE agents and I wanted
to start with a very simple test (just activating the JadeGateway
through a GateWayAgent). However I keep on getting 'false' from the
method JadeGateway.isGatewayActive(). I am stuck with this blocking
issue so I cannot introduce any Servlet-Agent message exchange.

I am using the latest version of JADE, NetBeans IDE 6.7.1 (with
GlassFish v3 Prelude Domain). The main container is already up and
running on the standard port 1099 and same host when deploying the jsp.

I attach the index.jsp and the gateway agent I implemented.

Thanks in advance for any help.

Best,

Andrea

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

_______________________________________________
jade-develop mailing list
jade-develop@...
https://avalon.cselt.it/mailman/listinfo/jade-develop
UNSUBSCRIBE INSTRUCTIONS AT
http://jade.tilab.com/community-mailinglist.htm

From forum: JADE - Dev

RE: Starting sniffer when jade is run

2009-12-17T02:12:30Z

Hi,

Unfortunately I don't think the sniffer can be used, as it is, to do exactly what you need. However you could try the JavaSniffer add-on. This is a tool that can be connected to a platform and that provides functionality similar to those of the sniffer agent and even more sophisticated. Since it is an external tool and not an agent of course it survives to the shutdown of the platform --> This should solve your problem.

Bye,

Giovanni

-----Original Message-----
From: Hussain, Adil [mailto:adil.hussain02@...]
Sent: martedì 15 dicembre 2009 20.36
To: Caire Giovanni; jade-develop@...
Subject: RE: Starting sniffer when jade is run

Hi Caire (and anyone else that can help),

The sniffer.properties file does the job exactly (i.e. specifying agents to be sniffed that don't yet exist). Thanks so much.

As for saving the sniffed messages in a file, the "WriteMessageList" button provided with Sniffer does do the job. However, thing is, my desired application is to run without a GUI. Jade is to be loaded with no gui and a number of agents (included the sniffer) that run for a certain amount of time and then the entire agent platform is to be shut down (automatically).

Any idea (anyone) how I could save/retrieve all the messages sniffed (without any interaction with a GUI)? Could I perhaps somehow send a message to the Sniffer agent before it is killed to save the sniffed messages in a file? Or perhaps somehow (if not a bad idea!) extend the Sniffer agent class (the takedown method) to save the sniffed messages when killed?

Regards,
Adil Hussain
_______________________________________________
jade-develop mailing list
jade-develop@...
https://avalon.cselt.it/mailman/listinfo/jade-develop
UNSUBSCRIBE INSTRUCTIONS AT
http://jade.tilab.com/community-mailinglist.htm

From forum: JADE - Dev

Fwd: confirm 6acd5fb48d1baf05b3f27314972091f3bf8459ca

2009-12-16T21:56:07Z

---------- Forwarded message ----------
From: <jade-develop-request@...>
Date: 2009/12/17
Subject: confirm 6acd5fb48d1baf05b3f27314972091f3bf8459ca
To: grupodms@...

Mailing list subscription confirmation notice for mailing list
jade-develop

We have received a request for subscription of your email address,
"grupodms@...", to the jade-develop@... mailing
list. To confirm that you want to be added to this mailing list,
simply reply to this message, keeping the Subject: header intact. Or
visit this web page:

https://avalon.cselt.it/mailman/confirm/jade-develop/6acd5fb48d1baf05b3f27314972091f3bf8459ca

Or include the following line -- and only the following line -- in a
message to jade-develop-request@...:

confirm 6acd5fb48d1baf05b3f27314972091f3bf8459ca

Note that simply sending a `reply' to this message should work from
most mail readers, since that usually leaves the Subject: line in the
right form (additional "Re:" text in the Subject: is okay).

If you do not wish to be subscribed to this list, please simply
disregard this message. If you think you are being maliciously
subscribed to the list, or have any other questions, send them to
jade-develop-owner@....

--
GRUPO DMS - IEEE UPLA
porque el conocimiento no tiene limites - 2009

_______________________________________________
jade-develop mailing list
jade-develop@...
https://avalon.cselt.it/mailman/listinfo/jade-develop
UNSUBSCRIBE INSTRUCTIONS AT
http://jade.tilab.com/community-mailinglist.htm

From forum: JADE - Dev

JadeGateway class

2009-12-16T10:08:10Z

Dear JADE experts,

I am learning how to connect a JSP page with JADE agents and I wanted
to start with a very simple test (just activating the JadeGateway
through a GateWayAgent). However I keep on getting 'false' from the
method JadeGateway.isGatewayActive(). I am stuck with this blocking
issue so I cannot introduce any Servlet-Agent message exchange.

I am using the latest version of JADE, NetBeans IDE 6.7.1 (with
GlassFish v3 Prelude Domain). The main container is already up and
running on the standard port 1099 and same host when deploying the jsp.

I attach the index.jsp and the gateway agent I implemented.

Thanks in advance for any help.

Best,

Andrea

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

package macgateway;

import jade.core.AID;
import jade.core.behaviours.CyclicBehaviour;
import jade.lang.acl.ACLMessage;
import jade.wrapper.gateway.GatewayAgent;

public class MACGateWayAgent extends GatewayAgent{

private BlackBoardBean board = null;

protected void setup(){

super.setup();

System.out.println("GateWay Agent is up and running.");

addBehaviour(new CyclicBehaviour(this){

public void action(){

ACLMessage msg = receive();

if((msg!= null) && (board!=null)){

board.setMessageContent(msg.getContent());
releaseCommand(board);
}else block();
}

});

}

protected void processCommand(java.lang.Object obj){

if(obj instanceof BlackBoardBean){

board = (BlackBoardBean)obj;

ACLMessage msg = new ACLMessage(ACLMessage.REQUEST);
msg.addReceiver(new AID(board.getReceiver(), AID.ISLOCALNAME));
msg.setContent(board.getMessageContent());
send(msg);

}

}

}

_______________________________________________
jade-develop mailing list
jade-develop@...
https://avalon.cselt.it/mailman/listinfo/jade-develop
UNSUBSCRIBE INSTRUCTIONS AT
http://jade.tilab.com/community-mailinglist.htm

index.jsp (549 bytes) Download Attachment

From forum: JADE - Dev

RE: Re: jade-develop Digest, Vol 83, Issue 11

2009-12-16T08:10:33Z

Hi,

Jade is fully (and solely) based on Java à If it is possible to create a Chrome plug-in that uses java code then it should also be possible to create a plug-in that runs one or more Jade agents. If this is the case I would suggest using JADE-LEAP and in particular the split container execution mode (see the LEAP user Guide for details) that does not require opening server sockets and other stuff that may be prevented by the Chrome plug-in execution model.

Bye,

Giovanni

From: jade-develop-bounces@... [mailto:jade-develop-bounces@...] On Behalf Of bala krishnan
Sent: martedì 15 dicembre 2009 6.01
To: jade-develop@...
Subject: [jade-develop] Re: jade-develop Digest, Vol 83, Issue 11

From forum: JADE - Dev

Problem with wsdl addon

2009-12-16T04:13:41Z

Hello,

I am using the wsdl plugin, and when I call a specific ws, I get the following exception:
jade.content.onto.OntologyException: No schema found for class [Ljava.lang.String;

which is thrown in the method:
convertObjToAbs of DynamicClient class

and specifically at line:
absObject = typeOnto.fromObject(value);

Can anybody help me solve this problem?

From forum: Jade Plugins Users

Re: search in the interenet

2009-12-16T02:56:37Z

JADE agents are in Java
there's lots of Java libraries for accessing Web APIs
ask/search e.g. at the fora related to Amazon Web API for details

hth,
Maciej

h.al6air . pisze:

> so basically jade should be there (on a host) where an agent can jump
> to? it is not possible to go anywhere in the interent..ok.. this is a
> differnt story from the API.
> sorry if i would bother you with one more question or actually an
> example of any agent using any API of website like expedia or amazon.
> what methods of packages will the agent use in order to use what's in
> the API
>
> thanks in advance
> hal6air
>
> On Wed, Dec 16, 2009 at 2:00 PM, Maciej Gawinecki <mgawinecki@...
> <mailto:mgawinecki@...>> wrote:
>
>
>
> h.al6air . pisze:
>
> for example: you want to buy a book from online. the agent will
> go get you offers (proposals) of the book..but in this senario
> am assuming that the seller party, doesn't have an agent.
>
>
> This scenario is not realistic unless you assume that that the
> hosting machine of seller provide agent-platform (e.g. JADE) for
> your visiting agent. Why not simply request data from the seller
> insteading of sending the code/state of a mobile agent over the net?
>
> is it possible that an agent go get information from the
> interent, say google, and get back with information, not
> necessarly an offer, a link to amazon.com <http://amazon.com/>
> <http://amazon.com <http://amazon.com/>> with the book title
> there is fine.
>
>
> you can realize this scenario without JADE agent at all. If you look
> how to get information from Amazon, look for some screen-scraping
> techniques or Web API of Amazon that will let you access Amazon's
> data in a structured way.
>
> HTH,
> Maciej
>
> hal6air
>
> On Wed, Dec 16, 2009 at 1:08 PM, Maciej Gawinecki
> <mgawinecki@... <mailto:mgawinecki@...>
> <mailto:mgawinecki@... <mailto:mgawinecki@...>>> wrote:
>
> what is the motivation/reason for such scenario?
>
> what would agent do it?
>
> Best,
> Maciej
>
> h.al6air . pisze:
>
> Hi,
> I want to create an agent that goes in the interent and
> search
> for a keyword and come back with links (for example). Is this
> possible? I have been searching for an example of the
> same but
> no luck! =/
> any suggestion?
> thanks in advance
> hal6air
>
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> jade-develop mailing list
> jade-develop@...
> <mailto:jade-develop@...>
> <mailto:jade-develop@...
> <mailto:jade-develop@...>>
>
> https://avalon.cselt.it/mailman/listinfo/jade-develop
> UNSUBSCRIBE INSTRUCTIONS AT
> http://jade.tilab.com/community-mailinglist.htm
>
>
>
>

From forum: JADE - Dev

RE: Help for beginner

2009-12-16T02:40:39Z

Hi,

Can you be more specific please? What is the exact error you get. Do you see any stack trace printed on the standard output. In case can you provide it.
Bye,

Giovanni

-----Original Message-----
From: jade-develop-bounces@... [mailto:jade-develop-bounces@...] On Behalf Of Andrius Jurgutis
Sent: martedì 15 dicembre 2009 8.49
To: jade-develop@...
Subject: [jade-develop] Help for beginner

Hello everyone,

I'am Jade beginner, so I need help.
I do not understand, how to configuring MTPs from the graphical
management console. I completed the activities as described in
"Select a container from the GUI, click the right button of the
mouse and a popup menu appears. Choose the Install a new MTP option
and a dialog will be shown. Here the following information can be set:

* the container to install the new MTP on (if different from the
selected one)
* the fully qualified name of the class implementing the
jade.mtp.MTP interface, and (if it is supported by the chosen protocol)
* optionally the transport address that will be used to contact
the new MTP.

For example, in order to install a new HTTP endpoint on the default
local port by using the HTTP MTP, one should write
jamr.jademtp.http.MessageTransportProtocol as the class name and
nothing as the address. In order to use the transport on a different
port or a particular interface of the current machine you could
provide as the transport address a standard http url:
http://mymachinename.org:8978 ( where 8978 would be the port number on
which the transport will bind ).

Choosing Uninstall an MTP shows a dialog where the user can select
from a list one of the currently installed MTPs and remove it from the
platform. "
but I get an error message, I do not understand what I am doing wrong ?

Thanks in advance

Andrius

_______________________________________________
jade-develop mailing list
jade-develop@...
https://avalon.cselt.it/mailman/listinfo/jade-develop
UNSUBSCRIBE INSTRUCTIONS AT
http://jade.tilab.com/community-mailinglist.htm
_______________________________________________
jade-develop mailing list
jade-develop@...
https://avalon.cselt.it/mailman/listinfo/jade-develop
UNSUBSCRIBE INSTRUCTIONS AT
http://jade.tilab.com/community-mailinglist.htm

From forum: JADE - Dev

Re: search in the interenet

2009-12-16T02:00:53Z

h.al6air . pisze:
> for example: you want to buy a book from online. the agent will go get
> you offers (proposals) of the book..but in this senario am assuming that
> the seller party, doesn't have an agent.

This scenario is not realistic unless you assume that that the hosting
machine of seller provide agent-platform (e.g. JADE) for your visiting
agent. Why not simply request data from the seller insteading of sending
the code/state of a mobile agent over the net?

> is it possible that an agent go get information from the interent, say
> google, and get back with information, not necessarly an offer, a link
> to amazon.com <http://amazon.com> with the book title there is fine.

you can realize this scenario without JADE agent at all. If you look how to
get information from Amazon, look for some screen-scraping techniques or
Web API of Amazon that will let you access Amazon's data in a structured way.

HTH,
Maciej

>
> hal6air
> On Wed, Dec 16, 2009 at 1:08 PM, Maciej Gawinecki <mgawinecki@...
> <mailto:mgawinecki@...>> wrote:
>
> what is the motivation/reason for such scenario?
>
> what would agent do it?
>
> Best,
> Maciej
>
> h.al6air . pisze:
>
> Hi,
> I want to create an agent that goes in the interent and search
> for a keyword and come back with links (for example). Is this
> possible? I have been searching for an example of the same but
> no luck! =/
> any suggestion?
> thanks in advance
> hal6air
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> jade-develop mailing list
> jade-develop@... <mailto:jade-develop@...>
> https://avalon.cselt.it/mailman/listinfo/jade-develop
> UNSUBSCRIBE INSTRUCTIONS AT
> http://jade.tilab.com/community-mailinglist.htm
>

From forum: JADE - Dev

Re: search in the interenet

2009-12-16T01:08:33Z

what is the motivation/reason for such scenario?

what would agent do it?

Best,
Maciej

h.al6air . pisze:

> Hi,
> I want to create an agent that goes in the interent and search for a
> keyword and come back with links (for example). Is this possible? I have
> been searching for an example of the same but no luck! =/
>
> any suggestion?
>
> thanks in advance
> hal6air
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> jade-develop mailing list
> jade-develop@...
> https://avalon.cselt.it/mailman/listinfo/jade-develop
> UNSUBSCRIBE INSTRUCTIONS AT
> http://jade.tilab.com/community-mailinglist.htm

From forum: JADE - Dev

search in the interenet

2009-12-16T00:50:28Z

Hi,

I want to create an agent that goes in the interent and search for a keyword and come back with links (for example). Is this possible? I have been searching for an example of the same but no luck! =/

any suggestion?

thanks in advance

hal6air

From forum: JADE - Dev

Re: RE: JADE-LEAP Memory Leak?

2009-12-15T19:53:26Z

FWIW, we've been running regular JADE (not JADE Leap) 24/7 as a service
that starts up when our machines boot.

It's been a long time since we did any testing but we had similar
concerns about memory growth and did some profiling to make sure that
our agents were taking too many resources from what the computers were
supposed to be doing. We noticed that memory would vary typically
between 30-50 MB (similar to what Caire reports below) but it would be
cyclic, growing a little, then shrinking back down in a timeframe that
coincided with Java garbage collection events. Obviously I can't really
know for sure that this is your problem, but my guess is that your
observed memory growth is just the Java memory management system in
operation. I'd conjecture that if you let it keep running, you'll see it
grow and shrink within some modest bounds. Obviously though, if it just
grows and grows and never shrinks back, then you do have a problem.

- Scott

On Tue, 2009-12-15 at 15:39 +0000, C.P.Bridges@... wrote:

> This is exactly it but using the arguments and creating just 1 agent. If you see the graph, the memory is still going up - albeit very slowly.
>
> I'm talking KB/ byte accuracy here.
>
> Cheers, Chris
>
> -----Original Message-----
> From: Caire Giovanni [mailto:giovanni.caire@...]
> Sent: 15 December 2009 09:21
> To: Bridges CP Mr (PG/R - Electronic Eng); jade-develop@...
> Subject: RE: JADE-LEAP Memory Leak?
>
> Hi,
>
> As far as I have understood the test you are performing should be similar to the following one:
>
> public class Test {
>
> public static final void main(String[] args) {
> Properties pp = new Properties();
> pp.setProperty("nomtp", "true");
> ProfileImpl p = new ProfileImpl(pp);
> long n = 0;
> try {
> ContainerController cc = Runtime.instance().createMainContainer(p);
> while (true) {
> AgentController ac = cc.createNewAgent("Test-"+n, "examples.hello.HelloWorldAgent", null);
> ac.start();
> n++;
> }
> }
> catch (Throwable t) {
> System.err.println("Error creating agent "+n);
> t.printStackTrace();
> }
> }
> }
>
> I run the above test up to the creation of 1.500.000 agents and I got no memory increment: the memory consumption ranges from ~20 MB up to 50MB.
>
> Is your test different with respect to mine?
>
> Bye,
>
> Giovanni
> -----Original Message-----
> From: C.P.Bridges@... [mailto:C.P.Bridges@...]
> Sent: lunedì 14 dicembre 2009 10.51
> To: Caire Giovanni; jade-develop@...
> Subject: RE: JADE-LEAP Memory Leak?
>
> Hi Giovanni,
>
> The test literally just loads up the HelloWorld agent and terminates once that has loaded. The method probe I use tracks the amount of memory used as in my previous figure to each method invoked. You'll see that the memory used keeps on rising - so when does it stop?
>
> Or after which classes/methods does the memory level off to stability?
>
> Cheers, Chris
>
> -----Original Message-----
> From: Caire Giovanni [mailto:giovanni.caire@...]
> Sent: 09 December 2009 16:48
> To: Bridges CP Mr (PG/R - Electronic Eng); jade-develop@...
> Subject: RE: JADE-LEAP Memory Leak?
>
> Hi,
>
> Can you please clarify what your test actually does?
> Note that we have mission critical systems continuously running in the fields with hundreds of agents and we never experienced memory-leak problems.
>
> Bye,
>
> Giovanni
>
> -----Original Message-----
> From: C.P.Bridges@... [mailto:C.P.Bridges@...]
> Sent: martedì 8 dicembre 2009 15.03
> To: jade-develop@...; Caire Giovanni
> Subject: JADE-LEAP Memory Leak?
>
> Hi Giovanni, JADE'ers,
>
> I've been working with JADE-LEAP (and other agent middleware) for a
> while now and have noticed that during experimentation, the memory
> consumption keeps increasing. My setup is just startup a HelloWorld
> agent in JRE 1.4 (or less for JADE-LEAP for CDC).
>
> Can you please tell me where I'd find this recursive code? Or some
> ideas?
>
> The attachment is some published results on each middleware and the
> memory used vs methods used (to fully load HelloWorld agent).
>
> Kind Regards, Chris
>
> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.
>
> This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.
>
>
> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.
>
> This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.
>
> _______________________________________________
> jade-develop mailing list
> jade-develop@...
> https://avalon.cselt.it/mailman/listinfo/jade-develop
> UNSUBSCRIBE INSTRUCTIONS AT
> http://jade.tilab.com/community-mailinglist.htm

From forum: JADE - Dev

RE: Starting sniffer when jade is run

2009-12-15T11:35:45Z

Hi Caire (and anyone else that can help),

The sniffer.properties file does the job exactly (i.e. specifying agents to be sniffed that don't yet exist). Thanks so much.

As for saving the sniffed messages in a file, the “WriteMessageList” button provided with Sniffer does do the job. However, thing is, my desired application is to run without a GUI. Jade is to be loaded with no gui and a number of agents (included the sniffer) that run for a certain amount of time and then the entire agent platform is to be shut down (automatically).

Any idea (anyone) how I could save/retrieve all the messages sniffed (without any interaction with a GUI)? Could I perhaps somehow send a message to the Sniffer agent before it is killed to save the sniffed messages in a file? Or perhaps somehow (if not a bad idea!) extend the Sniffer agent class (the takedown method) to save the sniffed messages when killed?

Regards,
Adil Hussain_______________________________________________
jade-develop mailing list
jade-develop@...
https://avalon.cselt.it/mailman/listinfo/jade-develop
UNSUBSCRIBE INSTRUCTIONS AT
http://jade.tilab.com/community-mailinglist.htm

From forum: JADE - Dev

RE: JADE-LEAP Memory Leak?

2009-12-15T07:39:05Z

This is exactly it but using the arguments and creating just 1 agent. If you see the graph, the memory is still going up - albeit very slowly.

I'm talking KB/ byte accuracy here.

Cheers, Chris

-----Original Message-----
From: Caire Giovanni [mailto:giovanni.caire@...]
Sent: 15 December 2009 09:21
To: Bridges CP Mr (PG/R - Electronic Eng); jade-develop@...
Subject: RE: JADE-LEAP Memory Leak?

Hi,

As far as I have understood the test you are performing should be similar to the following one:

public class Test {

public static final void main(String[] args) {
Properties pp = new Properties();
pp.setProperty("nomtp", "true");
ProfileImpl p = new ProfileImpl(pp);
long n = 0;
try {
ContainerController cc = Runtime.instance().createMainContainer(p);
while (true) {
AgentController ac = cc.createNewAgent("Test-"+n, "examples.hello.HelloWorldAgent", null);
ac.start();
n++;
}
}
catch (Throwable t) {
System.err.println("Error creating agent "+n);
t.printStackTrace();
}
}
}

I run the above test up to the creation of 1.500.000 agents and I got no memory increment: the memory consumption ranges from ~20 MB up to 50MB.

Is your test different with respect to mine?

Bye,

Giovanni
-----Original Message-----
From: C.P.Bridges@... [mailto:C.P.Bridges@...]
Sent: lunedì 14 dicembre 2009 10.51
To: Caire Giovanni; jade-develop@...
Subject: RE: JADE-LEAP Memory Leak?

Hi Giovanni,

The test literally just loads up the HelloWorld agent and terminates once that has loaded. The method probe I use tracks the amount of memory used as in my previous figure to each method invoked. You'll see that the memory used keeps on rising - so when does it stop?

Or after which classes/methods does the memory level off to stability?

Cheers, Chris

-----Original Message-----
From: Caire Giovanni [mailto:giovanni.caire@...]
Sent: 09 December 2009 16:48
To: Bridges CP Mr (PG/R - Electronic Eng); jade-develop@...
Subject: RE: JADE-LEAP Memory Leak?

Hi,

Can you please clarify what your test actually does?
Note that we have mission critical systems continuously running in the fields with hundreds of agents and we never experienced memory-leak problems.

Bye,

Giovanni

-----Original Message-----
From: C.P.Bridges@... [mailto:C.P.Bridges@...]
Sent: martedì 8 dicembre 2009 15.03
To: jade-develop@...; Caire Giovanni
Subject: JADE-LEAP Memory Leak?

Hi Giovanni, JADE'ers,

I've been working with JADE-LEAP (and other agent middleware) for a
while now and have noticed that during experimentation, the memory
consumption keeps increasing. My setup is just startup a HelloWorld
agent in JRE 1.4 (or less for JADE-LEAP for CDC).

Can you please tell me where I'd find this recursive code? Or some
ideas?

The attachment is some published results on each middleware and the
memory used vs methods used (to fully load HelloWorld agent).

Kind Regards, Chris

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.

_______________________________________________
jade-develop mailing list
jade-develop@...
https://avalon.cselt.it/mailman/listinfo/jade-develop
UNSUBSCRIBE INSTRUCTIONS AT
http://jade.tilab.com/community-mailinglist.htm

From forum: JADE - Dev

Debian command line arguments passing

2009-12-15T06:31:58Z

Hi all,

I need some help here, i dont know how to pass arguments in the command line in Debian, more specifically, i want to do this "Windows command" in Debian:

java jade.Boot hello:HelloWorldAgent(arg1 arg2)

Ive tried [arg1 arg2]; "arg1 arg2"... but none of them works! Thanks in advance!!!

_______________________________________________
jade-develop mailing list
jade-develop@...
https://avalon.cselt.it/mailman/listinfo/jade-develop
UNSUBSCRIBE INSTRUCTIONS AT
http://jade.tilab.com/community-mailinglist.htm

From forum: JADE - Dev

RE: Starting sniffer when jade is run

2009-12-15T06:15:58Z

Hi,

The Sniffer can be instructed to sniff agents before they are created by means of the sniffer.properties files.

In such file you can specify, among others, the preload property indicating the name of the agents you want to sniff.

E.g.

preload=da0;da1

Look at the jade.tools.sniffer.Sniffer class javadoc for details.

As for saving the sniffed messages in a file, the Sniffer provides the “WriteMessageList” button that does exactly what you need.

Bye,

Giovanni

From: jade-develop-bounces@... [mailto:jade-develop-bounces@...] On Behalf Of Hussain, Adil
Sent: domenica 13 dicembre 2009 20.42
To: jade-develop@...
Subject: [jade-develop] Starting sniffer when jade is run

Hi all,

I want run jade with a number of agents such that all messages exchanged between the agents are sniffed.

I know I can specify the sniffer agent to start with jade as with any other agent but the problem is twofold:

(1) some of the other agents might be created before the sniffer (and hence some messages will be missed)

(2) I believe I can't tell sniffer to sniff an agent until that agent exists (or by any other means except the gui).

Is there a way that the sniffer agent can be made to be the first agent to be created out of the list of agents I specify to be created?

Is there a way I can specify to the sniffer as its input the names of the agents it is to sniff, which might not exist yet, but which should be sniffed as soon as they are created? How?

Additionally, is it possible easily to output all messages the sniffer has sniffed to standard output or a file in a meaningful way? How?

Apologies for the numerous questions. Many thanks in advance.

Regards,

Adil Hussain

From forum: JADE - Dev

RE: JADE-LEAP Memory Leak?

2009-12-15T01:20:52Z

Hi,

As far as I have understood the test you are performing should be similar to the following one:

public class Test {

public static final void main(String[] args) {
Properties pp = new Properties();
pp.setProperty("nomtp", "true");
ProfileImpl p = new ProfileImpl(pp);
long n = 0;
try {
ContainerController cc = Runtime.instance().createMainContainer(p);
while (true) {
AgentController ac = cc.createNewAgent("Test-"+n, "examples.hello.HelloWorldAgent", null);
ac.start();
n++;
}
}
catch (Throwable t) {
System.err.println("Error creating agent "+n);
t.printStackTrace();
}
}
}

I run the above test up to the creation of 1.500.000 agents and I got no memory increment: the memory consumption ranges from ~20 MB up to 50MB.

Is your test different with respect to mine?

Bye,

Giovanni
-----Original Message-----
From: C.P.Bridges@... [mailto:C.P.Bridges@...]
Sent: lunedì 14 dicembre 2009 10.51
To: Caire Giovanni; jade-develop@...
Subject: RE: JADE-LEAP Memory Leak?

Hi Giovanni,

The test literally just loads up the HelloWorld agent and terminates once that has loaded. The method probe I use tracks the amount of memory used as in my previous figure to each method invoked. You'll see that the memory used keeps on rising - so when does it stop?

Or after which classes/methods does the memory level off to stability?

Cheers, Chris

-----Original Message-----
From: Caire Giovanni [mailto:giovanni.caire@...]
Sent: 09 December 2009 16:48
To: Bridges CP Mr (PG/R - Electronic Eng); jade-develop@...
Subject: RE: JADE-LEAP Memory Leak?

Hi,

Can you please clarify what your test actually does?
Note that we have mission critical systems continuously running in the fields with hundreds of agents and we never experienced memory-leak problems.

Bye,

Giovanni

-----Original Message-----
From: C.P.Bridges@... [mailto:C.P.Bridges@...]
Sent: martedì 8 dicembre 2009 15.03
To: jade-develop@...; Caire Giovanni
Subject: JADE-LEAP Memory Leak?

Hi Giovanni, JADE'ers,

I've been working with JADE-LEAP (and other agent middleware) for a
while now and have noticed that during experimentation, the memory
consumption keeps increasing. My setup is just startup a HelloWorld
agent in JRE 1.4 (or less for JADE-LEAP for CDC).

Can you please tell me where I'd find this recursive code? Or some
ideas?

The attachment is some published results on each middleware and the
memory used vs methods used (to fully load HelloWorld agent).

Kind Regards, Chris

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.

_______________________________________________
jade-develop mailing list
jade-develop@...
https://avalon.cselt.it/mailman/listinfo/jade-develop
UNSUBSCRIBE INSTRUCTIONS AT
http://jade.tilab.com/community-mailinglist.htm

From forum: JADE - Dev

Help for beginner

2009-12-14T23:48:31Z

Hello everyone,

I'am Jade beginner, so I need help.
I do not understand, how to configuring MTPs from the graphical
management console. I completed the activities as described in
"Select a container from the GUI, click the right button of the
mouse and a popup menu appears. Choose the Install a new MTP option
and a dialog will be shown. Here the following information can be set:

* the container to install the new MTP on (if different from the
selected one)
* the fully qualified name of the class implementing the
jade.mtp.MTP interface, and (if it is supported by the chosen protocol)
* optionally the transport address that will be used to contact
the new MTP.

For example, in order to install a new HTTP endpoint on the default
local port by using the HTTP MTP, one should write
jamr.jademtp.http.MessageTransportProtocol as the class name and
nothing as the address. In order to use the transport on a different
port or a particular interface of the current machine you could
provide as the transport address a standard http url:
http://mymachinename.org:8978 ( where 8978 would be the port number on
which the transport will bind ).

Choosing Uninstall an MTP shows a dialog where the user can select
from a list one of the currently installed MTPs and remove it from the
platform. "
but I get an error message, I do not understand what I am doing wrong ?

Thanks in advance

Andrius

_______________________________________________
jade-develop mailing list
jade-develop@...
https://avalon.cselt.it/mailman/listinfo/jade-develop
UNSUBSCRIBE INSTRUCTIONS AT
http://jade.tilab.com/community-mailinglist.htm

From forum: JADE - Dev

Re: jade-develop Digest, Vol 83, Issue 11

2009-12-14T21:00:34Z

Hi Everyone,
I would like to create an agent based system as a plugin for chrome...but i doubt that whether i could provide the JADE container to the agents in the plugin...is it possible? if so can you please explain how this could be done?
thanks in advance....

_______________________________________________
jade-develop mailing list
jade-develop@...
https://avalon.cselt.it/mailman/listinfo/jade-develop
UNSUBSCRIBE INSTRUCTIONS AT
http://jade.tilab.com/community-mailinglist.htm

From forum: JADE - Dev

RE: How to shut down Jade when run without using the GUI?

2009-12-14T08:14:31Z

Hi Adil,

Sorry, my fault on the getInstance. Sloppy cut-and-paste.

You must register the Codec Language and Ontology with the ContentManager before you call fillContent, like so:
import jade.content.lang.sl.SLCodec;
...
Codec codec = new SLCodec();
getContentManager().registerLanguage(codec);
getContentManager().registerOntology(JADEManagementOntology.getInstance());

You can then use codec.getName() for the String necessary in msg.setLanguage().

If you're going to do multiple things with this Agent, I usually do it first thing in Agent::setup(). However, if the whole point is to kill the platform, your agent isn't going to achieve much later on.

This *should* work. :)

Russ

-----Original Message-----
From: Hussain, Adil [mailto:adil.hussain02@...]
Sent: 14 December 2009 15:58
To: Russell Mills; jade-develop@...
Subject: RE: How to shut down Jade when run without using the GUI?

Hi Russ (and anyone that can help!),

I tried your code. It compiled but doesn't work. I get an exception "Unknown language fipa-sl". Any idea what I can do to fix this and send a message to the AMS to shut down the agent platform (and kill all agents)?

Btw, I had to make a couple of changes to your code to make it compile (I changed to getOntology() to getInstance(), and added exception handling), as follows:

ACLMessage msg = new ACLMessage(ACLMessage.REQUEST);
msg.addReceiver(getAMS());
msg.setLanguage(FIPANames.ContentLanguage.FIPA_SL);
msg.setOntology(JADEManagementOntology.getInstance().getName());
try {
getContentManager().fillContent(msg,new Action(getAID(), new ShutdownPlatform()));
send(msg);
}
catch (Exception e) {
e.printStackTrace();
}

Regards,
Adil
________________________________________
From: Russell Mills [russell.mills@...]
Sent: 14 December 2009 10:41
To: Hussain, Adil; jade-develop@...
Subject: RE: How to shut down Jade when run without using the GUI?

Hi Adil,

The class that you're looking for is the ShutdownPlatform Action in the JADEManagementOntology. You can send a Request message to the AMS with an instance of this in the content and the platform will shut down.

Code snippet (excluding error handling, assumes that you're inside an Agent rather than a Behaviour):

ACLMessage msg = new ACLMessage(ACLMessage.REQUEST); msg.addReceiver(getAMS()); msg.setLanguage(FIPANames.ContentLanguage.FIPA_SL);
msg.setOntology(JADEManagementOntology.getOntology().getName());
getContentManager().fillContent(msg,
new Action(getAID(), new ShutdownPlatform())); send(msg);

Hope this helps,

Russ
________________________________

From: jade-develop-bounces@... [mailto:jade-develop-bounces@...] On Behalf Of Hussain, Adil
Sent: 13 December 2009 19:41
To: jade-develop@...
Subject: [jade-develop] How to shut down Jade when run without using the GUI?

Hi all,

I need to start up Jade with a number of agents such that everything closes (all agents die) naturally after a certain amount of time (say 20 seconds) the way it would if I was to shut the platform using the gui, but I need this to happen without the gui. How would I do this?

I am thinking of loading an additional agent when I start up jade whose sole function is to sleep for 20 seconds, then wake and shut down the agent platform (close/end everything). Is this the correct/best way to do shut down jade with a gui? If so, what would this additional agent need to do to shut down the agent platform?

Regards,
Adil

RiskAware Limited. Registered in England. Company Number: 3812608. VAT Number: 740 891 815. Registered Address: 9th Floor, Colston Tower, Colston Street, Bristol, BS1 4XE.

The information in this email is intended solely for the addressee(s) and may contain privileged material. Access to this email by anyone else is unauthorised. Any review, retransmission, dissemination or any use of this information by persons or entities other than the intended recipient is strictly prohibited.

RiskAware Ltd reserves the right to monitor all outgoing and incoming e-mails.
_______________________________________________
jade-develop mailing list
jade-develop@...
https://avalon.cselt.it/mailman/listinfo/jade-develop
UNSUBSCRIBE INSTRUCTIONS AT
http://jade.tilab.com/community-mailinglist.htm

From forum: JADE - Dev

RE: How to shut down Jade when run without using the GUI?

2009-12-14T07:58:16Z

Hi Russ (and anyone that can help!),

I tried your code. It compiled but doesn't work. I get an exception "Unknown language fipa-sl". Any idea what I can do to fix this and send a message to the AMS to shut down the agent platform (and kill all agents)?

Btw, I had to make a couple of changes to your code to make it compile (I changed to getOntology() to getInstance(), and added exception handling), as follows:

ACLMessage msg = new ACLMessage(ACLMessage.REQUEST);
msg.addReceiver(getAMS());
msg.setLanguage(FIPANames.ContentLanguage.FIPA_SL);
msg.setOntology(JADEManagementOntology.getInstance().getName());
try {
getContentManager().fillContent(msg,new Action(getAID(), new ShutdownPlatform()));
send(msg);
}
catch (Exception e) {
e.printStackTrace();
}

Regards,
Adil
________________________________________
From: Russell Mills [russell.mills@...]
Sent: 14 December 2009 10:41
To: Hussain, Adil; jade-develop@...
Subject: RE: How to shut down Jade when run without using the GUI?

Hi Adil,

The class that you're looking for is the ShutdownPlatform Action in the JADEManagementOntology. You can send a Request message to the AMS with an instance of this in the content and the platform will shut down.

Code snippet (excluding error handling, assumes that you're inside an Agent rather than a Behaviour):

ACLMessage msg = new ACLMessage(ACLMessage.REQUEST);
msg.addReceiver(getAMS());
msg.setLanguage(FIPANames.ContentLanguage.FIPA_SL);
msg.setOntology(JADEManagementOntology.getOntology().getName());
getContentManager().fillContent(msg,
new Action(getAID(), new ShutdownPlatform()));
send(msg);

Hope this helps,

Russ
________________________________

From: jade-develop-bounces@... [mailto:jade-develop-bounces@...] On Behalf Of Hussain, Adil
Sent: 13 December 2009 19:41
To: jade-develop@...
Subject: [jade-develop] How to shut down Jade when run without using the GUI?

Hi all,

I need to start up Jade with a number of agents such that everything closes (all agents die) naturally after a certain amount of time (say 20 seconds) the way it would if I was to shut the platform using the gui, but I need this to happen without the gui. How would I do this?

I am thinking of loading an additional agent when I start up jade whose sole function is to sleep for 20 seconds, then wake and shut down the agent platform (close/end everything). Is this the correct/best way to do shut down jade with a gui? If so, what would this additional agent need to do to shut down the agent platform?

Regards,
Adil

RiskAware Limited. Registered in England. Company Number: 3812608. VAT Number: 740 891 815. Registered Address: 9th Floor, Colston Tower, Colston Street, Bristol, BS1 4XE.

The information in this email is intended solely for the addressee(s) and may contain privileged material. Access to this email by anyone else is unauthorised. Any review, retransmission, dissemination or any use of this information by persons or entities other than the intended recipient is strictly prohibited.

RiskAware Ltd reserves the right to monitor all outgoing and incoming e-mails.
_______________________________________________
jade-develop mailing list
jade-develop@...
https://avalon.cselt.it/mailman/listinfo/jade-develop
UNSUBSCRIBE INSTRUCTIONS AT
http://jade.tilab.com/community-mailinglist.htm

From forum: JADE - Dev

RE: How to shut down Jade when run without using the GUI?

2009-12-14T02:41:51Z

Hi Adil,

The class that you're looking for is the ShutdownPlatform Action in the JADEManagementOntology. You can send a Request message to the AMS with an instance of this in the content and the platform will shut down.

Code snippet (excluding error handling, assumes that you're inside an Agent rather than a Behaviour):

ACLMessage msg = new ACLMessage(ACLMessage.REQUEST);
msg.addReceiver(getAMS());
msg.setLanguage(FIPANames.ContentLanguage.FIPA_SL);
msg.setOntology(JADEManagementOntology.getOntology().getName());
getContentManager().fillContent(msg,
new Action(getAID(), new ShutdownPlatform()));
send(msg);

Hope this helps,

Russ
________________________________

From: jade-develop-bounces@... [mailto:jade-develop-bounces@...] On Behalf Of Hussain, Adil
Sent: 13 December 2009 19:41
To: jade-develop@...
Subject: [jade-develop] How to shut down Jade when run without using the GUI?

Hi all,

I need to start up Jade with a number of agents such that everything closes (all agents die) naturally after a certain amount of time (say 20 seconds) the way it would if I was to shut the platform using the gui, but I need this to happen without the gui. How would I do this?

I am thinking of loading an additional agent when I start up jade whose sole function is to sleep for 20 seconds, then wake and shut down the agent platform (close/end everything). Is this the correct/best way to do shut down jade with a gui? If so, what would this additional agent need to do to shut down the agent platform?

Regards,
Adil

RiskAware Limited. Registered in England. Company Number: 3812608. VAT Number: 740 891 815. Registered Address: 9th Floor, Colston Tower, Colston Street, Bristol, BS1 4XE.

The information in this email is intended solely for the addressee(s) and may contain privileged material. Access to this email by anyone else is unauthorised. Any review, retransmission, dissemination or any use of this information by persons or entities other than the intended recipient is strictly prohibited.

RiskAware Ltd reserves the right to monitor all outgoing and incoming e-mails.
_______________________________________________
jade-develop mailing list
jade-develop@...
https://avalon.cselt.it/mailman/listinfo/jade-develop
UNSUBSCRIBE INSTRUCTIONS AT
http://jade.tilab.com/community-mailinglist.htm

From forum: JADE - Dev

RE: JADE-LEAP Memory Leak?

2009-12-14T01:50:49Z

Hi Giovanni,

The test literally just loads up the HelloWorld agent and terminates once that has loaded. The method probe I use tracks the amount of memory used as in my previous figure to each method invoked. You'll see that the memory used keeps on rising - so when does it stop?

Or after which classes/methods does the memory level off to stability?

Cheers, Chris

-----Original Message-----
From: Caire Giovanni [mailto:giovanni.caire@...]
Sent: 09 December 2009 16:48
To: Bridges CP Mr (PG/R - Electronic Eng); jade-develop@...
Subject: RE: JADE-LEAP Memory Leak?

Hi,

Can you please clarify what your test actually does?
Note that we have mission critical systems continuously running in the fields with hundreds of agents and we never experienced memory-leak problems.

Bye,

Giovanni

-----Original Message-----
From: C.P.Bridges@... [mailto:C.P.Bridges@...]
Sent: martedì 8 dicembre 2009 15.03
To: jade-develop@...; Caire Giovanni
Subject: JADE-LEAP Memory Leak?

Hi Giovanni, JADE'ers,

I've been working with JADE-LEAP (and other agent middleware) for a
while now and have noticed that during experimentation, the memory
consumption keeps increasing. My setup is just startup a HelloWorld
agent in JRE 1.4 (or less for JADE-LEAP for CDC).

Can you please tell me where I'd find this recursive code? Or some
ideas?

The attachment is some published results on each middleware and the
memory used vs methods used (to fully load HelloWorld agent).

Kind Regards, Chris

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.

_______________________________________________
jade-develop mailing list
jade-develop@...
https://avalon.cselt.it/mailman/listinfo/jade-develop
UNSUBSCRIBE INSTRUCTIONS AT
http://jade.tilab.com/community-mailinglist.htm

From forum: JADE - Dev

Starting sniffer when jade is run

2009-12-13T11:42:11Z