404 Error When Posting via HTTPS

, ,
1

An external partner of ours receives a 404 ‘Page Not Found’ error when posting via HTTPS a message to our BC 4.6 server.

When they attempt to post to the very same URL a second time (five seconds later), they are successful.

We have verified that their certificates and ours are working properly, and that our service to receive the message is working.

This error occurs when using DNS and IP. Also there is no trace of the error in the wm error log (using default logging level).

Thanks for any suggestions.

2

Can you check with increasing server logging level (probably 9).

3

Just a shot in the dark: Is there a load balancing facility in the place? The SSL handshake takes a bit of time so a load balancer may be redirecting traffic to one server on the first bit of activity in the handshake and then to another a bit later.

4

Server log level is 4. I can set to level 9 but the next message won’t come until Tuesday the 22nd of April. That’s my next step though.

No load balancing being done, but I am concerned that maybe the SSL handshake is taking too long and they are timing out on their side.

5

My guess is this is not an IS issue but a network issue. Not sure where to look though, other than get network type involved.

6

> concerned that maybe the SSL handshake is taking too
> long and they are timing out on their side.

It seems something that should be generating another error code, is wrongly generating a HTTP 404 response.
(If nothing was generating the 404 response, your partner would get either a “connection refused” or a “page contains no data” error).

The 404 code could be generated either by:

  • Load balancer/SSL accelerator/ firewall/ Other freaky stuff on your side
  • Proxy server/ firewall/ Other freaky stuff on partner’s side (this looks more likely)

I’d check that your side’s setup was fine and then push it back to the partner.

7

hi all,
my server is not started properly shut down after in the middle of starting .see the below…
2004-12-09 14:32:56 EST [ISS.0025.0001C] Integration Server 6.1 Build 132
2004-12-09 14:32:56 EST [ISS.0025.0006C] License Manager started
2004-12-09 14:32:56 EST [ISS.0025.0041C] FIPS mode not initialized
2004-12-09 14:32:57 EST [BAS.0123.0001C] FSData full consistency check is being
performed. Db:WmRepository4\FSD
2004-12-09 14:32:57 EST [ISS.0025.0017C] Repository Manager started
2004-12-09 14:33:10 EST [ISS.0096.0001C] JDBCConnectionManager: initialization
ailed for DocumentHistory functional alias, check configuration.
2004-12-09 14:33:15 EST [ISS.0096.0001C] JDBCConnectionManager: initialization
ailed for ISCoreAudit functional alias, check configuration.
2004-12-09 14:33:20 EST [ISS.0096.0001C] JDBCConnectionManager: initialization
ailed for ProcessAudit functional alias, check configuration.
2004-12-09 14:33:25 EST [ISS.0096.0001C] JDBCConnectionManager: initialization
ailed for Reporting functional alias, check configuration.
2004-12-09 14:33:30 EST [ISS.0096.0001C] JDBCConnectionManager: initialization
ailed for Staging functional alias, check configuration.
2004-12-09 14:33:35 EST [ISS.0096.0001C] JDBCConnectionManager: initialization
ailed for TN functional alias, check configuration.
2004-12-09 14:33:40 EST [ISS.0096.0001C] JDBCConnectionManager: initialization
ailed for Xref functional alias, check configuration.
2004-12-09 14:33:40 EST [ISS.0025.0024C] JDBC Connection Manager started
2004-12-09 14:33:41 EST [BAS.0123.0001C] FSData full consistency check is being
performed. Db:audit\data\AuditStore.
2004-12-09 14:33:42 EST [ISS.0025.0023C] Audit Log Manager started
2004-12-09 14:33:43 EST [ISS.0025.0021C] ACL Manager started
2004-12-09 14:33:43 EST [ISS.0025.0008C] State Manager started
2004-12-09 14:33:47 EST [ISS.0025.0010C] Service Manager started
2004-12-09 14:33:47 EST [ISS.0025.0020C] Validation Processor started
2004-12-09 14:33:47 EST [ISS.0025.0022C] Statistics Processor started
2004-12-09 14:33:47 EST [ISS.0025.0018C] Invoke Manager started
2004-12-09 14:33:47 EST [ISS.0025.0012C] Cache Manager started
2004-12-09 14:33:47 EST [ISS.0098.0009V2] Dispatcher initializing configuration
from file: .\config\dispatch.cnf
2004-12-09 14:33:47 EST [ISS.0098.0028V2] CommsFactory registering and initiali
ing Transport Factory: BROKERTRANSPORTFACTORY
2004-12-09 14:33:48 EST [BAS.0123.0001C] FSData full consistency check is being
performed. Db:DocumentStore\ISTransStore
2004-12-09 14:33:49 EST [ISS.0098.0026D] Document Store DefaultStore initialize

2004-12-09 14:33:50 EST [BAS.0123.0001C] FSData full consistency check is being
performed. Db:DocumentStore\TriggerStore
2004-12-09 14:33:52 EST [ISS.0098.0026D] Document Store VolatileTriggerStore in
tialized
2004-12-09 14:33:52 EST [ISS.0098.0026D] Document Store TriggerStore initialize

2004-12-09 14:33:52 EST [BAS.0123.0001C] FSData full consistency check is being
performed. Db:DocumentStore\ISResubmitStore
2004-12-09 14:33:53 EST [ISS.0098.0026D] Document Store ResubmitStore initializ
d
2004-12-09 14:33:53 EST [ISS.0106.0001D] Join Manager initialized
2004-12-09 14:33:53 EST [ISS.0025.0032C] Dispatcher initialized
2004-12-09 14:33:53 EST [ISS.0028.0011E] Unable to write package manifest file:
.\packages\Default\manifest.v3 (The system cannot find the path specified) (cre
ting Default package)
2004-12-09 14:33:53 EST [ISS.0025.0004C] Flow Service Manager started
2004-12-09 14:33:53 EST [ISS.0025.0002C] Package Manager started
2004-12-09 14:33:53 EST [ISS.0025.0011C] Package Replicator Manager started
2004-12-09 14:33:53 EST [ISS.0028.0001C] Loading packages
2004-12-0

8

I assume you are starting on default port 5555. It looks like you already have an application listening on this port. Try starting from a command line with the following:

server.bat (or server.sh if UNIX) -port 5556