You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a difference in standalone-sip.xml between JBoss AS7 and EAP that breaks the scripts that enable logging to rvd.log. In fact, the xml namespace "urn:jboss:domain:logging:1.5" in EAP is different from the the respective "urn:jboss:domain:logging:1.2" in AS7. config-rvd-logging.sh won't pick it up and update it accordingly.
We have to use a different approach there that does not rely on this namespace.
Meanwhile, a workaround to enable logging for Designer is to rename RC_HOME/standalone/deployments/restcomm-rvd.war/WEB-INF/classes/log4j-standalone.xml
to RC_HOME/standalone/deployments/restcomm-rvd.war/WEB-INF/classes/log4j.xml
and restart server
The text was updated successfully, but these errors were encountered:
There is a difference in standalone-sip.xml between JBoss AS7 and EAP that breaks the scripts that enable logging to rvd.log. In fact, the xml namespace "urn:jboss:domain:logging:1.5" in EAP is different from the the respective "urn:jboss:domain:logging:1.2" in AS7. config-rvd-logging.sh won't pick it up and update it accordingly.
We have to use a different approach there that does not rely on this namespace.
Meanwhile, a workaround to enable logging for Designer is to rename
RC_HOME/standalone/deployments/restcomm-rvd.war/WEB-INF/classes/log4j-standalone.xml
to
RC_HOME/standalone/deployments/restcomm-rvd.war/WEB-INF/classes/log4j.xml
and restart server
The text was updated successfully, but these errors were encountered: