Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 807573, 1 year ago
Unable to write to logs dir: /opt/j2ee_agents/am_websphere_agent/logs/debug
java.lang.Exception: Unable to write to logs dir: /opt/j2ee_agents/am_websphere_agent/logs/debug	at com.sun.identity.agents.tools.util.LogHelper.initializeLogsDir(LogHelper.java:115)	at com.sun.identity.agents.tools.util.Debug.initializeDebug(Debug.java:92)	at com.sun.identity.agents.tools.util.Debug.(Debug.java:140)	at com.sun.identity.agents.tools.util.ToolsConfiguration.initializeConfiguration(ToolsConfiguration.java:93)	at com.sun.identity.agents.tools.util.ToolsConfiguration.(ToolsConfiguration.java:164)	at com.sun.identity.agents.tools.admin.AgentAdmin.(AgentAdmin.java:355)	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:80)	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:44)	at java.lang.reflect.Constructor.newInstance(Constructor.java:315)	at java.lang.Class.newInstance3(Class.java:367)	at java.lang.Class.newInstance(Class.java:305)	at com.sun.identity.agents.tools.launch.AgentAdminLauncher.launchAdminTool(AgentAdminLauncher.java:203)	at com.sun.identity.agents.tools.launch.AgentAdminLauncher.main(AgentAdminLauncher.java:308)