[JBoss JIRA] (AS7-2138) javax.naming.NameNotFoundException: rmi://127.0.0.1:1090/jmxrmi thrown when creating MBeanServerConnection
by John Sanda (JIRA)
[ https://issues.jboss.org/browse/AS7-2138?page=com.atlassian.jira.plugin.s... ]
John Sanda commented on AS7-2138:
---------------------------------
Can this issue please be reopened? It is not fixed. I am seeing this problem with a 7.2.0.Alpha1-redhat-4 build. Here is my environment info,
OS: Mac OS X 10.8.3
Java: 1.7.0_13
JRE: HotSpot 64 bit
> javax.naming.NameNotFoundException: rmi://127.0.0.1:1090/jmxrmi thrown when creating MBeanServerConnection
> ----------------------------------------------------------------------------------------------------------
>
> Key: AS7-2138
> URL: https://issues.jboss.org/browse/AS7-2138
> Project: Application Server 7
> Issue Type: Bug
> Components: JMX
> Affects Versions: 7.0.0.Final, 7.0.1.Final, 7.0.2.Final, 7.1.0.Final
> Reporter: Stian Thorgersen
> Assignee: Bartosz Baranowski
> Fix For: 7.1.2.Final (EAP)
>
> Attachments: jmx-test.jar, JmxClient.java, JMXConnectionBean.java, JmxServer.java
>
>
> When trying to create a MBeanServerConnection from within an EJB a "javax.naming.NameNotFoundException" is thrown. When executed as a standalone Java the same code works fine. To verify that it works as a standalone Java process run "java -cp jmx-test.jar com.example.JMXConnectionBean" (with AS7 running on the same machine).
> Full stack trace:
> {code}
> Caused by: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.NameNotFoundException: rmi://127.0.0.1:1090/jmxrmi -- service jboss.naming.context.java.rmi:."127.0.0.1:1090".jmxrmi
> at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:340) [:1.6.0_26]
> at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) [:1.6.0_26]
> at com.example.JMXConnectionBean.init(JMXConnectionBean.java:28)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_26]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_26]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_26]
> at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_26]
> at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptor.java:70)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.as.ee.component.ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptor.java:53)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:44)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.as.ejb3.component.session.SessionInvocationContextInterceptor$CustomSessionInvocationContext.proceed(SessionInvocationContextInterceptor.java:126)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:211)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:313)
> at org.jboss.as.ejb3.tx.SingletonLifecycleCMTTxInterceptor.processInvocation(SingletonLifecycleCMTTxInterceptor.java:56)
> at org.jboss.as.ejb3.tx.SingletonLifecycleCMTTxInterceptor.processInvocation(SingletonLifecycleCMTTxInterceptor.java:42)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.as.ejb3.component.session.SessionInvocationContextInterceptor.processInvocation(SessionInvocationContextInterceptor.java:71)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:152)
> ... 9 more
> Caused by: javax.naming.NameNotFoundException: rmi://127.0.0.1:1090/jmxrmi -- service jboss.naming.context.java.rmi:."127.0.0.1:1090".jmxrmi
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173)
> at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:209)
> at javax.naming.InitialContext.lookup(InitialContext.java:392) [:1.6.0_26]
> at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1888) [:1.6.0_26]
> at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1858) [:1.6.0_26]
> at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:257) [:1.6.0_26]
> ... 37 more
> {code}
--
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
13 years, 2 months
[JBoss JIRA] (WFLY-794) javax.naming.NameNotFoundException: rmi://127.0.0.1:1090/jmxrmi thrown when creating MBeanServerConnection
by John Sanda (JIRA)
[ https://issues.jboss.org/browse/WFLY-794?page=com.atlassian.jira.plugin.s... ]
John Sanda commented on WFLY-794:
---------------------------------
I have hit this bug as well. It is not an OpenJDK issue. I am running on Mac OS X 10.8.3 and 64 bit HotSpot JVM version 1.7.0_13. I have reproduced the bug on AS 7.1.1.Final and on EAP 6.1 (where the build version is 7.2.0.Alpha1-redhat-4).
> javax.naming.NameNotFoundException: rmi://127.0.0.1:1090/jmxrmi thrown when creating MBeanServerConnection
> ----------------------------------------------------------------------------------------------------------
>
> Key: WFLY-794
> URL: https://issues.jboss.org/browse/WFLY-794
> Project: WildFly
> Issue Type: Bug
> Components: JMX
> Reporter: Alex Corvino
> Assignee: Bartosz Baranowski
> Attachments: jmx-test.jar, JmxClient.java, JMXConnectionBean.java, JmxServer.java
>
>
> When trying to create a MBeanServerConnection to a NON-JBoss application from within an EJB a "javax.naming.NameNotFoundException" is thrown.
> Steps to reproduce:
> Set up a stand-alone application that exposes an MBean. (ActiveMQ will work in this case.)
> Modify the attached JMXConnectionBean.java to connect to the ActiveMQ instance.
> Deploy the bean. A NameNotFoundException will be thrown.
> I've seen this behavior in 7.1.1.Final, 7.1.2.Final (EAP), 7.1.3.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final).
> Note that this behavior is NOT seen when connecting to another JBoss server.
> Full stack trace:
> {code}
> Caused by: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.NameNotFoundException: rmi://127.0.0.1:1090/jmxrmi -- service jboss.naming.context.java.rmi:."127.0.0.1:1090".jmxrmi
> at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:340) [:1.6.0_26]
> at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) [:1.6.0_26]
> at com.example.JMXConnectionBean.init(JMXConnectionBean.java:28)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_26]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_26]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_26]
> at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_26]
> at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptor.java:70)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.as.ee.component.ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptor.java:53)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:44)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.as.ejb3.component.session.SessionInvocationContextInterceptor$CustomSessionInvocationContext.proceed(SessionInvocationContextInterceptor.java:126)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:211)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:313)
> at org.jboss.as.ejb3.tx.SingletonLifecycleCMTTxInterceptor.processInvocation(SingletonLifecycleCMTTxInterceptor.java:56)
> at org.jboss.as.ejb3.tx.SingletonLifecycleCMTTxInterceptor.processInvocation(SingletonLifecycleCMTTxInterceptor.java:42)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.as.ejb3.component.session.SessionInvocationContextInterceptor.processInvocation(SessionInvocationContextInterceptor.java:71)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:152)
> ... 9 more
> Caused by: javax.naming.NameNotFoundException: rmi://127.0.0.1:1090/jmxrmi -- service jboss.naming.context.java.rmi:."127.0.0.1:1090".jmxrmi
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173)
> at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:209)
> at javax.naming.InitialContext.lookup(InitialContext.java:392) [:1.6.0_26]
> at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1888) [:1.6.0_26]
> at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1858) [:1.6.0_26]
> at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:257) [:1.6.0_26]
> ... 37 more
> {code}
--
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
13 years, 2 months
[JBoss JIRA] (WFLY-1309) CLI: creating a server on a domain slave followed by setting a system property fails when done in batch mode
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-1309?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-1309:
----------------------------------------
Tom, can you attach the config files you are using? If you're starting with the standard domain.xml, don't bother to attach, but I'd like to see all host.xml files.
> CLI: creating a server on a domain slave followed by setting a system property fails when done in batch mode
> ------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-1309
> URL: https://issues.jboss.org/browse/WFLY-1309
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 8.0.0.Alpha1
> Environment: wildfly build from a git clone on 2013-05-02
> Reporter: Tom Fonteyne
> Assignee: Brian Stansberry
>
> Setup two boxes:
> - on one, run domain mode (full-ha) -> domain controller
> - on the other, configure host.xml to point to the DC, and run the host controller
> Now in CLI:
> # add the group:
> /server-group=slaves:add(profile=full-ha,socket-binding-group=full-ha-sockets)
> # create server and set a prop
> batch
> /host=slave1/server-config=i1:add(group=slaves,auto-start=false)
> /host=slave1/server-config=i1/system-property=env:add(value=dev)
> run-batch
> results in:
> JBAS010839: Operation failed or was rolled back on all servers.
> Debugging (on EAP 6.0.1) showed the real reason:
> activeStep.response = (org.jboss.dmr.ModelNode) {
> "outcome" => "failed",
> "failure-description" => "JBAS010850: No handler for operation
> composite at address [
> (\"host\" => \"slave1\"),
> (\"server\" => \"test\")
> ]",
> "rolled-back" => true
> }
> More debugging led to :
> org.jboss.as.controller.AbstractOperationContext
> seems to be where the rollback is set. When debugging, I found that the constructor always sets
> ModelController.OperationTransactionControl transactionControl
> but at line 332 (eap 6.0.1) / line 372 (wildfly), the end of doCompleteStep() :
> // Allow any containing TransactionControl to vote
> final AtomicReference<ResultAction> ref = new AtomicReference<ResultAction>(transactionControl == null ? ResultAction.KEEP : ResultAction.ROLLBACK);
> and ref becomes a rollback.
> I "walked" pretty much of all the code going on in between. The bit where the config is getting persisted is successful.
> But I'm afraid I'm out of my depth as there is *a lot* going on to execute such a composite command :)
--
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
13 years, 2 months
[JBoss JIRA] (WFLY-406) Redesign web session clustering
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-406?page=com.atlassian.jira.plugin.s... ]
Paul Ferraro updated WFLY-406:
------------------------------
Fix Version/s: 8.0.0.Alpha2
(was: 8.0.0.Alpha1)
> Redesign web session clustering
> -------------------------------
>
> Key: WFLY-406
> URL: https://issues.jboss.org/browse/WFLY-406
> Project: WildFly
> Issue Type: Task
> Components: Clustering
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 8.0.0.Alpha2
>
>
> The current web session replication code has been around for ages and suffers from a number of issues:
> * By maintaining a separate local map of sessions in conjunction with the session data stored in the distributed cache, stale data is inevitable - an number of issues have cropped up in EAP testing.
> * Extra concurrency measures are required to ensure synchronicity of the local session map with the distributed cache.
> * Extra logic/locking is required to invalidate the local session map is required per request
> * AtomicMaps, on which the currently implementation relies, have proven buggy
> * Session access outside of the scope of the replication valve is possible and problematic
> * Maintaining sessions locally means that the clustering code needs to implement passivation and expiration manually - instead of leveraging Infinispan full capabilities.
> * The current code base is tightly coupled to JBoss Web. Migrating the code to support Undertow will inevitably introduce issues and code duplication.
> The new design will incorporate a proper SPI for the servlet container. Thus the logic to integrate with Undertow vs JBoss Web will be relatively thin.
--
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
13 years, 2 months
[JBoss JIRA] (JBJCA-1027) Resources referenced from classloader not released
by Jesper Pedersen (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1027?page=com.atlassian.jira.plugin... ]
Jesper Pedersen updated JBJCA-1027:
-----------------------------------
Summary: Resources referenced from classloader not released (was: com.github.fungal.impl.KernelImpl.recursiveDelete cannot delete temporary jar file on Windows)
Fix Version/s: 1.1.0.Beta5
Component/s: Deployer
Validator
(was: Fungal)
> Resources referenced from classloader not released
> --------------------------------------------------
>
> Key: JBJCA-1027
> URL: https://issues.jboss.org/browse/JBJCA-1027
> Project: IronJacamar
> Issue Type: Bug
> Components: Deployer, Validator
> Affects Versions: 1.0.16.Final, 1.1.0.Beta4
> Environment: Windows 7; Windows 2008 Server
> Reporter: Gytis Trikleris
> Assignee: Jesper Pedersen
> Fix For: 1.1.0.Beta5
>
>
> {code}
> -------------------------------------------------------------------------------
> Test set: org.jboss.narayana.quickstart.jca.model.CustomerDAOTest
> -------------------------------------------------------------------------------
> Tests run: 10, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.32 sec <<< FAILURE!
> org.jboss.narayana.quickstart.jca.model.CustomerDAOTest Time elapsed: 0.063 sec <<< ERROR!
> java.io.IOException: Could not delete C:\Users\hudson\AppData\Local\Temp\2\iron.jacamar\tmp\jdbc-xa.rar\ironjacamar-jdbc.jar
> at com.github.fungal.impl.KernelImpl.recursiveDelete(KernelImpl.java:1520)
> at com.github.fungal.impl.KernelImpl.recursiveDelete(KernelImpl.java:1515)
> at com.github.fungal.impl.KernelImpl.recursiveDelete(KernelImpl.java:1515)
> at com.github.fungal.impl.KernelImpl.shutdown(KernelImpl.java:850)
> at org.jboss.jca.embedded.EmbeddedJCA.shutdown(EmbeddedJCA.java:158)
> at org.jboss.narayana.quickstart.jca.common.AbstractTest.afterClass(AbstractTest.java:61)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:36)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:35)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:146)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:97)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
> at $Proxy0.invoke(Unknown Source)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:145)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:87)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)
> {code}
> It works fine on Linux. However, it fails on both Windows 7 and Windows 2008 server.
> This simple test class also fails during shutdown with the same error:
> {code}
> public class SimpleTest {
> private static final String JDBC_RAR_FILE_PATH = "src/main/resources/jdbc-xa.rar";
> private static Embedded EMBEDDED;
> @Test
> public void test() throws Throwable {
> EMBEDDED = EmbeddedFactory.create();
> EMBEDDED.startup();
> EMBEDDED.deploy(getURL(JDBC_RAR_FILE_PATH));
> System.out.println("Test...");
> EMBEDDED.undeploy(getURL(JDBC_RAR_FILE_PATH));
> EMBEDDED.shutdown();
> }
> private static URL getURL(final String path) throws MalformedURLException {
> final File f = new File(path);
> return f.toURI().toURL();
> }
> }
> {code}
--
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
13 years, 2 months
[JBoss JIRA] (WFLY-1303) metadata-complete="true" not honored for ServletContainerInitializer's annotated with @HandlesTypes
by Aaron Whiteside (JIRA)
[ https://issues.jboss.org/browse/WFLY-1303?page=com.atlassian.jira.plugin.... ]
Aaron Whiteside edited comment on WFLY-1303 at 5/2/13 11:16 AM:
----------------------------------------------------------------
What about Servlet 3.0 and 2.5? If the web.xml specifies one of those versions, how should the container behave? If the container supports 3.1 does that mean it does not support 3.0 or 2.5 in regard to compatibility? If I deploy this on a 2.5 servlet container I wouldn't see the same error?
was (Author: Aaron.Whiteside):
What about Servlet 3.0 and 2.5? If the web.xml specifies one of those versions, how should the container behavior? If the container supports 3.1 does that mean it does not support 3.0 or 2.5 in regard to compatibility? If I deploy this on a 2.5 servlet container I wouldn't see the same error?
> metadata-complete="true" not honored for ServletContainerInitializer's annotated with @HandlesTypes
> ---------------------------------------------------------------------------------------------------
>
> Key: WFLY-1303
> URL: https://issues.jboss.org/browse/WFLY-1303
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Alpha1
> Reporter: Aaron Whiteside
> Assignee: Tomaz Cerar
>
> metadata-complete="true" not honored for ServletContainerInitializer's annotated with @HandlesTypes
> web.xml:
> {code}
> <?xml version="1.0" encoding="UTF-8"?>
> <web-app xmlns="http://java.sun.com/xml/ns/javaee"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd"
> version="3.0"
> metadata-complete="true">
> <listener>
> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
> </listener>
> <context-param>
> <param-name>contextConfigLocation</param-name>
> <param-value>WEB-INF/spring/root-context.xml</param-value>
> </context-param>
> </web-app>
> {code}
> Server.log output when deploying a war that contains the lib jersey-container-servlet-2.0-rc1.jar.
> {code}
> awhiteside@localhost jboss-as-8.0.0.Alpha1-SNAPSHOT# ./bin/standalone.sh
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /home/awhiteside/Downloads/jboss-as-8.0.0.Alpha1-SNAPSHOT
> JAVA: /usr/local/java/bin/java
> JAVA_OPTS: -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 19:20:03,372 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final
> 19:20:03,516 INFO [org.jboss.msc] (main) JBoss MSC version 1.1.2.Final
> 19:20:03,567 INFO [org.jboss.as] (MSC service thread 1-7) JBAS015899: JBoss AS 8.0.0.Alpha1-SNAPSHOT "TBD" starting
> 19:20:04,293 INFO [org.xnio] (MSC service thread 1-4) XNIO Version 3.1.0.CR2
> 19:20:04,296 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
> 19:20:04,297 INFO [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.1.0.CR2
> 19:20:04,311 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 3.2.16.GA
> 19:20:04,354 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
> 19:20:04,357 INFO [org.jboss.as.connector.logging] (MSC service thread 1-6) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.16.Final)
> 19:20:04,385 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 37) JBAS012605: Activated the following JSF Implementations: [main]
> 19:20:04,389 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 39) JBAS011800: Activating Naming Subsystem
> 19:20:04,398 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013171: Activating Security Subsystem
> 19:20:04,405 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 26) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
> 19:20:04,413 INFO [org.jboss.as.undertow] (MSC service thread 1-8) JBAS017502: Undertow 1.0.0.Alpha9 starting
> 19:20:04,414 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) JBAS010417: Started Driver service with driver-name = h2
> 19:20:04,428 INFO [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service
> 19:20:04,430 INFO [org.jboss.as.security] (MSC service thread 1-3) JBAS013170: Current PicketBox version=4.0.16.Final
> 19:20:04,436 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
> 19:20:04,439 INFO [org.jboss.as.undertow] (ServerService Thread Pool -- 47) JBAS017502: Undertow 1.0.0.Alpha9 starting
> 19:20:04,440 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mail/Default]
> 19:20:04,581 INFO [io.undertow] (ServerService Thread Pool -- 47) Creating file handler for path /home/awhiteside/Downloads/jboss-as-8.0.0.Alpha1-SNAPSHOT/welcome-content
> 19:20:04,611 INFO [org.jboss.as.undertow] (MSC service thread 1-1) Starting server server service: service jboss.undertow.server.default-server
> 19:20:04,619 INFO [org.jboss.as.undertow] (MSC service thread 1-3) Starting host default-host
> 19:20:04,619 INFO [org.jboss.as.undertow] (MSC service thread 1-3) registering handler io.undertow.server.handlers.resource.ResourceHandler@4155a5c7 under path '/'
> 19:20:04,624 INFO [org.jboss.ws.common.management] (MSC service thread 1-5) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.2.0.Alpha1
> 19:20:04,692 INFO [org.jboss.as.undertow] (MSC service thread 1-1) JBAS017519: Undertow HTTP listener default listening on /127.0.0.1:8080
> 19:20:04,815 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on 127.0.0.1:9999
> 19:20:04,815 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 127.0.0.1:4447
> 19:20:04,825 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /home/awhiteside/Downloads/jboss-as-8.0.0.Alpha1-SNAPSHOT/standalone/deployments
> 19:20:04,831 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "hawtio.war" (runtime-name: "hawtio.war")
> 19:20:04,850 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
> 19:20:05,466 INFO [io.undertow.servlet] (MSC service thread 1-1) jolokia-agent: Using access restrictor classpath:/jolokia-access.xml
> 19:20:05,520 INFO [org.jboss.as.undertow] (MSC service thread 1-1) JBAS018210: Register web context: /hawtio
> 19:20:05,547 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) JBAS018559: Deployed "hawtio.war" (runtime-name : "hawtio.war")
> 19:20:05,627 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
> 19:20:05,627 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
> 19:20:05,627 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 8.0.0.Alpha1-SNAPSHOT "TBD" started in 2545ms - Started 198 of 234 services (55 services are lazy, passive or on-demand)
> 19:20:15,567 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "messaging-gateway.war" (runtime-name: "messaging-gateway.war")
> 19:20:17,769 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry jaxb-api.jar in /content/messaging-gateway.war/WEB-INF/lib/jaxb-impl-2.2.6.jar does not point to a valid jar for a Class-Path reference.
> 19:20:17,770 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry webservices-api.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 19:20:17,771 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry webservices-extra.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 19:20:17,771 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry webservices-rt_l10n.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 19:20:17,771 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry webservices-rt_ja.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 19:20:17,772 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry webservices-rt_zh.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 19:20:17,772 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry webservices-rt_fr.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 19:20:17,772 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry webservices-rt_de.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 19:20:17,772 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry webservices-rt_es.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 19:20:17,773 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry webservices-rt_it.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 19:20:17,773 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry webservices-rt_sw.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 19:20:17,773 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry webservices-rt_ko.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 19:20:17,773 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry webservices-rt_zh_TW.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 19:20:17,777 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry webservices-rt.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-tools-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 19:20:17,806 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015893: Encountered invalid class name 'org.kxml2.io.KXmlParser,org.kxml2.io.KXmlSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory'
> 19:20:17,810 INFO [org.jboss.as.pojo] (MSC service thread 1-3) JBAS017000: Found legacy bean/pojo namespace: urn:jboss:bean-deployer:2.0 - might be missing some xml features (potential exceptions).
> 19:20:17,936 WARN [org.jboss.as.ee] (MSC service thread 1-4) JBAS011006: Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to exception: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011054: Could not find default constructor for class org.springframework.web.context.request.async.StandardServletAsyncWebRequest
> at org.jboss.as.ee.component.DefaultInterceptorConfigurator.configure(DefaultInterceptorConfigurator.java:93) [jboss-as-ee-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:80) [jboss-as-ee-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
> 19:20:17,942 WARN [org.jboss.as.ee] (MSC service thread 1-4) JBAS011006: Not installing optional component org.eclipse.jetty.server.handler.StatisticsHandler$1 due to exception: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011054: Could not find default constructor for class org.eclipse.jetty.server.handler.StatisticsHandler$1
> at org.jboss.as.ee.component.DefaultInterceptorConfigurator.configure(DefaultInterceptorConfigurator.java:93) [jboss-as-ee-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:80) [jboss-as-ee-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
> 19:20:17,944 WARN [org.jboss.as.ee] (MSC service thread 1-4) JBAS011006: Not installing optional component com.sun.xml.ws.transport.http.servlet.WSAsyncListener$1 due to exception: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011054: Could not find default constructor for class com.sun.xml.ws.transport.http.servlet.WSAsyncListener$1
> at org.jboss.as.ee.component.DefaultInterceptorConfigurator.configure(DefaultInterceptorConfigurator.java:93) [jboss-as-ee-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:80) [jboss-as-ee-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
> 19:20:17,972 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.undertow.deployment.default-host./messaging-gateway: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./messaging-gateway: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1930) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
> Caused by: java.lang.RuntimeException: java.lang.NullPointerException
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:176)
> at org.jboss.as.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:129)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
> ... 3 more
> Caused by: java.lang.NullPointerException
> at io.undertow.servlet.spec.ServletRegistrationImpl.getClassName(ServletRegistrationImpl.java:152)
> at org.glassfish.jersey.servlet.init.JerseyServletContainerInitializer.addServletWithExistingRegistration(JerseyServletContainerInitializer.java:222)
> at org.glassfish.jersey.servlet.init.JerseyServletContainerInitializer.onStartup(JerseyServletContainerInitializer.java:136)
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:153)
> ... 6 more
> 19:20:17,987 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS015870: Deploy of deployment "messaging-gateway.war" was rolled back with the following failure message:
> {"JBAS014671: Failed services" => {"jboss.undertow.deployment.default-host./messaging-gateway" => "org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./messaging-gateway: Failed to start service
> Caused by: java.lang.RuntimeException: java.lang.NullPointerException
> Caused by: java.lang.NullPointerException"}}
> 19:20:18,035 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015877: Stopped deployment messaging-gateway.war (runtime-name: messaging-gateway.war) in 48ms
> 19:20:18,037 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.deployment.unit."messaging-gateway.war".component."javax.faces.webapp.FacetTag".START (missing) dependents: [service jboss.deployment.unit."messaging-gateway.war".deploymentCompleteService]
> service jboss.deployment.unit."messaging-gateway.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (missing) dependents: [service jboss.deployment.unit."messaging-gateway.war".deploymentCompleteService]
> JBAS014777: Services which failed to start: service jboss.undertow.deployment.default-host./messaging-gateway
> {code}
> jboss-deployment-structure.xml
> {code}
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
> <deployment>
> <exclude-subsystems>
> <subsystem name="jaxrs"/>
> <subsystem name="webservices"/>
> </exclude-subsystems>
> <exclusions>
> <module name="org.slf4j"/>
> <module name="org.slf4j.impl"/>
> <module name="org.slf4j.ext"/>
> <module name="org.slf4j.jcl-over-slf4j"/>
> <module name="org.apache.commons.logging"/>
> <module name="org.apache.log4j"/>
> <!--<module name="org.hibernate"/>-->
> </exclusions>
> </deployment>
> </jboss-deployment-structure>
> {code}
> The class in question it is trying to instantiate..
> {code}
> package org.glassfish.jersey.servlet.init;
> ...
> @HandlesTypes({Path.class, Provider.class, Application.class, ApplicationPath.class})
> public class JerseyServletContainerInitializer implements ServletContainerInitializer {
> .....
> {code}
--
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
13 years, 2 months