HelloWorld Error (#667)

Closed

Activities

Eric Dziewa opened 8 years ago

Due Date
2016-08-21

Turning debug level way up on a new install produces lots of errors about public class HelloWorld . The server still runs fine.

tigase-console.log

wojciech.kapcia@tigase.net commented 8 years ago

Could you please share exact version (and/or package you used) and complete configuration?

wojciech.kapcia@tigase.net commented 8 years ago

It looks like this file is not part of any of the distribution builds nor our sources.

Eric Dziewa commented 8 years ago

I was using tigase-issue #7.1.0-SNAPSHOT-b4199 on tpub. It's strange because i grepped for that string in the entire directory, it's only mentioned in logs. Maybe it's in one of the jars.

config-type=--gen-config-def
--admins = admin@tpub.xmpp-test.net
--virt-hosts = tpub.xmpp-test.net
--debug=server,xmpp.impl,ext,muc,component
--packet.debug.full=true
basic-conf/logging/java.util.logging.FileHandler.limit=100000000
basic-conf/logging/java.util.logging.FileHandler.count=20

--sm-plugins=+jabber\:iq\:auth,+urn\:ietf\:params\:xml\:ns\:xmpp-sasl,+urn\:ietf\:params\:xml\:ns\:xmpp-bind,+urn\:ietf\:params\:xml\:ns\:xmpp-session,+jabber\:iq\:register,+jabber\:iq\:roster,+presence-state,+presence-subscription,+basic-filter,+domain-filter,+jabber\:iq\:privacy,+jabber\:iq\:version,+http\://jabber.org/protocol/stats,+starttls,-msgoffline,+vcard-temp,+http\://jabber.org/protocol/commands,+jabber\:iq\:private,+urn\:xmpp\:ping,+pep,+zlib,+message-archive-xep-0136,+amp

--hardened-mode=true

--auth-db = tigase-custom
--auth-db-uri=jdbc:mysql://localhost/tpub?user=tigase&password=xmpp3030
--user-db=mysql
--user-db-uri=jdbc:mysql://localhost/tpub?user=tigase&password=xmpp3030&autoCreateUser=true

--comp-name-1=ext
--comp-class-1=tigase.server.ext.ComponentProtocol
--external=jitsi-videobridge.tpub.xmpp-test.net:jvbsecret:listen:5275

muc/message-filter-enabled[B]=false
muc/presence-filter-enabled[B]=false
muc/muc-allow-chat-states[B]=true

bosh/concurrent-requests[I]=16

--stats-archiv=tigase.stats.CounterDataFileLogger:stats-file-logger:60
stats/stats-archiv/stats-file-logger/stats-directory=/home/tigase/tpub.stats
stats/stats-archiv/stats-file-logger/stats-unixtime=true
stats/stats-archiv/stats-file-logger/stats-level=FINEST

--comp-name-3=pubsub
--comp-class-3=tigase.pubsub.PubSubComponent

--comp-name-4=http
--comp-class-4=tigase.http.HttpMessageReceiver

Andrzej Wójcik (Tigase) commented 8 years ago

I already talked about this issue with %wojtek and we checked that there is no mention of HelloWorld class (script) in Tigase sources.

So as you mentioned I expected that there is no mention of it in directory.

As I checked MonitorComponent sources I see that it loads scripts/task from database, so most likely this HelloWorld class is in script which is somewhere in database used by this installation. I suppose that it will be in tig_pairs table in pval column.

Eric Dziewa commented 8 years ago

I will verify because I think I've seen this before.

Eric Dziewa commented 8 years ago

I've found this in the database on tpub tig_pairs. I deleted it and the error has gone away. Can any of you identify how it got there?

<monitor-task type="task" taskName="disk-task">
<x xmlns="jabber:x:data" type="submit">
<field var="x-task#enabled" type="boolean">
<value>
1</value>
</field>
<field var="x-task#period" type="text-single">
<value>
1000</value>
</field>
<field var="threshold" type="text-single">
<value>
0.1</value>
</field>
</x>
</monitor-task>
<monitor-task scriptExtension="groovy" type="scriptTask" taskName="Hello World">
<script>
cHVibGljIGNsYXNzIEhlbGxvV29ybGQgew==</script>
<x xmlns="jabber:x:data" type="">
<title>
Task Configuration</title>
<field var="x-task#enabled" type="boolean" label="Enabled">
<value>
1</value>
</field>
</x>
</monitor-task>
<monitor-task type="task" taskName="sample-task">
<class>
tigase.monitor.tasks.SampleTask</class>
<x xmlns="jabber:x:data" type="submit">
<field var="x-task#enabled" type="boolean">
<value>
1</value>
</field>
</x>
</monitor-task>
<monitor-task scriptExtension="groovy" type="scriptTask" taskName="Test">
<script>
JCBncm9vdnkgSGVsbG9Xb3JsZC5ncm9vdnk=</script>
<x xmlns="jabber:x:data" type="">
<title>
Task Configuration</title>
<field var="x-task#enabled" type="boolean" label="Enabled">
<value>
1</value>
</field>
</x>
</monitor-task>

wojciech.kapcia@tigase.net commented 8 years ago

This is just a guess, but: I think you can manage the tasks via AdHocs, thus it got created while testing, then along the way there may have been a change in the code resulting in error. I don't think we need to investigate it further.

Type	Bug
Priority	Normal
Assignee	Eric Dziewa
RedmineID	4067
Spent time	22h 30m

Issue Votes (0)

Watchers (0)

Reference

tigase/_server/server-core#667