[JBoss JIRA] (JASSIST-166) Invalid assumption involving "length" variable
by Flávio Brasil (JIRA)
Flávio Brasil created JASSIST-166:
-------------------------------------
Summary: Invalid assumption involving "length" variable
Key: JASSIST-166
URL: https://issues.jboss.org/browse/JASSIST-166
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA, 3.15.0-GA
Environment: MacBook Air
Mac OS X Lion 10.7.3 (11D50b)
Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01-415, mixed mode)
Reporter: Flávio Brasil
Assignee: Shigeru Chiba
Invalid assumption involving "length" variable. Method javassist.compiler.TypeChecker.atExpr(Expr) assumes that the variable length is a method from an array.
The problem is not reproductible with another variables names.
The main class to reproduce the bug is in the field "Steps to reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] (JGRP-1449) SEQUENCER race leads to lost messages
by David Hotham (JIRA)
David Hotham created JGRP-1449:
----------------------------------
Summary: SEQUENCER race leads to lost messages
Key: JGRP-1449
URL: https://issues.jboss.org/browse/JGRP-1449
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.9
Reporter: David Hotham
Assignee: Bela Ban
I'm seeing an issue where SEQUENCER is dropping messages, with logs like this:
2012-04-13 10:05:21.363 [Incoming-1,pisces,CFS-B-pisces-cfs02] ERROR org.jgroups.protocols.SEQUENCER - CFS-B-pisces-cfs02: non-coord; dropping FORWARD request from CFS-A-pisces-cfs03
It looks as though there's some sort of race where:
- a member ("CFS-B-pisces-cfs02") is becoming coordinator, but SEQUENCER hasn't yet seen the view change
- meanwhile some other member ("CFS-A-pisces-cfs03") has been told of the view change, and so SEQUENCER there forwards messages to the new coordinator
- but because the new coordinator doesn't yet know that it is coordinator, we hit the problem above.
The messages don't ever get retransmitted; so they're simply lost.
Here's some trace from the member who drops the message, with the line from my application showing that he does indeed become coordinator a few milliseconds later:
2012-04-13 10:05:21.363 [Incoming-1,pisces,CFS-B-pisces-cfs02] ERROR org.jgroups.protocols.SEQUENCER - CFS-B-pisces-cfs02: non-coord; dropping FORWARD request from CFS-A-pisces-cfs03
2012-04-13 10:05:21.393 [Incoming-2,pisces,CFS-B-pisces-cfs02] INFO c.m.c.CommunicatorComponent$Communicator - New view: MergeView::[CFS-B-pisces-cfs02|86] [CFS-B-pisces-cfs02, CFS-B-pisces-cfs03, CFS-A-pisces-cfs03, CFS-A-pisces-cfs02], subgroups=[CFS-A-pisces-cfs03|84] [CFS-A-pisces-cfs03, CFS-A-pisces-cfs02], [CFS-B-pisces-cfs03|85] [CFS-B-pisces-cfs03, CFS-A-pisces-cfs02, CFS-B-pisces-cfs02]
And here's trace from the other end, showing that message being broadcast in the new view.
2012-04-13 10:05:21.359 [Incoming-1,pisces,CFS-A-pisces-cfs03] INFO c.m.c.CommunicatorComponent$Communicator - New view: MergeView::[CFS-B-pisces-cfs02|86] [CFS-B-pisces-cfs02, CFS-B-pisces-cfs03, CFS-A-pisces-cfs03, CFS-A-pisces-cfs02], subgroups=[CFS-A-pisces-cfs03|84] [CFS-A-pisces-cfs03, CFS-A-pisces-cfs02], [CFS-B-pisces-cfs03|85] [CFS-B-pisces-cfs03, CFS-A-pisces-cfs02, CFS-B-pisces-cfs02]
2012-04-13 10:05:21.361 [ForkJoinPool-1-worker-0] INFO c.m.c.CommunicatorComponent$Communicator - Broadcasting ClusterMgmtMsg
I can try to get lower level trace from JGroups if that would help.
I'm using the same stack as in JGRP-1443.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (HIBERNATE-100) All versions of hibernate-tools packages are broken on eclipse-3.4
by solid Iduncare (JIRA)
All versions of hibernate-tools packages are broken on eclipse-3.4
------------------------------------------------------------------
Key: HIBERNATE-100
URL: http://jira.jboss.com/jira/browse/HIBERNATE-100
Project: Hibernate
Issue Type: Bug
Environment: Reproducable on Linux, Windows and Mac OSX
Reporter: solid Iduncare
Assigned To: Steve Ebersole
All versions of the Jboss hibernate-tools eclipse plugin fail in various ways on eclipse-3.4 (Ganymede). I have obtained various versions of the plugin via the eclipse update sites (both stable and dev) and all have various problems. I first attempted to download the latest from the stable update link (http://download.jboss.org/jbosstools/updates/stable/) . I selected the hibernate tools package for install only. It installs but is unusable. It seems to have no ill effects otherwise. When you attempt to add a hibernate configuration in the hibernate console, you get an exception similar to the followng:
java.lang.NoClassDefFoundError: org/eclipse/ui/internal/util/SWTResourceUtil
at org.hibernate.eclipse.console.workbench.xpl.AnyAdaptableLabelProvider.getImage(AnyAdaptableLabelProvider.java:166)
at org.eclipse.jface.viewers.WrappedViewerLabelProvider.getImage(WrappedViewerLabelProvider.java:117)
at org.eclipse.jface.viewers.WrappedViewerLabelProvider.update(WrappedViewerLabelProvider.java:165)
at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:145)
at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:932)
at org.eclipse.jface.viewers.AbstractTreeViewer$UpdateItemSafeRunnable.run(AbstractTreeViewer.java:102)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.runtime.Platform.run(Platform.java:880)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:1012)
at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:466)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.runtime.Platform.run(Platform.java:880)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2041)
at org.eclipse.jface.viewers.AbstractTreeViewer.createTreeItem(AbstractTreeViewer.java:827)
at org.eclipse.jface.viewers.AbstractTreeViewer.createAddedElements(AbstractTreeViewer.java:340)
at org.eclipse.jface.viewers.AbstractTreeViewer.internalAdd(AbstractTreeViewer.java:270)
at org.eclipse.jface.viewers.TreeViewer.internalAdd(TreeViewer.java:652)
at org.hibernate.eclipse.console.viewers.xpl.MTreeViewer.add(MTreeViewer.java:106)
at org.eclipse.ui.progress.DeferredTreeContentManager$3.runInUIThread(DeferredTreeContentManager.java:353)
at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:94)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3800)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
I googled this error and it brought me to a hibernate jira page hosted by atlasian. That Jira page recommended using the latest hibernate tools plugin from the dev update site(http://download.jboss.org/jbosside/hibernatetools/updates/development/) so I did. Now this is where all hell brakes loose. After installing the latest version from this site and restarting eclipse, the JEE perspective is completely disabled. JSP files open in a regular text editor and all attempts to update eclipse fail with this exception:
Cannot complete the request. See the details.
Cannot find a solution where both Match[requiredCompatibility:
org.eclipse.equinox.p2.iu/org.eclipse.emf.ecore.xml/[2.1.0,2.1.0]] and Match[requiredCompatability:
....
In short there is no usable version of hibernate tools for eclipse-3.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
14 years, 1 month
[JBoss JIRA] (AS7-4022) Add support for indexing properties to infinispan subsystem schema
by Paul Ferraro (JIRA)
Paul Ferraro created AS7-4022:
---------------------------------
Summary: Add support for indexing properties to infinispan subsystem schema
Key: AS7-4022
URL: https://issues.jboss.org/browse/AS7-4022
Project: Application Server 7
Issue Type: Feature Request
Components: Clustering
Affects Versions: 7.1.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Fix For: 7.1.1.Final
As requested by CapeDwarf team:
e.g.
<distributed-cache name="default" mode="ASYNC" batching="true" indexing="LOCAL" owners="2">
<transaction mode="NON_XA"/>
<eviction strategy="NONE"/>
<indexing>
<property name="hibernate.search.default.directory_provider">infinispan</property>
<property name="hibernate.search.default.worker.backend">jgroupsMaster</property>
</properties>
</indexing>
</distributed-cache>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (AS7-947) server:reload() exception
by Heiko Braun (JIRA)
server:reload() exception
-------------------------
Key: AS7-947
URL: https://issues.jboss.org/browse/AS7-947
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Reporter: Heiko Braun
Assignee: Brian Stansberry
Priority: Critical
Fix For: 7.0.0.CR1
Reloading yields an exception:
/host=local/server=server-one:reload
{noformat}
[Host Controller] 12:32:50,188 ERROR [org.jboss.as.host.controller] (pool-1-thread-24) Could not start server Server:server-one: java.lang.IllegalArgumentException: A node is already registered at '(server => server-one)'
[Host Controller] at org.jboss.as.controller.registry.NodeSubregistry.registerProxyController(NodeSubregistry.java:89) [jboss-as-controller-7.0.0.Beta4-SNAPSHOT.jar:7.0.0.Beta4-SNAPSHOT]
{noformat}
A second operation request results in "broken pipe":
{noformat}
[Host Controller] 12:33:03,025 ERROR [org.jboss.as.protocol] (ModelControllerClient-thread - 1) Failed to close resource org.jboss.as.protocol.SimpleByteDataOutput@37c398e: java.net.SocketException: Broken pipe
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] (AS7-3615) CLI: xa-data-source add command does not allow to specify xa-datasource-properties
by Dominik Pospisil (JIRA)
Dominik Pospisil created AS7-3615:
-------------------------------------
Summary: CLI: xa-data-source add command does not allow to specify xa-datasource-properties
Key: AS7-3615
URL: https://issues.jboss.org/browse/AS7-3615
Project: Application Server 7
Issue Type: Bug
Components: CLI
Affects Versions: 7.1.0.Final
Reporter: Dominik Pospisil
Assignee: Alexey Loubyansky
It seems that CLI xa-data-source add command does not allow to specify xa-datasource-properties. As having non empty xa-tadasource-properties map is mandatory, enabling such datasource fails:
[standalone@localhost:9999 xa-datasource-properties] xa-data-source add --name=TestXADS --jndi-name=java:jboss/datasources/TestXADS --driver-name=h2
[standalone@localhost:9999 xa-datasource-properties] xa-data-source enable --name=TestXADS
JBAS014750: Operation handler failed to complete
Server exception:
15:54:56,948 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC00001: Failed to start service jboss.data-source.java:jboss/datasources/TestXADS: org.jboss.msc.service.StartException in service jboss.data-source.java:jboss/datasources/TestXADS: JBAS010433: Error during the deployment of TestXADS
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:118)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.7.0_b147-icedtea]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.7.0_b147-icedtea]
at java.lang.Thread.run(Thread.java:722) [:1.7.0_b147-icedtea]
Caused by: org.jboss.jca.common.api.validator.ValidateException: IJ010069: Missing required element xa-datasource-property in org.jboss.jca.common.metadata.ds.XADataSourceImpl
at org.jboss.jca.common.metadata.ds.XADataSourceImpl.validate(XADataSourceImpl.java:384)
at org.jboss.jca.common.metadata.ds.XADataSourceImpl.<init>(XADataSourceImpl.java:115)
at org.jboss.as.connector.subsystems.datasources.ModifiableXaDataSource.getUnModifiableInstance(ModifiableXaDataSource.java:372)
at org.jboss.as.connector.subsystems.datasources.XaDataSourceService.getDeployer(XaDataSourceService.java:66)
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:111)
... 5 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month