June 2007 - jboss-user - Jboss List Archives

by rcoss

Is there a way to configure a new Instance of the CMSPortlet that will browse a given CMS directory or is it only for viewing a given page? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056194#4056194 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056194

18 years, 10 months

1
0
0 / 0

[JBoss Seam] - Re: selectDate

by shane.bryzak＠jboss.com

Please open a JIRA issue for this, it should be a simple change to support it. Make sure you assign it to me. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056193#4056193 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056193

18 years, 10 months

1
0
0 / 0

[JBoss jBPM] - Re: multiple calendars

by jorges38

I also need to use multiple calendars. Is it possible? In my project I need to store national holidays as well as holiday for certain parts of the country (by state and city)...depending on the region that the process is handled the system should not count that day as a working day. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056192#4056192 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056192

18 years, 10 months

1
0
0 / 0

[JBoss Messaging] - Re: two server cluster - consumer count 2

by timfox

You haven't explained why it is a problem for you to have both connections created on the same node. If you use a connection factory with loadBalancing = true, then it will round robin the creation of the connections on the two nodes. This gives a good distribution of connections when you have many connections. I can only assume from your post that you actually want your connections always created on the same node given a specific connection factory?? In which case deploy a cf with supportsLoadBalancing = false; See the userguide for more details: http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056190#4056190 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056190

18 years, 10 months

1
0
0 / 0

[JBoss Messaging] - Messaging 1.3GA lock ups

by colomb

Apologies for the long stack trace ahead of time. We are evaluating jboss 1.3.0GA w/JBoss AS 4.2.0 and are seeing the messaging server completely lock up. New connections just hang while connecting and current connections hand while sending/recieving messages. We are only seeing this happen when stepping through code on the client side. I could see that pausing a client side app would make it lose connectivity with the server (missing pings, etc), but why is the server locking up? If anyone could provide some insight, we would greatly appreciate it. Thank you. 4:07:01,037 WARN [SimpleConnectionManager] ConnectionManager[9fa2fb] cannot look up remoting session ID a2s2w-151xj5-f3608vvm-1-f366eupl-u | 14:07:01,037 WARN [SimpleConnectionManager] A problem has been detected with the connection to remote client a2s2w-151xj5-f3608vvm-1-f366eupl-u. It is possible the client has exited without closing its connection(s) or there is a network problem. All connection resources corresponding to that client process will now be removed. | 14:07:01,037 WARN [Dispatcher] Cannot find object with id 50 to register | 14:07:01,038 ERROR [ExceptionUtil] ConnectionEndpoint[48] close [a2s31a-nkbv1l-f3666m5m-1-f366ftbi-1n] | javax.jms.IllegalStateException: Cannot find binding for topic sub with queue name: a2s31a-nkbv1l-f3666m5m-1-f366erdf-1b | at org.jboss.jms.server.endpoint.ServerConsumerEndpoint.localClose(ServerConsumerEndpoint.java:490) | at org.jboss.jms.server.endpoint.ServerSessionEndpoint.localClose(ServerSessionEndpoint.java:795) | at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.close(ServerConnectionEndpoint.java:376) | at org.jboss.jms.server.connectionmanager.SimpleConnectionManager.handleClientFailure(SimpleConnectionManager.java:192) | at org.jboss.jms.server.connectionmanager.SimpleConnectionManager.handleConnectionException(SimpleConnectionManager.java:227) | at org.jboss.remoting.ConnectionNotifier.connectionLost(ConnectionNotifier.java:45) | at org.jboss.remoting.Lease.notifyClientLost(Lease.java:211) | at org.jboss.remoting.Lease.access$300(Lease.java:39) | at org.jboss.remoting.Lease$LeaseTimerTask.run(Lease.java:248) | at java.util.TimerThread.mainLoop(Timer.java:512) | at java.util.TimerThread.run(Timer.java:462) | 14:07:01,038 ERROR [SimpleConnectionManager] Failed to close connection | javax.jms.IllegalStateException: Cannot find binding for topic sub with queue name: a2s31a-nkbv1l-f3666m5m-1-f366erdf-1b | at org.jboss.jms.server.endpoint.ServerConsumerEndpoint.localClose(ServerConsumerEndpoint.java:490) | at org.jboss.jms.server.endpoint.ServerSessionEndpoint.localClose(ServerSessionEndpoint.java:795) | at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.close(ServerConnectionEndpoint.java:376) | at org.jboss.jms.server.connectionmanager.SimpleConnectionManager.handleClientFailure(SimpleConnectionManager.java:192) | at org.jboss.jms.server.connectionmanager.SimpleConnectionManager.handleConnectionException(SimpleConnectionManager.java:227) | at org.jboss.remoting.ConnectionNotifier.connectionLost(ConnectionNotifier.java:45) | at org.jboss.remoting.Lease.notifyClientLost(Lease.java:211) | at org.jboss.remoting.Lease.access$300(Lease.java:39) | at org.jboss.remoting.Lease$LeaseTimerTask.run(Lease.java:248) | at java.util.TimerThread.mainLoop(Timer.java:512) | at java.util.TimerThread.run(Timer.java:462) | 14:07:01,038 WARN [SimpleConnectionManager] A problem has been detected with the connection to remote client a2s2w-151xj5-f3608vvm-1-f3608ynh-l. It is possible the client has exited without closing its connection(s) or there is a network problem. All connection resources corresponding to that client process will now be removed. | 14:07:01,039 WARN [SimpleConnectionManager] A problem has been detected with the connection to remote client a2s2w-151xj5-f3608vvm-1-f3608yco-h. It is possible the client has exited without closing its connection(s) or there is a network problem. All connection resources corresponding to that client process will now be removed. | 14:07:01,039 WARN [SimpleConnectionManager] A problem has been detected with the connection to remote client a2s2w-151xj5-f3608vvm-1-f3608ya3-b. It is possible the client has exited without closing its connection(s) or there is a network problem. All connection resources corresponding to that client process will now be removed. | 14:12:16,874 WARN [BisocketClientInvoker] Unable to send ping: shutting down PingTimerTask | java.net.SocketException: Broken pipe | at java.net.SocketOutputStream.socketWrite0(Native Method) | at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) | at java.net.SocketOutputStream.write(SocketOutputStream.java:115) | at org.jboss.remoting.transport.bisocket.BisocketClientInvoker$PingTimerTask.run(BisocketClientInvoker.java:497) | at java.util.TimerThread.mainLoop(Timer.java:512) | at java.util.TimerThread.run(Timer.java:462) | 14:12:26,579 WARN [SimpleConnectionManager] ConnectionManager[9fa2fb] cannot look up remoting session ID a2s2j-dflkpp-f366gqob-1-f366gsia-b | 14:12:26,579 WARN [SimpleConnectionManager] A problem has been detected with the connection to remote client a2s2j-dflkpp-f366gqob-1-f366gsia-b. It is possible the client has exited without closing its connection(s) or there is a network problem. All connection resources corresponding to that client process will now be removed. | 14:24:45,557 WARN [SimpleConnectionManager] ConnectionManager[9fa2fb] cannot look up remoting session ID a2s2w-wlnmoy-f36701d9-1-f3670vvd-m | 14:24:45,557 WARN [SimpleConnectionManager] A problem has been detected with the connection to remote client a2s2w-wlnmoy-f36701d9-1-f3670vvd-m. It is possible the client has exited without closing its connection(s) or there is a network problem. All connection resources corresponding to that client process will now be removed. | 14:25:56,702 WARN [SimpleConnectionManager] A problem has been detected with the connection to remote client a2s2w-wlnmoy-f36701d9-1-f367030j-4. It is possible the client has exited without closing its connection(s) or there is a network problem. All connection resources corresponding to that client process will now be removed. | | [cssdev@DL04_46:~]$!vi | vi MyContentGatewayClient.cpp | [cssdev@DL04_46:~]$vi /var/log/css/jboss.log | at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105) | at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$close_N4742752445160157748.invokeNext(ConnectionAdvised$close_N4742752445160157748.java) | at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.close(ConnectionAdvised.java) | at org.jboss.jms.wireformat.CloseRequest.serverInvoke(CloseRequest.java:66) | at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:141) | at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:734) | at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:560) | at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:383) | at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:165) | 14:06:36,880 WARN [BisocketClientInvoker] Unable to send ping: shutting down PingTimerTask | java.net.SocketException: Broken pipe | at java.net.SocketOutputStream.socketWrite0(Native Method) | at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) | at java.net.SocketOutputStream.write(SocketOutputStream.java:115) | at org.jboss.remoting.transport.bisocket.BisocketClientInvoker$PingTimerTask.run(BisocketClientInvoker.java:497) | at java.util.TimerThread.mainLoop(Timer.java:512) | at java.util.TimerThread.run(Timer.java:462) | 14:07:01,037 WARN [SimpleConnectionManager] ConnectionManager[9fa2fb] cannot look up remoting session ID a2s2w-151xj5-f3608vvm-1-f366eupl-u | 14:07:01,037 WARN [SimpleConnectionManager] A problem has been detected with the connection to remote client a2s2w-151xj5-f3608vvm-1-f366eupl-u. It is possible the client has exited without closing its connection(s) or there is a network problem. All connection resources corresponding to that client process will now be removed. | 14:07:01,037 WARN [Dispatcher] Cannot find object with id 50 to register | 14:07:01,038 ERROR [ExceptionUtil] ConnectionEndpoint[48] close [a2s31a-nkbv1l-f3666m5m-1-f366ftbi-1n] | javax.jms.IllegalStateException: Cannot find binding for topic sub with queue name: a2s31a-nkbv1l-f3666m5m-1-f366erdf-1b | at org.jboss.jms.server.endpoint.ServerConsumerEndpoint.localClose(ServerConsumerEndpoint.java:490) | at org.jboss.jms.server.endpoint.ServerSessionEndpoint.localClose(ServerSessionEndpoint.java:795) | at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.close(ServerConnectionEndpoint.java:376) | at org.jboss.jms.server.connectionmanager.SimpleConnectionManager.handleClientFailure(SimpleConnectionManager.java:192) | at org.jboss.jms.server.connectionmanager.SimpleConnectionManager.handleConnectionException(SimpleConnectionManager.java:227) | at org.jboss.remoting.ConnectionNotifier.connectionLost(ConnectionNotifier.java:45) | at org.jboss.remoting.Lease.notifyClientLost(Lease.java:211) | at org.jboss.remoting.Lease.access$300(Lease.java:39) | at org.jboss.remoting.Lease$LeaseTimerTask.run(Lease.java:248) | at java.util.TimerThread.mainLoop(Timer.java:512) | at java.util.TimerThread.run(Timer.java:462) | 14:07:01,038 ERROR [SimpleConnectionManager] Failed to close connection | javax.jms.IllegalStateException: Cannot find binding for topic sub with queue name: a2s31a-nkbv1l-f3666m5m-1-f366erdf-1b | at org.jboss.jms.server.endpoint.ServerConsumerEndpoint.localClose(ServerConsumerEndpoint.java:490) | at org.jboss.jms.server.endpoint.ServerSessionEndpoint.localClose(ServerSessionEndpoint.java:795) | at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.close(ServerConnectionEndpoint.java:376) | at org.jboss.jms.server.connectionmanager.SimpleConnectionManager.handleClientFailure(SimpleConnectionManager.java:192) | at org.jboss.jms.server.connectionmanager.SimpleConnectionManager.handleConnectionException(SimpleConnectionManager.java:227) | at org.jboss.remoting.ConnectionNotifier.connectionLost(ConnectionNotifier.java:45) | at org.jboss.remoting.Lease.notifyClientLost(Lease.java:211) | at org.jboss.remoting.Lease.access$300(Lease.java:39) | at org.jboss.remoting.Lease$LeaseTimerTask.run(Lease.java:248) | at java.util.TimerThread.mainLoop(Timer.java:512) | at java.util.TimerThread.run(Timer.java:462) | 14:07:01,038 WARN [SimpleConnectionManager] A problem has been detected with the connection to remote client a2s2w-151xj5-f3608vvm-1-f3608ynh-l. It is possible the client has exited without closing its connection(s) or there is a network problem. All connection resources corresponding to that client process will now be removed. | 14:07:01,039 WARN [SimpleConnectionManager] A problem has been detected with the connection to remote client a2s2w-151xj5-f3608vvm-1-f3608yco-h. It is possible the client has exited without closing its connection(s) or there is a network problem. All connection resources corresponding to that client process will now be removed. | 14:07:01,039 WARN [SimpleConnectionManager] A problem has been detected with the connection to remote client a2s2w-151xj5-f3608vvm-1-f3608ya3-b. It is possible the client has exited without closing its connection(s) or there is a network problem. All connection resources corresponding to that client process will now be removed. | 14:12:16,874 WARN [BisocketClientInvoker] Unable to send ping: shutting down PingTimerTask | java.net.SocketException: Broken pipe | at java.net.SocketOutputStream.socketWrite0(Native Method) | at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) | at java.net.SocketOutputStream.write(SocketOutputStream.java:115) | at org.jboss.remoting.transport.bisocket.BisocketClientInvoker$PingTimerTask.run(BisocketClientInvoker.java:497) | at java.util.TimerThread.mainLoop(Timer.java:512) | at java.util.TimerThread.run(Timer.java:462) | 14:12:26,579 WARN [SimpleConnectionManager] ConnectionManager[9fa2fb] cannot look up remoting session ID a2s2j-dflkpp-f366gqob-1-f366gsia-b | 14:12:26,579 WARN [SimpleConnectionManager] A problem has been detected with the connection to remote client a2s2j-dflkpp-f366gqob-1-f366gsia-b. It is possible the client has exited without closing its connection(s) or there is a network problem. All connection resources corresponding to that client process will now be removed. | 14:24:45,557 WARN [SimpleConnectionManager] ConnectionManager[9fa2fb] cannot look up remoting session ID a2s2w-wlnmoy-f36701d9-1-f3670vvd-m | 14:24:45,557 WARN [SimpleConnectionManager] A problem has been detected with the connection to remote client a2s2w-wlnmoy-f36701d9-1-f3670vvd-m. It is possible the client has exited without closing its connection(s) or there is a network problem. All connection resources corresponding to that client process will now be removed. | 14:25:56,702 WARN [SimpleConnectionManager] A problem has been detected with the connection to remote client a2s2w-wlnmoy-f36701d9-1-f367030j-4. It is possible the client has exited without closing its connection(s) or there is a network problem. All connection resources corresponding to that client process will now be removed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056189#4056189 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056189

18 years, 10 months

1
0
0 / 0

[Installation, Configuration & Deployment] - how to separate listening port on JMX console and my web app

by kaymenji

Hi All, My boss want me to do the following: access my web application through port 8080, but access JBOSS JMX console through 9090. And boss want to enable the firewall. So only open the port 8080 for users outside firewall to access my web application. And whoever want to access JBOSS JMX console have to sit inside firewall. That means I have to configure JBOSS to listening 2 different TCP port for both JMX and my application. I read a lot of jboss documents, I could not find a way to configure multiple TCP ports for different application. Currently I access JMX and my web application both through port 8080(default). For sure, I don't think I can use virtual host, that is still actually go through the same port for different applications. Can anyone give me some idea? Thanks! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056188#4056188 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056188

18 years, 10 months

1
0
0 / 0

[JBoss Seam] - selectDate

by gustavogt

Hi! I´m using a 's:selectDate' and my locale configuration is 'BR' (locale.getCountry="BR"). The firstDayofWeek returned is Monday, how can I change it to Sunday? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056186#4056186 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056186

18 years, 10 months

1
0
0 / 0

[JBoss Messaging] - Re: two server cluster - consumer count 2

by kpirkl＠elynx.com

I figured this out. My cluster has two nodes 5074 and 15446. The ClusteredConnectionFactory LoadBalancingFactory is set to the RoundRobinLoadBalancingFactory. The RoundRobinLoadBalancingPolicy walks a list of ConnectionFactoryDelegates which is sequentially ordered. Each stand alone client application gets one connection from the list. This list is ordered the same on both nodes. The result, connection always start on the same node. Question, is the list of delegates the same order on every node in the cluster if the cluster contained 5 nodes, 10 nodes? Possible solutions anyone? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056185#4056185 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056185

18 years, 10 months

1
0
0 / 0

[JBoss Portal] - Re: JBoss Portal 2.6.0 CR2 Release

by cgonzalezd

When do you the final release will go out? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056180#4056180 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056180

18 years, 10 months

1
0
0 / 0

[Persistence, JBoss/CMP, Hibernate, Database] - CMP and concurency

by olivier_etienne

Hi All, Maybe you'll find my question stupid but... I can't find the answer. In my mind, only CMP Beans can use concurency options (optimistic/pessimistic) and transaction mode definition (Required, requires, RequireNew, ...). But in the JBoss documentation (admin guide for JBos 3.2.x), they talk about "Entity beans" for these functionnalities and EntityBeans is CMP + BMP. Then, can someone confirm if these functionnalities are available on both CMP and BMP ejb ? Best regards, Olivier View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056176#4056176 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056176

18 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user June 2007