[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Apache configuration



Vince I agree with you completely, that are jerks out there that get
there kicks out of admonishing people.   I am done with this site.

-----Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Selders,
Vince E
Sent: Monday, April 23, 2012 7:15 AM
To: HTTPAPI and FTPAPI Projects
Subject: RE: Apache configuration

The only bad question is the one left unasked.  Forgive me for infecting
this list with a question that I felt was relevant to the forum.  I
suppose I thought having a server was important in using HTTP API and
therefore the proper set up of it might warrant discussion.  Simply put,
I may not know what is relevant and what isn't, I'd rather my question
simply be ignored if not relevant than to be admonished for posting what
I thought was a question with merit.  I didn't offer a lot because, in
my simple mind, it seems that there would be a generic configuration ...
that is all I want.

I do appreciate your testament to HTTPAPI, and will pursue upgrading.
However, it will not be done without extensive testing as is dictated by
my company's extensive change management process.

I'm not looking for the solution to my problem, I just want to make
certain my initial set up and configuration is intact.  If setting up a
server to run a web service using HTTPAPU is not relevant, by all means,
disregard.

To be sure I'm getting a MCH3601 in msgq QSYSOPR, when (C)ancelled or
(D)umped results in a HTTP 500 error.

And this happens when my program hits the code that I originally sent.

Thanks
v

-----Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Porterfield,
Sean
Sent: Monday, April 16, 2012 15:56
To: HTTPAPI and FTPAPI Projects
Subject: RE: Apache configuration

General tips, since you didn't offer a whole lot.  First, this list is
for HTTPAPI and FTPAPI; there are other places to discuss Apache if
that's where your problem is.

Second, it's very, very rare for an upgrade of HTTPAPI to cause
problems.  It's been carefully designed and programmed to avoid that.

Third, enable the debug log and check it for problems or post it for
others to view.

It's not clear to me if you're saying the program using HTTPAPI is "hung
up" or if it's your web service.  Again, this list is for discussion of
the former not the latter.
--
Sean Porterfield


-----Original Message-----
From: Selders, Vince E
Sent: Friday, April 13, 2012 07:50
To: ftpapi@xxxxxxxxxxxxxxxxxxxxxx
Subject: Apache configuration

Hey all

Some time ago I had a quick and dirty little web service hosted on the
iSeries.  Ultimately we ended up just consuming web services from other
platforms and the need to host was lost.  Well, the need is back so I'm
trying to resurrect my old code and everything seems to look fine but it
seems to get hung up.  As I said, this one is a very simple proof of
concept.  It receives a network ID and turns around and sends an email
(SNDDST) to
networkID@xxxxxxxxxxxxxxxxxx<mailto:networkID@xxxxxxxxxxxxxxxxxx>.  Back
when I was playing with it, it worked fine.  I had written an RPG
program with which to consume the web service.  Again, very simple, from
a command line CALL MYPROGRAM PARM(networked).

Well, now it gets hung up in the consumer when it goes to do the actual
consumption:

rc = http_url_post_xml(
                    'http://sysName:14444/cgibin/vescl'
                        : %addr(SOAP) + 2
                        : %len(SOAP)
                        : *NULL
                        : %paddr(Incoming)
                        : %addr(msgOut)
                        : HTTP_TIMEOUT
                        : HTTP_USERAGENT
                        : 'text/xml'
                        : 'http://sysName:14444/cgibin/vescl');

It's been a while since I did play with it, and I don't discount that I
may have been tweaking and playing with the code after hosting got shut
down, but something tells me I'm not doing something at the Apache
Server level that I need to, or in the mean time something about the
server itself has changed.  Any ideas, suggestions, or recommendations
are welcome.

I will say we're now at V7R1 on this box, and (sad to say) I've not
upgraded HTTP API in quite a while.  I need to do that, but that will
become a major deal because of the change management in place.  They are
giving me a partition to play in a little, so I will definitely get up
to date there and begin the task of changing over.

Thanks a ton!

Vincent Selders

This email is confidential, intended only for the named recipient(s)
above and may contain information that is privileged.  If you have
received this message in error or are not the named recipient(s), please
notify the sender immediately and delete this email message from your
computer as any and all unauthorized distribution or use of this message
is strictly prohibited.  Thank you.
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------