OpenEdge 12 Explorer Tomcat error

Posted by Andrzej.Sz on 21-May-2019 18:42

Hi,

I've installed OE12 DevStudio under Win 10 64-bit system. I try to run OE Explorer but Tomcat error arrives.

"HTTP Status 404 – Not Found , The origin server did not find a current representation for the target resource or is not willing to disclose that one exists."

admserv.log contains few [STDERR] errors recorded during installation:

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".

SLF4J: Defaulting to no-operation (NOP) logger implementation

SLF4J: See www.slf4j.org/codes.html for further details.

SLF4J: Failed to load class "org.slf4j.impl.StaticMDCBinder".

SLF4J: Defaulting to no-operation MDCAdapter implementation.

SLF4J: See www.slf4j.org/codes.html for further details.

Could somebody help me to solve the problem?

Regards

Andrzej

Posted by Matt Baker on 07-Jun-2019 21:11

bug number is ADAS-17756.  if you want to call tech support they can attach your info to the bug so it can be prioritized.

There is a message in the promsgs file that should never be translated and OEM tests this to ensure the message is present to ensure the promsgs file is "recent" enough to be used. Looks like that message got translated.

All Replies

Posted by Sai Tharun Kollampally on 22-May-2019 05:34

Hi,

Are you getting "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder" while ActiveMQ broker configuration or at Application Server instance initialization in admserv.log file?

It is because earlier(prior to 12.0) we used to have a common jar for ActiveMQ called as activemq-all-5.15.6.jar which has been divided into several jars, only the ones which are needed.Same with Progress Application Server. So we can include either logback-classic-1.0.13.jar which is available at $DLC/java/ext or logback-classic-1.2.3.jar which is available at $DLC/servers/pasoe/common/lib/ to getrid of this error.

But I think it is not related to OE Explorer 404 error, as SLF4J is related to logging mechanism for Application Server.

I tried the same with OEM but it is working absolutely fine.

Can you please check the URL once?

Thanks,

Sai Tharun Kollampally

Posted by Stefan Drissen on 22-May-2019 07:50

I also have the same errors about the logger, but they are not blocking my AdminServer / OpenEdge Explorer (not Management) from starting:

...
[2019/05/22@09:28:13.699+0200] [3] [ActiveMQS]             The optional ActiveMQ broker configuration file c:\progress\oe12.0\properties\activemq.xml does not exist.  Default configuration will be used. (17212)
[2019/05/22@09:28:13.741+0200] [3] [STDERR]                SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
[2019/05/22@09:28:13.741+0200] [3] [STDERR]                SLF4J: Defaulting to no-operation (NOP) logger implementation
[2019/05/22@09:28:13.741+0200] [3] [STDERR]                SLF4J: See www.slf4j.org/codes.html for further details.
[2019/05/22@09:28:15.892+0200] [2] [ManagementPlugin]      OE Management remote monitoring properties. (11199)
...
[2019/05/22@09:28:15.997+0200] [3] [Database]              Connecting to socket... (8463)
[2019/05/22@09:28:16.001+0200] [3] [STDERR]                SLF4J: Failed to load class "org.slf4j.impl.StaticMDCBinder".
[2019/05/22@09:28:16.001+0200] [3] [STDERR]                SLF4J: Defaulting to no-operation MDCAdapter implementation.
[2019/05/22@09:28:16.001+0200] [3] [STDERR]                SLF4J: See www.slf4j.org/codes.html for further details.
[2019/05/22@09:28:16.026+0200] [3] [Database]              Opening database server listening port on address /0.0.0.0:7850
[2019/05/22@09:28:16.027+0200] [3] [DatabaseAgent]         Opening agent socket connection on address /0.0.0.0:8847
[2019/05/22@09:28:18.980+0200] [3] [PAS]                   Finished Progress Application Server instance initialization
...

What /was/ blocking was the need to adjust the default ports in the management.properties file which I have never had to do prior to 12.0.
Subsequently, after changing, I also need to change the "remote" AdminServer properties in OEE to also use that port.
Posted by Andrzej.Sz on 22-May-2019 14:57

Stefan,

I've installed OE12 with default ports (port=20931, adminport=7847, httpport=9090, agent port=8847). I'm not sure what to do to adjust ports. Which port parameters in management.properties file to uncomment (port=6835, discoveryPort=6840, sslPort=7278)? What are "remote" AdminServer properties?

Posted by Andrzej.Sz on 22-May-2019 15:43

I agree, it seems to be not related to OE Explorer.

default URL call:   http://localhost:9090/

Posted by Stefan Drissen on 22-May-2019 19:02

[quote user="Andrzej.Sz"]

I've installed OE12 with default ports (port=20931, adminport=7847, httpport=9090, agent port=8847). I'm not sure what to do to adjust ports. Which port parameters in management.properties file to uncomment (port=6835, discoveryPort=6840, sslPort=7278)? What are "remote" AdminServer properties?

[/quote]

I have 12.0 installed alongside 11.7 and 11.6 and have "standard" non-default ports for every version. With 12.0, for the first time, I needed to adjust the management.properties ports - not sure why. I just uncommented and increased them all by 1.

A co-worker had the same issue with 12.0 vs 11.6. Since I already had both 11.7 and 11.6 installed I'm a bit confused as to why they did not already have a conflict.

The remote AdminServer properties come into play once you can connect to OEE (default: localhost:9090) - until I fixed all of the above, OpenEdge Management (which seems to be a separate new tomcat thing in 12.0) considered my AdminServer 'access denied' / offline. 

Posted by Ruben Dröge on 23-May-2019 06:17

[mention:f74159d0d7ac493497e441f53f353b10:e9ed411860ed4f2ba0265705b8793d05] : you are correct, we moved from Jetty to Tomcat (PAS) for OpenEdge Management / Explorer and it's no longer tied to the AdminServer.

Please check docs.progress.com/.../OpenEdge-Management-AdminServer-Configuration-Upgrade.html for more information regarding the fathom / PAS properties.

Posted by Stefan Drissen on 23-May-2019 06:47

[quote user="Ruben Dröge"]

Please check docs.progress.com/.../OpenEdge-Management-AdminServer-Configuration-Upgrade.html for more information regarding the fathom / PAS properties.

[/quote]
Thanks for that document - I think that is what https://docs.progress.com/bundle/openedge-whats-new/page/OpenEdge-Management-now-runs-independently-of-AdminServer.html is trying to point to with "For details, see Migrate OpenEdge Management from Jetty to Progress Application Server in Upgrade to OpenEdge 12." (and failing 404).
Posted by Andrzej.Sz on 07-Jun-2019 20:26

I've changed installation default language from polish to american. HTTP status 404 error disappeared. Fathom and OE Explorer start without problems.

Posted by Andrzej.Sz on 07-Jun-2019 20:32

My co-worker discovered these error in installation log:

2019-05-31 15:15:18,675 ERROR [Fathom] [Catalina-startStop-1] - ** Failed to load license manager: Unable to instantiate license manager class com.progress.common.licensemgr.LicenseMgr: NULL

2019-05-31 15:15:18,675 INFO  [Fathom] [Catalina-startStop-1] - Enabling OpenEdge Explorer

2019-05-31 15:15:20,425 ERROR [Fathom] [Catalina-startStop-1] - promsgs file is not the correct version. Consult the Fathom Release notes for more information

2019-05-31 15:15:20,425 ERROR [Fathom] [Catalina-startStop-1] - ** Progress promsgs file not compatible

Posted by Matt Baker on 07-Jun-2019 21:07

Thanks Andrzej.  that is a very very old sanity check from pre 10 days when OEM was a separate install. It is one of those things that isn't supposed to be triggered ever.  I'll log a bug for this.

Posted by Matt Baker on 07-Jun-2019 21:11

bug number is ADAS-17756.  if you want to call tech support they can attach your info to the bug so it can be prioritized.

There is a message in the promsgs file that should never be translated and OEM tests this to ensure the message is present to ensure the promsgs file is "recent" enough to be used. Looks like that message got translated.

Posted by Andrzej.Sz on 07-Jun-2019 21:31

Thank you Matt. It isn't critical now.

More important problem is described here community.progress.com/.../58418

This thread is closed