January 2009 - jopr-issues - Jboss List Archives

[JBoss JIRA] Created: (JOPR-59) Update JOPR public and private documentation to include guide for setting up monitoring of ESBs under JOPR for SOA

by Mark Burchard (JIRA)

Update JOPR public and private documentation to include guide for setting up monitoring of ESBs under JOPR for SOA ------------------------------------------------------------------------------------------------------------------ Key: JOPR-59 URL: https://jira.jboss.org/jira/browse/JOPR-59 Project: Jopr Issue Type: Task Environment: N/A Reporter: Mark Burchard Priority: Minor The documentation already exists: http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.GA/html-single/Ad... It just needs to be linked from or integrated into the online documentation and re-branded as JOPR. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (JOPR-38) be able to create other packages suported by JBoss AS

by Rafael Soares (JIRA)

be able to create other packages suported by JBoss AS ----------------------------------------------------- Key: JOPR-38 URL: https://jira.jboss.org/jira/browse/JOPR-38 Project: Jopr Issue Type: Feature Request Components: Plugin - JBoss AS 4, Plugin - JBoss AS 5 Affects Versions: 2.1, 2.2 Reporter: Rafael Soares Priority: Minor Be able to create other package's types supported by JBoss AS deployers like SAR, JAR, HAR, WSR, *-service.xml (for MBeans definition). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JOPR-45) be able to delete a resource deployed on JBoss AS

by Rafael Torres Coelho Soares (JIRA)

be able to delete a resource deployed on JBoss AS ------------------------------------------------- Key: JOPR-45 URL: https://jira.jboss.org/jira/browse/JOPR-45 Project: Jopr Issue Type: Feature Request Components: Plugin - JBoss AS 4, Plugin - JBoss AS 5 Environment: Jopr 2.1 JBoss AS 4.x OS Linux Debian JDK 1.5 Reporter: Rafael Torres Coelho Soares Priority: Minor Some times is necessary to delete a resource deployed on JBoss AS, for example, a DataSource or WAR/JAR/EAR package unusable. Would be nice if we could do this delete operation through Jopr UI :) Regards. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JOPR-50) Specifying wrong jnp port when connecting to JBAS doesn't prevent plugin config from being saved

by Charles Crouch (JIRA)

Specifying wrong jnp port when connecting to JBAS doesn't prevent plugin config from being saved ------------------------------------------------------------------------------------------------ Key: JOPR-50 URL: https://jira.jboss.org/jira/browse/JOPR-50 Project: Jopr Issue Type: Bug Components: Plugin - JBoss AS 4 Reporter: Charles Crouch Priority: Critical Fix For: 2.2 I thought previously we would get an exception when updating the plugin config if we couldnt connect to the server with the new settings. e.g. specifying "jnp://127.0.0.1:23499" results in "Connection properties updated. ", but no new services are discovered because we can't actually connect on that port. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JOPR-48) NPE in JBAS discovery

by Charles Crouch (JIRA)

NPE in JBAS discovery --------------------- Key: JOPR-48 URL: https://jira.jboss.org/jira/browse/JOPR-48 Project: Jopr Issue Type: Bug Components: Plugin - JBoss AS 4 Reporter: Charles Crouch Fix For: 2.2 2009-01-15 14:28:23,961 ERROR [InventoryManager.discovery-1] (org.rhq.plugins.jbossas.JBossASDiscoveryComponent)- Failed to process JBossAS command line: [/qa/tools/opt/jdk1.5.0_15/bin/java, -Dprogram.name=run.sh, -Dapp.name=rhq-server, -Xms256M, -Xmx1024M, -XX:PermSize=128M, -XX:MaxPermSize=256M, -Djava.net.preferIPv4Stack=true, -Djboss.server.log.dir=/home/jshaughn/jon-server-2.2.0-SNAPSHOT/logs, -Djava.awt.headless=true, -Djboss.platform.mbeanserver, -Dsun.lang.ClassLoader.allowArraySyntax=true, -Djava.util.logging.config.file=/server/default/conf/logging.properties, -Djava.net.preferIPv4Stack=true, -Djava.endorsed.dirs=/home/jshaughn/jon-server-2.2.0-SNAPSHOT/jbossas/lib/endorsed, -classpath, /home/jshaughn/jon-server-2.2.0-SNAPSHOT/jbossas/bin/run.jar:/qa/tools/opt/jdk1.5.0_15/lib/tools.jar, org.jboss.Main, -P, /home/jshaughn/jon-server-2.2.0-SNAPSHOT/bin/rhq-server.properties] java.lang.NullPointerException at org.rhq.plugins.jbossas.helper.JBossInstanceInfo.processJBossArgs(JBossInstanceInfo.java:163) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JOPR-49) Authentication failure error messages only captured when agent runs in debug mode

by Lami Akagwu (JIRA)

Authentication failure error messages only captured when agent runs in debug mode --------------------------------------------------------------------------------- Key: JOPR-49 URL: https://jira.jboss.org/jira/browse/JOPR-49 Project: Jopr Issue Type: Bug Components: Plugin - JBoss AS 4 Affects Versions: 2.2 Reporter: Lami Akagwu If you attempt to shutdown/start an AS instance and the login credentials are invalid, the authentication failure error messages is not captured in the agent log. The error message is only visible if the agent is run in debug mode. In addition, the operation is flagged as a success in the GUI even though it failed due to the invalid login credentials. ----------------------------------------------------------------------------- 2009-01-20 15:11:00,133 DEBUG [WorkerThread#0[127.0.0.1:49324]] (enterprise.communications.command.server.CommandProcessor)- {CommandProcessor.executed}Executed command - response is [Command Response: isSuccessful=[true]; command=[null]; results=[null]; exception=[>> exception was null <<]] 2009-01-20 15:11:00,234 DEBUG [ResourceContainer.invoker.daemon-5] (Sigar)- [cpu] HT enabled, siblings: 2 2009-01-20 15:11:00,736 DEBUG [ResourceContainer.invoker.daemon-5] (Sigar)- [cpu] HT enabled, siblings: 2 2009-01-20 15:11:00,786 DEBUG [ResourceContainer.invoker.nonDaemon-1] (org.rhq.plugins.jbossas.JBossASServerOperationsDelegate)- Exit code from process execution: 1 2009-01-20 15:11:00,789 DEBUG [ResourceContainer.invoker.nonDaemon-1] (org.rhq.plugins.jbossas.JBossASServerOperationsDelegate)- Output from process execution: ----------------------- Exception in thread "main" java.lang.SecurityException: Failed to authenticate principal=admin, securityDomain=jmx-console at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:97) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:818) at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:419) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305) at sun.rmi.transport.Transport$1.run(Transport.java:159) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:155) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:255) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142) at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source) at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133) at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365) at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197) at org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70) at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100) at $Proxy0.invoke(Unknown Source) at org.jboss.Shutdown$ServerProxyHandler.invoke(Shutdown.java:266) at $Proxy1.shutdown(Unknown Source) at org.jboss.Shutdown.main(Shutdown.java:237) ----------------------------------------------------------------------------- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JOPR-52) Jopr ask for license when I change my IP address.

by Eduardo de Moura Rodrigues (JIRA)

Jopr ask for license when I change my IP address. ------------------------------------------------- Key: JOPR-52 URL: https://jira.jboss.org/jira/browse/JOPR-52 Project: Jopr Issue Type: Bug Affects Versions: 2.1 Environment: Debian Lenny 5.0, 2.6.26-1-686 i686 GNU/Linux. Running JOPR 2.1.0 Server. Reporter: Eduardo de Moura Rodrigues Priority: Minor When I changed the server's IP address, JOPR started to ask for a valid license, I couldn't do anything else. I haven't changed anything on agents. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JOPR-58) Datasource operations should not end up in a npe when the called jmx method does not exist.

by Heiko W. Rupp (JIRA)

Datasource operations should not end up in a npe when the called jmx method does not exist. ------------------------------------------------------------------------------------------- Key: JOPR-58 URL: https://jira.jboss.org/jira/browse/JOPR-58 Project: Jopr Issue Type: Bug Components: Plugin - JBoss AS 4 Affects Versions: 2.1 Reporter: Heiko W. Rupp Assignee: Heiko W. Rupp Fix For: 2.2 See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=147861 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
2
0 / 0

[JBoss JIRA] Commented: (JOPR-5) get build numbers for rhq and jopr into about box

by John Mazzitelli (JIRA)

[ https://jira.jboss.org/jira/browse/JOPR-5?page=com.atlassian.jira.plugin.... ] John Mazzitelli commented on JOPR-5: ------------------------------------ FWIW, we currently get version info and log it like this: "16:26:08,093 INFO [CoreServer] Version=[1.2.0-SNAPSHOT], Build Number=[2807], B uild Date=[28.Jan.2009 17.28.18 EST]" This should be the RHQ-specific information. It gets this from the CoreServerMBean - the about box can get this same information from this same MBean very easily via LookupUtil.getCoreServer() - its got methods to get this version data. > get build numbers for rhq and jopr into about box > ------------------------------------------------- > > Key: JOPR-5 > URL: https://jira.jboss.org/jira/browse/JOPR-5 > Project: Jopr > Issue Type: Feature Request > Affects Versions: 2.1 > Reporter: John Mazzitelli > Assignee: Greg Hinkle > Priority: Minor > > It would be nice if the build could populate the build number that includes both the RHQ svn rev and the jopr rev. > Right now, the "about box" only shows one (I think it shows the jopr rev, but not sure). It would be nice for the about box to show something like this: > "build number: rhq=1234, jopr=23456" > this has obvious advantages (knowing the rhq rev without knowing the jopr rev is meaningless if you are trying to find out which jboss plugin code is being run, and vice versa) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JOPR-57) re-enable event collection on rhq server

by Charles Crouch (JIRA)

re-enable event collection on rhq server ---------------------------------------- Key: JOPR-57 URL: https://jira.jboss.org/jira/browse/JOPR-57 Project: Jopr Issue Type: Task Reporter: Charles Crouch Priority: Critical Fix For: 2.2 This needs to get pushed to 2.3 when that Fix Version is available. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jopr-issues January 2009