You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Manuel Garcia (JIRA)" <ji...@apache.org> on 2008/12/18 15:44:05 UTC

[jira] Commented: (AMQ-1605) 5.0.0: applet fails to initialize with default log4j.properties.

    [ https://issues.apache.org/activemq/browse/AMQ-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48265#action_48265 ] 

Manuel Garcia commented on AMQ-1605:
------------------------------------

I think that is because applets run on a security sandbox. To allow them to create threads, make connections, etc., you'll need to sing them with a certificate. When the user loads the applet into the browser he/she will be ask to accept the certificate. Then the applet will connect.
It's just a thought.

> 5.0.0: applet fails to initialize with default log4j.properties.
> ----------------------------------------------------------------
>
>                 Key: AMQ-1605
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1605
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client
>    Affects Versions: 5.0.0
>         Environment: jre 1.6.0_03 applet on both firefox and msie.
>            Reporter: Bear Giles
>             Fix For: 5.3.0
>
>
> We are unable to create a JMS-aware applet because of an initialization error in ActiveMQConnectionFactory/ActiveMQConnection.  My research suggests that the problem is due to a static logger instance and a default log4j.properties file that contains an appender that is inappropriate (as in, throws security exceptions) in applets.
> java.lang.ExceptionInInitializerError
>             at org.apache.activemq.ActiveMQConnection.<clinit>(ActiveMQConnection.java:106)
>             at com.si.applet.JmsApplet.<init>(JmsApplet.java:36)
>             at com.si.applet.ProducerConsumerApplet.<init>(ProducerConsumerApplet.java:36)
>             at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>             at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
>             at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
>             at java.lang.reflect.Constructor.newInstance(Unknown Source)
>             at java.lang.Class.newInstance0(Unknown Source)
>             at java.lang.Class.newInstance(Unknown Source)
>             at sun.applet.AppletPanel.createApplet(Unknown Source)
>             at sun.plugin.AppletViewer.createApplet(Unknown Source)
>             at sun.applet.AppletPanel.runLoader(Unknown Source)
>             at sun.applet.AppletPanel.run(Unknown Source)
>             at java.lang.Thread.run(Unknown Source)
> Caused by: java.security.AccessControlException: access denied (java.util.PropertyPermission org.apache.commons.logging.LogFactory.HashtableImpl read)
>             at java.security.AccessControlContext.checkPermission(Unknown Source)
>             at java.security.AccessController.checkPermission(Unknown Source)
>             at java.lang.SecurityManager.checkPermission(Unknown Source)
>             at java.lang.SecurityManager.checkPropertyAccess(Unknown Source)
>             at java.lang.System.getProperty(Unknown Source)
>             at org.apache.commons.logging.LogFactory.createFactoryStore(LogFactory.java:320)
>             at org.apache.commons.logging.LogFactory.<clinit>(LogFactory.java:1725)
>             ... 14 more 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.