<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to bugs</title><link>https://sourceforge.net/p/ist-contract/bugs/</link><description>Recent changes to bugs</description><atom:link href="https://sourceforge.net/p/ist-contract/bugs/feed.rss" rel="self"/><language>en</language><lastBuildDate>Tue, 30 Sep 2008 09:26:57 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/ist-contract/bugs/feed.rss" rel="self" type="application/rss+xml"/><item><title>References from client stubs to nonexisting operations in AE</title><link>https://sourceforge.net/p/ist-contract/bugs/24/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;In the AgentEndpoint client stub remain references to operations no longer existing in AgentEndpoint, e.g. receiveInput, etc. The stubs should reflect the current status od AE, obsolete operations should be removed to prevent their generation by wsimport.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jiri Biba</dc:creator><pubDate>Tue, 30 Sep 2008 09:26:57 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net19d366a9e2c15bc0783a1905d0f0d6324135b36b</guid></item><item><title>corrupted AgentWebServiceLib.jar</title><link>https://sourceforge.net/p/ist-contract/bugs/23/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;When just adding the AgentWebServiceLib.jar to a list of libraries of a web application, it is not possible to deploy such application to glassfish server. It seems that it prays for some libraries necessary for modules that are absolutely unnecessary for just connection to AgentEndPoint and simple communication to the agents. Adding all jar files from ContractLibraries does not solve the problem because of two reasons: there are redundant files, and the amount of files is too huge to fit to memory. &lt;/p&gt;
&lt;p&gt;Suggested solution:&lt;br /&gt;
Step 1: include all libraries necessary for AgentWebServiceLib into its distribution.&lt;br /&gt;
Step 2: provide light interface for communication with agents instead of huge holistic and impossible to use library (see &lt;a href="http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=2137564&amp;amp;group_id=206620&amp;amp;atid=998331"&gt;http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=2137564&amp;amp;group_id=206620&amp;amp;atid=998331&lt;/a&gt; and &lt;a href="http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=2137651&amp;amp;group_id=206620&amp;amp;atid=998331\"&gt;http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=2137651&amp;amp;group_id=206620&amp;amp;atid=998331\&lt;/a&gt;) &lt;/p&gt;
&lt;p&gt;Attachment: console printout of glassfish&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jiri Hodik</dc:creator><pubDate>Tue, 30 Sep 2008 06:59:43 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net7f46a52358efe2c1b8656d1cc8d3a156cead04c5</guid></item><item><title>AgentWSGui deployment failure</title><link>https://sourceforge.net/p/ist-contract/bugs/22/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;AgentWSGui fails to deploy due to some problems with corrupted fakeimport.jar, though the jar does not seem to be corrupted anyhow. See the log + ziped AgentWSGui project (excluded all libraries to save megabytes).&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jiri Biba</dc:creator><pubDate>Wed, 24 Sep 2008 06:19:39 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netaa268832e18cb45403b3cb2584d31c6b2383abeb</guid></item><item><title>JAVA_HOME exceptions + 100% processor load on linux</title><link>https://sourceforge.net/p/ist-contract/bugs/21/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;When running a ToyExample, the negotiation is finished and the workflow is supposed to be loaded, the execution ends up with:&lt;/p&gt;
&lt;p&gt;Caused by: /home/biba/svnroot/sourceforge/TechnologyDemo/trunk/ContractWorkflow/PurchaserWS/nbproject/build-impl.xml:215: Unable to find a javac compiler;&lt;br /&gt;
com.sun.tools.javac.Main is not on the classpath.&lt;br /&gt;
Perhaps JAVA_HOME does not point to the JDK.&lt;br /&gt;
It is currently set to "/usr/java/jdk1.6.0_06/jre"&lt;/p&gt;
&lt;p&gt;Though, JAVA_HOME is set to "/usr/java/jdk1.6.0" which is a link to "/usr/java/jdk1.6.0_06". Where does the "/jre" string come from?&lt;/p&gt;
&lt;p&gt;Besides, during the demo run the glassfish consumes 100% of processor resources and can be only killed from the system. Attaching log.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jiri Biba</dc:creator><pubDate>Wed, 24 Sep 2008 06:09:49 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netf60ae12f41bf553d2ef5208fe781853ee6feda99</guid></item><item><title>AgentWSGui/Monitor buggy behaviour of combobox+button</title><link>https://sourceforge.net/p/ist-contract/bugs/20/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;There seems to be a GUI bug in AgentWSGui/Monitor tab - when creating second or further agent, the AgentEndpoint.createAgent() seems to be invoked just after a mere item change in the combobox instead of after clicking the Monitor button. This perhaps causes another error which occurs on chosing an agent in the combobox which has been already created - this results in "Error in getAgents(): [The call failed on the server; see server log for details]". Moreover, the glassfish totally consumes all processor resources. The log file attached.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jiri Biba</dc:creator><pubDate>Wed, 24 Sep 2008 05:56:41 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net630c8590ceeed019dccdcd0780cd9d58b80b6ae4</guid></item><item><title>Concurrent modification conflict in AgentEndpoint</title><link>https://sourceforge.net/p/ist-contract/bugs/19/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The functionality of the method AgentEndpoint.provideData(…) is not clear. As it is provided as an interface of an agent there is either concurrent modification conflict or unpredictable data loosing. In a very special situation when the agent puts some data to its RuntimeDataHolder under some key (e.g., "TopSecretDataForBebe") and somebody else rewrite them using provideData("TopSecretDataForBebe", ...) before Bebe’s application requests them (using requestData("TopSecretDataForBebe", ...), the data read by Bebe are the data altered by someone else but they seem to be the data from the agent.&lt;/p&gt;
&lt;p&gt;This is not problem only in intended data forging, such functionality may be critical e.g. during review when random events supported by “magic numbers” in code may invoke emergent behavior of the system that we have not seen before :o)&lt;br /&gt;
&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jiri Hodik</dc:creator><pubDate>Tue, 23 Sep 2008 14:15:14 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netfb8f233daa3053bfb5604ba351e176d863b72cd9</guid></item><item><title>AgentWS build fails on windows (target "jar")</title><link>https://sourceforge.net/p/ist-contract/bugs/18/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Persisting build problem on windows - "ant jar" fails on java.io.IOException: Cannot run program "c:\Program Files\Java\jdk1.6.0\jre\bin\java.exe": CreateProcess error=87, The parameter is incorrect&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jiri Biba</dc:creator><pubDate>Thu, 18 Sep 2008 14:16:13 -0000</pubDate><guid isPermaLink="false">https://sourceforge.neta5bd980a838c429570fff0183b9b3dbf754ec68b</guid></item><item><title>Exceptions on agent creation</title><link>https://sourceforge.net/p/ist-contract/bugs/17/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;There is a number of exceptions which remain unresolved and continue to be printed out for quite a time. Those exceptions which cannot be resolved should remain reported, but should be done in a more conscise form than printStackTrace (e.g. just one-line report.). The same holds for other pending exceptions waiting for resolution. This particularly regards exceptions from statefu web service implementation, workflow manager initialization, management client intialization and message processing in dialogue manager - see the attached log.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jiri Biba</dc:creator><pubDate>Wed, 17 Sep 2008 10:47:14 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net9a3aa428c0d8efbed2ef9410ba0e4f62db8e56a7</guid></item><item><title>java.lang.NullPointerException in evaluationPropertyAlias</title><link>https://sourceforge.net/p/ist-contract/bugs/16/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;When BPELs processes are deployes in the sama machine (localhost), some notification failures to the BPEL processes are preventing the BPEL scripts from complete execution, causing the abort of the workflow through an exit activity. Basically the BPELs scrips behave as notifications were not sent and the respective timeouts associated to the onAlarm activities expire.&lt;/p&gt;
&lt;p&gt;This bug seems not affecting the BPEL execution, whenever the two BPELs script are deployed in different machines.&lt;br /&gt;
&lt;/p&gt;
&lt;p&gt;Stack Trace from the server.log&lt;/p&gt;
&lt;p&gt;glassfish version: Sun Java System Application Server 9.1_02 (build b04-fcs)&lt;br /&gt;
jbi version: OPEN ESB v2&lt;/p&gt;
&lt;p&gt;[#|2008-07-22T18:49:27.629+0200|WARNING|sun-appserver9.1|com.sun.jbi.engine.bpel.BPELSEInOutThread|_ThreadID=28;_ThreadName=BPELSEInOutThread9;_RequestID=d5136c03-754d-4e90-a8e7-9f0a7be33cd7;|BPJBI-6010:Failed to process In Only Message M Ex 134773100246850-5464-134360381676280074&lt;br /&gt;
java.lang.NullPointerException&lt;br /&gt;
at com.sun.jbi.engine.bpel.core.bpel.engine.impl.CorrelationManagerImpl.evaluatePropertyAlias(CorrelationManagerImpl.java:243)&lt;br /&gt;
at com.sun.jbi.engine.bpel.core.bpel.engine.impl.CorrelationManagerImpl.evaluateVals(CorrelationManagerImpl.java:211)&lt;br /&gt;
at com.sun.jbi.engine.bpel.core.bpel.engine.impl.CorrelationManagerImpl.getCorrIds(CorrelationManagerImpl.java:306)&lt;br /&gt;
at com.sun.jbi.engine.bpel.core.bpel.engine.impl.CorrelationManagerImpl.getCorrelateOnlyIDs(CorrelationManagerImpl.java:103)&lt;br /&gt;
at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.handleRequest(BPELProcessManagerImpl.java:1116)&lt;br /&gt;
at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.handleEvent(BPELProcessManagerImpl.java:279)&lt;br /&gt;
at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:1313)&lt;br /&gt;
at com.sun.jbi.engine.bpel.BPELSEInOutThread.processRequest(BPELSEInOutThread.java:632)&lt;br /&gt;
at com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:305)&lt;br /&gt;
at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:191)&lt;br /&gt;
|#]&lt;/p&gt;
&lt;p&gt;[#|2008-07-22T18:49:27.632+0200|WARNING|sun-appserver9.1|com.sun.jbi.engine.bpel.BPELSEHelper|_ThreadID=28;_ThreadName=BPELSEInOutThread9;_RequestID=d5136c03-754d-4e90-a8e7-9f0a7be33cd7;|BPJBI-6001:Sending ERROR status (Service Name = {http://www.ist-contract.org/services/bpel/SupplierService}PaymentReceivedPL, Endpoint Name = PaymentAcceptedRole_myRole, Operation Name = {http://www.ist-contract.org/services/wsdl/PaymentStatus}paymentAccepted, Message Exchange Id = 134773100246850-5464-134360381676280074)&lt;br /&gt;
Error properties&lt;br /&gt;
com.sun.jbi.crl.faultcode = Server&lt;br /&gt;
com.sun.jbi.crl.faultstring = null&lt;br /&gt;
com.sun.jbi.crl.faultactor = sun-bpel-engine&lt;br /&gt;
com.sun.jbi.crl.faultdetail =&lt;br /&gt;
null&lt;br /&gt;
java.lang.NullPointerException&lt;br /&gt;
at com.sun.jbi.engine.bpel.core.bpel.engine.impl.CorrelationManagerImpl.evaluatePropertyAlias(CorrelationManagerImpl.java:243)&lt;br /&gt;
at com.sun.jbi.engine.bpel.core.bpel.engine.impl.CorrelationManagerImpl.evaluateVals(CorrelationManagerImpl.java:211)&lt;br /&gt;
at com.sun.jbi.engine.bpel.core.bpel.engine.impl.CorrelationManagerImpl.getCorrIds(CorrelationManagerImpl.java:306)&lt;br /&gt;
at com.sun.jbi.engine.bpel.core.bpel.engine.impl.CorrelationManagerImpl.getCorrelateOnlyIDs(CorrelationManagerImpl.java:103)&lt;br /&gt;
at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.handleRequest(BPELProcessManagerImpl.java:1116)&lt;br /&gt;
at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.handleEvent(BPELProcessManagerImpl.java:279)&lt;br /&gt;
at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:1313)&lt;br /&gt;
at com.sun.jbi.engine.bpel.BPELSEInOutThread.processRequest(BPELSEInOutThread.java:632)&lt;br /&gt;
at com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:305)&lt;br /&gt;
at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:191)&lt;br /&gt;
|#]&lt;/p&gt;
&lt;p&gt;[#|2008-07-22T18:49:27.634+0200|SEVERE|sun-appserver9.1|sun-http-binding.com.sun.jbi.httpsoapbc.OutboundMessageProcessor|_ThreadID=36;_ThreadName=HTTPBC-OutboundReceiver-3;_RequestID=5e0b23f4-026e-4b2e-8eb6-d05777f7fdc4;|HTTPBC-E00721: Provider for service [{http://www.ist-contract.org/services/wsdl/PaymentStatus}PaymentStatusService] endpoint [PaymentAcceptedPort] responded with an error status. No detail was provided.|#]&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">rconfalonieri</dc:creator><pubDate>Wed, 23 Jul 2008 16:18:05 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net7f5df7812e45133386ce988efc616e7586ae655b</guid></item><item><title>bug in OntologyLibrary - unable to unmarshal message content</title><link>https://sourceforge.net/p/ist-contract/bugs/15/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I finally hunted down the reason for the VoidConcept appearing in the received message in my Subscribe protocol. The XML content received is OK and corresponds to the ObservationSubscription class. The problem occurs when the OntologyLibrary.getOntologyConcept() attempts to unmarshal it - it reports that the ontology is unknown - basically, if not placed in the edu.upc.lsi.kemlg.aws.input.domain package, it cannot be unmarshalled. The workaround is to use this package for the message contents defined in AWSPlatformBuilders, yet, it should have used the package specified in the agent.xml in the &lt;br /&gt;
&amp;lt;tns:Ontology&amp;gt;&lt;br /&gt;
&amp;lt;tns:package&amp;gt;ontology&amp;lt;/tns:package&amp;gt;&lt;br /&gt;
&amp;lt;/tns:Ontology&amp;gt;&lt;br /&gt;
The workaround can be used now, but this should be fixed. BTW: what is the reason for using the DOMParser instead of the JAXB for unmarshalling?&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jiri Biba</dc:creator><pubDate>Tue, 17 Jun 2008 13:56:02 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net7fe86be8ad278349c614103ebb24b02125a533d0</guid></item></channel></rss>