Highlighted
Absent Member.
Absent Member.
2016 views

auto refresh


GroupWise 14.0.1 HP1 on SLES11SP3/OES11SP2

Hi,

we experience problems with the auto refresh feature of webaccess: after
start of webaccess it works a while, then stops; after rctomcat6 restart the
same again.

Webaccess is on it's own server outside a firewall (DMZ); Port 8500 from the
POAs to webaccess is available. In the other direction, from Webaccess to
POAs the SOAP Ports are available - port 8500 isn't needed in that
direction, is it?

I'm also aware of the recommendation from another thread to change
SOAP.Poll.host from 127.0.0.1 to "the webaccess server IP" - but if I
understand correctly in that context they had Webaccess and POA on the same
server. Should I set it to the Webaccess IP or POA IP.

One more question, just for my understanding: if there are 3 POAs - does
Webaccess need SOAP access to all 3 seperately, or can it access mailboxes
of all POAs "through" one POA?

Thanks,
Mirko
Labels (1)
0 Likes
30 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: auto refresh

Hi Mirko,

I have a customer with their WebAccess on a separate server to the POA's. Making this change: SOAP.Poll.host from 127.0.0.1 to "the webaccess server IP"
did have an impact on performance and I don't think that it would hurt to implement that change.

Additionally you can specify more than one SOAP provider (up to 3 if memory serves correctly) for fail over purposes:

Provider.SOAP.1.ip=IP of 1st POA
Provider.SOAP.1.port=7191
Provider.SOAP.2.ip=IP of 2nd POA
Provider.SOAP.2.port=7191
Provider.SOAP.3.ip=IP of 3rd POA
Provider.SOAP.3.port=7191

Let us know how it goes.

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: auto refresh

Hi Laura,

laurabuckley wrote:


> I have a customer with their WebAccess on a separate server to the
> POA's. Making this change: SOAP.Poll.host from 127.0.0.1 to "the
> webaccess server IP"
> did have an impact on performance and I don't think that it would hurt
> to implement that change.


I changed this now. I restarted WebAccess yesterday and today again auto
refresh did not work. Change and restart today - I'll wait and see if it
keeps working longer...

>
> Additionally you can specify more than one SOAP provider (up to 3 if
> memory serves correctly) for fail over purposes:
>
> Provider.SOAP.1.ip=IP of 1st POA
> Provider.SOAP.1.port=7191
> Provider.SOAP.2.ip=IP of 2nd POA
> Provider.SOAP.2.port=7191
> Provider.SOAP.3.ip=IP of 3rd POA
> Provider.SOAP.3.port=7191


I already had these. So it did not help for auto refresh.

I try an answer to my own question:

>One more question, just for my understanding: if there are 3 POAs - does
>Webaccess need SOAP access to all 3 seperately, or can it access mailboxes
>of all POAs "through" one POA?


I checked this today: blocked the SOAP port for access (only) from the
WebAccess server for one POA. User can't log in.

So, WebAccess obviously *does* need direct access to the users POA. POAs do
not proxy traffic, they only redirect to other POAs. The entrys above only
try to avoid a situation where the users POA is available but not the one
Webaccess asks for a redirect, right?

Thanks,
Mirko
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: auto refresh

Mirko Guldner wrote on 04/08/2015 05:19 PM:
> So, WebAccess obviously*does* need direct access to the users POA. POAs do
> not proxy traffic, they only redirect to other POAs. The entrys above only
> try to avoid a situation where the users POA is available but not the one
> Webaccess asks for a redirect, right?


Correct.
As for your original problem, I'd now start looking at a LAN trace. Not sure what exactly to look for, though 😕

Uwe

--
Novell Knowledge Partner
Please don't send me support related e-mail unless I ask you to do so.
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: auto refresh

Hi Mirko

Just to rule something out, is it possible to open port 8500 UDP in both directions for testing purposes?

If you can do that, then, as Uwe suggests, a LAN trace on UDP traffic on that port between your server in the DMZ and a Post Office might provide some clues.

Also, just a question, what is sitting between your WebAccess server in the DMZ and the people accessing it out on the internet?

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: auto refresh

Hi Mirko,

Further to what I've posted above, the next time auto-refresh stops working, kindly give us the output of the following command on your WebAccess server:

lsof -i :8500; netstat -tulpn | grep 8500

Looking forward to hearing back from you.

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: auto refresh


right now auto refresh is still working 🙂


laurabuckley wrote:

>
> Hi Mirko,
>
> Further to what I've posted above, the next time auto-refresh stops
> working, kindly give us the output of the following command on your
> WebAccess server:
>
> lsof -i :8500; netstat -tulpn | grep 8500
>
> Looking forward to hearing back from you.
>
> Cheers,
>
>



0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: auto refresh

Hi Mirko

Good to hear that it's still working.

The minute that it's not please give us the output of the "lsof" command - will assist tremendously in troubleshooting.

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: auto refresh


It happend again...


webmail2:~ # lsof -i :8500; netstat -tulpn | grep 8500
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
java 1029 tomcat 201u IPv6 14076071 0t0 UDP webmail2.rz.hs-
offenburg.de:fmtp
udp 125664 0 141.79.10.7:8500 :::*
1029/java
webmail2:~ # rctomcat6 restart
Shutting down Tomcat (/usr/share/tomcat6)

done
Starting Tomcat (/usr/share/tomcat6)
done
webmail2:~ # lsof -i :8500; netstat -tulpn | grep 8500
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
java 8883 tomcat 201u IPv6 19892652 0t0 UDP webmail2.rz.hs-
offenburg.de:fmtp
udp 0 0 141.79.10.7:8500 :::*
8883/java


Between WebAccess and Browser sits an Apache for reverse proxying.

Thanks,
Mirko




laurabuckley wrote:

>
> Hi Mirko
>
> Good to hear that it's still working.
>
> The minute that it's not please give us the output of the "lsof" command
> - will assist tremendously in troubleshooting.
>
> Cheers,
>
>


0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: auto refresh

Hi Mirko

In both instances of the command it would appear that the auto refresh service was running and listening.

Perhaps there is a timeout between the Apache and your WebAccess server?

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: auto refresh

laurabuckley wrote:


> Perhaps there is a timeout between the Apache and your WebAccess server?


A few minutes before I restarted tomcat I thought I should try if auto
refresh works if I access WebAccess directly, without proxy - and then I
forgot... 😕 Next time..
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: auto refresh

Hi Mirko,

Yes, testing auto refresh on WebAccess directly will assist in our troubleshooting process.

Please keep us informed 🙂

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.