[JBoss JIRA] Created: (AS7-1470) Application classes or applications referencing libraries depending on JAXB APIs fail to deploy
by Lincoln Baxter III (JIRA)
Application classes or applications referencing libraries depending on JAXB APIs fail to deploy
-----------------------------------------------------------------------------------------------
Key: AS7-1470
URL: https://issues.jboss.org/browse/AS7-1470
Project: Application Server 7
Issue Type: Bug
Components: XML Frameworks
Affects Versions: 7.0.0.Final
Environment: Sun JDK 1.6.0_24
Reporter: Lincoln Baxter III
Assignee: Jason Greene
It seems the AS7 is configured to hide JAXB implementation classes from deployed applications. It should in fact provide these classes, or another implementation of them.
11:22:52,669 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/example]] (MSC service thread 1-3) Exception sending context initialized event to listener instance of class com.ocpsoft.rewrite.servlet.impl.RewriteServletContextListener: com.ocpsoft.pretty.PrettyException: Failed to load configuration.
at com.ocpsoft.pretty.faces.config.PrettyConfigurator.configure(PrettyConfigurator.java:91) [prettyfaces-jsf2-3.3.1-SNAPSHOT.jar:]
at com.ocpsoft.rewrite.prettyfaces.PrettyConfigContextListener.contextInitialized(PrettyConfigContextListener.java:40) [prettyfaces-jsf2-3.3.1-SNAPSHOT.jar:]
at com.ocpsoft.rewrite.servlet.impl.RewriteServletContextListener.contextInitialized(RewriteServletContextListener.java:45) [rewrite-impl-servlet-1.0.0-SNAPSHOT.jar:]
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3368) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3821) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1]
at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:70) [jboss-as-web-7.0.0.CR1.jar:7.0.0.CR1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_24]
Caused by: java.lang.IllegalStateException: javax.xml.bind.JAXBException: Provider com.sun.xml.internal.bind.v2.ContextFactory not found
- with linked exception:
[java.lang.ClassNotFoundException: com.sun.xml.internal.bind.v2.ContextFactory from [Module "deployment.example.war:main" from Service Module Loader]]
at com.ocpsoft.pretty.faces.config.JAXBPrettyConfigParser.<init>(JAXBPrettyConfigParser.java:74) [prettyfaces-jsf2-3.3.1-SNAPSHOT.jar:]
at com.ocpsoft.pretty.faces.config.spi.ClassLoaderConfigurationProvider.loadConfiguration(ClassLoaderConfigurationProvider.java:54) [prettyfaces-jsf2-3.3.1-SNAPSHOT.jar:]
at com.ocpsoft.pretty.faces.config.PrettyConfigurator.configure(PrettyConfigurator.java:63) [prettyfaces-jsf2-3.3.1-SNAPSHOT.jar:]
... 10 more
Caused by: javax.xml.bind.JAXBException: Provider com.sun.xml.internal.bind.v2.ContextFactory not found
- with linked exception:
[java.lang.ClassNotFoundException: com.sun.xml.internal.bind.v2.ContextFactory from [Module "deployment.example.war:main" from Service Module Loader]]
at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:146) [jboss-jaxb-api_2.2_spec-1.0.2.Final.jar:1.0.2.Final]
at javax.xml.bind.ContextFinder.find(ContextFinder.java:289) [jboss-jaxb-api_2.2_spec-1.0.2.Final.jar:1.0.2.Final]
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:412) [jboss-jaxb-api_2.2_spec-1.0.2.Final.jar:1.0.2.Final]
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:375) [jboss-jaxb-api_2.2_spec-1.0.2.Final.jar:1.0.2.Final]
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:279) [jboss-jaxb-api_2.2_spec-1.0.2.Final.jar:1.0.2.Final]
at com.ocpsoft.pretty.faces.config.JAXBPrettyConfigParser.<init>(JAXBPrettyConfigParser.java:66) [prettyfaces-jsf2-3.3.1-SNAPSHOT.jar:]
... 12 more
Caused by: java.lang.ClassNotFoundException: com.sun.xml.internal.bind.v2.ContextFactory from [Module "deployment.example.war:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:191)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:358)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:307)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:101)
at javax.xml.bind.ContextFinder.safeLoadClass(ContextFinder.java:490) [jboss-jaxb-api_2.2_spec-1.0.2.Final.jar:1.0.2.Final]
at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:112) [jboss-jaxb-api_2.2_spec-1.0.2.Final.jar:1.0.2.Final]
... 17 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Created: (AS7-1707) jboss-as-arquillian-container-managed gets stuck when starting JBossAS 7.0.1+
by Martin Gencur (JIRA)
jboss-as-arquillian-container-managed gets stuck when starting JBossAS 7.0.1+
-----------------------------------------------------------------------------
Key: AS7-1707
URL: https://issues.jboss.org/browse/AS7-1707
Project: Application Server 7
Issue Type: Bug
Components: Test Suite
Affects Versions: 7.0.1.Final
Reporter: Martin Gencur
Assignee: Aslak Knutsen
When starting JBossAS 7.0.0.Final with jboss-as-arquillian-container-managed from maven, the JBossAS (even more instances in a cluster) starts smoothly. After updating the version to 7.0.1.Final, the managed container gets stuck when starting first of the JBossAS instances in the cluster. It hangs on "09:39:04,084 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.1.Final "Zap" started in 2570ms - Started 93 of 148 services (55 services are passive or on-demand)"
This is still true with JBossAS 7.1.0.Alpha1-SNAPSHOT (where HEAD = commit 0e3e092eb97d2b3d324ca623db0dabc949a6fbbe - AS7-1697 Add test that verifies methods with arrays in their signature are handled correctly)
I tried various combinations of maven-surefire-plugin (2.9 with forkMode = once, 2.9 with fork mode never, 2.8.1 with fork mode once), none of them works.
The configuration I'm using in arquillian.xml is:
{code:xml}
<group qualifier="Grid">
<container qualifier="container1" managed="true">
<protocol type="jmx-as7">
<property name="executionType">REMOTE</property>
</protocol>
<configuration>
<property name="bindAddress">test1</property>
<property name="managementPort">9999</property>
<property name="jbossHome">/home/mgencur/Java/jboss7/jboss-as-7.0.1.Final</property>
</configuration>
</container>
<container qualifier="container2" managed="false">
<protocol type="jmx-as7">
<property name="executionType">REMOTE</property>
</protocol>
<configuration>
<property name="bindAddress">test2</property>
<property name="managementPort">19999</property>
<property name="jbossHome">/home/mgencur/Java/jboss7/jboss-as-7.0.1.Final-2</property>
</configuration>
</container>
</group>
{code}
Is this a configuration problem?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Commented: (AS7-1338) Remote JNDI support for AS7
by Carlo de Wolf (JIRA)
[ https://issues.jboss.org/browse/AS7-1338?page=com.atlassian.jira.plugin.s... ]
Carlo de Wolf commented on AS7-1338:
------------------------------------
Since people keep coming back to this issue for what is actually "Client JNDI support" I've raised AS7-1709.
> Remote JNDI support for AS7
> ---------------------------
>
> Key: AS7-1338
> URL: https://issues.jboss.org/browse/AS7-1338
> Project: Application Server 7
> Issue Type: Task
> Components: Naming
> Reporter: Richard Opalka
> Assignee: David Lloyd
> Priority: Blocker
> Fix For: No Release
>
>
> <opalka> wolfc, dmlloyd I'm not able to connect to JNDI on AS7. in the AS7 config I see it should be running on 1099, but I'm getting http://fpaste.org/wgy8/ :(
> <opalka> wolfc, dmlloyd in the config I see the following ports defined
> <opalka> ---
> <opalka> <socket-binding name="jndi" port="1099"/>
> <opalka> <socket-binding name="jmx-connector-registry" port="1090"/>
> <opalka> <socket-binding name="jmx-connector-server" port="1091"/>
> <opalka> ---
> <dmlloyd> we don't do JNDI over RMI anymore
> <dmlloyd> that listing is an error
> <opalka> dmlloyd, So we're not able to do JNDI lookups to AS7 anymore and don't plan to?
> <opalka> dmlloyd, or we'll be doing JNDI over different binary protocol?
> <dmlloyd> no, we will be able to, it'll just work somewhat differently
> <opalka> dmlloyd, ok, I'm excluding the tests then ...
> <opalka> dmlloyd, Is there a JIRA covering this issue so I can use it in my excludes comment?
> <dmlloyd> not that I'm aware of, it's just an outstanding task
> <dmlloyd> remote invocation is not planned to be covered in next months' beta release
> <opalka> dmlloyd, ok, thx for info ;)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months