December 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMCRON-37) IllegalArgumentException: timeout value is negative

by Christian Kaltepoth (JIRA)

IllegalArgumentException: timeout value is negative --------------------------------------------------- Key: SEAMCRON-37 URL: https://issues.jboss.org/browse/SEAMCRON-37 Project: Seam Cron Issue Type: Task Affects Versions: 3.0.0.Alpha1 Environment: Tomcat 7.0.16, JDK6, Weld 1.1.0 Reporter: Christian Kaltepoth Assignee: Peter Royle I'm using Seam Cron to implement some background processing stuff in my application. Unfortunately after a few days the Quartz scheduler dies with this exception: {code} 2011-08-05 22:54:56,157 ERROR [QuartzSchedulerThread] Runtime error occured in main trigger firing loop. java.lang.IllegalArgumentException: timeout value is negative at java.lang.Object.wait(Native Method) at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:296) {code} I did some research and found out that this is a known bug of Quartz 1.6.1. For details see the upstream issue: http://jira.opensymphony.com/browse/QUARTZ-707 This bug has been fixed in Quartz 1.6.2. So I think it would make sense to update the Quartz dependency of Seam Cron to the most recent Quartz version which is 1.6.5. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (JBSEAM-4528) static pages don't work at all with database down and XA datasource used

by deanhiller (JIRA)

static pages don't work at all with database down and XA datasource used ------------------------------------------------------------------------ Key: JBSEAM-4528 URL: https://jira.jboss.org/jira/browse/JBSEAM-4528 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.2.0.GA Environment: postgres or oracle with postgres or oracle XADatasource. postgres jdbc driver is fine while oracle driver is not Reporter: deanhiller Priority: Critical If this is a hibernate bug, please report hibernate issue and ticket here as other seam users will run into this problem and it looks like a seam framework problem(or at least could be solved in seam but it may be possible to solve in hibernate too and could be solved in each and every driver datasource as well). Steps to reproduce 1. start up the jboss 5.1.0 with latest seam 2. pull your internet connection so the db is gone 3. have all your customers go to a static page like /web/error.xhtml RESULT: jboss goes to it's knees as users in IE end up in infinite redirects to your server causing more and more load on the server. The drivers talk to the database when they should not be. I have a work around proxy driver for oracle's jdbc driver. I do not however have a fix for oracle's datasource or postgres datasource. I imagine someone could write a proxy datasource that would solve this problem for all people, hibernate, seam and all xa drivers. I will attach logs of postgres xa driver and oracle one but basically they are trying to open a connection to database when ANY http request comes in until waiting to see if we actually do any select statements or updates or inserts. For some reason, the postgres driver and oracle driver where fine here...they did not make db requests when an http request came in. The oracle driver however did make a request to the db when commit is called even if no sql was done against the db where postgres driver ignored the commit since no sql was done. I will try to attach files or more comments here. PLEASE if you report a tic in hibernate put it in here for others to find when they hit this issue. keyphrases: seam doesn't work when database goes down seam infinite redirect on db outage database failure causes seam to not work -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
11
0 / 0

[JBoss JIRA] (SEAMSECURITY-134) AttributeManager does not contain some implementations

by Benan Aktaş (Created) (JIRA)

AttributeManager does not contain some implementations ------------------------------------------------------- Key: SEAMSECURITY-134 URL: https://issues.jboss.org/browse/SEAMSECURITY-134 Project: Seam Security Issue Type: Feature Request Affects Versions: 3.1.0.CR1 Reporter: Benan Aktaş Priority: Minor Fix For: 3.1.0.Final AttributeManager does not contain some implementations like -findUserByUniqueAttribute - findIdentityObjectByUniqueAttribute - getAttributesMetaData - getSupportedAttributeNames - getIdentityObjectsCount and several others. So we can not use IdentityAttribute entity as much as we want. -- 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

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SEAMSECURITY-133) Apply one role or another

by kelly goedert (Created) (JIRA)

Apply one role or another ------------------------- Key: SEAMSECURITY-133 URL: https://issues.jboss.org/browse/SEAMSECURITY-133 Project: Seam Security Issue Type: Feature Request Reporter: kelly goedert It would be nice to be able to apply roles using conditions like, role A or role B, or yet role A and role B to give user access to a feature. I posted an example on the forum. http://www.seamframework.org/Community/SeamSecurityApplyingRoleRestrictions -- 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

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SEAMJMS-61) Status Watcher example does not work

by Tomas Remes (Created) (JIRA)

Status Watcher example does not work ------------------------------------ Key: SEAMJMS-61 URL: https://issues.jboss.org/browse/SEAMJMS-61 Project: Seam JMS Issue Type: Bug Affects Versions: 3.1.0.CR1 Environment: seam-3.1.0.CR1 Reporter: Tomas Remes Fix For: 3.1.0.Final Statuswatcher example gets deployed all right, but after typing its URL in the browser, following problem occurs: java.lang.NullPointerException org.jboss.seam.jms.TopicBuilderImpl.createMessageConsumer(TopicBuilderImpl.java:110) org.jboss.seam.jms.TopicBuilderImpl.listen(TopicBuilderImpl.java:187) org.jboss.seam.jms.example.statuswatcher.session.ReceivingClient.initialize(ReceivingClient.java:55) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305) org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) ...... It is same on both - AS-6.1.0 and AS-7.0.2 -- 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

14 years, 3 months

8
10
0 / 0

[JBoss JIRA] Created: (SEAMCRON-9) Should we expose exceptions during @Asynchronous via Future?

by Peter Royle (JIRA)

Should we expose exceptions during @Asynchronous via Future? ------------------------------------------------------------ Key: SEAMCRON-9 URL: https://issues.jboss.org/browse/SEAMCRON-9 Project: Seam Cron Issue Type: Enhancement Reporter: Peter Royle Assignee: Peter Royle Priority: Minor When an @Asynchronous method returns a Future, in EJB it allows you to access exceptions thrown by the @Asynchronous method via the returned Future object (EJB 3.1, 3.4.8). If possible we should mimic this behaviour. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (SEAMJMS-25) Add test cases for Glassfish 3.1

by John Ament (JIRA)

Add test cases for Glassfish 3.1 -------------------------------- Key: SEAMJMS-25 URL: https://issues.jboss.org/browse/SEAMJMS-25 Project: Seam JMS Issue Type: Enhancement Components: Injection Reporter: John Ament Assignee: John Ament Fix For: 3.0.0.Beta2 Need to add some test cases for glassfish v3.1, based on weld 1.1.1. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
7
0 / 0

[JBoss JIRA] Created: (SEAMJMS-49) Fix JMS Status Watcher example.

by John Ament (JIRA)

Fix JMS Status Watcher example. ------------------------------- Key: SEAMJMS-49 URL: https://issues.jboss.org/browse/SEAMJMS-49 Project: Seam JMS Issue Type: Task Components: Event Bridging Affects Versions: 3.0.0.CR1 Reporter: Marek Schmidt Assignee: John Ament Fix For: 3.0.0.CR2 4. There are some old unused files in the jms-statuswatcher example that can probably be safely deleted: examples/jms-statuswatcher/src/main/java/org/jboss/seam/jms/example/statuswatcher/qualifiers/StatusBridge.java examples/jms-statuswatcher/src/main/java/org/jboss/seam/jms/example/statuswatcher/qualifiers/StatusTopic.java examples/jms-statuswatcher/src/main/java/org/jboss/seam/jms/example/statuswatcher/session/RoutingConfig.java (unless wanted to be kept for illustrative purposes as an alternative approach to CdiJmsMapping) the following files have some unused imports: examples/jms-statuswatcher/src/main/java/org/jboss/seam/jms/example/statuswatcher/session/ReceivingClient.java examples/jms-statuswatcher/src/main/java/org/jboss/seam/jms/example/statuswatcher/session/ReceivingClientListener.java -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
5
0 / 0

[JBoss JIRA] (SEAMSOCIAL-27) Enhance loose coupling by having module injecting core service instead of inherit from them

by Antoine Sabot-Durand (Created) (JIRA)

Enhance loose coupling by having module injecting core service instead of inherit from them ------------------------------------------------------------------------------------------- Key: SEAMSOCIAL-27 URL: https://issues.jboss.org/browse/SEAMSOCIAL-27 Project: Seam Social Issue Type: Enhancement Components: Twitter, Facebook, LinkedIn Affects Versions: 3.1.0.Beta4 Reporter: Antoine Sabot-Durand Assignee: Antoine Sabot-Durand Fix For: 3.1.0.Beta5 Right now module use core seam social by inheriting OAuthService implementation. To have a better loose coopling we should -- 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

14 years, 3 months

6
5
0 / 0

[JBoss JIRA] (SOLDER-309) @Observes HttpServletResponse response causes IllegalProductException

by Ove Ranheim (Created) (JIRA)

@Observes HttpServletResponse response causes IllegalProductException --------------------------------------------------------------------- Key: SOLDER-309 URL: https://issues.jboss.org/browse/SOLDER-309 Project: Solder Issue Type: Bug Components: Servlet Affects Versions: 3.1.0.CR1 Reporter: Ove Ranheim Fix For: 3.1.0.Final The ImplicitHttpServletObjectsProducer.getHttpServletResponse() produces a null instance when invoked from an @Observer. {noformat} public void observeHttpRequest(@Observes @Initialized HttpServletRequest request, HttpServletResponse response) { final String path = request.getServletPath(); // Only manage contexts for authorized users if (identity.isLoggedIn()) { // Redirect user to dashboard if landing page is request if ("/index".equals(path) || "/index.jsf".equals(path)) { log.infof("Authorized request to: %s. Will be redirected to home!", path); try { response.sendRedirect(request.getContextPath() + "/home"); } catch (IOException e) { e.printStackTrace(); } } } } {noformat} Causes the exception: {noformat} org.jboss.weld.exceptions.IllegalProductException: WELD-000052 Cannot return null from a non-dependent producer method: [method] @Produces @Typed @RequestScoped protected org.jboss.solder.servlet.http.ImplicitHttpServletObjectsProducer.getHttpServletResponse() org.jboss.weld.bean.AbstractProducerBean.checkReturnValue(AbstractProducerBean.java:256) org.jboss.weld.bean.AbstractProducerBean.create(AbstractProducerBean.java:362) org.jboss.weld.context.AbstractContext.get(AbstractContext.java:122) org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:99) org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:124) org.jboss.weld.proxies.HttpServletResponse$1903192262$Proxy$_$$_WeldClientProxy.sendRedirect(HttpServletResponse$1903192262$Proxy$_$$_WeldClientProxy.java) com.musific.webapp.session.HttpRequestWatcher.observeHttpRequest(HttpRequestWatcher.java:80) com.musific.webapp.session.HttpRequestWatcher$Proxy$_$$_WeldClientProxy.observeHttpRequest(HttpRequestWatcher$Proxy$_$$_WeldClientProxy.java) sun.reflect.GeneratedMethodAccessor223.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305) org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163) org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299) org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188) org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59) org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198) org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282) org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265) org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234) org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635) org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:622) org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:616) org.jboss.solder.servlet.event.AbstractServletEventBridge.fireEvent(AbstractServletEventBridge.java:45) org.jboss.solder.servlet.event.ServletEventBridgeListener.requestInitialized(ServletEventBridgeListener.java:76) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) java.lang.Thread.run(Thread.java:680) {noformat} -- 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

14 years, 3 months

11
19
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2011