February 2009 - embjopr-issues - Jboss List Archives

[JBoss JIRA] Created: (EMBJOPR-79) After failed deployment of EAR, it's not listed but stays in /deploy. All following (.*ar) deployments display the old failure message.

by Ondrej Žižka (JIRA)

After failed deployment of EAR, it's not listed but stays in /deploy. All following (.*ar) deployments display the old failure message. --------------------------------------------------------------------------------------------------------------------------------------- Key: EMBJOPR-79 URL: https://jira.jboss.org/jira/browse/EMBJOPR-79 Project: Embedded Jopr Issue Type: Bug Components: Web App/Integration Affects Versions: 1.1 Environment: Embedded Jopr Core 1.1.1-SNAPSHOT Reporter: Ondrej Žižka Deployment of EAR with invalid application.xml fails with this message: -------------------------------------------------------------------------------- Failed to create Resource hellothere.war - cause: java.lang.RuntimeException:org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** DEPLOYMENTS MISSING DEPLOYERS: Name vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.Beta1/server/default/deploy/malformed-application-xml.ear -> org.jboss.deployers.client.spi.IncompleteDeploymentException:Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** DEPLOYMENTS MISSING DEPLOYERS: Name vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.Beta1/server/default/deploy/malformed-application-xml.ear -------------------------------------------------------------------------------- However. the EAR itself stays in the /deploy dir on AS. Further, all further deployments end up with failure message of the same text except the first line: -------------------------------------------------------------------------------- Failed to create Resource hellothere.war - cause: ... -------------------------------------------------------------------------------- -- 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

15 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (EMBJOPR-83) java.lang.LinkageErrors seen during start of JBoss AS 5.1 with admin-console.war deployed

by Shelly McGowan (JIRA)

java.lang.LinkageErrors seen during start of JBoss AS 5.1 with admin-console.war deployed ----------------------------------------------------------------------------------------- Key: EMBJOPR-83 URL: https://jira.jboss.org/jira/browse/EMBJOPR-83 Project: Embedded Jopr Issue Type: Bug Environment: JBoss AS Branch_5_x r84532, embjopr r162 Reporter: Shelly McGowan During the inialization of the administration console, the rhq-platform-plugin gets loaded, searches jaxb.properties for a JAXB implementation and finds jaxb-impl.jar from $JBOSS_HOME/lib 2009-02-20 15:20:41,594 INFO [org.jboss.on.embedded.BootstrapAction] (main) Bootstrapping Administration Console v1.1.1-SNAPSHOT... 2009-02-20 15:20:41,594 DEBUG [org.jboss.on.embedded.BootstrapAction] (main) Reconfiguring JDK logging... 2009-02-20 15:20:41,617 DEBUG [org.jboss.on.embedded.BootstrapAction] (main) Configuring Mock Scenario Loader... 2009-02-20 15:20:41,618 INFO [org.rhq.core.pc.PluginContainer] (main) Initializing Plugin Container v1.2.0-SNAPSHOT... 2009-02-20 15:20:41,723 DEBUG [org.rhq.core.pc.PluginContainer] (main) Starting and configuring container service: PluginManager 2009-02-20 15:20:41,737 DEBUG [org.rhq.core.pc.plugin.PluginManager] (main) Plugin found at: jndi:/localhost/admin-console/plugins/rhq-platform-plugin-1.2.0-SNAPSHOT.jar 2009-02-20 15:20:41,741 DEBUG [org.rhq.core.clientapi.descriptor.AgentPluginDescriptorUtil] (main) Loading plugin descriptor from plugin jar at [jndi:/localhost/admin-console/plugins/rhq-platform-plugin-1.2.0-SNAPSHOT.jar]... 2009-02-20 15:20:41,741 FINE [javax.xml.bind] (main) Searching jaxb.properties 2009-02-20 15:20:41,742 FINE [javax.xml.bind] (main) Searching the system property 2009-02-20 15:20:41,742 FINE [javax.xml.bind] (main) Searching META-INF/services 2009-02-20 15:20:41,743 FINE [javax.xml.bind] (main) Trying to load com.sun.xml.bind.v2.ContextFactory 2009-02-20 15:20:41,744 FINE [javax.xml.bind] (main) loaded com.sun.xml.bind.v2.ContextFactory from vfszip:/home/smcgowan2/workspace/Branch_5_x/build/output/jboss-5.1.0.Beta1/lib/jaxb-impl.jar/com/sun/xml/bind/v2/ContextFactory.class 2009-02-20 15:20:41,748 FINE [com.sun.xml.bind.v2.ContextFactory] (main) Property com.sun.xml.bind.XmlAccessorFactoryis not active. Using JAXB's implementation 2009-02-20 15:20:41,947 FINE [com.sun.xml.bind.v2.runtime.reflect.opt.OptimizedAccessorFactory] (main) Using optimized Accessor for protected org.rhq.core.clientapi.descriptor.plugin.Version org.rhq.core.clientapi.descriptor.plugin.ResourceDescriptor.version : : Next, while loading jopr-jboss-as-5-plugin, the same seach occurs but this time loading the class results in an exception: 2009-02-20 15:20:44,006 DEBUG [org.rhq.core.pc.plugin.PluginManager] (main) Loading independent plugin [JBossAS5] from URL: jndi:/localhost/admin-console/plugins/jopr-jboss-as-5-plugin-2.2.0-SNAPSHOT.jar 2009-02-20 15:20:44,006 DEBUG [org.rhq.core.pc.plugin.PluginManager] (main) Loading plugin from: jndi:/localhost/admin-console/plugins/jopr-jboss-as-5-plugin-2.2.0-SNAPSHOT.jar 2009-02-20 15:20:44,026 DEBUG [org.rhq.core.pc.plugin.PluginDescriptorLoader] (main) Created classloader for plugin [jndi:/localhost/admin-console/plugins/jopr-jboss-as-5-plugin-2.2.0-SNAPSHOT.jar] 2009-02-20 15:20:44,026 DEBUG [org.rhq.core.clientapi.descriptor.AgentPluginDescriptorUtil] (main) Loading plugin descriptor from plugin jar at [jndi:/localhost/admin-console/plugins/jopr-jboss-as-5-plugin-2.2.0-SNAPSHOT.jar]... 2009-02-20 15:20:44,026 FINE [javax.xml.bind] (main) Searching jaxb.properties 2009-02-20 15:20:44,027 FINE [javax.xml.bind] (main) Searching the system property 2009-02-20 15:20:44,027 FINE [javax.xml.bind] (main) Searching META-INF/services 2009-02-20 15:20:44,027 FINE [javax.xml.bind] (main) Trying to load com.sun.xml.bind.v2.ContextFactory 2009-02-20 15:20:44,028 FINE [javax.xml.bind] (main) loaded com.sun.xml.bind.v2.ContextFactory from vfszip:/home/smcgowan2/workspace/Branch_5_x/build/output/jboss-5.1.0.Beta1/lib/jaxb-impl.jar/com/sun/xml/bind/v2/ContextFactory.class 2009-02-20 15:20:44,029 FINE [com.sun.xml.bind.v2.ContextFactory] (main) Property com.sun.xml.bind.XmlAccessorFactoryis not active. Using JAXB's implementation 2009-02-20 15:20:44,308 FINE [com.sun.xml.bind.v2.runtime.reflect.opt.Injector] (main) Unable to inject org/rhq/core/clientapi/descriptor/plugin/ResourceDescriptor$JaxbAccessorF_version java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor252.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sun.xml.bind.v2.runtime.reflect.opt.Injector.inject(Injector.java:181) at com.sun.xml.bind.v2.runtime.reflect.opt.Injector.inject(Injector.java:85) at com.sun.xml.bind.v2.runtime.reflect.opt.AccessorInjector.prepare(AccessorInjector.java:87) at com.sun.xml.bind.v2.runtime.reflect.opt.OptimizedAccessorFactory.get(OptimizedAccessorFactory.java:165) at com.sun.xml.bind.v2.runtime.reflect.Accessor$FieldReflection.optimize(Accessor.java:253) at com.sun.xml.bind.v2.runtime.property.SingleElementNodeProperty.<init>(SingleElementNodeProperty.java:89) at sun.reflect.GeneratedConstructorAccessor47.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at com.sun.xml.bind.v2.runtime.property.PropertyFactory.create(PropertyFactory.java:124) Caused by: java.lang.LinkageError: duplicate class definition: org/rhq/core/clientapi/descriptor/plugin/ResourceDescriptor$JaxbAccessorF_version at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:620) at java.lang.ClassLoader.defineClass(ClassLoader.java:465) The server does start. -- 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

15 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (EMBJOPR-76) Fix use of deprecated Seam methods

by Charles Crouch (JIRA)

Fix use of deprecated Seam methods ---------------------------------- Key: EMBJOPR-76 URL: https://jira.jboss.org/jira/browse/EMBJOPR-76 Project: Embedded Jopr Issue Type: Bug Affects Versions: 1.2 Reporter: Charles Crouch Priority: Minor Fix For: 1.2 When deploying Embedded into JBAS5 I'm seeing the following in the server.log 2009-02-18 13:08:40,921 WARN [org.jboss.seam.init.Initialization] (HDScanner) <action expression="#{redirect.captureCurrentView}" /> has been deprecated, use <action execute="#{redirect.captureCurrentView}" /> instead 2009-02-18 13:08:40,921 WARN [org.jboss.seam.init.Initialization] (HDScanner) <action expression="#{redirect.returnToCapturedView}" /> has been deprecated, use <action execute="#{redirect.returnToCapturedView}" /> instead -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (EMBJOPR-74) Deployed EJBs not listed

by Ondrej Žižka (JIRA)

Deployed EJBs not listed ------------------------ Key: EMBJOPR-74 URL: https://jira.jboss.org/jira/browse/EMBJOPR-74 Project: Embedded Jopr Issue Type: Bug Components: Core Infrastructure Affects Versions: 1.1 Environment: JBoss AS 5.x branch, EmbJopr 1.1.1-SNAPSHOT Reporter: Ondrej Žižka After successful deployment of an EJB jar, the jar itself goes to the deploy dir, but is not listed in EmbJopr in the summary tab. -- 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

15 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (EMBJOPR-72) Change some HTML bits to improve testability

by Ondrej Žižka (JIRA)

Change some HTML bits to improve testability -------------------------------------------- Key: EMBJOPR-72 URL: https://jira.jboss.org/jira/browse/EMBJOPR-72 Project: Embedded Jopr Issue Type: Task Reporter: Ondrej Žižka Assignee: Ondrej Žižka For QA, we use XPath. Some HTML constructs are XPath - unfriendly, like mixed content on various places where we need to work with the text. Mixed content = element that has both text nodes and elements as children. These changes should not affect functionality nor appearance of EmbJopr. -- 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

15 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (EMBJOPR-73) EJB deployments cannot be managed in Console with AS 5

by Shelly McGowan (JIRA)

EJB deployments cannot be managed in Console with AS 5 ------------------------------------------------------ Key: EMBJOPR-73 URL: https://jira.jboss.org/jira/browse/EMBJOPR-73 Project: Embedded Jopr Issue Type: Bug Reporter: Shelly McGowan Adding a standalone ejb.jar (where the .jar contains a stateless session bean and its' home and remote interfaces) returns status of: "Resource ejb.jar created successfully!" However, the ejb.jar is never added to the list of EJB JAR applications but was successfully deployed to the application server. ejb.jars do not show up even if the ejb.jar was hot deployed. ejbs also do not show up if they are deployed as part of an .ear. With AS 4, the if an .ear deployment contains ejb.jars the components are manageable. -- 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

15 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (EMBJOPR-38) AS5 plugin: execute ManagementView.loadProfile() once per PC discovery scan rather than on every call to discoverResources() for each type of service

by Ian Springer (JIRA)

AS5 plugin: execute ManagementView.loadProfile() once per PC discovery scan rather than on every call to discoverResources() for each type of service ----------------------------------------------------------------------------------------------------------------------------------------------------- Key: EMBJOPR-38 URL: https://jira.jboss.org/jira/browse/EMBJOPR-38 Project: Embedded Jopr Issue Type: Bug Components: Plugin Affects Versions: 1.0 Reporter: Ian Springer Priority: Critical Fix For: 1.1 This is important, because I'm pretty sure ManagementView.loadProfile() is an expensive call and we want to minimize our memory and CPU footprint in the host app server. This depends on the enhancement described by http://jira.rhq-project.org/browse/RHQ-1118 being implemented first. -- 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

15 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (EMBJOPR-33) Referencing JPA Persistence Units as PAR is an outdated specification term

by Shelly McGowan (JIRA)

Referencing JPA Persistence Units as PAR is an outdated specification term -------------------------------------------------------------------------- Key: EMBJOPR-33 URL: https://jira.jboss.org/jira/browse/EMBJOPR-33 Project: Embedded Jopr Issue Type: Bug Components: Look 'n' Feel (html/css) Reporter: Shelly McGowan Assignee: Charles Crouch Fix For: 1.1 One of the application types to be managed are JPA Persistence Units (PAR). The archive suffix, .par, was used to reference a persistence archive. This notion was removed in the Propsed Final Draft of the Persistence API 1.0 specification instead specifying the persistence unit should be packaged inside one or more .jar files. Is it intentional for the management console to refer to the persistence unit application type as PARs to differentiate between other application types? -- 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

15 years, 10 months

2
1
0 / 0

[JBoss JIRA] Updated: (EMBJOPR-70) java.lang.ClassCastException running 1.1.0.GA in 4.2.2.GA or 4.2.3.GA

by Heiko W. Rupp (JIRA)

[ https://jira.jboss.org/jira/browse/EMBJOPR-70?page=com.atlassian.jira.plu... ] Heiko W. Rupp updated EMBJOPR-70: --------------------------------- Fix Version/s: (was: 1.1) Affects Version/s: 1.1 > java.lang.ClassCastException running 1.1.0.GA in 4.2.2.GA or 4.2.3.GA > --------------------------------------------------------------------- > > Key: EMBJOPR-70 > URL: https://jira.jboss.org/jira/browse/EMBJOPR-70 > Project: Embedded Jopr > Issue Type: Bug > Affects Versions: 1.1 > Reporter: Tom Cunningham > > Seeing the following ClassCastException when running emb jopr 1.1.0.GA in either 4.2.2.GA or 4.2.3.GA. I see it on startup and also when logging in to admin-console. > 12:44:26,343 WARN [RuntimeDiscoveryExecutor] Failed to execute runtime discovery for Resources of type ResourceType[id=0, category=Service, name=JBossMQ, plugin=JBossAS] > java.lang.ClassCastException: org.jboss.mq.server.JMSDestinationManager > at org.rhq.plugins.jbossas.AbstractMessagingDiscoveryComponent.getVersionFromSource(AbstractMessagingDiscoveryComponent.java:107) > at org.rhq.plugins.jbossas.AbstractMessagingDiscoveryComponent.discoverResources(AbstractMessagingDiscoveryComponent.java:72) > at org.rhq.plugins.jbossas.JBossMQDiscoveryComponent.discoverResources(JBossMQDiscoveryComponent.java:44) > at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.executeComponentDiscovery(RuntimeDiscoveryExecutor.java:246) > at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.discoverForResource(RuntimeDiscoveryExecutor.java:218) > at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.runtimeDiscover(RuntimeDiscoveryExecutor.java:136) > at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.call(RuntimeDiscoveryExecutor.java:97) > at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.call(RuntimeDiscoveryExecutor.java:54) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) > at java.util.concurrent.FutureTask.run(FutureTask.java:123) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:65) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:168) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) > at java.lang.Thread.run(Thread.java:613) > 12:44:26,394 INFO [ContentManager] Discovered 1 new packages for Resource with id [-33]. > 12:44:26,412 INFO [ContentManager] Discovered 1 new packages for Resource with id [-34]. > 12:44:26,421 INFO [ContentManager] Discovered 1 new packages for Resource with id [-35]. -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Assigned: (EMBJOPR-70) java.lang.ClassCastException running 1.1.0.GA in 4.2.2.GA or 4.2.3.GA

by Heiko W. Rupp (JIRA)

[ https://jira.jboss.org/jira/browse/EMBJOPR-70?page=com.atlassian.jira.plu... ] Heiko W. Rupp reassigned EMBJOPR-70: ------------------------------------ Assignee: (was: Heiko W. Rupp) > java.lang.ClassCastException running 1.1.0.GA in 4.2.2.GA or 4.2.3.GA > --------------------------------------------------------------------- > > Key: EMBJOPR-70 > URL: https://jira.jboss.org/jira/browse/EMBJOPR-70 > Project: Embedded Jopr > Issue Type: Bug > Affects Versions: 1.1 > Reporter: Tom Cunningham > > Seeing the following ClassCastException when running emb jopr 1.1.0.GA in either 4.2.2.GA or 4.2.3.GA. I see it on startup and also when logging in to admin-console. > 12:44:26,343 WARN [RuntimeDiscoveryExecutor] Failed to execute runtime discovery for Resources of type ResourceType[id=0, category=Service, name=JBossMQ, plugin=JBossAS] > java.lang.ClassCastException: org.jboss.mq.server.JMSDestinationManager > at org.rhq.plugins.jbossas.AbstractMessagingDiscoveryComponent.getVersionFromSource(AbstractMessagingDiscoveryComponent.java:107) > at org.rhq.plugins.jbossas.AbstractMessagingDiscoveryComponent.discoverResources(AbstractMessagingDiscoveryComponent.java:72) > at org.rhq.plugins.jbossas.JBossMQDiscoveryComponent.discoverResources(JBossMQDiscoveryComponent.java:44) > at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.executeComponentDiscovery(RuntimeDiscoveryExecutor.java:246) > at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.discoverForResource(RuntimeDiscoveryExecutor.java:218) > at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.runtimeDiscover(RuntimeDiscoveryExecutor.java:136) > at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.call(RuntimeDiscoveryExecutor.java:97) > at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.call(RuntimeDiscoveryExecutor.java:54) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) > at java.util.concurrent.FutureTask.run(FutureTask.java:123) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:65) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:168) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) > at java.lang.Thread.run(Thread.java:613) > 12:44:26,394 INFO [ContentManager] Discovered 1 new packages for Resource with id [-33]. > 12:44:26,412 INFO [ContentManager] Discovered 1 new packages for Resource with id [-34]. > 12:44:26,421 INFO [ContentManager] Discovered 1 new packages for Resource with id [-35]. -- 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

15 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

embjopr-issues February 2009