[JBoss JIRA] (JBIDE-14709) Error in server log when redeploying datasource
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14709?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-14709:
-----------------------------------
Fix Version/s: 4.1.x
> Error in server log when redeploying datasource
> ------------------------------------------------
>
> Key: JBIDE-14709
> URL: https://issues.jboss.org/browse/JBIDE-14709
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Seam 2
> Affects Versions: 4.1.0.Beta1
> Environment: JBDS 7.0.0.Beta1, EAP 6.1.0.GA
> Reporter: Tomas Remes
> Assignee: Alexey Kazakov
> Fix For: 4.1.x
>
>
> I am not sure, if this problem is related to JBT, but is best reproducible by this way. Steps to reproduce:
> 1. Create and run EAP 6.1.0 server
> 2. Create Seam Web Project (I used MySQL datasource)
> 3. Try to edit newly created datasource file in the project and save it.
> 4. Redeploy is triggered.
> 5. However the datasource is redeployed, notice the following exception in the server.log:
> {noformat}
> 11:07:34,057 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.naming.context.java.testProjectEntityManagerFactory: org.jboss.msc.service.StartException in service jboss.naming.context.java.testProjectEntityManagerFactory: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17]
> Caused by: org.jboss.msc.inject.InjectionException: Value already set for this injector
> at org.jboss.msc.inject.RetainingInjector.inject(RetainingInjector.java:50) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler$1.inject(PersistenceUnitServiceHandler.java:386)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler$1.inject(PersistenceUnitServiceHandler.java:382)
> at org.jboss.msc.inject.CastingInjector.inject(CastingInjector.java:55) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl.doInject(ServiceControllerImpl.java:1549) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl.access$1900(ServiceControllerImpl.java:49) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.performInjections(ServiceControllerImpl.java:1780) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1741) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> ... 3 more
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (JBIDE-14709) Error in server log when redeploying datasource
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14709?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-14709:
--------------------------------------
Assignee: Alexey Kazakov
> Error in server log when redeploying datasource
> ------------------------------------------------
>
> Key: JBIDE-14709
> URL: https://issues.jboss.org/browse/JBIDE-14709
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Seam 2
> Affects Versions: 4.1.0.Beta1
> Environment: JBDS 7.0.0.Beta1, EAP 6.1.0.GA
> Reporter: Tomas Remes
> Assignee: Alexey Kazakov
>
> I am not sure, if this problem is related to JBT, but is best reproducible by this way. Steps to reproduce:
> 1. Create and run EAP 6.1.0 server
> 2. Create Seam Web Project (I used MySQL datasource)
> 3. Try to edit newly created datasource file in the project and save it.
> 4. Redeploy is triggered.
> 5. However the datasource is redeployed, notice the following exception in the server.log:
> {noformat}
> 11:07:34,057 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.naming.context.java.testProjectEntityManagerFactory: org.jboss.msc.service.StartException in service jboss.naming.context.java.testProjectEntityManagerFactory: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17]
> Caused by: org.jboss.msc.inject.InjectionException: Value already set for this injector
> at org.jboss.msc.inject.RetainingInjector.inject(RetainingInjector.java:50) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler$1.inject(PersistenceUnitServiceHandler.java:386)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler$1.inject(PersistenceUnitServiceHandler.java:382)
> at org.jboss.msc.inject.CastingInjector.inject(CastingInjector.java:55) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl.doInject(ServiceControllerImpl.java:1549) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl.access$1900(ServiceControllerImpl.java:49) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.performInjections(ServiceControllerImpl.java:1780) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1741) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> ... 3 more
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (JBIDE-14708) Opening xml files with multiple editor tabs
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14708?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-14708:
-----------------------------------------
Tomas, could write some details on your configuration like OS, architecture, java vendor and version as well as attach log-file from <your workspace>/.metadata/.log if possible.
> Opening xml files with multiple editor tabs
> -------------------------------------------
>
> Key: JBIDE-14708
> URL: https://issues.jboss.org/browse/JBIDE-14708
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: XML Structured Editor
> Affects Versions: 4.1.0.Beta1
> Environment: JBDS 7.0.0.Beta1
> Reporter: Tomas Remes
> Assignee: Victor Rubezhny
> Priority: Critical
> Fix For: 4.1.0.Beta2
>
>
> Create for example new Seam Web Project. At first open web.xml file, then open e.g. faces-config.xml file. In this point I would assume this file active in the view (not the first one) as it was in previous JBDS release. It does not seem to be perspective dependant and I open it from package explorer. Both files opened by JBoss Tools XML Editor.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (JBIDE-14708) Opening xml files with multiple editor tabs
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14708?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-14708:
--------------------------------------
Assignee: Victor Rubezhny
I can reproduce it with JBoss Tools XML Editor only. Works fine with WTP XML Editor. Weird.
> Opening xml files with multiple editor tabs
> -------------------------------------------
>
> Key: JBIDE-14708
> URL: https://issues.jboss.org/browse/JBIDE-14708
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: XML Structured Editor
> Affects Versions: 4.1.0.Beta1
> Environment: JBDS 7.0.0.Beta1
> Reporter: Tomas Remes
> Assignee: Victor Rubezhny
> Priority: Critical
> Fix For: 4.1.0.Beta2
>
>
> Create for example new Seam Web Project. At first open web.xml file, then open e.g. faces-config.xml file. In this point I would assume this file active in the view (not the first one) as it was in previous JBDS release. It does not seem to be perspective dependant and I open it from package explorer. Both files opened by JBoss Tools XML Editor.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (JBIDE-14708) Opening xml files with multiple editor tabs
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14708?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-14708:
-----------------------------------
Component/s: XML Structured Editor
> Opening xml files with multiple editor tabs
> -------------------------------------------
>
> Key: JBIDE-14708
> URL: https://issues.jboss.org/browse/JBIDE-14708
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: XML Structured Editor
> Affects Versions: 4.1.0.Beta1
> Environment: JBDS 7.0.0.Beta1
> Reporter: Tomas Remes
> Priority: Critical
> Fix For: 4.1.0.Beta2
>
>
> Create for example new Seam Web Project. At first open web.xml file, then open e.g. faces-config.xml file. In this point I would assume this file active in the view (not the first one) as it was in previous JBDS release. It does not seem to be perspective dependant and I open it from package explorer. Both files opened by JBoss Tools XML Editor.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (JBIDE-14708) Opening xml files with multiple editor tabs
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14708?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-14708:
-----------------------------------
Priority: Critical (was: Minor)
> Opening xml files with multiple editor tabs
> -------------------------------------------
>
> Key: JBIDE-14708
> URL: https://issues.jboss.org/browse/JBIDE-14708
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Affects Versions: 4.1.0.Beta1
> Environment: JBDS 7.0.0.Beta1
> Reporter: Tomas Remes
> Priority: Critical
>
> Create for example new Seam Web Project. At first open web.xml file, then open e.g. faces-config.xml file. In this point I would assume this file active in the view (not the first one) as it was in previous JBDS release. It does not seem to be perspective dependant and I open it from package explorer. Both files opened by JBoss Tools XML Editor.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (JBIDE-14708) Opening xml files with multiple editor tabs
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14708?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-14708:
-----------------------------------
Fix Version/s: 4.1.0.Beta2
> Opening xml files with multiple editor tabs
> -------------------------------------------
>
> Key: JBIDE-14708
> URL: https://issues.jboss.org/browse/JBIDE-14708
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Affects Versions: 4.1.0.Beta1
> Environment: JBDS 7.0.0.Beta1
> Reporter: Tomas Remes
> Priority: Critical
> Fix For: 4.1.0.Beta2
>
>
> Create for example new Seam Web Project. At first open web.xml file, then open e.g. faces-config.xml file. In this point I would assume this file active in the view (not the first one) as it was in previous JBDS release. It does not seem to be perspective dependant and I open it from package explorer. Both files opened by JBoss Tools XML Editor.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (JBIDE-14126) Weinre Inspector is showing no data within Elements tab
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14126?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-14126:
-------------------------------------------
Component/s: upstream
> Weinre Inspector is showing no data within Elements tab
> -------------------------------------------------------
>
> Key: JBIDE-14126
> URL: https://issues.jboss.org/browse/JBIDE-14126
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim, upstream
> Affects Versions: 4.1.0.Alpha2
> Environment: Fedora 17 64bit, KDE, jbdevstudio-product-eap-universal-7.0.0.Alpha2-v20130421-0725-B198, Java Sun JDK 1.6.0_32
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
> Fix For: 4.1.0.Beta2
>
> Attachments: localamazon.png, localbrowsersimhtml5.png, localhtml5.png, phonegapamazon.png
>
>
> 1. Open www.amazon.com page in Browsersim
> 2. Run Weinre Inspector via Browsersim context menu "Weinre"
> ERROR: No elements shown on Elements tab
> Client is connected:
> !phonegapamazon.png!
> 3. Run Weinre server locally.
> 4. Set Browsersim to use local Weinre server
> 5. Run Weinre Inspector as in step 2.
> ERROR: No elements shown on Elements tab
> Client is connected:
> !localamazon.png!
> 6. Create HTML5 project from JBoss Central
> 7. Insert script tag allowing debugging via local Weinre server to index.html
> 8. Run HTML5 project on Server
> 9. Open HTML5 index.html in system borwser
> ASSERT: Weinre debugging works
> !localhtml5.png!
> ERROR: Weinre debugging is not working from JBDS internal browser
> 10. Open index.html of HTML5 project in Browsersim
> 11. Open Weinre debug link in Browser
> ERROR: No elements shown on Elements tab
> Client is connected:
> !localbrowsersimhtml5.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months