[JBoss JIRA] (DROOLS-1056) QueryDataServiceIntegrationTest fails for MySQL5.5
by Karel Suta (JIRA)
Karel Suta created DROOLS-1056:
----------------------------------
Summary: QueryDataServiceIntegrationTest fails for MySQL5.5
Key: DROOLS-1056
URL: https://issues.jboss.org/browse/DROOLS-1056
Project: Drools
Issue Type: Bug
Components: kie server
Affects Versions: 6.4.0.Beta1
Environment: version 6.4.0-SNAPSHOT
Reporter: Karel Suta
Assignee: Edson Tirelli
Priority: Minor
Attachments: stacktrace.txt, stacktrace2.txt
QueryDataServiceIntegrationTest fails when it is run against MySQL 5.5 database. It is caused by errors in SQL expressions for queries.
See attachments.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (REMJMX-105) Memory leak with http remoting jmx
by Andy G (JIRA)
[ https://issues.jboss.org/browse/REMJMX-105?page=com.atlassian.jira.plugin... ]
Andy G updated REMJMX-105:
--------------------------
Description:
We see the memory leak with the RemoteConnectionChannel.java when we try to use the JBOSS mbean server connection in web application.
We initialize the JMX connection factory as below
{code:title=Bar.java|borderStyle=solid}
try {
this.jmxConnector = JMXConnectorFactory.connect(serviceURL, auth);
if (this.jmxConnector != null) {
MBeanServerConnection mbs = this.jmxConnector.getMBeanServerConnection();
if (mbs != null) {
this.mbs = mbs;
}
}
} catch (IOException e) {
connected = false;
}
{code}
Then use mbean server connection after scheduled interval say 60 secs to read the mbeans from above mbean server connection.
private Map<String, Object> getAttributesForMBean(ObjectName objectName, List<String> attributeNames) {
HashMap<String, Object> attributeMap = new HashMap<String, Object>();
for (String attributeName : attributeNames) {
Object attributeValue = null;
if (this.hasAttribute(objectName, attributeName)) {
try {
attributeValue = this.mbs.getAttribute(objectName, attributeName);
} catch (Exception e) {
logger.warn("In getAttributes(), for " + objectName + ": " , e);
}
}
attributeMap.put(attributeName, attributeValue);
}
return attributeMap;
}
We see that RemoteConnectionChannel keeps accumulating XnioWorkerTaskPool and leads to memory leak.
was:
We see the memory leak with the RemoteConnectionChannel.java when we try to use the JBOSS mbean server connection in web application.
We initialize the JMX connection factory as below
try {
this.jmxConnector = JMXConnectorFactory.connect(serviceURL, auth);
if (this.jmxConnector != null) {
MBeanServerConnection mbs = this.jmxConnector.getMBeanServerConnection();
if (mbs != null) {
this.mbs = mbs;
}
}
} catch (IOException e) {
connected = false;
}
Then use mbean server connection after scheduled interval say 60 secs to read the mbeans from above mbean server connection.
private Map<String, Object> getAttributesForMBean(ObjectName objectName, List<String> attributeNames) {
HashMap<String, Object> attributeMap = new HashMap<String, Object>();
for (String attributeName : attributeNames) {
Object attributeValue = null;
if (this.hasAttribute(objectName, attributeName)) {
try {
attributeValue = this.mbs.getAttribute(objectName, attributeName);
} catch (Exception e) {
logger.warn("In getAttributes(), for " + objectName + ": " , e);
}
}
attributeMap.put(attributeName, attributeValue);
}
return attributeMap;
}
We see that RemoteConnectionChannel keeps accumulating XnioWorkerTaskPool and leads to memory leak.
> Memory leak with http remoting jmx
> ----------------------------------
>
> Key: REMJMX-105
> URL: https://issues.jboss.org/browse/REMJMX-105
> Project: Remoting JMX
> Issue Type: Bug
> Components: Connection
> Affects Versions: 2.0.1.Final
> Reporter: Andy G
> Assignee: Darran Lofthouse
> Attachments: screenshot-1.png
>
>
> We see the memory leak with the RemoteConnectionChannel.java when we try to use the JBOSS mbean server connection in web application.
> We initialize the JMX connection factory as below
> {code:title=Bar.java|borderStyle=solid}
> try {
> this.jmxConnector = JMXConnectorFactory.connect(serviceURL, auth);
> if (this.jmxConnector != null) {
>
> MBeanServerConnection mbs = this.jmxConnector.getMBeanServerConnection();
> if (mbs != null) {
> this.mbs = mbs;
> }
> }
>
> } catch (IOException e) {
> connected = false;
>
>
> }
> {code}
> Then use mbean server connection after scheduled interval say 60 secs to read the mbeans from above mbean server connection.
> private Map<String, Object> getAttributesForMBean(ObjectName objectName, List<String> attributeNames) {
>
> HashMap<String, Object> attributeMap = new HashMap<String, Object>();
> for (String attributeName : attributeNames) {
> Object attributeValue = null;
> if (this.hasAttribute(objectName, attributeName)) {
> try {
> attributeValue = this.mbs.getAttribute(objectName, attributeName);
> } catch (Exception e) {
> logger.warn("In getAttributes(), for " + objectName + ": " , e);
> }
> }
> attributeMap.put(attributeName, attributeValue);
> }
>
> return attributeMap;
> }
> We see that RemoteConnectionChannel keeps accumulating XnioWorkerTaskPool and leads to memory leak.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (REMJMX-105) Memory leak with http remoting jmx
by Andy G (JIRA)
[ https://issues.jboss.org/browse/REMJMX-105?page=com.atlassian.jira.plugin... ]
Andy G updated REMJMX-105:
--------------------------
Description:
We see the memory leak with the RemoteConnectionChannel.java when we try to use the JBOSS mbean server connection in web application.
We initialize the JMX connection factory as below
{code:borderStyle=solid}
try {
this.jmxConnector = JMXConnectorFactory.connect(serviceURL, auth);
if (this.jmxConnector != null) {
MBeanServerConnection mbs = this.jmxConnector.getMBeanServerConnection();
if (mbs != null) {
this.mbs = mbs;
}
}
} catch (IOException e) {
connected = false;
}
{code}
Then use mbean server connection after scheduled interval say 60 secs to read the mbeans from above mbean server connection.
{code:borderStyle=solid}
private Map<String, Object> getAttributesForMBean(ObjectName objectName, List<String> attributeNames) {
HashMap<String, Object> attributeMap = new HashMap<String, Object>();
for (String attributeName : attributeNames) {
Object attributeValue = null;
if (this.hasAttribute(objectName, attributeName)) {
try {
attributeValue = this.mbs.getAttribute(objectName, attributeName);
} catch (Exception e) {
logger.warn("In getAttributes(), for " + objectName + ": " , e);
}
}
attributeMap.put(attributeName, attributeValue);
}
return attributeMap;
}
{code}
We see that RemoteConnectionChannel keeps accumulating XnioWorkerTaskPool and leads to memory leak.
was:
We see the memory leak with the RemoteConnectionChannel.java when we try to use the JBOSS mbean server connection in web application.
We initialize the JMX connection factory as below
{code:title=Bar.java|borderStyle=solid}
try {
this.jmxConnector = JMXConnectorFactory.connect(serviceURL, auth);
if (this.jmxConnector != null) {
MBeanServerConnection mbs = this.jmxConnector.getMBeanServerConnection();
if (mbs != null) {
this.mbs = mbs;
}
}
} catch (IOException e) {
connected = false;
}
{code}
Then use mbean server connection after scheduled interval say 60 secs to read the mbeans from above mbean server connection.
private Map<String, Object> getAttributesForMBean(ObjectName objectName, List<String> attributeNames) {
HashMap<String, Object> attributeMap = new HashMap<String, Object>();
for (String attributeName : attributeNames) {
Object attributeValue = null;
if (this.hasAttribute(objectName, attributeName)) {
try {
attributeValue = this.mbs.getAttribute(objectName, attributeName);
} catch (Exception e) {
logger.warn("In getAttributes(), for " + objectName + ": " , e);
}
}
attributeMap.put(attributeName, attributeValue);
}
return attributeMap;
}
We see that RemoteConnectionChannel keeps accumulating XnioWorkerTaskPool and leads to memory leak.
> Memory leak with http remoting jmx
> ----------------------------------
>
> Key: REMJMX-105
> URL: https://issues.jboss.org/browse/REMJMX-105
> Project: Remoting JMX
> Issue Type: Bug
> Components: Connection
> Affects Versions: 2.0.1.Final
> Reporter: Andy G
> Assignee: Darran Lofthouse
> Attachments: screenshot-1.png
>
>
> We see the memory leak with the RemoteConnectionChannel.java when we try to use the JBOSS mbean server connection in web application.
> We initialize the JMX connection factory as below
> {code:borderStyle=solid}
> try {
> this.jmxConnector = JMXConnectorFactory.connect(serviceURL, auth);
> if (this.jmxConnector != null) {
>
> MBeanServerConnection mbs = this.jmxConnector.getMBeanServerConnection();
> if (mbs != null) {
> this.mbs = mbs;
> }
> }
>
> } catch (IOException e) {
> connected = false;
>
>
> }
> {code}
> Then use mbean server connection after scheduled interval say 60 secs to read the mbeans from above mbean server connection.
> {code:borderStyle=solid}
> private Map<String, Object> getAttributesForMBean(ObjectName objectName, List<String> attributeNames) {
>
> HashMap<String, Object> attributeMap = new HashMap<String, Object>();
> for (String attributeName : attributeNames) {
> Object attributeValue = null;
> if (this.hasAttribute(objectName, attributeName)) {
> try {
> attributeValue = this.mbs.getAttribute(objectName, attributeName);
> } catch (Exception e) {
> logger.warn("In getAttributes(), for " + objectName + ": " , e);
> }
> }
> attributeMap.put(attributeName, attributeValue);
> }
>
> return attributeMap;
> }
> {code}
> We see that RemoteConnectionChannel keeps accumulating XnioWorkerTaskPool and leads to memory leak.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (REMJMX-105) Memory leak with http remoting jmx
by Andy G (JIRA)
[ https://issues.jboss.org/browse/REMJMX-105?page=com.atlassian.jira.plugin... ]
Andy G updated REMJMX-105:
--------------------------
Priority: Critical (was: Major)
> Memory leak with http remoting jmx
> ----------------------------------
>
> Key: REMJMX-105
> URL: https://issues.jboss.org/browse/REMJMX-105
> Project: Remoting JMX
> Issue Type: Bug
> Components: Connection
> Affects Versions: 2.0.1.Final
> Reporter: Andy G
> Assignee: Darran Lofthouse
> Priority: Critical
> Attachments: screenshot-1.png
>
>
> We see the memory leak with the RemoteConnectionChannel.java when we try to use the JBOSS mbean server connection in web application.
> We initialize the JMX connection factory as below
> {code:borderStyle=solid}
> try {
> this.jmxConnector = JMXConnectorFactory.connect(serviceURL, auth);
> if (this.jmxConnector != null) {
>
> MBeanServerConnection mbs = this.jmxConnector.getMBeanServerConnection();
> if (mbs != null) {
> this.mbs = mbs;
> }
> }
>
> } catch (IOException e) {
> connected = false;
>
>
> }
> {code}
> Then use mbean server connection after scheduled interval say 60 secs to read the mbeans from above mbean server connection.
> {code:borderStyle=solid}
> private Map<String, Object> getAttributesForMBean(ObjectName objectName, List<String> attributeNames) {
>
> HashMap<String, Object> attributeMap = new HashMap<String, Object>();
> for (String attributeName : attributeNames) {
> Object attributeValue = null;
> if (this.hasAttribute(objectName, attributeName)) {
> try {
> attributeValue = this.mbs.getAttribute(objectName, attributeName);
> } catch (Exception e) {
> logger.warn("In getAttributes(), for " + objectName + ": " , e);
> }
> }
> attributeMap.put(attributeName, attributeValue);
> }
>
> return attributeMap;
> }
> {code}
> We see that RemoteConnectionChannel keeps accumulating XnioWorkerTaskPool and leads to memory leak.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (REMJMX-105) Memory leak with http remoting jmx
by Andy G (JIRA)
[ https://issues.jboss.org/browse/REMJMX-105?page=com.atlassian.jira.plugin... ]
Andy G updated REMJMX-105:
--------------------------
Attachment: screenshot-1.png
> Memory leak with http remoting jmx
> ----------------------------------
>
> Key: REMJMX-105
> URL: https://issues.jboss.org/browse/REMJMX-105
> Project: Remoting JMX
> Issue Type: Bug
> Components: Connection
> Affects Versions: 2.0.1.Final
> Reporter: Andy G
> Assignee: Darran Lofthouse
> Attachments: screenshot-1.png
>
>
> We see the memory leak with the RemoteConnectionChannel.java when we try to use the JBOSS mbean server connection in web application.
> We initialize the JMX connection factory as below
> try {
> this.jmxConnector = JMXConnectorFactory.connect(serviceURL, auth);
> if (this.jmxConnector != null) {
>
> MBeanServerConnection mbs = this.jmxConnector.getMBeanServerConnection();
> if (mbs != null) {
> this.mbs = mbs;
> }
> }
>
> } catch (IOException e) {
> connected = false;
>
>
> }
> Then use mbean server connection after scheduled interval say 60 secs to read the mbeans from above mbean server connection.
> private Map<String, Object> getAttributesForMBean(ObjectName objectName, List<String> attributeNames) {
>
> HashMap<String, Object> attributeMap = new HashMap<String, Object>();
> for (String attributeName : attributeNames) {
> Object attributeValue = null;
> if (this.hasAttribute(objectName, attributeName)) {
> try {
> attributeValue = this.mbs.getAttribute(objectName, attributeName);
> } catch (Exception e) {
> logger.warn("In getAttributes(), for " + objectName + ": " , e);
> }
> }
> attributeMap.put(attributeName, attributeValue);
> }
>
> return attributeMap;
> }
> We see that RemoteConnectionChannel keeps accumulating XnioWorkerTaskPool and leads to memory leak.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (REMJMX-105) Memory leak with http remoting jmx
by Andy G (JIRA)
Andy G created REMJMX-105:
-----------------------------
Summary: Memory leak with http remoting jmx
Key: REMJMX-105
URL: https://issues.jboss.org/browse/REMJMX-105
Project: Remoting JMX
Issue Type: Bug
Components: Connection
Affects Versions: 2.0.1.Final
Reporter: Andy G
Assignee: Darran Lofthouse
We see the memory leak with the RemoteConnectionChannel.java when we try to use the JBOSS mbean server connection in web application.
We initialize the JMX connection factory as below
try {
this.jmxConnector = JMXConnectorFactory.connect(serviceURL, auth);
if (this.jmxConnector != null) {
MBeanServerConnection mbs = this.jmxConnector.getMBeanServerConnection();
if (mbs != null) {
this.mbs = mbs;
}
}
} catch (IOException e) {
connected = false;
}
Then use mbean server connection after scheduled interval say 60 secs to read the mbeans from above mbean server connection.
private Map<String, Object> getAttributesForMBean(ObjectName objectName, List<String> attributeNames) {
HashMap<String, Object> attributeMap = new HashMap<String, Object>();
for (String attributeName : attributeNames) {
Object attributeValue = null;
if (this.hasAttribute(objectName, attributeName)) {
try {
attributeValue = this.mbs.getAttribute(objectName, attributeName);
} catch (Exception e) {
logger.warn("In getAttributes(), for " + objectName + ": " , e);
}
}
attributeMap.put(attributeName, attributeValue);
}
return attributeMap;
}
We see that RemoteConnectionChannel keeps accumulating XnioWorkerTaskPool and leads to memory leak.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months