July 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBAS-7032) Getting invalid deployment on what appears to be valid, a webbeans ear file.

by Stan Silvert (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-7032?page=com.atlassian.jira.plug... ] Stan Silvert commented on JBAS-7032: ------------------------------------ I think I see what the problem is. So after you get rid of the NPE by moving the jars, you try to hit the admin console and see the stack trace reported earlier. I notice that this stack trace contains WebBeansPhaseListener. This is installed automatically by JSF when it sees the /webbeans.deployer/lib-int/faces in the classpath. /webbeans.deployer/lib-int/faces/META-INF/faces-config.xml has an entry that tells JSF to load the WebBeansPhaseListener. Since admin console doesn't use WebBeans, this should not happen. So I suspect that the problem is with the WebBeans deployer. I'm guessing that it is placing the /webbeans.deployer/lib-int/faces in some classpath that is visible by the admin console's ServletContext resource path. > Getting invalid deployment on what appears to be valid, a webbeans ear file. > ---------------------------------------------------------------------------- > > Key: JBAS-7032 > URL: https://jira.jboss.org/jira/browse/JBAS-7032 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Deployers > Environment: JBoss AS 5.1 > JDK 1.6 u 13 > OpenSuSe 11.1 / SLES 10.2 > Reporter: John Ament > Assignee: Shelly McGowan > Priority: Blocker > Fix For: JBossAS-5.2.0.Beta1 > > Attachments: WhatUpDawg.ear > > > The best description I can give is from the forum. > Basically, I have an EAR that appears to be completely valid, it's 2 war's and 1 ejb module. It's built using web beans. I get the described stack trace when either deploying via the UI or just dropping the EAR file in deploy. However, I get different results. When I drop the ear in and restart, it loads perfectly (my app) but embedded jopr fails. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2200) Add the ablility to add an excel decision table and drl template in a changeset

by Andre Malenfant (JIRA)

Add the ablility to add an excel decision table and drl template in a changeset ------------------------------------------------------------------------------- Key: JBRULES-2200 URL: https://jira.jboss.org/jira/browse/JBRULES-2200 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-compiler, drools-decisiontables Reporter: Andre Malenfant Assignee: Mark Proctor Currently, change sets can contain Excel decision tables that will be automatically compiled. This allows to use the Agent functionality to have the decision table automatically recompiled upon a change to the Excel file. This only works for decision tables that contain the necessary metadata to generate the rules but does not work for "plain" decision tables that are compiled programatically by providing a template drl and using an ExternalSpreadsheetCompiler. It would be very useful to be able to specify a decision table and the corresponding drl template in a change set and be able to use the Agent functionality to have the rules recompiled automatically when one or the other file changes. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBXB-206) Performance work

by Jesper Pedersen (JIRA)

Performance work ---------------- Key: JBXB-206 URL: https://jira.jboss.org/jira/browse/JBXB-206 Project: JBoss XML Binding (JBossXB) Issue Type: Task Affects Versions: JBossXB-2.0.1.GA Reporter: Jesper Pedersen Attachments: jboss-profiler.properties, jbossxb.zip I'm seeing some large unmarshall times when using JBossXB to retrieve my JBMETA model. Created this issue in order to track any performance improvements that can be done. -- 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, 10 months

2
10
0 / 0

[JBoss JIRA] Created: (JBAS-7029) Test org.jboss.test.profileservice.test.PlatformMBeanUnitTestCase(profileservice).testThreadMXBean fails on JDK6

by Pavel Slavicek (JIRA)

Test org.jboss.test.profileservice.test.PlatformMBeanUnitTestCase(profileservice).testThreadMXBean fails on JDK6 ---------------------------------------------------------------------------------------------------------------- Key: JBAS-7029 URL: https://jira.jboss.org/jira/browse/JBAS-7029 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-5.1.0.GA Environment: Windows and Linux JDK6 Reporter: Pavel Slavicek Assignee: Shelly McGowan Test org.jboss.test.profileservice.test.PlatformMBeanUnitTestCase(profileservice).testThreadMXBean fails on JDK6 on line Set<ManagedOperation> ops = mo.getOperations(); log.debug(ops); assertEquals("Ops count is 8", 8, ops.size()); JDK6 contains JMX 1.4 and ThreadMXBean has 11 operations. Test log: junit.framework.AssertionFailedError: Ops count is 8 expected:<8> but was:<11> -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1644) Work out a suitable way to provide JBM examples/doc for AS 5

by Howard Gao (JIRA)

Work out a suitable way to provide JBM examples/doc for AS 5 ------------------------------------------------------------ Key: JBMESSAGING-1644 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1644 Project: JBoss Messaging Issue Type: Task Components: AS Integration Affects Versions: 1.4.3.GA Reporter: Howard Gao Assignee: Howard Gao Priority: Critical Fix For: 1.4.5.GA Current AS 5 distribution kit doesn't have JBM doc/examples of the corresponding version included, that makes it very inconvenient to use JBM with AS5. Users often get confused with which version of JBM is the correct version, and where to get the resouces (docs, examples). We have to provide a solution to that. -- 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, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1678) OME on the Journal when processing too many files

by Clebert Suconic (JIRA)

OME on the Journal when processing too many files ------------------------------------------------- Key: JBMESSAGING-1678 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1678 Project: JBoss Messaging Issue Type: Bug Affects Versions: 2.0.0.beta3, 2.0.0.beta2, 2.0.0 Beta1 Reporter: Clebert Suconic Assignee: Clebert Suconic Fix For: 2.0.0 Set one producer.. sending one message / second (about 200 messages) Set another producer/consumer (in another destination) sending as fast as it can. (about 500K messages). At the end you will have 200 files... but only 200 messages (one valid on each file). This will lead to an OME. On trunk, you need to deactivate compacting to replicate this. -- 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, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (JBBOOT-97) Initialize VFS during server initialization

by Andrew Lee Rubinger (JIRA)

Initialize VFS during server initialization ------------------------------------------- Key: JBBOOT-97 URL: https://jira.jboss.org/jira/browse/JBBOOT-97 Project: JBoss Bootstrap Issue Type: Task Components: impl-as Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: 2.0.0-beta-1 Use the new LifecycleStates defined by JBBOOT-95 to init VFS during server initialization -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBBOOT-95) Create server states to account for callbacks before and after server init

by Andrew Lee Rubinger (JIRA)

Create server states to account for callbacks before and after server init -------------------------------------------------------------------------- Key: JBBOOT-95 URL: https://jira.jboss.org/jira/browse/JBBOOT-95 Project: JBoss Bootstrap Issue Type: Task Components: impl-base, spi Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger We need to be able to have lifecycle callbacks take place either right before or right after server initialization. -- 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, 10 months

1
2
0 / 0

[JBoss JIRA] Commented: (JBAS-7032) Getting invalid deployment on what appears to be valid, a webbeans ear file.

by Stan Silvert (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-7032?page=com.atlassian.jira.plug... ] Stan Silvert commented on JBAS-7032: ------------------------------------ Shelly, I reproduced the NPE you were talking about: 12:36:01,025 ERROR [Digester] End event threw exception java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor289.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java:216) at org.apache.commons.digester.SetNextRule.end(SetNextRule.java:217) at org.apache.commons.digester.Rule.end(Rule.java:253) at org.apache.commons.digester.Digester.endElement(Digester.java:1222) Caused by: java.lang.NullPointerException at org.ajax4jsf.resource.InternetResourceBase.restoreData(InternetResourceBase.java:248) at org.richfaces.renderkit.html.Paint2DResource.getRenderer(Paint2DResource.java:68) at org.ajax4jsf.resource.ResourceBuilderImpl.addResource(ResourceBuilderImpl.java:406) This is easily reproduced by just cold-deploying the EAR attached to this JIRA. However, this EAR has several web jars that are in WhatUpDawg.ear/lib that probably shouldn't be there. I moved these to WhatUpDawg.ear/WhatUpDawg.war/WEB-INF/lib: jsf-facelets.jar jsf-tlds.jar (You shouldn't need this because the server exposes a global copy) jstl.jar (You shouldn't need this because the server exposes a global copy) richfaces-api-3.3.1.GA.jar richfaces-impl-3.3.1.GA.jar richfaces-ui-3.3.1.GA.jar So with these "web" jars in the proper place, Shelly's problem goes away. Was there some reason that you wanted to move Facelets and RichFaces outside of the war? > Getting invalid deployment on what appears to be valid, a webbeans ear file. > ---------------------------------------------------------------------------- > > Key: JBAS-7032 > URL: https://jira.jboss.org/jira/browse/JBAS-7032 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Deployers > Environment: JBoss AS 5.1 > JDK 1.6 u 13 > OpenSuSe 11.1 / SLES 10.2 > Reporter: John Ament > Assignee: Shelly McGowan > Priority: Blocker > Fix For: JBossAS-5.2.0.Beta1 > > Attachments: WhatUpDawg.ear > > > The best description I can give is from the forum. > Basically, I have an EAR that appears to be completely valid, it's 2 war's and 1 ejb module. It's built using web beans. I get the described stack trace when either deploying via the UI or just dropping the EAR file in deploy. However, I get different results. When I drop the ear in and restart, it loads perfectly (my app) but embedded jopr fails. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2198) CLONE -fireAllRules() blocks if called while fireUntilHalt() is running

by Neil Wallace (JIRA)

CLONE -fireAllRules() blocks if called while fireUntilHalt() is running ----------------------------------------------------------------------- Key: JBRULES-2198 URL: https://jira.jboss.org/jira/browse/JBRULES-2198 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.0.1.FINAL Reporter: Neil Wallace Assignee: Edson Tirelli Fix For: 5.0.2, 5.1.0.M1 Drools work items call fireAllRules() automatically after completion. If the engine is already running fireUntilHalt() though, it blocks. -- 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, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2009