March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPM-828) Add accessor methods to TaskNode.java

by Keen Yong (JIRA)

Add accessor methods to TaskNode.java ------------------------------------- Key: JBPM-828 URL: http://jira.jboss.com/jira/browse/JBPM-828 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Affects Versions: jBPM 3.1.3 Reporter: Keen Yong Assigned To: Tom Baeyens The TaskNode.java is missing two set accessor methods - setCreateTasks() and setSignal(). The get accessor methods are available. We need these methods to create the process definition. 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

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-4259) Include jbossws-1.2.1.GA

by Thomas Diesler (JIRA)

Include jbossws-1.2.1.GA ------------------------ Key: JBAS-4259 URL: http://jira.jboss.com/jira/browse/JBAS-4259 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: JBossAS-4.2.0.GA -- 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
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-4210) HTTP request dispatched to the wrong servlet

by Thomas Diesler (JIRA)

HTTP request dispatched to the wrong servlet -------------------------------------------- Key: JBAS-4210 URL: http://jira.jboss.com/jira/browse/JBAS-4210 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Here is a web.xml that contains more than one servlet <web-app version='2.4' xmlns='http://java.sun.com/xml/ns/j2ee' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xsi:schemaLocation='http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd'> <servlet> <servlet-name>ServletTest</servlet-name> <servlet-class>org.jboss.test.ws.jaxrpc.jbws1093.ServletTest</servlet-class> </servlet> <servlet> <servlet-name>TestEndpoint</servlet-name> <servlet-class>org.jboss.ws.integration.jboss50.JBossServiceEndpointServlet</servlet-class> <init-param> <param-name>ServiceEndpointImpl</param-name> <param-value>org.jboss.test.ws.jaxrpc.jbws1093.TestEndpointImpl</param-value> </init-param> </servlet> <servlet-mapping> <servlet-name>ServletTest</servlet-name> <url-pattern>/ServletTest</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>TestEndpoint</servlet-name> <url-pattern>/TestEndpoint</url-pattern> </servlet-mapping> </web-app> A request to http://localhost:8080/jaxrpc-jbws1093/ServletTest is incorrectly dispatched to the TestEndpoint 22:48:15,930 ERROR [[ServletTest]] Servlet.service() for servlet ServletTest threw exception org.jboss.ws.WSException: Cannot obtain endpoint for: jboss.ws:context=jaxrpc-jbws1093,endpoint=ServletTest at org.jboss.ws.core.server.AbstractServiceEndpointServlet.initServiceEndpoint(AbstractServiceEndpointServlet.java:161) at org.jboss.ws.integration.jboss50.JBossServiceEndpointServlet.initServiceEndpoint(JBossServiceEndpointServlet.java:49) at org.jboss.ws.core.server.AbstractServiceEndpointServlet.service(AbstractServiceEndpointServlet.java:73) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:228) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) To reproduce run [tdiesler@tdvaio jbossws-tests]$ ant -Dtest=org.jboss.test.ws.jaxrpc.jbws1093.JBWS1093TestCase one-test one-test: [junit] Running org.jboss.test.ws.jaxrpc.jbws1093.JBWS1093TestCase [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 6.324 sec [junit] Test org.jboss.test.ws.jaxrpc.jbws1093.JBWS1093TestCase FAILED This seems to be related to the latest updates to the tomcat service -- 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
2
0 / 0

[JBoss JIRA] Created: (JBAS-4257) Jboss fails to start with MySQL due to case sensitive issue

by Benoit Xhenseval (JIRA)

Jboss fails to start with MySQL due to case sensitive issue ----------------------------------------------------------- Key: JBAS-4257 URL: http://jira.jboss.com/jira/browse/JBAS-4257 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Scheduling/Timers Affects Versions: JBossAS-4.0.5.GA Environment: Difference between Windows and Unix based. Reporter: Benoit Xhenseval Assigned To: Dimitris Andreadis Hi, Here is a case whereby the HARDCODED table name in org.jboss.ejb.txttimer GeneralPurposeDatabasePersistencePlugin is causing a problem. Facts: --------- 1) MySQL is case SENSITIVE for database and table names under any OS, except Windows! 2) Since MySQL 4.0, all tables are created in lowercase regardless of the script 3) GeneralPurposeDatabasePersistencePlugin hardcodes the table TIMERS to be upper case. Environment: -------------------- 1) Development happens under windows, hence all tables are in lower case 'timers' 2) Deployment will be on UNIX 3) the deployment database is created from a MySQL BACKUP of a development/test environment which is under Windows. 4) For extra security, Jboss will run with a datasource that CANNOT create a table Issue: --------- * the backup will contain only lowercase tables * JBoss will try to see if table TIMERS exists but because of the case, will not find it * JBoss then tries to create it, but will not be able to do so! Resolution: ---------------- * In order to be truly portable, all scripts should use lower case for tables/databases. * Ideally externalise the creation but otherwise, just use "timers" in lowercase * Similar issue exist in the jms jboss-service.xml with JMS_MESSAGES etc. I would suggest changing the scripts to be in lower case. 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

2
1
0 / 0

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

2
6
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: (JBAS-4278) Timers: PreparedStatement.setNull() should be used for null arguments

by Alexey Loubyansky (JIRA)

Timers: PreparedStatement.setNull() should be used for null arguments --------------------------------------------------------------------- Key: JBAS-4278 URL: http://jira.jboss.com/jira/browse/JBAS-4278 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-4.2.0.CR1, JBossAS-5.0.0.Beta1, JBossAS-4.0.5.GA Reporter: Alexey Loubyansky Assigned To: Alexey Loubyansky When a timer is inserted into the database PreparedStatement.setBytes(i, bytes) is called despite the bytes sometimes may be null. This doesn't work for all databases. -- 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-702) Typo org.drools.RuleBaseConfiguration,101: drools.iassertBehaviour

by Juergen none (JIRA)

Typo org.drools.RuleBaseConfiguration,101: drools.iassertBehaviour ------------------------------------------------------------------ Key: JBRULES-702 URL: http://jira.jboss.com/jira/browse/JBRULES-702 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Reteoo Affects Versions: 3.1-m1 Reporter: Juergen none Assigned To: Mark Proctor Priority: Trivial Typo in org.drools.RuleBaseConfiguration.java, line 101: drools.iassertBehaviour 3.1-M1 -- 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: (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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2007