Forum Problems Installing LAMS: wildfire - lams 2.2 connection problem


 
You may request notification for wildfire - lams 2.2 connection problem.
Search: 

1: wildfire - lams 2.2 connection problem
04/13/09 03:30 AM
[ Reply | Forward ]
When I preview chat activity no users are displayed, no sent text is displayed and I get the error
"Couldn't connect. Please try again...
Code: 500
Type: wait
Condition: internal-server-error"

In wildfire server logs I get the following messages:



"at org.jivesoftware.wildfire.server.OutgoingSessionPromise$1$1.run(OutgoingSessionPromise.java:91)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
2009.04.13 05:11:28 [org.jivesoftware.wildfire.server.OutgoingServerSession.createOutgoingSession(OutgoingServerSession.java:259)] Error trying to connect to remote server: conference.elearning.agogiygeias.gr(DNS lookup: conference.elearning.agogiygeias.gr:5269)
java.net.UnknownHostException: conference.elearning.agogiygeias.gr
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at org.jivesoftware.wildfire.server.OutgoingServerSession.createOutgoingSession(OutgoingServerSession.java:254)
at org.jivesoftware.wildfire.server.OutgoingServerSession.authenticateDomain(OutgoingServerSession.java:140)
at org.jivesoftware.wildfire.server.OutgoingSessionPromise.createSessionAndSendPacket(OutgoingSessionPromise.java:126)
at org.jivesoftware.wildfire.server.OutgoingSessionPromise.access$300(OutgoingSessionPromise.java:37)
at org.jivesoftware.wildfire.server.OutgoingSessionPromise$1$1.run(OutgoingSessionPromise.java:91)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
2009.04.13 05:11:28 [org.jivesoftware.wildfire.net.SocketReader.run(SocketReader.java:161)] Connection closed before session established
Socket[addr=/72.14.182.219,port=55553,localport=5269]
2009.04.13 05:11:28 [org.jivesoftware.wildfire.net.SocketReader.run(SocketReader.java:161)] Connection closed before session established
Socket[addr=/72.14.182.219,port=55554,localport=5269]
2009.04.13 05:11:28 [org.jivesoftware.wildfire.server.OutgoingServerSession.createOutgoingSession(OutgoingServerSession.java:259)] Error trying to connect to remote server: agogiygeias.gr(DNS lookup: agogiygeias.gr:5269)
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at org.jivesoftware.wildfire.server.OutgoingServerSession.createOutgoingSession(OutgoingServerSession.java:254)
at org.jivesoftware.wildfire.server.OutgoingServerSession.authenticateDomain(OutgoingServerSession.java:183)
at org.jivesoftware.wildfire.server.OutgoingSessionPromise.createSessionAndSendPacket(OutgoingSessionPromise.java:126)
at org.jivesoftware.wildfire.server.OutgoingSessionPromise.access$300(OutgoingSessionPromise.java:37)
at org.jivesoftware.wildfire.server.OutgoingSessionPromise$1$1.run(OutgoingSessionPromise.java:91)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
2009.04.13 05:11:28 [org.jivesoftware.wildfire.server.OutgoingServerSession.createOutgoingSession(OutgoingServerSession.java:259)] Error trying to connect to remote server: gr(DNS lookup: gr:5269)
java.net.UnknownHostException: gr
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at org.jivesoftware.wildfire.server.OutgoingServerSession.createOutgoingSession(OutgoingServerSession.java:254)
at org.jivesoftware.wildfire.server.OutgoingServerSession.authenticateDomain(OutgoingServerSession.java:183)
at org.jivesoftware.wildfire.server.OutgoingSessionPromise.createSessionAndSendPacket(OutgoingSessionPromise.java:126)
at org.jivesoftware.wildfire.server.OutgoingSessionPromise.access$300(OutgoingSessionPromise.java:37)
at org.jivesoftware.wildfire.server.OutgoingSessionPromise$1$1.run(OutgoingSessionPromise.java:91)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)"

Any suggestions?

Posted by Nikos Dovros

2: Re: wildfire - lams 2.2 connection problem
In response to 1 04/14/09 03:46 PM
[ Reply | Forward ]
Nikos,

Have a look at how to configure it here:

http://is.gd/srQK

Thanks,

Ernie

Posted by Ernie Ghiglione

3: Re: Re: wildfire - lams 2.2 connection problem
In response to 2 04/15/09 06:44 AM
[ Reply | Forward ]
Thanks Ernie
Your link redirects to http://wiki.lamsfoundation.org/display/lamsdocs/LAMS+Configuration, which I have already advised.
Nikos

Posted by Nikos Dovros

4: Re: wildfire - lams 2.2 connection problem
In response to 1 04/17/09 03:19 AM
[ Reply | Forward ]
What have you got for the following parameters?

Wildfire:
Server domain (e.g. example.com)

LAMS:
Xmpp server domain (e.g. example.com)
Xmpp conference (e.g. conference.example.com)

LAMS' Xmpp server domain must be the same as Wildfire's server domain. Also the server domains (e.g. agogiygeias.gr?) must be accessible from each machine.

Posted by Jun-Dir Liew

5: Re: Re: wildfire - lams 2.2 connection problem
In response to 4 04/17/09 11:11 AM
[ Reply | Forward ]
Thank you Jun-Dir.
You really helped me. During wildifre configuration I had accepted thw server name that the configuration had prompted (something like li55-555). I changed the server name (wihtout http://) and now chat tool seems to work fine. Online users are displayed, messages are passed and I can see the history while monitoring the lesson.
Yet, when I click "finish" I get an instant message of error 500 -internal server something (I can't read it fully). I don't know if it is a problem.
And something else. Shouldn't the users of a chat room be notified when someone leaves the chat room?
Nikos

Posted by Nikos Dovros

6: Re: Re: Re: wildfire - lams 2.2 connection problem
In response to 5 04/20/09 04:04 AM
[ Reply | Forward ]
I don't think the chat tool displays any special text when someone leaves the room, but only removes them from the user list on the right.
With the error when you click finish - could you send your lams server.log and lams.log at the time the error occurred? It doesn't look like it's affecting your chat functionality, except that it's disconcerting receiving an error message of any kind.

Posted by Jun-Dir Liew

7: Re: Re: Re: Re: wildfire - lams 2.2 connection problem
In response to 6 04/21/09 03:37 AM
[ Reply | Forward ]
Thank you Jun-Dir

I attach server.log and lams.log

http://elearning.agogiygeias.gr/server.log
http://elearning.agogiygeias.gr/lams.log

Nikos

Posted by Nikos Dovros

Reply to first post on this page
Back to Problems Installing LAMS
.LRN Home