<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to bugs</title><link href="https://sourceforge.net/p/genesys-mw/bugs/" rel="alternate"/><link href="https://sourceforge.net/p/genesys-mw/bugs/feed.atom" rel="self"/><id>https://sourceforge.net/p/genesys-mw/bugs/</id><updated>2004-08-24T08:18:34Z</updated><subtitle>Recent changes to bugs</subtitle><entry><title>SupervisionResponseRenderer stopVisualisation never called</title><link href="https://sourceforge.net/p/genesys-mw/bugs/9/" rel="alternate"/><published>2004-08-24T08:18:34Z</published><updated>2004-08-24T08:18:34Z</updated><author><name>Balazs Pataki</name><uri>https://sourceforge.net/u/patakib/</uri></author><id>https://sourceforge.net0fdb7e2abaeb0c7de037f5685fc81a8df48ea87d</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I just found that the startVisualisation() method is&lt;br /&gt;
always called when I do a Query in the Generic console,&lt;br /&gt;
but the matching stopVisualization() is never gets&lt;br /&gt;
called. This causes problems, because the renderers&lt;br /&gt;
(following the examples) have the following as their&lt;br /&gt;
start/stopVisualisation() code:&lt;/p&gt;
&lt;p&gt;public void startVisualization() {&lt;br /&gt;
log().debug( "startVisualization(): entering" );&lt;br /&gt;
this.msgStorage.addChangeListener( this,&lt;br /&gt;
this.messageCategory );&lt;br /&gt;
}&lt;/p&gt;
&lt;p&gt;public void stopVisualization() {&lt;br /&gt;
log().debug( "startVisualization(): entering" );&lt;br /&gt;
this.msgStorage.removeChangeListener( this );&lt;br /&gt;
}&lt;/p&gt;
&lt;p&gt;Since stopVisualization() is never called, the renderer&lt;br /&gt;
is never removed from the change listener array and&lt;br /&gt;
therefore with the first query storageChanged() is&lt;br /&gt;
called once, with the second query it is called twice&lt;br /&gt;
and so on.&lt;/p&gt;
&lt;p&gt;It is not clear for me now how&lt;br /&gt;
start/stopVisualisation() is supposed to be used. As a&lt;br /&gt;
workarond I put the addChangeListener() into another&lt;br /&gt;
method of the renderer.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>The size of server-config.wsdd increases every time</title><link href="https://sourceforge.net/p/genesys-mw/bugs/8/" rel="alternate"/><published>2004-08-09T16:21:52Z</published><updated>2004-08-09T16:21:52Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net2c10cdbff0d3bb7d222a52ba6adff66a620ec58b</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The size of &amp;lt;server-config.wsdd&amp;gt; file (that is&lt;br /&gt;
generated automatically in &amp;lt;.../bin&amp;gt; folder) increases&lt;br /&gt;
each time when component starts.&lt;br /&gt;
Namely, each &amp;lt;typeMapping ...&amp;gt; element presented in&lt;br /&gt;
original &amp;lt;.../conf/server-config.wsdd&amp;gt; (there are five&lt;br /&gt;
initially) is being repeated every start.&lt;/p&gt;
&lt;p&gt;As a result, the size of &amp;lt;server-config.wsdd&amp;gt; increases&lt;br /&gt;
by ~2Kb after each start.&lt;/p&gt;
&lt;p&gt;See in attach sample of &amp;lt;.../bin/server-config.wsdd&amp;gt; of&lt;br /&gt;
Sample Delegate Agent (2.0.1) after the third start.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Problem with phantom agents in console</title><link href="https://sourceforge.net/p/genesys-mw/bugs/7/" rel="alternate"/><published>2004-07-23T10:46:00Z</published><updated>2004-07-23T10:46:00Z</updated><author><name>Balazs Pataki</name><uri>https://sourceforge.net/u/patakib/</uri></author><id>https://sourceforge.netbc2bc4d31db4dc477ffca4368efa4b2dfaf13fde</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;While testing my agent I sometimes forgot to unregister&lt;br /&gt;
it from the core, so there are some agents registered&lt;br /&gt;
that are not active anymore. These agents are listed in&lt;br /&gt;
the Generic Console, when I search my agent by NAME.&lt;br /&gt;
This is OK so far.&lt;/p&gt;
&lt;p&gt;The problem is that I can still invoke Query and&lt;br /&gt;
Subscribe on messages of phantom agents and these&lt;br /&gt;
messages are routed to the only real agents that is&lt;br /&gt;
actually running. The agents listed in the left column&lt;br /&gt;
all have different Component ID-s so I should get an&lt;br /&gt;
error that the agent with this ID is unavailable.&lt;/p&gt;
&lt;p&gt;Even if I Query my really working agent the result of&lt;br /&gt;
the query appears in the message view of all other&lt;br /&gt;
(phantom) agents.&lt;/p&gt;
&lt;p&gt;So, if I do a "Heartbeat" query in one agent, the&lt;br /&gt;
result will appear under the "Heartbeat" of all other&lt;br /&gt;
agents, which have Heartbeat registered.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>./client_deploy.xml hard coded into SoapClientUtil</title><link href="https://sourceforge.net/p/genesys-mw/bugs/6/" rel="alternate"/><published>2004-07-22T12:25:29Z</published><updated>2004-07-22T12:25:29Z</updated><author><name>Balazs Pataki</name><uri>https://sourceforge.net/u/patakib/</uri></author><id>https://sourceforge.nete21a239405d63dd3f8a60d0204f9d5f4dce3ae7c</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;In eu.genesys.v2.kernel.messaging.SoapClientUtil the&lt;br /&gt;
reference to ./client_deploy.xml is hard coded into the&lt;br /&gt;
static initializer:&lt;/p&gt;
&lt;p&gt;static {&lt;br /&gt;
//Deploy the AXIS client configuration&lt;br /&gt;
try {&lt;br /&gt;
// TODO: use system properties for that&lt;br /&gt;
org.apache.axis.utils.Admin.main( new String[]&lt;br /&gt;
{ "client", "./client_deploy.xml" } );&lt;br /&gt;
service = new Service();&lt;br /&gt;
callsMap = new HashMap();&lt;br /&gt;
}&lt;br /&gt;
// TODO: catch the proper exception here&lt;br /&gt;
catch( Exception e ) {&lt;br /&gt;
log().error("Cannot deploy the AXIS client&lt;br /&gt;
configuration.", e);&lt;br /&gt;
}&lt;br /&gt;
}// static&lt;/p&gt;
&lt;p&gt;As the TODO suggests, it should be configurable via the&lt;br /&gt;
agent's .properties file.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Agent tree view not sscrollable</title><link href="https://sourceforge.net/p/genesys-mw/bugs/5/" rel="alternate"/><published>2004-07-22T08:30:21Z</published><updated>2004-07-22T08:30:21Z</updated><author><name>Balazs Pataki</name><uri>https://sourceforge.net/u/patakib/</uri></author><id>https://sourceforge.netce9a1172871ff238908fe4b08fe211358bfc2091</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The agent tree view in the console cannot be scrolled,&lt;br /&gt;
so if one has many agents, those at the end of the list&lt;br /&gt;
cannot be reached. &lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Header timestamp not updated with queries</title><link href="https://sourceforge.net/p/genesys-mw/bugs/4/" rel="alternate"/><published>2004-07-22T08:25:18Z</published><updated>2004-07-22T08:25:18Z</updated><author><name>Balazs Pataki</name><uri>https://sourceforge.net/u/patakib/</uri></author><id>https://sourceforge.netedb5a94231ae88f5338d56c1c5b8fe138fad9eb2</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Is the timestamp correctly set in supervision response&lt;br /&gt;
headers by the Java adapter?&lt;/p&gt;
&lt;p&gt;I tried the following: from the console I Querried a&lt;br /&gt;
Sample agent for Heartbeat mbelow. As you can see the&lt;br /&gt;
console shows the same Timestamp for every message&lt;br /&gt;
while the value in the &amp;lt;supervisionResponse&amp;gt; is&lt;br /&gt;
essages. I did it three times and received the&lt;br /&gt;
responses always updated. Shouldn't the header&lt;br /&gt;
timestamp update as well? I haven't checked if it is a&lt;br /&gt;
problem with the console (displays wrong header value)&lt;br /&gt;
or with the adapter (doesn't update the timestamp field).&lt;/p&gt;
&lt;p&gt;1.&lt;/p&gt;
&lt;p&gt;Supervision response:&lt;/p&gt;
&lt;p&gt;Header:&lt;br /&gt;
{eu.genesys.v2.kernel.messaging.GenesysHeaderBlock=&lt;br /&gt;
Header :&lt;br /&gt;
Source : 1.0.0.d7e3a87e-100007f-b17e0a-72a16fd4&lt;br /&gt;
Destination : 1.0.0.bd91a064-100007f-166ff9c-670e9ade&lt;br /&gt;
Timestamp : 1090423878909&lt;br /&gt;
}&lt;/p&gt;
&lt;p&gt;Response:&lt;br /&gt;
&amp;lt;?xml version="1.0" encoding="UTF-8"?&amp;gt;&lt;br /&gt;
&amp;lt;supervisionResponse&lt;br /&gt;
xmlns="http://genesys-project.org/xsd/encoding/gse/GenesysEncoding"&amp;gt;1090424494901&amp;lt;/supervisionResponse&amp;gt;&lt;/p&gt;
&lt;p&gt;2.&lt;/p&gt;
&lt;p&gt;Supervision response:&lt;/p&gt;
&lt;p&gt;Header:&lt;br /&gt;
{eu.genesys.v2.kernel.messaging.GenesysHeaderBlock=&lt;br /&gt;
Header :&lt;br /&gt;
Source : 1.0.0.d7e3a87e-100007f-b17e0a-72a16fd4&lt;br /&gt;
Destination : 1.0.0.bd91a064-100007f-166ff9c-670e9ade&lt;br /&gt;
Timestamp : 1090423878909&lt;br /&gt;
}&lt;/p&gt;
&lt;p&gt;Response:&lt;br /&gt;
&amp;lt;?xml version="1.0" encoding="UTF-8"?&amp;gt;&lt;br /&gt;
&amp;lt;supervisionResponse&lt;br /&gt;
xmlns="http://genesys-project.org/xsd/encoding/gse/GenesysEncoding"&amp;gt;1090424497079&amp;lt;/supervisionResponse&amp;gt;&lt;/p&gt;
&lt;p&gt;3.&lt;/p&gt;
&lt;p&gt;Supervision response:&lt;/p&gt;
&lt;p&gt;Header:&lt;br /&gt;
{eu.genesys.v2.kernel.messaging.GenesysHeaderBlock=&lt;br /&gt;
Header :&lt;br /&gt;
Source : 1.0.0.d7e3a87e-100007f-b17e0a-72a16fd4&lt;br /&gt;
Destination : 1.0.0.bd91a064-100007f-166ff9c-670e9ade&lt;br /&gt;
Timestamp : 1090423878909&lt;br /&gt;
}&lt;/p&gt;
&lt;p&gt;Response:&lt;br /&gt;
&amp;lt;?xml version="1.0" encoding="UTF-8"?&amp;gt;&lt;br /&gt;
&amp;lt;supervisionResponse&lt;br /&gt;
xmlns="http://genesys-project.org/xsd/encoding/gse/GenesysEncoding"&amp;gt;1090424511160&amp;lt;/supervisionResponse&amp;gt;&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Problems with blanks in path to &amp;lt;component&amp;gt;.properties file</title><link href="https://sourceforge.net/p/genesys-mw/bugs/3/" rel="alternate"/><published>2003-11-19T12:54:14Z</published><updated>2003-11-19T12:54:14Z</updated><author><name>Vladimir Voloshinov</name><uri>https://sourceforge.net/u/vladimirvv/</uri></author><id>https://sourceforge.net6c03bf708519fa196c398d3b008468b6bc1df368</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Standard GeneSyS &amp;amp;quot;save properties&amp;amp;quot; utility fails to save &lt;br /&gt;
propertis to /conf/*.properties file if its full path contains &lt;br /&gt;
blanks.&lt;/p&gt;
&lt;p&gt;Find in attachment log.txt and console output - the result &lt;br /&gt;
of attempt to run &lt;br /&gt;
&amp;amp;lt;registerSampleAgent.bat&amp;amp;gt; in case when&lt;br /&gt;
SAMPLE AGENT has been installed in the folder &lt;br /&gt;
&amp;amp;quot;D:\GeneSyS\sourceforge\my files\sample-&lt;br /&gt;
agent&amp;amp;quot;.&lt;/p&gt;
&lt;p&gt;Registration had passed successfully, but agent execution &lt;br /&gt;
failed.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Monitoring Console execution fails</title><link href="https://sourceforge.net/p/genesys-mw/bugs/2/" rel="alternate"/><published>2003-11-18T17:19:57Z</published><updated>2003-11-18T17:19:57Z</updated><author><name>Stefan Wesner</name><uri>https://sourceforge.net/u/swesner/</uri></author><id>https://sourceforge.net932b1adba76d7778794c3bd1ae48d060b041e7c1</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;If the system monitoring console is started on windows &lt;br /&gt;
in a path where a blank is part of the directory name &lt;br /&gt;
the configuration file cannot be opened.&lt;/p&gt;
&lt;p&gt;As it is typical for a windows user to place programs in &lt;br /&gt;
the &amp;amp;quot;Own Files&amp;amp;quot; section this will lead to errors for almost &lt;br /&gt;
all windows users.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Run script for system console</title><link href="https://sourceforge.net/p/genesys-mw/bugs/1/" rel="alternate"/><published>2003-11-18T17:16:21Z</published><updated>2003-11-18T17:16:21Z</updated><author><name>Stefan Wesner</name><uri>https://sourceforge.net/u/swesner/</uri></author><id>https://sourceforge.net217b008c12e7ecb41266d63940fab0ef5616f6e2</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The run script for the system console contains '#' as &lt;br /&gt;
comment token. In windows REM has to be used.&lt;/p&gt;
&lt;p&gt;This leads to ugly messages on the command line&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>