December 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPM-734) org.jbpm.util.XmlException: couldn't parse xml

by Ivan Garcia (JIRA)

org.jbpm.util.XmlException: couldn't parse xml ---------------------------------------------- Key: JBPM-734 URL: http://jira.jboss.com/jira/browse/JBPM-734 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.1.2 Reporter: Ivan Garcia Assigned To: Tom Baeyens This code try{ String cfg = "<jbpm-configuration>"; cfg += "</jbpm-configuration>"; jbpmConfiguration = JbpmConfiguration.parseXmlString(cfg); }catch(Exception e){ e.printStackTrace(); } launch this exception, org.jbpm.util.XmlException: couldn't parse xml at org.jbpm.util.XmlUtil.parseXmlInputSource(XmlUtil.java:78) at org.jbpm.util.XmlUtil.parseXmlResource(XmlUtil.java:60) at org.jbpm.configuration.ObjectFactoryParser.parseElementsFromResource(ObjectFactoryParser.java:104) at org.jbpm.JbpmConfiguration.parseObjectFactory(JbpmConfiguration.java:299) at org.jbpm.JbpmConfiguration.parseXmlString(JbpmConfiguration.java:318) Caused by: java.net.MalformedURLException at java.net.URL.<init>(URL.java:601) at java.net.URL.<init>(URL.java:464) at java.net.URL.<init>(URL.java:413) at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source) at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at org.jbpm.util.XmlUtil.parseXmlInputSource(XmlUtil.java:76) ... 6 more and i dont know why :-( Thanks -- 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, 3 months

4
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-622) JBossMessage.setJMSReplyTo() method does not allow to set up nulls

by Ilya Bochkov (JIRA)

JBossMessage.setJMSReplyTo() method does not allow to set up nulls ------------------------------------------------------------------ Key: JBMESSAGING-622 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-622 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.0.1.GA Reporter: Ilya Bochkov Assigned To: Ovidiu Feodorov The method body checks if a destination is an instance of JBossDestination. If you pass null then an exception is thrown, though null is a valid value. public void setJMSReplyTo(Destination replyTo) throws JMSException { if (!(replyTo instanceof JBossDestination)) { throw new InvalidDestinationException("Replyto cannot be foreign"); } this.replyToDestination = (JBossDestination)replyTo; } I've changed the method definition to: public void setJMSReplyTo(Destination replyTo) throws JMSException { if(replyTo == null){ this.replyToDestination = null; return; } if (!(replyTo instanceof JBossDestination)) { throw new InvalidDestinationException("Replyto cannot be foreign"); } this.replyToDestination = (JBossDestination)replyTo; } Please, if this is a correct fix incorporate it in future releases. Thanks! -- 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, 3 months

6
11
0 / 0

[JBoss JIRA] Created: (JBCACHE-764) Update docs, examples and tutorial to reflect 2.0.0 API

by Manik Surtani (JIRA)

Update docs, examples and tutorial to reflect 2.0.0 API ------------------------------------------------------- Key: JBCACHE-764 URL: http://jira.jboss.com/jira/browse/JBCACHE-764 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0 -- 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, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JGRP-328) MultiplexerTest.testStateTransferWithReconnect() has leftover threads if run with -Dstack=tcp

by Bela Ban (JIRA)

MultiplexerTest.testStateTransferWithReconnect() has leftover threads if run with -Dstack=tcp --------------------------------------------------------------------------------------------- Key: JGRP-328 URL: http://jira.jboss.com/jira/browse/JGRP-328 Project: JGroups Issue Type: Bug Affects Versions: 2.3 SP1 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.4 -- 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, 3 months

3
5
0 / 0

[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, 3 months

4
7
0 / 0

[JBoss JIRA] Created: (JBAS-3846) add mail.smtp.port property to mail-service.xml

by Jon Stevens (JIRA)

add mail.smtp.port property to mail-service.xml ----------------------------------------------- Key: JBAS-3846 URL: http://jira.jboss.com/jira/browse/JBAS-3846 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-4.0.5.GA Reporter: Jon Stevens Please add this line to the default mail-service.xml: <property name="mail.smtp.port" value="25"/> thanks. jon -- 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, 3 months

3
3
0 / 0

[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:  <mbean code="org.jboss.ejb.txtimer.DatabasePersistencePolicy" name="jboss.ejb:service=EJBTimerService,persistencePolicy=database">  <depends optional-attribute-name="DataSource">jboss.jca:service=DataSourceBinding,name=DefaultDS</depends>  <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, 3 months

2
4
0 / 0

[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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-469) function name overloading

by Mark Proctor (JIRA)

function name overloading ------------------------- Key: JBRULES-469 URL: http://jira.jboss.com/jira/browse/JBRULES-469 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rule Assemply/SPI Reporter: Mark Proctor Assigned To: Mark Proctor Currently the function resolver is limited with regards to overloading and you can only use the same function name once in a package. We need to have more correct overloading and ofcourse handle multiple versions of the same function name in a package. -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBSER-84) Improve serialization of immutable objects

by Michael Santos (JIRA)

Improve serialization of immutable objects ------------------------------------------ Key: JBSER-84 URL: http://jira.jboss.com/jira/browse/JBSER-84 Project: JBoss Serialization Issue Type: Feature Request Reporter: Michael Santos Assigned To: Clebert Suconic It is common for objects to contain references to hundreds or thousands of equal immutable object instances, especially java.lang.Number subclasses. Some immutable objects produce a considerable serialized amount of information, such as java.math.BigDecimal. However, there's usually no reason for different instances being used to represent the same value; they only exist due to the way they were produced (parsing &, conversion APIs and JDBC are definitely fine examples of that). Experiments on a particular project have shown replacing all these equal instances by one of them can reduce the serialized size of some objects by half. Therefore, JBoss Serialization should provide way to allow users to tell it's ok to use the same reference for all these immutable instances and which classes are to be considered immutable and replace them during the writing phase. This would be much more efficient and wouldn't require developers to rewrite their code in order to optimize serialization of some objects. A global way, such as system property, of telling the API to do this by default with the most commonly used Java SE classes would be desirable as well. -- 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, 3 months

4
7
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2006