January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (GPD-11) can't install subversion plugin together with gpd

by Tom Baeyens (JIRA)

can't install subversion plugin together with gpd ------------------------------------------------- Key: GPD-11 URL: http://jira.jboss.com/jira/browse/GPD-11 Project: JBoss jBPM GPD Issue Type: Bug Reporter: Tom Baeyens Assigned To: Koen Aers Priority: Critical org.jbpm.gd.jpdl.feature (3.0.12) requires plug-in "org.apache.xerces". is the error message that i get while trying to install the subversion plugin from the update site http://subclipse.tigris.org/update_1.2.x i don't know exactly which version of the gpd is installed, but i know it's a recent one; -- 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

2
6
0 / 0

[JBoss JIRA] Updated: (JBREM-510) SSLSocketBuilder should require a SocketFactory in server mode to have a keystore.

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-510?page=all ] Tom Elrod updated JBREM-510: ----------------------------- Fix Version/s: 2.2.0.Beta2 (Boon) (was: 2.2.0.Beta1 (Bluto)) > SSLSocketBuilder should require a SocketFactory in server mode to have a keystore. > ---------------------------------------------------------------------------------- > > Key: JBREM-510 > URL: http://jira.jboss.com/jira/browse/JBREM-510 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 2.2.0.Alpha3 (Bluto) > Reporter: Ron Sigal > Assigned To: Ron Sigal > Priority: Minor > Fix For: 2.2.0.Beta2 (Boon) > > > SSLSocketBuilder needs to > 1. allow a ServerSocketFactory in client mode to not have a keystore, and > 2. require a SocketFactory in server mode to have a keystore. > Part 1 is fixed as of 6/20/06, as part of changes made for JBREM-368/JBREM-491. -- 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

1
0
0 / 0

[JBoss JIRA] Commented: (GPD-4) add support for adding Action to Nodes without adding Event

by Koen Aers (JIRA)

[ http://jira.jboss.com/jira/browse/GPD-4?page=comments#action_12351467 ] Koen Aers commented on GPD-4: ----------------------------- The feature will not be implemented in the GPD 3.0.x stream. > add support for adding Action to Nodes without adding Event > ----------------------------------------------------------- > > Key: GPD-4 > URL: http://jira.jboss.com/jira/browse/GPD-4 > Project: JBoss jBPM GPD > Issue Type: Feature Request > Components: jpdl > Affects Versions: jBPM JPDL Designer 3.0.11, jBPM JPDL Designer 3.1.0 alpha1 > Reporter: mehmet bozok > Assigned To: Koen Aers > Fix For: jBPM JPDL Designer 3.1.0.alpha2 > > > We are extending some parts of GDP in our project, and we need to add Action to Node without adding an Event then show this Aciton on outline tree view. Althought there is a mechanism to add a single Action to Nodes(not in GDP menu but implemented in > org.jbpm.ui.model.Node), it is not shown at outline tree view. In order to make Action appear on tree view as a Node child we needed to > add a menu option, and handle ActionTreeEditPart and NodeTreeEditpart relation in a different way. (not by changing GPD code, but instantiating editparts then reflecting org.eclipse.gef.AbstractEditPart and calling its protected methods which is not a very safe way.) > Therefore it seems neccesary to change iplementation so that single Action (also providing which Action to add) can be added to Node and shown in outline tree view. -- 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

1
0
0 / 0

[JBoss JIRA] Created: (GPD-22) Add graphical support for super states

by Koen Aers (JIRA)

Add graphical support for super states -------------------------------------- Key: GPD-22 URL: http://jira.jboss.com/jira/browse/GPD-22 Project: JBoss jBPM GPD Issue Type: Task Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0 alpha1 Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.alpha3 -- 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

1
3
0 / 0

[JBoss JIRA] Created: (JBAOP-349) $implements/$implementing do not work with classes in the default package

by Kabir Khan (JIRA)

$implements/$implementing do not work with classes in the default package ------------------------------------------------------------------------- Key: JBAOP-349 URL: http://jira.jboss.com/jira/browse/JBAOP-349 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.alpha2, 1.5.3.GA Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.alpha3 "execution(* $instanceof{x}->$implements{x})" does not work "execution(* $instanceof{x}->$implements{x.y})" works -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-766) Massive functional testsuite failure (108 failures, 99 errors) related to the latest remoting changes

by Ovidiu Feodorov (JIRA)

Massive functional testsuite failure (108 failures, 99 errors) related to the latest remoting changes ----------------------------------------------------------------------------------------------------- Key: JBMESSAGING-766 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-766 Project: JBoss Messaging Issue Type: Sub-task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Blocker Fix For: 1.2.0.Beta2 -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-386) On Linux running jUDDI-registry/sql/mysql/create_database.sql creates the tables in UPPER-CASE

by jarkko Lietolahti (JIRA)

On Linux running jUDDI-registry/sql/mysql/create_database.sql creates the tables in UPPER-CASE ---------------------------------------------------------------------------------------------- Key: JBESB-386 URL: http://jira.jboss.com/jira/browse/JBESB-386 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Reporter: jarkko Lietolahti Assigned To: Mark Little On Linux running jUDDI-registry/sql/mysql/create_database.sql creates the tables in UPPER-CASE, however the default juddi-ds.xml says: <check-valid-connection-sql>select count(*) from publisher</check-valid-connection-sql> which doesn't work on Linux/Unix OSes. To fix either create tables in lower case or case the check sql to use upper-case table name. <check-valid-connection-sql>select count(*) from PUBLISHER</check-valid-connection-sql> -- 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

3
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-945) Post-activation nodeActivated notification sent before node added to tree

by Brian Stansberry (JIRA)

Post-activation nodeActivated notification sent before node added to tree ------------------------------------------------------------------------- Key: JBCACHE-945 URL: http://jira.jboss.com/jira/browse/JBCACHE-945 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Cache loaders Affects Versions: 2.0.0.ALPHA2 Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 2.0.0.BETA1 CacheLoaderInterceptor.loadData is sending out a post-activation notification prematurely, before the activated node is in the tree. A listener that responds to the event by trying to read the node will generate a recursion (node not in tree, so again activated from cache loader, activation notification emitted, etc.) Solution is to emit the notifications in CacheLoaderInterceptor.loadNode, before and after the nodes are created/populated. -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBCOMMON-12) Add jdk1.6 detection in org.jboss.util.platform.Java

by Dimitris Andreadis (JIRA)

Add jdk1.6 detection in org.jboss.util.platform.Java ---------------------------------------------------- Key: JBCOMMON-12 URL: http://jira.jboss.com/jira/browse/JBCOMMON-12 Project: JBoss Common Issue Type: Feature Request Security Level: Public (Everyone can see) Components: core Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: 1.0.3.GA, 2.0.4.GA Check for the presense of java.lang.management.LockInfo, introduced in jdk1.6 -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-771) One way invocations do not return the connection to the pool

by Tim Fox (JIRA)

One way invocations do not return the connection to the pool ------------------------------------------------------------ Key: JBMESSAGING-771 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-771 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.Beta1 Reporter: Tim Fox Assigned To: Ovidiu Feodorov Priority: Blocker Fix For: 1.2.0.Beta2 When using one way invocations to delivery messages from server to client, then after sending about 50 messages, it fails, with: 16:36:34,140 TRACE @Thread-6 [ChannelSupport] Queue[0/testQueue] removing first ref in memory 16:36:34,140 TRACE @Thread-6 [ChannelSupport] Queue[0/testQueue] pushing Reference[305]:RELIABLE 16:36:34,140 TRACE @Thread-6 [ServerConsumerEndpoint] ConsumerEndpoint[8] receives Reference[305]:RELIABLE for delivery 16:36:34,140 TRACE @Thread-6 [ServerConsumerEndpoint] ConsumerEndpoint[8] has the main lock, preparing the message for delivery 16:36:34,140 TRACE @Thread-6 [ServerSessionEndpoint] SessionEndpoint[7] added delivery 50: Delivery[Reference[305]:RELIABLE](active) 16:36:34,140 TRACE @Thread-6 [ServerConsumerEndpoint] ConsumerEndpoint[8] submitting message JBossMessage[305]:PERSISTENT to the remoting layer to be sent asynchronously 16:36:34,140 DEBUG @Thread-6 [ServerInvokerCallbackHandler] ServerInvokerCallbackHandler[5c4o1b-9oatvb-ex94gcjm-1-ex94gea4-c+5c4o1b-9oatvb-ex94gcjm-1-ex94gebu-e] got PUSH callback InvocationRequest[952905] 16:36:34,140 DEBUG @Thread-6 [ServerInvokerCallbackHandler] ServerInvokerCallbackHandler[5c4o1b-9oatvb-ex94gcjm-1-ex94gea4-c+5c4o1b-9oatvb-ex94gcjm-1-ex94gebu-e] sending ASYNCHRONOUSLY the callback to the client 16:36:34,140 TRACE @Thread-6 [MicroRemoteClientInvoker] SocketClientInvoker[10d0eae, socket://192.168.1.11:2745](1) invoking InvocationRequest[b83be0] with parameter OnewayInvocation[InternalInvocation[1631573]] 16:36:34,140 TRACE @Thread-6 [MicroSocketClientInvoker] SocketClientInvoker[10d0eae, socket://192.168.1.11:2745] creating socket 49, attempt 1 16:36:34,140 TRACE @Thread-6 [SocketWrapper] creating SocketWrapper for Socket[addr=/192.168.1.11,port=2745,localport=1453], using timeout 0 16:36:34,140 TRACE @Thread-6 [MicroSocketClientInvoker] SocketClientInvoker[10d0eae, socket://192.168.1.11:2745] writing version 2 on output stream 16:36:34,140 TRACE @Thread-6 [MicroSocketClientInvoker] SocketClientInvoker[10d0eae, socket://192.168.1.11:2745] writing invocation on output stream 16:36:34,140 TRACE @Thread-6 [MicroSocketClientInvoker] SocketClientInvoker[10d0eae, socket://192.168.1.11:2745] done writing invocation on output stream 16:36:34,140 TRACE @Thread-6 [MicroSocketClientInvoker] SocketClientInvoker[10d0eae, socket://192.168.1.11:2745] sent oneway invocation, so not waiting for response, returning null 16:36:34,140 TRACE @Thread-6 [RoundRobinPointToPointRouter] receiver ConsumerEndpoint[8] handled Reference[305]:RELIABLE and returned Delivery[Reference[305]:RELIABLE](active) 16:36:34,140 TRACE @Thread-6 [ChannelSupport] Queue[0/testQueue]: Delivery[Reference[305]:RELIABLE](active) returned for message Reference[305]:RELIABLE 16:36:34,140 TRACE @Thread-6 [ChannelSupport] Queue[0/testQueue] removing first ref in memory 16:36:34,140 TRACE @Thread-6 [ChannelSupport] Queue[0/testQueue] pushing Reference[306]:RELIABLE 16:36:34,140 TRACE @Thread-6 [ServerConsumerEndpoint] ConsumerEndpoint[8] receives Reference[306]:RELIABLE for delivery 16:36:34,140 TRACE @Thread-6 [ServerConsumerEndpoint] ConsumerEndpoint[8] has the main lock, preparing the message for delivery 16:36:34,140 TRACE @Thread-6 [ServerSessionEndpoint] SessionEndpoint[7] added delivery 51: Delivery[Reference[306]:RELIABLE](active) 16:36:34,140 TRACE @Thread-6 [ServerConsumerEndpoint] ConsumerEndpoint[8] submitting message JBossMessage[306]:PERSISTENT to the remoting layer to be sent asynchronously 16:36:34,140 DEBUG @Thread-6 [ServerInvokerCallbackHandler] ServerInvokerCallbackHandler[5c4o1b-9oatvb-ex94gcjm-1-ex94gea4-c+5c4o1b-9oatvb-ex94gcjm-1-ex94gebu-e] got PUSH callback InvocationRequest[1533c8] 16:36:34,140 DEBUG @Thread-6 [ServerInvokerCallbackHandler] ServerInvokerCallbackHandler[5c4o1b-9oatvb-ex94gcjm-1-ex94gea4-c+5c4o1b-9oatvb-ex94gcjm-1-ex94gebu-e] sending ASYNCHRONOUSLY the callback to the client 16:36:34,140 TRACE @Thread-6 [MicroRemoteClientInvoker] SocketClientInvoker[10d0eae, socket://192.168.1.11:2745](1) invoking InvocationRequest[1faa614] with parameter OnewayInvocation[InternalInvocation[ad7d80]] 16:36:35,140 TRACE @Thread-6 [DefaultCallbackErrorHandler] Caught org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for locator - InvokerLocator [socket://192.168.1.11:2745/null?callbackServerHost=192.168.1.11&callbackServerPort=2745&callbackServerProtocol=socket&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&datatype=jms&serializationtype=jms&serverSocketClass=org.jboss.jms.server.remoting.ServerSocketWrapper] exception performing callback. Number of errors sending callbacks is 1 16:36:35,140 ERROR @Thread-6 [ServerInvokerCallbackHandler] Error handling callback. org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for locator - InvokerLocator [socket://192.168.1.11:2745/null?callbackServerHost=192.168.1.11&callbackServerPort=2745&callbackServerProtocol=socket&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&datatype=jms&serializationtype=jms&serverSocketClass=org.jboss.jms.server.remoting.ServerSocketWrapper] at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:328) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:118) at org.jboss.remoting.Client.invoke(Client.java:1414) at org.jboss.remoting.Client.invoke(Client.java:511) at org.jboss.remoting.Client.invokeOneway(Client.java:559) at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallback(ServerInvokerCallbackHandler.java:686) at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallbackOneway(ServerInvokerCallbackHandler.java:563) at org.jboss.jms.server.endpoint.ServerConsumerEndpoint.handle(ServerConsumerEndpoint.java:248) at org.jboss.messaging.core.local.RoundRobinPointToPointRouter.handle(RoundRobinPointToPointRouter.java:108) at org.jboss.messaging.core.ChannelSupport.deliverInternal(ChannelSupport.java:635) at org.jboss.messaging.core.ChannelSupport$InMemoryCallback.doAfterCommit(ChannelSupport.java:1199) at org.jboss.messaging.core.ChannelSupport$InMemoryCallback.run(ChannelSupport.java:1058) at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89) at java.lang.Thread.run(Thread.java:534) Caused by: java.net.SocketException: Can not obtain client socket connection from pool. Have waited 1 seconds for available connection (50 in use) at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:749) at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:324) ... 13 more Unfortunately I do not have the source code that corresponds to the version of remoting we are using, but, assuming things haven't changed too much, then it seems pretty clear why this bug is happening. MicroSocketClientInvoker::transport: There is a glaring and obvious bug here: if(metadata != null) { Object val = metadata.get(org.jboss.remoting.Client.ONEWAY_FLAG); if(val != null && val instanceof String && Boolean.valueOf((String)val).booleanValue()) { if(isTraceEnabled) { log.trace("Oneway invocation, so not waiting for response. Returning null."); } return null; } } I.e. if the invocation is one way then it just returns null immediately, WITHOUT returning the connection to the pool first!! The returning of the connection should be done in a finally block, since it needs to be done if an exception occurs as well. Doesn't remoting have stress tests that catch these kinds of things? -- 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

3
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2007