[JBoss JIRA] Created: (JBAS-7666) Datasource wrapper returns same java.sql.Connection object to multiple threads in multithreaded environment
by Smita Nimbalkar (JIRA)
Datasource wrapper returns same java.sql.Connection object to multiple threads in multithreaded environment
------------------------------------------------------------------------------------------------------------
Key: JBAS-7666
URL: https://jira.jboss.org/jira/browse/JBAS-7666
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-5.1.0.GA
Environment: JBoss Version: jboss-5.1.0.GA, OS: Linux (2.6.18-164.el5), Architecture: amd64 64bit, JVM: Java HotSpot(TM) 64-Bit Server VM (14.0-b16, mixed mode)
Reporter: Smita Nimbalkar
Sometimes this happens that in multithreaded environment Datasource wrapper returns same java.sql.Connection object from connection pool to different threads.
Test case scenario:
There are multiple threads which needs java.sql.Connection object. If one thread has reference to java.sql.Connection then when other thread requests connection then it gets reference to same java.sql.Connection object that means two threads has reference to same connection object from the pool.
If one thread closes this connection first and then other thread tries to do any operation on connection object then we get following exception:
Caused by: java.lang.IllegalAccessException: Failed to find connection: 14271357
at org.jboss.resource.adapter.jdbc.remote.WrapperDataSourceService.invoke(WrapperDataSourceService.java:212)
at sun.reflect.GeneratedMethodAccessor281.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.GeneratedMethodAccessor283.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
at sun.rmi.transport.Transport$1.run(Transport.java:159)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source)
at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
... 17 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (JBAS-7703) org.jboss.test.web.test.JSPAnnotationENCUnitTestCase.testSimpleEjbJSPAnnotations
by Brian Stansberry (JIRA)
org.jboss.test.web.test.JSPAnnotationENCUnitTestCase.testSimpleEjbJSPAnnotations
--------------------------------------------------------------------------------
Key: JBAS-7703
URL: https://jira.jboss.org/jira/browse/JBAS-7703
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Web (Tomcat) service
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: JBossAS-6.0.0.M2
Test case is failing because of a problem in the ENC mapping to global JNDI.
Test deploys a JSP with the following field:
@EJB
private SimpleStateless simpleStateless;
Populating the field results in an exception with the following critical part:
javax.naming.NamingException: Could not dereference object [Root exception is javax.naming.NameNotFoundException: SimpleStatelessBean not bound]
org.jnp.interfaces.NamingContext.resolveLink(NamingContext.java:1356)
org.jnp.interfaces.NamingContext.lookup(NamingContext.java:819)
org.jnp.interfaces.NamingContext.lookup(NamingContext.java:688)
org.jboss.ejb3.JndiUtil.lookup(JndiUtil.java:44)
org.jboss.injection.JndiPropertyInjector.lookup(JndiPropertyInjector.java:75)
org.jboss.injection.JndiPropertyInjector.inject(JndiPropertyInjector.java:99)
org.jboss.web.tomcat.service.TomcatInjectionContainer.processInjectors(TomcatInjectionContainer.java:391)
org.jboss.web.tomcat.service.TomcatInjectionContainer.processAnnotations(TomcatInjectionContainer.java:445)
org.jboss.web.tomcat.service.TomcatInjectionContainer.processDynamicBeanAnnotations(TomcatInjectionContainer.java:407)
org.jboss.web.tomcat.service.TomcatInjectionContainer.newInstance(TomcatInjectionContainer.java:290)
org.jboss.web.tomcat.service.TomcatInjectionContainer.newInstance(TomcatInjectionContainer.java:281)
org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:145)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:253)
javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
The ENC contains a LinkRef of type LinkAddress, content SimpleStatelessBean. Problem is "SimpleStatelessBean" does not match the global JNDI namespace binding for the EJB. The EJB is contained in a jbosstest-jsp-injection.ear and the global JNDI namespace bindings for the EJB are:
+- jbosstest-jsp-injection (class: org.jnp.interfaces.NamingContext)
| +- SimpleStatelessBean (class: org.jnp.interfaces.NamingContext)
| | +- local-org.jboss.test.web.ejb3.SimpleLocal (class: Proxy for: org.jboss.test.web.ejb3.SimpleLocal)
| | +- local (class: Proxy for: org.jboss.test.web.ejb3.SimpleLocal)
| | +- remote (class: Proxy for: org.jboss.test.web.ejb3.SimpleStateless)
| | +- remote-org.jboss.test.web.ejb3.SimpleStateless (class: Proxy for: org.jboss.test.web.ejb3.SimpleStateless)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (GPD-400) Designer removes <java> tags from <on> tags
by Tamas Malatinszki (JIRA)
Designer removes <java> tags from <on> tags
-------------------------------------------
Key: GPD-400
URL: https://jira.jboss.org/browse/GPD-400
Project: jBPM GPD
Issue Type: Bug
Affects Versions: jBPM jPDL Designer 4.0.0.GA
Environment: Windows XP, Eclipse 3.5.2
Reporter: Tamas Malatinszki
Assignee: Koen Aers
Original XML file:
<mail g="348,588,169,53" name="Notification" template="mailtemplate">
<on event="start">
<java class="com.own.jbpm.Notifications" method="licenseChecking" var="mail">
<arg><object expr="#{processId}"/></arg>
</java>
</on>
<transition g="7,-8" name="Waiting for license" to="Waiting for license requirements" />
</mail>
After any modification on Diagram view:
<mail g="348,588,169,53" name="Notification" template="mailtemplate">
<on event="start">
</on>
<transition g="7,-8" name="Waiting for license" to="Waiting for license requirements" />
</mail>
Issue is seems similar to GPD-395.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (JBRULES-2682) ServiceRegistryImpl is registered twice: once as a singleton and once as a service tracker
by Antoine Toulme (JIRA)
ServiceRegistryImpl is registered twice: once as a singleton and once as a service tracker
------------------------------------------------------------------------------------------
Key: JBRULES-2682
URL: https://jira.jboss.org/browse/JBRULES-2682
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-api
Affects Versions: 5.2.0.M1
Reporter: Antoine Toulme
Assignee: Mark Proctor
Fix For: FUTURE
Attachments: ServiceRegistryImpl.patch
This bug occurs when using Drools inside an OSGi environment. The ServiceRegistryImpl is instantiated instead of using the instance singleton, which leads to having objects being registered against the wrong ServiceRegistry. The OSGi class loader won't let the default instantiator work, as the classes are part of a different bundle. As a result, the configuration of the knowledge base fails.
The patch attached fixes this problem, it is a one liner.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (JBAS-8037) Optimize AS build process
by Jesper Pedersen (JIRA)
Optimize AS build process
-------------------------
Key: JBAS-8037
URL: https://jira.jboss.org/browse/JBAS-8037
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Build System
Affects Versions: 6.0.0.M3
Reporter: Jesper Pedersen
Assignee: Paul Gier
Priority: Critical
The AS build process it taking way too long when there are no changes made.
Do:
svn co https://....
cd trunk
./build.sh
Then without changing anything do
./build.sh
again - result:
[INFO] Total time: 5 minutes 29 seconds
[INFO] Finished at: Thu May 20 05:10:56 EDT 2010
[INFO] Final Memory: 193M/452M
The Nexus repo seems to be checked too frequently - but I'll let you create sub-tasks for those issues
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (JBAS-8378) QuerySyntaxException : Entity not mapped when code is migrated from jboss-4.2.3 to jboss-5.1.0.GA
by Raghavan TV (JIRA)
QuerySyntaxException : Entity not mapped when code is migrated from jboss-4.2.3 to jboss-5.1.0.GA
-------------------------------------------------------------------------------------------------
Key: JBAS-8378
URL: https://jira.jboss.org/browse/JBAS-8378
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Hibernate service
Affects Versions: JBossAS-5.1.0.GA
Environment: jboss-5.1.0.GA, jdk-1.6.0_05, oracle 10g, hibernate that is bundled with jboss-5.1.0.GA
Reporter: Raghavan TV
Assignee: Steve Ebersole
Priority: Critical
We encountered this error during the migration of our j2ee app from jboss-4.2.3 to jboss-5.1.0.GA. To narrow down the issue, created a unit code to reproduce the same problem.
Stack Trace
---------------
21:02:27,059 ERROR [STDERR] org.hibernate.hql.ast.QuerySyntaxException: SsoUser is not mapped [select ssou from SsoUser ssou]
at org.hibernate.hql.ast.util.SessionFactoryHelper.requireClassPersister(SessionFactoryHelper.java:181)
at org.hibernate.hql.ast.tree.FromElementFactory.addFromElement(FromElementFactory.java:110)
at org.hibernate.hql.ast.tree.FromClause.addFromElement(FromClause.java:93)
at org.hibernate.hql.ast.HqlSqlWalker.createFromElement(HqlSqlWalker.java:277)
at org.hibernate.hql.antlr.HqlSqlBaseWalker.fromElement(HqlSqlBaseWalker.java:3056)
at org.hibernate.hql.antlr.HqlSqlBaseWalker.fromElementList(HqlSqlBaseWalker.java:2945)
at org.hibernate.hql.antlr.HqlSqlBaseWalker.fromClause(HqlSqlBaseWalker.java:688)
at org.hibernate.hql.antlr.HqlSqlBaseWalker.query(HqlSqlBaseWalker.java:544)
at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectStatement(HqlSqlBaseWalker.java:281)
at org.hibernate.hql.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java:229)
at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:251)
at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:183)
at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:134)
at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:101)
at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:80)
at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:94)
at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:156)
at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:135)
at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1650)
at com.mycomp.mydomain.testhibernateprj.TestDAO.getSsoUserById(TestDAO.java:25)
at com.tcs.telecom.tib.testhibernateprj.servlets.SampleServlet.processRequest(SampleServlet.java:40)
at com.mycomp.mydomain.testhibernateprj.servlets.SampleServlet.doGet(SampleServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months