You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Bjoern Sonntag (JIRA)" <ji...@apache.org> on 2016/05/21 04:57:12 UTC
[jira] [Created] (AMQ-6300)
org.apache.activemq.SERIALIZABLE_PACKAGES="*" doesn't work
Bjoern Sonntag created AMQ-6300:
-----------------------------------
Summary: org.apache.activemq.SERIALIZABLE_PACKAGES="*" doesn't work
Key: AMQ-6300
URL: https://issues.apache.org/jira/browse/AMQ-6300
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.13.3
Environment: - Linux server 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
- java version "1.8.0_25"
Java(TM) SE Runtime Environment (build 1.8.0_25-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)
- Wildlfy 10.0.0.FINAL
- ActiveMQ 5.13.3
Reporter: Bjoern Sonntag
Priority: Critical
Hello,
i tried to use ActiveMQ in Combination with the Wildfly Application Server to establish a centrallogging acrhitecture. Some applications can write logging output through log4j JMSTopicAppender and on the Wildfly is a MDB which shall receive the message.
BUT i get every time the
06:45:58,259 ERROR [de.dropletinnovations.centrallogging.centralloggingsystem.LoggingMessageService] (default-threads - 24) Failed to build body from content. Serializable class not available to broker. Reason: java.lang.ClassNotFoundException: Forbidden class org.apache.log4j.spi.LoggingEvent! This class is not trusted to be serialized as ObjectMessage payload. Please take a look at http://activemq.apache.org/objectmessage.html for more information on how to configure trusted classes.
I've see at the page and added
if [ -z "$ACTIVEMQ_OPTS" ] ; then
ACTIVEMQ_OPTS="$ACTIVEMQ_OPTS_MEMORY -Djava.util.logging.config.file=logging.properties -Djava.security.auth.login.config=$ACTIVEMQ_CONF/login.config -Dorg.apache.activemq.SERIALIZABLE_PACKAGES='*'"
I try it without quotes too but both didn't work.
thank a lot.
with best regards
Bjoern
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)