Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Observing an errornous stacktrace with jmxremote.access file #11654

Closed
dulanjalidilmi opened this issue Apr 27, 2021 · 1 comment
Closed

Observing an errornous stacktrace with jmxremote.access file #11654

dulanjalidilmi opened this issue Apr 27, 2021 · 1 comment

Comments

@dulanjalidilmi
Copy link

Describe the issue:
With the fix : [wso2-support/carbon-kernel/pull/1040/] for [wso2/product-ei/issues/5200] we have added new file jmxremote.access file in EI 6.5.0 in <EI_HOME>/conf/security. Since IS 5.8.0 is using the same kernel version (4.4.40), erroneous stack trace during server startup will be appeared as follows due to unavailability of the file.

[2021-04-20 23:42:21,010] ERROR {org.wso2.carbon.core.init.JMXServerManager} -  Could not initialize RMI server
java.lang.IllegalArgumentException: /Users/wso2/tharindub/patch/QUICKLAUNCHSUB-295/test-startup-issue/wso2is-5.8.0/repository/conf/security/jmxremote.access (No such file or directory)
	at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:375)
	at org.wso2.carbon.core.init.JMXServerManager.startJMXService(JMXServerManager.java:128)
	at org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.completeInitialization(StartupFinalizerServiceComponent.java:209)
	at org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.serviceChanged(StartupFinalizerServiceComponent.java:317)
	at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
	at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
	at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
	at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
	at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
	at org.wso2.carbon.server.admin.internal.ServerAdminServiceComponent.activate(ServerAdminServiceComponent.java:106)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
	at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
	at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
	at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
	at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
	at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)

How to reproduce:
Start wum updated IS 5.8.0 pack.

Expected behavior:

Environment information (Please complete the following information; remove any unnecessary fields) :

  • Product Version: IS 5.8.0

Optional Fields

Related issues:

Suggested labels:

@isharak
Copy link
Member

isharak commented Nov 6, 2024

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!

@isharak isharak closed this as completed Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants