From twright at bbn.com  Fri Jan 18 13:50:48 2008
From: twright at bbn.com (Todd Wright)
Date: Fri, 18 Jan 2008 13:50:48 -0500
Subject: Inter Node Communication
In-Reply-To: <200506081036.10574.twright@bbn.com>
References: <9aab3c40506071918631fd4@mail.gmail.com>
	<42A6FFC9.5090909@bbn.com> <200506081036.10574.twright@bbn.com>
Message-ID: <4790F508.1070500@bbn.com>


Attached below is an updated version of the simple RMI "echo" test.  This 
version works with Cougaar 12.4+.

Please see the zip's README for details.

Todd

Todd Wright wrote:
> On Wednesday 08 June 2005 10:25, Aaron Helsinger wrote:
>> Based on the fact that the error message says "127.0.0.1", this suggests
>> that  Node B is still looking at localhost for the WP server. Are you
>> sure that alpreg.ini was edited on both machines?
> 
> Right, both "alpreg.ini" files should contain the same hostname (not 
> "localhost").
> 
> I've also seen this error when the `hostname` returns "localhost", due to a 
> system configuration problem in /etc/hosts.  In your case, node "A" thinks 
> that its IP address is "127.0.0.1", which confuses node "B" when it finds 
> this address through the usual Cougaar naming service startup.
> 
> I've attached a trimmed-down example that should help you debug.  Run 
> "./compile" to compile, then start the server on one host:
>   ./runServer
> On a remote host, run the client with the URI printed by the above server 
> command, e.g.:
>   ./runClient rmi://123.45.67.89:38335/EchoServer_Stub/1_e..
> The client should print "hello".
> In your config I expect the server to print a URI starting with 
> "rmi://127.0.0.1".
> 
> Todd
> 
>> Andie Kurniawan wrote:
>>> Hello,
>>>
>>> I have been following the 'Introduction to Cougaar Programming' by
>>> Mark Barger. I stuck in the last example where two agents located
>>> across two machines are communicated (example 11).
>>>
>>> Based on the presentation slides, I have modified 'alpreg.ini' to
>>> change localhost to the hostname (I put the IP address of the first
>>> machine) on both machines and then start Exercise11A before ExerciseB.
>>>
>>> On the first machine where the nameserver is located, there was no
>>> error message. However, on the other machine, I received the following
>>> message
>>>
>>> WARN [DestinationQueueImpl] - Exercise11B: Failure in communication,
>>> message The source: Exercise11B The Target: Exercise11A The Message
>>> Id: 0 caused by
>>> java.rmi.ConnectException: Connection refused to host: 127.0.0.1;
>>> nested exception is:
>>>  java.net.ConnectException: Connection refused
>>>
>>> Just for some additional information, both of the machines are running
>>> Ubuntu Linux and using java version 1.4.2.
>>>
>>> Any help will be appreciated.
>>>
>>> Best Wishes,
>>> Andie Kurniawan
>>>
>>> _______________________________________________
>>> Cougaar-developers mailing list
>>> Cougaar-developers at cougaar.org
>>> http://cougaar.org/mailman/listinfo/cougaar-developers
>> _______________________________________________
>> Cougaar-developers mailing list
>> Cougaar-developers at cougaar.org
>> http://cougaar.org/mailman/listinfo/cougaar-developers
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Cougaar-developers mailing list
>> Cougaar-developers at cougaar.org
>> http://cougaar.org/mailman/listinfo/cougaar-developers
-------------- next part --------------
This is a message from the MailScanner E-Mail Virus Protection Service
----------------------------------------------------------------------
The original e-mail attachment "rmi_encode_test.zip"
is on the list of unacceptable attachments for this site and has been
replaced by this warning message.

Due to limitations placed on us by the Regulation of Investigatory Powers
Act 2000, we were unable to keep a copy of the original attachment.

At Fri Jan 18 13:43:46 2008 the virus scanner said:
   MailScanner: Batch files are often malicious (runServer.bat)
   MailScanner: Batch files are often malicious (compile.bat)
   MailScanner: Batch files are often malicious (runClient.bat)

-- 
Postmaster
Cougaar Open Source Community
www.cougaar.org

MailScanner thanks transtec Computers for their support

From twright at bbn.com  Fri Jan 18 14:17:49 2008
From: twright at bbn.com (Todd Wright)
Date: Fri, 18 Jan 2008 14:17:49 -0500
Subject: Inter Node Communication
In-Reply-To: <4790F508.1070500@bbn.com>
References: <9aab3c40506071918631fd4@mail.gmail.com>	<42A6FFC9.5090909@bbn.com>
	<200506081036.10574.twright@bbn.com> <4790F508.1070500@bbn.com>
Message-ID: <4790FB5D.50903@bbn.com>

Todd Wright wrote:
> 
> Attached below is an updated version of the simple RMI "echo" test.  
> This version works with Cougaar 12.4+.
> 
> Please see the zip's README for details.

Sorry, the server blocked the attachment.

I've uploaded the zip to the website:
   http://mts.cougaar.org/

Todd

> 
> Todd
> 
> Todd Wright wrote:
>> On Wednesday 08 June 2005 10:25, Aaron Helsinger wrote:
>>> Based on the fact that the error message says "127.0.0.1", this suggests
>>> that  Node B is still looking at localhost for the WP server. Are you
>>> sure that alpreg.ini was edited on both machines?
>>
>> Right, both "alpreg.ini" files should contain the same hostname (not 
>> "localhost").
>>
>> I've also seen this error when the `hostname` returns "localhost", due 
>> to a system configuration problem in /etc/hosts.  In your case, node 
>> "A" thinks that its IP address is "127.0.0.1", which confuses node "B" 
>> when it finds this address through the usual Cougaar naming service 
>> startup.
>>
>> I've attached a trimmed-down example that should help you debug.  Run 
>> "./compile" to compile, then start the server on one host:
>>   ./runServer
>> On a remote host, run the client with the URI printed by the above 
>> server command, e.g.:
>>   ./runClient rmi://123.45.67.89:38335/EchoServer_Stub/1_e..
>> The client should print "hello".
>> In your config I expect the server to print a URI starting with 
>> "rmi://127.0.0.1".
>>
>> Todd
>>
>>> Andie Kurniawan wrote:
>>>> Hello,
>>>>
>>>> I have been following the 'Introduction to Cougaar Programming' by
>>>> Mark Barger. I stuck in the last example where two agents located
>>>> across two machines are communicated (example 11).
>>>>
>>>> Based on the presentation slides, I have modified 'alpreg.ini' to
>>>> change localhost to the hostname (I put the IP address of the first
>>>> machine) on both machines and then start Exercise11A before ExerciseB.
>>>>
>>>> On the first machine where the nameserver is located, there was no
>>>> error message. However, on the other machine, I received the following
>>>> message
>>>>
>>>> WARN [DestinationQueueImpl] - Exercise11B: Failure in communication,
>>>> message The source: Exercise11B The Target: Exercise11A The Message
>>>> Id: 0 caused by
>>>> java.rmi.ConnectException: Connection refused to host: 127.0.0.1;
>>>> nested exception is:
>>>>  java.net.ConnectException: Connection refused
>>>>
>>>> Just for some additional information, both of the machines are running
>>>> Ubuntu Linux and using java version 1.4.2.
>>>>
>>>> Any help will be appreciated.
>>>>
>>>> Best Wishes,
>>>> Andie Kurniawan
>>>>
>>>> _______________________________________________
>>>> Cougaar-developers mailing list
>>>> Cougaar-developers at cougaar.org
>>>> http://cougaar.org/mailman/listinfo/cougaar-developers
>>> _______________________________________________
>>> Cougaar-developers mailing list
>>> Cougaar-developers at cougaar.org
>>> http://cougaar.org/mailman/listinfo/cougaar-developers
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Cougaar-developers mailing list
>>> Cougaar-developers at cougaar.org
>>> http://cougaar.org/mailman/listinfo/cougaar-developers
> 
> ------------------------------------------------------------------------
> 
> This is a message from the MailScanner E-Mail Virus Protection Service
> ----------------------------------------------------------------------
> The original e-mail attachment "rmi_encode_test.zip"
> is on the list of unacceptable attachments for this site and has been
> replaced by this warning message.
> 
> Due to limitations placed on us by the Regulation of Investigatory Powers
> Act 2000, we were unable to keep a copy of the original attachment.
> 
> At Fri Jan 18 13:43:46 2008 the virus scanner said:
>    MailScanner: Batch files are often malicious (runServer.bat)
>    MailScanner: Batch files are often malicious (compile.bat)
>    MailScanner: Batch files are often malicious (runClient.bat)
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Cougaar-developers mailing list
> Cougaar-developers at cougaar.org
> http://cougaar.org/mailman/listinfo/cougaar-developers


From mkamerma at science.uva.nl  Mon Jan 21 05:51:13 2008
From: mkamerma at science.uva.nl (Michiel Kamermans)
Date: Mon, 21 Jan 2008 11:51:13 +0100
Subject: cougaar 12.4 and saxon 9
Message-ID: <47947921.8080300@science.uva.nl>

Cougaar 12.4 seems to incompatible with the new generation of Saxon XSLT 
parsers, suffering from the same problem as outlined in 
http://osdir.com/ml/text.xml.o-xml/2003-12/msg00001.html

because the new parser throws an exception when there is no 
xml-stylesheet defined, instead of registering that there simply is 
none, cougaar doesn't catch exception yet and instead terminates citing 
this exception.

- Mike Kamermans
University of Amsterdam


From andreas at paleden.com  Tue Jan 22 02:20:49 2008
From: andreas at paleden.com (Andreas)
Date: Mon, 21 Jan 2008 23:20:49 -0800
Subject: Problem starting cougaar using communities
In-Reply-To: <47947921.8080300@science.uva.nl>
References: <47947921.8080300@science.uva.nl>
Message-ID: <47959951.1070706@paleden.com>

I just went through the mesh demo and I am trying to convert some of my 
earlier test code to startup using runtime and society xml files.  
Before I made things work by copying files into various subfolders of 
the cougaar_install directories.

The following applies to my environment

    * Java 1.6
    * Cougaar 12.4
    * Windows 2000

I have installed cougaar to c:/cougaar and I have created a separate 
location for my test application APPA which is c:/cougaar_apps and 
c:/cougaar_apps/appa respectively.

When I run the application the community information cannot be loaded.  
I have included the trace at the end of this email.

I have copied the communities.xml to the c:/cougaar_apps/appa/config 
directory.

I seems as if the -Dorg.cougaar.config.path does not work.  I have used 
several different combinations in the BasicRuntime.xml file none of 
which worked.

Examples:
    
<vm_parameter>-Dorg.cougaar.config.path=c:/cougaar/configs/common\;C:/cougaar_apps/appa/config\</vm_parameter>
    
<vm_parameter>-Dorg.cougaar.config.path=c:/cougaar/configs/common;C:/cougaar_apps/appa/config</vm_parameter>
    
<vm_parameter>-Dorg.cougaar.config.path=c:/cougaar/configs/common</vm_parameter>
    
<vm_parameter>-Dorg.cougaar.config.path=C:/cougaar_apps/appa/config</vm_parameter>

I have attached a zip of all the directories in c:/cougaar_apps.

Can someone please tell me what I am doing wrong here.

Thanks,
Andreas




C:\cougaar_apps\appa\run>cougaar 
c:/cougaar_apps/appa/config/DirMonAgent.xml BasicRuntime.xml
C:\DOCUME~1\amundin\LOCALS~1\Temp\cougaar_exec055.bat
COUGAAR 12.4 built on Thu Sep 27 12:19:45 PDT 2007
Repository: B12_4 on Thu Sep 27 12:17:21 PDT 2007
VM: JDK 1.6.0_03-b05 (mixed mode)
OS: Windows 2000 (5.0)
2008-01-21 23:08:16,848 SHOUT [XMLComponentInitializerServiceProvider] - 
Initializing node "APPA" from XML file "c:/coug
aar_apps/appa/config/DirMonAgent.xml"
2008-01-21 23:08:21,625 WARN  [CommunityPlugin] - DirMonAgent: Unable to 
obtain community information for agent DirMonAg
ent
2008-01-21 23:08:21,625 FATAL [SuicideService] - Suicide from DirMonAgent
java.lang.NullPointerException
        at 
org.cougaar.community.CommunityPlugin.findMyStartupCommunities(CommunityPlugin.java:150)
        at 
org.cougaar.community.CommunityPlugin.joinStartupCommunities(CommunityPlugin.java:176)
        at 
org.cougaar.community.CommunityPlugin.setupSubscriptions(CommunityPlugin.java:99)
        at 
org.cougaar.core.blackboard.BlackboardClientComponent.precycle(BlackboardClientComponent.java:329)
        at 
org.cougaar.core.blackboard.BlackboardClientComponent$2.trigger(BlackboardClientComponent.java:245)
        at 
org.cougaar.util.SyncTriggerModelImpl.runInnerTrigger(SyncTriggerModelImpl.java:233)
        at 
org.cougaar.util.SyncTriggerModelImpl.access$000(SyncTriggerModelImpl.java:56)
        at 
org.cougaar.util.SyncTriggerModelImpl$2.trigger(SyncTriggerModelImpl.java:98)
        at 
org.cougaar.core.agent.service.scheduler.SchedulerServiceProvider$WorkerBase.runTrigger(SchedulerServiceProvi
der.java:217)
        at 
org.cougaar.core.agent.service.scheduler.SchedulerServiceProvider$NormalScheduler$Worker.run(SchedulerService
Provider.java:313)
        at 
org.cougaar.core.thread.SchedulableObject.run(SchedulableObject.java:118)
        at 
org.cougaar.core.thread.ThreadPool$PooledThread.continuationLoop(ThreadPool.java:94)
        at 
org.cougaar.core.thread.ThreadPool$PooledThread.run(ThreadPool.java:122)
2008-01-21 23:08:21,635 WARN  [CommunityPlugin] - DirMonMgr: Unable to 
obtain community information for agent DirMonMgr
2008-01-21 23:08:21,635 FATAL [SuicideService] - Suicide from DirMonMgr
java.lang.NullPointerException
        at 
org.cougaar.community.CommunityPlugin.findMyStartupCommunities(CommunityPlugin.java:150)
        at 
org.cougaar.community.CommunityPlugin.joinStartupCommunities(CommunityPlugin.java:176)
        at 
org.cougaar.community.CommunityPlugin.setupSubscriptions(CommunityPlugin.java:99)
        at 
org.cougaar.core.blackboard.BlackboardClientComponent.precycle(BlackboardClientComponent.java:329)
        at 
org.cougaar.core.blackboard.BlackboardClientComponent$2.trigger(BlackboardClientComponent.java:245)
        at 
org.cougaar.util.SyncTriggerModelImpl.runInnerTrigger(SyncTriggerModelImpl.java:233)
        at 
org.cougaar.util.SyncTriggerModelImpl.access$000(SyncTriggerModelImpl.java:56)
        at 
org.cougaar.util.SyncTriggerModelImpl$2.trigger(SyncTriggerModelImpl.java:98)
        at 
org.cougaar.core.agent.service.scheduler.SchedulerServiceProvider$WorkerBase.runTrigger(SchedulerServiceProvi
der.java:217)
        at 
org.cougaar.core.agent.service.scheduler.SchedulerServiceProvider$NormalScheduler$Worker.run(SchedulerService
Provider.java:313)
        at 
org.cougaar.core.thread.SchedulableObject.run(SchedulableObject.java:118)
        at 
org.cougaar.core.thread.ThreadPool$PooledThread.continuationLoop(ThreadPool.java:94)
        at 
org.cougaar.core.thread.ThreadPool$PooledThread.run(ThreadPool.java:122)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://cougaar.org/pipermail/cougaar-developers/attachments/20080121/cf63abf5/attachment-0001.html
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: cougaar_exec055.bat.txt
Url: http://cougaar.org/pipermail/cougaar-developers/attachments/20080121/cf63abf5/cougaar_exec055.bat-0001.txt
-------------- next part --------------
This is a message from the MailScanner E-Mail Virus Protection Service
----------------------------------------------------------------------
The original e-mail attachment "appa.zip"
is on the list of unacceptable attachments for this site and has been
replaced by this warning message.

Due to limitations placed on us by the Regulation of Investigatory Powers
Act 2000, we were unable to keep a copy of the original attachment.

At Tue Jan 22 02:24:12 2008 the virus scanner said:
   MailScanner: Batch files are often malicious (run.bat)

-- 
Postmaster
Cougaar Open Source Community
www.cougaar.org

MailScanner thanks transtec Computers for their support

From twright at bbn.com  Tue Jan 22 15:42:15 2008
From: twright at bbn.com (Todd Wright)
Date: Tue, 22 Jan 2008 15:42:15 -0500
Subject: cougaar 12.4 and saxon 9
In-Reply-To: <47947921.8080300@science.uva.nl>
References: <47947921.8080300@science.uva.nl>
Message-ID: <47965527.2060804@bbn.com>


Where is this exception being thrown?  Is it in
   org.cougaar.core.node.XSLTransformer.findXmlStylesheetTransformerHandler
http://cougaar.org/cgi-bin/viewcvs.cgi/core/src/org/cougaar/core/node/XSLTransformer.java?annotate=1.4&cvsroot=core#390
?
If so, I can modify this method to return null if an exception is thrown.

Please reply with the exception stacktrace.

The Cougaar XSLT parser checks for an optional stylesheet tag in the XML file. 
  My understanding is that this tag is *optional*, since the user may want to 
apply different stylesheets to the same XML data file, in which case the 
stylesheet should be specified at runtime (as Cougaar does) instead of in the 
XML file.  I can't see why the new Saxon XSLT parser would throw an exception 
in this case.  Hopefully the stacktrace will help explain the problem.

Todd

Michiel Kamermans wrote:
> Cougaar 12.4 seems to incompatible with the new generation of Saxon XSLT 
> parsers, suffering from the same problem as outlined in 
> http://osdir.com/ml/text.xml.o-xml/2003-12/msg00001.html
> 
> because the new parser throws an exception when there is no 
> xml-stylesheet defined, instead of registering that there simply is 
> none, cougaar doesn't catch exception yet and instead terminates citing 
> this exception.
> 
> - Mike Kamermans
> University of Amsterdam
> 
> _______________________________________________
> Cougaar-developers mailing list
> Cougaar-developers at cougaar.org
> http://cougaar.org/mailman/listinfo/cougaar-developers
> 


From twright at bbn.com  Tue Jan 22 16:07:40 2008
From: twright at bbn.com (Todd Wright)
Date: Tue, 22 Jan 2008 16:07:40 -0500
Subject: Problem starting cougaar using communities
In-Reply-To: <47959951.1070706@paleden.com>
References: <47947921.8080300@science.uva.nl> <47959951.1070706@paleden.com>
Message-ID: <47965B1C.2030904@bbn.com>


Communities are not required for the mesh demo.  Remove the following plugin 
from your XML file:
   org.cougaar.community.CommunityPlugin

You're correctly setting the Cougaar template property:
   -Dorg.cougaar.society.xsl.param.template=single_node
which disables the legacy community service:
   http://cougaar.cougaar.org/software/latest/OnlineManual/Templates.html

If you require the legacy community service, you can enable it by either removing:
   -Dorg.cougaar.society.xsl.param.template=single_node
or adding:
   -Dorg.cougaar.society.xsl.param.communities=legacy
This will load the service and it should find your "communities.xml".

You may also be interested in the non-legacy community service implementation, 
which can be enabled with:
   -Dorg.cougaar.society.xsl.param.template=wan
or:
   -Dorg.cougaar.society.xsl.param.communities=true
Demo "join" and "test" plugins are included with Cougaar:
http://cougaar.cougaar.org/software/latest/javadoc/core/doc/api/org/cougaar/core/agent/service/community/package-summary.html

Todd

Andreas wrote:
> I just went through the mesh demo and I am trying to convert some of my 
> earlier test code to startup using runtime and society xml files.  
> Before I made things work by copying files into various subfolders of 
> the cougaar_install directories.
> 
> The following applies to my environment
> 
>     * Java 1.6
>     * Cougaar 12.4
>     * Windows 2000
> 
> I have installed cougaar to c:/cougaar and I have created a separate 
> location for my test application APPA which is c:/cougaar_apps and 
> c:/cougaar_apps/appa respectively.
> 
> When I run the application the community information cannot be loaded.  
> I have included the trace at the end of this email.
> 
> I have copied the communities.xml to the c:/cougaar_apps/appa/config 
> directory.
> 
> I seems as if the -Dorg.cougaar.config.path does not work.  I have used 
> several different combinations in the BasicRuntime.xml file none of 
> which worked.
> 
> Examples:
>     
> <vm_parameter>-Dorg.cougaar.config.path=c:/cougaar/configs/common\;C:/cougaar_apps/appa/config\</vm_parameter>
>     
> <vm_parameter>-Dorg.cougaar.config.path=c:/cougaar/configs/common;C:/cougaar_apps/appa/config</vm_parameter>
>     
> <vm_parameter>-Dorg.cougaar.config.path=c:/cougaar/configs/common</vm_parameter>
>     
> <vm_parameter>-Dorg.cougaar.config.path=C:/cougaar_apps/appa/config</vm_parameter>
> 
> I have attached a zip of all the directories in c:/cougaar_apps.
> 
> Can someone please tell me what I am doing wrong here.
> 
> Thanks,
> Andreas
> 
> 
> 
> 
> C:\cougaar_apps\appa\run>cougaar 
> c:/cougaar_apps/appa/config/DirMonAgent.xml BasicRuntime.xml
> C:\DOCUME~1\amundin\LOCALS~1\Temp\cougaar_exec055.bat
> COUGAAR 12.4 built on Thu Sep 27 12:19:45 PDT 2007
> Repository: B12_4 on Thu Sep 27 12:17:21 PDT 2007
> VM: JDK 1.6.0_03-b05 (mixed mode)
> OS: Windows 2000 (5.0)
> 2008-01-21 23:08:16,848 SHOUT [XMLComponentInitializerServiceProvider] - 
> Initializing node "APPA" from XML file "c:/coug
> aar_apps/appa/config/DirMonAgent.xml"
> 2008-01-21 23:08:21,625 WARN  [CommunityPlugin] - DirMonAgent: Unable to 
> obtain community information for agent DirMonAg
> ent
> 2008-01-21 23:08:21,625 FATAL [SuicideService] - Suicide from DirMonAgent
> java.lang.NullPointerException
>         at 
> org.cougaar.community.CommunityPlugin.findMyStartupCommunities(CommunityPlugin.java:150)
>         at 
> org.cougaar.community.CommunityPlugin.joinStartupCommunities(CommunityPlugin.java:176)
>         at 
> org.cougaar.community.CommunityPlugin.setupSubscriptions(CommunityPlugin.java:99)
>         at 
> org.cougaar.core.blackboard.BlackboardClientComponent.precycle(BlackboardClientComponent.java:329)
>         at 
> org.cougaar.core.blackboard.BlackboardClientComponent$2.trigger(BlackboardClientComponent.java:245)
>         at 
> org.cougaar.util.SyncTriggerModelImpl.runInnerTrigger(SyncTriggerModelImpl.java:233)
>         at 
> org.cougaar.util.SyncTriggerModelImpl.access$000(SyncTriggerModelImpl.java:56)
>         at 
> org.cougaar.util.SyncTriggerModelImpl$2.trigger(SyncTriggerModelImpl.java:98)
>         at 
> org.cougaar.core.agent.service.scheduler.SchedulerServiceProvider$WorkerBase.runTrigger(SchedulerServiceProvi
> der.java:217)
>         at 
> org.cougaar.core.agent.service.scheduler.SchedulerServiceProvider$NormalScheduler$Worker.run(SchedulerService
> Provider.java:313)
>         at 
> org.cougaar.core.thread.SchedulableObject.run(SchedulableObject.java:118)
>         at 
> org.cougaar.core.thread.ThreadPool$PooledThread.continuationLoop(ThreadPool.java:94)
>         at 
> org.cougaar.core.thread.ThreadPool$PooledThread.run(ThreadPool.java:122)
> 2008-01-21 23:08:21,635 WARN  [CommunityPlugin] - DirMonMgr: Unable to 
> obtain community information for agent DirMonMgr
> 2008-01-21 23:08:21,635 FATAL [SuicideService] - Suicide from DirMonMgr
> java.lang.NullPointerException
>         at 
> org.cougaar.community.CommunityPlugin.findMyStartupCommunities(CommunityPlugin.java:150)
>         at 
> org.cougaar.community.CommunityPlugin.joinStartupCommunities(CommunityPlugin.java:176)
>         at 
> org.cougaar.community.CommunityPlugin.setupSubscriptions(CommunityPlugin.java:99)
>         at 
> org.cougaar.core.blackboard.BlackboardClientComponent.precycle(BlackboardClientComponent.java:329)
>         at 
> org.cougaar.core.blackboard.BlackboardClientComponent$2.trigger(BlackboardClientComponent.java:245)
>         at 
> org.cougaar.util.SyncTriggerModelImpl.runInnerTrigger(SyncTriggerModelImpl.java:233)
>         at 
> org.cougaar.util.SyncTriggerModelImpl.access$000(SyncTriggerModelImpl.java:56)
>         at 
> org.cougaar.util.SyncTriggerModelImpl$2.trigger(SyncTriggerModelImpl.java:98)
>         at 
> org.cougaar.core.agent.service.scheduler.SchedulerServiceProvider$WorkerBase.runTrigger(SchedulerServiceProvi
> der.java:217)
>         at 
> org.cougaar.core.agent.service.scheduler.SchedulerServiceProvider$NormalScheduler$Worker.run(SchedulerService
> Provider.java:313)
>         at 
> org.cougaar.core.thread.SchedulableObject.run(SchedulableObject.java:118)
>         at 
> org.cougaar.core.thread.ThreadPool$PooledThread.continuationLoop(ThreadPool.java:94)
>         at 
> org.cougaar.core.thread.ThreadPool$PooledThread.run(ThreadPool.java:122)
> 
> 
> ------------------------------------------------------------------------
> 
> @echo off 
> @REM Generated by Cougaar.bat! 
> java -Dorg.cougaar.society.xsl.param.template=single_node -Dorg.cougaar.core.logging.config.filename=logging.props -Dorg.cougaar.config.path=c:/cougaar/configs/common\;C:/cougaar_apps/appa/config\; -Dorg.cougaar.class.path=C:/cougaar_apps/appa/lib/appa.jar -Dorg.cougaar.runtime.path=C:/cougaar_apps/appa/run -Dorg.cougaar.society.path=C:/cougaar_apps/appa -Dorg.cougaar.install.path=c:/cougaar -Dorg.cougaar.system.path=c:/cougaar/sys -Dorg.cougaar.bootstrap.application=org.cougaar.core.node.Node -Dorg.cougaar.society.file=c:/cougaar_apps/appa/config/DirMonAgent.xml -Dorg.cougaar.runtime.file=BasicRuntime.xml -Dorg.cougaar.node.name=APPA -Xbootclasspath/p:c:/cougaar/lib/javaiopatch.jar -Dorg.cougaar.core.node.InitializationComponent=XML -Djava.class.path=c:/cougaar/lib/bootstrap.jar org.cougaar.bootstrap.Bootstrapper
> 
> 
> ------------------------------------------------------------------------
> 
> This is a message from the MailScanner E-Mail Virus Protection Service
> ----------------------------------------------------------------------
> The original e-mail attachment "appa.zip"
> is on the list of unacceptable attachments for this site and has been
> replaced by this warning message.
> 
> Due to limitations placed on us by the Regulation of Investigatory Powers
> Act 2000, we were unable to keep a copy of the original attachment.
> 
> At Tue Jan 22 02:24:12 2008 the virus scanner said:
>    MailScanner: Batch files are often malicious (run.bat)
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Cougaar-developers mailing list
> Cougaar-developers at cougaar.org
> http://cougaar.org/mailman/listinfo/cougaar-developers


From andreas at paleden.com  Wed Jan 23 11:22:57 2008
From: andreas at paleden.com (Andreas)
Date: Wed, 23 Jan 2008 08:22:57 -0800
Subject: Problem starting cougaar using communities
Message-ID: <20080123082257.9FDC0DB3@resin15.mta.everyone.net>

Todd,

Thanks for the information.  What I am interested in is the non-legacy community service implementation.  

The only thing I was referring to the mesh demo for was how it was started up using a separate runtime.xml and society.xml files.  I like the separation of the different information which this enables.  It was when I tried it that I no longer could run my old application and got the result in my original email.  I will try configure it to use -Dorg.cougaar.society.xsl.param.communities=true

Thanks,
Andreas



--- twright at bbn.com wrote:

From: Todd Wright <twright at bbn.com>
To: Andreas <andreas at paleden.com>
CC:  cougaar-developers at cougaar.org
Subject: Re: Problem starting cougaar using communities
Date: Tue, 22 Jan 2008 16:07:40 -0500


Communities are not required for the mesh demo.  Remove the following plugin 
from your XML file:
   org.cougaar.community.CommunityPlugin

You're correctly setting the Cougaar template property:
   -Dorg.cougaar.society.xsl.param.template=single_node
which disables the legacy community service:
   http://cougaar.cougaar.org/software/latest/OnlineManual/Templates.html

If you require the legacy community service, you can enable it by either removing:
   -Dorg.cougaar.society.xsl.param.template=single_node
or adding:
   -Dorg.cougaar.society.xsl.param.communities=legacy
This will load the service and it should find your "communities.xml".

You may also be interested in the non-legacy community service implementation, 
which can be enabled with:
   -Dorg.cougaar.society.xsl.param.template=wan
or:
   -Dorg.cougaar.society.xsl.param.communities=true
Demo "join" and "test" plugins are included with Cougaar:
http://cougaar.cougaar.org/software/latest/javadoc/core/doc/api/org/cougaar/core/agent/service/community/package-summary.html

Todd

Andreas wrote:
> ....


From andreas at paleden.com  Sat Jan 26 19:00:22 2008
From: andreas at paleden.com (Andreas)
Date: Sat, 26 Jan 2008 16:00:22 -0800
Subject: Problem starting cougaar using communities
In-Reply-To: <47965B1C.2030904@bbn.com>
References: <47947921.8080300@science.uva.nl> <47959951.1070706@paleden.com>
	<47965B1C.2030904@bbn.com>
Message-ID: <479BC996.6060008@paleden.com>

Todd or anyone else who would like to chime in,

Where can I find more information on the non-legacy community service? 

I get the impression the documentation of Cougaar Communities in the 
Cougaar Developers Guide 11.4 describes the legacy community service.

What I really quickly tried to do with my application was to 
re-configure it using the following

    <runtime>
    ...   
       
    <vm_parameter>-Dorg.cougaar.society.xsl.param.communities=true</vm_parameter>
    </runtime>

and

    <society>
        <node name="APPA">
            <agent name="DirMonAgent">
    ...      
               <!-- Community members need the CommunityPlugin but this
    is for the legacy community service so I am commenting it out
               <component class='org.cougaar.community.CommunityPlugin' />
                -->
                <!-- for the non-legacy community service I need to use
    the following -->
                <component
    class="org.cougaar.core.agent.service.community.JoinCommunity">
                    <argument name="community" value="DirMonCommunity"/>
               </component>
            </agent>
        </node>
    </society>

These are just excerpts.

When I run the application it starts up ok, but then starts sending out 
the following warning message over and over.

    Warning Trigger
    TSD:Trigger(com.appa.agent.plugin.dirmon.DLReportPlugin):null threw
    java.lang.UnsupportedOperationExcept
    ion: Only supports null or "(Role=Member)" search filter, not
    (Role=Manager)
    java.lang.UnsupportedOperationException: Only supports null or
    "(Role=Member)" search filter, not (Role=Manager)
            at
    org.cougaar.core.agent.service.community.CommunityServiceProvider$CommunityServiceImpl.searchCommunity(Commun
    ityServiceProvider.java:578)
            at
    org.cougaar.core.agent.service.community.CommunityServiceProvider$CommunityServiceImpl.search(CommunityServic
    eProvider.java:567)
    ....

One of my ABA targets was using Role=Manager.  Without the community.xml 
file no agents are defined with the role=Manager.  How do I go about 
doing this with the non-legacy service?  Is it just a matter of coding 
it into the agent load or setupSubscription methods or is there some 
kind of configuration approach?

Thanks in advance.
Andreas






Todd Wright wrote:
>
> Communities are not required for the mesh demo.  Remove the following 
> plugin from your XML file:
>   org.cougaar.community.CommunityPlugin
>
> You're correctly setting the Cougaar template property:
>   -Dorg.cougaar.society.xsl.param.template=single_node
> which disables the legacy community service:
>   http://cougaar.cougaar.org/software/latest/OnlineManual/Templates.html
>
> If you require the legacy community service, you can enable it by 
> either removing:
>   -Dorg.cougaar.society.xsl.param.template=single_node
> or adding:
>   -Dorg.cougaar.society.xsl.param.communities=legacy
> This will load the service and it should find your "communities.xml".
>
> You may also be interested in the non-legacy community service 
> implementation, which can be enabled with:
>   -Dorg.cougaar.society.xsl.param.template=wan
> or:
>   -Dorg.cougaar.society.xsl.param.communities=true
> Demo "join" and "test" plugins are included with Cougaar:
> http://cougaar.cougaar.org/software/latest/javadoc/core/doc/api/org/cougaar/core/agent/service/community/package-summary.html 
>
>
> Todd
>
> Andreas wrote:
...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://cougaar.org/pipermail/cougaar-developers/attachments/20080126/994bee9c/attachment-0001.html
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: output.txt
Url: http://cougaar.org/pipermail/cougaar-developers/attachments/20080126/994bee9c/output-0001.txt