2010-05-11 161 views
1

每次我尝试部署我的服务器端代码时,构建失败。如果我尝试重启我的机器,那么构建会成功,但如果我尝试构建后续时间,则会失败。我碰到下面的严重消息时,我尝试建立:GlassFish构建失败

SEVERE: "IOP00410216: (COMM_FAILURE) Unable to create IIOP listener on the specified host/port: localhost/3820" 
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 216 completed: No 


WARNING: Can not find resource bundle for this logger. class name that failed: org.glassfish.enterprise.iiop.impl.IIOPSSLSocketFactory 
     WARNING: Exception getting SocketInfo 
    java.lang.RuntimeException: Orb initialization eror 


WARNING: "IOP02310202: (OBJ_ADAPTER) Error in connecting servant to ORB" 
org.omg.CORBA.OBJ_ADAPTER: vmcid: SUN minor code: 202 completed: No 

以下是在严峻的方法的详细信息:

SEVERE: "IOP00410216: (COMM_FAILURE) Unable to create IIOP listener on the specified host/port: localhost/3820" 
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 216 completed: No 
     at com.sun.corba.ee.impl.logging.ORBUtilSystemException.createListenerFailed(ORBUtilSystemException.java:3835) 
     at com.sun.corba.ee.impl.logging.ORBUtilSystemException.createListenerFailed(ORBUtilSystemException.java:3855) 
     at com.sun.corba.ee.impl.transport.SocketOrChannelAcceptorImpl.initialize(SocketOrChannelAcceptorImpl.java:98) 
     at com.sun.corba.ee.impl.transport.CorbaTransportManagerImpl.getAcceptors(CorbaTransportManagerImpl.java:247) 
     at com.sun.corba.ee.impl.transport.CorbaTransportManagerImpl.addToIORTemplate(CorbaTransportManagerImpl.java:264) 
     at com.sun.corba.ee.spi.oa.ObjectAdapterBase.initializeTemplate(ObjectAdapterBase.java:131) 
     at com.sun.corba.ee.impl.oa.toa.TOAImpl.<init>(TOAImpl.java:130) 
     at com.sun.corba.ee.impl.oa.toa.TOAFactory.getTOA(TOAFactory.java:114) 
     at com.sun.corba.ee.impl.orb.ORBImpl.connect(ORBImpl.java:1740) 
     at com.sun.corba.ee.spi.presentation.rmi.StubAdapter.connect(StubAdapter.java:212) 
     at com.sun.corba.ee.impl.orb.ORBImpl.getIOR(ORBImpl.java:2194) 
     at com.sun.corba.ee.impl.orb.ORBImpl.getFVDCodeBaseIOR(ORBImpl.java:966) 
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
     at java.lang.reflect.Method.invoke(Method.java:597) 
     at org.glassfish.gmbal.generic.FacetAccessorImpl.invoke(FacetAccessorImpl.java:126) 
     at org.glassfish.gmbal.impl.MBeanImpl.invoke(MBeanImpl.java:440) 
     at org.glassfish.gmbal.impl.AttributeDescriptor.get(AttributeDescriptor.java:144) 
     at org.glassfish.gmbal.impl.MBeanSkeleton.getAttribute(MBeanSkeleton.java:569) 
     at org.glassfish.gmbal.impl.MBeanSkeleton.getAttributes(MBeanSkeleton.java:625) 
     at org.glassfish.gmbal.impl.MBeanImpl.getAttributes(MBeanImpl.java:389) 
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttributes(DefaultMBeanServerInterceptor.java:726) 
     at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttributes(JmxMBeanServer.java:665) 
     at org.glassfish.admin.amx.util.jmx.MBeanProxyHandler.getAttributes(MBeanProxyHandler.java:273) 
     at org.glassfish.admin.amx.core.proxy.AMXProxyHandler.attributesMap(AMXProxyHandler.java:1193) 
     at org.glassfish.admin.amx.core.proxy.AMXProxyHandler.attributesMap(AMXProxyHandler.java:1203) 
     at org.glassfish.admin.amx.core.proxy.AMXProxyHandler.handleSpecialMethod(AMXProxyHandler.java:414) 
     at org.glassfish.admin.amx.core.proxy.AMXProxyHandler._invoke(AMXProxyHandler.java:792) 
     at org.glassfish.admin.amx.core.proxy.AMXProxyHandler.invoke(AMXProxyHandler.java:526) 
     at $Proxy107.attributesMap(Unknown Source) 
     at org.glassfish.admin.amx.core.AMXValidator._validate(AMXValidator.java:642) 
     at org.glassfish.admin.amx.core.AMXValidator.validate(AMXValidator.java:1298) 
     at org.glassfish.admin.amx.impl.mbean.ComplianceMonitor$ValidatorThread.doRun(ComplianceMonitor.java:256) 
     at org.glassfish.admin.amx.impl.mbean.ComplianceMonitor$ValidatorThread.run(ComplianceMonitor.java:227) 
Caused by: java.net.BindException: Address already in use 
     at sun.nio.ch.Net.bind(Native Method) 
     at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119) 
     at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) 
     at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:52) 
     at org.glassfish.enterprise.iiop.impl.IIOPSSLSocketFactory.createServerSocket(IIOPSSLSocketFactory.java:293) 
     at com.sun.corba.ee.impl.transport.SocketOrChannelAcceptorImpl.initialize(SocketOrChannelAcceptorImpl.java:91) 
     ... 32 more 
+0

清理标签glassfishv3而不是玻璃鱼的东西。这在文本中没有修订标记,因此我会将修订标记保留在标记中... – vkraemer 2010-05-12 00:04:28

+0

@vkraemer:标记['v3']如何(http://stackoverflow.com/questions/tagged/v3)在其自己的意义? – BalusC 2010-05-12 00:24:07

+0

我可以编辑标签来统一它们...我没有必要的2k代表将版本ID移动到问题的文本中...我不希望版本信息在此问题上丢失.. 。所以v3标签就诞生了......我可能会编辑v3标签,之后我点击将版本标识符放入文本所需的信誉标志。 – vkraemer 2010-05-12 00:49:04

回答

0

我得到这个问题,因为我的程序意外崩溃,而服务器仍在运行。所以,每次发生这种情况时,我清理了代码崩溃时保持打开的tcp端口。

1

看起来有些进程正在使用的端口3820。既然你说第一次构建工作正常,我试图说,你的构建试图启动服务器,即使它已经开始......这会导致这种错误。如果您在说'构建'时包含更多关于您的意思的信息,则某人可能会给您一个更完整的答案。