Welcome to OGeek Q&A Community for programmer and developer-Open, Learning and Share
Welcome To Ask or Share your Answers For Others

Categories

0 votes
434 views
in Technique[技术] by (71.8m points)

ibm mobilefirst - IBM Worklight 6.2: JMX configuration error. Unable to obtain MBeans

I have IBM Worklight 6.2 development environment with the following setup.

  1. Oracle Java 1.7

  2. Eclipse 4.3

  3. IBM Worklight 6.2 Developer Edition

A sample Hybrid project had been created and deployed in the Worklight development server and app works fine in the Mobile Browser Simulator.

I am getting the following error in Worklight Server console in Eclipse:

[ERROR ] Failed to obtain JMX connection to access an MBean.

There might be a JMX configuration error: Read timed out

[ERROR ] FWLSE3000E: A server error was detected.

FWLSE3012E: JMX configuration error. Unable to obtain MBeans. Reason: "Read timed out".

And also I am getting the following error in Worklight Console[Web Console].

FWLSE3012E: JMX configuration error. Unable to obtain MBeans. Reason: "Read timed out".

Note: I have read the following questions but no luck.

  1. IBM Worklight - Can't run an app on WebSphere Application Server

  2. How to solve management service not starting up in Worklight 6.2

Additional Info:

I used to get the following error whenever the Worklight development server is started from eclipse.

*[WARNING ] CWNEN0070W: The javax.ws.rs.QueryParam annotation class will not be recognized because it was loaded from the null location rather than from a product class loader.

[WARNING ] CWNEN0070W: The javax.ws.rs.PathParam annotation class will not be recognized because it was loaded from the null location rather than from a product class loader.

[WARNING ] CWNEN0070W: The javax.ws.rs.HeaderParam annotation class will not be recognized because it was loaded from the null location rather than from a product class loader.

[WARNING ] CWNEN0070W: The javax.ws.rs.CookieParam annotation class will not be recognized because it was loaded from the null location rather than from a product class loader.

[WARNING ] CWNEN0070W: The javax.ws.rs.core.Context annotation class will not be recognized because it was loaded from the null location rather than from a product class loader.

[WARNING ] CWNEN0070W: The javax.ws.rs.MatrixParam annotation class will not be recognized because it was loaded from the null location rather than from a product class loader.*

I hope necessary information's I have provided. Let me know if u still need.

See Question&Answers more detail:os

与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
Welcome To Ask or Share your Answers For Others

1 Reply

0 votes
by (71.8m points)

The JMX timeout error in Worklight 6.2 is a known issue.

Typically when this error occurs to me, a way to resolve it is to either 'wait' a while and then to stop & restart the Worklight Server (in Eclipse > Servers view > 'play' button). Another option is to restart Eclipse.

You can also try the suggestions from the comments:

Try to edit the file WorklightServerConfig/servers/worklight/jvm.options in your Eclipse workspace, adding the line "-Dcom.ibm.ws.jmx.connector.client.rest.readTimeout=180000". Then stop and restart the Worklight Development Server.

and

Try to edit the file WorklightServerConfig/servers/worklight/server.xml and add in the section the following line, then restart and try again:

<executor name="LargeThreadPool" id="default" coreThreads="40" maxThreads="80" keepAlive="60s" stealPolicy="STRICT" rejectedWorkPolicy="CALLER_RUNS" />

Best is to open a PMR (support ticket) and request an iFix as this is due to be fixed.


与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
OGeek|极客中国-欢迎来到极客的世界,一个免费开放的程序员编程交流平台!开放,进步,分享!让技术改变生活,让极客改变未来! Welcome to OGeek Q&A Community for programmer and developer-Open, Learning and Share
Click Here to Ask a Question

...