- This topic has 7 replies, 3 voices, and was last updated 10 years, 8 months ago by
.
-
Posts
-
I am using MyEclipse 2013 SR1 and configured to work with Websphere 7 App Server. I can start the server without any issue but while stopping the server from MyEclipse it throws an error but eventually shuts down. The error message is:
[7/24/13 11:03:26:537 EDT] 00000000 WsServerStop E ADMU3002E: Exception attempting to process server server1 [7/24/13 11:03:26:537 EDT] 00000000 WsServerStop E ADMU3007E: Exception javax.management.JMRuntimeException: >> SERVER (id=4773e3aa, host=DEVWIN1I.devtech.cya.com) TRACE START: >> javax.management.JMRuntimeException: ADMN0022E: Access is denied for the stop operation on Server MBean because of insufficient or empty credentials. >> at com.ibm.ws.management.AdminServiceImpl.preInvoke(AdminServiceImpl.java:2370) >> at com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.java:1309) >> at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118) >> at com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:1225) >> at com.ibm.ws.management.connector.AdminServiceDelegator.invoke(AdminServiceDelegator.java:181) >> at com.ibm.ws.management.connector.rmi.RMIConnectorService.invoke(RMIConnectorService.java:282) >> at com.ibm.ws.management.connector.rmi._RMIConnectorService_Tie.invoke(_RMIConnectorService_Tie.java:395) >> at com.ibm.ws.management.connector.rmi._RMIConnectorService_Tie._invoke(_RMIConnectorService_Tie.java:160) >> at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:622) >> at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:475) >> at com.ibm.rmi.iiop.ORB.process(ORB.java:504) >> at com.ibm.CORBA.iiop.ORB.process(ORB.java:1571) >> at com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2771) >> at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2640) >> at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:63) >> at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:118) >> at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604) >> SERVER (id=4773e3aa, host=DEVWIN1I.devtech.cya.com) TRACE END.But I can start and stop the server from command prompt without any errors. I tried setting up the username & password in client.props files but that did not help. I also tried passing the username & password using optional shutdown arguments but that did not help either.
Any help will be appreciated…
Thanks,
moutts,
Do you have administrative security enabled on the WebSphere 7.0 profile that you are using from MyEclipse? If enabled, please make sure that ‘Username’ and ‘Password’ should match the server admin login and password (these are created while installing the WAS 7.0 server in your machine).
In case the server doesn’t have password, this option has to be disabled. It is recommended that you don’t enable administrative security. (Please take a look at the attached screenshot for reference)
Hope this helps.
Hi Pradeep,
The screenshot which you attached is MyEclipse Blue and the MyEclipse 2013 SR1 version does not have those options to specify the administrative security credentials. I am using MyEclipse 2013 SR1.
Also disabling Administrative Security directly on Websphere is not an option for me. In the previous versions of MyEclipse that I have used never had issues stopping the server.Is there any other additional configuration needs to be done in MyEclipse 2013 SR1 for Websphere 7 to stop the server gracefully?
Thanks,
moutts,
Please refer Brian’s reply in the following link. Though the issue is different, the underlying cause is probably the same.
https://www.genuitec.com/forums/topic/deploying-ear-fails-on-websphere/#post-340879&highlight=#134574So is this an official disclosure from MyEclipse Development team that we have to move towards MyEclipse Blue if we want to continue our development with Websphere application servers? or we should just stay in MyEclipse10 and not upgrade to MyEclipse 2013 SR1?
Thanks,
moutss,
MyEclipse never did support WAS 7 – we provided a connector only up to version 6.1; so using WAS 7 with MyEclipse has always been unsupported. We have not developed / tested the WAS 7 connector to work with MyEclipse Pro, but added support to MyEclipse Blue.
In our own testing, we did try to take a look and see if 2013 had specifically caused some breaks, but we found the same problems using WAS 7 with MyEclipse 10.x that we did with 2013 – fixing these are low priority given the above, and the fact that we have another exclusively developed product for WebSphere.
I would recommend writing to sales@genuitec.com with a link to this thread for an extended trial of Blue and/or to see if your existing accounts can be upgraded.
If you have any further questions, please ask.
Brian,
Yes I just went back to MyEclipse 10 and observed the same behavior as you explained. I realized previously we were using MyEclipse 10 with WAS 6.1 which explains why I didn’t see these behavior in previous versions.Now coming back to your recommendation to use MyEclipse Blue, we develop software that are intended to deploy on different versions of Weblogic, Websphere & JBoss servers and not just for Websphere. So using MyEclipse Blue is not a solution for our team.
So I guess we have no option but to just live with these bugs in this version and hoping that to be fixed in some future releases 🙁 Not to mention Redeploy feature is also not working for WAS 7.
Could you please atleast open these defects with your development team and provide me with details when is the next version or SP for the Pro edition is scheduled to be released?
Now coming back to your recommendation to use MyEclipse Blue, we develop software that are intended to deploy on different versions of Weblogic, Websphere & JBoss servers and not just for Websphere. So using MyEclipse Blue is not a solution for our team.
MyEclipse Blue is a superset of MyEclipse – while it does have advanced connectors for WebSphere, it includes all the connectors that MyEclipse has as well – so deploying to Weblogic and JBoss with Blue is not a problem. This is precisely why Blue would be great for your company, do give it a shot 🙂
