[JBoss JIRA] (AS7-3186) Admin console: HTML code inconsistency causing automated tests to fail
by Jan Martiska (Created) (JIRA)
Admin console: HTML code inconsistency causing automated tests to fail
----------------------------------------------------------------------
Key: AS7-3186
URL: https://issues.jboss.org/browse/AS7-3186
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Jan Martiska
Assignee: Pavel Slegr
Run AS7 in Domain mode. Navigate to Runtime/Status/Domain Status
- the item "Server Instances" in the menu has a different HTML code than others.
<div class="gwt-HTML">Server Instances</div>
compared to other nodes, e.g. JVM Status:
<div style="display: inline; " class="gwt-TreeItem" role="treeitem" id="gwt-uid-6" aria-level="2" aria-setsize="2" aria-posinset="2" aria-selected="true">JVM Status</div>
Selenium tests try to locate these items using the class gwt-TreeItem and role "treeitem", these should be applied to "Server Instances" menu item too.
--
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
[JBoss JIRA] (AS7-3265) Java Mail: NoSuchProviderException for any default provider with a Seam 2 application
by Philippe Guinot (Created) (JIRA)
Java Mail: NoSuchProviderException for any default provider with a Seam 2 application
-------------------------------------------------------------------------------------
Key: AS7-3265
URL: https://issues.jboss.org/browse/AS7-3265
Project: Application Server 7
Issue Type: Bug
Components: EE
Affects Versions: 7.1.0.Final
Environment: 7.1.0 Final nightly built from January 6.
Seam 2.2.2
Reporter: Philippe Guinot
Assignee: David Lloyd
Priority: Minor
My web application contains Seam 2.2.2, which has a META-INF/javamail.providers.
In javax.mail.Session.loadProviders(Class cl):
{code}loadAllResources("META-INF/javamail.providers", cl, loader);{code}
=> load Seam 2.2.2's mock provider.
{code}loadResource("/META-INF/javamail.default.providers", cl, loader);{code}
=> should load Java Mail's default providers, but given class is org.jboss.as.mail.extension.MailSessionService$PasswordAuthentication, which has no access to java mail's META-INF
{code}if (providers.size() == 0)
pr("DEBUG: failed to load any providers, using defaults");{code}
=> unfortunately, Seam's mock loader has been loaded, and no default will be loaded.
Then, using Java Mail I get:
{code}javax.mail.NoSuchProviderException: No provider for smtp
at javax.mail.Session.getProvider(Session.java:464) [mail-1.4.4.jar:1.4.4]
at javax.mail.Session.getTransport(Session.java:659) [mail-1.4.4.jar:1.4.4]
at javax.mail.Session.getTransport(Session.java:640) [mail-1.4.4.jar:1.4.4]
at javax.mail.Session.getTransport(Session.java:626) [mail-1.4.4.jar:1.4.4]
{code}
--
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
[JBoss JIRA] (AS7-2397) Infinispan subsystem is not functional unless the jpa one activated.
by Shane Johnson (Created) (JIRA)
Infinispan subsystem is not functional unless the jpa one activated.
--------------------------------------------------------------------
Key: AS7-2397
URL: https://issues.jboss.org/browse/AS7-2397
Project: Application Server 7
Issue Type: Bug
Components: Modules
Affects Versions: 7.0.1.Final
Reporter: Shane Johnson
Assignee: David Lloyd
If I start an Infinispan cache eagerly then I get an exception that transactions are required and a transaction manager has not been properly configured. Seems that the default Infinispan cache configuration is transactional, but the allowed values to override this do NOT include non transactional like the standard Infinispan configuration does.
If I try to get at an Infinispan cache via @Resource using the JNDI mapped name, it is not found because it is in fact not created despite the subsystem being activated. It is only created if I add a persistence.xml file to my deployment with L2 caching enabled in order to activate the JPA subsystem. Once the JPA subsystem is activated it seems that the Infinispan subsystem is able to create the caches on demand when I need them.
The Infinispan subsystem should not be dependent on the JPA subsystem.
--
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
[JBoss JIRA] (AS7-3266) Launching OSGi subsystem causes exception
by David Bosschaert (Created) (JIRA)
Launching OSGi subsystem causes exception
-----------------------------------------
Key: AS7-3266
URL: https://issues.jboss.org/browse/AS7-3266
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Reporter: David Bosschaert
Assignee: Thomas Diesler
[built using upstream/master on Jan 11, 2012]
Launching the OSGi subsystem causes the following exception to appear:
08:24:45,474 ERROR [org.jboss.osgi.framework.internal.FrameworkEventsPlugin] (MSC service thread 1-10) Framework ERROR: org.osgi.framework.BundleException: Cannot resolve bundle resModule: [jboss-as-osgi-configadmin:7.1.0.Final-SNAPSHOT]
at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:157) [jbosgi-framework-core-1.1.0.jar:1.1.0]
at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551) [jbosgi-framework-core-1.1.0.jar:1.1.0]
at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:211) [jbosgi-framework-core-1.1.0.jar:1.1.0]
at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494) [jbosgi-framework-core-1.1.0.jar:1.1.0]
at org.jboss.osgi.framework.internal.StartLevelPlugin.increaseStartLevel(StartLevelPlugin.java:257) [jbosgi-framework-core-1.1.0.jar:1.1.0]
at org.jboss.osgi.framework.internal.FrameworkActive.start(FrameworkActive.java:93) [jbosgi-framework-core-1.1.0.jar:1.1.0]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_29]
Caused by: org.jboss.osgi.resolver.XResolverException: Unable to resolve Module[jboss-as-osgi-configadmin:7.1.0.Final-SNAPSHOT]: missing requirement [Module[jboss-as-osgi-configadmin:7.1.0.Final-SNAPSHOT]] package; (package=org.jboss.as.configadmin.service)
at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:117) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.spi.AbstractResolver.resolve(AbstractResolver.java:148) [jbosgi-resolver-spi-1.0.10.jar:1.0.10]
at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:155) [jbosgi-framework-core-1.1.0.jar:1.1.0]
... 10 more
08:24:45,476 ERROR [org.jboss.osgi.framework.internal.FrameworkEventsPlugin] (MSC service thread 1-10) Framework ERROR: org.osgi.framework.BundleException: Cannot resolve bundle: jboss-as-osgi-configadmin:7.1.0.Final-SNAPSHOT
at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:212) [jbosgi-framework-core-1.1.0.jar:1.1.0]
at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494) [jbosgi-framework-core-1.1.0.jar:1.1.0]
at org.jboss.osgi.framework.internal.StartLevelPlugin.increaseStartLevel(StartLevelPlugin.java:257) [jbosgi-framework-core-1.1.0.jar:1.1.0]
at org.jboss.osgi.framework.internal.FrameworkActive.start(FrameworkActive.java:93) [jbosgi-framework-core-1.1.0.jar:1.1.0]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_29]
08:24:45,477 INFO [org.jboss.osgi.framework.internal.FrameworkActive] (MSC service thread 1-10) OSGi Framework started
08:24:45,488 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.1.0.Final-SNAPSHOT "Flux Capacitor" started in 1716ms - Started 131 of 202 services (69 services are passive or on-demand)
--
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