Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

BlackBerry® Enterprise Service 10

Reply
Visitor
Posts: 1
Registered: ‎06-03-2009
My Device: Not Specified

BES admin service stops working

After a server reboot or service restart the BES admin service works fine. After a couple of hours it will no longer work or accept new logins. Here are snipptes from the BBAS-AS and BBAS-NCCJ logs for the relavent periods but full error blocks are too long to post (20,000 char limit). If I restart both services it usually starts working again, although on occassion it takes and entire server reboot. Has anyone else encountered this and found a fix or workaround?

 

BBAS-AS

 

(06/03 13:40:40:387):{http-SDC-BES-01.EXCHANGE.WASHINGTON.EDU%2F140.142.10.168-443-1} [com.rim.bes.bas.commands.securitymanager.SecurityLogin] [INFO] [BBAS-1006] {unknown} Logged in user drossow
(06/03 13:40:40:449):{http-SDC-BES-01.EXCHANGE.WASHINGTON.EDU%2F140.142.10.168-443-1} [com.rim.bes.bas.licensemanagertools.LicenseManagerAccessorUtilities] [WARN] [BBAS-2008] {u=2, uc=-1, o=0, t=4830} checkMasterKeyConsistency could not complete due to exception:  org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [sslsocket://127.0.0.1:23843/?socketFactoryClassName=com.rim.bes.bas.clientconnectionmanager.ClientConnectionSocketFactory]

*** Start of original stack trace ***

org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [sslsocket://127.0.0.1:23843/?socketFactoryClassName=com.rim.bes.bas.clientconnectionmanager.ClientConnectionSocketFactory]
 at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:559)
 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:61)
 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 $Proxy559.checkMasterKeyConsistency(Unknown Source)

 

...

etc

...

 

 

 

BBAS-NCCJ

 

(06/03 13:40:40:434):{WorkerThread#0[127.0.0.1:3203]} [org.jboss.remoting.transport.socket.ServerThread] [ERROR] Worker thread initialization failure
java.lang.reflect.InvocationTargetException
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
 at java.lang.reflect.Constructor.newInstance(Unknown Source)
 at org.jboss.remoting.transport.socket.ServerThread.createServerSocketWrapper(ServerThread.java:720)
 at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:368)
 at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
Caused by: java.net.SocketException: Socket Closed
 at java.net.PlainSocketImpl.setOption(Unknown Source)
 at java.net.Socket.setSoTimeout(Unknown Source)
 at com.sun.net.ssl.internal.ssl.SSLSocketImpl.setSoTimeout(Unknown Source)
 at org.jboss.remoting.transport.socket.SocketWrapper.setTimeout(SocketWrapper.java:85)
 at org.jboss.remoting.transport.socket.ClientSocketWrapper.createStreams(ClientSocketWrapper.java:168)
 at org.jboss.remoting.transport.socket.ClientSocketWrapper.<init>(ClientSocketWrapper.java:66)
 at org.jboss.remoting.transport.socket.ServerSocketWrapper.<init>(ServerSocketWrapper.java:46)
 ... 7 more
(06/03 13:41:10:497):{WorkerThread#0[127.0.0.1:3367]} [org.jboss.remoting.transport.socket.ServerThread] [ERROR] Worker thread initialization failure
java.lang.reflect.InvocationTargetException
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
 at java.lang.reflect.Constructor.newInstance(Unknown Source)
 at org.jboss.remoting.transport.socket.ServerThread.createServerSocketWrapper(ServerThread.java:720)
 at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:368)
 at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
Caused by: java.net.SocketException: Socket Closed
 at java.net.PlainSocketImpl.setOption(Unknown Source)
 at java.net.Socket.setSoTimeout(Unknown Source)
 at com.sun.net.ssl.internal.ssl.SSLSocketImpl.setSoTimeout(Unknown Source)
 at org.jboss.remoting.transport.socket.SocketWrapper.setTimeout(SocketWrapper.java:85)
 at org.jboss.remoting.transport.socket.ClientSocketWrapper.createStreams(ClientSocketWrapper.java:168)
 at org.jboss.remoting.transport.socket.ClientSocketWrapper.<init>(ClientSocketWrapper.java:66)
 at org.jboss.remoting.transport.socket.ServerSocketWrapper.<init>(ServerSocketWrapper.java:46)
 ... 7 more

 

...

etc

...

New Member
Posts: 1
Registered: ‎11-10-2009
My Device: Not Specified

Re: BES admin service stops working

I'm experiencing the same issue on a test server I'm working with. Below is the error I'm experiencing in the BBAS-AS logs. I recently tried creating a Certification using a Microsoft 2008 PKI server and added this SSL cert to the BES. This is the only change to the environment.

 

BES 5.0 MR3

VMWare ESX 3.5

 

 

BBAS-AS  ERROR:

 

*** end of original stack trace ***


org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [sslsocket://127.0.0.1:23843/?socketFactoryClassName=com.rim.bes.bas.clientconnectionmanager.ClientConnectionSocketFactory]
 at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:559)
 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:61)
 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 $Proxy463.getBIPPPassword(Unknown Source)
 at com.rim.bes.bas.encryptiontools.EncryptionToolsCallWrapper.run(EncryptionToolsCallWrapper.java:255)
 at com.rim.bes.bas.authenticationmanager.AuthenticationManagerUtilities.runAsCredentialsLocal(AuthenticationManagerUtilities.java:855)
 at com.rim.bes.bas.authenticationmanager.AuthenticationManagerUtilities.runAsAuthenticationCredentialsLocal(AuthenticationManagerUtilities.java:782)
 at com.rim.bes.bas.encryptiontools.EncryptionToolsUtilities.getBIPPPassword(EncryptionToolsUtilities.java:364)
 at com.rim.bes.basplugin.mdss.webservice.proxy.MDSSProxy.getAdminClient(MDSSProxy.java:2296)
 at com.rim.bes.basplugin.mdss.webservice.proxy.MDSSProxy.<init>(MDSSProxy.java:666)
 at com.rim.bes.basplugin.mdss.webservice.proxy.MDSSProxy.getInstance(MDSSProxy.java:760)
 at com.rim.bes.basplugin.mdss.MDSSManagerBean._getMDSSProxyByServiceInstanceID(MDSSManagerBean.java:5416)
 at com.rim.bes.basplugin.mdss.MDSSManagerBean._getMDSSProxyWithConnectionByServiceInstanceID(MDSSManagerBean.java:5330)
 at com.rim.bes.basplugin.mdss.MDSSManagerBean._resetAllConnectionServices(MDSSManagerBean.java:4050)
 at com.rim.bes.basplugin.mdss.MDSSManagerBean.resetAllConnectionServicesLocal(MDSSManagerBean.java:3883)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
 at java.lang.reflect.Method.invoke(Unknown Source)

Highlighted
Retired
Posts: 616
Registered: ‎03-25-2009
My Device: BlackBerry Curve 9360
My Carrier: Bell

Re: BES admin service stops working

By any chance, are there multiple BAS nodes in the environment? Are they across different subnets?

______________________________________________
The only stupid question is the one you don't ask before you reboot the BES.