February 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2907) Trinidad applications runs fine on JBoss AS 7, but on AS 8 generates error

by deepak vohra (JIRA)

deepak vohra created WFLY-2907: ---------------------------------- Summary: Trinidad applications runs fine on JBoss AS 7, but on AS 8 generates error Key: WFLY-2907 URL: https://issues.jboss.org/browse/WFLY-2907 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: Trinidad 2 Reporter: deepak vohra A Trinidad 2 UI page generates following exception. Application runs fine on JBoss AS 8. java.lang.NullPointerException at com.sun.el.ValueExpressionLiteral.getValue(ValueExpressionLiteral.java:79) [javax.el-3.0-b07.jar:3.0-b07] at org.apache.jasper.el.JspValueExpression.getValue(JspValueExpression.java:101) [jastow-1.0.0.CR1.jar:1.0.0.CR1] at org.apache.myfaces.trinidad.webapp.UIXComponentELTag.setProperty(UIXComponentELTag.java:109) [trinidad-api-2.0.1.jar:2.0.1] at org.apache.myfaces.trinidadinternal.taglib.core.nav.CoreCommandLinkTag.setProperties(CoreCommandLinkTag.java:251) [trinidad-impl-2.0.1.jar:2.0.1] at org.apache.myfaces.trinidad.webapp.UIXComponentELTag.setProperties(UIXComponentELTag.java:96) [trinidad-api-2.0.1.jar:2.0.1] at javax.faces.webapp.UIComponentELTag.createComponent(UIComponentELTag.java:230) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4] at javax.faces.webapp.UIComponentClassicTagBase.createChild(UIComponentClassicTagBase.java:504) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4] at javax.faces.webapp.UIComponentClassicTagBase.findComponent(UIComponentClassicTagBase.java:742) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4] at javax.faces.webapp.UIComponentClassicTagBase.doStartTag(UIComponentClassicTagBase.java:1309) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4] at org.apache.myfaces.trinidad.webapp.UIXComponentELTag.doStartTag(UIXComponentELTag.java:67) [trinidad-api-2.0.1.jar:2.0.1] at org.apache.jsp.index_jsp._jspx_meth_tr_005fcommandLink_005f0(index_jsp.java:252) at org.apache.jsp.index_jsp._jspx_meth_tr_005fform_005f0(index_jsp.java:208) at org.apache.jsp.index_jsp._jspx_meth_tr_005fdocument_005f0(index_jsp.java:161) at org.apache.jsp.index_jsp._jspx_meth_f_005fview_005f0(index_jsp.java:118) at org.apache.jsp.index_jsp._jspService(index_jsp.java:80) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:69) [jastow-1.0.0.CR1.jar:1.0.0.CR1] at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:366) [jastow-1.0.0.CR1.jar:1.0.0.CR1] ... 54 more -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2881) org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase#testCalendarBasedTimeout

by Frank Langelage (JIRA)

[ https://issues.jboss.org/browse/WFLY-2881?page=com.atlassian.jira.plugin.... ] Frank Langelage commented on WFLY-2881: --------------------------------------- That was already committed when I had the problem, that's for sure. Commenting out this line did not solve the problem but created a new one, CalendarBasedTimeoutWithDifferentTimeZoneTestCase also failed, if I remember correctly. > org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase#testCalendarBasedTimeout > -------------------------------------------------------------------------------------- > > Key: WFLY-2881 > URL: https://issues.jboss.org/browse/WFLY-2881 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Affects Versions: 8.0.0.Final > Reporter: Frank Langelage > Assignee: Tomaz Cerar > Attachments: org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase.txt, TEST-org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase.xml > > > Running build with smoke tests on current github sources I get failure in this test case. > HOUR_OF_DAY is not 0 as expected but 1. > I changed the Assert in the test case to print out firstTimeout.toString() instead of only timeZoneDisplayName. > See attached files for more. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2881) org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase#testCalendarBasedTimeout

by Cody Lerum (JIRA)

[ https://issues.jboss.org/browse/WFLY-2881?page=com.atlassian.jira.plugin.... ] Cody Lerum commented on WFLY-2881: ---------------------------------- What about https://github.com/wildfly/wildfly/commit/4cec495de4348018078e20a092edc9c... > org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase#testCalendarBasedTimeout > -------------------------------------------------------------------------------------- > > Key: WFLY-2881 > URL: https://issues.jboss.org/browse/WFLY-2881 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Affects Versions: 8.0.0.Final > Reporter: Frank Langelage > Assignee: Tomaz Cerar > Attachments: org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase.txt, TEST-org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase.xml > > > Running build with smoke tests on current github sources I get failure in this test case. > HOUR_OF_DAY is not 0 as expected but 1. > I changed the Assert in the test case to print out firstTimeout.toString() instead of only timeZoneDisplayName. > See attached files for more. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2881) org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase#testCalendarBasedTimeout

by Frank Langelage (JIRA)

[ https://issues.jboss.org/browse/WFLY-2881?page=com.atlassian.jira.plugin.... ] Frank Langelage commented on WFLY-2881: --------------------------------------- Currently I also cannot reproduce the problem. When I created this issue, it was producible every time. But looking at build 2623 http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=10705&buildTyp... you can see that it also happened on the redhat build server. And disappeared. I see no code change that might have fixed the problem. I suspect that the appearance of the problem has to do with the time of the day when the test is run. I'll try a test run later again and tomorrow morning German time. Anyways within the testcase the Assert.fail(timeZoneDisplayName); in line 496 and 527 should be changed to Assert.fail(firstTimeout.toString()); to printout the whole Calendar object or at least to a printout of the fields checked or Assert.equals for th checked fields. The timezone is not checked. > org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase#testCalendarBasedTimeout > -------------------------------------------------------------------------------------- > > Key: WFLY-2881 > URL: https://issues.jboss.org/browse/WFLY-2881 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Affects Versions: 8.0.0.Final > Reporter: Frank Langelage > Assignee: Tomaz Cerar > Attachments: org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase.txt, TEST-org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase.xml > > > Running build with smoke tests on current github sources I get failure in this test case. > HOUR_OF_DAY is not 0 as expected but 1. > I changed the Assert in the test case to print out firstTimeout.toString() instead of only timeZoneDisplayName. > See attached files for more. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-426) Globals can't be used with temporal operators

by Davide Sottara (JIRA)

Davide Sottara created DROOLS-426: ------------------------------------- Summary: Globals can't be used with temporal operators Key: DROOLS-426 URL: https://issues.jboss.org/browse/DROOLS-426 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Davide Sottara Assignee: Mark Proctor Priority: Critical Assuming: global Date now; The pattern "Foo( this before now )" will generate various errors. The reason is that the Global[X]Extractors (X = {"","Date","Number"} are erroneously declared as self-referential extractors. If Foo is not an @event, a CCE will arise since the operators will use "this" rather than the global. Otherwise, the result will be inconsistent -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2906) WildFly 8CR1 keeps lock on Manifest.mf files in exploded deployment

by Wolfgang Knauf (JIRA)

Wolfgang Knauf created WFLY-2906: ------------------------------------ Summary: WildFly 8CR1 keeps lock on Manifest.mf files in exploded deployment Key: WFLY-2906 URL: https://issues.jboss.org/browse/WFLY-2906 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 8.0.0.CR1 Environment: Windows7x64, Oracle Java 1.7.0_51 Reporter: Wolfgang Knauf I have a small JSF web app. When performing exploded deployment, after a ".dodeploy"/."undeploy"/".dodeploy"/".undeploy" cycle, the manifest.mf files are locked (I cannot delete the files, Windows tells me that they are used by a Java process) A similar sample without JSF (and beans.xml) does not show this problem. See the forum post for more details and the zip file of the "to be deployed" app. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2905) PROCESS_ID_UUID should be done and tested for older model versions

by Amos Feng (JIRA)

Amos Feng created WFLY-2905: ------------------------------- Summary: PROCESS_ID_UUID should be done and tested for older model versions Key: WFLY-2905 URL: https://issues.jboss.org/browse/WFLY-2905 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Transactions Reporter: Amos Feng Assignee: Amos Feng Fix For: 8.0.1.Final There are some problem with the transformer when setting the default value of PROCESS_ID_UUID -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2898) JNDI Name lookup of the DataSource returns NULL

by Igor Shulika (JIRA)

[ https://issues.jboss.org/browse/WFLY-2898?page=com.atlassian.jira.plugin.... ] Igor Shulika commented on WFLY-2898: ------------------------------------ <subsystem xmlns="urn:jboss:domain:naming:2.0"> <remote-naming/> </subsystem> > JNDI Name lookup of the DataSource returns NULL > ----------------------------------------------- > > Key: WFLY-2898 > URL: https://issues.jboss.org/browse/WFLY-2898 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Naming, Web (Undertow) > Affects Versions: 8.0.0.CR1, 8.0.0.Final > Reporter: Igor Shulika > Assignee: Eduardo Martins > Attachments: 1.PNG, 2.PNG, 3.PNG > > > Hi, > I'm having a problem to obtain DataSource using JNDI Name lookup. > Please see my code below: > Connection connection = null; > DataSource dataSource = null; > try { > final Context initContext = new InitialContext(); > dataSource = (DataSource) initContext.lookup("java:/MyDataSource"); connection = dataSource.getConnection(); > } catch (Exception e) { > LOGGER.error(e); > } > I'm doing initContext.lookup from a servlet, everything is working on JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14). > Also I can find and test connection of my “java:/MyDataSource” under the “Datasources” section of the WildFly Administration Console just fine(anoter word the datasource is there). -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2898) JNDI Name lookup of the DataSource returns NULL

by Igor Shulika (JIRA)

[ https://issues.jboss.org/browse/WFLY-2898?page=com.atlassian.jira.plugin.... ] Igor Shulika commented on WFLY-2898: ------------------------------------ Everything is working on JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14), looks like something changed recently. > JNDI Name lookup of the DataSource returns NULL > ----------------------------------------------- > > Key: WFLY-2898 > URL: https://issues.jboss.org/browse/WFLY-2898 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Naming, Web (Undertow) > Affects Versions: 8.0.0.CR1, 8.0.0.Final > Reporter: Igor Shulika > Assignee: Eduardo Martins > Attachments: 1.PNG, 2.PNG, 3.PNG > > > Hi, > I'm having a problem to obtain DataSource using JNDI Name lookup. > Please see my code below: > Connection connection = null; > DataSource dataSource = null; > try { > final Context initContext = new InitialContext(); > dataSource = (DataSource) initContext.lookup("java:/MyDataSource"); connection = dataSource.getConnection(); > } catch (Exception e) { > LOGGER.error(e); > } > I'm doing initContext.lookup from a servlet, everything is working on JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14). > Also I can find and test connection of my “java:/MyDataSource” under the “Datasources” section of the WildFly Administration Console just fine(anoter word the datasource is there). -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2898) JNDI Name lookup of the DataSource returns NULL

by Igor Shulika (JIRA)

[ https://issues.jboss.org/browse/WFLY-2898?page=com.atlassian.jira.plugin.... ] Igor Shulika commented on WFLY-2898: ------------------------------------ <subsystem xmlns="urn:jboss:domain:datasources:2.0"> <datasources> <datasource jndi-name="java:/GOLDDatasource" pool-name="GOLDDatasource" enabled="true" use-java-context="true"> <connection-url>jdbc:oracle:thin:@xxxxxx:1521/dev11g</connection-url> <driver-class>org.jaffa.driver.oracle.OracleDriver</driver-class> <driver>oracle</driver> <pool> <max-pool-size>100</max-pool-size> </pool> <security> <user-name>xxxxx</user-name> <password>xxxxx</password> </security> </datasource> <xa-datasource jndi-name="java:/GOLDTxDatasource" pool-name="GOLDTxDatasource" enabled="true" use-java-context="true"> <xa-datasource-property name="URL"> jdbc:oracle:thin:@xxxxxxxx:1521/dev11g </xa-datasource-property> <xa-datasource-property name="User"> xxxxx </xa-datasource-property> <xa-datasource-property name="Password"> xxxxx </xa-datasource-property> <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class> <driver>oracle</driver> <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation> <xa-pool> <min-pool-size>1</min-pool-size> <max-pool-size>100</max-pool-size> <prefill>false</prefill> <use-strict-min>false</use-strict-min> <flush-strategy>FailingConnectionOnly</flush-strategy> <no-tx-separate-pools>true</no-tx-separate-pools> <pad-xid>false</pad-xid> <wrap-xa-resource>true</wrap-xa-resource> </xa-pool> <security> <user-name>xxxxx</user-name> <password>xxxxxx</password> </security> <validation> <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker"/> <validate-on-match>false</validate-on-match> <background-validation>false</background-validation> <use-fast-fail>false</use-fast-fail> <stale-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleStaleConnectionChecker"/> <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleExceptionSorter"/> </validation> </xa-datasource> <drivers> <driver name="oracle" module="org.jaffa.jdbc.driver.oracle"> <driver-class>org.jaffa.driver.oracle.OracleDriver</driver-class> <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class> </driver> </drivers> </datasources> </subsystem> > JNDI Name lookup of the DataSource returns NULL > ----------------------------------------------- > > Key: WFLY-2898 > URL: https://issues.jboss.org/browse/WFLY-2898 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Naming, Web (Undertow) > Affects Versions: 8.0.0.CR1, 8.0.0.Final > Reporter: Igor Shulika > Assignee: Eduardo Martins > Attachments: 1.PNG, 2.PNG, 3.PNG > > > Hi, > I'm having a problem to obtain DataSource using JNDI Name lookup. > Please see my code below: > Connection connection = null; > DataSource dataSource = null; > try { > final Context initContext = new InitialContext(); > dataSource = (DataSource) initContext.lookup("java:/MyDataSource"); connection = dataSource.getConnection(); > } catch (Exception e) { > LOGGER.error(e); > } > I'm doing initContext.lookup from a servlet, everything is working on JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14). > Also I can find and test connection of my “java:/MyDataSource” under the “Datasources” section of the WildFly Administration Console just fine(anoter word the datasource is there). -- 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

12 years, 3 months

1
0
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 February 2014