websphere's specific error

I am getting this error while stoping the server. any ideas ??

-RT

com.intellij.j2ee.webSphere.client.AdminExceptionWrapper: com.ibm.websphere.management.exception.AdminException:

at com.intellij.j2ee.webSphere.client.AppManagementWrapperImpl.startApplication(AppManagementWrapperImpl.java:99)
at com.intellij.j2ee.webSphere.runDebug.serverInstance.impl.WebSphereInstanceImpl$9.run(WebSphereInstanceImpl.java:209)
at com.intellij.j2ee.webSphere.runDebug.serverInstance.impl.ServerRequestingThreadImpl.runRequest(ServerRequestingThreadImpl.java:123)
at com.intellij.j2ee.webSphere.runDebug.serverInstance.impl.ServerRequestingThreadImpl.run(ServerRequestingThreadImpl.java:100)
Caused by: com.ibm.websphere.management.exception.AdminException:
at com.ibm.websphere.management.application.AppManagementProxy.proxyInvoke(AppManagementProxy.java:175)
at com.ibm.websphere.management.application.AppManagementProxy.startApplication(AppManagementProxy.java:535)
at com.intellij.j2ee.webSphere.client.AppManagementWrapperImpl.startApplication(AppManagementWrapperImpl.java:96)
... 3 more
Caused by: javax.management.MBeanException: null nested exception is com.ibm.websphere.management.exception.AdminException:
ADMA0017E: The context for ApplicationModule cannot be obtained.
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.handleAdminFault(SOAPConnectorClient.java:723)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeTemplate(SOAPConnectorClient.java:690)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnectorClient.java:547)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnectorClient.java:367)
at $Proxy48.invoke(Unknown Source)
at com.ibm.ws.management.AdminClientImpl.invoke(AdminClientImpl.java:191)
at com.ibm.websphere.management.application.AppManagementProxy.proxyInvoke(AppManagementProxy.java:169)
... 5 more
Caused by: com.ibm.websphere.management.exception.AdminException: ADMA0017E:
The context for ApplicationModule cannot be obtained.
at com.ibm.ws.management.application.AppManagementImpl.startApplication(AppManagementImpl.java:634)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java)
at java.lang.reflect.Method.invoke(Method.java)
at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1366)
at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:1012)
at mx4j.server.interceptor.InvokerMBeanServerInterceptor.invoke(InvokerMBeanServerInterceptor.java:233)
at mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:128)
at mx4j.server.interceptor.SecurityMBeanServerInterceptor.invoke(SecurityMBeanServerInterceptor.java:86)
at mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:128)
at mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:128)
at mx4j.server.interceptor.ContextClassLoaderMBeanServerInterceptor.invoke(ContextClassLoaderMBeanServerInterceptor.java:167)
at mx4j.server.MX4JMBeanServer.invoke(MX4JMBeanServer.java:1249)
at com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.java:901)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java)
at com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:817)
at com.ibm.ws.management.connector.AdminServiceDelegator.invoke(AdminServiceDelegator.java:139)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java)
at java.lang.reflect.Method.invoke(Method.java)
at com.ibm.ws.management.connector.soap.SOAPConnector.invoke(SOAPConnector.java:325)
at com.ibm.ws.management.connector.soap.SOAPConnector.service(SOAPConnector.java:193)
at com.ibm.ws.management.connector.soap.SOAPConnection.handleRequest(SOAPConnection.java:55)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:641)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:469)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1332)


4 comments

Hello Rambabu,

Please provide more information:

1) Was your application deployed to WebSphere successfully?

2) Did you stop the server from IDEA by the 'Stop' button or in some other
way?

I am getting this error while stoping the server. any ideas ??

-RT

---
Nikolay Chashnikov
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0

Hello Nikolay,
Thanks for your reply. First time application didn't deploy properly and
second time it was deployed and I got same error both times.
I stop the server using stop button.

My second error is unable to find the classes, may be problem with classloader
policy in websphere env. I want to change the classloader policy to module
instead of application, How can I change it.

-RT



Error 500: java.lang.LinkageError: LinkageError while defining class: com.xxx.xxx.xxx.web.data.ExportJdeSearchFormData
Could not be defined due to: com/xxx/xxx/xxx/web/data/ExportJdeSearchFormData
(Unsupported major.minor version 49.0) This is often caused by having a class
defined at multiple locations within the classloader hierarchy. Other potential
causes include compiling against an older or newer version of the class that
has an incompatible method signature. Dumping the current context classloader
hierarchy: ==> indicates defining classloader com.ibm.ws.classloader.CompoundClassLoader@3d3d953a
Local ClassPath: C:\Program Files\IBM\WebSphere\AppServer\profiles\default\installedApps\rambabu

Hello Rambabu,

Please provide more information:

1) Was your application deployed to WebSphere successfully?

2) Did you stop the server from IDEA by the 'Stop' button or in some
other way?

>> I am getting this error while stoping the server. any ideas ??
>>
>> -RT
>>

---
Nikolay Chashnikov
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"



0

Hello Rambabu,

Please file a Jira request for your first problem.

The second problem seems to be caused by an inappropriate JDK version in
your project. Try to set JDK 1.4 instead of 1.5.

Hello Nikolay,
Thanks for your reply. First time application didn't deploy properly
and
second time it was deployed and I got same error both times.
I stop the server using stop button.

My second error is unable to find the classes, may be problem with
classloader policy in websphere env. I want to change the classloader
policy to module instead of application, How can I change it.

-RT

Error 500: java.lang.LinkageError: LinkageError while defining class:
com.xxx.xxx.xxx.web.data.ExportJdeSearchFormData Could not be defined
due to: com/xxx/xxx/xxx/web/data/ExportJdeSearchFormData (Unsupported
major.minor version 49.0) This is often caused by having a class
defined at multiple locations within the classloader hierarchy. Other
potential causes include compiling against an older or newer version
of the class that has an incompatible method signature. Dumping the
current context classloader hierarchy: ==> indicates defining
classloader com.ibm.ws.classloader.CompoundClassLoader@3d3d953a
Local ClassPath: C:\Program
Files\IBM\WebSphere\AppServer\profiles\default\installedApps\rambabu

>> Hello Rambabu,
>>
>> Please provide more information:
>>
>> 1) Was your application deployed to WebSphere successfully?
>>
>> 2) Did you stop the server from IDEA by the 'Stop' button or in some
>> other way?
>>
>>> I am getting this error while stoping the server. any ideas ??
>>>
>>> -RT
>>>
>> ---
>> Nikolay Chashnikov
>> Software Developer
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
---
Nikolay Chashnikov
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0

Hello Nikolay,
http://www.jetbrains.net/jira/browse/IDEA-6803

-RT

Hello Rambabu,

Please file a Jira request for your first problem.

The second problem seems to be caused by an inappropriate JDK version
in your project. Try to set JDK 1.4 instead of 1.5.

>> Hello Nikolay,
>> Thanks for your reply. First time application didn't deploy properly
>> and
>> second time it was deployed and I got same error both times.
>> I stop the server using stop button.
>> My second error is unable to find the classes, may be problem with
>> classloader policy in websphere env. I want to change the classloader
>> policy to module instead of application, How can I change it.
>>
>> -RT
>>
>> Error 500: java.lang.LinkageError: LinkageError while defining class:
>> com.xxx.xxx.xxx.web.data.ExportJdeSearchFormData Could not be defined
>> due to: com/xxx/xxx/xxx/web/data/ExportJdeSearchFormData (Unsupported
>> major.minor version 49.0) This is often caused by having a class
>> defined at multiple locations within the classloader hierarchy. Other
>> potential causes include compiling against an older or newer version
>> of the class that has an incompatible method signature. Dumping the
>> current context classloader hierarchy: ==> indicates defining
>> classloader com.ibm.ws.classloader.CompoundClassLoader@3d3d953a
>> Local ClassPath: C:\Program
>> Files\IBM\WebSphere\AppServer\profiles\default\installedApps\rambabu
>>
>>> Hello Rambabu,
>>>
>>> Please provide more information:
>>>
>>> 1) Was your application deployed to WebSphere successfully?
>>>
>>> 2) Did you stop the server from IDEA by the 'Stop' button or in some
>>> other way?
>>>
>>>> I am getting this error while stoping the server. any ideas ??
>>>>
>>>> -RT
>>>>
>>> ---
>>> Nikolay Chashnikov
>>> Software Developer
>>> JetBrains, Inc
>>> http://www.jetbrains.com
>>> "Develop with pleasure!"

---
Nikolay Chashnikov
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"



0

Please sign in to leave a comment.