Problems creating new community
Hi,
I am currently running an evaluation version of RAM (Server setup version= RAM75-I20100911_1018) Server= IBM Embeddable WebSphere Application Server 7.0.0.11 embeddedEXPRESS STANDALONE I managed to install the app successfully, however the system throws the following error when i tried to created a new community (or in fact do anything that will create a new record in the system) I am running the instance on my local machine with MS SQL 2005 (Single Instance) Any assistance is appreciated. Thanks!! 00000014 application E com.ibm.ram.repository.core.IRepositoryAccess$RepositoryException: Transaction context in use by another session. javax.faces.el.EvaluationException: com.ibm.ram.repository.core.IRepositoryAccess$RepositoryException: Transaction context in use by another session. at com.sun.faces.application.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102) at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102) at javax.faces.component.UICommand.broadcast(UICommand.java:387) at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:458) at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:763) at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:82) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1661) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1595) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:131) at com.ibm.ram.repository.web.security.RAMServletFilter.doFilter(RAMServletFilter.java:442) at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116) at com.ibm.ram.repository.web.filters.GZipFilter.doFilter(GZipFilter.java:42) at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116) at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:77) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:908) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:932) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:500) at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178) at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:91) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:864) at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1583) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:186) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:455) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:384) at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:83) at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165) at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161) at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138) at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204) at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775) at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1550) Caused by: com.ibm.ram.repository.core.IRepositoryAccess$RepositoryException: Transaction context in use by another session. at com.ibm.ram.repository.core.sdo.BaseRAMSchemaAccess.primApplyResourceGroupChanges(BaseRAMSchemaAccess.java:6488) at com.ibm.ram.repository.core.sdo.BaseRAMSchemaAccess.applyResourceGroupChanges(BaseRAMSchemaAccess.java:6419) at com.ibm.ram.repository.security.SecurityManager.createGroup(SecurityManager.java:1552) at pagecode.admin.AdminCommunities.doEditGroup(AdminCommunities.java:331) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:600) at org.apache.el.parser.AstValue.invoke(AstValue.java:131) at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) at com.sun.faces.application.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88) ... 37 more Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Transaction context in use by another session. at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:196) at com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(tdsparser.java:246) at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:83) at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:39) at com.microsoft.sqlserver.jdbc.SQLServerResultSet.doUpdateRowRPC(SQLServerResultSet.java:3987) at com.microsoft.sqlserver.jdbc.SQLServerResultSet.access$200(SQLServerResultSet.java:16) at com.microsoft.sqlserver.jdbc.SQLServerResultSet$1UpdateRowRPC.doExecute(SQLServerResultSet.java:3921) at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:4026) at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1416) at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:185) at com.microsoft.sqlserver.jdbc.SQLServerResultSet.updateRow(SQLServerResultSet.java:3957) at com.ibm.ws.rsadapter.jdbc.WSJdbcResultSet.updateRow(WSJdbcResultSet.java:5767) at com.ibm.ram.repository.core.sdo.BaseRAMSchemaAccess$UniqueKeyMediator.moreKeys(BaseRAMSchemaAccess.java:274) at com.ibm.ram.repository.core.sdo.BaseRAMSchemaAccess$UniqueKeyMediator.init(BaseRAMSchemaAccess.java:253) at com.ibm.ram.repository.core.sdo.BaseRAMSchemaAccess$UniqueKeyMediator.getKey(BaseRAMSchemaAccess.java:214) at com.ibm.ram.repository.core.sdo.BaseRAMSchemaAccess.primApplyResourceGroupChanges(BaseRAMSchemaAccess.java:6458) ... 47 more #################################################################################### # Environment # #################################################################################### Operating System= Windows XP 5.1 build 2600 Service Pack 3 x86 Server= IBM Embeddable WebSphere Application Server 7.0.0.11 embeddedEXPRESS STANDALONE Profile Folder= C:\Program Files\IBM\RAMServer\ewas7\profiles\profile1 Server setup version= RAM75-I20100911_1018 Location of Server Setup=http://localhost:13080/ram.setup/wizard/report/ReportServlet #################################################################################### # WebSphere Configuration # #################################################################################### Database status=ok # Database section # #################### # Datasource # Name=Microsoft SQLServer 2005 JDBC RAM JNDI Name=jdbc/RAM_Con Scope=Node:RAMNode110428, Server:server1 Data store helper class name=com.ibm.websphere.rsadapter.MicrosoftSQLServerDataStoreHelper Component Managed Authentication Alias=RAMNodeCell110428/RAM_Con Statement Cache Size=100 # Datasource custom properties # databaseName=assetMgr portNumber=1433 serverName=keekiat JDBC Provider Name=Microsoft SQL Server 2005 JDBC provider JDBC Provider Classpath=${MSSQLSERVER_JDBC_DRIVER_PATH}/sqljdbc4.jar # WebSphere variables # Scope=WebSphere:cell=RAMNodeCell110428,node=RAMNode110428,server=server1 MSSQLSERVER_JDBC_DRIVER_PATH=${USER_INSTALL_ROOT}/config/cells/RAMNodeCell110428/ram_jdbc # Component Alias properties # Name=RAMNodeCell110428/RAM_Con User Id=sa # Security section # #################### Enable administrative security=true Enable application security=true Java 2 security=false User account repository=Standalone Custom registry (file) Primary administrative user name=admin Automatically generated server identity=false Server user ID on a Version 6.0.x node= Ignore case for authorization=false Custom registry class name=com.ibm.websphere.security.FileRegistrySample Custom Properties > usersFile=C:\Program Files\IBM\RAMServer\ewas7\profiles\profile1\config/cells/RAMNodeCell110428/props\users.props Custom Properties > groupsFile=C:\Program Files\IBM\RAMServer\ewas7\profiles\profile1\config/cells/RAMNodeCell110428/props\groups.props # Deployment section # ###################### # Servers # Application server name=WebSphere:cell=RAMNodeCell110428,node=RAMNode110428,server=server1 # Applications # Application name=RAM1WebApplication Application status=Installed State=Started Version=RAM75-I20100911_1018 Module=com.ibm.ram |
3 answers
Assume this is SP2 for the SQL server?
Note also, that RAM 7.5 SP2 (7.5.0.2) is out. By single SQL server, also assume it is not linked, or that there are multiple ip addresses for it: http://social.msdn.microsoft.com/Forums/en/transactsql/thread/2da5983c-2256-4394-82e0-c0c26c663a7e |
Assume this is SP2 for the SQL server? Thanks a lot for your reply. Yes i am using SP2 for SQL Server... i upgraded it to SP4 this morning but the problem persist. I executed the sp_addlinkedserver command to add 'KEEKIAT' because RAM was throwing this error Could not find server 'KEEKIAT' in sys.servers. Verify that the correct server name was specified. If necessary, execute the stored procedure sp_addlinkedserver to add the server to sys.servers. P/S: 'KEEKIAT' is the name of my computer. EDIT: I think i will try upgrading to the latest version to see it helps. Thanks a lot! |
Upgraded to RAM 7.5 SP2 (7.5.0.2) but the same problem persist.
The link that you provide mention something along this line: "...or do not user loopback server in your query. SQL Server doesn't officially support loopback server scenario." |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.