Port Error

Dapron

I get the following Error Message when i connect to the following url
http://174.36.167.70:8080/AwareIM/logonAdmin.html

Unable to open TCP/IP socket for server localhost on port 9000,br.Please make sure that port 9000 in unblocked.,br.Original exception is connection refused: connect.

I need to say that iam still having my BO in testing mode & didnt make it operasional. Want to test it over the net. Will that cause the error.

Want the client to see the BO & make changes before making it Operasional.

aware_support

The error message is self-explanatory. You need to make sure that port 9000 is available.

lineamovil

Dapron wrote
I get the following Error Message when i connect to the following url
http://174.36.167.70:8080/AwareIM/logonAdmin.html

Unable to open TCP/IP socket for server localhost on port 9000,br.Please make sure that port 9000 in unblocked.,br.Original exception is connection refused: connect.

I need to say that iam still having my BO in testing mode & didnt make it operasional. Want to test it over the net. Will that cause the error.

Want the client to see the BO & make changes before making it Operasional.

Hello Dapron. Im having the same problem with Iweb. The only way im fixing it is rebooting the server. It works for some time but then the problem comes again.

thank you!

yuri.rj

Same to me
It's happening for months now.
It's driving me crazy.
After reboot the system works fine...for a couple day(maybe less) than it starts occurring again.
I used TCPVIEW and there is no process running on the 9000 port.

yuri.rj

Anyone tried to change Jboss default port?
Maybe 9001,9002,9003.
I really don't know what to do. it happens 3 times a week.
People are trying to kill me... I've spent my whole vacation rebooting the system remotely. 🙁

aware_support

This is unlikely to be an Aware IM problem. Something happens with your TCP/IP sockets while Aware IM is running and they become unavailable or blocked. Check with your service provider if you are deploying your solution on a hosting server.

yuri.rj

It's my server.. My company..
As said in other post... I started using control panel now... Let's see if it will happen again

Powerm

same problem for me, only server restart works for couple of minutes or hours. Does the same with port 9010.

yuri.rj

Are you still having the same problem?
I am!
Once in a week my server stops and i can't make it available anymore

aware_support

We'd really like to help but don't know where to start. This problem seems to only affect those on this thread - there must be some TCP/IP setting on your servers that cause this problem - for example, some limitation on a number of open sockets. Please check your TCP/IP settings and experiment and/or consult an operating system expert for TCP/IP

yuri.rj

I followed your instructions on another thread and replaced JBOSS folder from the Trial Version
And it started working again....but i really don't know for how long it will stay that way....

I have other applications(not aware) in our company and my main objective was to replace all of them by one aware application, but people are beginning not to trust Aware.

I really hope i can solve this before it loses it's reliability

Thanks again

rocketman

I'm making some assumptions here but here are some real world scenarios for you to consider. The assumption is you are running windows operating systems

This error can (does) occur when running Aware IM as a service if - after a reboot AwareIM tries to start before MySQL (or other database) is ready.

If you are running server 2008 try putting a delayed start on AwareIM.

If your server is set to automatically download and install microsoft updates - reset it so that the install process is at your discretion under your control. because some updates will cause a reboot.

A complete reboot is not usually necessary, just shut down the services and then restart them (in the order jBoss, Tomcat, AwareIM) If you are using the control panel - just shut down and restart the control panel

If you are running on a VPS some service providers will restart the server if another user has caused a hang. This again is outside of your control and you'll just have to live with it. When the server restarts - the above scenarion will apply. Consider a dedicated server or a cloud server running xen technology

If you are running backup exec 2010 This program uses port 9000, try setting jBoss on another port (easy to do in the control panel - but don't forget to open the new port on your firewall)

Try assigning more memory to jBoss. It might be a "too may sockets" issue

If you're running Unix OS - then you are on your own - I know nothing about unix but same principles apply. Make sure there is no other software running on your server that conflicts with port 9000 and that jBoss has a good chunk of memory

Ater several months of pain, I recently moved to a dedicated server and am now having really restful night's sleep - and no grief from my users

Let me know how you all get on 🙂

aware_support

If this happens again for someone please e-mail us the contents of the JBoss folder and the contents of the JBoss output window BEFORE restarting the server. Maybe it will give us some clues as to why JBoss misbehaves occasionally.

Powerm

Hello,

In my case I had to delete few rules on one of my tables, these rules were pushing the CPU to its limits, causing the port error.
All works fine now.

yuri.rj

First i'll wait for a few days using the replaced JBoss folder.
Then i'll try to monitor my rules like Powerm says... i don't think i have much things that could cause that.
After that i'll try rocketman instructions

And of course if it happens again i'll report to support again.

Thank you all for this... i'll keep you informed

robleer

I had two problems causing this port 9000 problem

First, I run my Aware app on a Virtual Windows Server. My service provider now an then changes the underlying hardware, which causes a problem with my Aware license.
My license was now an then invalid and then my Aware server fails to start: port 9000 error. Took me some time to find our that this was the problem causing my Awared service failing to start.

The second problem wat the startup sequence of the services. If one of the services does not start (after a reboot or so): port 9000 error.

I changed the startup of the (windows) services and let Windows retry the start of the services for several times until it succeeds.

After that my server comes up after a (planned or unplanned) reboot and no problem anymore.

For the license problem, Aware support helped me with that and they changed something in my installation so the license problem does not occur anymore on a VPS.

Hope this helps to find your problem.

pniehaus

I think we may have an update on this. We changed the AwareIM server IP number and got the same error.

When trying to reach the application web site as well as when trying to log in from the config tool.

The error message confuses matters.
The actual reason for the error in the first instance was that MySQL was not running because a IP address was hardcoded in the MySQL config. That was fixed and the website worked.

The second reason was that a hosts file is used on the PC with the configtool and this file contained (you guessed it) a hardcoded IP for the AwareIM server.