[JBoss JIRA] (WFLY-3433) Switch URI scheme from remoting:// http-remoting:// https-remoting:// to remote:// remote+http:// and remote+https://
by Darran Lofthouse (JIRA)
Darran Lofthouse created WFLY-3433:
--------------------------------------
Summary: Switch URI scheme from remoting:// http-remoting:// https-remoting:// to remote:// remote+http:// and remote+https://
Key: WFLY-3433
URL: https://issues.jboss.org/browse/WFLY-3433
Project: WildFly
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: CLI, Domain Management
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 9.0.0.CR1
>From [~dmlloyd]
{quote}
When we have multi-layer protocol going on, the URI scheme we should use
is like this:
outer+middle+inner://
{quote}
Switch URI schemes from remoting:// http-remoting:// https-remoting:// to remote:// remote+http:// and remote+https://
The existing schemes will be needed for backwards compatibility but somehow deprecated.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
9 years, 10 months
[JBoss JIRA] (DROOLS-511) KieContainerImpl.updateResourcesIncrementally throws NullPointerException when a package doesn't exist
by Mike Wilson (JIRA)
[ https://issues.jboss.org/browse/DROOLS-511?page=com.atlassian.jira.plugin... ]
Mike Wilson updated DROOLS-511:
-------------------------------
Summary: KieContainerImpl.updateResourcesIncrementally throws NullPointerException when a package doesn't exist (was: KieContainerImpl.updateResourcesIncrementally throws NullPointerException when a pacakge doesn't exist)
> KieContainerImpl.updateResourcesIncrementally throws NullPointerException when a package doesn't exist
> ------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-511
> URL: https://issues.jboss.org/browse/DROOLS-511
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 6.0.0.Final
> Reporter: Mike Wilson
> Assignee: Mark Proctor
>
> When calling KieContainerImpl.updateToVersion(ReleaseId), we sometimes experience a NullPointerException during a chained set of method calls that try to obtain a package, and then a rule within it.
> If the package is null, a NullPointerException is thrown, because there is no check in place before that call to get the rule from the package.
> To prevent this, a null check should be added to the package before trying to get the rule from it.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
9 years, 10 months
[JBoss JIRA] (DROOLS-512) KSession MBeans are no longer created.
by Mike Wilson (JIRA)
Mike Wilson created DROOLS-512:
----------------------------------
Summary: KSession MBeans are no longer created.
Key: DROOLS-512
URL: https://issues.jboss.org/browse/DROOLS-512
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 6.1.0.Beta4
Reporter: Mike Wilson
Assignee: Mark Proctor
After upgrading drools dependencies from version 6.0.2-SNAPSHOT to 6.1.0-SNAPSHOT, the mbeans that used to be created for each KieSession no longer get created.
The problem seems to have been introduced when the StatefulKnowledgeSessionImpl constructor was modified in this commit: https://github.com/droolsjbpm/drools/commit/1f8dc32725276a68456c5c4315c6a...
The previous version of the constructor made a call to StatefulKnowledgeSession.setKnowledgeRuntime(InternalKnowledgeRuntime kruntime), which resulted in the ksession mbean being created and registered.
I tried adding the following line to the end of the constructor, and the ksession mbeans started to get created again:
{code}
setKnowledgeRuntime(this);
{code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
9 years, 10 months
[JBoss JIRA] (WFLY-3432) Perm Gen Memory, overflow of memory, Java heap space
by Thiago Hernandes (JIRA)
[ https://issues.jboss.org/browse/WFLY-3432?page=com.atlassian.jira.plugin.... ]
Thiago Hernandes commented on WFLY-3432:
----------------------------------------
I solved this with:
Wildfly 8.0 and 8.1
---------------------------------------------------------------------------------------
java.lang.OutOfMemoryError: Java heap space
---------------------------------------------------------------------------------------
Solution to Perm Gen Memory, overflow of memory etc...
In file: standalone.conf (/wildfly8.1/bin) at the block:
if [ "x$JAVA_OPTS" = "x" ]; then
JAVA_OPTS="-Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true"
JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true"
else
Replace with (to machines with 4GB RAM):
if [ "x$JAVA_OPTS" = "x" ]; then
JAVA_OPTS="-Xms512m -Xmx2048m -XX:MaxPermSize=2048m -Djava.net.preferIPv4Stack=true"
JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true"
else
Important notice that 156 initial value, 1024 max value and another 1024 the Perm max size.
It´s possible to increase this values when server configurartion´s is more powerful
> Perm Gen Memory, overflow of memory, Java heap space
> ----------------------------------------------------
>
> Key: WFLY-3432
> URL: https://issues.jboss.org/browse/WFLY-3432
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Thiago Hernandes
> Assignee: Jason Greene
> Labels: heap, java, space
> Fix For: 8.1.0.Final
>
>
> I´ve a recent problem with Heap Memory.
> This: java.lang.OutOfMemoryError: Java heap space when proccessed a report
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
9 years, 10 months
[JBoss JIRA] (WFLY-3432) Perm Gen Memory, overflow of memory, Java heap space
by Thiago Hernandes (JIRA)
[ https://issues.jboss.org/browse/WFLY-3432?page=com.atlassian.jira.plugin.... ]
Thiago Hernandes resolved WFLY-3432.
------------------------------------
Fix Version/s: 8.1.0.Final
Resolution: Done
Wildfly 8.0 and 8.1
---------------------------------------------------------------------------------------
java.lang.OutOfMemoryError: Java heap space
---------------------------------------------------------------------------------------
Solution to Perm Gen Memory, overflow of memory etc...
In file: standalone.conf (/wildfly8.1/bin) at the block:
if [ "x$JAVA_OPTS" = "x" ]; then
JAVA_OPTS="-Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true"
JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true"
else
Replace with (to machines with 4GB RAM):
if [ "x$JAVA_OPTS" = "x" ]; then
JAVA_OPTS="-Xms512m -Xmx2048m -XX:MaxPermSize=2048m -Djava.net.preferIPv4Stack=true"
JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true"
else
Important notice that 156 initial value, 1024 max value and another 1024 the Perm max size.
It´s possible to increase this values when server configurartion´s is more powerful
> Perm Gen Memory, overflow of memory, Java heap space
> ----------------------------------------------------
>
> Key: WFLY-3432
> URL: https://issues.jboss.org/browse/WFLY-3432
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Thiago Hernandes
> Assignee: Jason Greene
> Labels: heap, java, space
> Fix For: 8.1.0.Final
>
>
> I´ve a recent problem with Heap Memory.
> This: java.lang.OutOfMemoryError: Java heap space when proccessed a report
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
9 years, 10 months