[Installation, Configuration & DEPLOYMENT] - Re: How to run multiple instances of JBoss on a single syste
by mheidt
And what about running this as a service?
AS 4.2.1.GA
run
run -c port80
runs in parallel within consoles.
I make a second service.bat (service80.bat) and changed it:
set SVCNAME=JBAS42SVC80
set SVCDISP=JBoss Application Server 4.2 Port 80
set SVCDESC=JBoss Application Server 4.2 Port 80
| :cmdInstall
| jbosssvc.exe -iwdc %SVCNAME% "%DIRNAME%" "%SVCDISP%" "%SVCDESC%" service80.bat
|
| :cmdStart
| REM Executed on service start
| call run.bat -c port80 >run.log
| goto cmdEnd
|
and installed it via
service80.bat install
The services got installed and either of them starts up.
But not both of them in parallel.
When starting the second one, I get a
anonymous wrote : The JBoss Application Server 4.2 Port 80 service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service.
|
Or when I do a "service80.bat start" I get
anonymous wrote : The process cannot access the file because it is being used by another process
|
Creating a second run.bat (run80.bat) instead of the parameter "-c port 80" failed with the same errors.
??????
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150709#4150709
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150709
18 years, 1 month
[JBoss Cache: Core Edition] - Re: Remoting On Existing POJO Channel
by kblanken
No view change messages. I've seen them before using the multiplexer, but not now:
[5/14/08 12:48:16:183 CEST] 00000028 TreeCache I org.jboss.cache.TreeCache _createService channel is already running
| [5/14/08 12:48:16:215 CEST] 00000029 UDP I org.jgroups.protocols.UDP createSockets sockets will use interface 80.253.209.188
| [5/14/08 12:48:16:230 CEST] 00000029 UDP I org.jgroups.protocols.UDP createSockets socket information:
| local_addr=80.253.209.188:4786, mcast_addr=234.56.78.90:48866, bind_addr=/80.253.209.188, ttl=64
| sock: bound to 80.253.209.188:4786, receive buffer size=80000, send buffer size=150000
| mcast_recv_sock: bound to 80.253.209.188:48866, send buffer size=150000, receive buffer size=80000
| mcast_send_sock: bound to 80.253.209.188:4787, send buffer size=150000, receive buffer size=80000
| [5/14/08 12:48:16:246 CEST] 0000002a SystemOut O
| -------------------------------------------------------
| GMS: address is 80.253.209.188:4786
| -------------------------------------------------------
| [5/14/08 12:48:18:327 CEST] 0000002b ENCRYPT I org.jgroups.protocols.ENCRYPT down handling view: [80.253.209.188:4786|0] [80.253.209.188:4786]
| [5/14/08 12:48:18:342 CEST] 0000002b ENCRYPT I org.jgroups.protocols.ENCRYPT becomeKeyServer I have become key server 80.253.209.188:4786
| [5/14/08 12:48:18:358 CEST] 00000028 TreeCache I org.jboss.cache.TreeCache startService TreeCache local address is 80.253.209.188:4786
And this is where the code hangs.
Shouldn't the startService() method continue regardless of other potential members?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150708#4150708
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150708
18 years, 1 month
[JBoss Portal] - Re: Custom Login Module - Login Link
by ai77
The problem is that the user has to exist in both my database/WS and the jboss-portal database. If it is so, everything works fine, my custom-login-module is called and i see the links on top of the page. Note that the user in the jboss DB just needs to have the same login (password and other info can be different). If you think about it, it makes sense as there are lots of things associated to that user that are jboss specific, as permissions, dashboard, pages, own portals... but it's still a pain.
The problem now is to keep the two databases synchronized. If inserting users through the jboss user management portlet, i thought I could override its WF jbp_identity_validation_approval_workflow (see identity-ui-configuration.xml) to call my Web Service to insert the user in my DB as well. I haven't gone so far yet, but if somebody has done it, please let me know!
I didn't override the commit method in my custom login.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150704#4150704
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150704
18 years, 1 month
[EJB 3.0] - Remote EJB calls ?
by JKV
I am using JBOSS 4.2.2 and EJB 3.0. I am accessing an EJB remotely from a client. I wanted to make a test run and made my calls within a while loop
Ex:
while (true) {
// Call Remote Bean
}
It run well for some time and then it gave the following exception
ex=Can not get connection to server. Problem establishing socket connection for InvokerLocator [socket://x.x.x.x:3873/]
org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [socket://x.x.x.x:3873/]
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:532)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
at org.jboss.remoting.Client.invoke(Client.java:1634)
at org.jboss.remoting.Client.invoke(Client.java:548)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:67)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107)
at $Proxy16.preProcessMessage(Unknown Source)...
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.net.SocketException: Can not obtain client socket connection from pool. Have waited 32204 milliseconds for available connection (52in use)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:862)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:525)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
at org.jboss.remoting.Client.invoke(Client.java:1634)
at org.jboss.remoting.Client.invoke(Client.java:548)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:67)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107)
at $Proxy16.preProcessMessage(Unknown Source)...
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:74)
Is there any way to configure the number of connections in the pool? Or whether there is any limitation on the number of calls to the EJB within a specified time limit?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150687#4150687
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150687
18 years, 1 month