Jorn, I've made changes to the UIMA AS service code to reduce logging. In fact, I've changed the code to log an entry just once on initial failure to connect to the broker's MBeanServer and also reduced the severity to INFO from WARNING. This is a normal situation that one wants to run a broker without a JMX Connector.
Jerry C 2010/4/20 Jörn Kottmann (JIRA) <[email protected]> > > [ > https://issues.apache.org/jira/browse/UIMA-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858899#action_12858899] > > Jörn Kottmann commented on UIMA-1766: > ------------------------------------- > > I think the first fix broke something, when the current trunk is run on our > server it spams the log file with > this exception traces. The test server the service is running on has the ip > 10.45.2.103 and our test activemq broker > is running on 10.45.2.100. > > It looks like to use the activemq broker for some JMX stuff. > > Here is the error message: > 4/20/10 4:20:56 PM - 30: > org.apache.uima.adapter.jms.activemq.JmsInputChannel.ackMessage: WARNING: > java.io.IOException: Failed to retrieve RMIServer stub: > javax.naming.ServiceUnavailableException [Root exception is > java.rmi.ConnectException: Connection refused to host: 10.45.2.100; nested > exception is: > java.net.ConnectException: Connection refused] > at > javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:323) > at > javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) > at > org.apache.uima.aae.jmx.RemoteJMXServer.initialize(RemoteJMXServer.java:76) > at > org.apache.uima.adapter.jms.activemq.JmsInputChannel.attachToRemoteBrokerJMXServer(JmsInputChannel.java:837) > at > org.apache.uima.adapter.jms.activemq.JmsInputChannel.onMessage(JmsInputChannel.java:605) > at > org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:518) > at > org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:479) > at > org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:451) > at > org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:323) > at > org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:261) > at > org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:982) > at > org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:974) > at > org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:876) > at java.lang.Thread.run(Thread.java:619) > Caused by: javax.naming.ServiceUnavailableException [Root exception is > java.rmi.ConnectException: Connection refused to host: 10.45.2.100; nested > exception is: > java.net.ConnectException: Connection refused] > at > com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:101) > at > com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:185) > at javax.naming.InitialContext.lookup(InitialContext.java:392) > at > javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1871) > at > javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1841) > at > javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:257) > ... 13 more > Caused by: java.rmi.ConnectException: Connection refused to host: > 10.45.2.100; nested exception is: > java.net.ConnectException: Connection refused > at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601) > at > sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198) > at > sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184) > at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:322) > at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source) > at > com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:97) > ... 18 more > Caused by: java.net.ConnectException: Connection refused > at java.net.PlainSocketImpl.socketConnect(Native Method) > at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) > at > java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) > at java.net.Socket.connect(Socket.java:519) > at java.net.Socket.connect(Socket.java:469) > at java.net.Socket.<init>(Socket.java:366) > at java.net.Socket.<init>(Socket.java:180) > at > sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22) > at > sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128) > at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595) > ... 23 more > > > > > Fix Memory Leak in UIMA AS Service > > ---------------------------------- > > > > Key: UIMA-1766 > > URL: https://issues.apache.org/jira/browse/UIMA-1766 > > Project: UIMA > > Issue Type: Bug > > Components: Async Scaleout > > Affects Versions: 2.3AS > > Reporter: Jerry Cwiklik > > Assignee: Jerry Cwiklik > > > > When running an Aggregate with a colocated Cas Multiplier per CAS > statistics are not being removed from a Map maintained by the Cas Multiplier > service. As more CASes are sent to the CM, instances of ServicePerformance > object are added to the Map and never removed leading to a memory leak and > eventual OOM error. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > >
