[JBoss JIRA] Created: (JBAS-8843) size-rotating-file-handler not rotating
by Matthias Unverzagt (JIRA)
size-rotating-file-handler not rotating
---------------------------------------
Key: JBAS-8843
URL: https://issues.jboss.org/browse/JBAS-8843
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Logging
Affects Versions: 6.0.0.Final
Environment: Copied from boot.log:
############################
19:38:58,804 INFO [AbstractServer] Starting: JBossAS [6.0.1.SNAPSHOT "Neo"]
19:39:00,419 INFO [ServerInfo] Java version: 1.6.0_23,Sun Microsystems Inc.
19:39:00,419 INFO [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_23-b05)
19:39:00,419 INFO [ServerInfo] Java VM: Java HotSpot(TM) 64-Bit Server VM 19.0-b09,Sun Microsystems Inc.
19:39:00,420 INFO [ServerInfo] OS-System: Windows 7 6.1,amd64
19:39:00,420 INFO [ServerInfo] VM arguments: -Dprogram.name=run.bat -Xms1g -Xmx3g -XX:MaxPermSize=700M -Xdebug -Xrunjdwp:transport=dt_socket,address=9009,server=y,suspend=n -Djava.endorsed.dirs=E:\work\prgs\jboss-6.0.1-SNAPSHOT\lib\endorsed
19:39:00,420 DEBUG [ServerInfo] Full System Properties Dump
19:39:00,421 DEBUG [ServerInfo] awt.toolkit: sun.awt.windows.WToolkit
19:39:00,421 DEBUG [ServerInfo] bind.address: nb-matthias
19:39:00,421 DEBUG [ServerInfo] file.encoding: Cp1252
19:39:00,421 DEBUG [ServerInfo] file.encoding.pkg: sun.io
19:39:00,421 DEBUG [ServerInfo] file.separator: \
19:39:00,421 DEBUG [ServerInfo] java.awt.graphicsenv: sun.awt.Win32GraphicsEnvironment
19:39:00,422 DEBUG [ServerInfo] java.awt.printerjob: sun.awt.windows.WPrinterJob
19:39:00,422 DEBUG [ServerInfo] java.class.path: C:\Program Files\Java\jdk1.6.0_23\lib\tools.jar;E:\work\prgs\jboss-6.0.1-SNAPSHOT\bin\run.jar
19:39:00,422 DEBUG [ServerInfo] java.class.version: 50.0
19:39:00,422 DEBUG [ServerInfo] java.endorsed.dirs: E:\work\prgs\jboss-6.0.1-SNAPSHOT\lib\endorsed
19:39:00,422 DEBUG [ServerInfo] java.ext.dirs: C:\Program Files\Java\jdk1.6.0_23\jre\lib\ext;C:\Windows\Sun\Java\lib\ext
19:39:00,422 DEBUG [ServerInfo] java.home: C:\Program Files\Java\jdk1.6.0_23\jre
19:39:00,422 DEBUG [ServerInfo] java.io.tmpdir: C:\Users\matthias\AppData\Local\Temp\
19:39:00,423 DEBUG [ServerInfo] java.library.path: C:\Program Files\Java\jdk1.6.0_23\bin;.;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Program Files\Java\jdk1.6.0_23\bin;C:\apps\apache-maven-3.0.2\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\TortoiseGit\bin;C:\Program Files\TortoiseSVN\bin;C:\Program Files (x86)\NTRU Cryptosystems\NTRU TCG Software Stack\bin\;C:\Program Files\NTRU Cryptosystems\NTRU TCG Software Stack\bin\;C:\Program Files\Wave Systems Corp\Gemalto\Access Client\v5\;C:\Program Files\SlikSvn\bin\
19:39:00,423 DEBUG [ServerInfo] java.protocol.handler.pkgs: org.jboss.net.protocol|org.jboss.vfs.protocol
19:39:00,423 DEBUG [ServerInfo] java.rmi.server.RMIClassLoaderSpi: org.jboss.system.JBossRMIClassLoader
19:39:00,423 DEBUG [ServerInfo] java.rmi.server.hostname: nb-matthias
19:39:00,423 DEBUG [ServerInfo] java.runtime.name: Java(TM) SE Runtime Environment
19:39:00,423 DEBUG [ServerInfo] java.runtime.version: 1.6.0_23-b05
19:39:00,423 DEBUG [ServerInfo] java.specification.name: Java Platform API Specification
19:39:00,423 DEBUG [ServerInfo] java.specification.vendor: Sun Microsystems Inc.
19:39:00,424 DEBUG [ServerInfo] java.specification.version: 1.6
19:39:00,424 DEBUG [ServerInfo] java.util.logging.manager: org.jboss.logmanager.LogManager
19:39:00,424 DEBUG [ServerInfo] java.vendor: Sun Microsystems Inc.
19:39:00,424 DEBUG [ServerInfo] java.vendor.url: http://java.sun.com/
19:39:00,424 DEBUG [ServerInfo] java.vendor.url.bug: http://java.sun.com/cgi-bin/bugreport.cgi
19:39:00,424 DEBUG [ServerInfo] java.version: 1.6.0_23
19:39:00,424 DEBUG [ServerInfo] java.vm.info: mixed mode
19:39:00,425 DEBUG [ServerInfo] java.vm.name: Java HotSpot(TM) 64-Bit Server VM
19:39:00,425 DEBUG [ServerInfo] java.vm.specification.name: Java Virtual Machine Specification
19:39:00,425 DEBUG [ServerInfo] java.vm.specification.vendor: Sun Microsystems Inc.
19:39:00,425 DEBUG [ServerInfo] java.vm.specification.version: 1.0
19:39:00,425 DEBUG [ServerInfo] java.vm.vendor: Sun Microsystems Inc.
19:39:00,425 DEBUG [ServerInfo] java.vm.version: 19.0-b09
19:39:00,425 DEBUG [ServerInfo] javax.management.builder.initial: org.jboss.mx.server.MBeanServerBuilderImpl
19:39:00,425 DEBUG [ServerInfo] jboss.bind.address: 0.0.0.0
19:39:00,426 DEBUG [ServerInfo] jboss.boot.server.log.dir: E:\work\prgs\jboss-6.0.1-SNAPSHOT\server\default\log
19:39:00,426 DEBUG [ServerInfo] jboss.bootstrap.home.url: file:/E:/work/prgs/jboss-6.0.1-SNAPSHOT/server/default/conf/
19:39:00,426 DEBUG [ServerInfo] jboss.bootstrap.name: bootstrap.xml
19:39:00,426 DEBUG [ServerInfo] jboss.bootstrap.url: file:/E:/work/prgs/jboss-6.0.1-SNAPSHOT/server/default/conf/bootstrap.xml
19:39:00,426 DEBUG [ServerInfo] jboss.common.base.url: file:/E:/work/prgs/jboss-6.0.1-SNAPSHOT/common/
19:39:00,426 DEBUG [ServerInfo] jboss.common.lib.url: file:/E:/work/prgs/jboss-6.0.1-SNAPSHOT/common/lib/
19:39:00,426 DEBUG [ServerInfo] jboss.home: E:\work\prgs\jboss-6.0.1-SNAPSHOT
19:39:00,426 DEBUG [ServerInfo] jboss.home.dir: E:\work\prgs\jboss-6.0.1-SNAPSHOT
19:39:00,427 DEBUG [ServerInfo] jboss.home.url: file:/E:/work/prgs/jboss-6.0.1-SNAPSHOT/
19:39:00,427 DEBUG [ServerInfo] jboss.host.name: nb-matthias
19:39:00,427 DEBUG [ServerInfo] jboss.lib.url: file:/E:/work/prgs/jboss-6.0.1-SNAPSHOT/lib/
19:39:00,427 DEBUG [ServerInfo] jboss.native.dir: E:\work\prgs\jboss-6.0.1-SNAPSHOT\server\default\tmp\native
19:39:00,427 DEBUG [ServerInfo] jboss.native.load: false
19:39:00,427 DEBUG [ServerInfo] jboss.node.name: nb-matthias
19:39:00,427 DEBUG [ServerInfo] jboss.partition.name: DefaultPartition
19:39:00,427 DEBUG [ServerInfo] jboss.platform.mbeanserver: true
19:39:00,428 DEBUG [ServerInfo] jboss.qualified.host.name: nb-matthias
19:39:00,428 DEBUG [ServerInfo] jboss.server.base.dir: E:\work\prgs\jboss-6.0.1-SNAPSHOT\server
19:39:00,428 DEBUG [ServerInfo] jboss.server.base.url: file:/E:/work/prgs/jboss-6.0.1-SNAPSHOT/server/
19:39:00,428 DEBUG [ServerInfo] jboss.server.config.url: file:/E:/work/prgs/jboss-6.0.1-SNAPSHOT/server/default/conf/
19:39:00,428 DEBUG [ServerInfo] jboss.server.data.dir: E:\work\prgs\jboss-6.0.1-SNAPSHOT\server\default\data
19:39:00,428 DEBUG [ServerInfo] jboss.server.home.dir: E:\work\prgs\jboss-6.0.1-SNAPSHOT\server\default
19:39:00,428 DEBUG [ServerInfo] jboss.server.home.url: file:/E:/work/prgs/jboss-6.0.1-SNAPSHOT/server/default/
19:39:00,428 DEBUG [ServerInfo] jboss.server.lib.url: file:/E:/work/prgs/jboss-6.0.1-SNAPSHOT/server/default/lib/
19:39:00,429 DEBUG [ServerInfo] jboss.server.log.dir: E:\work\prgs\jboss-6.0.1-SNAPSHOT\server\default\log
19:39:00,429 DEBUG [ServerInfo] jboss.server.name: default
19:39:00,429 DEBUG [ServerInfo] jboss.server.temp.dir: E:\work\prgs\jboss-6.0.1-SNAPSHOT\server\default\tmp
19:39:00,429 DEBUG [ServerInfo] jboss.vfs.forceCopy: true
19:39:00,429 DEBUG [ServerInfo] jbossmx.loader.repository.class: org.jboss.mx.loading.UnifiedLoaderRepository3
19:39:00,429 DEBUG [ServerInfo] jgroups.bind_addr: nb-matthias
19:39:00,429 DEBUG [ServerInfo] line.separator:
19:39:00,429 DEBUG [ServerInfo] log4j.defaultInitOverride: true
19:39:00,430 DEBUG [ServerInfo] org.jboss.deployers.spi.deployer.matchers.NameIgnoreMechanism: org.jboss.deployers.spi.deployer.helpers.DummyNameIgnoreMechanism
19:39:00,430 DEBUG [ServerInfo] org.jboss.logging.Logger.pluginClass: org.jboss.logging.logmanager.LoggerPluginImpl
19:39:00,444 DEBUG [ServerInfo] org.jboss.reflect.spi.TypeInfoFactory: org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactory
19:39:00,444 DEBUG [ServerInfo] os.arch: amd64
19:39:00,444 DEBUG [ServerInfo] os.name: Windows 7
19:39:00,444 DEBUG [ServerInfo] os.version: 6.1
19:39:00,444 DEBUG [ServerInfo] path.separator: ;
19:39:00,444 DEBUG [ServerInfo] program.name: run.bat
19:39:00,445 DEBUG [ServerInfo] sun.arch.data.model: 64
19:39:00,445 DEBUG [ServerInfo] sun.boot.class.path: E:\work\prgs\jboss-6.0.1-SNAPSHOT\lib\endorsed\activation.jar;E:\work\prgs\jboss-6.0.1-SNAPSHOT\lib\endorsed\jboss-annotations-api_1.1_spec.jar;E:\work\prgs\jboss-6.0.1-SNAPSHOT\lib\endorsed\jboss-jaxb-api_2.2_spec.jar;E:\work\prgs\jboss-6.0.1-SNAPSHOT\lib\endorsed\jboss-jaxws-api_2.2_spec.jar;E:\work\prgs\jboss-6.0.1-SNAPSHOT\lib\endorsed\jbossws-cxf-factories.jar;E:\work\prgs\jboss-6.0.1-SNAPSHOT\lib\endorsed\stax-api.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\resources.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\rt.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\jce.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\modules\jdk.boot.jar;C:\Program Files\Java\jdk1.6.0_23\jre\classes
19:39:00,445 DEBUG [ServerInfo] sun.boot.library.path: C:\Program Files\Java\jdk1.6.0_23\jre\bin
19:39:00,445 DEBUG [ServerInfo] sun.cpu.endian: little
19:39:00,445 DEBUG [ServerInfo] sun.cpu.isalist: amd64
19:39:00,445 DEBUG [ServerInfo] sun.desktop: windows
19:39:00,445 DEBUG [ServerInfo] sun.io.unicode.encoding: UnicodeLittle
19:39:00,446 DEBUG [ServerInfo] sun.java.launcher: SUN_STANDARD
19:39:00,446 DEBUG [ServerInfo] sun.jnu.encoding: Cp1252
19:39:00,446 DEBUG [ServerInfo] sun.management.compiler: HotSpot 64-Bit Server Compiler
19:39:00,446 DEBUG [ServerInfo] sun.os.patch.level:
19:39:00,446 DEBUG [ServerInfo] user.country: DE
19:39:00,446 DEBUG [ServerInfo] user.dir: C:\Windows\System32
19:39:00,446 DEBUG [ServerInfo] user.home: C:\Users\matthias
19:39:00,446 DEBUG [ServerInfo] user.language: de
19:39:00,447 DEBUG [ServerInfo] user.name: matthias
19:39:00,447 DEBUG [ServerInfo] user.timezone: Europe/Berlin
19:39:00,447 DEBUG [ServerInfo] user.variant:
19:39:00,447 DEBUG [ServerInfo] xb.builder.repeatableParticleHandlers: false
19:39:00,447 DEBUG [ServerInfo] xb.builder.useUnorderedSequence: true
Reporter: Matthias Unverzagt
Assignee: David Lloyd
size-rotating-file-handler only rotates once and then the logfile grows.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] (AS7-3792) Remote EJB client still throws exception rather than blocking
by Radoslav Husar (JIRA)
Radoslav Husar created AS7-3792:
-----------------------------------
Summary: Remote EJB client still throws exception rather than blocking
Key: AS7-3792
URL: https://issues.jboss.org/browse/AS7-3792
Project: Application Server 7
Issue Type: Bug
Components: Clustering, EJB
Affects Versions: 7.1.0.Final
Reporter: Radoslav Husar
Assignee: jaikiran pai
Priority: Critical
Fix For: 7.1.1.Final
Lets reopen this topic, there seems to be flaw in implementation of EJBCLIENT-23, I am really seeing this exception with 1.0.2.Final client and AS 7.1.0.Final.
The exception is thrown on invoking method on the remote SFSB.
{noformat}
2012/02/16 08:34:58:715 EST [ERROR][Runner - 36] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error getting response. <java.lang.reflect.UndeclaredThrowableException>
java.lang.reflect.UndeclaredThrowableException
at $Proxy0.getSerialAndIncrement(Unknown Source)
at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:68)
at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:51)
at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.jboss.remoting3.ChannelBusyException: Too many open outbound writes
at org.jboss.remoting3.remote.RemoteConnectionChannel.openOutboundMessage(RemoteConnectionChannel.java:111)
at org.jboss.remoting3.remote.RemoteConnectionChannel.writeMessage(RemoteConnectionChannel.java:296)
at org.jboss.ejb.client.remoting.ChannelAssociation.acquireChannelMessageOutputStream(ChannelAssociation.java:235)
at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.processInvocation(RemotingConnectionEJBReceiver.java:193)
at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:173)
at org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:43)
at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:175)
at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:92)
at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:175)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
... 5 more
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] (AS7-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
14 years, 3 months
[JBoss JIRA] (AS7-3945) Fail to enable DS
by Heiko Braun (JIRA)
Heiko Braun created AS7-3945:
--------------------------------
Summary: Fail to enable DS
Key: AS7-3945
URL: https://issues.jboss.org/browse/AS7-3945
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Reporter: Heiko Braun
Assignee: Stefano Maestri
Fix For: 7.1.1.Final
Disable the default DS in standalone mode and re-eanble it:
{noformat}
{
"outcome" => "failed",
"failure-description" => "JBAS014749: Operation handler failed: Service jboss.data-source-config.ExampleDS is already registered",
"rolled-back" => true,
"response-headers" => {"process-state" => "restart-required"}
}
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] (AS7-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
14 years, 3 months