[ https://issues.jboss.org/browse/JBIDE-11509?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-11509: ---------------------------------------- Fix Version/s: 3.3.0.Beta3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11509?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-11509: ------------------------------------- I have found that simply having previous deployments on the server, stopping it, restarting the IDE, then using Run As Run on Server on the stopped server (with a deployments folder full of previously deployed apps) will also demonstrate the problem. I can see how this would throw off a newbie who thought his previously deployed apps that were once successful, now fail. I made a video of the flow that I use - this hits me regularly http://screencast.com/t/YyQ31jCOnYy -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11509?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-11509: ------------------------------------- This problem is a HUGE one for new users who lack experience. Perhaps we should undeploy all the previously deployed apps automatically - because Run As on Server with a stopped server, with previously deployed apps, seems to always fail. And then we chase the AS team to get this corrected! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11509?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-11509: ------------------------------------- Did you watch the video? There is nothing wrong with the .wars, they just fail upon server restart. The solution is to simply Full Publish them or just Remove/Add them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11509?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-11509: --------------------------------------------- if they fail on server restart the server believes something is wrong. What is in the log ? What is in the .failed files ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11509?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-11509: ------------------------------------- AS log/console errors: 06:53:01,332 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-2) HHH000231: Schema export unsuccessful: org.hibernate.tool.hbm2ddl.ImportScriptException: Error during statement execution (file: '/import.sql'): insert into Member (id, name, email, phone_number) values (0, 'John Smith', 'john.smith(a)mailinator.com', '2125551212') at org.hibernate.tool.hbm2ddl.SchemaExport.importScript(SchemaExport.java:452) [hibernate-core-4.0.1.Final.jar:4.0.1.Final] Caused by: org.h2.jdbc.JdbcSQLException: Unique index or primary key violation: "PRIMARY_KEY_8 ON PUBLIC.MEMBER(ID)"; SQL statement: insert into Member (id, name, email, phone_number) values (0, 'John Smith', 'john.smith(a)mailinator.com', '2125551212') [23505-161] and JBAS014777: Services which failed to start: service jboss.deployment.unit."truxie.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."truxie.war".WeldService: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions: Exception 0 : java.lang.NullPointerException at org.jboss.weld.manager.BeanManagerImpl.getMostSpecializedBean(BeanManagerImpl.java:931) at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:605) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:228) at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:207) at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:75) at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:46) at org.jboss.weld.bootstrap.events.BeforeBeanDiscoveryImpl.fire(BeforeBeanDiscoveryImpl.java:46) at org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:322) at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:81) at org.jboss.as.weld.services.WeldService.start(WeldService.java:76) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:680) service jboss.deployment.unit."poh5.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."poh5.war".WeldService: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions: Exception 0 : -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11509?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-11509: ------------------------------------- http://screencast.com/t/vGzPjEAWfWvI Looks like Weld to me -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11509?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-11509: ------------------------------------- The .war was generated from the JBoss Central archetypes - no custom coding. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11509?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-11509: --------------------------------------------- Rob, which part ? the problem or suggestion for solutions ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11509?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-11509: ------------------------------------- try this: 1) Using JBoss Central, Create Projects, Java EE Web Project (jboss-javaee6-webapp) 2) Deploy the generated project 3) Grab a copy of h2console.war from the AS7 quickstarts and deploy that 4) Using JBoss Central, Create Projects, HTML5 Project (poh5) 5) Deploy the generated project 6) Stop the server 7) Shutdown Eclipse 8) Start Eclipse (or perhaps Restart might be the issue) 9) Using JBoss Central, Create Projects, RichFaces Project 10) Deploy the generated project using Run As Run on Server It does seem to be more of a problem when there is more than one project deployed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11509?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-11509: --------------------------------------- The issue happens because the BeansClosure.getClosure(BeanManagerImpl beanManager) method in the weld-core module isn't thread-safe. It is easier to reproduce the issue when debugging JBoss AS 7. I have created a patch for JBoss AS 7.1.1. Burr, Could you replace <JBOSS_HOME>/modules/org/jboss/weld/core/main/weld-core-1.1.5.AS71.Final.jar in the JBoss AS 7.1.1 server with the attached jar and try to reproduce the issue. Attached are the weld-core jar for JBoss AS 7.1.1 and the patch against weld 1.1.5.Final that is used in JBoss AS 7.1.1. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11509?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-11509: ------------------------------------- Considering this is a bug in the app server, I'm not sure what can be done here on the tooling side. I can try to add logic to verify module state after a server starts up, but we have to remember that different app servers have different levels of support for verifying deployment status. For example, the jmx beans in jboss 6 that verify module state seem to be missing (JBIDE-11514). Also, if the deployments are on a remote server, verification will depend entirely on whether their management services are exposed. Otherwise there'll be pretty much nothing I can do to verify the state of modules. Finally, verifying the actual state of all modules may end up slowing down the startup process. This may be a minor concern, really, but it's a possibility worth noting. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11509?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-11509: ------------------------------------- Snjezana, I think that fixed me up! Thank you. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11509?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-11509: --------------------------------------- {quote} Snjezana - great if you got a fix; we should make sure that get into AS. But that issue is not the problem this issue is about - this issue is simply about how users can recover from 1 out of many apps have failed deployment. {quote} I have reproduced the issue Burr described in https://issues.jboss.org/browse/JBIDE-11509?focusedCommentId=12685407&... All the applications: jboss-javaee6-webapp, h2console.war, poh5 and richfaces are valid and are deployed correctly using the steps 1-5. When restarting the server, one or more deployments fail and AS undeploys all applications according to AS7-783. The issue isn't always reproducible, but happens randomly. It can be easily reproduced by setting a breakpoint to BeansClosure.getClosure() and start JBoss AS in the debug mode. The problem is in the weld-core <= 1.1.5.Final project, not in JBoss AS. It happens when all deployments are valid. It is fixed in Weld 1.1.6.Final(WELD-1067). JBoss AS 7.1.2 will include the fix (it contains weld 1.1.7.Final). The issue described in AS7-783 happens if there is an invalid deployment. I suppose the AS team has rejected AS7-783 for performance reason. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11509?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-11509: --------------------------------------------- WELD-1067 is the real cause of the problems here and not part of AS 7.1.x but will be in EAP 6.0 Moved that concern to be covered in JBIDE-10116 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11509?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-11509. --------------------------------- Verified in jbdevstudio-product-universal-5.0.0.v20120605-2229-H183-CR1.jar -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira