October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4661) org.jboss.test.marshaliiop.test.EjbUnMarshalUnitTestCase.testUnMarshalException failing

by Adrian Brock (JIRA)

org.jboss.test.marshaliiop.test.EjbUnMarshalUnitTestCase.testUnMarshalException failing --------------------------------------------------------------------------------------- Key: JBAS-4661 URL: http://jira.jboss.com/jira/browse/JBAS-4661 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: IIOP service Reporter: Adrian Brock Assigned To: Francisco Reverbel Fix For: JBossAS-5.0.0.GA The ejb unmarshalling exception test is failing in head. This looks like it is a problem within JacORB or the JDK? JBoss is throwing the correct exception: 2007-09-04 15:47:26,829 TRACE [org.jboss.proxy.ejb.EjbObjectCorbaServant.marshalliiop/MarshallSession] Exception in EJBObject invocation org.omg.CORBA.MARSHAL: class not found: org.jboss.test.marshaliiop.TestPayload vmcid: 0x0 minor code: 0 completed: No at org.jacorb.orb.CDRInputStream.read_untyped_value(Unknown Source) at org.jacorb.orb.CDRInputStream.read_typed_value(Unknown Source) at org.jacorb.orb.CDRInputStream.read_value(Unknown Source) at org.jacorb.orb.Any.read_value(Unknown Source) at org.jacorb.orb.CDRInputStream.read_any(Unknown Source) at com.sun.corba.se.impl.javax.rmi.CORBA.Util.readAny(Util.java:401) at javax.rmi.CORBA.Util.readAny(Util.java:92) at org.jboss.iiop.rmi.marshal.CDRStream$ObjectReader.read(CDRStream.java:616) at org.jboss.iiop.rmi.marshal.strategy.SkeletonStrategy.readParams(SkeletonStrategy.java:128) at org.jboss.proxy.ejb.EjbObjectCorbaServant._invoke(EjbObjectCorbaServant.java:275) at org.jacorb.poa.RequestProcessor.invokeOperation(Unknown Source) at org.jacorb.poa.RequestProcessor.process(Unknown Source) at org.jacorb.poa.RequestProcessor.run(Unknown Source) But by the time it hits the client side, it has lost the information and throws it as an UNKNOWN? java.rmi.RemoteException: CORBA UNKNOWN 0 No; nested exception is: org.omg.CORBA.UNKNOWN: org.omg.CORBA.portable.UnknownException: vmcid: 0x0 minor code: 0 completed: No at com.sun.corba.se.impl.javax.rmi.CORBA.Util.mapSystemException(Util.java:282) at javax.rmi.CORBA.Util.mapSystemException(Util.java:67) at org.jboss.proxy.ejb.DynamicIIOPStub.invoke(DynamicIIOPStub.java:148) at org.jboss.proxy.ejb.DynamicIIOPStub.invokeInt(DynamicIIOPStub.java:242) at org.jboss.test.marshaliiop.interfaces._MarshalSession_Stub.testMethod(Unknown Source) at org.jboss.test.marshaliiop.test.EjbUnMarshalUnitTestCase.testUnMarshalException(EjbUnMarshalUnitTestCase.java:48) Caused by: org.omg.CORBA.UNKNOWN: org.omg.CORBA.portable.UnknownException: vmcid: 0x0 minor code: 0 completed: No at org.jacorb.orb.SystemExceptionHelper.read(SystemExceptionHelper.java:230) at org.jacorb.orb.ReplyReceiver.getReply(Unknown Source) at org.jacorb.orb.Delegate.invoke_internal(Unknown Source) at org.jacorb.orb.Delegate.invoke(Unknown Source) at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:457) at org.jboss.proxy.ejb.DynamicIIOPStub.invoke(DynamicIIOPStub.java:123) -- 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

17 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1050) Application client support for persistence unit

by Carlo de Wolf (JIRA)

Application client support for persistence unit ----------------------------------------------- Key: EJBTHREE-1050 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1050 Project: EJB 3.0 Issue Type: Task Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: HEAD See JavaEE 5 5.12. -- 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

17 years, 10 months

3
9
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1057) Create/update DTD/schemas for descriptors.

by Chris Laprun (JIRA)

Create/update DTD/schemas for descriptors. ------------------------------------------ Key: JBPORTAL-1057 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1057 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Documentation Affects Versions: 2.4 Final Reporter: Chris Laprun Assigned To: Roy Russo Priority: Minor Fix For: 2.4.1 Final -- 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

17 years, 10 months

7
11
0 / 0

[JBoss JIRA] Created: (JBAS-4812) Clients getting javax.ejb.NoSuchEJBException when using SFSB buddy replication

by Dominik Pospisil (JIRA)

Clients getting javax.ejb.NoSuchEJBException when using SFSB buddy replication ------------------------------------------------------------------------------ Key: JBAS-4812 URL: http://jira.jboss.com/jira/browse/JBAS-4812 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-4.2.0.GA Reporter: Dominik Pospisil Assigned To: Brian Stansberry Attachments: ejb3-buddy.tgz Attaching failover test log files. Note, that clients get those errors even before simulated failover. This is reproducible only with buddy replication turned on. -- 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

17 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-4529) Test a 4.2 release with a multiplexer sar

by Brian Stansberry (JIRA)

Test a 4.2 release with a multiplexer sar ----------------------------------------- Key: JBAS-4529 URL: http://jira.jboss.com/jira/browse/JBAS-4529 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Optional Plug in JGroups 2.5 or later, add a multiplexer sar and run the testsuite. Report any issues and add a wiki page explaining how to do it. This would be far from a full QA of the use of the multiplexer. No such sar would be include in any official 4.2 distro (see comments on parent issue for why not.) There would be no intent to try to support such usage (and the wiki *must* say that.) This is more in the spirit of providing a bit of info to community users who may want to try it themselves, at their own risk. -- 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

17 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-4608) Consider adding FLUSH to channels in Branch_4_x

by Brian Stansberry (JIRA)

Consider adding FLUSH to channels in Branch_4_x ----------------------------------------------- Key: JBAS-4608 URL: http://jira.jboss.com/jira/browse/JBAS-4608 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-4.2.2.GA David Ward experienced problems with virtual synchrony in demo apps he was running on 4.2.1.GA. These were resolved by adding FLUSH to the cluster-service.xml stack. Need to consider whether we should add FLUSH to the standard stacks in 4.2.x. -- 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

17 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (HIBERNATE-73) @OneToOne with @PrimaryKeyJoinColumn does not work right

by Tim McCune (JIRA)

@OneToOne with @PrimaryKeyJoinColumn does not work right -------------------------------------------------------- Key: HIBERNATE-73 URL: http://jira.jboss.com/jira/browse/HIBERNATE-73 Project: Hibernate Issue Type: Bug Environment: JBoss 4.2.1 Reporter: Tim McCune Assigned To: Steve Ebersole Given the following code: @Entity public class Employee { @Id Integer id; @OneToOne @PrimaryKeyJoinColumn EmployeeInfo info; ... } @Entity public class EmployeeInfo { @Id Integer id; ... } Hibernate creates EMPLOYEE and EMPLOYEEINFO tables, but does not create a foreign key relationship from EMPLOYEEINFO to EMPLOYEE. Furthermore, Hibernate does not set the EmployeeInfo's id correctly when persisting it. The following code: EmployeeInfo info = new EmployeeInfo(); employee.setInfo(info); does insert a new row into EMPLOYEEINFO, but it has an id of "1" when it should have an id that is the same as the corresponding Employee. -- 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

17 years, 10 months

5
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1123) When working with a snapshot release, JBM should report at boot "r<svn-revision-number" instead of the next point release

by Ovidiu Feodorov (JIRA)

When working with a snapshot release, JBM should report at boot "r<svn-revision-number" instead of the next point release -------------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-1123 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1123 Project: JBoss Messaging Issue Type: Feature Request Affects Versions: 1.4.0.GA Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Minor -- 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

17 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4644) fix org.jboss.test.webservice.jbws309.JBWS309TestCase(JACC) - 5 errors

by Dimitris Andreadis (JIRA)

fix org.jboss.test.webservice.jbws309.JBWS309TestCase(JACC) - 5 errors ---------------------------------------------------------------------- Key: JBAS-4644 URL: http://jira.jboss.com/jira/browse/JBAS-4644 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Assigned To: Thomas Diesler Fix For: JBossAS-5.0.0.Beta3 Problem appears either as: testRoleSecuredServiceAccess Error Call invocation failed; nested exception is: java.io.IOException: Could not transmit message java.rmi.RemoteException: Call invocation failed; nested exception is: java.io.IOException: Could not transmit message at org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:536) at org.jboss.ws.core.jaxrpc.client.CallImpl.invoke(CallImpl.java:277) at org.jboss.ws.core.jaxrpc.client.PortProxy.invoke(PortProxy.java:151) at $Proxy4.getContactInfo(Unknown Source) at org.jboss.test.webservice.jbws309.JBWS309TestCase.testRoleSecuredServiceAccess(JBWS309TestCase.java:190) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) Caused by: java.io.IOException: Could not transmit message at org.jboss.ws.core.client.RemotingConnectionImpl.invoke(RemotingConnectionImpl.java:204) at org.jboss.ws.core.client.SOAPRemotingConnection.invoke(SOAPRemotingConnection.java:77) at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:337) at org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:517) ... 25 more Caused by: org.jboss.remoting.CannotConnectException: Can not connect http client invoker. at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:332) at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:135) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) at org.jboss.remoting.Client.invoke(Client.java:1550) at org.jboss.remoting.Client.invoke(Client.java:530) at org.jboss.ws.core.client.RemotingConnectionImpl.invoke(RemotingConnectionImpl.java:183) ... 28 more Caused by: org.jboss.ws.WSException: Invalid HTTP server response [401] - Unauthorized at org.jboss.ws.core.soap.SOAPMessageUnMarshaller.read(SOAPMessageUnMarshaller.java:77) at org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse(HTTPClientInvoker.java:472) at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:304) ... 33 more Or testRoleSecuredSLSB Error SecurityException; nested exception is: javax.security.auth.login.FailedLoginException: Password Incorrect/Password Required java.rmi.AccessException: SecurityException; nested exception is: javax.security.auth.login.FailedLoginException: Password Incorrect/Password Required at org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:388) at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:136) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactoryFinderInterceptor.java:107) at org.jboss.ejb.SessionContainer.internalInvokeHome(SessionContainer.java:640) at org.jboss.ejb.Container.invoke(Container.java:1006) 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.unified.server.UnifiedInvoker.invoke(UnifiedInvoker.java:230) 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 javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:201) at $Proxy14.invoke(Unknown Source) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:734) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:560) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:383) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:165) Caused by: javax.security.auth.login.FailedLoginException: Password Incorrect/Password Required at org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:212) at org.jboss.security.auth.spi.UsersRolesLoginModule.login(UsersRolesLoginModule.java:152) at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769) at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186) at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680) at javax.security.auth.login.LoginContext.login(LoginContext.java:579) at org.jboss.security.plugins.JaasSecurityManager.defaultLogin(JaasSecurityManager.java:524) at org.jboss.security.plugins.JaasSecurityManager.authenticate(JaasSecurityManager.java:458) at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:353) at org.jboss.ejb.plugins.SecurityInterceptor.checkSecurityAssociation(SecurityInterceptor.java:317) at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:185) at org.jboss.ejb.plugins.security.PreSecurityInterceptor.invokeHome(PreSecurityInterceptor.java:140) at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:132) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactoryFinderInterceptor.java:107) at org.jboss.ejb.SessionContainer.internalInvokeHome(SessionContainer.java:640) at org.jboss.ejb.Container.invoke(Container.java:1006) 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.unified.server.UnifiedInvoker.invoke(UnifiedInvoker.java:230) 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 javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:201) at $Proxy14.invoke(Unknown Source) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:734) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:560) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:383) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:165) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163) at org.jboss.remoting.Client.invoke(Client.java:1550) at org.jboss.remoting.Client.invoke(Client.java:530) at org.jboss.invocation.unified.interfaces.UnifiedInvokerProxy.invoke(UnifiedInvokerProxy.java:161) at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:244) at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:181) at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:61) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:86) at org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java:184) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101) at $Proxy1.create(Unknown Source) at org.jboss.test.webservice.jbws309.JBWS309TestCase.testRoleSecuredSLSB(JBWS309TestCase.java:93) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) -- 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

17 years, 10 months

4
25
0 / 0

[JBoss JIRA] Created: (JBAS-3918) jbossweb virtual-host processing not working

by Scott M Stark (JIRA)

jbossweb virtual-host processing not working -------------------------------------------- Key: JBAS-3918 URL: http://jira.jboss.com/jira/browse/JBAS-3918 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-5.0.0.Beta1 Reporter: Scott M Stark Assigned To: Remy Maucherat Fix For: JBossAS-5.0.0.Beta2 Add a Host entry to the deployers/jbossweb.deployer/server.xml as described in the 4.0.x section of: http://wiki.jboss.org/wiki/Wiki.jsp?page=VirtualHosts for example: <Host name="succubus-vhost" autoDeploy="false" deployOnStartup="false" deployXML="false"> <Valve className="org.apache.catalina.valves.AccessLogValve" prefix="succubus-vhost" suffix=".log" pattern="common" directory="${jboss.server.home.dir}/log"/> </Host> add a virtual-host entry to the jmx-console.war/WEB-INF/jboss-web.xml: <jboss-web> <virtual-host>succubus-vhost</virtual-host> </jboss-web> and try to access the jmx-console using succubus-vhost: [starksm@succubus Security]$ wget http://succubus-vhost:8080/jmx-console/index.jsp --08:21:41-- http://succubus-vhost:8080/jmx-console/index.jsp => `index.jsp' Resolving succubus-vhost... 192.168.10.10 Connecting to succubus-vhost|192.168.10.10|:8080... connected. HTTP request sent, awaiting response... 400 No Host matches server name succubus-vhost 08:21:41 ERROR 400: No Host matches server name succubus-vhost. -- 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

17 years, 10 months

7
10
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 October 2007