[JBoss JIRA] (AS7-5623) Upgrade mim4j 0.6 -> 0.7.2
by Paul Gier (JIRA)
Paul Gier created AS7-5623:
------------------------------
Summary: Upgrade mim4j 0.6 -> 0.7.2
Key: AS7-5623
URL: https://issues.jboss.org/browse/AS7-5623
Project: Application Server 7
Issue Type: Component Upgrade
Components: REST, Web Services
Reporter: Paul Gier
Assignee: Paul Gier
Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP)
The recent upgrade of apache cxf to version 2.4.8 has a (loosely connected) dependency on upgrading mime4j.
{noformat}
+- apache cxf 2.4.8
| \- neethi 3.0.2
| \- apache axiom 1.2.13 (provided and test scope deps)
| \- mime4j 0.7.2
{noformat}
This upgrade does involve some API changes but the module is marked "private" so it may or may not be acceptable for the 7.1 branch. The testsuite passes with the update, but the upgrade might require a resteasy upgrade because resteasy uses the mime4j api directly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (AS7-5621) CLONE - @Resource(mappedName=...) cannot initialize static variable
by Miroslav Novak (JIRA)
Miroslav Novak created AS7-5621:
-----------------------------------
Summary: CLONE - @Resource(mappedName=...) cannot initialize static variable
Key: AS7-5621
URL: https://issues.jboss.org/browse/AS7-5621
Project: Application Server 7
Issue Type: Bug
Components: CDI / Weld
Affects Versions: 7.1.3.Final (EAP)
Reporter: Miroslav Novak
Assignee: Stuart Douglas
Fix For: 7.1.4.Final (EAP)
There is a change in behaviour of:
{code}
@Resource(mappedName = "java:/JmsXA")
private static ConnectionFactory cf;
{code}
In EAP6/AS7.1.2.Final this property is initialized but in EAP6.0.1.ER2/AS7.1.3.Final is not.
This could also break backward compatibility. Is there a reason why this feature should not work?
Used MDB:
{code}
import java.util.concurrent.atomic.AtomicInteger;
import javax.annotation.Resource;
import javax.ejb.*;
import javax.jms.*;
import org.apache.log4j.Level;
import org.apache.log4j.Logger;
@MessageDriven(name = "mdb",
activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
@ActivationConfigProperty(propertyName = "destination", propertyValue = "jms/queue/InQueue")})
@TransactionManagement(value = TransactionManagementType.CONTAINER)
@TransactionAttribute(value = TransactionAttributeType.REQUIRED)
public class LocalMdbFromQueue implements MessageDrivenBean, MessageListener {
@Resource(mappedName = "java:/JmsXA")
private static ConnectionFactory cf;
@Resource(mappedName = "java:/jms/queue/OutQueue")
private static Queue queue;
public static AtomicInteger globalCounter = new AtomicInteger();
private static final long serialVersionUID = 2770941392406343837L;
private static final Logger log = Logger.getLogger(LocalMdbFromQueue.class.getName());
private MessageDrivenContext context = null;
public LocalMdbFromQueue() {
super();
}
@Override
public void setMessageDrivenContext(MessageDrivenContext ctx) {
this.context = ctx;
}
public void ejbCreate() {
}
@Override
public void ejbRemove() {
}
@Override
public void onMessage(Message message) {
Connection con = null;
Session session;
try {
long time = System.currentTimeMillis();
int counter = 0;
try {
counter = message.getIntProperty("count");
} catch (Exception e) {
log.log(Level.ERROR, e.getMessage(), e);
}
String messageInfo = message.getJMSMessageID() + ", count:" + counter;
log.log(Level.INFO, " Start of message: " + globalCounter.incrementAndGet() + ", message info:" + messageInfo);
con = cf.createConnection();
con.start();
session = con.createSession(false, Session.AUTO_ACKNOWLEDGE);
String text = message.getJMSMessageID() + " processed by: " + hashCode();
MessageProducer sender = session.createProducer(queue);
TextMessage newMessage = session.createTextMessage(text);
newMessage.setStringProperty("inMessageId", message.getJMSMessageID());
sender.send(newMessage);
log.log(Level.INFO, " End of " + messageInfo + " in " + (System.currentTimeMillis() - time) + " ms");
} catch (Exception t) {
t.printStackTrace();
log.log(Level.FATAL, t.getMessage(), t);
} finally {
if (con != null) {
try {
con.close();
} catch (JMSException e) {
log.log(Level.FATAL, e.getMessage(), e);
}
}
}
}
}
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (AS7-5618) Erroneous Error message (should actually be a warning, and reworded)
by Jess Sightler (JIRA)
Jess Sightler created AS7-5618:
----------------------------------
Summary: Erroneous Error message (should actually be a warning, and reworded)
Key: AS7-5618
URL: https://issues.jboss.org/browse/AS7-5618
Project: Application Server 7
Issue Type: Bug
Components: Security
Affects Versions: 7.1.2.Final (EAP)
Reporter: Jess Sightler
Assignee: Anil Saldhana
When no security domain is specified for BaseCertLoginModule, this log message is printed to the console:
"The JSSE security domain other is not valid. All authentication using this login module will fail!"
I believe that whether this is actually the case ultimately depends on the verifier. In the case of AnyCertVerifier (or any customer Verifier), the security domain will not be necessary. This means that the login module will actually work, despite the above message to the contrary.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (JBMETA-361) CLONE - application.xml does not fully support property replacement
by Tom Fonteyne (JIRA)
[ https://issues.jboss.org/browse/JBMETA-361?page=com.atlassian.jira.plugin... ]
Tom Fonteyne updated JBMETA-361:
--------------------------------
Steps to Reproduce:
Make sure to set:
<subsystem xmlns="urn:jboss:domain:ee:1.1">
<spec-descriptor-property-replacement>
true
</spec-descriptor-property-replacement>
<jboss-descriptor-property-replacement>
true
</jboss-descriptor-property-replacement>
</subsystem>
Attached is a test case. Deploy and access the URL
It will show 'web-test' ${sysProp:'app-test'}
indicating that substitution ins application.xml was not done.
See application.xml:
<env-entry>
<env-entry-name>test</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>${sysProp:'app-test'}</env-entry-value>
</env-entry>
in web.xml
<context-param>
<param-name>webtest</param-name>
<param-value>${sysProp:'web-test'}</param-value>
</context-param>
I did some digging:
org/jboss/metadata/parser/util/MetaDataElementParser.java:
139 if (DescriptionGroupMetaDataParser.parse(reader, earMetaData.getDescriptionGroup())) {
140 return;
141 }
142 if (EnvironmentRefsGroupMetaDataParser.parse(reader, earMetaData.getEarEnvironmentRefsGroup())) {
143 return;
144 }
are not calling the parse method with the "propertyReplacer"
was:
Attached is a test case. Deploy and access the URL
It will show 'web-test' ${sysProp:'app-test'}
indicating that substitution ins application.xml was not done.
See application.xml:
<env-entry>
<env-entry-name>test</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>${sysProp:'app-test'}</env-entry-value>
</env-entry>
in web.xml
<context-param>
<param-name>webtest</param-name>
<param-value>${sysProp:'web-test'}</param-value>
</context-param>
I did some digging:
org/jboss/metadata/parser/util/MetaDataElementParser.java:
139 if (DescriptionGroupMetaDataParser.parse(reader, earMetaData.getDescriptionGroup())) {
140 return;
141 }
142 if (EnvironmentRefsGroupMetaDataParser.parse(reader, earMetaData.getEarEnvironmentRefsGroup())) {
143 return;
144 }
are not calling the parse method with the "propertyReplacer"
> CLONE - application.xml does not fully support property replacement
> -------------------------------------------------------------------
>
> Key: JBMETA-361
> URL: https://issues.jboss.org/browse/JBMETA-361
> Project: JBoss Metadata
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: ear, web
> Affects Versions: 7.0.4
> Reporter: Tom Fonteyne
> Priority: Minor
> Attachments: PropertyTest.ear
>
>
> Property substitution in application.xml does not work
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (JBMETA-361) CLONE - application.xml does not fully support property replacement
by Tom Fonteyne (JIRA)
[ https://issues.jboss.org/browse/JBMETA-361?page=com.atlassian.jira.plugin... ]
Tom Fonteyne updated JBMETA-361:
--------------------------------
Description: Property substitution in application.xml does not work (was: Property substitution in application.xml/web.xml does not work)
Steps to Reproduce:
Attached is a test case. Deploy and access the URL
It will show 'web-test' ${sysProp:'app-test'}
indicating that substitution ins application.xml was not done.
See application.xml:
<env-entry>
<env-entry-name>test</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>${sysProp:'app-test'}</env-entry-value>
</env-entry>
in web.xml
<context-param>
<param-name>webtest</param-name>
<param-value>${sysProp:'web-test'}</param-value>
</context-param>
I did some digging:
org/jboss/metadata/parser/util/MetaDataElementParser.java:
139 if (DescriptionGroupMetaDataParser.parse(reader, earMetaData.getDescriptionGroup())) {
140 return;
141 }
142 if (EnvironmentRefsGroupMetaDataParser.parse(reader, earMetaData.getEarEnvironmentRefsGroup())) {
143 return;
144 }
are not calling the parse method with the "propertyReplacer"
was:
Attached is a test case. Deploy and access the URL
It will show ${sysProp:'web-test'} ${sysProp:'app-test'}
indicating that substitution was not done.
See application.xml:
<env-entry>
<env-entry-name>test</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>${sysProp:'app-test'}</env-entry-value>
</env-entry>
in web.xml
<context-param>
<param-name>webtest</param-name>
<param-value>${sysProp:'web-test'}</param-value>
</context-param>
I did some digging:
org/jboss/metadata/parser/util/MetaDataElementParser.java:
139 if (DescriptionGroupMetaDataParser.parse(reader, earMetaData.getDescriptionGroup())) {
140 return;
141 }
142 if (EnvironmentRefsGroupMetaDataParser.parse(reader, earMetaData.getEarEnvironmentRefsGroup())) {
143 return;
144 }
are not calling the parse method with the "propertyReplacer"
I suspect the one for web.xml to be similar.
> CLONE - application.xml does not fully support property replacement
> -------------------------------------------------------------------
>
> Key: JBMETA-361
> URL: https://issues.jboss.org/browse/JBMETA-361
> Project: JBoss Metadata
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: ear, web
> Affects Versions: 7.0.4
> Reporter: Tom Fonteyne
> Priority: Minor
> Attachments: PropertyTest.ear
>
>
> Property substitution in application.xml does not work
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (JBJCA-898) expose statistics from wrapper datasource
by Mathieu Lachance (JIRA)
Mathieu Lachance created JBJCA-898:
--------------------------------------
Summary: expose statistics from wrapper datasource
Key: JBJCA-898
URL: https://issues.jboss.org/browse/JBJCA-898
Project: IronJacamar
Issue Type: Feature Request
Affects Versions: 1.0.9.Final
Environment: JBoss AS 7.1.1.Final
Reporter: Mathieu Lachance
Assignee: Jesper Pedersen
When getting from JNDI datasource from JBoss AS 7.1.1.Final we obtain a org.jboss.jca.adapters.jdbc.WrapperDataSource. This class hold a org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnectionFactory which hold org.jboss.jca.adapters.jdbc.statistics.JdbcStatisticsPlugin.
It would be nice that we could grant access to these statistics in a read only way. I would suggest adding these delegate method to WrapperDataSource :
isEnabled()
getPreparedStatementCacheAccessCount()
getPreparedStatementCacheAddCount()
getPreparedStatementCacheCurrentSize()
getPreparedStatementCacheDeleteCount()
getPreparedStatementCacheHitCount()
getPreparedStatementCacheMissCount()
I was also wondering where the Available Count, Average Blocking Time, Average Creation Time, Created Count, .... statisics were stored. It would be nice to expose them as well.
Big thanks,
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months