Webcenter Content 11g Standalone Applications and Applets no Longer Start
(Doc ID 1497256.1)
Last updated on AUGUST 16, 2018
Applies to:Oracle WebCenter Content - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
Standalone Archiver does not start from command line.
In addition, when trying to start from the Archiver icon, the window just blinks.
When running Archiver, or any other of the Webcenter Content Server 11g standalone applications, the following error is displayed when running from command line:
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
JRockit aborted: Unknown error (50)
In order to use the Eclipse development environment to debug a custom component, the following debug mode settings were changed in the Webcenter Content environment, as follows:
and then in the WLS console, for the Webcenter Content server, this is added this to the server start..arguments:
-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n
This sets a listener on port 8000.
Then, in Eclipse, a debug configuration is created, and in the connection properties, set the Webcenter Content IP address, and port 8000.
As an example, this allows the ability to debug and set breakpoints inside a Custom Component that is in development, etc.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document