This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
NB 6.0 20070716120000 & GF v2 b55 bundled: EAR project disable/enable with MSD Bean (queue) referenced by servlet (Send JMS) fails ejb-project : 1 session bean stateless/local int , 1 MSD Bean with project destination (queue) with onMessage() prints the msg.getTimestamp() web-project : 1 servlet + Send JMS call to the queue. Deployment & Run is ok: can see the deployment of the JMS resources and when accessing the servlet can see the "got message timestamp-value": <<got message 1184750566796 got message 1184750590421 got message 1184750613656 >> at disable: << ADM1041:Sent the event to instance:[ApplicationDeployEvent -- disable EnterpriseApplication2] CORE5022: All ejb(s) of [EnterpriseApplication2] were unloaded successfully! ... >> at enable: getting namingException: << ADM1041:Sent the event to instance:[ApplicationDeployEvent -- enable EnterpriseApplication2] "DPL8007: Invalid Deployment Descriptors element message-destination value null" endpoint.determine.destinationtype LDR5010: All ejb(s) of [EnterpriseApplication2] loaded successfully! NAM0007 : Message Destination Reference java:comp/env/myQueue1 has not been linked to a Message Destination WEB0123: WebModule [/EnterpriseApplication2-war] failed to deploy and has been disabled javax.naming.NamingException: Message Destination Reference java:comp/env/myQueue1 has not been resolved at com.sun.enterprise.naming.NamingManagerImpl.bindObjects(NamingManagerImpl.java:521) at com.sun.enterprise.web.WebModuleContextConfig.configureResource(WebModuleContextConfig.java:220) ... >>> joining the server.log file in attachement.
Created attachment 45299 [details] server log for jms resources
Please attach the project too.
see if something similar happens if you deploy the ear file and then use disable/enable on the ent app... (via asadmin)
Created attachment 45367 [details] adding the zip of the app after clean proj (zip on windows)
NB 6.0 20070716120000 & GF v2 b55 bundled: First Try: -------------------- app deployed again/run ok, kept the InternetExplorer window connection to http://localhost:8080/EnterprsieAppication2.war/NewServlet. 1) disable ent app with asadmin cmd prompt window: asadmin>disable EnterpriseApplication2 Command disable executed successfully. asadmin in GlassFish v2 server.log: << got message 1184830690343 ADM1041:Sent the event to instance:[ApplicationDeployEvent -- disable EnterpriseApplication2] CORE5022: All ejb(s) of [EnterpriseApplication2] were unloaded successfully! MQJMSRA_DC2001: connectionId=7365096082285926144:_destroy():called on a connection that was not closed. MQJMSRA_DC2001: connectionId=7365096082285926145:_destroy():called on a connection that was not closed. MQJMSRA_MC2001: createConnection API used w/ username, password for Container Auth MQJMSRA_MC2001: createConnection API used w/ username, password for Container Auth >> 2) enable ent app with asadmin: asadmin>enable EnterpriseApplication2 Command enable executed successfully asadmin> In GlassFish V2 server.log: we get the same error as with IDE-Services/App Enable ADM1041:Sent the event to instance:[ApplicationDeployEvent -- enable EnterpriseApplication2] "DPL8007: Invalid Deployment Descriptors element message-destination value null" endpoint.determine.destinationtype LDR5010: All ejb(s) of [EnterpriseApplication2] loaded successfully! NAM0007 : Message Destination Reference java:comp/env/myQueue1 has not been linked to a Message Destination WEB0123: WebModule [/EnterpriseApplication2-war] failed to deploy and has been disabled javax.naming.NamingException: Message Destination Reference java:comp/env/myQueue1 has not been resolved at com.sun.enterprise.naming.NamingManagerImpl.bindObjects(NamingManagerImpl.java:521) at com.sun.enterprise.web.WebModuleContextConfig.configureResource(WebModuleContextConfig.java:220) ... etc. Second Try: --------------- ** Undeploy the app (to start properly the test, undeploy the resources) ** close the browser ** stop the server (as cannot do deploy again: due to issue 110131) ** start the server ** "Undeploy & Deploy" action ** "Run" ==>> http://localhost:8080/EnterpriseApplication2-war add the Servlet URI http://localhost:8080/EnterpriseApplication2-war/NewServlet (refresh 2-3times to see the messages sent and received in the server.log) ** close the browser window (close the connection) ** Disable the app with asadmin OK ** Enable the app with asadmin: same problem as in upper cases. In the server.log can see: Command disable executed successfully. asadmin in GlassFish v2 server.log: << got message 1184830690343 ADM1041:Sent the event to instance:[ApplicationDeployEvent -- disable EnterpriseApplication2] CORE5022: All ejb(s) of [EnterpriseApplication2] were unloaded successfully! MQJMSRA_DC2001: connectionId=7365096082285926144:_destroy():called on a connection that was not closed. MQJMSRA_DC2001: connectionId=7365096082285926145:_destroy():called on a connection that was not closed. MQJMSRA_MC2001: createConnection API used w/ username, password for Container Auth MQJMSRA_MC2001: createConnection API used w/ username, password for Container Auth >> 2) enable ent app with asadmin: asadmin>enable EnterpriseApplication2 Command enable executed successfully asadmin> In GlassFish V2 server.log: we get the same error as with IDE-Services/App Enable ADM1041:Sent the event to instance:[ApplicationDeployEvent -- enable EnterpriseApplication2] "DPL8007: Invalid Deployment Descriptors element message-destination value null" endpoint.determine.destinationtype LDR5010: All ejb(s) of [EnterpriseApplication2] loaded successfully! NAM0007 : Message Destination Reference java:comp/env/myQueue1 has not been linked to a Message Destination WEB0123: WebModule [/EnterpriseApplication2-war] failed to deploy and has been disabled javax.naming.NamingException: Message Destination Reference java:comp/env/myQueue1 has not been resolved at com.sun.enterprise.naming.NamingManagerImpl.bindObjects(NamingManagerImpl.java:521) at com.sun.enterprise.web.WebModuleContextConfig.configureResource(WebModuleContextConfig.java:220) ... etc. Second Try: --------------- ** Undeploy the app (to start properly the test, undeploy the resources) ** close the browser ** stop the server (as cannot do deploy again: due to issue 110131) ** start the server ** "Undeploy & Deploy" action ** "Run" ==>> http://localhost:8080/EnterpriseApplication2-war add the Servlet URI http://localhost:8080/EnterpriseApplication2-war/NewServlet (refresh 2-3times to see the messages sent and received in the server.log) ** close the browser window ** Disable the app with asadmin OK ** Enable the app with asadmin: same problem as in upper cases. In the server.log can see: LDR5010: All ejb(s) of [EnterpriseApplication2] loaded successfully! NAM0007 : Message Destination Reference java:comp/env/myQueue1 has not been linked to a Message Destination WEB0123: WebModule [/EnterpriseApplication2-war] failed to deploy and has been disabled But in the Services/Servers/GlassFish V2/Applications/Enterprise Applications/EnterpriseApplication2 can see when expanding this node, the two entries: /EnterpriseApplication2-war (default/jsp/NewServlet) and EnterpriseApplication2-ejb.jar (NewSessionBean and NewMessageBean) in IDE-log: INFO java.lang.NullPointerException at org.netbeans.modules.j2ee.sun.ide.controllers.EJBModuleController.isEnabled(EJBModuleController.java:268) at org.netbeans.modules.j2ee.sun.ide.runtime.nodes.AppserverMgmtApplicationsNode.isEnabled(AppserverMgmtApplicationsNode.java:138) [catch] at org.netbeans.modules.j2ee.sun.ide.runtime.actions.EnableDisableAction.enable(EnableDisableAction.java:97) at org.openide.util.actions.NodeAction$DelegateAction.resultChanged(NodeAction.java:589) at sun.reflect.GeneratedMethodAccessor45.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.openide.util.WeakListenerImpl$ProxyListener.invoke(WeakListenerImpl.java:427) at $Proxy6.resultChanged(Unknown Source) at org.openide.util.lookup.ProxyLookup.setLookups(ProxyLookup.java:170) at org.openide.explorer.DefaultEMLookup.updateLookups(DefaultEMLookup.java:109) at org.openide.explorer.DefaultEMLookup.propertyChange(DefaultEMLookup.java:141) at org.openide.util.WeakListenerImpl$PropertyChange.propertyChange(WeakListenerImpl.java:164) at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:339) at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:276) at org.openide.explorer.ExplorerManager$2.run(ExplorerManager.java:814) at org.openide.util.Mutex.doEvent(Mutex.java:1181) at org.openide.util.Mutex.readAccess(Mutex.java:287) at org.openide.explorer.ExplorerManager.fireInAWT(ExplorerManager.java:811) at org.openide.explorer.ExplorerManager.access$600(ExplorerManager.java:67) at org.openide.explorer.ExplorerManager$1AtomicSetSelectedNodes.fire(ExplorerManager.java:259) at org.openide.explorer.ExplorerManager.setSelectedNodes(ExplorerManager.java:272) at org.openide.explorer.ExplorerManager$1SetExploredContextAndSelection.run(ExplorerManager.java:364) at org.openide.util.Mutex.readAccess(Mutex.java:296) at org.openide.explorer.ExplorerManager.setExploredContextAndSelection(ExplorerManager.java:383) at org.openide.explorer.view.BeanTreeView.selectionChanged(BeanTreeView.java:133) at org.openide.explorer.view.TreeView.callSelectionChanged(TreeView.java:713) at org.openide.explorer.view.TreeView$TreePropertyListener.run(TreeView.java:1269) at org.openide.util.Mutex.postRequest(Mutex.java:1140) at org.openide.util.Mutex.postReadRequest(Mutex.java:473) at org.openide.explorer.view.TreeView$TreePropertyListener.valueChanged(TreeView.java:1240) at javax.swing.tree.DefaultTreeSelectionModel.fireValueChanged(DefaultTreeSelectionModel.java:629) at javax.swing.tree.DefaultTreeSelectionModel.notifyPathChange(DefaultTreeSelectionModel.java:1078) at javax.swing.tree.DefaultTreeSelectionModel.setSelectionPaths(DefaultTreeSelectionModel.java:287) at javax.swing.tree.DefaultTreeSelectionModel.setSelectionPath(DefaultTreeSelectionModel.java:170) at javax.swing.JTree.setSelectionPath(JTree.java:1600) at javax.swing.plaf.basic.BasicTreeUI.selectPathForEvent(BasicTreeUI.java:2306) at javax.swing.plaf.basic.BasicTreeUI$Handler.handleSelection(BasicTreeUI.java:3507) at javax.swing.plaf.basic.BasicTreeUI$Handler.mousePressedDND(BasicTreeUI.java:3484) at javax.swing.plaf.basic.BasicTreeUI$Handler.mousePressed(BasicTreeUI.java:3443) at java.awt.AWTEventMulticaster.mousePressed(AWTEventMulticaster.java:262) at java.awt.AWTEventMulticaster.mousePressed(AWTEventMulticaster.java:262) at java.awt.AWTEventMulticaster.mousePressed(AWTEventMulticaster.java:262) at java.awt.AWTEventMulticaster.mousePressed(AWTEventMulticaster.java:262) at java.awt.AWTEventMulticaster.mousePressed(AWTEventMulticaster.java:262) at java.awt.Component.processMouseEvent(Component.java:6035) at javax.swing.JComponent.processMouseEvent(JComponent.java:3260) at java.awt.Component.processEvent(Component.java:5803) at java.awt.Container.processEvent(Container.java:2058) at java.awt.Component.dispatchEventImpl(Component.java:4410) at java.awt.Container.dispatchEventImpl(Container.java:2116) at java.awt.Component.dispatchEvent(Component.java:4240) at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4322) at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3983) at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3916) at java.awt.Container.dispatchEventImpl(Container.java:2102) at java.awt.Window.dispatchEventImpl(Window.java:2429) at java.awt.Component.dispatchEvent(Component.java:4240) at java.awt.EventQueue.dispatchEvent(EventQueue.java:599) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160) at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)
try again the test with : server "Directory Deployment Enable" set to disable ** clean and build ** deploy ent app after deployment of the ent app, in Services/Servers/GlassFish V2/Applications/EnterpriseApplication2 can find two nodes : /EnterpriseApplication2-war (default/jsp/NewServlet) and EnterpriseApplication2-ejb.jar ** Run ok. ** close the browser window ** disable with IDE: in the upper node EnterpriseApplication2 after expand : EnterpriseApplication2-ejb.jar with NewSessionBean/NewMessageBean ** enable: same issue in the upper node EnterpriseApplication2 after expand : EnterpriseApplication2-war (default/jsp/NewServlet) and EnterpriseApplication2-ejb.jar (NewSessionBean/NewMessageBean) ** undeploy ** clean : OK ** clean and build : OK ** undeploy & deploy: OK in the upper node EnterpriseApplication2 after expand : EnterpriseApplication2-war (default/jsp/NewServlet) and EnterpriseApplication2-ejb.jar ** Run: go to servlet URI ** Refresh after accessing the ejb via the servlet shows now the two subnodes in EnterpriseApplication2-ejb.jar (NewSessionBean and MessageBean) ** Disable: remove the EnterpriseApplication2-war ** enable same issue. Not related to the type of deployment.
The server is unable to resolve a JMS resource's connector connection pool if the pool's name is not the same as the connector resource's name. ie. JMS resource Name : myQueue1Factory Connector Connection Pool Name : myQueue1FactoryPool -- does not work Connector Connection Pool Name : myQueue1Factory -- works Filed a glassfish issue, https://glassfish.dev.java.net/issues/show_bug.cgi?id=3391 If necessary, plugin can workaround this issue for the zero-config case by defaulting the pool name to the connector resource. Prefer not to do that if the server fixes the issue. name.
Working around theproblem with the connecor pool name does not fix the issue. I still see an error regarding the Destination Resource myQueue1 on enable. NAM0007 : Message Destination Reference java:comp/env/myQueue1 has not been linked to a Message Destination
Created second glassfish issue for error whileloading webapp on enable. https://glassfish.dev.java.net/issues/show_bug.cgi?id=3392
GlassFish Issue https://glassfish.dev.java.net/issues/show_bug.cgi?id=3391 has been fixed and that resolves this issue. Fix is in GlassFish build b57
07251200 & GF v2 b57 & jdk 1.6 u1 : on windows xp opened again my project: EnterpriseApplication at the first deploy get: << Initial deploying EnterpriseApplication2 to C:\Documents and Settings\Administrator\My Documents\NetBeansProjects\EnterpriseApplication2\dist\gfdeploy Completed initial distribution of EnterpriseApplication2 Start registering the project's server resources Finished registering server resources moduleID=EnterpriseApplication2 deployment started : 0% Deploying application in domain failed; The resource myQueue1 is having a conflict with resource defined in domain.xml. The resource myQueue1FactoryPool is having a conflict with resource defined in domain.xml. The resource myQueue1Factory is having a conflict with resource defined in domain.xml. C:\Documents and Settings\Administrator\My Documents\NetBeansProjects\EnterpriseApplication2\nbproject\build-impl.xml:183: Deployment error: The module has not been deployed. See the server log for details. BUILD FAILED (total time: 5 seconds) >> my GF v2 b57 is freshly installed and verified before the deployment that no resource was present in Services/ Resources/ JMS resources neither in Connectors. after this error in deployment, the resources are created in my server seem to be trying to create more than once. will try with a new project
Created attachment 45777 [details] server.log from windows processed with dos2unix
removed the file sun-resources.xml from my ejb-project and created the jms resources by Admin Console, and was able to deploy as expected.
Nuoar, the error you were seeing with sun-resources.xml in the project was due to issue 111033
with the resources added with Admin console and continue, can do disable and enable with b57 and run is ok. So, marking as verified will double check with a new project as said before.
if we create a new ear project like the one I had and added a second MSDB with a similar config (queue) of my first project, the newly sun-resource.xml created prevents me to deploy the ejb-project and get the same error for resource conflict in the domain, wait for this evening to download the fix from Vince if integrated in 07261200.