[JBoss JIRA] Created: (JBCACHE-975) PojoCache Collection proxy is not serializable
by Ben Wang (JIRA)
PojoCache Collection proxy is not serializable
----------------------------------------------
Key: JBCACHE-975
URL: http://jira.jboss.com/jira/browse/JBCACHE-975
Project: JBoss Cache
Issue Type: Task
Security Level: Public (Everyone can see)
Components: PojoCache
Reporter: Ben Wang
Assigned To: Ben Wang
Fix For: PojoCache
Current PojoCache2.0 uses JBossAop that introduces new dependency on other JBoss system classes. As a result, the CachedListInterceptor (of which belongs to AopProxy) is not serializalbe even by JBoss Serialization. Of course, a straightforward use of serialization with Java one would fail previously. So now, in order to replicate the list in plain Cache, a user will need to perform detach first, e.g.,
list = pcache.detach("pojo");
cache.put("key", list);
--
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
[JBoss JIRA] Created: (JBCACHE-736) PojoCache passivation failure
by Ben Wang (JIRA)
PojoCache passivation failure
-----------------------------
Key: JBCACHE-736
URL: http://jira.jboss.com/jira/browse/JBCACHE-736
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: PojoCache
Affects Versions: 1.4.0
Reporter: Ben Wang
Assigned To: Ben Wang
In release 1.4 of PojoCache, passivation won't work becuase the new AopEvictionInterceptor and that we override the evict method such that we issue recursiveEvict that in turn is doing _remove(). Becuase of this, it bypasses the passivation interceptor.
However, the fix is not so obvious. As it also involves the eviction paradigm for POJo as well. In 2.0 instead, I have opted for not to over-ride evict such that we would only support passivation on a node basis (instead of POJO). This way, passivation is transparent to the POJO level. I have a passivation package to test out these cases.
--
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
[JBoss JIRA] Created: (JBCACHE-947) Optimization in attach and detach; reduce calls to getPojo()
by Elias Ross (JIRA)
Optimization in attach and detach; reduce calls to getPojo()
------------------------------------------------------------
Key: JBCACHE-947
URL: http://jira.jboss.com/jira/browse/JBCACHE-947
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: PojoCache
Affects Versions: PojoCache
Reporter: Elias Ross
Assigned To: Ben Wang
PojoCache.attach() calls getPojo() at least three times. Once in putObjectI() to determine if the existing object is the same as the attaching object (fairly rare condition), then once again in putObjectII() (which might be redundant.) Then, it calls detach() which calls getPojo() -- see below.
I believe that simply calling pCache.detach() and returning the old value might be sufficient.
Also, detach() likewise locates the object before removal, though the removal method itself returns the original object. This is because notification includes the original object before removal. In some cases, notification may not be required. It may also be better to refactor the notification listener so that every removal doesn't require two calls to "getPojo".
I discovered this following the number of calls made in a profiler tool.
--
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
[JBoss JIRA] Created: (JBCACHE-1007) Synchronization impls should scrub state in afterCompletion
by Brian Stansberry (JIRA)
Synchronization impls should scrub state in afterCompletion
-----------------------------------------------------------
Key: JBCACHE-1007
URL: http://jira.jboss.com/jira/browse/JBCACHE-1007
Project: JBoss Cache
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Priority: Minor
Fix For: 2.0.0.CR1
I've seen cases where transaction manager's hold refs to Synchronization objects for a while after the tx commits. This can give the appearance of memory leaks if the Synchronization holds state and someone is testing for leaks of objects linked to that state. Also, a user reports that JOTM is not releasing refs to Synchronizations, thus leaking anything referred to from the Synchronization (see forum thread.)
Solution to this is to have the Synchronization clear its internal state in a finally block in afterCompletion(). Once that method executes, the state is no longer needed. See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=104067 for more on this.
If possible, it's also good to have the Synchronization impl be a static class, so there is no, for example, TxInterceptor.this ref leading back to the interceptor from TxInterceptor$RemoteSynchronizationHandler.
This is a minor issue, since if the TM does what it should and eventually drops the ref to the Synchronization, the issue cleans itself up. But clearing the Synchronization state aggressively helps avoid the appearance of leaks, and also helps unit tests that check for classloader leaks to ignore spurious stuff.
--
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
[JBoss JIRA] Created: (JBAS-4251) JMS persistance configuration for db2 (db2-jdbc2-service.xml)
by Rajesh Rajasekaran (JIRA)
JMS persistance configuration for db2 (db2-jdbc2-service.xml)
-------------------------------------------------------------
Key: JBAS-4251
URL: http://jira.jboss.com/jira/browse/JBAS-4251
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: JMS service
Reporter: Rajesh Rajasekaran
Assigned To: Adrian Brock
Fix For: JBossAS-4.2.0.GA, JBossAS-4.0.5.SP1
We need a db2-jdbc2-service.xml to be ship with jboss-4.2.x (and also jboss-4.0.x) to support DB2 databases.
To start with i copied oracle-jdbc2-service.xml to db2-jdbc2-service.xml and made a few SQL changes.
1.) With DB2 all primary keys should be explicitly mentioned NOT NULL
I added NOT NULL to TXID column.
CREATE TABLE JMS_TRANSACTIONS ( TXID INTEGER NOT NULL, PRIMARY KEY (TXID) )
WIth this persistance configurations work with DB2 8.0
2.) With DB2 7.2 the following query throws an error:
db2 => CREATE TABLE JMS_MESSAGES (MESSAGEID INTEGER NOT NULL, DESTINATION VARCHAR(150) NOT NULL, TXID INTEGER, TXOP CHAR(1), MESSAGEBLOB BLOB, PRIMARY KEY (MESSAGEID, DESTINATION))
DB21034E The command was processed as an SQL statement because it was not a
valid Command Line Processor command. During SQL processing it returned:
SQL0604N The length, precision, or scale attribute for column, distinct type,
structured type, attribute of structured type, function, or type mapping
"MESSAGEBLOB" is not valid. SQLSTATE=42611
--
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
[JBoss JIRA] Created: (JBAS-4240) SQL error in uuid-key-generator.sar jboss-service.xml against DB2 7.2
by Rajesh Rajasekaran (JIRA)
SQL error in uuid-key-generator.sar jboss-service.xml against DB2 7.2
---------------------------------------------------------------------
Key: JBAS-4240
URL: http://jira.jboss.com/jira/browse/JBAS-4240
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Rajesh Rajasekaran
Assigned To: Rajesh Rajasekaran
Fix For: JBossAS-5.0.0.Beta2, JBossAS-4.2.0.GA, JBossAS-4.0.5.SP1
The spaces at the end of each line of the SQL doesn not work with DB2 7.2
<!-- Create table DDL -->
<attribute name="CreateTableDdl">
create table HILOSEQUENCES (
SEQUENCENAME varchar(50) not null,
HIGHVALUES integer not null,
constraint hilo_pk primary key (SEQUENCENAME)
)
</attribute>
The following error occurs on server startup:
2007-03-23 14:34:47,234 DEBUG [org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory] Executing DDL: create table HILOSEQUENCES (
SEQUENCENAME varchar(50) not null,
HIGHVALUES integer not null,
constraint hilo_pk primary key (SEQUENCENAME)
)
2007-03-23 14:34:47,437 DEBUG [org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory] Starting failed jboss:service=KeyGeneratorFactory,type=HiLo
com.ibm.db2.jcc.c.SqlException: DB2 SQL error: SQLCODE: -7, SQLSTATE: 42601, SQLERRMC:
;able HILOSEQUENCES (
at com.ibm.db2.jcc.c.fg.e(fg.java:1596)
at com.ibm.db2.jcc.c.fg.b(fg.java:1160)
at com.ibm.db2.jcc.b.gb.h(gb.java:217)
at com.ibm.db2.jcc.b.gb.b(gb.java:46)
at com.ibm.db2.jcc.b.w.b(w.java:40)
at com.ibm.db2.jcc.b.vb.f(vb.java:118)
at com.ibm.db2.jcc.c.fg.m(fg.java:1155)
Going through the db2 reference says:
db2 => ? sql0007
SQL0007N The character "<character>" following "<text>" is
not valid.
Explanation: The specified "<character>" is not a valid
character in SQL statements. The "<text>" field indicates the 20
characters of the SQL statement that preceded the character that
is not valid.
Hence I am wrapping up the SQL in a single line.
However this problem does not exist with DB2 8.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
[JBoss JIRA] Created: (JBPM-896) reassign in console crashes
by Tom Baeyens (JIRA)
reassign in console crashes
---------------------------
Key: JBPM-896
URL: http://jira.jboss.com/jira/browse/JBPM-896
Project: JBoss jBPM
Issue Type: Bug
Components: Web Interface
Reporter: Tom Baeyens
Assigned To: Tom Baeyens
Fix For: jBPM jPDL 3.2
i think it will probably appear after every reassign. but in case that works, try reproducing with the following scenario:
1) start a new process instance
2) a start task instance was created for the start task
3) entered a couple of values
4) did Save and Close
5) then I was navigated to the next task
6) in that next task i did a reassign
then i got the following exception
org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: org.jbpm.taskmgmt.exe.TaskInstance.variableInstances, no session or session was closed
at org.hibernate.collection.AbstractPersistentCollection.throwLazyInitializationException(AbstractPersistentCollection.java:358)
at org.hibernate.collection.AbstractPersistentCollection.throwLazyInitializationExceptionIfNotConnected(AbstractPersistentCollection.java:350)
at org.hibernate.collection.AbstractPersistentCollection.readIndexExistence(AbstractPersistentCollection.java:115)
at org.hibernate.collection.PersistentMap.containsKey(PersistentMap.java:109)
at org.jbpm.context.exe.VariableContainer.hasVariableLocally(VariableContainer.java:119)
at org.jbpm.context.exe.VariableContainer.getVariable(VariableContainer.java:28)
at org.jbpm.context.exe.VariableContainer$$FastClassByCGLIB$$56c4a5bb.invoke(<generated>)
at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:163)
at org.jbpm.taskmgmt.exe.TaskInstance$$EnhancerByCGLIB$$32f29d9a.getVariable(<generated>)
at org.jbpm.webapp.bean.TaskInstanceVariableMap.get(TaskInstanceVariableMap.java:37)
at javax.el.MapELResolver.getValue(MapELResolver.java:157)
at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:135)
at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:64)
at com.sun.el.parser.AstValue.getValue(AstValue.java:96)
at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:183)
at com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.java:71)
at javax.faces.component.UIOutput.getValue(UIOutput.java:173)
at com.sun.faces.renderkit.html_basic.HtmlBasicInputRenderer.getValue(HtmlBasicInputRenderer.java:189)
at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.getCurrentValue(HtmlBasicRenderer.java:320)
at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeEnd(HtmlBasicRenderer.java:200)
at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:829)
at org.jbpm.webapp.tag.jbpm.ui.ComponentBase.doEncode(ComponentBase.java:48)
at org.jbpm.webapp.tag.jbpm.ui.ComponentBase.doEncode(ComponentBase.java:45)
at org.jbpm.webapp.tag.jbpm.ui.DataForm.renderCells(DataForm.java:117)
at org.jbpm.webapp.tag.jbpm.ui.DataForm.encodeChildren(DataForm.java:95)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:884)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:890)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:890)
at javax.faces.render.Renderer.encodeChildren(Renderer.java:137)
at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:810)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:884)
at javax.faces.render.Renderer.encodeChildren(Renderer.java:137)
at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:810)
at org.jbpm.webapp.tag.jbpm.ui.ComponentBase.doEncode(ComponentBase.java:33)
at org.jbpm.webapp.tag.jbpm.ui.ComponentBase.doEncode(ComponentBase.java:58)
at org.jbpm.webapp.tag.jbpm.ui.Tab.encodeChildren(Tab.java:112)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:884)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:890)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:890)
at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:578)
at org.jbpm.webapp.application.JbpmViewHandler.renderView(JbpmViewHandler.java:58)
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:106)
at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:248)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jbpm.webapp.filter.LogFilter.doFilter(LogFilter.java:59)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:595)
--
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
[JBoss JIRA] Created: (JBPM-897) add feedback when navigating to the next task
by Tom Baeyens (JIRA)
add feedback when navigating to the next task
---------------------------------------------
Key: JBPM-897
URL: http://jira.jboss.com/jira/browse/JBPM-897
Project: JBoss jBPM
Issue Type: Task
Components: Web Interface
Reporter: Tom Baeyens
Assigned To: Tom Baeyens
Fix For: jBPM jPDL 3.2
when executing the process creates a new task after a task has been closed, the console navigates to the new task. currently, i think this is too confusing as there is no feedback. saying why the user navigated to this screen instead of the task list.
i think it is better to navigate to the task list always and generate feedback saying: 'these tasks were created for you during the process execution:...' with links that can take you to these tasks.
--
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
[JBoss JIRA] Created: (JBPM-888) jBPM Suite web-console: user grover cannot login
by Arjan van Bentem (JIRA)
jBPM Suite web-console: user grover cannot login
------------------------------------------------
Key: JBPM-888
URL: http://jira.jboss.com/jira/browse/JBPM-888
Project: JBoss jBPM
Issue Type: Bug
Components: Web Interface
Affects Versions: jBPM jPDL 3.2 beta 2
Environment: All
Reporter: Arjan van Bentem
Assigned To: Tom Baeyens
Priority: Minor
The demo user "grover" cannot log into the web console.
The file \jbpm-jpdl-3.2.Beta2-suite\server\server\jbpm\data\hypersonic\jbpmDB.script holds, among many other lines:
INSERT INTO JBPM_ID_MEMBERSHIP VALUES(1,'M',NULL,NULL,2,2)
INSERT INTO JBPM_ID_MEMBERSHIP VALUES(2,'M',NULL,NULL,2,4)
INSERT INTO JBPM_ID_MEMBERSHIP VALUES(3,'M',NULL,NULL,1,4)
INSERT INTO JBPM_ID_MEMBERSHIP VALUES(4,'M',NULL,NULL,3,4)
INSERT INTO JBPM_ID_MEMBERSHIP VALUES(5,'M',NULL,NULL,3,3)
INSERT INTO JBPM_ID_MEMBERSHIP VALUES(6,'M',NULL,NULL,2,3)
INSERT INTO JBPM_ID_MEMBERSHIP VALUES(7,'M',NULL,NULL,2,5)
INSERT INTO JBPM_ID_MEMBERSHIP VALUES(8,'M',NULL,'boss',2,1)
INSERT INTO JBPM_ID_MEMBERSHIP VALUES(9,'M',NULL,NULL,1,1)
INSERT INTO JBPM_ID_USER VALUES(1,'U','cookie monster','cookie.monster(a)sesamestreet.tv','cookie monster')
INSERT INTO JBPM_ID_USER VALUES(2,'U','ernie','ernie(a)sesamestreet.tv','ernie')
INSERT INTO JBPM_ID_USER VALUES(3,'U','bert','bert(a)sesamestreet.tv','bert')
INSERT INTO JBPM_ID_USER VALUES(4,'U','grover','grover(a)sesamestreet.tv','grover')
Fix:
To allow Grover to login, this also needs
INSERT INTO JBPM_ID_MEMBERSHIP VALUES(10,'M',NULL,NULL,4,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