April 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBAS-8297) Weld throws error No active contexts for scope type javax.enterprise.context.RequestScoped

by Ben D'Herville (JIRA)

[ https://issues.jboss.org/browse/JBAS-8297?page=com.atlassian.jira.plugin.... ] Ben D'Herville commented on JBAS-8297: -------------------------------------- Details of this very similar issue in Apache may be helpful. https://issues.apache.org/bugzilla/show_bug.cgi?id=50789 > Weld throws error No active contexts for scope type javax.enterprise.context.RequestScoped > ------------------------------------------------------------------------------------------ > > Key: JBAS-8297 > URL: https://issues.jboss.org/browse/JBAS-8297 > Project: Legacy JBoss Application Server 6 > Issue Type: Bug > Components: Weld/CDI > Environment: JBoss 6.0.0.M2, Windows XP SP3 > Reporter: Marcos Antonio > Assignee: Ales Justin > Fix For: 6.1.0 > > Attachments: solicitacoes.zip > > > 2010-04-22 09:55:36,484 WARN [org.apache.catalina.authenticator.FormAuthenticator] (http-127.0.0.1-8080-1) Unexpected error forwarding to login page: javax.servlet.ServletException: WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScoped -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-9339) Provide jta-data-source if not specified

by Shelly McGowan (JIRA)

Provide jta-data-source if not specified ---------------------------------------- Key: JBAS-9339 URL: https://issues.jboss.org/browse/JBAS-9339 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JPA / Hibernate Reporter: Shelly McGowan Assignee: Scott Marlow Fix For: 7.0.0.CR1 Persistence 2.0 Spec, Chapter 8.2.1.5 In Java EE environments, the jta-data-source and non-jta-data-source elements are used to specify the global JNDI name of the JTA and/or non-JTA data source to be used by the persistence provider. and need to provide one if it is not specified: If neither is specified, the deployer must specify a JTA data source at deployment or a JTA data source must be provided by the container, and a JTA EntityManagerFactory will be created to correspond to it. Without the jta-data-source element in the persistence.xml, the deployment fails to start: 08:53:57,004 WARN [org.hibernate.connection.UserSuppliedConnectionProvider] (MSC service thread 1-6) No connection properties specified - the user must supply JDBC connections 08:53:57,011 INFO [org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider] (MSC service thread 1-5) Using provided datasource 08:53:57,017 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: Failed to start service jboss.persistenceunit."my_web.war#MY-EM": org.jboss.msc.service.StartException in service jboss.persistenceunit."my_web.war#MY-EM": Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1363) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_21] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_21] at java.lang.Thread.run(Thread.java:619) [:1.6.0_21] Caused by: javax.persistence.PersistenceException: [PersistenceUnit: MY-EM] Unable to build EntityManagerFactory at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:911) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:74) at org.jboss.as.jpa.service.PersistenceUnitService.createContainerEntityManagerFactory(PersistenceUnitService.java:169) at org.jboss.as.jpa.service.PersistenceUnitService.start(PersistenceUnitService.java:78) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

3
10
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1842) Live node dropping out of cluster can cause duplicate message delivery

by Justin Bertram (JIRA)

Live node dropping out of cluster can cause duplicate message delivery ---------------------------------------------------------------------- Key: JBMESSAGING-1842 URL: https://issues.jboss.org/browse/JBMESSAGING-1842 Project: JBoss Messaging Issue Type: Bug Components: JMS Clustering Affects Versions: 1.4.0.SP3.CP10 Reporter: Justin Bertram Assignee: Yong Hao Gao When a live node is kicked out of the cluster (for whatever reason) its JBoss Messaging ServerPeer remains active which means the node is still available to receive messages and, if necessary, persist them to the database. However, the CHANNEL_ID values used for the persisted messages will be invalid since the fail-over procedure would have removed the "dead" node's channels from the JBM_POSTOFFICE and new CHANNEL_ID values will be used when the "dead" node is finally restarted. This essentially orphans any persistent messages sent to the "dead" node after it has been kicked out of the cluster. Recovering the orphaned messages would require manual intervention with the database, but even then it might not be possible to match the old CHANNEL_ID values with the new ones. The simplest way to solve this problem is to add a constraint to the database that forces the inserted message's CHANNEL_ID to correspond to a CHANNEL_ID from JBM_POSTOFFICE. Of course, such a constraint will hurt performance a bit, but it could be optional - customers could trade robustness for speed. The node would still need to be restarted in order to rejoin the cluster appropriately, but the constraint would avoid orphaned messages. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
13
0 / 0

[JBoss JIRA] Created: (AS7-676) JVM properties ignored when added to server group

by Heiko Braun (JIRA)

JVM properties ignored when added to server group ------------------------------------------------- Key: AS7-676 URL: https://issues.jboss.org/browse/AS7-676 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.Beta4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-9353) port connector subsystems to IronJacamar beta6

by Stefano Maestri (JIRA)

port connector subsystems to IronJacamar beta6 ---------------------------------------------- Key: JBAS-9353 URL: https://issues.jboss.org/browse/JBAS-9353 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JCA service Reporter: Stefano Maestri Assignee: Stefano Maestri Fix For: 7.0.0.Beta4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Assigned: (AS7-672) HostController status

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-672?page=com.atlassian.jira.plugin.sy... ] Brian Stansberry reassigned AS7-672: ------------------------------------ Assignee: Brian Stansberry > HostController status > --------------------- > > Key: AS7-672 > URL: https://issues.jboss.org/browse/AS7-672 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 7.0.0.CR1 > > > Analogous to a server's status, but for a HostController. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-9330) Console Funtionality: add/remove/deploy/undeploy/redeploy to server groups in a domain

by Stan Silvert (JIRA)

Console Funtionality: add/remove/deploy/undeploy/redeploy to server groups in a domain -------------------------------------------------------------------------------------- Key: JBAS-9330 URL: https://issues.jboss.org/browse/JBAS-9330 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web Console Affects Versions: 7.0.0.Beta3 Reporter: Stan Silvert Assignee: Stan Silvert Fix For: 7.0.0.Beta4 Update "Current Deployments" screen to view content store along with deployments to each server group. Provide add/remove/deploy/undeploy/redeploy funcitons. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-693) Server group deployment's "enabled" attribute not marshalled

by Brian Stansberry (JIRA)

Server group deployment's "enabled" attribute not marshalled ------------------------------------------------------------ Key: AS7-693 URL: https://issues.jboss.org/browse/AS7-693 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.0.0.Beta3 Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.0.0.Beta4 If "enabled" is set to false it's not getting marshalled. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-695) Filter server instances by group

by Heiko Braun (JIRA)

Filter server instances by group -------------------------------- Key: AS7-695 URL: https://issues.jboss.org/browse/AS7-695 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.Beta4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-675) /server-group=<group>/jvm=<jvm>:add() ignores properties

by Heiko Braun (JIRA)

/server-group=<group>/jvm=<jvm>:add() ignores properties -------------------------------------------------------- Key: AS7-675 URL: https://issues.jboss.org/browse/AS7-675 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Braun Assignee: Jason Greene Fix For: 7.0.0.Beta4 [INFO] { [INFO] "operation" => "add", [INFO] "address" => [ [INFO] ("server-group" => "my-group"), [INFO] ("jvm" => "default") [INFO] ], [INFO] "jvm" => ("default" => { [INFO] "heap-size" => "64m", [INFO] "max-heap-size" => "128m" [INFO] }) [INFO] } leads to [localhost:9999 /] /server-group=my-group:read-resource(recursive=true) { "outcome" => "success", "result" => { "profile" => "default", "jvm" => {"default" => { "type" => undefined, "agent-lib" => undefined, "agent-path" => undefined, "debug-enabled" => undefined, "debug-options" => undefined, "env-classpath-ignored" => undefined, "environment-variables" => undefined, "heap-size" => undefined, "max-heap-size" => undefined, "java-agent" => undefined, "java-home" => undefined, "jvm-options" => undefined, "permgen-size" => undefined, "max-permgen-size" => undefined, "stack-size" => undefined }}, "deployment" => undefined, "socket-binding-group" => "standard-sockets" }, "compensating-operation" => undefined } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2011