[jira] Created: (GERONIMO-3983) Update JMS Resource portlet to show the Destination statistics
Update JMS Resource portlet to show the Destination statistics -- Key: GERONIMO-3983 URL: https://issues.apache.org/jira/browse/GERONIMO-3983 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Reporter: Anish Pathadan Update the JMS Resource portlet to show the destination statistics such as Consumer Count,Queue Size,Enqueue Count and Dequeue Count for each Queues/Topics. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3983) Update JMS Resource portlet to show the Destination statistics
[ https://issues.apache.org/jira/browse/GERONIMO-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anish Pathadan updated GERONIMO-3983: - Attachment: screenshot-1.jpg Update JMS Resource portlet with Consumer Count and Queue Size. Update JMS Resource portlet to show the Destination statistics -- Key: GERONIMO-3983 URL: https://issues.apache.org/jira/browse/GERONIMO-3983 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Reporter: Anish Pathadan Attachments: screenshot-1.jpg Update the JMS Resource portlet to show the destination statistics such as Consumer Count,Queue Size,Enqueue Count and Dequeue Count for each Queues/Topics. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3983) Update JMS Resource portlet to show the Destination statistics
[ https://issues.apache.org/jira/browse/GERONIMO-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anish Pathadan updated GERONIMO-3983: - Attachment: JMS Resource Portlet_Statistics.patch Attached is the patch for updating JMS Resource portlet to include Destination statistics Consumer Count and Queue Size. Update JMS Resource portlet to show the Destination statistics -- Key: GERONIMO-3983 URL: https://issues.apache.org/jira/browse/GERONIMO-3983 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Reporter: Anish Pathadan Attachments: JMS Resource Portlet_Statistics.patch, screenshot-1.jpg Update the JMS Resource portlet to show the destination statistics such as Consumer Count,Queue Size,Enqueue Count and Dequeue Count for each Queues/Topics. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3983) Update JMS Resource portlet to show the Destination statistics
[ https://issues.apache.org/jira/browse/GERONIMO-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12591292#action_12591292 ] Anish Pathadan commented on GERONIMO-3983: -- Currently I have disabled showing enqueue/dequeue count for ActiveMQ queues and Topics due to the following defect in ActiveMQ https://issues.apache.org/activemq/browse/AMQ-1368 Once that defect is fixed, the list.jsp in activemq-portlet can be edited to include these fields also. Update JMS Resource portlet to show the Destination statistics -- Key: GERONIMO-3983 URL: https://issues.apache.org/jira/browse/GERONIMO-3983 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Reporter: Anish Pathadan Attachments: JMS Resource Portlet_Statistics.patch, screenshot-1.jpg Update the JMS Resource portlet to show the destination statistics such as Consumer Count,Queue Size,Enqueue Count and Dequeue Count for each Queues/Topics. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3819) Update JMS Resources Portlet
[ https://issues.apache.org/jira/browse/GERONIMO-3819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587683#action_12587683 ] Anish Pathadan commented on GERONIMO-3819: -- I was actually out of action for some time. Thanks Donald and Vamsi for reviewing and applying the patch. I will start working on adding more features to this portlet. Thanks, Anish Pathadan Update JMS Resources Portlet Key: GERONIMO-3819 URL: https://issues.apache.org/jira/browse/GERONIMO-3819 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: console Reporter: Anish Pathadan Assignee: Donald Woods Fix For: 2.2 Attachments: Browse Messages.jpg, JMS Resource Portlet_Main.jpg, JMSResource_portlet_1.0.patch, JMSResource_portlet_1.1.patch, Send Message.jpg Update the JMS Resources portlet to include the following information from the JMS Provider 1.Count of messages send to each queue/topic ,pending messages 2.Option to send messages to messages to particular queues/topics 3.Purge messages from queues/topics 4.Browse and send messages to queues/topics -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3819) Update JMS Resources Portlet
[ https://issues.apache.org/jira/browse/GERONIMO-3819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12581833#action_12581833 ] Anish Pathadan commented on GERONIMO-3819: -- Can anybody please try the patch and comment on it. I would like to add some more features to JMS resource portlet.For that I need your inputs on what features/enhancements you would like to see in this portlet. Update JMS Resources Portlet Key: GERONIMO-3819 URL: https://issues.apache.org/jira/browse/GERONIMO-3819 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: console Reporter: Anish Pathadan Assignee: Anish Pathadan Fix For: 2.1.1, 2.2 Attachments: Browse Messages.jpg, JMS Resource Portlet_Main.jpg, JMSResource_portlet_1.0.patch, JMSResource_portlet_1.1.patch, Send Message.jpg Update the JMS Resources portlet to include the following information from the JMS Provider 1.Count of messages send to each queue/topic ,pending messages 2.Option to send messages to messages to particular queues/topics 3.Purge messages from queues/topics 4.Browse and send messages to queues/topics -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3819) Update JMS Resources Portlet
[ https://issues.apache.org/jira/browse/GERONIMO-3819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anish Pathadan updated GERONIMO-3819: - Attachment: JMSResource_portlet_1.1.patch Thanks Vamsi for the comments.I have tried to correct all of them in the attached patch JMSResource_portlet_1.1.patch .Let me know incase I have missed out anything. There were two exceptions in the trace you have given.I could reproduce both the issues: I was putting some activemq text messages in session to show its contents.You get the exception when trying to stop the server while the session has some messages in it.Geronimo tries to serialise and save these non-serializable messages and results in the exception. I have corrected this one by creating my own serializable object to hold the necessary message info. The other exception is generated after sending a non-persistent messages to activemq queues/topics. This is a defect in activemq.I have reported the same in the following JIRA https://issues.apache.org/jira/browse/GERONIMO-3928 Update JMS Resources Portlet Key: GERONIMO-3819 URL: https://issues.apache.org/jira/browse/GERONIMO-3819 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: console Reporter: Anish Pathadan Assignee: Anish Pathadan Fix For: 2.1.1, 2.2 Attachments: Browse Messages.jpg, JMS Resource Portlet_Main.jpg, JMSResource_portlet_1.0.patch, JMSResource_portlet_1.1.patch, Send Message.jpg Update the JMS Resources portlet to include the following information from the JMS Provider 1.Count of messages send to each queue/topic ,pending messages 2.Option to send messages to messages to particular queues/topics 3.Purge messages from queues/topics 4.Browse and send messages to queues/topics -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3928) Exception on stopping server after sending a non persistent message
[ https://issues.apache.org/jira/browse/GERONIMO-3928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12579745#action_12579745 ] Anish Pathadan commented on GERONIMO-3928: -- There is no incorrect behaviour as far as I could observe.I had send some non persistant messages and restarted the server.After restart the messages are no more in the queue.It works as expected. Only annoying thing is the exception on stopping the server. Exception on stopping server after sending a non persistent message --- Key: GERONIMO-3928 URL: https://issues.apache.org/jira/browse/GERONIMO-3928 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Reporter: Anish Pathadan Fix For: 2.2 Attachments: sendMessage.war Hi, I am getting the following exception on stopping the server after sending a non persistent message to a queue. I have attached a test case for this. Steps to reproduce the issue:- 1).Deploy the attached sendMessage.war 2).Access http://localhost:8080/sendMessage/SendMessage to send a non persistent message. 3).Stop the server using Ctrl-C Following is the stack trace 07:39:08,828 WARN [ActiveMQManagedConnection] Connection failed: javax.jms.JMSE xception: java.io.EOFException 07:39:08,843 WARN [GeronimoConnectionEventListener] connectionErrorOccurred cal led with null javax.jms.JMSException: java.io.EOFException at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSuppo rt.java:46) at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConne ction.java:1519) at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection .java:1535) at org.apache.activemq.transport.TransportFilter.onException(TransportFi lter.java:96) at org.apache.activemq.transport.ResponseCorrelator.onException(Response Correlator.java:114) at org.apache.activemq.transport.TransportFilter.onException(TransportFi lter.java:96) at org.apache.activemq.transport.TransportFilter.onException(TransportFi lter.java:96) at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFo rmatNegotiator.java:147) at org.apache.activemq.transport.InactivityMonitor.onException(Inactivit yMonitor.java:150) at org.apache.activemq.transport.TransportSupport.onException(TransportS upport.java:97) at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java: 150) at java.lang.Thread.run(Thread.java:595) Caused by: java.io.EOFException at java.io.DataInputStream.readInt(DataInputStream.java:358) at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat. java:267) at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTranspo rt.java:156) at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java: 136) ... 1 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3928) Exception on stopping server after sending a non persistent message
Exception on stopping server after sending a non persistent message --- Key: GERONIMO-3928 URL: https://issues.apache.org/jira/browse/GERONIMO-3928 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: ActiveMQ Reporter: Anish Pathadan Fix For: 2.2 Hi, I am getting the following exception on stopping the server after sending a non persistent message to a queue. I have attached a test case for this. Steps to reproduce the issue:- 1).Deploy the attached sendMessage.war 2).Access http://localhost:8080/sendMessage/SendMessage to send a non persistent message. 3).Stop the server using Ctrl-C Following is the stack trace 07:39:08,828 WARN [ActiveMQManagedConnection] Connection failed: javax.jms.JMSE xception: java.io.EOFException 07:39:08,843 WARN [GeronimoConnectionEventListener] connectionErrorOccurred cal led with null javax.jms.JMSException: java.io.EOFException at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSuppo rt.java:46) at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConne ction.java:1519) at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection .java:1535) at org.apache.activemq.transport.TransportFilter.onException(TransportFi lter.java:96) at org.apache.activemq.transport.ResponseCorrelator.onException(Response Correlator.java:114) at org.apache.activemq.transport.TransportFilter.onException(TransportFi lter.java:96) at org.apache.activemq.transport.TransportFilter.onException(TransportFi lter.java:96) at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFo rmatNegotiator.java:147) at org.apache.activemq.transport.InactivityMonitor.onException(Inactivit yMonitor.java:150) at org.apache.activemq.transport.TransportSupport.onException(TransportS upport.java:97) at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java: 150) at java.lang.Thread.run(Thread.java:595) Caused by: java.io.EOFException at java.io.DataInputStream.readInt(DataInputStream.java:358) at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat. java:267) at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTranspo rt.java:156) at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java: 136) ... 1 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3928) Exception on stopping server after sending a non persistent message
[ https://issues.apache.org/jira/browse/GERONIMO-3928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anish Pathadan updated GERONIMO-3928: - Attachment: sendMessage.war Exception on stopping server after sending a non persistent message --- Key: GERONIMO-3928 URL: https://issues.apache.org/jira/browse/GERONIMO-3928 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Reporter: Anish Pathadan Fix For: 2.2 Attachments: sendMessage.war Hi, I am getting the following exception on stopping the server after sending a non persistent message to a queue. I have attached a test case for this. Steps to reproduce the issue:- 1).Deploy the attached sendMessage.war 2).Access http://localhost:8080/sendMessage/SendMessage to send a non persistent message. 3).Stop the server using Ctrl-C Following is the stack trace 07:39:08,828 WARN [ActiveMQManagedConnection] Connection failed: javax.jms.JMSE xception: java.io.EOFException 07:39:08,843 WARN [GeronimoConnectionEventListener] connectionErrorOccurred cal led with null javax.jms.JMSException: java.io.EOFException at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSuppo rt.java:46) at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConne ction.java:1519) at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection .java:1535) at org.apache.activemq.transport.TransportFilter.onException(TransportFi lter.java:96) at org.apache.activemq.transport.ResponseCorrelator.onException(Response Correlator.java:114) at org.apache.activemq.transport.TransportFilter.onException(TransportFi lter.java:96) at org.apache.activemq.transport.TransportFilter.onException(TransportFi lter.java:96) at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFo rmatNegotiator.java:147) at org.apache.activemq.transport.InactivityMonitor.onException(Inactivit yMonitor.java:150) at org.apache.activemq.transport.TransportSupport.onException(TransportS upport.java:97) at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java: 150) at java.lang.Thread.run(Thread.java:595) Caused by: java.io.EOFException at java.io.DataInputStream.readInt(DataInputStream.java:358) at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat. java:267) at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTranspo rt.java:156) at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java: 136) ... 1 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3819) Update JMS Resources Portlet
[ https://issues.apache.org/jira/browse/GERONIMO-3819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anish Pathadan updated GERONIMO-3819: - Attachment: JMS Resource Portlet_Main.jpg Main JMS Resource portlet.For Queues three new actions has been added (Browse,Send,Purge). For Topic one new action Send is added. Update JMS Resources Portlet Key: GERONIMO-3819 URL: https://issues.apache.org/jira/browse/GERONIMO-3819 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: console Reporter: Anish Pathadan Assignee: Anish Pathadan Attachments: JMS Resource Portlet_Main.jpg, JMSResource_portlet_1.0.patch Update the JMS Resources portlet to include the following information from the JMS Provider 1.Count of messages send to each queue/topic ,pending messages 2.Option to send messages to messages to particular queues/topics 3.Purge messages from queues/topics 4.Browse and send messages to queues/topics -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3819) Update JMS Resources Portlet
[ https://issues.apache.org/jira/browse/GERONIMO-3819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anish Pathadan updated GERONIMO-3819: - Attachment: Browse Messages.jpg This screen will show message properties like Priority,Message Id,Destination Physical Name,Time Stamp,Message Type,Correlation Id etc. for all the message in the selected Queue. Update JMS Resources Portlet Key: GERONIMO-3819 URL: https://issues.apache.org/jira/browse/GERONIMO-3819 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: console Reporter: Anish Pathadan Assignee: Anish Pathadan Attachments: Browse Messages.jpg, JMS Resource Portlet_Main.jpg, JMSResource_portlet_1.0.patch Update the JMS Resources portlet to include the following information from the JMS Provider 1.Count of messages send to each queue/topic ,pending messages 2.Option to send messages to messages to particular queues/topics 3.Purge messages from queues/topics 4.Browse and send messages to queues/topics -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3819) Update JMS Resources Portlet
[ https://issues.apache.org/jira/browse/GERONIMO-3819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anish Pathadan updated GERONIMO-3819: - Attachment: Send Message.jpg Use this portlet to send text messages to the selected queue/Topic.. Update JMS Resources Portlet Key: GERONIMO-3819 URL: https://issues.apache.org/jira/browse/GERONIMO-3819 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: console Reporter: Anish Pathadan Assignee: Anish Pathadan Attachments: Browse Messages.jpg, JMS Resource Portlet_Main.jpg, JMSResource_portlet_1.0.patch, Send Message.jpg Update the JMS Resources portlet to include the following information from the JMS Provider 1.Count of messages send to each queue/topic ,pending messages 2.Option to send messages to messages to particular queues/topics 3.Purge messages from queues/topics 4.Browse and send messages to queues/topics -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3819) Update JMS Resources Portlet
[ https://issues.apache.org/jira/browse/GERONIMO-3819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572878#action_12572878 ] Anish Pathadan commented on GERONIMO-3819: -- I have implemented the following features: 1. Browse messages in queue 2.Send messages to Queues/Topics 3.Purge messages from queue. I have attached a patch (JMSResource_portlet_1.0.patch) for the same. Update JMS Resources Portlet Key: GERONIMO-3819 URL: https://issues.apache.org/jira/browse/GERONIMO-3819 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: console Reporter: Anish Pathadan Assignee: Anish Pathadan Update the JMS Resources portlet to include the following information from the JMS Provider 1.Count of messages send to each queue/topic ,pending messages 2.Option to send messages to messages to particular queues/topics 3.Purge messages from queues/topics 4.Browse and send messages to queues/topics -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3819) Update JMS Resources Portlet
[ https://issues.apache.org/jira/browse/GERONIMO-3819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anish Pathadan updated GERONIMO-3819: - Attachment: JMSResource_portlet_1.0.patch Update JMS Resources Portlet Key: GERONIMO-3819 URL: https://issues.apache.org/jira/browse/GERONIMO-3819 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: console Reporter: Anish Pathadan Assignee: Anish Pathadan Attachments: JMSResource_portlet_1.0.patch Update the JMS Resources portlet to include the following information from the JMS Provider 1.Count of messages send to each queue/topic ,pending messages 2.Option to send messages to messages to particular queues/topics 3.Purge messages from queues/topics 4.Browse and send messages to queues/topics -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3819) Update JMS Resources Portlet
Update JMS Resources Portlet Key: GERONIMO-3819 URL: https://issues.apache.org/jira/browse/GERONIMO-3819 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: console Reporter: anish pathadan Assignee: anish pathadan Update the JMS Resources portlet to include the following information from the JMS Provider 1.Count of messages send to each queue/topic ,pending messages 2.Option to send messages to messages to particular queues/topics 3.Purge messages from queues/topics 4.Browse and send messages to queues/topics -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3683) Unable to view the installed geronimo plugins
Unable to view the installed geronimo plugins - Key: GERONIMO-3683 URL: https://issues.apache.org/jira/browse/GERONIMO-3683 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: Plugins Affects Versions: 2.0.2, 2.0.1 Environment: Windows XP Reporter: anish pathadan I have installed a geronimo plugin created by myself in my geronimo server.When I tried to access the plugins from a different server using the following url http://server-ip:8080/console-standard/maven-repo/ I am getting the following exception. 11:27:24,296 ERROR [[maven-repo]] Servlet.service() for servlet maven-repo threw exception java.lang.ArrayIndexOutOfBoundsException: 0 at org.apache.geronimo.console.car.GeronimoAsMavenServlet.generateConfig File(GeronimoAsMavenServlet.java:243) at org.apache.geronimo.console.car.GeronimoAsMavenServlet.handleRequest( GeronimoAsMavenServlet.java:90) at org.apache.geronimo.console.car.GeronimoAsMavenServlet.doGet(Geronimo AsMavenServlet.java:78) at javax.servlet.http.HttpServlet.service(HttpServlet.java:693) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl icationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF ilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV alve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV alve.java:175) at org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSu bjectValve.java:56) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authentica torBase.java:525) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve. invoke(GeronimoStandardContext.java:353) at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(Gero nimoBeforeAfterValve.java:47) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j ava:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j ava:104) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal ve.java:109) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java: 563) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav a:261) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java :844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce ss(Http11Protocol.java:581) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:44 7) at java.lang.Thread.run(Thread.java:619) Thanks, Anish -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3599) Unable to create new JMS Resource group through console in IE7
Unable to create new JMS Resource group through console in IE7 -- Key: GERONIMO-3599 URL: https://issues.apache.org/jira/browse/GERONIMO-3599 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Affects Versions: 2.0.1 Environment: WIN XP Reporter: anish pathadan I am not able to create a new JMS Resouce group through console. I am getting cannot display the page error after entering the Q name and physical name and then pressing next. The following is the url http://localhost:8080/console/portal/services/services_jms/_ps_services_jms_row1_col1_p1/normal/_pm_services_jms_row1_col1_p1/view/_ac_services_jms_row1_col1_p1/AC/_st_services_jms_row1_col1_p1/normal/_md_services_jms_row1_col1_p1/view/_pid/services_jms_row1_col1_p1 The problem only comes with Internet Explorer 7. Best Regards, Anish Pathadan -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-2880) TransportDisposedIOException occurs when trying to close ActiveMQ queue
[ https://issues.apache.org/jira/browse/GERONIMO-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] anish pathadan updated GERONIMO-2880: - Attachment: AMQ_NoTxDatasource.patch TransportDisposedIOException occurs when trying to close ActiveMQ queue --- Key: GERONIMO-2880 URL: https://issues.apache.org/jira/browse/GERONIMO-2880 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.0.x Environment: Windows XP SP2 Reporter: Aman Nanner Priority: Critical Fix For: 2.0.x, 2.1 Attachments: AMQ_NoTxDatasource.patch I have discovered some problems with queues while running unittest in our own J2EE app. After sending a message on a queue, when we try to call the close() method on the queue, we get the following exception: org.apache.activemq.transport.TransportDisposedIOException: Peer (vm://localhost#69) disposed. where the number after localhost is different every time. We do not experience this problem with topics. We are using ActiveMQ as part of an embedded configuration with Geronimo. I've done some debugging and the problem occurs at this line in the ActiveMQMessageProducer.close() method: this.session.asyncSendPacket(info.createRemoveCommand()); The queue itself is disposed properly in the dispose() method that is called in the line before, but this sending of the asynchronous packet fails. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2880) TransportDisposedIOException occurs when trying to close ActiveMQ queue
[ https://issues.apache.org/jira/browse/GERONIMO-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537956 ] anish pathadan commented on GERONIMO-2880: -- Hi All, The issue is due to geronimo using XA datasource (SystemDatasource) for activemq persistence. I have discussed this issue in activemq forum and I got the recommendation to use a non XA datasource for activemq persistence. The reason is activemq itself is managing the transaction for broker persistence and it doesn't make sense to use XA datasource as there is no other Transaction Manager involved in it. I have modified the activemq-broker plan to use NoTxDatasource and I got the issue resolved.I am attaching a patch also.I verified the issue in AG 2.0.1 release. Thanks, Anish Pathadan TransportDisposedIOException occurs when trying to close ActiveMQ queue --- Key: GERONIMO-2880 URL: https://issues.apache.org/jira/browse/GERONIMO-2880 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.0.x Environment: Windows XP SP2 Reporter: Aman Nanner Priority: Critical Fix For: 2.0.x, 2.1 I have discovered some problems with queues while running unittest in our own J2EE app. After sending a message on a queue, when we try to call the close() method on the queue, we get the following exception: org.apache.activemq.transport.TransportDisposedIOException: Peer (vm://localhost#69) disposed. where the number after localhost is different every time. We do not experience this problem with topics. We are using ActiveMQ as part of an embedded configuration with Geronimo. I've done some debugging and the problem occurs at this line in the ActiveMQMessageProducer.close() method: this.session.asyncSendPacket(info.createRemoveCommand()); The queue itself is disposed properly in the dispose() method that is called in the line before, but this sending of the asynchronous packet fails. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2880) TransportDisposedIOException occurs when trying to close ActiveMQ queue
[ https://issues.apache.org/jira/browse/GERONIMO-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525123 ] anish pathadan commented on GERONIMO-2880: -- Hi Aman, I could successfully send messages from a standalone client as well as from a servlet.There was no exception while closing the session or connection. Can you provide a test case for the issue. Thanks, Anish Pathadan TransportDisposedIOException occurs when trying to close ActiveMQ queue --- Key: GERONIMO-2880 URL: https://issues.apache.org/jira/browse/GERONIMO-2880 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.0.x Environment: Windows XP SP2 Reporter: Aman Nanner Priority: Critical Fix For: 2.0.x, 2.1 I have discovered some problems with queues while running unittest in our own J2EE app. After sending a message on a queue, when we try to call the close() method on the queue, we get the following exception: org.apache.activemq.transport.TransportDisposedIOException: Peer (vm://localhost#69) disposed. where the number after localhost is different every time. We do not experience this problem with topics. We are using ActiveMQ as part of an embedded configuration with Geronimo. I've done some debugging and the problem occurs at this line in the ActiveMQMessageProducer.close() method: this.session.asyncSendPacket(info.createRemoveCommand()); The queue itself is disposed properly in the dispose() method that is called in the line before, but this sending of the asynchronous packet fails. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3367) Unable to access console after stop/restart of active mq connector
Unable to access console after stop/restart of active mq connector -- Key: GERONIMO-3367 URL: https://issues.apache.org/jira/browse/GERONIMO-3367 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: connector Reporter: anish pathadan Unable to access console after stop/restart of Active MQ resource adapter. Attached below is the trace 17:18:55,875 WARN [startup] Unable to scrape for @Stateful, @Stateless or @Mess ageDriven annotations. EjbModule URL not valid: MEJBGBean java.net.MalformedURLException: no protocol: MEJBGBean at java.net.URL.init(URL.java:567) at java.net.URL.init(URL.java:464) at java.net.URL.init(URL.java:413) at org.apache.openejb.config.AnnotationDeployer$DiscoverBeansInClassLoad er.deploy(AnnotationDeployer.java:190) at org.apache.openejb.config.AnnotationDeployer$DiscoverBeansInClassLoad er.deploy(AnnotationDeployer.java:167) at org.apache.openejb.config.AnnotationDeployer.deploy(AnnotationDeploye r.java:158) at org.apache.openejb.config.ConfigurationFactory$Chain.deploy(Configura tionFactory.java:110) at org.apache.openejb.config.ConfigurationFactory.configureApplication(C onfigurationFactory.java:311) at org.apache.openejb.config.ConfigurationFactory.configureApplication(C onfigurationFactory.java:298) at org.apache.geronimo.openejb.OpenEjbSystemGBean.configureApplication(O penEjbSystemGBean.java:305) at org.apache.geronimo.openejb.OpenEjbSystemGBean$$FastClassByCGLIB$$500 5cdd0.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethod Invoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperatio n.java:127) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance. java:820) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:5 7) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperat ionInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(Pro xyMethodInterceptor.java:96) at org.apache.geronimo.openejb.OpenEjbSystem$$EnhancerByCGLIB$$30a1d823. configureApplication(generated) at org.apache.geronimo.openejb.MEJBGBean.doStart(MEJBGBean.java:48) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanI nstance.java:986) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart (GBeanInstanceState.java:267) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInsta nceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.j ava:529) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GB eanDependency.java:111) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDepe ndency.java:146) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDepe ndency.java:120) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEve nt(BasicLifecycleMonitor.java:173) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(Bas icLifecycleMonitor.java:41) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBr oadcaster.fireRunningEvent(BasicLifecycleMonitor.java:251) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart (GBeanInstanceState.java:292) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInsta nceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.j ava:529) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GB eanDependency.java:111) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDepe ndency.java:146) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDepe ndency.java:120) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEve nt(BasicLifecycleMonitor.java:173) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(Bas icLifecycleMonitor.java:41) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBr oadcaster.fireRunningEvent(BasicLifecycleMonitor.java:251) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart (GBeanInstanceState.java:292) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInsta nceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(G BeanInstanceState.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanI
