November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBESB-228) Possible issue with BodyImpl

by Mark Little (JIRA)

Possible issue with BodyImpl ---------------------------- Key: JBESB-228 URL: http://jira.jboss.com/jira/browse/JBESB-228 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Maintenance Pack 1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.0 Esteban wrote: "I do recall that while testing the CbrProxyAction we encountered some unexpected behaviour in the BodyImpl, so we had to stuff results in the Message Properties (and not in the Body named objects). Unfortunately I can't remember the details. " -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBXB-90) Wildcard bindings are not detected in complicated/nested model groups

by Adrian Brock (JIRA)

Wildcard bindings are not detected in complicated/nested model groups --------------------------------------------------------------------- Key: JBXB-90 URL: http://jira.jboss.com/jira/browse/JBXB-90 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Affects Versions: JBossXB-1.0.0.CR7 Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossXB-1.0 Nested wilcard bindings are not detected if the model group contains a nested wildcard with another nested model group before the wildcard. This example shows the problem: <xsd:complexType name="nested-wildcard" mixed="true"> <xsd:sequence> <xsd:element name="e1" type="xsd:string"/> <xsd:choice minOccurs="0">  <xsd:sequence> <xsd:element name="e2" type="xsd:string" minOccurs="0"/> <xsd:element name="e3" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/> </xsd:sequence> <xsd:element name="e4" type="xsd:string"/> <xsd:any namespace="##other" processContents="strict"/> </xsd:choice> </xsd:sequence> </xsd:complexType> I've created a NestedWilcardUnitTestCase for this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-243) Files without copyright

by Mark Little (JIRA)

Files without copyright ----------------------- Key: JBESB-243 URL: http://jira.jboss.com/jira/browse/JBESB-243 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Reporter: Mark Little Assigned To: Daniel Brum Priority: Blocker Fix For: 4.0 RC1 LoanBrokerException.java BankQuoteResponse.java -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-197) Add SCP listener support

by Mark Little (JIRA)

Add SCP listener support ------------------------ Key: JBESB-197 URL: http://jira.jboss.com/jira/browse/JBESB-197 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Distribution, ESB Core Affects Versions: 4.0 Beta 1 Maintenance Pack 1 Reporter: Mark Little Assigned To: Bruno Georges Priority: Minor Fix For: 4.0 Bruno said: For FTP and CP over SSH, there are some opensource implementation, one we have used is http://www.jcraft.com/jsch/ JSch is licensed under BSD style License. Would this be an option? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-244) Transient junit failures running tests

by Kevin Conner (JIRA)

Transient junit failures running tests -------------------------------------- Key: JBESB-244 URL: http://jira.jboss.com/jira/browse/JBESB-244 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Kevin Conner I have been seeing transient junit failures while running the tests. This failure manifiests itself as the corruption of the junit report files. The corruption of the files is caused by the HSQL database issuing a call to System.exit() before junit has managed to write the complete report. The utility classes should be modified to pass in the '-no_system_exit true' configuration parameter when starting the invm database. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-211) Add in new EULA

by Mark Little (JIRA)

Add in new EULA --------------- Key: JBESB-211 URL: http://jira.jboss.com/jira/browse/JBESB-211 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Mark Little Assigned To: Mark Little Priority: Critical Fix For: 4.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-111) ControllerContext state is updated outside the controller's lock

by Adrian Brock (JIRA)

ControllerContext state is updated outside the controller's lock ---------------------------------------------------------------- Key: JBMICROCONT-111 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-111 Project: JBoss MicroContainer Issue Type: Bug Components: Dependency Affects Versions: JBossMC_2_0_0M1 Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossMC_2_0_0 Beta The controller context state is updated outside the read/write lock of the controller in the install/uninstall callbacks of AbstractControllerContext This can lead to race conditions like JBAS-3865 The context state should be updated at the same time as the controller's internal state. This requires a change to the spi to introduce ControllerContext.setState() For anybody extending AbstractControllerContext (which includes all JBoss impls) this change will picked up automatically. For any others, the updating of the state needs to be moved from the install/uninstall methods to the new method of that implementation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-112) Infinite loop on internal error in AbstractController change()

by Adrian Brock (JIRA)

Infinite loop on internal error in AbstractController change() -------------------------------------------------------------- Key: JBMICROCONT-112 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-112 Project: JBoss MicroContainer Issue Type: Bug Components: Dependency Affects Versions: JBossMC_2_0_0M1 Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossMC_2_0_0 Beta There is an infinite loop in the AbstractController change() method if there is an internal error. This is because when it spots the internal error, it just logs it and returns. The fix is to throw an error to break out of the loop that "bumps" the context through the states. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-3880) java.rmi.ConnectException: Failed to communicate (java.net.SocketTimeoutException: Read timed out)

by nishu_saini (JIRA)

java.rmi.ConnectException: Failed to communicate (java.net.SocketTimeoutException: Read timed out) -------------------------------------------------------------------------------------------------- Key: JBAS-3880 URL: http://jira.jboss.com/jira/browse/JBAS-3880 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-4.0.4RC1, JBossAS-4.0.3 SP1 Environment: Windows 2003 Server, Windows XP, J2SDK 1.4.2, JDK 1.5.0_09 Reporter: nishu_saini Assigned To: Scott M Stark Hi I have a client application which is accessing a Remote EJB deployed over JBoss AS 4.0.4 RC1 and JBoss AS 4.0.3 SP1. The client sends and recieves some large chunks of data to and from the server. But the following exception has started to come on client very frequently. Can we increase The Time out? Is the time out occurring during the reciept or sending of data or during the ping pong between server and client? How can we solve this problem? What is the cause of this problem? java.rmi.ConnectException: Failed to communicate; nested exception is: java.net.SocketTimeoutException: Read timed out at org.jboss.invocation.pooled.interfaces.PooledInvokerProxy.invoke(PooledInvokerProxy.java:382) at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:227) at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:167) at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55) at org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:97) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86) ... 8 more Caused by: java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at java.io.ObjectInputStream$PeekInputStream.peek(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.peek(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at org.jboss.invocation.pooled.interfaces.PooledInvokerProxy.invoke(PooledInvokerProxy.java:366) ... 14 more If any body finds the solution of this problem, please tell us. Thanks Nishant Saini http://www.simplyjava.com -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 8 months

3
3
0 / 0

[JBoss JIRA] Commented: (JBAS-3158) Need a way to detect collisions between JSF RI and JSF MyFaces

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3158?page=comments#action_12347751 ] Dimitris Andreadis commented on JBAS-3158: ------------------------------------------ Stan, do you want to schedule this for 4.2.0.CR1 ? > Need a way to detect collisions between JSF RI and JSF MyFaces > -------------------------------------------------------------- > > Key: JBAS-3158 > URL: http://jira.jboss.com/jira/browse/JBAS-3158 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Stan Silvert > Assigned To: Stan Silvert > Priority: Minor > > Developers who choose to bundle the Sun JSF Reference Implementation with their WAR will get strange errors like ERROR [javax.faces.webapp.UIComponentTag] Faces context not found. getResponseWriter will fail. Check if the FacesServlet has been initialized at all in your web.xml. > This is because of collisions between classes provided in both implementations which are required to have the same javax.faces package name. We should be able to detect if the RI is present and tell the user to either remove the RI, remove MyFaces, or scope the deployment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 8 months

1
0
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 November 2006