[JBoss JIRA] (AS7-3106) @WebServiceProvider annotation is not processed when implementation class loaded from dependant module
by Peter Skopek (Created) (JIRA)
@WebServiceProvider annotation is not processed when implementation class loaded from dependant module
------------------------------------------------------------------------------------------------------
Key: AS7-3106
URL: https://issues.jboss.org/browse/AS7-3106
Project: Application Server 7
Issue Type: Bug
Components: Web Services
Affects Versions: 7.1.0.Beta1b
Reporter: Peter Skopek
Assignee: Alessio Soldano
Fix For: 7.1.0.CR1
When deploying picketlink-sts.war with dependent module org.picketlink specified in META-INF/jboss-deployment-structure.xml which contains class referred to as servlet (in web.xml) annotated with @WebServiceProvider it is deployed as servlet and not as webservice.
If I copy the class file to war to WEB-INF/classes it works as expected.
See two attached .war files.
Only correct one creates following log entries:
{noformat}
17:30:33,595 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-5) Add Service
id=PicketLinkSTS
address=http://localhost:8080/picketlink-sts-correct
implementor=org.picketlink.identity.federation.core.wstrust.PicketLinkSTS
invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker
serviceName={urn:picketlink:identity-federation:sts}PicketLinkSTS
portName={urn:picketlink:identity-federation:sts}PicketLinkSTSPort
wsdlLocation=null
mtomEnabled=false
17:30:33,597 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-5) register: jboss.ws:context=picketlink-sts-correct,endpoint=PicketLinkSTS
17:30:33,859 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-5) Creating Service {urn:picketlink:identity-federation:sts}PicketLinkSTS from WSDL: WEB-INF/wsdl/PicketLinkSTS.wsdl
17:30:34,070 INFO [org.jboss.wsf.stack.cxf.transport.AddressRewritingEndpointInfo] (MSC service thread 1-5) Setting new service endpoint address in wsdl: http://localhost:8080/picketlink-sts/PicketLinkSTS
17:30:34,132 INFO [org.jboss.wsf.stack.cxf.transport.AddressRewritingEndpointInfo] (MSC service thread 1-5) Setting new service endpoint address in wsdl: http://localhost:8080/picketlink-sts-correct
17:30:34,179 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-5) Setting the server's publish address to be http://localhost:8080/picketlink-sts-correct
{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, 10 months
[JBoss JIRA] Created: (AS7-1769) Exposing deployments services through the xml deployment descriptor of the jar/sar/war/ear
by Nikos Ballas (JIRA)
Exposing deployments services through the xml deployment descriptor of the jar/sar/war/ear
------------------------------------------------------------------------------------------
Key: AS7-1769
URL: https://issues.jboss.org/browse/AS7-1769
Project: Application Server 7
Issue Type: Feature Request
Components: EJB, JPA / Hibernate
Affects Versions: 7.0.1.Final
Environment: Linux, Window, MacOS, *BSD
Reporter: Nikos Ballas
Assignee: Carlo de Wolf
Following scenario:
Web application which is assembled by 4 different jars/wars:
(1)myapp-model.jar -> contains the model + persistence.xml containing the definition of a CMT.
(2)myapp-buisness.jar -> contains buisness EJB3's Spring Beans, whatever you can think of.
(3)myapp-messaging.jar -> Contains MDB's for sending messages to several queues.
(4)myapp-console.war -> Contains the web interface of the app.
Now the -> define a dependency from a project to another to function,i.e. A->B means that A project has a dependency in B. Now the graph of dependencies between projects are:
(4)->(2)->(1).
Currently in jboss as 7 you are able to deploy your application either as module exposing several services(even though there is no clear documentation on how you do that.You follow the old way, you have to do something else?Nowhere in any documentation isn't that documented.) or you can use the deployments folder and copy everything there.Given the previous scenario if we deploy the module(2) then even if we have as dependency in the jboss-deployment-structure.xml the reference to the module(1) then we will get an exception saying that the persistence unit defined isn't accessible or undefined for the module(2). Now with the new version of jboss that allow us to manipulate the dependencies using the module mechanism and the well defined deployment and dependencies between projects it would be really useful if.
When we define a dependency from one module to another, in my example from (2)->(1), also the mcs services defined are also exported in the target deployment, thus allowing access to the pu with the name for example is deployed. I don't know if this can be applied for the module architecture also.
regards
Nick
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (JBRULES-3364) Outdated Drools 5.3.0.Final documentation
by L Carlon (JIRA)
L Carlon created JBRULES-3364:
---------------------------------
Summary: Outdated Drools 5.3.0.Final documentation
Key: JBRULES-3364
URL: https://issues.jboss.org/browse/JBRULES-3364
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-docs
Affects Versions: 5.3.0.Final
Reporter: L Carlon
Assignee: Geoffrey De Smet
Priority: Minor
Originally reported to BZ. Geoffrey, I wasn't sure who to assign this to, I hope you don't mind I gave it to you to reassign as appropriate.
Copied from BZ:
Description of problem:
Documentation for Drools 5.3.0.Final is outdated because in part Drools Expert,
section 8.6.4. The Audit View, is used outdated example about creating audit
log where deprecated RuleBase is used instead of KnowledgeBase.
Link to this documentation:
http://docs.jboss.org/drools/release/5.3.0.Final/drools-expert-docs/html/...
Version-Release number of selected component (if applicable):
Drools 5.3.0.Final Documentation
Actual results:
WorkingMemory workingMemory = ruleBase.newWorkingMemory();
// Create a new Working Memory Logger, that logs to file.
WorkingMemoryFileLogger logger = new WorkingMemoryFileLogger(workingMemory);
// An event.log file is created in the subdirectory log (which must exist)
// of the working directory.
logger.setFileName( "log/event" );
workingMemory.assertObject(...);
workingMemory.fireAllRules();
// stop logging
logger.writeToDisk();
Expected results:
...something like this...
KnowledgeBase kbase = readKnowledgeBase();
StatefulKnowledgeSession ksession = kbase.newStatefulKnowledgeSession();
KnowledgeRuntimeLogger logger =
KnowledgeRuntimeLoggerFactory.newFileLogger(ksession, "test");
ksession.insert(...);
ksession.fireAllRules();
logger.close();
--
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, 10 months
[JBoss JIRA] Created: (JBMESSAGING-1782) on cluster hiccup jbossmessaging dies
by Armin Haaf (JIRA)
on cluster hiccup jbossmessaging dies
-------------------------------------
Key: JBMESSAGING-1782
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1782
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.3.GA
Environment: jboss 5.1
jboss groups 2.6.13 GA
Reporter: Armin Haaf
Priority: Blocker
sometimes we have a problem with our cluster loosing a socket connection. Groups come up again, but messaging dies and is no longer usable on this node.
Node 1 gots suspected by node 2 (i'm not sure why). Node 1 gets removed from the cluster and trys to reconnect. Reconnect seems to work, but messaging is now dead
output from node1:
2010-01-11 04:24:17,070 ERROR [org.jgroups.blocks.ConnectionTable] [T:169] failed sending data to 10.199.12.135:7900: java.net.SocketException: Broken pipe
2010-01-11 04:24:17,072 WARN [org.jgroups.protocols.FD] [T:48734] I was suspected by 10.199.12.135:32792; ignoring the SUSPECT message and sending back a HEARTBEAT_ACK
2010-01-11 04:24:17,072 WARN [org.jgroups.protocols.FD] [T:48717] I was suspected by 10.199.12.135:32792; ignoring the SUSPECT message and sending back a HEARTBEAT_ACK
2010-01-11 04:24:17,073 WARN [org.jgroups.protocols.FD] [T:48720] I was suspected by 10.199.12.135:32792; ignoring the SUSPECT message and sending back a HEARTBEAT_ACK
2010-01-11 04:24:17,073 WARN [org.jgroups.protocols.pbcast.GMS] [T:67] I (10.199.12.134:32797) am not a member of view [10.199.12.135:32792|12] [10.199.12.135:32792], shunning myself
and leaving the group (prev_members are [10.199.12.135:32792, 10.199.12.134:32797], current view is [10.199.12.135:32792|11] [10.199.12.135:32792, 10.199.12.134:32797])
2010-01-11 04:24:17,073 WARN [org.jgroups.protocols.pbcast.GMS] [T:48721] I (10.199.12.134:32797) am not a member of view [10.199.12.135:32792|10] [10.199.12.135:32792], shunning myse
lf and leaving the group (prev_members are [10.199.12.135:32792, 10.199.12.134:32797], current view is [10.199.12.135:32792|9] [10.199.12.135:32792, 10.199.12.134:32797])
2010-01-11 04:24:17,074 WARN [org.jgroups.protocols.pbcast.GMS] [T:48719] I (10.199.12.134:32797) am not a member of view [10.199.12.135:32792|12] [10.199.12.135:32792], shunning myse
lf and leaving the group (prev_members are [10.199.12.135:32792, 10.199.12.134:32797], current view is [10.199.12.135:32792|11] [10.199.12.135:32792, 10.199.12.134:32797])
2010-01-11 04:24:17,075 ERROR [org.jgroups.protocols.UNICAST] [T:48718] 10.199.12.134:32797: sender window for 10.199.12.135:32792 not found
2010-01-11 04:24:17,585 INFO [STDOUT] [T:48741]
---------------------------------------------------------
GMS: address is 10.199.12.134:32799 (cluster=lisa2000)
---------------------------------------------------------
2010-01-11 04:24:17,591 INFO [org.jboss.ha.framework.interfaces.HAPartition.lisa2000] [T:48741] New cluster view for partition lisa2000: 11 ([10.199.12.135:1099, 10.199.12.134:1099] d
elta: 0)
2010-01-11 04:24:17,593 INFO [STDOUT] [T:48742]
---------------------------------------------------------
GMS: address is 10.199.12.134:32799 (cluster=MessagingPostOffice-CTRL)
---------------------------------------------------------
2010-01-11 04:24:17,594 INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.lisa2000] [T:101] I am (10.199.12.134:1099) received membershipChanged event:
2010-01-11 04:24:17,594 INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.lisa2000] [T:101] Dead members: 0 ([])
2010-01-11 04:24:17,594 INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.lisa2000] [T:101] New Members : 0 ([])
2010-01-11 04:24:17,594 INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.lisa2000] [T:101] All Members : 2 ([10.199.12.135:1099, 10.199.12.134:1099])
2010-01-11 04:24:17,601 INFO [STDOUT] [T:48740]
---------------------------------------------------------
GMS: address is 10.199.12.134:32799 (cluster=lisa2000-HAPartitionCache)
---------------------------------------------------------
2010-01-11 04:24:17,601 INFO [org.jboss.messaging.core.impl.postoffice.GroupMember] [T:48742] org.jboss.messaging.core.impl.postoffice.GroupMember$ControlMembershipListener@429c429c g
ot new view [10.199.12.135:32792|13] [10.199.12.135:32792, 10.199.12.134:32799], old view is [10.199.12.135:32792|11] [10.199.12.135:32792, 10.199.12.134:32797]
2010-01-11 04:24:17,601 INFO [org.jboss.messaging.core.impl.postoffice.GroupMember] [T:48742] I am (10.199.12.134:32799)
2010-01-11 04:24:17,609 INFO [org.jboss.cache.RPCManagerImpl] [T:48740] Received new cluster view: [10.199.12.135:32792|13] [10.199.12.135:32792, 10.199.12.134:32799]
2010-01-11 04:24:17,617 INFO [org.jboss.cache.statetransfer.LegacyStateTransferIntegrator] [T:48753] Using version 4096
2010-01-11 04:24:19,686 INFO [org.jboss.messaging.core.impl.postoffice.GroupMember] [T:48742] Dead members: 1 ([10.199.12.134:32797])
2010-01-11 04:24:19,686 INFO [org.jboss.messaging.core.impl.postoffice.GroupMember] [T:48742] New Members : 1 ([10.199.12.134:32799])
2010-01-11 04:24:19,686 INFO [org.jboss.messaging.core.impl.postoffice.GroupMember] [T:48742] All Members : 2 ([10.199.12.135:32792, 10.199.12.134:32799])
2010-01-11 04:24:25,437 INFO [lisa.logistics.core.ejb.CommandExecutionBean] [T:782] Execute of ping takes 10 ms.
2010-01-11 04:24:28,705 ERROR [org.jboss.messaging.util.ExceptionUtil] [T:194] ConnectionEndpoint[l26-sy0xoa4g-1-qtygu64g-qp6dlm-q3cj5a] createSessionDelegate [t26-d91xoa4g-1-qtygu64g-
qp6dlm-q3cj5a]
java.lang.IllegalStateException: Cannot find binding for queue DLQ
at org.jboss.jms.server.ServerPeer.getDefaultDLQInstance(ServerPeer.java:1254)
at org.jboss.jms.server.endpoint.ServerSessionEndpoint.<init>(ServerSessionEndpoint.java:228)
at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.createSessionDelegate(ServerConnectionEndpoint.java:249)
at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.org$jboss$jms$server$endpoint$advised$ConnectionAdvised$createSessionDelegate$aop(ConnectionAdvised.java:75)
at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$createSessionDelegate_6052335267724906805.invokeTarget(ConnectionAdvised$createSessionDelegate_6052335267724906805.ja
va)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.createSessionDelegate(ConnectionAdvised.java)
at org.jboss.jms.wireformat.ConnectionCreateSessionDelegateRequest.serverInvoke(ConnectionCreateSessionDelegateRequest.java:87)
at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:744)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:697)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:551)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232)
output from node 2:
2010-01-11 04:24:15,618 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.lisa2000] [T:46047] Suspected member: 10.199.12.134:32797
2010-01-11 04:24:15,680 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.lisa2000] [T:89] New cluster view for partition lisa2000 (id: 10, delta: -1) : [10.199.1
2.135:1099]
2010-01-11 04:24:15,681 INFO [org.jboss.cache.RPCManagerImpl] [T:89] Received new cluster view: [10.199.12.135:32792|12] [10.199.12.135:32792]
2010-01-11 04:24:15,682 INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.lisa2000] [T:106] I am (10.199.12.135:1099) received membershipChanged event:
2010-01-11 04:24:15,682 INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.lisa2000] [T:106] Dead members: 1 ([10.199.12.134:1099])
2010-01-11 04:24:15,682 INFO [org.jboss.messaging.core.impl.postoffice.GroupMember] [T:108] org.jboss.messaging.core.impl.postoffice.GroupMember$ControlMembershipListener@443
24432 got new view [10.199.12.135:32792|12] [10.199.12.135:32792], old view is [10.199.12.135:32792|11] [10.199.12.135:32792, 10.199.12.134:32797]
2010-01-11 04:24:15,682 INFO [org.jboss.messaging.core.impl.postoffice.GroupMember] [T:108] I am (10.199.12.135:32792)
2010-01-11 04:24:15,683 ERROR [org.jboss.messaging.core.impl.postoffice.GroupMember] [T:108] Caught Exception in MembershipListener
java.lang.IllegalStateException: org.jboss.messaging.core.impl.postoffice.MessagingPostOffice@2b4e2b4e cannot find node ID for address 10.199.12.134:32797
at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.nodesLeft(MessagingPostOffice.java:942)
at org.jboss.messaging.core.impl.postoffice.GroupMember$ControlMembershipListener.viewAccepted(GroupMember.java:508)
at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.handleUpEvent(MessageDispatcher.java:733)
at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:776)
at org.jgroups.JChannel.up(JChannel.java:1336)
at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:454)
at org.jgroups.protocols.pbcast.FLUSH.up(FLUSH.java:435)
at org.jgroups.protocols.pbcast.STATE_TRANSFER.up(STATE_TRANSFER.java:153)
at org.jgroups.protocols.FRAG2.up(FRAG2.java:188)
at org.jgroups.protocols.FC.up(FC.java:493)
at org.jgroups.protocols.pbcast.GMS.installView(GMS.java:543)
at org.jgroups.protocols.pbcast.CoordGmsImpl.handleViewChange(CoordGmsImpl.java:463)
at org.jgroups.protocols.pbcast.GMS.up(GMS.java:749)
at org.jgroups.protocols.VIEW_SYNC.up(VIEW_SYNC.java:192)
at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:233)
at org.jgroups.protocols.UNICAST.up(UNICAST.java:328)
at org.jgroups.protocols.pbcast.NAKACK.handleMessage(NAKACK.java:895)
at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:708)
at org.jgroups.protocols.BARRIER.up(BARRIER.java:136)
at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:167)
at org.jgroups.protocols.FD.up(FD.java:284)
at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:307)
at org.jgroups.protocols.MERGE2.up(MERGE2.java:144)
at org.jgroups.protocols.Discovery.up(Discovery.java:262)
at org.jgroups.protocols.PING.up(PING.java:273)
at org.jgroups.protocols.TP$ProtocolAdapter.up(TP.java:2315)
at org.jgroups.protocols.TP.passMessageUp(TP.java:1249)
at org.jgroups.protocols.TP.access$100(TP.java:49)
at org.jgroups.protocols.TP$1.run(TP.java:1176)
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:736)
2010-01-11 04:24:15,682 INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.lisa2000] [T:106] New Members : 0 ([])
2010-01-11 04:24:15,683 INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.lisa2000] [T:106] All Members : 1 ([10.199.12.135:1099])
2010-01-11 04:24:17,033 WARN [org.jgroups.protocols.pbcast.NAKACK] [T:46042] 10.199.12.135:32792] discarded message from non-member 10.199.12.134:32797, my view is [10.199.12
.135:32792|12] [10.199.12.135:32792]
2010-01-11 04:24:17,033 WARN [org.jgroups.protocols.pbcast.NAKACK] [T:46041] 10.199.12.135:32792] discarded message from non-member 10.199.12.134:32797, my view is [10.199.12
.135:32792|10] [10.199.12.135:32792]
2010-01-11 04:24:17,069 WARN [org.jgroups.protocols.pbcast.NAKACK] [T:46041] 10.199.12.135:32792] discarded message from non-member 10.199.12.134:32797, my view is [10.199.12
.135:32792|10] [10.199.12.135:32792]
2010-01-11 04:24:17,072 WARN [org.jgroups.protocols.pbcast.NAKACK] [T:45905] 10.199.12.135:7900] discarded message from non-member 10.199.12.134:7900, my view is [10.199.12.1
35:7900|10] [10.199.12.135:7900]
2010-01-11 04:24:17,589 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.lisa2000] [T:103] New cluster view for partition lisa2000 (id: 11, delta: 1) : [10.199.1
2.135:1099, 10.199.12.134:1099]
2010-01-11 04:24:17,589 INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.lisa2000] [T:106] I am (10.199.12.135:1099) received membershipChanged event:
2010-01-11 04:24:17,589 INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.lisa2000] [T:106] Dead members: 0 ([])
2010-01-11 04:24:17,589 INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.lisa2000] [T:106] New Members : 1 ([10.199.12.134:1099])
2010-01-11 04:24:17,589 INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.lisa2000] [T:106] All Members : 2 ([10.199.12.135:1099, 10.199.12.134:1099])
2010-01-11 04:24:17,597 INFO [org.jboss.messaging.core.impl.postoffice.GroupMember] [T:113] org.jboss.messaging.core.impl.postoffice.GroupMember$ControlMembershipListener@443
24432 got new view [10.199.12.135:32792|13] [10.199.12.135:32792, 10.199.12.134:32799], old view is [10.199.12.135:32792|12] [10.199.12.135:32792]
2010-01-11 04:24:17,597 INFO [org.jboss.messaging.core.impl.postoffice.GroupMember] [T:113] I am (10.199.12.135:32792)
2010-01-11 04:24:17,597 INFO [org.jboss.messaging.core.impl.postoffice.GroupMember] [T:113] New Members : 1 ([10.199.12.134:32799])
2010-01-11 04:24:17,597 INFO [org.jboss.messaging.core.impl.postoffice.GroupMember] [T:113] All Members : 2 ([10.199.12.135:32792, 10.199.12.134:32799])
2010-01-11 04:24:17,607 INFO [org.jboss.cache.RPCManagerImpl] [T:99] Received new cluster view: [10.199.12.135:32792|13] [10.199.12.135:32792, 10.199.12.134:32799]
2010-01-11 04:24:19,609 WARN [org.jgroups.protocols.pbcast.GMS] [T:46052] 10.199.12.135:32792 failed to collect all ACKs (1) for unicasted view [10.199.12.135:32792|13] [10.1
99.12.135:32792, 10.199.12.134:32799] after 2000ms, missing ACKs from [10.199.12.134:32799], local_addr=10.199.12.135:32792
2010-01-11 04:24:19,611 ERROR [org.jboss.messaging.core.impl.postoffice.UnbindRequest] [T:875] Failed to remove binding
java.lang.IllegalStateException: Don't know about node id: 1
at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.removeBindingFromCluster(MessagingPostOffice.java:1079)
at org.jboss.messaging.core.impl.postoffice.UnbindRequest.execute(UnbindRequest.java:61)
at org.jboss.messaging.core.impl.postoffice.GroupMember$ControlRequestHandler.handle(GroupMember.java:622)
at org.jgroups.blocks.MessageDispatcher.handle(MessageDispatcher.java:616)
at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:637)
at org.jgroups.blocks.RequestCorrelator$Request.run(RequestCorrelator.java:944)
at org.jgroups.util.ReusableThread.run(ReusableThread.java:220)
at java.lang.Thread.run(Thread.java:736)
2010-01-11 04:24:19,611 ERROR [org.jboss.messaging.core.impl.postoffice.GroupMember] [T:875] Caught Exception in RequestHandler
java.lang.Exception: Failed to remove binding
at org.jboss.messaging.core.impl.postoffice.UnbindRequest.execute(UnbindRequest.java:67)
at org.jboss.messaging.core.impl.postoffice.GroupMember$ControlRequestHandler.handle(GroupMember.java:622)
at org.jgroups.blocks.MessageDispatcher.handle(MessageDispatcher.java:616)
at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:637)
at org.jgroups.blocks.RequestCorrelator$Request.run(RequestCorrelator.java:944)
at org.jgroups.util.ReusableThread.run(ReusableThread.java:220)
at java.lang.Thread.run(Thread.java:736)
Caused by:
java.lang.IllegalStateException: Don't know about node id: 1
at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.removeBindingFromCluster(MessagingPostOffice.java:1079)
at org.jboss.messaging.core.impl.postoffice.UnbindRequest.execute(UnbindRequest.java:61)
... 6 more
2010-01-11 04:24:19,611 ERROR [org.jgroups.blocks.RequestCorrelator] [T:875] error invoking method
java.lang.IllegalStateException: Failed to remove binding
at org.jboss.messaging.core.impl.postoffice.UnbindRequest.execute(UnbindRequest.java:67)
at org.jboss.messaging.core.impl.postoffice.GroupMember$ControlRequestHandler.handle(GroupMember.java:622)
at org.jgroups.blocks.MessageDispatcher.handle(MessageDispatcher.java:616)
at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:637)
at org.jgroups.blocks.RequestCorrelator$Request.run(RequestCorrelator.java:944)
at org.jgroups.util.ReusableThread.run(ReusableThread.java:220)
at java.lang.Thread.run(Thread.java:736)
2010-01-11 04:24:19,622 ERROR [org.jboss.messaging.core.impl.postoffice.UnbindRequest] [T:875] Failed to remove binding
java.lang.IllegalStateException: Don't know about node id: 1
at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.removeBindingFromCluster(MessagingPostOffice.java:1079)
at org.jboss.messaging.core.impl.postoffice.UnbindRequest.execute(UnbindRequest.java:61)
at org.jboss.messaging.core.impl.postoffice.GroupMember$ControlRequestHandler.handle(GroupMember.java:622)
at org.jgroups.blocks.MessageDispatcher.handle(MessageDispatcher.java:616)
at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:637)
at org.jgroups.blocks.RequestCorrelator$Request.run(RequestCorrelator.java:944)
at org.jgroups.util.ReusableThread.run(ReusableThread.java:220)
at java.lang.Thread.run(Thread.java:736)
2010-01-11 04:24:19,623 ERROR [org.jboss.messaging.core.impl.postoffice.GroupMember] [T:875] Caught Exception in RequestHandler
java.lang.Exception: Failed to remove binding
at org.jboss.messaging.core.impl.postoffice.UnbindRequest.execute(UnbindRequest.java:67)
at org.jboss.messaging.core.impl.postoffice.GroupMember$ControlRequestHandler.handle(GroupMember.java:622)
at org.jgroups.blocks.MessageDispatcher.handle(MessageDispatcher.java:616)
at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:637)
at org.jgroups.blocks.RequestCorrelator$Request.run(RequestCorrelator.java:944)
at org.jgroups.util.ReusableThread.run(ReusableThread.java:220)
at java.lang.Thread.run(Thread.java:736)
Caused by:
java.lang.IllegalStateException: Don't know about node id: 1
at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.removeBindingFromCluster(MessagingPostOffice.java:1079)
at org.jboss.messaging.core.impl.postoffice.UnbindRequest.execute(UnbindRequest.java:61)
... 6 more
2010-01-11 04:24:19,623 ERROR [org.jgroups.blocks.RequestCorrelator] [T:875] error invoking method
java.lang.IllegalStateException: Failed to remove binding
at org.jboss.messaging.core.impl.postoffice.UnbindRequest.execute(UnbindRequest.java:67)
at org.jboss.messaging.core.impl.postoffice.GroupMember$ControlRequestHandler.handle(GroupMember.java:622)
at org.jgroups.blocks.MessageDispatcher.handle(MessageDispatcher.java:616)
at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:637)
at org.jgroups.blocks.RequestCorrelator$Request.run(RequestCorrelator.java:944)
at org.jgroups.util.ReusableThread.run(ReusableThread.java:220)
at java.lang.Thread.run(Thread.java:736)
2010-01-11 04:24:23,881 WARN [org.jgroups.protocols.pbcast.NAKACK] [T:46065] 10.199.12.135:7900] discarded message from non-member 10.199.12.134:7900, my view is [10.199.12.1
35:7900|10] [10.199.12.135:7900]
2010-01-11 04:24:32,813 WARN [org.jgroups.protocols.pbcast.NAKACK] [T:46065] 10.199.12.135:7900] discarded message from non-member 10.199.12.134:7900, my view is [10.199.12.1
35:7900|10] [10.199.12.135:7900]
2010-01-11 04:24:33,501 WARN [org.jgroups.protocols.pbcast.NAKACK] [T:46065] 10.199.12.135:7900] discarded message from non-member 10.199.12.134:7900, my view is [10.199.12.1
35:7900|10] [10.199.12.135:7900]
2010-01-11 04:24:45,201 WARN [org.jgroups.protocols.pbcast.NAKACK] [T:46069] 10.199.12.135:7900] discarded message from non-member 10.199.12.134:7900, my view is [10.199.12.1
35:7900|10] [10.199.12.135:7900]
2010-01-11 04:24:53,645 ERROR [org.jgroups.blocks.ConnectionTable] [T:171] failed sending data to 10.199.12.134:7900: java.net.SocketException: Socket closed
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] Created: (JGRP-1355) Enhance ExecutionRunner to allow for better extensibility and safe shut down
by William Burns (JIRA)
Enhance ExecutionRunner to allow for better extensibility and safe shut down
----------------------------------------------------------------------------
Key: JGRP-1355
URL: https://issues.jboss.org/browse/JGRP-1355
Project: JGroups
Issue Type: Enhancement
Affects Versions: 2.12.1
Reporter: William Burns
Assignee: Bela Ban
Fix For: 3.0
The ExecutionRunner class which is used for running distributed tasks currently doesn't allow for nice extensibility. This is caused due to no real hook points or callbacks to add additional local functionality if a user desires. One such functionality may be to automatically rollback or commit a local database transaction after the task is finished. This would allow for calling code to not have to care about transactional awareness and be more usuable across a target suite. Also today there is no nice way of shutting down an ExecutionRunner, it is done today purely with interrupts, and if a task is currently running this will receive an interrupt request which could be problematic. We should have a way so that when an ExecutionRunner is interrupted that it will shutdown only after finishing the current request or immediately if there is no request.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months