[JBoss JIRA] (JBJCA-1246) Show extra classpath in rar-info report
by Jesper Pedersen (JIRA)
Jesper Pedersen created JBJCA-1246:
--------------------------------------
Summary: Show extra classpath in rar-info report
Key: JBJCA-1246
URL: https://issues.jboss.org/browse/JBJCA-1246
Project: IronJacamar
Issue Type: Task
Components: AS
Reporter: Jesper Pedersen
Assignee: Johnathon Lee
The rar-info report should show the optional classpath if used
{noformat}
Native: No
Extra classpath: jboss-jms-api_1.1_spec.jar, ...
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFLY-4338) JConsole script builds wrong path
by André Lemos (JIRA)
[ https://issues.jboss.org/browse/WFLY-4338?page=com.atlassian.jira.plugin.... ]
André Lemos updated WFLY-4338:
------------------------------
Attachment: jconsole.patch
quick & dirty patch to fix this issue
> JConsole script builds wrong path
> ---------------------------------
>
> Key: WFLY-4338
> URL: https://issues.jboss.org/browse/WFLY-4338
> Project: WildFly
> Issue Type: Bug
> Components: JMX
> Affects Versions: 8.2.0.Final
> Environment: Linux (Ubuntu 14.10) and Mac OS X Yosemite (10.10.2)
> Reporter: André Lemos
> Assignee: Kabir Khan
> Priority: Trivial
> Labels: bash, jconsole, wildfly
> Attachments: jconsole.patch
>
>
> The path built by the jconsole.sh script is incorrect, and as a result, when calling {{service:jmx:http-remoting-jmx://{insert server ip here}:9990}} is probably never recognized and the connection is never done.
> The path, under mac is:
> {{/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/bin/jconsole -J-Djava.class.path=/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/lib/jconsole.jar:/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/lib/tools.jar:"/Users/user/Documents/playground/wild/wildfly-8.2.0.Final"/bin/client/jboss-cli-client.jar}}
> So, there are " on the path for the jboss-cli-client.jar. which breaks things. This problem happens with both Linux and Mac.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFLY-4338) JConsole script builds wrong path
by André Lemos (JIRA)
André Lemos created WFLY-4338:
---------------------------------
Summary: JConsole script builds wrong path
Key: WFLY-4338
URL: https://issues.jboss.org/browse/WFLY-4338
Project: WildFly
Issue Type: Bug
Components: JMX
Affects Versions: 8.2.0.Final
Environment: Linux (Ubuntu 14.10) and Mac OS X Yosemite (10.10.2)
Reporter: André Lemos
Assignee: Kabir Khan
Priority: Trivial
The path built by the jconsole.sh script is incorrect, and as a result, when calling {{service:jmx:http-remoting-jmx://{insert server ip here}:9990}} is probably never recognized and the connection is never done.
The path, under mac is:
{{/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/bin/jconsole -J-Djava.class.path=/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/lib/jconsole.jar:/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/lib/tools.jar:"/Users/user/Documents/playground/wild/wildfly-8.2.0.Final"/bin/client/jboss-cli-client.jar}}
So, there are " on the path for the jboss-cli-client.jar. which breaks things. This problem happens with both Linux and Mac.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFCORE-537) Add path support into the management API
by Emmanuel Hugonnet (JIRA)
Emmanuel Hugonnet created WFCORE-537:
----------------------------------------
Summary: Add path support into the management API
Key: WFCORE-537
URL: https://issues.jboss.org/browse/WFCORE-537
Project: WildFly Core
Issue Type: Enhancement
Components: Domain Management
Affects Versions: 1.0.0.Alpha17
Reporter: Emmanuel Hugonnet
Assignee: Emmanuel Hugonnet
Add support for ModelNode of type String to pass the operation address of an operation instead of a list of ModelNode
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (AS7-2138) javax.naming.NameNotFoundException: rmi://127.0.0.1:1090/jmxrmi thrown when creating MBeanServerConnection
by Eugenio Lentini (JIRA)
[ https://issues.jboss.org/browse/AS7-2138?page=com.atlassian.jira.plugin.s... ]
Eugenio Lentini commented on AS7-2138:
--------------------------------------
Hi,
I am facing with the same issue running JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19). From within the web application deployed as exploded war in JBoss I would like to connect to
{noformat}
service:jmx:rmi://localhost:7276/jndi/rmi://localhost:7277/myservice
{noformat}
and I got the exception
{noformat}
javax.naming.NameNotFoundException: rmi://localhost:7277/myservice -- service jboss.naming.context.java.remoting-jmx:.localhost:7277.myservice
{noformat}
I have even tried with {{remoting-jmx}} in place of {{rmi}} but nothing to do, still the same issue. The workaround is not really feasible because we do not have control on the client machine and may be the client won't change the config.
* From the latest posts it is not clear if the issue still persist or if it has been resolve, could you please clarify?
* What about this comment _"The problem is that its not possible to connect to a standalone application that is running a standard JMX server from within JBoss."_
* Is there another way to accomplish the connection under JMX?
Thanks a lot for your attention.
Eugenio
> javax.naming.NameNotFoundException: rmi://127.0.0.1:1090/jmxrmi thrown when creating MBeanServerConnection
> ----------------------------------------------------------------------------------------------------------
>
> Key: AS7-2138
> URL: https://issues.jboss.org/browse/AS7-2138
> Project: Application Server 7
> Issue Type: Bug
> Components: JMX
> Affects Versions: 7.0.0.Final, 7.0.1.Final, 7.0.2.Final, 7.1.0.Final
> Reporter: Stian Thorgersen
> Assignee: Bartosz Baranowski
> Fix For: 7.1.2.Final (EAP)
>
> Attachments: jmx-test.jar, JmxClient.java, JMXConnectionBean.java, JmxServer.java
>
>
> When trying to create a MBeanServerConnection from within an EJB a "javax.naming.NameNotFoundException" is thrown. When executed as a standalone Java the same code works fine. To verify that it works as a standalone Java process run "java -cp jmx-test.jar com.example.JMXConnectionBean" (with AS7 running on the same machine).
> Full stack trace:
> {code}
> Caused by: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.NameNotFoundException: rmi://127.0.0.1:1090/jmxrmi -- service jboss.naming.context.java.rmi:."127.0.0.1:1090".jmxrmi
> at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:340) [:1.6.0_26]
> at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) [:1.6.0_26]
> at com.example.JMXConnectionBean.init(JMXConnectionBean.java:28)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_26]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_26]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_26]
> at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_26]
> at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptor.java:70)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.as.ee.component.ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptor.java:53)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:44)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.as.ejb3.component.session.SessionInvocationContextInterceptor$CustomSessionInvocationContext.proceed(SessionInvocationContextInterceptor.java:126)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:211)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:313)
> at org.jboss.as.ejb3.tx.SingletonLifecycleCMTTxInterceptor.processInvocation(SingletonLifecycleCMTTxInterceptor.java:56)
> at org.jboss.as.ejb3.tx.SingletonLifecycleCMTTxInterceptor.processInvocation(SingletonLifecycleCMTTxInterceptor.java:42)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.as.ejb3.component.session.SessionInvocationContextInterceptor.processInvocation(SessionInvocationContextInterceptor.java:71)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:152)
> ... 9 more
> Caused by: javax.naming.NameNotFoundException: rmi://127.0.0.1:1090/jmxrmi -- service jboss.naming.context.java.rmi:."127.0.0.1:1090".jmxrmi
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173)
> at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:209)
> at javax.naming.InitialContext.lookup(InitialContext.java:392) [:1.6.0_26]
> at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1888) [:1.6.0_26]
> at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1858) [:1.6.0_26]
> at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:257) [:1.6.0_26]
> ... 37 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (DROOLS-710) Problem when loading a jar in kie workbench
by Nicolas Heron (JIRA)
[ https://issues.jboss.org/browse/DROOLS-710?page=com.atlassian.jira.plugin... ]
Nicolas Heron commented on DROOLS-710:
--------------------------------------
The source code of the jar is here : https://github.com/chtiJBUG/drools-platform-parent/tree/master/drools-pla...
> Problem when loading a jar in kie workbench
> --------------------------------------------
>
> Key: DROOLS-710
> URL: https://issues.jboss.org/browse/DROOLS-710
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.2.0.CR4
> Reporter: Nicolas Heron
> Assignee: Mark Proctor
> Attachments: loyalty-model-0.5.1-SNAPSHOT.jar, Problem.txt
>
>
> I am uploading that jar in the artifact repository of the kid-wb. I am using version 6.2.0.CR4.
> I have defined the variable that point to the maven installation and the maven repo as follows.
> CATALINA_OPTS="-Xms1536m -Xmx6536m -XX:NewSize=256m -XX:MaxNewSize=256m -XX:PermSize=256m -XX:MaxPermSize=556m -XX:+DisableExplicitGC -Dhibernate.dialect=org.hibernate.dialect.PostgreSQLDialect -Dorg.kie.example.repositories=/home/kie-samples -Dorg.kie.example=true -Dorg.uberfire.nio.git.daemon.host=0.0.0.0 -Dorg.guvnor.m2repo.dir=$M2_HOME -Dorg.uberfire.nio.git.dir=/home/niodir -Djava.security.auth.login.config=/home/tomcat7/apache-tomcat-7.0/conf/jaasConfig -Dbtm.root=/home/bittronix -Dbitronix.tm.configuration=/home/tomcat7/apache-tomcat-7.0/conf/btm-config.properties -Djbpm.tsr.jndi.lookup=java:comp/env/TransactionSynchroniz
> I am running on tomcat7
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (DROOLS-710) Problem when loading a jar in kie workbench
by Nicolas Heron (JIRA)
[ https://issues.jboss.org/browse/DROOLS-710?page=com.atlassian.jira.plugin... ]
Nicolas Heron updated DROOLS-710:
---------------------------------
Attachment: loyalty-model-0.5.1-SNAPSHOT.jar
> Problem when loading a jar in kie workbench
> --------------------------------------------
>
> Key: DROOLS-710
> URL: https://issues.jboss.org/browse/DROOLS-710
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.2.0.CR4
> Reporter: Nicolas Heron
> Assignee: Mark Proctor
> Attachments: loyalty-model-0.5.1-SNAPSHOT.jar, Problem.txt
>
>
> I am uploading that jar in the artifact repository of the kid-wb. I am using version 6.2.0.CR4.
> I have defined the variable that point to the maven installation and the maven repo as follows.
> CATALINA_OPTS="-Xms1536m -Xmx6536m -XX:NewSize=256m -XX:MaxNewSize=256m -XX:PermSize=256m -XX:MaxPermSize=556m -XX:+DisableExplicitGC -Dhibernate.dialect=org.hibernate.dialect.PostgreSQLDialect -Dorg.kie.example.repositories=/home/kie-samples -Dorg.kie.example=true -Dorg.uberfire.nio.git.daemon.host=0.0.0.0 -Dorg.guvnor.m2repo.dir=$M2_HOME -Dorg.uberfire.nio.git.dir=/home/niodir -Djava.security.auth.login.config=/home/tomcat7/apache-tomcat-7.0/conf/jaasConfig -Dbtm.root=/home/bittronix -Dbitronix.tm.configuration=/home/tomcat7/apache-tomcat-7.0/conf/btm-config.properties -Djbpm.tsr.jndi.lookup=java:comp/env/TransactionSynchroniz
> I am running on tomcat7
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (DROOLS-710) Problem when loading a jar in kie workbench
by Nicolas Heron (JIRA)
[ https://issues.jboss.org/browse/DROOLS-710?page=com.atlassian.jira.plugin... ]
Nicolas Heron updated DROOLS-710:
---------------------------------
Attachment: Problem.txt
Log appearing in the kie-wb screen popup
> Problem when loading a jar in kie workbench
> --------------------------------------------
>
> Key: DROOLS-710
> URL: https://issues.jboss.org/browse/DROOLS-710
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.2.0.CR4
> Reporter: Nicolas Heron
> Assignee: Mark Proctor
> Attachments: Problem.txt
>
>
> I am uploading that jar in the artifact repository of the kid-wb. I am using version 6.2.0.CR4.
> I have defined the variable that point to the maven installation and the maven repo as follows.
> CATALINA_OPTS="-Xms1536m -Xmx6536m -XX:NewSize=256m -XX:MaxNewSize=256m -XX:PermSize=256m -XX:MaxPermSize=556m -XX:+DisableExplicitGC -Dhibernate.dialect=org.hibernate.dialect.PostgreSQLDialect -Dorg.kie.example.repositories=/home/kie-samples -Dorg.kie.example=true -Dorg.uberfire.nio.git.daemon.host=0.0.0.0 -Dorg.guvnor.m2repo.dir=$M2_HOME -Dorg.uberfire.nio.git.dir=/home/niodir -Djava.security.auth.login.config=/home/tomcat7/apache-tomcat-7.0/conf/jaasConfig -Dbtm.root=/home/bittronix -Dbitronix.tm.configuration=/home/tomcat7/apache-tomcat-7.0/conf/btm-config.properties -Djbpm.tsr.jndi.lookup=java:comp/env/TransactionSynchroniz
> I am running on tomcat7
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (DROOLS-710) Problem when loading a jar in kie workbench
by Nicolas Heron (JIRA)
[ https://issues.jboss.org/browse/DROOLS-710?page=com.atlassian.jira.plugin... ]
Nicolas Heron commented on DROOLS-710:
--------------------------------------
@Nicolas,
Can you confirm the org.chtijbug.drools:drools-platform-example-loyalty:0.5.1-SNAPSHOT POM is in your $M2_HOME?
Yes it is
Here is the content of the pom.xml
-------
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.chtijbug.drools</groupId>
<artifactId>drools-platform-example-loyalty</artifactId>
<version>0.5.1-SNAPSHOT</version>
</parent>
<artifactId>loyalty-model</artifactId>
<name>demopojo</name>
<description>demopojo</description>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>2.8.1</version>
<executions>
<execution>
<id>attach-javadocs</id>
<goals>
<goal>jar</goal>
</goals>
</execution>
</executions>
<configuration>
</configuration>
</plugin>
</plugins>
</build>
<dependencies>
<dependency>
<groupId>joda-time</groupId>
<artifactId>joda-time</artifactId>
</dependency>
</dependencies>
</project>
----------
> Problem when loading a jar in kie workbench
> --------------------------------------------
>
> Key: DROOLS-710
> URL: https://issues.jboss.org/browse/DROOLS-710
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.2.0.CR4
> Reporter: Nicolas Heron
> Assignee: Mark Proctor
>
> I am uploading that jar in the artifact repository of the kid-wb. I am using version 6.2.0.CR4.
> I have defined the variable that point to the maven installation and the maven repo as follows.
> CATALINA_OPTS="-Xms1536m -Xmx6536m -XX:NewSize=256m -XX:MaxNewSize=256m -XX:PermSize=256m -XX:MaxPermSize=556m -XX:+DisableExplicitGC -Dhibernate.dialect=org.hibernate.dialect.PostgreSQLDialect -Dorg.kie.example.repositories=/home/kie-samples -Dorg.kie.example=true -Dorg.uberfire.nio.git.daemon.host=0.0.0.0 -Dorg.guvnor.m2repo.dir=$M2_HOME -Dorg.uberfire.nio.git.dir=/home/niodir -Djava.security.auth.login.config=/home/tomcat7/apache-tomcat-7.0/conf/jaasConfig -Dbtm.root=/home/bittronix -Dbitronix.tm.configuration=/home/tomcat7/apache-tomcat-7.0/conf/btm-config.properties -Djbpm.tsr.jndi.lookup=java:comp/env/TransactionSynchroniz
> I am running on tomcat7
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months