[JBoss JIRA] Created: (JBLOGGING-58) Support setting the logging provider explicitly
by Dan Allen (JIRA)
Support setting the logging provider explicitly
-----------------------------------------------
Key: JBLOGGING-58
URL: https://issues.jboss.org/browse/JBLOGGING-58
Project: JBoss Logging
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 3.0.0.Beta4-jboss-logging
Reporter: Dan Allen
Assignee: David Lloyd
Priority: Minor
Fix For: 3.0.0.Beta5-jboss-logging
Currently, JBoss Logging uses a classloading approach to look for a logging provider based on a hardcoded order of precedence. While this is sufficient for the default case, there should be a way to specify the logger explicitly, in the case that there is more than one concrete logging implementation on the classpath.
The override should be part of the API, though a system property could also be supported. The API would take precedence.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] Created: (JBAS-9447) 'logout' on custom authentication module never called
by Thomas Woelfle (JIRA)
'logout' on custom authentication module never called
-----------------------------------------------------
Key: JBAS-9447
URL: https://issues.jboss.org/browse/JBAS-9447
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 6.1.0
Environment: JBoss 6.1.0, Java 1.6.0_26
Reporter: Thomas Woelfle
Hi there,
I have a custom authentication module that extends the JBoss DatabaseServerLoginModule (org.jboss.security.auth.spi.DatabaseServerLoginModule) that provides stuff like counting failed logins, disabling accounts, .... When loging in from a remote desktop client using LoginContext.login() the 'login' method of my custom authentication module is called. This works fine. But when loging out using LoginContext.logout() the 'logout' method of my authentication module is never called.
This seems to be a bug, isn't it?
Regards,
Thomas
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] Created: (AS7-1750) Invocation batching not enabled errors when using DIST mode for web sessions
by Paul Ferraro (JIRA)
Invocation batching not enabled errors when using DIST mode for web sessions
----------------------------------------------------------------------------
Key: AS7-1750
URL: https://issues.jboss.org/browse/AS7-1750
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Affects Versions: 7.0.1.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Fix For: 7.0.2.Final, 7.1.0.Alpha1
This is a regression caused by a change to DefaultEmbeddedCacheManager, where calls to getCache(...) for a non-existent cache result in the cache being based on the CacheContainer.DEFAULT_CACHE, not the default-cache.
11:25:20,945 WARN [org.jboss.as.clustering.web.infinispan.DistributedCacheManager] (notification-thread-0) Invocation batching not enabled in current configuration! Please use the <invocationBatching /> element.: org.infinispan.config.ConfigurationException: Invocation batching not enabled in current configuration! Please use the <invocationBatching /> element.
at org.infinispan.CacheImpl.startBatch(CacheImpl.java:433) [infinispan-core-5.0.0.FINAL.jar:5.0.0.FINAL]
at org.infinispan.AbstractDelegatingCache.startBatch(AbstractDelegatingCache.java:66) [infinispan-core-5.0.0.FINAL.jar:5.0.0.FINAL]
at org.jboss.as.clustering.web.infinispan.DistributedCacheManager$JvmRouteHandler.batch(DistributedCacheManager.java:618)
at org.jboss.as.clustering.web.infinispan.DistributedCacheManager$JvmRouteHandler.viewChanged(DistributedCacheManager.java:666)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_23]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [:1.6.0_23]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [:1.6.0_23]
at java.lang.reflect.Method.invoke(Method.java:616) [:1.6.0_23]
at org.infinispan.notifications.AbstractListenerImpl$ListenerInvocation$1.run(AbstractListenerImpl.java:200) [infinispan-core-5.0.0.FINAL.jar:5.0.0.FINAL]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_23]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_23]
at java.lang.Thread.run(Thread.java:679) [:1.6.0_23]
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] Created: (AS7-872) Log4J bundle fails to install due to javax.servlet imports
by David Bosschaert (JIRA)
Log4J bundle fails to install due to javax.servlet imports
----------------------------------------------------------
Key: AS7-872
URL: https://issues.jboss.org/browse/AS7-872
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: 7.0.0.CR1
Reporter: David Bosschaert
The following bundle is quite commonly used: http://ebr.springsource.com/repository/app/bundle/version/detail?name=com...
It's the springsource osgi-ified version of Log4J version 1.2.15
It installs without problems in Felix and Equinox but when installing it in AS7 it fails on a mandatory import of javax.swing?
There's a few things fishy about this:
1. why does the log bundle have this mandatory dependency? That probably a bug in the bundle, but anyway.
2. is the framework required to export javax.swing?
I always thought it wasn't but then on the other hand it works with Felix and Equinox, so it should work with us too... Especially such a common bundle should install smoothly IMHO.
{code}12:15:09,520 ERROR [org.jboss.osgi.framework.internal.AbstractBundleState] (MSC service thread 1-4) Could not resolve bundle: com.springsource.org.apache.log4j:1.2.15: org.osgi.framework.BundleException: Cannot resolve bundle resModule: [com.springsource.org.apache.log4j:1.2.15]
at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:157)
at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551)
at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:185)
at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:489)
at org.jboss.as.osgi.deployment.BundleStartTracker$1.processService(BundleStartTracker.java:135)
at org.jboss.as.osgi.deployment.BundleStartTracker$1.serviceStarted(BundleStartTracker.java:107)
at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1322) [jboss-msc-1.0.0.Beta8.jar:1.0.0.Beta8]
at org.jboss.msc.service.ServiceControllerImpl.access$2600(ServiceControllerImpl.java:47) [jboss-msc-1.0.0.Beta8.jar:1.0.0.Beta8]
at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1850) [jboss-msc-1.0.0.Beta8.jar:1.0.0.Beta8]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_23]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_23]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_23]
Caused by: org.jboss.osgi.resolver.XResolverException: Unable to resolve Module[com.springsource.org.apache.log4j:1.2.15]: missing requirement [Module[com.springsource.org.apache.log4j:1.2.15]] package; (package=javax.swing)
at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:117)
at org.jboss.osgi.resolver.spi.AbstractResolver.resolve(AbstractResolver.java:148)
at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:155)
... 11 more{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] Created: (JBWEB-202) Jboss acceptCount parameter works incorrectly
by Dmitry Murashenkov (JIRA)
Jboss acceptCount parameter works incorrectly
---------------------------------------------
Key: JBWEB-202
URL: https://issues.jboss.org/browse/JBWEB-202
Project: JBoss Web
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Tomcat
Affects Versions: JBossWeb-7.0.0.Beta11
Environment: APR connector is enabled (but seems that same bug is reproduced without it)
Reporter: Dmitry Murashenkov
Assignee: Remy Maucherat
We've found behavior of acceptCount property quite unexpected in JBoss 6. Seems that code is same in the latest repository revision.
TC is very simple:
1. Set connector properties:
<Connector ...
maxThreads="1"
acceptCount="100"/>
2. Send several http requests (few will be enough - 4-5 requests) to server in parallel. We performed load testing when found this bug, so we just started the load client which tried to make several connections and send a single request through each.
Expected result: all requests get handled within some time (because acceptCount is quite high - far bigger than the number of requests)
Actual result: several requests receive "Connection reset by peer"
The actual problem seems to be in AprEndpoint$Acceptor.run():
if (!processSocketWithOptions(socket)) {
Socket.destroy(socket);
}
Method processSocketWithOptions() invokes getWorkerThread() which returns null if no thread is available (at least by default - in LOW_MEMORY setting is not set) and so the socket is destroyed even though acceptCount number of incoming connections is not reached.
Of course formally connection is accepted in the first place and only then is closed, but actual outcome of this case is that connection is closed and cannot be used which is quite unexpected.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] Created: (AS7-1715) Transaction regression due to Hibernate upgrade
by Nicklas Karlsson (JIRA)
Transaction regression due to Hibernate upgrade
-----------------------------------------------
Key: AS7-1715
URL: https://issues.jboss.org/browse/AS7-1715
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.0.Beta1
Reporter: Nicklas Karlsson
Assignee: Scott Marlow
My application that was working in 7.0.1.Final breaks on upstream master. Downgrading the hibernate modules fixes things again. The stack is
09:48:36,363 ERROR [stderr] (http--127.0.0.1-80-1) javax.transaction.SystemException: IJ000356: Failed to enlist: java.lang.Throwable: Unabled to enlist resource, see the previous warnings. tx=TransactionImple < ac, BasicAction: 0:ffffa9fe144d:-5df39d87:4e64707d:c status: ActionStatus.ABORT_ONLY >
09:48:36,364 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.jca.core.connectionmanager.listener.TxConnectionListener$TransactionSynchronization.checkEnlisted(TxConnectionListener.java:552)
09:48:36,365 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.jca.core.connectionmanager.listener.TxConnectionListener.enlist(TxConnectionListener.java:282)
09:48:36,366 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.managedConnectionReconnected(TxConnectionManagerImpl.java:423)
09:48:36,367 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.reconnectManagedConnection(AbstractConnectionManager.java:602)
09:48:36,368 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:470)
09:48:36,368 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:129)
09:48:36,369 ERROR [stderr] (http--127.0.0.1-80-1) at org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider.getConnection(InjectedDataSourceConnectionProvider.java:67)
09:48:36,370 ERROR [stderr] (http--127.0.0.1-80-1) at org.hibernate.internal.AbstractSessionImpl$NonContextualJdbcConnectionAccess.obtainConnection(AbstractSessionImpl.java:276)
09:48:36,370 ERROR [stderr] (http--127.0.0.1-80-1) at org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.obtainConnection(LogicalConnectionImpl.java:296)
09:48:36,371 ERROR [stderr] (http--127.0.0.1-80-1) at org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.getConnection(LogicalConnectionImpl.java:168)
09:48:36,372 ERROR [stderr] (http--127.0.0.1-80-1) at org.hibernate.engine.jdbc.internal.proxy.ConnectionProxyHandler.extractPhysicalConnection(ConnectionProxyHandler.java:81)
09:48:36,373 ERROR [stderr] (http--127.0.0.1-80-1) at org.hibernate.engine.jdbc.internal.proxy.ConnectionProxyHandler.continueInvocation(ConnectionProxyHandler.java:137)
09:48:36,373 ERROR [stderr] (http--127.0.0.1-80-1) at org.hibernate.engine.jdbc.internal.proxy.AbstractProxyHandler.invoke(AbstractProxyHandler.java:80)
09:48:36,374 ERROR [stderr] (http--127.0.0.1-80-1) at $Proxy275.prepareStatement(Unknown Source)
09:48:36,375 ERROR [stderr] (http--127.0.0.1-80-1) at org.hibernate.engine.jdbc.internal.StatementPreparerImpl$5.doPrepare(StatementPreparerImpl.java:149)
09:48:36,375 ERROR [stderr] (http--127.0.0.1-80-1) at org.hibernate.engine.jdbc.internal.StatementPreparerImpl$StatementPreparationTemplate.prepareStatement(StatementPreparerImpl.java:178)
09:48:36,376 ERROR [stderr] (http--127.0.0.1-80-1) at org.hibernate.engine.jdbc.internal.StatementPreparerImpl.prepareQueryStatement(StatementPreparerImpl.java:147)
09:48:36,377 ERROR [stderr] (http--127.0.0.1-80-1) at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1741)
09:48:36,377 ERROR [stderr] (http--127.0.0.1-80-1) at org.hibernate.loader.Loader.doQuery(Loader.java:828)
09:48:36,377 ERROR [stderr] (http--127.0.0.1-80-1) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:289)
09:48:36,378 ERROR [stderr] (http--127.0.0.1-80-1) at org.hibernate.loader.Loader.doList(Loader.java:2449)
09:48:36,378 ERROR [stderr] (http--127.0.0.1-80-1) at org.hibernate.loader.Loader.doList(Loader.java:2435)
09:48:36,379 ERROR [stderr] (http--127.0.0.1-80-1) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2276)
09:48:36,379 ERROR [stderr] (http--127.0.0.1-80-1) at org.hibernate.loader.Loader.list(Loader.java:2271)
09:48:36,380 ERROR [stderr] (http--127.0.0.1-80-1) at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:470)
09:48:36,380 ERROR [stderr] (http--127.0.0.1-80-1) at org.hibernate.hql.internal.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:355)
09:48:36,381 ERROR [stderr] (http--127.0.0.1-80-1) at org.hibernate.engine.query.spi.HQLQueryPlan.performList(HQLQueryPlan.java:196)
09:48:36,381 ERROR [stderr] (http--127.0.0.1-80-1) at org.hibernate.internal.SessionImpl.list(SessionImpl.java:1116)
09:48:36,386 ERROR [stderr] (http--127.0.0.1-80-1) at org.hibernate.internal.QueryImpl.list(QueryImpl.java:100)
09:48:36,386 ERROR [stderr] (http--127.0.0.1-80-1) at org.hibernate.ejb.QueryImpl.getResultList(QueryImpl.java:252)
09:48:36,387 ERROR [stderr] (http--127.0.0.1-80-1) at fi.affecto.osti.fwkint.seam.international.status.DBResourceLoader.haeSovellusmessut(DBResourceLoader.java:61)
09:48:36,387 ERROR [stderr] (http--127.0.0.1-80-1) at fi.affecto.osti.fwkint.seam.international.status.DBResourceLoader.loadMessageBundleFor(DBResourceLoader.java:44)
09:48:36,388 ERROR [stderr] (http--127.0.0.1-80-1) at fi.affecto.osti.fwkint.seam.international.status.1678347348$Proxy$_$$_WeldSubclass.loadMessageBundleFor(1678347348$Proxy$_$$_WeldSubclass.java)
09:48:36,389 ERROR [stderr] (http--127.0.0.1-80-1) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
09:48:36,419 ERROR [stderr] (http--127.0.0.1-80-1) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
09:48:36,420 ERROR [stderr] (http--127.0.0.1-80-1) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
09:48:36,421 ERROR [stderr] (http--127.0.0.1-80-1) at java.lang.reflect.Method.invoke(Method.java:601)
09:48:36,421 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.interceptor.proxy.SimpleInterceptionChain.invokeNextInterceptor(SimpleInterceptionChain.java:112)
09:48:36,422 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.interceptor.proxy.InterceptorInvocationContext.proceed(InterceptorInvocationContext.java:119)
09:48:36,423 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.seam.transaction.TransactionInterceptor$1.work(TransactionInterceptor.java:152)
09:48:36,450 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.seam.transaction.Work.workInTransaction(Work.java:49)
09:48:36,451 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.seam.transaction.TransactionInterceptor.aroundInvoke(TransactionInterceptor.java:148)
09:48:36,451 ERROR [stderr] (http--127.0.0.1-80-1) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
09:48:36,452 ERROR [stderr] (http--127.0.0.1-80-1) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
09:48:36,453 ERROR [stderr] (http--127.0.0.1-80-1) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
09:48:36,454 ERROR [stderr] (http--127.0.0.1-80-1) at java.lang.reflect.Method.invoke(Method.java:601)
09:48:36,454 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.interceptor.proxy.InterceptorInvocation$InterceptorMethodInvocation.invoke(InterceptorInvocation.java:72)
09:48:36,466 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.interceptor.proxy.SimpleInterceptionChain.invokeNextInterceptor(SimpleInterceptionChain.java:82)
09:48:36,466 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.interceptor.proxy.InterceptorInvocationContext.proceed(InterceptorInvocationContext.java:119)
09:48:36,467 ERROR [stderr] (http--127.0.0.1-80-1) at fi.affecto.osti.fwkint.seam.exception.ExceptionHandlerInterceptor.manage(ExceptionHandlerInterceptor.java:27)
09:48:36,468 ERROR [stderr] (http--127.0.0.1-80-1) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
09:48:36,469 ERROR [stderr] (http--127.0.0.1-80-1) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
09:48:36,496 ERROR [stderr] (http--127.0.0.1-80-1) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
09:48:36,496 ERROR [stderr] (http--127.0.0.1-80-1) at java.lang.reflect.Method.invoke(Method.java:601)
09:48:36,497 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.interceptor.proxy.InterceptorInvocation$InterceptorMethodInvocation.invoke(InterceptorInvocation.java:72)
09:48:36,498 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.interceptor.proxy.SimpleInterceptionChain.invokeNextInterceptor(SimpleInterceptionChain.java:82)
09:48:36,498 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:133)
09:48:36,525 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:112)
09:48:36,525 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:65)
09:48:36,526 ERROR [stderr] (http--127.0.0.1-80-1) at fi.affecto.osti.fwkint.seam.international.status.1678347348$Proxy$_$$_WeldSubclass.loadMessageBundleFor(1678347348$Proxy$_$$_WeldSubclass.java)
09:48:36,527 ERROR [stderr] (http--127.0.0.1-80-1) at fi.affecto.osti.fwkint.seam.international.status.DBBundleLoader.loadBundle(DBBundleLoader.java:30)
09:48:36,527 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.seam.international.status.ApplicationBundles.get(ApplicationBundles.java:84)
09:48:36,528 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.seam.international.status.ApplicationBundles$Proxy$_$$_WeldClientProxy.get(ApplicationBundles$Proxy$_$$_WeldClientProxy.java)
09:48:36,555 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.seam.international.status.Bundles.get(Bundles.java:77)
09:48:36,555 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.seam.international.status.Bundles$Proxy$_$$_WeldClientProxy.get(Bundles$Proxy$_$$_WeldClientProxy.java)
09:48:36,556 ERROR [stderr] (http--127.0.0.1-80-1) at fi.affecto.osti.fwkint.seam.international.status.HoputeProducer.getMessut(HoputeProducer.java:22)
09:48:36,557 ERROR [stderr] (http--127.0.0.1-80-1) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
09:48:36,557 ERROR [stderr] (http--127.0.0.1-80-1) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
09:48:36,558 ERROR [stderr] (http--127.0.0.1-80-1) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
09:48:36,616 ERROR [stderr] (http--127.0.0.1-80-1) at java.lang.reflect.Method.invoke(Method.java:601)
09:48:36,617 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305)
09:48:36,617 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54)
09:48:36,618 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163)
09:48:36,619 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299)
09:48:36,619 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188)
09:48:36,620 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstance(MethodInjectionPoint.java:169)
09:48:36,621 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.weld.bean.ProducerMethod$1.produce(ProducerMethod.java:149)
09:48:36,621 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.weld.bean.AbstractProducerBean.create(AbstractProducerBean.java:361)
09:48:36,622 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.weld.context.unbound.DependentContextImpl.get(DependentContextImpl.java:67)
09:48:36,623 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:700)
09:48:36,624 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.weld.el.AbstractWeldELResolver.lookup(AbstractWeldELResolver.java:152)
09:48:36,624 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.weld.el.AbstractWeldELResolver.getValue(AbstractWeldELResolver.java:112)
09:48:36,625 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.as.weld.webtier.jsf.ForwardingELResolver.getValue(ForwardingELResolver.java:46)
09:48:36,648 ERROR [stderr] (http--127.0.0.1-80-1) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:175)
09:48:36,649 ERROR [stderr] (http--127.0.0.1-80-1) at com.sun.faces.el.DemuxCompositeELResolver._getValue(DemuxCompositeELResolver.java:176)
09:48:36,650 ERROR [stderr] (http--127.0.0.1-80-1) at com.sun.faces.el.DemuxCompositeELResolver.getValue(DemuxCompositeELResolver.java:203)
09:48:36,650 ERROR [stderr] (http--127.0.0.1-80-1) at org.apache.el.parser.AstIdentifier.getValue(AstIdentifier.java:67)
09:48:36,651 ERROR [stderr] (http--127.0.0.1-80-1) at org.apache.el.parser.AstValue.getValue(AstValue.java:115)
09:48:36,652 ERROR [stderr] (http--127.0.0.1-80-1) at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:187)
09:48:36,653 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:55)
09:48:36,680 ERROR [stderr] (http--127.0.0.1-80-1) at com.sun.faces.facelets.el.ELText$ELTextVariable.writeText(ELText.java:224)
09:48:36,681 ERROR [stderr] (http--127.0.0.1-80-1) at com.sun.faces.facelets.compiler.TextInstruction.write(TextInstruction.java:85)
09:48:36,682 ERROR [stderr] (http--127.0.0.1-80-1) at com.sun.faces.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:82)
09:48:36,683 ERROR [stderr] (http--127.0.0.1-80-1) at com.sun.faces.facelets.compiler.UILeaf.encodeAll(UILeaf.java:183)
09:48:36,683 ERROR [stderr] (http--127.0.0.1-80-1) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1655)
09:48:36,684 ERROR [stderr] (http--127.0.0.1-80-1) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1655)
09:48:36,685 ERROR [stderr] (http--127.0.0.1-80-1) at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:399)
09:48:36,711 ERROR [stderr] (http--127.0.0.1-80-1) at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:131)
09:48:36,712 ERROR [stderr] (http--127.0.0.1-80-1) at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:273)
09:48:36,712 ERROR [stderr] (http--127.0.0.1-80-1) at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:273)
09:48:36,713 ERROR [stderr] (http--127.0.0.1-80-1) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:121)
09:48:36,714 ERROR [stderr] (http--127.0.0.1-80-1) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
09:48:36,714 ERROR [stderr] (http--127.0.0.1-80-1) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
09:48:36,743 ERROR [stderr] (http--127.0.0.1-80-1) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:313)
09:48:36,743 ERROR [stderr] (http--127.0.0.1-80-1) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
09:48:36,744 ERROR [stderr] (http--127.0.0.1-80-1) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
09:48:36,744 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67)
09:48:36,745 ERROR [stderr] (http--127.0.0.1-80-1) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
09:48:36,745 ERROR [stderr] (http--127.0.0.1-80-1) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
09:48:36,746 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.seam.servlet.exception.CatchExceptionFilter.doFilter(CatchExceptionFilter.java:65)
09:48:36,775 ERROR [stderr] (http--127.0.0.1-80-1) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
09:48:36,775 ERROR [stderr] (http--127.0.0.1-80-1) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
09:48:36,776 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.seam.servlet.event.ServletEventBridgeFilter.doFilter(ServletEventBridgeFilter.java:72)
09:48:36,777 ERROR [stderr] (http--127.0.0.1-80-1) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
09:48:36,777 ERROR [stderr] (http--127.0.0.1-80-1) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
09:48:36,778 ERROR [stderr] (http--127.0.0.1-80-1) at fi.affecto.osti.fwkint.servlet.RollbackFilter.doFilter(RollbackFilter.java:34)
09:48:36,778 ERROR [stderr] (http--127.0.0.1-80-1) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
09:48:36,807 ERROR [stderr] (http--127.0.0.1-80-1) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
09:48:36,808 ERROR [stderr] (http--127.0.0.1-80-1) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
09:48:36,808 ERROR [stderr] (http--127.0.0.1-80-1) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
09:48:36,809 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139)
09:48:36,810 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57)
09:48:36,810 ERROR [stderr] (http--127.0.0.1-80-1) at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49)
09:48:36,811 ERROR [stderr] (http--127.0.0.1-80-1) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154)
09:48:36,840 ERROR [stderr] (http--127.0.0.1-80-1) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
09:48:36,840 ERROR [stderr] (http--127.0.0.1-80-1) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
09:48:36,841 ERROR [stderr] (http--127.0.0.1-80-1) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362)
09:48:36,842 ERROR [stderr] (http--127.0.0.1-80-1) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
09:48:36,842 ERROR [stderr] (http--127.0.0.1-80-1) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667)
09:48:36,843 ERROR [stderr] (http--127.0.0.1-80-1) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952)
09:48:36,844 ERROR [stderr] (http--127.0.0.1-80-1) at java.lang.Thread.run(Thread.java:722)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] Created: (AS7-1260) JGroups subsystem fails to setup some protocol stacks.
by Trustin Lee (JIRA)
JGroups subsystem fails to setup some protocol stacks.
------------------------------------------------------
Key: AS7-1260
URL: https://issues.jboss.org/browse/AS7-1260
Project: Application Server 7
Issue Type: Bug
Reporter: Trustin Lee
Assignee: Paul Ferraro
Priority: Critical
After upgrading from AS 7.0.0.CR1 to AS 7.0.0.Final, I started to see an exception raised by org.jboss.as.clustering.jgroups.JChannelFactory:
{code}
22:11:54,040 ERROR [stderr] (MSC service thread 1-1) java.lang.IllegalArgumentException: org.jgroups.ChannelException: unable to setup the protocol stack
22:11:54,040 ERROR [stderr] (MSC service thread 1-1) at org.jboss.as.clustering.infinispan.ChannelProvider.getJGroupsChannel(ChannelProvider.java:71)
22:11:54,041 ERROR [stderr] (MSC service thread 1-1) at org.infinispan.remoting.transport.jgroups.JGroupsTransport.buildChannel(JGroupsTransport.java:273)
22:11:54,041 ERROR [stderr] (MSC service thread 1-1) at org.infinispan.remoting.transport.jgroups.JGroupsTransport.initChannel(JGroupsTransport.java:226)
22:11:54,041 ERROR [stderr] (MSC service thread 1-1) at org.infinispan.remoting.transport.jgroups.JGroupsTransport.initChannelAndRPCDispatcher(JGroupsTransport.java:254)
22:11:54,041 ERROR [stderr] (MSC service thread 1-1) at org.infinispan.remoting.transport.jgroups.JGroupsTransport.start(JGroupsTransport.java:148)
22:11:54,041 ERROR [stderr] (MSC service thread 1-1) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
22:11:54,041 ERROR [stderr] (MSC service thread 1-1) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
22:11:54,042 ERROR [stderr] (MSC service thread 1-1) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
22:11:54,042 ERROR [stderr] (MSC service thread 1-1) at java.lang.reflect.Method.invoke(Method.java:597)
22:11:54,042 ERROR [stderr] (MSC service thread 1-1) at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:172)
22:11:54,042 ERROR [stderr] (MSC service thread 1-1) at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:918)
22:11:54,042 ERROR [stderr] (MSC service thread 1-1) at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:711)
22:11:54,042 ERROR [stderr] (MSC service thread 1-1) at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:611)
22:11:54,043 ERROR [stderr] (MSC service thread 1-1) at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:176)
22:11:54,043 ERROR [stderr] (MSC service thread 1-1) at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:171)
22:11:54,043 ERROR [stderr] (MSC service thread 1-1) at org.infinispan.CacheImpl.start(CacheImpl.java:366)
22:11:54,043 ERROR [stderr] (MSC service thread 1-1) at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:559)
22:11:54,043 ERROR [stderr] (MSC service thread 1-1) at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:455)
22:11:54,043 ERROR [stderr] (MSC service thread 1-1) at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:479)
22:11:54,044 ERROR [stderr] (MSC service thread 1-1) at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:84)
22:11:54,044 ERROR [stderr] (MSC service thread 1-1) at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:73)
22:11:54,044 ERROR [stderr] (MSC service thread 1-1) at org.jboss.as.clustering.infinispan.subsystem.CacheService.start(CacheService.java:73)
22:11:54,044 ERROR [stderr] (MSC service thread 1-1) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
22:11:54,044 ERROR [stderr] (MSC service thread 1-1) at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
22:11:54,044 ERROR [stderr] (MSC service thread 1-1) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
22:11:54,045 ERROR [stderr] (MSC service thread 1-1) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
22:11:54,045 ERROR [stderr] (MSC service thread 1-1) at java.lang.Thread.run(Thread.java:680)
22:11:54,045 ERROR [stderr] (MSC service thread 1-1) Caused by: org.jgroups.ChannelException: unable to setup the protocol stack
22:11:54,045 ERROR [stderr] (MSC service thread 1-1) at org.jgroups.JChannel.init(JChannel.java:1728)
22:11:54,045 ERROR [stderr] (MSC service thread 1-1) at org.jgroups.JChannel.<init>(JChannel.java:249)
22:11:54,045 ERROR [stderr] (MSC service thread 1-1) at org.jboss.as.clustering.jgroups.JChannelFactory$JChannel.<init>(JChannelFactory.java:269)
22:11:54,046 ERROR [stderr] (MSC service thread 1-1) at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:69)
22:11:54,046 ERROR [stderr] (MSC service thread 1-1) at org.jboss.as.clustering.infinispan.ChannelProvider.getJGroupsChannel(ChannelProvider.java:67)
22:11:54,046 ERROR [stderr] (MSC service thread 1-1) ... 26 more
22:11:54,046 ERROR [stderr] (MSC service thread 1-1) Caused by: java.lang.IllegalArgumentException: the following properties in PING are not recognized: {bind_addr=192.168.0.196}
22:11:54,046 ERROR [stderr] (MSC service thread 1-1) at org.jgroups.stack.Configurator.createLayer(Configurator.java:460)
22:11:54,047 ERROR [stderr] (MSC service thread 1-1) at org.jgroups.stack.Configurator.createProtocols(Configurator.java:393)
22:11:54,047 ERROR [stderr] (MSC service thread 1-1) at org.jgroups.stack.Configurator.setupProtocolStack(Configurator.java:88)
22:11:54,047 ERROR [stderr] (MSC service thread 1-1) at org.jgroups.stack.Configurator.setupProtocolStack(Configurator.java:55)
22:11:54,047 ERROR [stderr] (MSC service thread 1-1) at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:534)
22:11:54,047 ERROR [stderr] (MSC service thread 1-1) at org.jgroups.JChannel.init(JChannel.java:1725)
22:11:54,047 ERROR [stderr] (MSC service thread 1-1) ... 30 more
{code}
(Actually, the exception was being swallowed by Infinispan, so I had to modify the source code in Infinispan.)
Reverting back only the JGroups subsystem to 7.0.0.CR1 fixes the problem. The offending subsystem configuration is:
{code}
<subsystem xmlns="urn:jboss:domain:jgroups:1.0" default-stack="udp">
<stack name="udp">
<transport type="UDP"
socket-binding="jgroups-udp"
default-executor="jgroups"
oob-executor="jgroups-oob"
timer-executor="jgroups-timer"/>
<protocol type="PING"/>
<protocol type="MERGE2"/>
<protocol type="FD_SOCK"/>
<protocol type="FD"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="BARRIER"/>
<protocol type="pbcast.NAKACK"/>
<protocol type="UNICAST"/>
<protocol type="pbcast.STABLE"/>
<protocol type="VIEW_SYNC"/>
<protocol type="pbcast.GMS"/>
<protocol type="UFC"/>
<protocol type="MFC"/>
<protocol type="FRAG2"/>
<protocol type="pbcast.STREAMING_STATE_TRANSFER"/>
<protocol type="pbcast.FLUSH"/>
</stack>
<stack name="tcp">
<transport type="TCP"
socket-binding="jgroups-tcp"
default-executor="jgroups"
oob-executor="jgroups-oob"
timer-executor="jgroups-timer"/>
<protocol type="MPING" socket-binding="jgroups-mping"/>
<protocol type="MERGE2"/>
<protocol type="FD_SOCK"/>
<protocol type="FD"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="BARRIER"/>
<protocol type="pbcast.NAKACK"/>
<protocol type="UNICAST"/>
<protocol type="pbcast.STABLE"/>
<protocol type="VIEW_SYNC"/>
<protocol type="pbcast.GMS"/>
<protocol type="UFC"/>
<protocol type="MFC"/>
<protocol type="FRAG2"/>
<protocol type="pbcast.STREAMING_STATE_TRANSFER"/>
<protocol type="pbcast.FLUSH"/>
</stack>
</subsystem>
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] Created: (AS7-772) Allow operation handlers to register child ModelNodeRegistrations
by Brian Stansberry (JIRA)
Allow operation handlers to register child ModelNodeRegistrations
-----------------------------------------------------------------
Key: AS7-772
URL: https://issues.jboss.org/browse/AS7-772
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 7.0.0.CR1
Handlers (specifically datasource add handlers) can sometimes add services whose management interface is not known until runtime. The context provided to handlers should provide a hook to allow them to register child ModelNodeRegistration objects, relative to the resource the handler is managing.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years