jason-users Mailing List for jason

Hi,

Sorry for slow reply, I've been snowed under at work.

You're right, I'm building on the work you mentioned  
(http://www.iids.org/aigaion/indexempty.php?page=actionattachment&action=open&pub_id=261&location=thesis-Rogier.pdf-bfa451fd5967ae1e6b2d3d8f990dc368.pdf).

I'd thought it might be easier to use the existing ask performative,  
and use this in a send message, so that agents connected to a physical  
system in agentscape can report back data. e.g. send(sensor, ask,  
speed) so that any sensors currently existing in agentscape will  
report back values. Eventually I'm hoping to expand this out so that  
RMI type actions can be called on the physical sensor, using Jason to  
do the reasoning and then controlling sensors to improve, assert,  
disprove its belief base of what is going on in the real world.

So, a list is maintained in agentsapce of all agents, so i can use  
Map<AgentHandle, String> to =  
lookupPublished(e.getToHandle().toString()) to lift the 'to' component  
from the previous send message, which will then give me handle(s) to  
all the sensor agents in agentscape, and pass the message on.

The problem is, I can't get this message out to agentscape. I'm  
hitting the problem that Jason doesn't know that 'sensor' exists, and  
so does the sensible thing, reporting that the atom isn't valid.

Is there an easy way to override this, or will it break something in  
the jason architecture? Or a better approach?

Thanks for any suggestions!

Vin

Quoting Rafael H Bordini <r.b...@ac...>:

> Hi Vin,
>
> Jomi and I discussed this, and without knowing the details of the
> interaction of Jason and AgentScape we can only try to guess some
> possible alternatives:
>
> 1. Creating a new performative as you probably know is done completely
> on the AgentSpeak side, but if we understand correctly you'll then need
> to intercept this new performative and do something different with it
> in the Java side. For this, what you need to do is to use a customised
> AgArch class for your agents, and override the sendMsg method to use
> the super-class method for normal messages and you handle the
> askAgentScape in the way you want within your sendMsg method (with Java
> code that gets the information from AgentScape and force the replies
> into the agent mailbox, for example). There are some detail about
> architecture customisation in the Jason book, and jason.sf.net/api will
> probably help too.
>
> 2. If you have created a new Infrastructure which uses AgentScape to
> create (and possibly distribute) agents (actually, I think someone in
> the Netherlands did that, but I'm not sure), then you already have
> methods for this and you'd need to change them to handle the new
> performative.
>
> 3. Another possibility might be to use internal actions (which are
> implemented in Java) to retrieve the info from the AgentScape side and,
> e.g., add them in the agent's belief base or mailbox or however you
> want the agent to have access to the results.
>
> Sorry if this isn't helpful, but we don't know much about AgentScape
> and the details of how you interfaced it with Jason. Feel free to ask
> further questions and send more details if you think we can help.
>
> Cheers,
>
> Rafael and Jomi
>
>
>
> Vin Baines wrote:
>> Hi All,
>>
>> I'm using Jason agents in combination with the AgentScape platform,  
>>   where I've got a number of agents running in agentscape acting as  
>>   'sensors'. Jason agents are being succesfully told information by  
>>  the  agentscape agents and executing plans based upon this info,   
>> but I want to have the ability for Jason agents to query back to   
>> agentscape to  verify/assert. I've been thinking about the easiest   
>> way to do this, as a bit of java code is going to be needed to deal  
>>  with info flow  (agentscape handles & the passing of info back to   
>> jason).
>>
>> The easiest (and hopefully sensible) way I can think of doing this   
>> is  to add a new KQML performative to extend ask - e.g.   
>> askAgentScape (for the time being - this assumes the jason agent   
>> knows to ask agentscape rather than just ask! - but it would prove   
>> the concept).
>>
>> The implementation of jason inside agentscape currently doesn't   
>> handle any environments, so I can't just add new java code in there  
>>  to add  this extra functionality (e.g. as per room demo).
>>
>> So, two questions really. Where should this be added in? I'm   
>> thinking  extend jason with the functionality using agentscape   
>> classes, and then use the new jason.jar into agentscape so that the  
>>  asl files can use  something like askAgentScape(agName, value).
>>
>> Second question - does this sound a sensible way of going about it?  
>>   I'm keen to not go down a wrong hole for the 100th time..
>>
>> Thanks
>>
>> Vincent
>>
>>
>> ------------------------------------------------------------------------------
>> Crystal Reports - New Free Runtime and 30 Day Trial
>> Check out the new simplified licensing option that enables unlimited
>> royalty-free distribution of the report engine for externally   
>> facing server and web deployment.
>> http://p.sf.net/sfu/businessobjects
>> _______________________________________________
>> Jason-users mailing list
>> Jas...@li...
>> https://lists.sourceforge.net/lists/listinfo/jason-users

Iani, thanks again for discovering the bug.

the problem is fixed in the SVN and a jason.jar is available at

http://www.das.ufsc.br/~jomi/x/jason.jar

Regards,

Jomi

On Aug 24, 2009, at 9:00 PM, Iain Wallace wrote:

> I've discovered an inconsistency in the way Jason executes, depending
> on the level of verbosity selected or if the debugger is running. I'm
> not sure if what I'm trying to do is wrong, or there's a bug in Jason.
>
> I've created some simple code to reproduce the error.
>
> #debug.mas2j
> MAS debug {
>
> 	infrastructure: Centralised
>
> 	agents:
> 		test [verbose=0];
> }
>
> #test.asl
> !debug2.
>
> +!debug2 : true
> 	<- Q = done(y,a);
> 	   !debug1(Q).
>
> +!debug1(Run) : true
> 	<- !Run.
> +!done(y,a) : true
> 	<- .println("DONE!").
>
>
> The expected behaviour is the agent prints out "DONE!". However:
>
> If verbose is set to 0:
> [test] No failure event was generated for +!debug1(done(y,a))
> [source(self)]
> [test] test.asl:8: Variable 'done(y,a)' must be ground.
>
> Failure.
>
> If verbose is set to 1: - same result, failure.
>
> If verbose is set to 2, or in debug mode: success:
> [test] as2j: AgentSpeak program 'test.asl' parsed successfully!
> [test] as2j: AgentSpeak program 'jar:file:/Users/iain/Documents/ed- 
> uni-
> work/Jason-1.3/Jason.app/Contents/Resources/Java/lib/jason.jar!/asl/
> kqmlPlans.asl' parsed successfully!
> [test] percepts: []
> [test] Selected option (@l__0[source(self)] +!debug2 <- (Q =
> done(y,a)); !debug1(Q).,{}) for event +!debug2[source(self)]
> [test] Selected option (@l__1[source(self)] +!debug1(Run) <- !Run.,
> {Run=done(y,a)}) for event +!debug1(done(y,a))[source(self)]
>     !debug1(Q) / {Q=done(y,a)}
>
> [test] Selected option (@l__2[source(self)] +!done(y,a)
> <- .println("DONE!").,{}) for event +!done(y,a)[source(self)]
>     !Run / {Run=done(y,a)}
>     !debug1(Q) / {Q=done(y,a)}
>
> [test] DONE!
>
> If the behaviour is supposed to be as per verbose=2, then I will use
> that mode to continue development until there is a fix, otherwise I'll
> have to think of another way to do what I'm trying to do! (in which
> case expect a follow up email to the list!).
>
> Incidentally, this isn't the first time I've noticed a difference
> between the way Jason runs under different levels of verbosity - it's
> just the first time I've not been able to work around it, and have
> managed to isolate the problem into a simple example.
>
> Iain
>
> -- 
> The University of Edinburgh is a charitable body, registered in
> Scotland, with registration number SC005336.
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008  
> 30-Day
> trial. Simplify your report design, integration and deployment - and  
> focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Jason-users mailing list
> Jas...@li...
> https://lists.sourceforge.net/lists/listinfo/jason-users

Thanks for the reply.

For this. and any future bugs I find, would it be more helpful for me  
to submit them to the bug tracker on sourceforge (if I'm pretty sure  
it's a bug) or continue posting messages to this list? Or sign up to  
the jason-bugs list?

I'm using Jason a fair bit at the moment, and this is the 3rd bug in a  
couple of weeks I've found, so chances are I'll find some more.

Good luck in the contest, I look forward to seeing the Jason example.

Iain

On 25 Aug 2009, at 01:12, Rafael H Bordini wrote:

> Hi Iain,
>
> I can tell you that the intended behaviour is that this should work  
> ("DONE!" being printed).
>
> We know that things work differently in debug mode because the only  
> way we can do the Mind Inspecting thing is by synchronising things a  
> bit, so  debugging isn't easy if the problem you're after only  
> happens in a completely asynchronous system. But this has nothing to  
> do with the difference of behaviour in this case (it doesn't depend  
> on schedulling). I honestly can't imagine why things would work  
> differently because of the level of verbosity.
>
> If the debug info doesn't disturb you, please use verbosity=2 for  
> the time being, I'm pretty sure that's the correct behaviour. It may  
> take a while to fix this as the Multi-Agent Programming Contest is  
> very soon.
>
> Cheers,
>
> Rafael
>
>
> Iain Wallace wrote:
>> I've discovered an inconsistency in the way Jason executes,  
>> depending  on the level of verbosity selected or if the debugger is  
>> running. I'm  not sure if what I'm trying to do is wrong, or  
>> there's a bug in Jason.
>> I've created some simple code to reproduce the error.
>> #debug.mas2j
>> MAS debug {
>> 	infrastructure: Centralised
>> 	agents:
>> 		test [verbose=0];
>> }
>> #test.asl
>> !debug2.
>> +!debug2 : true
>> 	<- Q = done(y,a);
>> 	   !debug1(Q).
>> +!debug1(Run) : true
>> 	<- !Run.
>> +!done(y,a) : true
>> 	<- .println("DONE!").
>> The expected behaviour is the agent prints out "DONE!". However:
>> If verbose is set to 0:
>> [test] No failure event was generated for +!debug1(done(y,a))  
>> [source(self)]
>> [test] test.asl:8: Variable 'done(y,a)' must be ground.
>> Failure.
>> If verbose is set to 1: - same result, failure.
>> If verbose is set to 2, or in debug mode: success:
>> [test] as2j: AgentSpeak program 'test.asl' parsed successfully!
>> [test] as2j: AgentSpeak program 'jar:file:/Users/iain/Documents/ed- 
>> uni- work/Jason-1.3/Jason.app/Contents/Resources/Java/lib/ 
>> jason.jar!/asl/ kqmlPlans.asl' parsed successfully!
>> [test] percepts: []
>> [test] Selected option (@l__0[source(self)] +!debug2 <- (Q =   
>> done(y,a)); !debug1(Q).,{}) for event +!debug2[source(self)]
>> [test] Selected option (@l__1[source(self)] +!debug1(Run) <- !Run.,  
>> {Run=done(y,a)}) for event +!debug1(done(y,a))[source(self)]
>>     !debug1(Q) / {Q=done(y,a)}
>> [test] Selected option (@l__2[source(self)] +!done(y,a)   
>> <- .println("DONE!").,{}) for event +!done(y,a)[source(self)]
>>     !Run / {Run=done(y,a)}
>>     !debug1(Q) / {Q=done(y,a)}
>> [test] DONE!
>> If the behaviour is supposed to be as per verbose=2, then I will  
>> use  that mode to continue development until there is a fix,  
>> otherwise I'll  have to think of another way to do what I'm trying  
>> to do! (in which  case expect a follow up email to the list!).
>> Incidentally, this isn't the first time I've noticed a difference   
>> between the way Jason runs under different levels of verbosity -  
>> it's  just the first time I've not been able to work around it, and  
>> have  managed to isolate the problem into a simple example.
>> Iain
>


-- 
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

Hi Iain,

I can tell you that the intended behaviour is that this should work 
("DONE!" being printed).

We know that things work differently in debug mode because the only way 
we can do the Mind Inspecting thing is by synchronising things a bit, so 
  debugging isn't easy if the problem you're after only happens in a 
completely asynchronous system. But this has nothing to do with the 
difference of behaviour in this case (it doesn't depend on schedulling). 
I honestly can't imagine why things would work differently because of 
the level of verbosity.

If the debug info doesn't disturb you, please use verbosity=2 for the 
time being, I'm pretty sure that's the correct behaviour. It may take a 
while to fix this as the Multi-Agent Programming Contest is very soon.

Cheers,

Rafael


Iain Wallace wrote:
> I've discovered an inconsistency in the way Jason executes, depending  
> on the level of verbosity selected or if the debugger is running. I'm  
> not sure if what I'm trying to do is wrong, or there's a bug in Jason.
> 
> I've created some simple code to reproduce the error.
> 
> #debug.mas2j
> MAS debug {
> 
> 	infrastructure: Centralised
> 
> 	agents:
> 		test [verbose=0];
> }
> 
> #test.asl
> !debug2.
> 
> +!debug2 : true
> 	<- Q = done(y,a);
> 	   !debug1(Q).
> 
> +!debug1(Run) : true
> 	<- !Run.
> +!done(y,a) : true
> 	<- .println("DONE!").
> 
> 
> The expected behaviour is the agent prints out "DONE!". However:
> 
> If verbose is set to 0:
> [test] No failure event was generated for +!debug1(done(y,a)) 
> [source(self)]
> [test] test.asl:8: Variable 'done(y,a)' must be ground.
> 
> Failure.
> 
> If verbose is set to 1: - same result, failure.
> 
> If verbose is set to 2, or in debug mode: success:
> [test] as2j: AgentSpeak program 'test.asl' parsed successfully!
> [test] as2j: AgentSpeak program 'jar:file:/Users/iain/Documents/ed-uni- 
> work/Jason-1.3/Jason.app/Contents/Resources/Java/lib/jason.jar!/asl/ 
> kqmlPlans.asl' parsed successfully!
> [test] percepts: []
> [test] Selected option (@l__0[source(self)] +!debug2 <- (Q =  
> done(y,a)); !debug1(Q).,{}) for event +!debug2[source(self)]
> [test] Selected option (@l__1[source(self)] +!debug1(Run) <- !Run., 
> {Run=done(y,a)}) for event +!debug1(done(y,a))[source(self)]
>      !debug1(Q) / {Q=done(y,a)}
> 
> [test] Selected option (@l__2[source(self)] +!done(y,a)  
> <- .println("DONE!").,{}) for event +!done(y,a)[source(self)]
>      !Run / {Run=done(y,a)}
>      !debug1(Q) / {Q=done(y,a)}
> 
> [test] DONE!
> 
> If the behaviour is supposed to be as per verbose=2, then I will use  
> that mode to continue development until there is a fix, otherwise I'll  
> have to think of another way to do what I'm trying to do! (in which  
> case expect a follow up email to the list!).
> 
> Incidentally, this isn't the first time I've noticed a difference  
> between the way Jason runs under different levels of verbosity - it's  
> just the first time I've not been able to work around it, and have  
> managed to isolate the problem into a simple example.
> 
> Iain
> 

I've discovered an inconsistency in the way Jason executes, depending  
on the level of verbosity selected or if the debugger is running. I'm  
not sure if what I'm trying to do is wrong, or there's a bug in Jason.

I've created some simple code to reproduce the error.

#debug.mas2j
MAS debug {

	infrastructure: Centralised

	agents:
		test [verbose=0];
}

#test.asl
!debug2.

+!debug2 : true
	<- Q = done(y,a);
	   !debug1(Q).

+!debug1(Run) : true
	<- !Run.
+!done(y,a) : true
	<- .println("DONE!").


The expected behaviour is the agent prints out "DONE!". However:

If verbose is set to 0:
[test] No failure event was generated for +!debug1(done(y,a)) 
[source(self)]
[test] test.asl:8: Variable 'done(y,a)' must be ground.

Failure.

If verbose is set to 1: - same result, failure.

If verbose is set to 2, or in debug mode: success:
[test] as2j: AgentSpeak program 'test.asl' parsed successfully!
[test] as2j: AgentSpeak program 'jar:file:/Users/iain/Documents/ed-uni- 
work/Jason-1.3/Jason.app/Contents/Resources/Java/lib/jason.jar!/asl/ 
kqmlPlans.asl' parsed successfully!
[test] percepts: []
[test] Selected option (@l__0[source(self)] +!debug2 <- (Q =  
done(y,a)); !debug1(Q).,{}) for event +!debug2[source(self)]
[test] Selected option (@l__1[source(self)] +!debug1(Run) <- !Run., 
{Run=done(y,a)}) for event +!debug1(done(y,a))[source(self)]
     !debug1(Q) / {Q=done(y,a)}

[test] Selected option (@l__2[source(self)] +!done(y,a)  
<- .println("DONE!").,{}) for event +!done(y,a)[source(self)]
     !Run / {Run=done(y,a)}
     !debug1(Q) / {Q=done(y,a)}

[test] DONE!

If the behaviour is supposed to be as per verbose=2, then I will use  
that mode to continue development until there is a fix, otherwise I'll  
have to think of another way to do what I'm trying to do! (in which  
case expect a follow up email to the list!).

Incidentally, this isn't the first time I've noticed a difference  
between the way Jason runs under different levels of verbosity - it's  
just the first time I've not been able to work around it, and have  
managed to isolate the problem into a simple example.

Iain

-- 
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

Thanks for the prompt reply!

I'll maybe see if I can update my copy of Jason to the latest version  
out the repository then, as it's a useful fix to me. The workaround is  
awkward to use, as I noticed the problem due to issues with using the  
open-minded commitments, which generate a plan with .succeed_goal in  
them implicitly.

Iain

On 17 Aug 2009, at 21:39, Jomi Hubner wrote:

> Dear Iain,
>
> you are completely right in your understanding of .succeed_goal. You  
> found a bug for the case when the intention succeeds a goal of  
> itself (the intention to achieve go2 performs .succeed_goal(go2).  
> The action just after !go2 is not executed. So the workaround is to  
> put there a 'void' action, like
>
> +!go : true
> 	<- .println("1");
> 		.println("2");
> 		!go2;
>                .print; // this print will not be executed
> 		.println("3").
>
> I also fixed the bug in the source code repository at Sourceforge.
> (http://jason.sourceforge.net/faq/ 
> faq.html#SECTION00081000000000000000)
>
> Thanks for finding the bug!
>
> Jomi
>
>
> ps.: notice that this bug does not happen when an intention succeeds  
> a goal of another intention, e.g.:
>
> !go.
> !s.
>
> +!go : true
> 	<- .println("1");
> 		.println("2");
> 		!go2;
>        .println("3b");
> 		.println("3a").
> 		
> +!go2 : true
> 	<- .println("2.5");
> 		.wait(1000000);
> 		.println("2.7").
>
> +!s <- .wait(1000); .succeed_goal(go2).
>
>
>
> On Aug 17, 2009, at 12:13 PM, Iain Wallace wrote:
>
>> As far as I can tell, .succeed_goal in jason 1.3 isn't working
>> correctly (as I would expect, and as seems to be described by the  
>> book).
>>
>> I have an agent with the following test code:
>>
>> !go.
>>
>> +!go : true
>> 	<- .println("1");
>> 		.println("2");
>> 		!go2;
>> 		.println("3").
>> 		
>> +!go2 : true
>> 	<- .println("2.5");
>> 		.succeed_goal(go2);
>> 		.println("2.7").
>>
>> I would *expect* to see:
>>
>> 1
>> 2
>> 2.5
>> 3
>>
>> But what I actually get is:
>>
>> 1
>> 2
>> 2.5
>>
>> Even although only go2 is told to succeed, go finishes too, without
>> completing.
>>
>> Am I misunderstanding the correct operation here (book page 168/9),  
>> or
>> is this a bug? If so, can you suggest a workaround?
>>
>>
>> Iain
>>
>> -- 
>> The University of Edinburgh is a charitable body, registered in
>> Scotland, with registration number SC005336.
>>
>>
>> ------------------------------------------------------------------------------
>> Let Crystal Reports handle the reporting - Free Crystal Reports  
>> 2008 30-Day
>> trial. Simplify your report design, integration and deployment -  
>> and focus on
>> what you do best, core application coding. Discover what's new with
>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>> _______________________________________________
>> Jason-users mailing list
>> Jas...@li...
>> https://lists.sourceforge.net/lists/listinfo/jason-users
>
>


-- 
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

Dear Iain,

you are completely right in your understanding of .succeed_goal. You  
found a bug for the case when the intention succeeds a goal of itself  
(the intention to achieve go2 performs .succeed_goal(go2). The action  
just after !go2 is not executed. So the workaround is to put there a  
'void' action, like

+!go : true
	<- .println("1");
		.println("2");
		!go2;
                 .print; // this print will not be executed
		.println("3").

I also fixed the bug in the source code repository at Sourceforge.
(http://jason.sourceforge.net/faq/faq.html#SECTION00081000000000000000)

Thanks for finding the bug!

Jomi


ps.: notice that this bug does not happen when an intention succeeds a  
goal of another intention, e.g.:

!go.
!s.

+!go : true
	<- .println("1");
		.println("2");
		!go2;
         .println("3b");
		.println("3a").
		
+!go2 : true
	<- .println("2.5");
		.wait(1000000);
		.println("2.7").

+!s <- .wait(1000); .succeed_goal(go2).



On Aug 17, 2009, at 12:13 PM, Iain Wallace wrote:

> As far as I can tell, .succeed_goal in jason 1.3 isn't working
> correctly (as I would expect, and as seems to be described by the  
> book).
>
> I have an agent with the following test code:
>
> !go.
>
> +!go : true
> 	<- .println("1");
> 		.println("2");
> 		!go2;
> 		.println("3").
> 		
> +!go2 : true
> 	<- .println("2.5");
> 		.succeed_goal(go2);
> 		.println("2.7").
>
> I would *expect* to see:
>
> 1
> 2
> 2.5
> 3
>
> But what I actually get is:
>
> 1
> 2
> 2.5
>
> Even although only go2 is told to succeed, go finishes too, without
> completing.
>
> Am I misunderstanding the correct operation here (book page 168/9), or
> is this a bug? If so, can you suggest a workaround?
>
>
> Iain
>
> -- 
> The University of Edinburgh is a charitable body, registered in
> Scotland, with registration number SC005336.
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008  
> 30-Day
> trial. Simplify your report design, integration and deployment - and  
> focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Jason-users mailing list
> Jas...@li...
> https://lists.sourceforge.net/lists/listinfo/jason-users

As far as I can tell, .succeed_goal in jason 1.3 isn't working  
correctly (as I would expect, and as seems to be described by the book).

I have an agent with the following test code:

!go.

+!go : true
	<- .println("1");
		.println("2");
		!go2;
		.println("3").
		
+!go2 : true
	<- .println("2.5");
		.succeed_goal(go2);
		.println("2.7").

I would *expect* to see:

1
2
2.5
3

But what I actually get is:

1
2
2.5

Even although only go2 is told to succeed, go finishes too, without  
completing.

Am I misunderstanding the correct operation here (book page 168/9), or  
is this a bug? If so, can you suggest a workaround?


Iain

-- 
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

Hi Pennee,

It seems to problem is related to the 'AUTO_INCREMENT' option (or  
primary keys). If it is possible for your application, do not create  
the table by hand, let the JDBCBelBase to create one. In the case you  
are using a 'legacy' table with keys and auto_increment, you need to  
customise the JDBCBelBase for your requirements (there are methods  
responsible for the generation of SQL commands). The default  
implementation, afair, does not support them.

Another option, if other users need this kind of feature, is to  
discuss a general solution, implement it, and include in the next  
Jason distribution.

HTH,

Jomi

On Aug 4, 2009, at 8:46 AM, Pennee Wangmaeteekul wrote:

> Hi,
>
> I got an update problem after I tried to immitate the code on page  
> 158 in Jason Book.
>
> +someevent : author(Id,"Morgana",Email) <- -+author(Id, "Morgana","x...@ac... 
> ")
>
> For the code that I wrote in .mas2j file is
>
> ****************
> MAS testupdate {
>     infrastructure: Centralised
>     agents:
>         a beliefBaseClass jason.bb.JDBCPersistentBB(
>     "com.mysql.jdbc.Driver",
>     "jdbc:mysql://localhost/test",
>     "root",
>     "xyzxyz",
>     "[exam_exec(3,example)]");
> }
> ****************
> in .asl file is
>
> !someevent.
> +!someevent:exam_exec(Id,"Pennee",Email)<-
> .findall(data(Id,Email),exam_exec(Id,"Pennee",Email),L); .print(L);
> -+exam_exec(Id,"Pennee","ky...@gm...").
>
> ******************
> and sql syntaxs which I used to create the table and insert data are:
>
> create table example ( id INT NOT NULL AUTO_INCREMENT, PRIMARY  
> KEY(id), name varchar(10), email varchar(15));
> insert into example (name, email) values ("Pennee","pe...@gm...");
> ********************
>  After I ran the program, MAS Console appeared the following messages:
>
> a] [data(1,"pe...@gm...")]
> [JDBCPersistentBB] SQL Error
> com 
> .mysql 
> .jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException:  
> Duplicate entry '1' for key 1
>  at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native  
> Method)
>  at  
> sun 
> .reflect 
> .NativeConstructorAccessorImpl 
> .newInstance(NativeConstructorAccessorImpl.java:39)
>  at  
> sun 
> .reflect 
> .DelegatingConstructorAccessorImpl 
> .newInstance(DelegatingConstructorAccessorImpl.java:27)
>  at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
>  at com.mysql.jdbc.Util.handleNewInstance(Util.java:406)
>  at com.mysql.jdbc.Util.getInstance(Util.java:381)
>  at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1015)
>  at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956)
>  at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3536)
>  at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3468)
>  at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1957)
>  at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2107)
>  at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2642)
>  at com.mysql.jdbc.StatementImpl.executeUpdate(StatementImpl.java: 
> 1634)
>  at com.mysql.jdbc.StatementImpl.executeUpdate(StatementImpl.java: 
> 1553)
>  at jason.bb.JDBCPersistentBB.add(JDBCPersistentBB.java:262)
>  at jason.asSemantics.Agent.brf(Agent.java:605)
>  at  
> jason 
> .asSemantics.TransitionSystem.applyExecInt(TransitionSystem.java:586)
>  at  
> jason 
> .asSemantics 
> .TransitionSystem.applySemanticRule(TransitionSystem.java:136)
>  at  
> jason 
> .asSemantics.TransitionSystem.reasoningCycle(TransitionSystem.java: 
> 947)
>  at  
> jason.infra.centralised.CentralisedAgArch.run(CentralisedAgArch.java: 
> 197)
>  at java.lang.Thread.run(Thread.java:619)
> ******************************
>
> How should I solve this update problem? Or I ignore in some steps.
>
> Thank you for any advices,
>
> Regards,
> Pennee
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008  
> 30-Day
> trial. Simplify your report design, integration and deployment - and  
> focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july_______________________________________________
> Jason-users mailing list
> Jas...@li...
> https://lists.sourceforge.net/lists/listinfo/jason-users

Hi,

I got an update problem after I tried to immitate the code on page 158 in
Jason Book.

+someevent : author(Id,"Morgana",Email) <- -+author(Id, "Morgana","
x...@ac...")

For the code that I wrote in .mas2j file is

****************
MAS testupdate {
    infrastructure: Centralised
    agents:
        a beliefBaseClass jason.bb.JDBCPersistentBB(
    "com.mysql.jdbc.Driver",
    "jdbc:mysql://localhost/test",
    "root",
    "xyzxyz",
    "[exam_exec(3,example)]");
}
****************
in .asl file is

!someevent.
+!someevent:exam_exec(Id,"Pennee",Email)<-
.findall(data(Id,Email),exam_exec(Id,"Pennee",Email),L); .print(L);
-+exam_exec(Id,"Pennee","ky...@gm...").

******************
and sql syntaxs which I used to create the table and insert data are:

create table example ( id INT NOT NULL AUTO_INCREMENT, PRIMARY KEY(id), name
varchar(10), email varchar(15));
insert into example (name, email) values ("Pennee","pe...@gm...");
********************
 After I ran the program, MAS Console appeared the following messages:

a] [data(1,"pe...@gm...")]
[JDBCPersistentBB] SQL Error
com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException:
Duplicate entry '1' for key 1
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
 at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
 at com.mysql.jdbc.Util.handleNewInstance(Util.java:406)
 at com.mysql.jdbc.Util.getInstance(Util.java:381)
 at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1015)
 at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956)
 at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3536)
 at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3468)
 at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1957)
 at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2107)
 at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2642)
 at com.mysql.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1634)
 at com.mysql.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1553)
 at jason.bb.JDBCPersistentBB.add(JDBCPersistentBB.java:262)
 at jason.asSemantics.Agent.brf(Agent.java:605)
 at
jason.asSemantics.TransitionSystem.applyExecInt(TransitionSystem.java:586)
 at
jason.asSemantics.TransitionSystem.applySemanticRule(TransitionSystem.java:136)
 at
jason.asSemantics.TransitionSystem.reasoningCycle(TransitionSystem.java:947)
 at
jason.infra.centralised.CentralisedAgArch.run(CentralisedAgArch.java:197)
 at java.lang.Thread.run(Thread.java:619)
******************************

How should I solve this update problem? Or I ignore in some steps.

Thank you for any advices,

Regards,
Pennee