Hi Glen,

From what I can see, it seems Tomcat cannon bind to the port, because it may already be in use.

You change the port please do the following within the server.xml file , located in :
/appserver/conf
Open the XML in wordpad and change the following (should be towards the top of the file):
[code]


<Connector port="80"
maxHttpHeaderSize="8192"
[/code]
Change '80' to another port (e.g. 8081).
Please let me know how you go after changing the port.
If it still fails, you can send through the Yellowfin.log & JDBC.log file.

Please let me know how you go.

Regards,
David

David,

Looking at my server.xml file it shows the following:



<Connector port="1434"
maxHttpHeaderSize="8192"


but changed it to 8081 to see if it made a difference. Unfortunately it didn't seem to.

Have attached updated log files.

Thanks,
Glen

Hi Glen,

It looks like previously you have specified to use the SQL port '1434' which would explain the error.

Though now it seems you are getting past this point, and now getting another error:
[code]
SEVERE: StandardServer.await: create[8085]:
java.net.BindException: Address already in use: JVM_Bind
[/code]

Can you change the port to something that we know won't be in use . eg. '5252' and change the shutdown port to '5285'and then restart the Yellowfin server.

So your server.xml will look like this (I haven't copied the ENTIRE file):
[code]


<Connector port="5252" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" redirectPort="8443" acceptCount="100"
..........
[/code]

Please let me know how it goes.

Regards,
David

David,

Updated server.xml values as suggested with no luck.

Attached logs and screenshot of tomcat hanging when performing JDBC connections. I see it is still referring to port 1434....

Glen

Hi Glen,

Can you please email across the server.xml file, it seems this could be related to Tomcat not being able to recognize the address.

We may need to add an address parameter like in the post below:
Change Tomcat listening address


Though we should confirm this first.

Regards,
David

Hi David,

Have just emailed you the server.xml file as requested

Cheers,
Glen

Hi Glen,

The server.xml looks ok.

So the next thing to do will be to add the 'address= 127.0.0.1' parameter as specified in the post 'Change Tomcat listening address'.

Please let me know how it goes.

Regards,
David

David,

Server.xml now looks like this:





<Connector port="5252"
maxHttpHeaderSize="8192"

maxThreads="150"
minSpareThreads="25"
maxSpareThreads="75"
enableLookups="false"
redirectPort="8443"
acceptCount="100"
connectionTimeout="20000"
disableUploadTimeout="true"
URIEncoding="UTF-8"
compression="on"
compressionMinSize="2048"
noCompressionUserAgents="gozilla, traviata"
compressableMimeType="text/html,text/xml,text/plain"
address= "127.0.0.1"

and restarted YF server, opened browser to http:localhost with no success

New logs attached

Cheers,
Glen

David,

Server.xml now looks like this:





<Connector port="5252"
maxHttpHeaderSize="8192"

maxThreads="150"
minSpareThreads="25"
maxSpareThreads="75"
enableLookups="false"
redirectPort="8443"
acceptCount="100"
connectionTimeout="20000"
disableUploadTimeout="true"
URIEncoding="UTF-8"
compression="on"
compressionMinSize="2048"
noCompressionUserAgents="gozilla, traviata"
compressableMimeType="text/html,text/xml,text/plain"
address= "127.0.0.1"

and restarted YF server, opened browser to http:localhost with no success

New logs attached

Cheers,
Glen

The client had 2 issues that have been resolved.

Issue 1:
His SQL installation was not configured to accept connections using TCP/IP.
Information on this can be found
here

Issue 2:
A Yellowfin service was previously installed and running (using the same port).

This was fixed by changing the listening port as mentioned previously.