Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Error Connecting to Server

15 posts in General Discussion Last posting was on 2009-01-20 10:17:46.0Z
Jasvinder Bahra Posted on 2009-01-14 10:27:52.0Z
Sender: 1a5e.496c960b.1804289383@sybase.com
From: Jasvinder Bahra
Newsgroups: ianywhere.public.mbusinessanywhere.general
Subject: Error Connecting to Server
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <496dbe28.3772.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 14 Jan 2009 02:27:52 -0800
X-Trace: forums-1-dub 1231928872 10.22.241.41 (14 Jan 2009 02:27:52 -0800)
X-Original-Trace: 14 Jan 2009 02:27:52 -0800, 10.22.241.41
Lines: 26
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.mbusinessanywhere.general:1298
Article PK: 9350

I am attempting to view a website in M-Business Client. The
website in question runs on Apache Tomcat, and is hosted on
the server that runs the M-Business Anywhere Server.

However whenever I try, I get a "Error Connecting To Server.
Failed to connect to https://<<IP>>:9443/index.jsp." The
website is being hosted on Apache Tomcat, which is listening
on port 9443 for HTTPS connections.

I know that the website is up and running because I can
access it in a browser on the server. This also confirms
that the server can access the site (so the M-Business
Anywhere Server should have no trouble accessing the site).

I have confirmed that the M-Business Client is reaching the
M-Business Anywhere Server with its request because if I log
into the server administration web interface, I an see a
corresponding entry in the Sync Log Report. The report does
mention an error however - "ERROR: Connect Error.(400) -
https://<<IP>>:9443/index.jsp".

Note also that I have added the self-signed SSL certificate
Apache Tomcat is using to the M-Business Anywhere Server's
conf\trusted.txt file and restarted the M-Business services.

Anyone have any ideas as to why we're getting the error?


David Fishburn Posted on 2009-01-14 15:33:45.0Z
Newsgroups: ianywhere.public.mbusinessanywhere.general
Subject: Re: Error Connecting to Server
From: David Fishburn <fishburn_spam_off@ianywhere.com>
References: <496dbe28.3772.1681692777@sybase.com>
Organization: iAnywhere Solutions
Message-ID: <Xns9B936B72F4604fishburnsybasecom@10.22.241.106>
User-Agent: Xnews/2005.10.18
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Date: 14 Jan 2009 07:33:45 -0800
X-Trace: forums-1-dub 1231947225 10.22.241.152 (14 Jan 2009 07:33:45 -0800)
X-Original-Trace: 14 Jan 2009 07:33:45 -0800, vip152.sybase.com
Lines: 34
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.mbusinessanywhere.general:1300
Article PK: 9349

Jasvinder Bahra wrote in news:496dbe28.3772.1681692777@sybase.com
of ianywhere.public.mbusinessanywhere.general:

...
JB> However whenever I try, I get a "Error Connecting To Server.
JB> Failed to connect to https://<<IP>>:9443/index.jsp." The
JB> website is being hosted on Apache Tomcat, which is listening
JB> on port 9443 for HTTPS connections.

As a test, what happens when you try an HTTP instead of HTTPS address?
--
David Fishburn
Certified ASA Developer Version 8
iAnywhere Solutions - Sybase
Professional Services
Please only post to the newsgroup
Please ALWAYS include version and MORE importantly BUILD number with
EACH post (dbeng11 -v).

EBFs and Maintenance Releases
http://downloads.sybase.com/

Developer Community / Whitepapers
http://www.ianywhere.com/developer

Case-Express - to report bugs
http://case-express.sybase.com

CodeXchange - Free samples
http://ianywhere.codexchange.sybase.com/servlets/ProjectDocumentList

Documentation
http://dcx.sybase.com/


Jasvinder Bahra Posted on 2009-01-14 17:15:17.0Z
Sender: 1a5e.496c960b.1804289383@sybase.com
From: Jasvinder Bahra
Newsgroups: ianywhere.public.mbusinessanywhere.general
Subject: Re: Error Connecting to Server
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <496e1da5.49c5.1681692777@sybase.com>
References: <Xns9B936B72F4604fishburnsybasecom@10.22.241.106>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 14 Jan 2009 09:15:17 -0800
X-Trace: forums-1-dub 1231953317 10.22.241.41 (14 Jan 2009 09:15:17 -0800)
X-Original-Trace: 14 Jan 2009 09:15:17 -0800, 10.22.241.41
Lines: 7
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.mbusinessanywhere.general:1302
Article PK: 9355

> As a test, what happens when you try an HTTP instead of
HTTPS address?

David, when I try and access the website using the HTTP
protocol, I can access the website fine. Note that I have
to specify a different port number too, so the URL becomes
http://<<IP>>:9080/index.jsp


Jeff Albion (Sybase iAnywhere) Posted on 2009-01-14 15:36:50.0Z
From: "Jeff Albion (Sybase iAnywhere)" <firstname.lastname@ianywhere.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
Newsgroups: ianywhere.public.mbusinessanywhere.general
Subject: Re: Error Connecting to Server
References: <496dbe28.3772.1681692777@sybase.com>
In-Reply-To: <496dbe28.3772.1681692777@sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <496e0692$1@forums-1-dub>
Date: 14 Jan 2009 07:36:50 -0800
X-Trace: forums-1-dub 1231947410 10.22.241.152 (14 Jan 2009 07:36:50 -0800)
X-Original-Trace: 14 Jan 2009 07:36:50 -0800, vip152.sybase.com
Lines: 36
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.mbusinessanywhere.general:1301
Article PK: 17942

Jasvinder,

HTTP 400 is a "Bad Request" from the client (the M-Business server). If
you can access the URL from a browser on the server machine, that
suggests that there's something different with the request coming across
the wire.

Have you done any type of request tracing to determine the nature of the
problem? Have you tried doing it without HTTPS enabled on the remote server?

For tracing options, see:
http://www.ianywhere.com/developer/product_manuals/mbusiness_anywhere/70/en/html/mba_adminguideen70/adminguide-ag-logfiles-debuglevel.html

I'd recommend possibly looking at the debug options:
agsync, interactive, webtogo, maldebug, webtogo_trace, rover0, rover1,
rover2, rover3, cache

You may also want to consider comparing the two types of requests
(browser vs. M-Bus) at a lower level, such as using a packet tracing
utility like WireShark (http://www.wireshark.org/).

Hope that helps!

Jasvinder Bahra wrote:
> Anyone have any ideas as to why we're getting the error?

Regards,

--
Jeff Albion, Sybase iAnywhere

iAnywhere Developer Community :
http://www.sybase.com/developer/library/sql-anywhere-techcorner
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
SQL Anywhere Patches and EBFs :
http://downloads.sybase.com/swd/summary.do?baseprod=144&client=ianywhere&timeframe=0


Jasvinder Bahra Posted on 2009-01-14 17:23:46.0Z
Sender: 1a5e.496c960b.1804289383@sybase.com
From: Jasvinder Bahra
Newsgroups: ianywhere.public.mbusinessanywhere.general
Subject: Re: Error Connecting to Server
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <496e1fa2.4a26.1681692777@sybase.com>
References: <496e0692$1@forums-1-dub>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 14 Jan 2009 09:23:46 -0800
X-Trace: forums-1-dub 1231953826 10.22.241.41 (14 Jan 2009 09:23:46 -0800)
X-Original-Trace: 14 Jan 2009 09:23:46 -0800, 10.22.241.41
Lines: 60
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.mbusinessanywhere.general:1303
Article PK: 17943

> Have you done any type of request tracing to determine the
nature of the problem? Have you tried doing it without
HTTPS enabled on the remote server?

Jeff, we can access the website without problems if we use
the HTTP protocol (though we have to specifiy a different
port number in the url because Apache Tomcat listens for
HTTP connections on port 9080, and HTTPS connections on 9443
- our URL simply changes to http://<<IP>>:9080/index.jsp).

As this is the case, I imagine that tracing may be difficult
because we would have to use the HTTPS protocol to reproduce
the problem. I'll give it a go though - any more
information could be helpful.

> Jasvinder,
>
> HTTP 400 is a "Bad Request" from the client (the
> M-Business server). If you can access the URL from a
> browser on the server machine, that suggests that there's
> something different with the request coming across the
> wire.
>
> Have you done any type of request tracing to determine the
> nature of the problem? Have you tried doing it without
> HTTPS enabled on the remote server?
>
> For tracing options, see:
>
http://www.ianywhere.com/developer/product_manuals/mbusiness_anywhere/70/en/html/mba_adminguideen70/adminguide-ag-logfiles-debuglevel.html
>
> I'd recommend possibly looking at the debug options:
> agsync, interactive, webtogo, maldebug, webtogo_trace,
> rover0, rover1, rover2, rover3, cache
>
> You may also want to consider comparing the two types of
> requests (browser vs. M-Bus) at a lower level, such as
> using a packet tracing utility like WireShark
> (http://www.wireshark.org/).
>
> Hope that helps!
>
> Jasvinder Bahra wrote:
> > Anyone have any ideas as to why we're getting the error?
>
> Regards,
>
> --
> Jeff Albion, Sybase iAnywhere
>
> iAnywhere Developer Community :
>
http://www.sybase.com/developer/library/sql-anywhere-techcorner
> iAnywhere Documentation :
> http://www.ianywhere.com/developer/product_manuals SQL
> Anywhere Patches and EBFs :
>

http://downloads.sybase.com/swd/summary.do?baseprod=144&client=ianywhere&timeframe=0