May 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1869) Got Marshalling Exception when JMSWire Format writes object to Socket

by Nordine B (JIRA)

Got Marshalling Exception when JMSWire Format writes object to Socket --------------------------------------------------------------------- Key: JBMESSAGING-1869 URL: https://issues.jboss.org/browse/JBMESSAGING-1869 Project: JBoss Messaging Issue Type: Bug Components: JMS Destination Manager, JMS Remoting Affects Versions: 1.4.0.SP3.CP10 Environment: Windows, JBoss EAP 4.3.0.CP08 Reporter: Nordine B We are using Spring's Message Driven Pojo to consume messages. At startup when the MDP is lauched, we have the following exception: 12:09:43,656 INFO [STDOUT] 12:09:43.656 [MOMWorkManagerThreadPool(3)-8]] INFO fr.msa.agora.socle.g2.mom.internal.MDPContainerListenerImpl - Successfully refreshed JMS Connection 12:09:43,687 ERROR [SocketClientInvoker] Got marshalling exception, exiting java.io.EOFException at java.io.DataInputStream.readInt(DataInputStream.java:375) at org.jboss.jms.wireformat.JMSWireFormat.read(JMSWireFormat.java:288) at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedRead(MicroSocketClientInvoker.java:1036) at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:694) at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:458) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:141) at org.jboss.remoting.Client.invoke(Client.java:1935) at org.jboss.remoting.Client.invoke(Client.java:788) at org.jboss.remoting.Client.invoke(Client.java:776) at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:189) at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:160) at org.jboss.jms.client.delegate.ClientConsumerDelegate.org$jboss$jms$client$delegate$ClientConsumerDelegate$closing$aop(ClientConsumerDelegate.java:129) at org.jboss.jms.client.delegate.ClientConsumerDelegate$closing_2473194355759371067.invokeNext(ClientConsumerDelegate$closing_2473194355759371067.java) at org.jboss.jms.client.container.ConsumerAspect.handleClosing(ConsumerAspect.java:144) at org.jboss.aop.advice.org.jboss.jms.client.container.ConsumerAspect36.invoke(ConsumerAspect36.java) at org.jboss.jms.client.delegate.ClientConsumerDelegate$closing_2473194355759371067.invokeNext(ClientConsumerDelegate$closing_2473194355759371067.java) at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) at org.jboss.jms.client.delegate.ClientConsumerDelegate$closing_2473194355759371067.invokeNext(ClientConsumerDelegate$closing_2473194355759371067.java) at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:172) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) at org.jboss.jms.client.delegate.ClientConsumerDelegate$closing_2473194355759371067.invokeNext(ClientConsumerDelegate$closing_2473194355759371067.java) at org.jboss.jms.client.delegate.ClientConsumerDelegate.closing(ClientConsumerDelegate.java) at org.jboss.jms.client.JBossMessageConsumer.close(JBossMessageConsumer.java:96) at org.springframework.jms.connection.CachingConnectionFactory$CachedSessionInvocationHandler.physicalClose(CachingConnectionFactory.java:418) at org.springframework.jms.connection.CachingConnectionFactory$CachedSessionInvocationHandler.invoke(CachingConnectionFactory.java:305) at $Proxy133.close(Unknown Source) at org.springframework.jms.connection.JmsResourceHolder.closeAll(JmsResourceHolder.java:195) at org.springframework.jms.connection.JmsTransactionManager.doCleanupAfterCompletion(JmsTransactionManager.java:264) at org.springframework.transaction.support.AbstractPlatformTransactionManager.cleanupAfterCompletion(AbstractPlatformTransactionManager.java:1011) at org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:804) at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:723) at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:255) at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1056) at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:952) at org.springframework.jca.work.DelegatingWork.run(DelegatingWork.java:57) at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:213) at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:756) at java.lang.Thread.run(Thread.java:662) The exception repeats while MDP try to refresh the connection. 0 The strange thing is that if we replace jboss-messaging-client.jar 1.4.0.SP10 by the 1.4.0.SP08 version, everything works perfectly. You may know that we have applied Slimming on our JBoss EAP 4.3CP08 (http://community.jboss.org/wiki/JBoss4xSlimming) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1868) JBM_CLUSTER table creation SQL for sybase is not correct

by Yong Hao Gao (JIRA)

JBM_CLUSTER table creation SQL for sybase is not correct -------------------------------------------------------- Key: JBMESSAGING-1868 URL: https://issues.jboss.org/browse/JBMESSAGING-1868 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Persistence Affects Versions: 1.4.8.GA, 1.4.0.SP3.CP12 Reporter: Yong Hao Gao Assignee: Yong Hao Gao Fix For: 1.4.0.SP3.CP13, 1.4.8.SP1 CREATE TABLE JBM_CLUSTER (NODE_ID SMALLINT, PING_TIMESTAMP DATETIME, STATE SMALLINT, PRIMARY KEY(NODE_ID)) It should be CREATE TABLE JBM_CLUSTER (NODE_ID SMALLINT NOT NULL, PING_TIMESTAMP DATETIME, STATE SMALLINT, PRIMARY KEY(NODE_ID)) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
5
0 / 0

[JBoss JIRA] Created: (JBBUILD-663) Some artifacts, like org.hibernate:hibernate-entitymanager:3.5.6-Final are missing in Nexus search

by BTO Sabre (JIRA)

Some artifacts, like org.hibernate:hibernate-entitymanager:3.5.6-Final are missing in Nexus search -------------------------------------------------------------------------------------------------- Key: JBBUILD-663 URL: https://jira.jboss.org/browse/JBBUILD-663 Project: JBoss Build System Issue Type: Bug Components: Sonatype Reporter: BTO Sabre Assignee: Paul Gier Priority: Critical Some artifacts are in repo but not show up in Nexus. I guess this is index issue. For example below artifact is in repo https://repository.jboss.org/nexus/content/groups/public-jboss/org/hibern... but not in Nexus https://repository.jboss.org/nexus/index.html#nexus-search;gav~org.hibern... This bug is critical because we are unable to download this artifact using jboss-public repository proxied in our Nexus. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBWEB-200) REGRESSION: JSP generation uses TomcatInjectionContainer unsafely, leading to race condition

by Richard Kennard (JIRA)

REGRESSION: JSP generation uses TomcatInjectionContainer unsafely, leading to race condition -------------------------------------------------------------------------------------------- Key: JBWEB-200 URL: https://issues.jboss.org/browse/JBWEB-200 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Components: Tomcat Affects Versions: JBossWeb-3.0.0.CR1 Environment: JBoss AS 6.0.0.Final Reporter: Richard Kennard Assignee: Remy Maucherat Priority: Critical Hi guys, Thanks for the great work you do on JBoss Web! We've been using it in production for years and it's a really solid product. We are just upgrading from JBoss 5.1.0.GA to JBoss AS 6.0.0.Final. There appears to have been a serious regression in the JSP compilation. In JBoss 5.1.0.GA our JSP page compiled to this (looking in the /work folder)... PageContext pageContext = _jspx_page_context; JspWriter out = _jspx_page_context.getOut(); // tags:page-loggedIn org.apache.jsp.tag.web.page_002dloggedIn_tag _jspx_th_tags_005fpage_002dloggedIn_005f0 = (new org.apache.jsp.tag.web.page_002dloggedIn_tag()); _jsp_instancemanager.newInstance(_jspx_th_tags_005fpage_002dloggedIn_005f0); _jspx_th_tags_005fpage_002dloggedIn_005f0.setJspContext(_jspx_page_context); ...but in JBoss AS 6.0.0.Final it compiles to this... PageContext pageContext = _jspx_page_context; JspWriter out = _jspx_page_context.getOut(); // tags:page-loggedIn org.apache.jsp.tag.web.page_002dloggedIn_tag _jspx_th_tags_005fpage_002dloggedIn_005f0 = (org.apache.jsp.tag.web.page_002dloggedIn_tag)_jsp_instancemanager.newInstance("org.apache.jsp.tag.web.page_002dloggedIn_tag", this.getClass().getClassLoader()); _jspx_th_tags_005fpage_002dloggedIn_005f0.setJspContext(_jspx_page_context); There is a slight difference in which _jsp_instancemanager method is being called. The new JSP is calling the version of the method which takes a String. The old JSP was using the version which takes an Object. Behind the scenes _jsp_instance maps to TomcatInjectionContainer, which uses a ClassLoader implemented by JasperLoader. However, JasperLoader.loadClass(name, resolve) is NOT THREAD SAFE. Even though it probably should be (java.lang.ClassLoader.loadClass(name, resolve) *is* Thread-safe, but JasperLoader overrides it and neglects to use 'synchronized'). So there may be 2 bugs here? Anyway, regardless of whether the bug is in the JSP compilation or JasperLoader, under concurrent load we see this: Caused by: java.lang.IllegalArgumentException: org.apache.jsp.tag.web at java.lang.ClassLoader.definePackage(ClassLoader.java:1452) at java.net.URLClassLoader.defineClass(URLClassLoader.java:251) at java.net.URLClassLoader.access$000(URLClassLoader.java:58) at java.net.URLClassLoader$1.run(URLClassLoader.java:197) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at org.apache.jasper.servlet.JasperLoader.loadClass(JasperLoader.java:135) at org.apache.jasper.servlet.JasperLoader.loadClass(JasperLoader.java:67) at org.jboss.web.tomcat.service.TomcatInjectionContainer.newInstance(TomcatInjectionContainer.java:278) at org.apache.jsp.platforms.platforms_jsp._jspx_meth_tags_005fpage_002dloggedIn_005f0(platforms_jsp.java:113) Which is caused by this: 2011-05-23 13:53:11,874 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/].[jsp]] (http-116.50.21.248-8443-7) Servlet.service() for servlet jsp threw exception: java.lang.LinkageError: loader (instance of org/apache/jasper/servlet/JasperLoader): attempted duplicate class definition for name: "org/apache/jsp/tag/web/page_002dloggedIn_tag" at java.lang.ClassLoader.defineClass1(Native Method) [:1.6.0_24] at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632) [:1.6.0_24] at java.lang.ClassLoader.defineClass(ClassLoader.java:616) [:1.6.0_24] at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) [:1.6.0_24] at java.net.URLClassLoader.defineClass(URLClassLoader.java:283) [:1.6.0_24] at java.net.URLClassLoader.access$000(URLClassLoader.java:58) [:1.6.0_24] at java.net.URLClassLoader$1.run(URLClassLoader.java:197) [:1.6.0_24] at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_24] at java.net.URLClassLoader.findClass(URLClassLoader.java:190) [:1.6.0_24] at org.apache.jasper.servlet.JasperLoader.loadClass(JasperLoader.java:135) [:6.0.0.Final] at org.apache.jasper.servlet.JasperLoader.loadClass(JasperLoader.java:67) [:6.0.0.Final] at org.jboss.web.tomcat.service.TomcatInjectionContainer.newInstance(TomcatInjectionContainer.java:278) [:6.0.0.Final] This is a regression from JBoss AS 5.1.0, which could handle building JSPs concurrently (and under load) without problem. Note we are using a shared JSP tagfile here (in /WEB-INF/tags). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
13
0 / 0

[JBoss JIRA] Created: (JBAS-9398) Upgrade HornetQ to 2.2.2.Final

by Billy Sjöberg (JIRA)

Upgrade HornetQ to 2.2.2.Final ------------------------------ Key: JBAS-9398 URL: https://issues.jboss.org/browse/JBAS-9398 Project: Legacy JBoss Application Server 6 Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: JMS (HornetQ) Affects Versions: 6.1.0 Reporter: Billy Sjöberg Assignee: Clebert Suconic Priority: Minor Fix For: 6.1.0 Bundle 2.2.2.Final release of HornetQ with the 6.1 AS release. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2244) BMT interceptor doesn't take into account application exceptions

by jaikiran pai (JIRA)

BMT interceptor doesn't take into account application exceptions ---------------------------------------------------------------- Key: EJBTHREE-2244 URL: https://issues.jboss.org/browse/EJBTHREE-2244 Project: EJB 3.0 Issue Type: Bug Components: transactions Affects Versions: 2.0.0-alpha-1 Reporter: jaikiran pai Assignee: jaikiran pai Fix For: 2.0.0-alpha-2 BMT interceptors currently don't check for application exception semantics as mandated by EJB3 spec. See EJB3.1 spec section 14.3.1, Table 16 for details. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
2
0 / 0

[JBoss JIRA] Moved: (JBAS-9396) Create documentation for using the jboss client dependency in a maven build.

by Paul Gier (JIRA)

[ https://issues.jboss.org/browse/JBAS-9396?page=com.atlassian.jira.plugin.... ] Paul Gier moved JBBUILD-505 to JBAS-9396: ----------------------------------------- Project: Legacy JBoss Application Server 6 (was: JBoss Build System) Key: JBAS-9396 (was: JBBUILD-505) Issue Type: Enhancement (was: Task) Component/s: Build System (was: Maven Builds) Security: Public Fix Version/s: Open To Community (was: Build Support 2011) > Create documentation for using the jboss client dependency in a maven build. > ---------------------------------------------------------------------------- > > Key: JBAS-9396 > URL: https://issues.jboss.org/browse/JBAS-9396 > Project: Legacy JBoss Application Server 6 > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Gier > Fix For: Open To Community > > > There needs to be some documentation on the wiki about how to use the jbossall client jar. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (AS7-840) Add a @javax.ejb.EJBs processor

by jaikiran pai (JIRA)

Add a @javax.ejb.EJBs processor ------------------------------- Key: AS7-840 URL: https://issues.jboss.org/browse/AS7-840 Project: Application Server 7 Issue Type: Task Components: EE Reporter: jaikiran pai Assignee: jaikiran pai Fix For: 7.0.0.CR1 Currently we only process @EJB. We need to implement @EJBs processing too. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (AS7-834) Implement a deterministic way of adding interceptors and configurators to a view and component

by jaikiran pai (JIRA)

Implement a deterministic way of adding interceptors and configurators to a view and component ---------------------------------------------------------------------------------------------- Key: AS7-834 URL: https://issues.jboss.org/browse/AS7-834 Project: Application Server 7 Issue Type: Task Components: EE Reporter: jaikiran pai Assignee: Jason Greene Fix For: 7.0.0.CR1 In the new EE framework, adding view/component configurators and interceptors to the view/component isn't deterministic and is very brittle. This needs to be re-implemented in a better way to provide a deterministic and more robust ordering of the configurators and interceptors. I'm not assigning this to myself (yet) since I'm currently trying to get the EJB3 TCK related fixes done first. Once I finish that and if no one comes to this before me, then I'll pick this up. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (JBBUILD-660) extension of archetype jar gets changes from .jar to .maven-archetype when published to Nexus releases repo via mvn deploy

by Ian Springer (JIRA)

extension of archetype jar gets changes from .jar to .maven-archetype when published to Nexus releases repo via mvn deploy --------------------------------------------------------------------------------------------------------------------------- Key: JBBUILD-660 URL: https://jira.jboss.org/browse/JBBUILD-660 Project: JBoss Build System Issue Type: Bug Components: Sonatype Affects Versions: Maven Repository Nexus Rollout Reporter: Ian Springer Assignee: Paul Gier Priority: Critical I published the following artifact using 'mvn deploy' from a project with type maven-archetype: https://repository.jboss.org/nexus/content/repositories/releases/org/rhq/... Notice the jarfile's extension got changed from .jar to .maven-archetype. I'm not sure if it was the maven deploy plugin or Nexus that did this. but I suspect it was Nexus. It needs to have the extension .jar, because the archetype:generate goal assumes all archetype artifacts will have that extension. -- 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

15 years, 1 month

2
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2011