[JBoss JIRA] Created: (JBAS-3996) Web Console AppletBrowser hangs browser because of missing Logger
by teej TJ (JIRA)
Web Console AppletBrowser hangs browser because of missing Logger
-----------------------------------------------------------------
Key: JBAS-3996
URL: http://jira.jboss.com/jira/browse/JBAS-3996
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Console
Affects Versions: JBossAS-5.0.0.Beta1
Environment: Ubuntu Edgy Eft 6.10 Linux 2.6.17-10-generic #2 SMP Tue Dec 5 22:28:26 UTC 2006 i686 GNU/Linux
Firefox 2.0.0.1
Sun Java 1.5.0_08
Reporter: teej TJ
Assigned To: Darran Lofthouse
Firefox hangs and has to be killed when the JBoss Web Console link is followed on the JBoss Management service (http://localhost:8080/).
The hang is caused by a NoClassDefFoundError exception whilst attempting to load AppletBrowser in applet.jar. This appears to be another instance of the use of Logger where it has been removed (as in the shutdown.sh script bugs JBAS-3560).
org.jboss.console.remote.Util:
private static org.jboss.logging.Logger log = org.jboss.logging.Logger.getLogger(Util.class);
--- Java Console Report ---
basic: Loading applet ...
basic: Initializing applet ...
basic: Starting applet ...
network: Connecting http://10.254.251.2:8080/web-console/applet.jar with proxy=DIRECT
network: Connecting http://10.254.251.2:8080/web-console/applet.jar with cookie "JSESSIONID=239D5221F10892A8D9A66F83680E589C"
basic: Loading http://10.254.251.2:8080/web-console/applet.jar from cache
basic: No certificate info, this is unsigned JAR file.
http://10.254.251.2:8080/web-console/Invoker
network: Connecting http://10.254.251.2:8080/web-console/org/jboss/logging/Logger.class with proxy=DIRECT
network: Connecting http://10.254.251.2:8080/web-console/org/jboss/logging/Logger.class with cookie "JSESSIONID=239D5221F10892A8D9A66F83680E589C"
java.lang.NoClassDefFoundError: org/jboss/logging/Logger
at org.jboss.console.remote.Util.<clinit>(Util.java:33)
at org.jboss.console.remote.AppletRemoteMBeanInvoker.invoke(AppletRemoteMBeanInvoker.java:64)
at org.jboss.console.navtree.ConsoleTreeModel.loadTree(ConsoleTreeModel.java:118)
at org.jboss.console.navtree.ConsoleTreeModel.<init>(ConsoleTreeModel.java:73)
at org.jboss.console.navtree.AdminTreeBrowser.<init>(AdminTreeBrowser.java:77)
at org.jboss.console.navtree.AppletBrowser.start(AppletBrowser.java:65)
at sun.applet.AppletPanel.run(AppletPanel.java:418)
at java.lang.Thread.run(Thread.java:595)
basic: Exception: java.lang.NoClassDefFoundError: org/jboss/logging/Logger
java.lang.NoClassDefFoundError: org/jboss/logging/Logger
at org.jboss.console.remote.Util.<clinit>(Util.java:33)
at org.jboss.console.remote.AppletRemoteMBeanInvoker.invoke(AppletRemoteMBeanInvoker.java:64)
at org.jboss.console.navtree.ConsoleTreeModel.loadTree(ConsoleTreeModel.java:118)
at org.jboss.console.navtree.ConsoleTreeModel.<init>(ConsoleTreeModel.java:73)
at org.jboss.console.navtree.AdminTreeBrowser.<init>(AdminTreeBrowser.java:77)
at org.jboss.console.navtree.AppletBrowser.start(AppletBrowser.java:65)
at sun.applet.AppletPanel.run(AppletPanel.java:418)
at java.lang.Thread.run(Thread.java:595)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 2 months
[JBoss JIRA] Created: (JBMESSAGING-875) Non durable subscription optimisation
by Tim Fox (JIRA)
Non durable subscription optimisation
-------------------------------------
Key: JBMESSAGING-875
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-875
Project: JBoss Messaging
Issue Type: Sub-task
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 1.2.1
Since non durable subscriptions only live for the life-time of the consumer the it's struck me that we don't actually need to send any acks from the client to the server as messages are acknowledged for non durable subs.
Basically I think we can acknowledge them before they are sent from server to client.
This is because there's no case where messages will be redelivered from the server to the non durable sub, therefore no need for acks.
On session recovery and session rollback messages are redelivered locally (i.e. they are already on the client) so no need for the server to redeliver.
This also means we don't need to maintain a delivery list in the server consumer endpoint in this case, and the server consumer endpoint can return a done delivery every time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 2 months