应用程序中报错java.lang.reflect.InvocationTargetException
答案:4 悬赏:0
解决时间 2021-03-10 02:02
- 提问者网友:敏感魔鬼
- 2021-03-09 03:33
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.sun.javaws.Launcher.executeApplication(Unknown Source)
at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
at com.sun.javaws.Launcher.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Failed to generate class for weblogic.jndi.internal.ServerNamingNode_WLStub ]
at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:662)
at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:651)
at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:59)
at weblogic.jndi.WLInitialContextFactoryDelegate.newRootNamingNodeStub(WLInitialContextFactoryDelegate.java:489)
at weblogic.jndi.WLInitialContextFactoryDelegate.newRemoteContext(WLInitialContextFactoryDelegate.java:452)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:372)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:339)
at weblogic.jndi.Environment.getContext(Environment.java:154)
at weblogic.jndi.internal.NamingNodeReplicaHandler.failOver(NamingNodeReplicaHandler.java:108)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:232)
at weblogic.jndi.internal.ServerNamingNode_WLStub.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:337)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:332)
at weblogic.rmi.Naming.getContext(Naming.java:262)
at weblogic.rmi.Naming.lookup(Naming.java:72)
at com.neusoft.dao.ConnConfig.initRMI(ConnConfig.java:122)
at com.neusoft.dao.ConnConfig.getRmiDao(ConnConfig.java:57)
at com.neusoft.frame.LoginUser.isSystemBusy(LoginUser.java:550)
at com.neusoft.frame.LoginUser.checkUser(LoginUser.java:423)
at com.neusoft.frame.LoginUser.show(LoginUser.java:364)
at com.neusoft.frame.ClientApp.<init>(ClientApp.java:73)
at com.neusoft.frame.ClientApp.main(ClientApp.java:140)
... 9 more
我实在是看不懂。。。我不知道财富怎么赠送,所以悬赏的不多,请包涵~~
最佳答案
- 二级知识专家网友:而你却相形见绌
- 2021-03-09 04:01
可以确认是jar版本问题,你把2处应用的jar版本都统一到你能用的那个版本吧
全部回答
- 1楼网友:许你一世温柔
- 2021-03-09 06:12
重装weblogic试一下
- 2楼网友:你把微笑给了谁
- 2021-03-09 05:34
权限不够
- 3楼网友:狙击你的心
- 2021-03-09 04:23
InvocationTargetException 是一种包装由调用方法或构造方法所抛出异常的受查异常。这个异常并不是Eclipse插件开发特有的,而是标准JDK中的,它定义在 java.lang.reflect包下。在进行Java开发的时候很少会接触到这个异常,不过在进行Eclipse插件开发中则不同,很多API都声明抛出此类异常,因此必须对此异常进行处理。
例如,我们开发一个方法用来统一处理异常:
private static void handleException(Exception e)
{
MessageDialog.openError(Activator.getDefault().getWorkbench()
.getDisplay().getActiveShell(), "error", e.getMessage());
e.printStackTrace();
}
我们发现当传递来的参数e为InvocationTargetException 的时候弹出的对话框中的消息是空的,查看InvocationTargetException 的源码得知InvocationTargetException 并没有覆盖getMessage方法,所以消息当然是空的了。我们需要调用InvocationTargetException 的getTargetException方法得到要被包装的异常,这个异常才是真正我们需要的异常。修改代码如下所示:
private static void handleException(Exception e)
{
String msg = null;
if (e instanceof InvocationTargetException)
{
Throwable targetEx = ((InvocationTargetException) e)
.getTargetException();
if (targetEx != null)
{
msg = targetEx.getMessage();
}
} else
{
msg = e.getMessage();
}
MessageDialog.openError(Activator.getDefault().getWorkbench()
.getDisplay().getActiveShell(), "error", msg);
e.printStackTrace();
}
我要举报
如以上问答内容为低俗、色情、不良、暴力、侵权、涉及违法等信息,可以点下面链接进行举报!
大家都在看
推荐资讯