[JBoss JIRA] Created: (JBJMX-104) SNMP Adaptor doen't accept TruthValue according to SNMP v2
by Luca Stancapiano (JIRA)
SNMP Adaptor doen't accept TruthValue according to SNMP v2
----------------------------------------------------------
Key: JBJMX-104
URL: http://jira.jboss.com/jira/browse/JBJMX-104
Project: JBoss JMX
Issue Type: Patch
Environment: linux , eclipse, I'm using jboss 4.0.4-GA
Reporter: Luca Stancapiano
hi.......if you try to take a TruthValue using a MIB Browser , you receive nothing because org.jboss.jmx.adaptor.snmp.agent.RequestHandlerImpl doesn't manage booleans ....I added a patch into getValueFor method ( row 474 ) that manage it with good results. I think that setValue method doesn't need the same correction because joesnmp can simply to interpret TruthValue as SnmpStringOctet object
row 474:
else if (val instanceof Boolean)
{
Boolean in = (Boolean) val;
ssy = new SnmpOctetString(in.toString().getBytes());
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 2 months
[JBoss JIRA] Created: (JBAS-4042) Timer service fails to create TIMERS table is table exists in other schema
by Darran Lofthouse (JIRA)
Timer service fails to create TIMERS table is table exists in other schema
--------------------------------------------------------------------------
Key: JBAS-4042
URL: http://jira.jboss.com/jira/browse/JBAS-4042
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Scheduling/Timers
Affects Versions: JBossAS-4.0.4.GA
Environment: Reported against Oracle 9i
Reporter: Darran Lofthouse
Assigned To: Dimitris Andreadis
Fix For: JBossAS-4.2.1.CR1
The TIMER service does not allow the name of the table to be used by the timer service to be overriden.
To check is the table already exists the following is called: -
rs = dmd.getTables(catalog, schema, tableName, null);
return rs.next();
For the timer service no schema is specified so this returns the TIMER tables for all schemas so we do not create the table for the current schema even though it is not available.
If the table name is specified as SCHEMA_NAME.TABLE_NAME then the search will be restricted to the schema so will prevent tables from other schemas being picked up.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 2 months
[JBoss JIRA] Created: (JBAS-3953) OracleDatabasePersistencePlugin does not override selectTimers(ObjectName containerId) - selecting persisted timers fails at startup
by Gunnar von der Beck (JIRA)
OracleDatabasePersistencePlugin does not override selectTimers(ObjectName containerId) - selecting persisted timers fails at startup
------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-3953
URL: http://jira.jboss.com/jira/browse/JBAS-3953
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.4.GA
Environment: Oracle Database instead of HSQL-DB
Reporter: Gunnar von der Beck
Precondition:
-------------------
Configure the use of the OracleDatabasePersistencePlugin for EJBTimers:
<!-- A persistence policy that persistes timers to a database -->
<mbean code="org.jboss.ejb.txtimer.DatabasePersistencePolicy" name="jboss.ejb:service=EJBTimerService,persistencePolicy=database">
<!-- DataSource JNDI name -->
<depends optional-attribute-name="DataSource">jboss.jca:service=DataSourceBinding,name=DefaultDS</depends>
<!-- The plugin that handles database persistence -->
<attribute name="DatabasePersistencePlugin">org.jboss.ejb.txtimer.OracleDatabasePersistencePlugin</attribute>
</mbean>
Error:
--------
The org.jboss.ejb.txtimer.OracleDatabasePersistencePlugin extends GeneralPurposeDatabasePersistencePlugin and implements a method
public List selectTimers() throws SQLException;
In order to override the behavior of the GeneralPurposeDatabasePersistencePlugin the correct signature must be
public List selectTimers(ObjectName containerId) throws SQLException;
Hence the following exception occurs when restoring persisted timers at server startup:
2006-12-19 13:27:33,789 ERROR [org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin] Cannot deserialize
java.io.StreamCorruptedException: invalid stream header
at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:764)
at java.io.ObjectInputStream.<init>(ObjectInputStream.java:277)
at org.jboss.invocation.MarshalledValueInputStream.<init>(MarshalledValueInputStream.java:74)
at org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin.deserialize(GeneralPurposeDatabasePersistencePlugin.java:386)
at org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin.selectTimers(GeneralPurposeDatabasePersistencePlugin.java:228)
at org.jboss.ejb.txtimer.DatabasePersistencePolicy.listTimerHandles(DatabasePersistencePolicy.java:175)
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:585)
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.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy16.listTimerHandles(Unknown Source)
at org.jboss.ejb.txtimer.EJBTimerServiceImpl.restoreTimers(EJBTimerServiceImpl.java:408)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 2 months
[JBoss JIRA] Created: (JBRULES-460) Please allow ftp downloads to "resume"
by hoogenbj (JIRA)
Please allow ftp downloads to "resume"
--------------------------------------
Key: JBRULES-460
URL: http://jira.jboss.com/jira/browse/JBRULES-460
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Environment: Any
Reporter: hoogenbj
Assigned To: Mark Proctor
Priority: Minor
Hi Guys
In my part of the world (South Africa) we still get dropped connections and here a 128kbps connection counts as broadband. It is extremely &*^&^$%#$ annoying if I lose a connection while trying to download a 23MB file (JBoss Rules 3.0.4 binary with deps) and I have to start from the beginning because your ftp server does not allow "resume". (I've already made 3 attempts today)
PLEASE PLEASE PLEASE change it. Other parts of JBoss do allow it so why not you?
I'm not sure why you disallow it. Maybe you think that people multiplexing a download over multiple connections (with DAP) put too much load on the server?
Think about it: you are actually increasing the load by not allowing it, because someone like me have to make multiple attempts at downloading something before succeeding. If I have to try 3 times and come close to succeeding the first two times, it is effectively the same as three people downloading the same software. Allow resume and I'll succeed sooner and go away sooner.
Again, PUHHLEASSEEE!
Regards
Johan Hoogenboezem
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 2 months
[JBoss JIRA] Created: (JBRULES-658) Unable to invoke global variable Service from an embedded Function()
by James DePaul (JIRA)
Unable to invoke global variable Service from an embedded Function()
--------------------------------------------------------------------
Key: JBRULES-658
URL: http://jira.jboss.com/jira/browse/JBRULES-658
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Drl Parser/Builder
Environment: Windows
Reporter: James DePaul
Assigned To: Mark Proctor
Priority: Minor
Trying to invoke a service referenced in a global variable works when invoked from the <consequence> block, but NOT from the function imbeded in the Rule definition - see code sample below:
rule "Shipper Match"
salience 90
when
shipperGI : GateIn ( customerId == "NISSAN", primaryShipperId == "YELLOW" )
then
myService.sendNotification(shipperGI, Constants.SHIPPER_MATCH); // <-- This WORKS
// notifyPartNer(shipperGI, COnstants.SHIPPER_MATCH); <-- This DOES NOT work!
end
// Match found - notify customer
function void notifyPartner(GateIn _event, String _action ) {
System.out.println("Invoking Service for action = " + _action );
//myService.sendNotification(_event, _action);
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 2 months