[JBoss JIRA] (AS7-3156) Cannot add clustered caches to a cache container started without a transport
by Tristan Tarrant (Created) (JIRA)
Cannot add clustered caches to a cache container started without a transport
----------------------------------------------------------------------------
Key: AS7-3156
URL: https://issues.jboss.org/browse/AS7-3156
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Affects Versions: 7.1.0.CR1b
Reporter: Tristan Tarrant
Assignee: Paul Ferraro
Fix For: 7.1.0.Final
Because a transport is bound to a cache container only if there are clustered caches in the initial configuration, adding a clustered cache to such a cache container will result in Infinispan complaining about not having a transport.
This can be solved by either always starting with a transport, or by making a distinction between local and clustered cache containers.
Furthermore, making a clustered cache EAGER within the configuration XML file (they are LAZY by default), will trigger this problem even on startup:
MSC00001: Failed to start service jboss.infinispan.sfsb.repl: org.jboss.msc.service.StartException in service jboss.infinispan.sfsb.repl: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1780) [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:662) [:1.6.0_29]
Caused by: org.infinispan.config.ConfigurationException: Cache cannot use a clustered mode (REPL_ASYNC) mode and not define a transport!
at org.infinispan.config.Configuration.assertValid(Configuration.java:1664)
at org.infinispan.manager.DefaultCacheManager.wireCache(DefaultCacheManager.java:683)
at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:645)
at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:541)
at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:555)
at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:118)
at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:109)
at org.jboss.as.clustering.infinispan.subsystem.CacheService.start(CacheService.java:80)
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]
... 3 more
--
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
12 years, 7 months
[JBoss JIRA] (AS7-2138) javax.naming.NameNotFoundException: rmi://127.0.0.1:1090/jmxrmi thrown when creating MBeanServerConnection
by Stian Thorgersen (Created) (JIRA)
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
Reporter: Stian Thorgersen
Attachments: jmx-test.jar, JMXConnectionBean.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.
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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (AS7-2536) CLI Configurability
by Vimal Kansal (Created) (JIRA)
CLI Configurability
-------------------
Key: AS7-2536
URL: https://issues.jboss.org/browse/AS7-2536
Project: Application Server 7
Issue Type: Feature Request
Components: CLI
Reporter: Vimal Kansal
Assignee: Alexey Loubyansky
+1 on the CLI config may ping you later in the week as we are getting
close to adding both SSL and Kerberos to Remoting so both may need some
static config to configure.
Regards,
Darran Lofthouse.
On 11/07/2011 01:32 PM, Alexey Loubyansky wrote:
> > No, it's not and deserves a jira.
> >
> > There should be a CLI config somewhere.
> > Besides the history file location and name, there should be the length
> > of the history which is 500 by default.
> > (Related to history 'history --clear' clears only the in-memory one but
> > doesn't touch the file, probably it should, to be consistent.)
> >
> > There are other things to store. Not sure yet whether they deserve a
> > separate file. E.g. rollout plans.
> >
> > Alexey
> >
> > On 11/07/2011 06:19 AM, Vimal Kansal wrote:
>> >> Hi,
>> >>
>> >> By default .jboss-cli-history file is created in home folder. I was
>> >> wondering if this is configurable?
>> >>
>> >> Thx
>> >>
>> >> Vimal
--
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
12 years, 7 months
[JBoss JIRA] Created: (AS7-1455) Log shows a parser error, but not the cause
by Heiko Rupp (JIRA)
Log shows a parser error, but not the cause
-------------------------------------------
Key: AS7-1455
URL: https://issues.jboss.org/browse/AS7-1455
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.0.0.Final
Reporter: Heiko Rupp
Assignee: Brian Stansberry
I see this from time to time:
13:20:50,933 ERROR [org.jboss.as.domain.http.api] (HttpManagementService-threads - 219) Unexpected error executing model request: java.io.IOException: Parser error
at org.jboss.dmr.ModelNode.fromJSONStream(ModelNode.java:1221)
at org.jboss.as.domain.http.server.DomainApiHandler.convertPostRequest(DomainApiHandler.java:323)
at org.jboss.as.domain.http.server.DomainApiHandler.processRequest(DomainApiHandler.java:187)
at org.jboss.as.domain.http.server.DomainApiHandler.handle(DomainApiHandler.java:123)
at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:82)
at org.jboss.sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:80)
at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:85)
at org.jboss.sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:606)
at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:82)
at org.jboss.sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:578)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_26]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
but can't fix what we send, as the error message does not tell
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] Created: (AS7-1561) <distributable> web applications fail to deploy with the DOMAIN HA configuration
by Riccardo Pasquini (JIRA)
<distributable> web applications fail to deploy with the DOMAIN HA configuration
--------------------------------------------------------------------------------
Key: AS7-1561
URL: https://issues.jboss.org/browse/AS7-1561
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: 7.0.0.Final, 7.1.0.Alpha1
Environment: riccardo@7suse:~> uname -a
Linux 7suse.localhost 2.6.37.6-0.7-desktop #1 SMP PREEMPT 2011-07-21 02:17:24 +0200 x86_64 x86_64 x86_64 GNU/Linux
riccardo@7suse:~> java -version
java version "1.6.0_26"
Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode)
Reporter: Riccardo Pasquini
Assignee: Remy Maucherat
Using the console to deploy a web application packaged as WAR and described as <distributable /> fails on enabling in the server group with the following message:
Failed to disable Webapp-0.1-SNAPSHOT.war.
Unexpected HTTP response: 500
Request
{
"address" => [
("server-group" => "dragon-standalone"),
("deployment" => "Webapp-0.1-SNAPSHOT.war")
],
"operation" => "deploy"
}
Response
Internal Server Error
{
"outcome" => "failed",
"result" => {"server-groups" => [("dragon-standalone" => {"master" => {
"host" => "master",
"response" => {
"outcome" => "failed",
"failure-description" => "Operation handler failed to complete",
"rolled-back" => true
}
}})]},
"failure-description" => "Operation failed or was rolled back on all servers.",
"rolled-back" => true
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (AS7-2929) Add support for unscheduled write-behind cache stores to Infinispan subsytem
by Martin Gencur (Created) (JIRA)
Add support for unscheduled write-behind cache stores to Infinispan subsytem
----------------------------------------------------------------------------
Key: AS7-2929
URL: https://issues.jboss.org/browse/AS7-2929
Project: Application Server 7
Issue Type: Feature Request
Components: Clustering
Reporter: Martin Gencur
Assignee: Tristan Tarrant
Infinispan subsystem should support unscheduled write-behind cache stores. Currently it is not possible to set this up.
In Infinispan this is done via <async> sub-element of <loader> element. E.g. <async enabled="true" threadPoolSize="10" />
Documentation for EDG is mentioning both unscheduled and scheduled write-behind cache stores even though scheduled one is not implemented even in Infinispan (ISPN-328). OTOH, the unscheduled one is implemented and should be available in EDG.
So take into account that in future there might be also scheduled write-behind store available and infinispan schema for JBossAS should count with that.
--
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
12 years, 7 months
[JBoss JIRA] Created: (AS7-1182) DatabaseServerLoginModule doesn't work
by Juergen Zimmermann (JIRA)
DatabaseServerLoginModule doesn't work
--------------------------------------
Key: AS7-1182
URL: https://issues.jboss.org/browse/AS7-1182
Project: Application Server 7
Issue Type: Bug
Components: Security
Affects Versions: 7.0.0.CR1
Reporter: Juergen Zimmermann
I want to migrate from JBossAS 6 to 7.0.0.CR1. In standalone.xml I declare the following security domain, but get the stacktrace (see below) looking for UsersRolesLoginModule instead of DatabaseServerLoginModule.
Security domain in standalone.xml:
<security-domain name="swe2" cache-type="default">
<authentication>
<login-module code="Database" flag="required">
<module-option name="dsJndiName" value="java:/swe2DS"/>
<module-option name="unauthenticatedIdentity" value="gast"/>
<module-option name="principalsQuery" value="SELECT password FROM kunde WHERE username=?"/>
<module-option name="rolesQuery" value="SELECT role, 'Roles' FROM swe2_role r INNER JOIN kunde k ON r.kunde_fk = k.k_id WHERE k.username=?"/>
<module-option name="hashAlgorithm" value="SHA-1"/>
<module-option name="hashEncoding" value="base64"/>
</login-module>
</authentication>
</security-domain>
Stacktrace regarding UsersRolesLoginModule (instead of DatabaseServerLoginModule):
16:03:58,528 ERROR [org.jboss.security.auth.spi.UsersRolesLoginModule] (http--127.0.0.1-8080-2) Failed to load users/passwords/role files: java.io.IOException: No properties file: users.properties or defaults: defaultUsers.properties found
at org.jboss.security.auth.spi.Util.loadProperties(Util.java:227) [picketbox-4.0.0.CR1.jar:4.0.0.CR1]
at org.jboss.security.auth.spi.UsersRolesLoginModule.loadUsers(UsersRolesLoginModule.java:188) [picketbox-4.0.0.CR1.jar:4.0.0.CR1]
at org.jboss.security.auth.spi.UsersRolesLoginModule.createUsers(UsersRolesLoginModule.java:202) [picketbox-4.0.0.CR1.jar:4.0.0.CR1]
at org.jboss.security.auth.spi.UsersRolesLoginModule.initialize(UsersRolesLoginModule.java:129) [picketbox-4.0.0.CR1.jar:4.0.0.CR1]
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 javax.security.auth.login.LoginContext.invoke(LoginContext.java:756) [:1.6.0_26]
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186) [:1.6.0_26]
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683) [:1.6.0_26]
at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_26]
at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680) [:1.6.0_26]
at javax.security.auth.login.LoginContext.login(LoginContext.java:579) [:1.6.0_26]
at org.jboss.security.authentication.JBossCachedAuthenticationManager.defaultLogin(JBossCachedAuthenticationManager.java:411) [picketbox-infinispan-4.0.0.CR1.jar:4.0.0.CR1]
at org.jboss.security.authentication.JBossCachedAuthenticationManager.authenticate(JBossCachedAuthenticationManager.java:345) [picketbox-infinispan-4.0.0.CR1.jar:4.0.0.CR1]
at org.jboss.security.authentication.JBossCachedAuthenticationManager.isValid(JBossCachedAuthenticationManager.java:154) [picketbox-infinispan-4.0.0.CR1.jar:4.0.0.CR1]
at org.jboss.as.web.security.JBossWebRealm.authenticate(JBossWebRealm.java:127) [jboss-as-web-7.0.0.CR1.jar:7.0.0.CR1]
at org.apache.catalina.authenticator.BasicAuthenticator.authenticate(BasicAuthenticator.java:180) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1]
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:446) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1]
at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.0.CR1.jar:7.0.0.CR1]
at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49) [jboss-as-jpa-7.0.0.CR1.jar:7.0.0.CR1]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1]
at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:893) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1]
at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:626) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1]
at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:2054) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months