[JBoss JIRA] (AS7-5598) It must be possible to define a cluster connection without static connectors or discovery-group
by Jeff Mesnil (JIRA)
Jeff Mesnil created AS7-5598:
--------------------------------
Summary: It must be possible to define a cluster connection without static connectors or discovery-group
Key: AS7-5598
URL: https://issues.jboss.org/browse/AS7-5598
Project: Application Server 7
Issue Type: Bug
Components: JMS
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
Fix For: 7.2.0.Alpha1
I constrained the messaging subsystem to not accept a cluster-connection without either a static-connectors or a discovery-group-name.
However there is one use case where we must accept a cluster-connection without either: when a node must be part of a cluster, accepts connection but not attempts to connect to other nodes. This is shown by HornetQ clustered-static-oneway example where server3 accepts connections from server2 but does not connect to any other cluster nodes.
The constraints must be relaxed to accept a cluster connection without a static connectors or a discovery-group-ref element
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (AS7-4274) Remoting deadlock after deserialization exception of a large object graph returned from EJB.
by Daniel Bevenius (JIRA)
Daniel Bevenius created AS7-4274:
------------------------------------
Summary: Remoting deadlock after deserialization exception of a large object graph returned from EJB.
Key: AS7-4274
URL: https://issues.jboss.org/browse/AS7-4274
Project: Application Server 7
Issue Type: Bug
Components: EJB, Remoting
Affects Versions: 7.1.1.Final
Environment: JBoss AS 7.1.1.Final
Reporter: Daniel Bevenius
Assignee: jaikiran pai
The use case is a remote EJB client that calls an EJB which returns a large object graph. Due to a configuration error on our part a class that is part of this object graph is not available in the clients classpath. This causes a ClassNotFoundException to be thrown when deserializing, and after this exception is thrown the client "freezes" but can be interrupted by CTRL+C, but the server will deadlock and will not respond and has to be shutdown by killing the server process.
Below is part of the thread dump (the complete thread dump will be attached to this jira)
{noformat}
"Remoting "beve-7719" read-1" prio=5 tid=00000000028cc800 nid=0xb56ab000 waiting for monitor entry [00000000b56aa000]
java.lang.Thread.State: BLOCKED (on object monitor)
at org.xnio.streams.BufferPipeOutputStream.close(BufferPipeOutputStream.java:156)
- waiting to lock <0000000005697300> (a org.xnio.streams.BufferPipeOutputStream)
at org.xnio.IoUtils.safeClose(IoUtils.java:137)
at org.jboss.remoting3.remote.OutboundMessage.closeAsync(OutboundMessage.java:158)
at org.jboss.remoting3.remote.RemoteConnectionChannel.handleAsyncClose(RemoteConnectionChannel.java:502)
at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:259)
at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:45)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
at org.xnio.nio.NioHandle.run(NioHandle.java:90)
at org.xnio.nio.WorkerThread.run(WorkerThread.java:184)
Locked ownable synchronizers:
- None
"EJB default - 4" prio=5 tid=0000000002a10c00 nid=0xb3971000 in Object.wait() [00000000b3970000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <00000000056972d0> (a org.jboss.remoting3.remote.OutboundMessage)
at java.lang.Object.wait(Object.java:485)
at org.jboss.remoting3.remote.OutboundMessage$1.accept(OutboundMessage.java:91)
- locked <00000000056972d0> (a org.jboss.remoting3.remote.OutboundMessage)
at org.xnio.streams.BufferPipeOutputStream.send(BufferPipeOutputStream.java:125)
at org.xnio.streams.BufferPipeOutputStream.send(BufferPipeOutputStream.java:113)
at org.xnio.streams.BufferPipeOutputStream.getBuffer(BufferPipeOutputStream.java:77)
at org.xnio.streams.BufferPipeOutputStream.write(BufferPipeOutputStream.java:86)
- locked <0000000005697300> (a org.xnio.streams.BufferPipeOutputStream)
at org.jboss.remoting3.remote.OutboundMessage.write(OutboundMessage.java:168)
at java.io.DataOutputStream.write(DataOutputStream.java:71)
- locked <00000000056972b8> (a java.io.DataOutputStream)
at org.jboss.as.ejb3.remote.protocol.versionone.AbstractMessageHandler$1.write(AbstractMessageHandler.java:188)
at java.io.OutputStream.write(OutputStream.java:99)
at org.jboss.marshalling.OutputStreamByteOutput.write(OutputStreamByteOutput.java:56)
at org.jboss.marshalling.SimpleDataOutput.flush(SimpleDataOutput.java:311)
at org.jboss.marshalling.SimpleDataOutput.write(SimpleDataOutput.java:82)
at org.jboss.marshalling.river.BlockMarshaller.flush(BlockMarshaller.java:306)
at org.jboss.marshalling.river.RiverMarshaller.writeEndBlock(RiverMarshaller.java:961)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1008)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:885)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:825)
at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1063)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1019)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:885)
at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:62)
at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:119)
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.writeMethodInvocationResponse(MethodInvocationMessageHandler.java:338)
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$500(MethodInvocationMessageHandler.java:64)
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:226)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
Locked ownable synchronizers:
- <0000000008350f48> (a java.util.concurrent.locks.ReentrantLock$NonfairSync)
{noformat}
--
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
13 years, 9 months
[JBoss JIRA] (JBRULES-3634) A null pointer in DRL non-null safe navigation should clearly mention the DRL line for which it occurs
by Geoffrey De Smet (JIRA)
Geoffrey De Smet created JBRULES-3634:
-----------------------------------------
Summary: A null pointer in DRL non-null safe navigation should clearly mention the DRL line for which it occurs
Key: JBRULES-3634
URL: https://issues.jboss.org/browse/JBRULES-3634
Project: Drools
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.4.0.Final
Reporter: Geoffrey De Smet
Assignee: Mario Fusco
In a very big DRL file, there are many references like this:
{code}
when
...
Course($c : timeslot.calendarDate)
...
{code}
Now, one of them did something wrong, which one?
{code}
Exception in thread "main" java.lang.RuntimeException: cannot invoke getter: getTimeSlot [declr.class: org.Course; act.class: org.Course] (see trace)
at org.mvel2.optimizers.impl.refl.nodes.GetterAccessor.getValue(GetterAccessor.java:74)
at org.mvel2.ast.ASTNode.getReducedValueAccelerated(ASTNode.java:108)
at org.mvel2.MVELRuntime.execute(MVELRuntime.java:85)
at org.mvel2.compiler.CompiledExpression.getDirectValue(CompiledExpression.java:123)
at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:119)
at org.mvel2.MVEL.executeExpression(MVEL.java:954)
at org.drools.base.extractors.MVELClassFieldReader.getValue(MVELClassFieldReader.java:100)
at org.drools.base.extractors.BaseObjectClassFieldReader.getHashCode(BaseObjectClassFieldReader.java:204)
at org.drools.rule.Declaration.getHashCode(Declaration.java:287)
at org.drools.core.util.AbstractHashTable$DoubleCompositeIndex.hashCodeOf(AbstractHashTable.java:627)
at org.drools.core.util.index.LeftTupleIndexHashTable.removeAdd(LeftTupleIndexHashTable.java:332)
at org.drools.reteoo.JoinNode.modifyLeftTuple(JoinNode.java:310)
at org.drools.reteoo.LeftTupleSource.doModifyLeftTuple(LeftTupleSource.java:304)
at org.drools.reteoo.LeftTupleSource.modifyLeftTuple(LeftTupleSource.java:278)
at org.drools.reteoo.JoinNode.modifyLeftTuple(JoinNode.java:437)
at org.drools.reteoo.CompositeLeftTupleSinkAdapter.doPropagateModifyObject(CompositeLeftTupleSinkAdapter.java:260)
at org.drools.reteoo.CompositeLeftTupleSinkAdapter.propagateModifyObject(CompositeLeftTupleSinkAdapter.java:275)
at org.drools.reteoo.LeftInputAdapterNode.modifyObject(LeftInputAdapterNode.java:170)
at org.drools.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:507)
at org.drools.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:432)
at org.drools.reteoo.ObjectTypeNode.modifyObject(ObjectTypeNode.java:314)
at org.drools.reteoo.EntryPointNode.modifyObject(EntryPointNode.java:265)
at org.drools.common.NamedEntryPoint.update(NamedEntryPoint.java:483)
at org.drools.common.AbstractWorkingMemory.update(AbstractWorkingMemory.java:976)
at org.drools.common.AbstractWorkingMemory.update(AbstractWorkingMemory.java:949)
at org.drools.planner.core.score.director.drools.DroolsScoreDirector.afterVariableChanged(DroolsScoreDirector.java:127)
at org.UninitializerHack.changeWorkingSolution(UninitializerHack.java:16)
at org.drools.planner.core.phase.custom.DefaultCustomSolverPhase.solve(DefaultCustomSolverPhase.java:50)
at org.drools.planner.core.solver.DefaultSolver.runSolverPhases(DefaultSolver.java:190)
at org.drools.planner.core.solver.DefaultSolver.solve(DefaultSolver.java:155)
at org.drools.planner.benchmark.core.ProblemBenchmark.warmUp(ProblemBenchmark.java:161)
at org.drools.planner.benchmark.core.DefaultPlannerBenchmark.warmUp(DefaultPlannerBenchmark.java:225)
at org.drools.planner.benchmark.core.DefaultPlannerBenchmark.benchmark(DefaultPlannerBenchmark.java:172)
at org.BenchmarkerMain.main(BenchmarkerMain.java:45)
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:597)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120)
Caused by: java.lang.RuntimeException: unable to invoke method: org.TimeSlot.getCalendarDate: target of method is null
at org.mvel2.optimizers.impl.refl.nodes.GetterAccessor.getValue(GetterAccessor.java:66)
at org.mvel2.optimizers.impl.refl.nodes.GetterAccessor.getValue(GetterAccessor.java:40)
... 38 more
Caused by: java.lang.NullPointerException
at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.mvel2.optimizers.impl.refl.nodes.GetterAccessor.getValue(GetterAccessor.java:43)
... 39 more
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (SECURITY-697) Improve error message for "PB00019: Processing Failed:Unable to get Keystore: "
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/SECURITY-697?page=com.atlassian.jira.plug... ]
jaikiran pai moved AS7-5594 to SECURITY-697:
--------------------------------------------
Project: PicketBox (JBoss Security and Identity Management) (was: Application Server 7)
Key: SECURITY-697 (was: AS7-5594)
Issue Type: Enhancement (was: Feature Request)
Workflow: jira (was: GIT Pull Request workflow )
Affects Version/s: (was: 7.1.2.Final (EAP))
Component/s: (was: Security)
Security: Public
> Improve error message for "PB00019: Processing Failed:Unable to get Keystore: "
> -------------------------------------------------------------------------------
>
> Key: SECURITY-697
> URL: https://issues.jboss.org/browse/SECURITY-697
> Project: PicketBox (JBoss Security and Identity Management)
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Akram Ben Aissi
>
> The error message related to PB00019 must me more explicit.
> A special case is when the keystore URL provided to vault.sh script points to a non existing file.
> In this case, error message must explicitly state that file does not exist, or URL is not correct.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (AS7-5594) Improve error message for "PB00019: Processing Failed:Unable to get Keystore: "
by Akram Ben Aissi (JIRA)
[ https://issues.jboss.org/browse/AS7-5594?page=com.atlassian.jira.plugin.s... ]
Akram Ben Aissi moved JBPAPP-9980 to AS7-5594:
----------------------------------------------
Project: Application Server 7 (was: JBoss Enterprise Application Platform)
Key: AS7-5594 (was: JBPAPP-9980)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: 7.1.2.Final (EAP)
(was: EAP 6.0.0)
Component/s: Security
(was: Security)
Security: (was: Public)
Docs QE Status: (was: NEW)
> Improve error message for "PB00019: Processing Failed:Unable to get Keystore: "
> -------------------------------------------------------------------------------
>
> Key: AS7-5594
> URL: https://issues.jboss.org/browse/AS7-5594
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Security
> Affects Versions: 7.1.2.Final (EAP)
> Reporter: Akram Ben Aissi
>
> The error message related to PB00019 must me more explicit.
> A special case is when the keystore URL provided to vault.sh script points to a non existing file.
> In this case, error message must explicitly state that file does not exist, or URL is not correct.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (JBRULES-3632) UnsupportedOperationException on an update call
by Michal Bali (JIRA)
Michal Bali created JBRULES-3632:
------------------------------------
Summary: UnsupportedOperationException on an update call
Key: JBRULES-3632
URL: https://issues.jboss.org/browse/JBRULES-3632
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler (expert), drools-core (expert)
Affects Versions: 5.4.0.Final, 5.5.0.Beta1
Reporter: Michal Bali
Assignee: Mark Proctor
Hi,
I am getting the following exception when calling fireAllRules:
Exception executing consequence for rule "ruleThatFails" in indexingproblem.remove.me.anditworks: java.lang.UnsupportedOperationException
at org.drools.runtime.rule.impl.DefaultConsequenceExceptionHandler.handleException(DefaultConsequenceExceptionHandler.java:39)
at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:1287)
at org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1212)
at org.drools.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1446)
at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:710)
at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:674)
at org.drools.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:230)
at com.mycompany.app.IndexingProblemMain.main(IndexingProblemMain.java:36)
Caused by: java.lang.UnsupportedOperationException
at org.drools.reteoo.BaseLeftTuple.getPrevious(BaseLeftTuple.java:480)
at org.drools.core.util.index.LeftTupleList.remove(LeftTupleList.java:114)
at org.drools.core.util.index.LeftTupleList.removeAdd(LeftTupleList.java:68)
at org.drools.reteoo.JoinNode.modifyLeftTuple(JoinNode.java:310)
at org.drools.reteoo.LeftTupleSource.doModifyLeftTuple(LeftTupleSource.java:304)
at org.drools.reteoo.LeftTupleSource.modifyLeftTuple(LeftTupleSource.java:278)
at org.drools.reteoo.JoinNode.modifyLeftTuple(JoinNode.java:437)
at org.drools.reteoo.SingleLeftTupleSinkAdapter.doPropagateModifyLeftTuple(SingleLeftTupleSinkAdapter.java:205)
at org.drools.reteoo.SingleLeftTupleSinkAdapter.propagateModifyObject(SingleLeftTupleSinkAdapter.java:235)
at org.drools.reteoo.LeftInputAdapterNode.modifyObject(LeftInputAdapterNode.java:170)
at org.drools.reteoo.SingleObjectSinkAdapter.propagateModifyObject(SingleObjectSinkAdapter.java:68)
at org.drools.reteoo.AlphaNode.modifyObject(AlphaNode.java:157)
at org.drools.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:507)
at org.drools.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:421)
at org.drools.reteoo.ObjectTypeNode.modifyObject(ObjectTypeNode.java:314)
at org.drools.reteoo.EntryPointNode.modifyObject(EntryPointNode.java:265)
at org.drools.common.NamedEntryPoint.update(NamedEntryPoint.java:483)
at org.drools.common.NamedEntryPoint.update(NamedEntryPoint.java:383)
at org.drools.base.DefaultKnowledgeHelper.update(DefaultKnowledgeHelper.java:337)
at indexingproblem.remove.me.anditworks.Rule_ruleThatFails_b159773c7b1a41a2a93044d2816b96ca.defaultConsequence(Rule_ruleThatFails_b159773c7b1a41a2a93044d2816b96ca.java:9)
at indexingproblem.remove.me.anditworks.Rule_ruleThatFails_b159773c7b1a41a2a93044d2816b96caDefaultConsequenceInvokerGenerated.evaluate(Unknown Source)
at indexingproblem.remove.me.anditworks.Rule_ruleThatFails_b159773c7b1a41a2a93044d2816b96caDefaultConsequenceInvoker.evaluate(Unknown Source)
at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:1277)
... 6 more
I have tried to create a minimal test case that recreates this issue, here it is:
package indexingproblem.remove.me.anditworks;
declare Criteria
processed : boolean
end
declare CheeseCriteria extends Criteria
end
rule setUp
salience 10000
when
then
insert(new CheeseCriteria());
end
rule aaa
when
CheeseCriteria( )
then
end
rule bbb
when
CheeseCriteria( )
then
end
rule ccc
when
CheeseCriteria( )
then
end
rule eeeFalse
when
Criteria( processed == false )
then
end
declare Filter
end
rule fffTrue
when
Criteria( processed == true )
Filter( )
then
end
rule ruleThatFails
when
$criteria : Criteria( processed == false )
then
modify($criteria) {
setProcessed(true)
}
end
This is working fine with 5.3.0.Final. But it is failing with 5.4.0.Final and also 5.5.0-SNAPSHOT. Note that if you change the rule package to be "package indexingproblem" the exception is not thrown. The code for building the KnowledgeBase is standard, I haven't used any additional options. No fact is inserted only one fireAllRules call.
Thanking you.
Best regards,
Michal
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months