[JBoss JIRA] Created: (JBAS-4316) Minor bug in debug output of HAPartitionImpl.viewAccepted
by Bernd Köcke (JIRA)
Minor bug in debug output of HAPartitionImpl.viewAccepted
---------------------------------------------------------
Key: JBAS-4316
URL: http://jira.jboss.com/jira/browse/JBAS-4316
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering
Affects Versions: JBossAS-4.2.0.CR1, JBossAS-4.0.5.GA, JBossAS-4.0.4.GA, JBossAS-4.0.2 Final
Environment: Linux 2.6.x, Sun-JVM 1.5.0_11-b03, 1.6.0-b105, JBoss 4.0.2.final, but I found the same line of code in the above noted versions
Reporter: Bernd Köcke
Assigned To: Brian Stansberry
Near the end of class.method org.jboss.ha.framework.server.HAPartitionImpl.viewAccepted a debug statement prints out the size of old and new members. But this prints only the size of the new view and not the old one, because this.members and event.allMembers are filled with the list of the new view a few lines above. I will add a patch for JBoss-4.0.2.
I don't think this is a major issue, but the priority-field above is marked for committers only, so I left it untouched.
--
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
18 years, 7 months
[JBoss JIRA] Created: (JBRULES-740) IncompatibleClassChangeError working with ShadowProxy
by Dirk Bergstrom (JIRA)
IncompatibleClassChangeError working with ShadowProxy
-----------------------------------------------------
Key: JBRULES-740
URL: http://jira.jboss.com/jira/browse/JBRULES-740
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.1-m2
Environment: Trunk (revision 10170)
Reporter: Dirk Bergstrom
Assigned To: Mark Proctor
Attachments: Record.java, RLIRecord.java
I'm getting an exception while asserting objects into the working memory. Depending on the timing, I get different stacktraces leading up the same exception on the same generated class. I have 15 rules and three types of objects in the working memory. 2500 User objects, 37 Milestone objects, and 2000 RLI objects. If I assert all the Users and Milestones first, I get the first exception below during assertion of the RLI objects, at the 257th object asserted. If I arrange to skip that particular record, I can assert a few more before another record trips the bug. If I put a try/catch block around the assertion and continue after hitting an exception, I can assert about 1600 of the records successfully, and the others reliably throw (ie. if I try to assert them later). If I assert RLIs first, I get the second stacktrace during assertion of Milestones. Looks like the problem happens during execution of one or more rules. I'll attach the RLI class, and its parent class (which is also the parent of the other two classes).
Exception in thread "RLIs Processor" java.lang.IncompatibleClassChangeError
at net.juniper.dash.data.RLIRecordShadowProxy.hashCode(Unknown Source)
at java.util.HashMap.put(HashMap.java:418)
at java.util.HashSet.add(HashSet.java:194)
at org.drools.reteoo.CollectNode.assertTuple(CollectNode.java:135)
at org.drools.reteoo.CollectNode.assertObject(CollectNode.java:212)
at
org.drools.reteoo.SingleObjectSinkAdapter.propagateAssertObject(SingleObjectSinkAdapter.java:20)
at org.drools.reteoo.AlphaNode.assertObject(AlphaNode.java:145)
at
org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:304)
at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:176)
at org.drools.reteoo.Rete.assertObject(Rete.java:121)
at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:196)
at
org.drools.reteoo.ReteooWorkingMemory.doAssertObject(ReteooWorkingMemory.java:68)
at
org.drools.common.AbstractWorkingMemory.assertObject(AbstractWorkingMemory.java:729)
at
org.drools.common.AbstractWorkingMemory.assertObject(AbstractWorkingMemory.java:548)
Exception in thread "Milestones and NPI Processor" java.lang.IncompatibleClassChangeError
at net.juniper.dash.data.RLIRecordShadowProxy.hashCode(Unknown Source)
at java.util.HashMap.put(HashMap.java:418)
at java.util.HashSet.add(HashSet.java:194)
at org.drools.reteoo.CollectNode.assertTuple(CollectNode.java:135)
at org.drools.reteoo.CompositeTupleSinkAdapter.propagateAssertTuple(CompositeTupleSinkAdapter.java:30)
at org.drools.reteoo.JoinNode.assertTuple(JoinNode.java:116)
at org.drools.reteoo.SingleTupleSinkAdapter.createAndPropagateAssertTuple(SingleTupleSinkAdapter.java:55)
at org.drools.reteoo.LeftInputAdapterNode.assertObject(LeftInputAdapterNode.java:147)
at org.drools.reteoo.SingleObjectSinkAdapter.propagateAssertObject(SingleObjectSinkAdapter.java:20)
at org.drools.reteoo.AlphaNode.assertObject(AlphaNode.java:145)
at org.drools.reteoo.SingleObjectSinkAdapter.propagateAssertObject(SingleObjectSinkAdapter.java:20)
at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:176)
at org.drools.reteoo.Rete.assertObject(Rete.java:121)
at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:196)
at org.drools.reteoo.ReteooWorkingMemory.doAssertObject(ReteooWorkingMemory.java:68)
at org.drools.common.AbstractWorkingMemory.assertObject(AbstractWorkingMemory.java:729)
at org.drools.common.AbstractWorkingMemory.assertObject(AbstractWorkingMemory.java:548)
at net.juniper.dash.data.DataSource.reconcileAssertedRecords(DataSource.java:190)
at net.juniper.dash.data.DataSource.populateRecords(DataSource.java:150)
at net.juniper.dash.Updater$DataSourceProcessor.work(Updater.java:181)
at net.juniper.dash.Refresher.run(Refresher.java:70)
--
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
18 years, 7 months
[JBoss JIRA] Created: (JBMESSAGING-915) Sybase Persistence Problem - CLUSTERED is a keyword
by Radim Marek (JIRA)
Sybase Persistence Problem - CLUSTERED is a keyword
---------------------------------------------------
Key: JBMESSAGING-915
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-915
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core Persistence
Affects Versions: 1.2.0.GA
Environment: Windows XP/Linux gentoo (dev); Adaptive Server Enterprise/12.5.3/EBF 13339 ESD#7/P/x86_64/Enterprise Linux/ase1253/1951/64-bit/OPT/Fri Mar 24 00:39:11 2006; Java 5 Update 11
Reporter: Radim Marek
Assigned To: Ovidiu Feodorov
examples/config sybase-persistence-service.xml is used using CLUSTERD as column name and it's keyword in Sybase.
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.messaging:service=PostOffice
State: FAILED
Reason: com.sybase.jdbc3.jdbc.SybSQLException: Incorrect syntax near the keyword 'CLUSTERED'.
I Depend On:
jboss.messaging:service=ServerPeer
jboss.jca:service=DataSourceBinding,name=DefaultDS
jboss:service=TransactionManager
Depends On Me:
jboss.messaging.connectionfactory:service=ConnectionFactory
jboss.messaging.connectionfactory:service=NonClusteredConnectionFactory
jboss.messaging.destination:service=Queue,name=DLQ
jboss.messaging.destination:service=Queue,name=ExpiryQueue
jboss.messaging.destination:service=Topic,name=testTopic
jboss.messaging.destination:service=Topic,name=securedTopic
jboss.messaging.destination:service=Topic,name=testDurableTopic
jboss.messaging.destination:service=Queue,name=testQueue
jboss.messaging.destination:service=Queue,name=A
jboss.messaging.destination:service=Queue,name=B
jboss.messaging.destination:service=Queue,name=C
jboss.messaging.destination:service=Queue,name=D
jboss.messaging.destination:service=Queue,name=ex
jboss.messaging.destination:service=Queue,name=PrivateDLQ
jboss.messaging.destination:service=Queue,name=PrivateExpiryQueue
jboss.messaging.destination:service=Queue,name=QueueWithOwnDLQAndExpiryQueue
jboss.messaging.destination:service=Topic,name=TopicWithOwnDLQAndExpiryQueue
jboss.messaging.destination:service=Queue,name=QueueWithOwnRedeliveryDelay
jboss.messaging.destination:service=Topic,name=TopicWithOwnRedeliveryDelay
jboss.messaging.destination:service=Queue,name=testDistributedQueue
jboss.messaging.destination:service=Topic,name=testDistributedTopic
--
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
18 years, 7 months
[JBoss JIRA] Created: (HIBERNATE-61) ConcurrentModificationException when deleting persistent object with list of child-objects
by Bas Velthuizen (JIRA)
ConcurrentModificationException when deleting persistent object with list of child-objects
------------------------------------------------------------------------------------------
Key: HIBERNATE-61
URL: http://jira.jboss.com/jira/browse/HIBERNATE-61
Project: Hibernate
Issue Type: Bug
Environment: jboss-4.0.5, hibernate 3.2.3, java 1.5.10, Windows XP Pro
Reporter: Bas Velthuizen
Assigned To: Steve Ebersole
Mapping of the persistent class:
<class name="Rule" table="tbl_rule">
<id name="id" type="java.lang.Integer">
<column name="id_rule" />
<generator class="native" />
</id>
<property name="name" type="java.lang.String" access="field">
<column name="s_name" length="50" not-null="true" unique="true" />
</property>
<property name="description" type="java.lang.String">
<column name="s_description" length="255" not-null="true" default="" />
</property>
.
.
.
<list name="commands" table="tbl_command" cascade="all-delete-orphan" inverse="true" lazy="true">
<key column="id_rule" />
<list-index column="i_order" />
<one-to-many class="com.aci.rulesbase.actions.CommandAction" />
</list>.
.
.
</class>
Java code:
getSession().delete((Rule)entity);
the resulting exception is:
java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:841)
at java.util.HashMap$ValueIterator.next(HashMap.java:871)
at org.hibernate.pretty.Printer.toString(Printer.java:90)
at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:97)
at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:26)
at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000)
at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338)
at org.hibernate.transaction.CacheSynchronization.beforeCompletion(CacheSynchronization.java:59)
at org.jboss.tm.TransactionImpl.doBeforeCompletion(TransactionImpl.java:1491)
at org.jboss.tm.TransactionImpl.beforePrepare(TransactionImpl.java:1110)
at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:324)
... 49 more
I've traced the error until I came to org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions() (line 97)
Here, an iterator is created to write all actions to the log. This only happens if debug-logging is enabled for this class.
A workaround for this is to disable debug-logging in the log4J config file
--
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
18 years, 7 months