September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBAS-2566) Remove public interface changes from HEAD

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2566?page=all ] Adrian Brock closed JBAS-2566. ------------------------------ Resolution: Done Assignee: Adrian Brock (was: Elias Ross) No, I fixed this in the latest synchronization of the 4.0.x and 5.0.x trees. This removed the addition of the ThreadPool to the invoker/interceptor interfaces which should be handled in the same way as the org.jboss.mq.Recoverable interface I added. > Remove public interface changes from HEAD > ----------------------------------------- > > Key: JBAS-2566 > URL: http://jira.jboss.com/jira/browse/JBAS-2566 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: JMS service > Reporter: Elias Ross > Assigned To: Adrian Brock > Fix For: JBossAS-5.0.0.Beta > > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3643) null message blob is created in the jms_messages table which leads to PersistenceManager fail to restore queue during restart

by Edward Lu (JIRA)

null message blob is created in the jms_messages table which leads to PersistenceManager fail to restore queue during restart ----------------------------------------------------------------------------------------------------------------------------- Key: JBAS-3643 URL: http://jira.jboss.com/jira/browse/JBAS-3643 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.0.4.GA Environment: Windows XP, Oracle 9.2.0.5 Reporter: Edward Lu Assigned To: Adrian Brock Priority: Critical A null blob is inserted into the jms_message table as a result of sending message (greater than 4k messages) to jms queue. The Oracle jdbc persistence manager is deployed in our environment as JMS queue persistence mechanism. As a result, when JBoss is restarted, the persistence manager could not restore queue since there is null blob in the jms_messages table (please see the following stack traces and sqlplus output): I did a quick search and found that JBAS-2503 indicates the Oracle 4k limit problem should be resolved with JBossAS-4.0.4 GA. But I did run into the above problem with JBossAS-4.0.4 GA version. Your help is highly appreciated. **************************************************************************************** SQL> select count(*) from jms_messages where messageblob is null; COUNT(*) ---------- 3 ******************************************************************************************* 2006-09-11 15:56:43,447 WARN [ServiceController] - Problem starting service jboss.mq.destination:name=edAuditQueue,service=Queue^M org.jboss.mq.SpyJMSException: Unexpected error in recovery; - nested throwable: (java.lang.NullPointerException)^M at org.jboss.mq.SpyJMSException.getAsJMSException(SpyJMSException.java:78)^M at org.jboss.mq.SpyJMSException.rethrowAsJMSException(SpyJMSException.java:63)^M at org.jboss.mq.pm.jdbc2.PersistenceManager.restoreQueue(PersistenceManager.java:525)^M at org.jboss.mq.server.JMSQueue.<init>(JMSQueue.java:65)^M at org.jboss.mq.server.jmx.Queue.startService(Queue.java:78)^M ...... ...... Caused by: java.lang.NullPointerException^M at java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java:2150)^M at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2163)^M at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2631)^M at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:734)^M at java.io.ObjectInputStream.<init>(ObjectInputStream.java:253)^M at org.jboss.mq.pm.jdbc2.PersistenceManager.extractMessage(PersistenceManager.java:665)^M at org.jboss.mq.pm.jdbc2.PersistenceManager.internalRestoreQueue(PersistenceManager.java:556)^M at org.jboss.mq.pm.jdbc2.PersistenceManager.restoreQueue(PersistenceManager.java:514)^M ******************************************************************************************************************* -- 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, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-705) Pluggable default naming conventions for ejb3 jndi bindings

by Roland R?z (JIRA)

Pluggable default naming conventions for ejb3 jndi bindings ----------------------------------------------------------- Key: EJBTHREE-705 URL: http://jira.jboss.com/jira/browse/EJBTHREE-705 Project: EJB 3.0 Issue Type: Feature Request Reporter: Roland R?z Priority: Minor Currently the org.jboss.ejb3.ProxyFactoryHelper uses the [<earname>/]<ejbname>/[remote|local] naming convention. An Interface could provide the default names for jndi binding when the deployer doesn't provide them. The interface could look like this: public interface DefaultJndiNameProvider { String getDefaultRemoteJndiName(Container container); String getDefaultLocalJndiName(Container container); } The implementation of the DefaultJndiNameProvider could be configured using a System Property. -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-704) Missing privileged action to get Principal

by Roland R?z (JIRA)

Missing privileged action to get Principal ------------------------------------------- Key: EJBTHREE-704 URL: http://jira.jboss.com/jira/browse/EJBTHREE-704 Project: EJB 3.0 Issue Type: Bug Reporter: Roland R?z The method org.jboss.ejb3.BaseSessionContext.getCallerPrincipal should use a privileged action instead of SecurityAssociation.getCallerPrincipal(). @see http://jira.jboss.com/jira/browse/JBAOP-95 -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (BPEL-186) Write a blog entry about the beta release

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-186?page=comments#action_12343355 ] Alejandro Guizar commented on BPEL-186: --------------------------------------- Blog published: http://tinyurl.com/hjj4c > Write a blog entry about the beta release > ----------------------------------------- > > Key: BPEL-186 > URL: http://jira.jboss.com/jira/browse/BPEL-186 > Project: JBoss jBPM BPEL > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documents > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1 beta 2 > > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-750) NPE on TaskInstance.java on end() when TaskInstance created manually and no Task is assigned

by Uhyon Chung (JIRA)

NPE on TaskInstance.java on end() when TaskInstance created manually and no Task is assigned -------------------------------------------------------------------------------------------- Key: JBPM-750 URL: http://jira.jboss.com/jira/browse/JBPM-750 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.1.2 Environment: All Reporter: Uhyon Chung Assigned To: Tom Baeyens When you create a new TaskInstance manually (from a ActionHandler) without a Task assigned, an NPE occurs in a log statement in the end(Transition) method. If you take a look at the end method, it seems to allow null tasks, because it checks whether the task is null before execution methods on the task field. However, in the log.debug statement, it does not do this null check, which causes an NPE. I'm not quite sure if having a TaskInstance without a Task is really a good practice, but otherwise I would need to create a Task object and add it to the ProcessDefinition, which is definitely not something I want to be doing since I just want to add a task instance to the user's task list dynamically. I've created a small fix, and the patch is as follows.I made the patch based on the 3.1.2 on CVS using Eclipse patch. ### Eclipse Workspace Patch 1.0 #P jbpm3 Index: jpdl/jar/src/main/java/org/jbpm/taskmgmt/exe/TaskInstance.java =================================================================== RCS file: /cvsroot/jbpm/jbpm.3/jpdl/jar/src/main/java/org/jbpm/taskmgmt/exe/TaskInstance.java,v retrieving revision 1.6 diff -u -r1.6 TaskInstance.java --- jpdl/jar/src/main/java/org/jbpm/taskmgmt/exe/TaskInstance.java 8 Sep 2006 11:23:07 -0000 1.6 +++ jpdl/jar/src/main/java/org/jbpm/taskmgmt/exe/TaskInstance.java 15 Sep 2006 06:27:07 -0000 @@ if (transition==null) { - log.debug("completion of task '"+task.getName()+"' results in taking the default transition"); + log.debug("completion of task '"+(task==null?getName():task.getName())+"' results in taking the default transition"); token.signal(); } else { - log.debug("completion of task '"+task.getName()+"' results in taking transition '"+transition+"'"); + log.debug("completion of task '"+(task==null?getName():task.getName())+"' results in taking transition '"+transition+"'"); token.signal(transition); } } -464,10 +464,10 @@ ) { -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3494) failure in org.jboss.test.classloader.test.BasicLoaderUnitTestCase

by Prabhat Jha (JIRA)

failure in org.jboss.test.classloader.test.BasicLoaderUnitTestCase ------------------------------------------------------------------ Key: JBAS-3494 URL: http://jira.jboss.com/jira/browse/JBAS-3494 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ClassLoading, Test Suite Affects Versions: JBossAS-4.0.5.CR1 Environment: linux - dev03 in qa, java version "1.4.2_11" - jrockit Reporter: Prabhat Jha Assigned To: Scott M Stark Fix For: JBossAS-4.0.5.CR1 There is a failure in org.jboss.test.classloader.test.BasicLoaderUnitTestCase junit.framework.AssertionFailedError: Should not have gotten ExThrower methods at org.jboss.test.classloader.test.BasicLoaderUnitTestCase.testNoClassDefFoundError2(BasicLoaderUnitTestCase.java:109) at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source) There is no associated server log -- 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, 10 months

3
5
0 / 0

[JBoss JIRA] Closed: (JBIDE-303) Custom JBoss configuration wizard (ala JBoss installer)

by Robert Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-303?page=all ] Robert Stryker closed JBIDE-303. -------------------------------- Resolution: Rejected Feature decided against. > Custom JBoss configuration wizard (ala JBoss installer) > ------------------------------------------------------- > > Key: JBIDE-303 > URL: http://jira.jboss.com/jira/browse/JBIDE-303 > Project: JBoss IDE > Issue Type: Feature Request > Components: JBossAS Adapter > Reporter: Marshall Culpepper > Assigned To: Robert Stryker > Priority: Minor > Fix For: 2.0.0.GA > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Create a configuration wizard similar to the JBoss installation wizard that would allow the user to create a custom JBoss configuration from a standard JBoss installation. > Some ideas: > - Automatically secure jmx/admin consoles > - install/don't install certain services -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-364) Secured JBoss server configured via 'JBoss Server View' fail to Start/Debug

by Johans Marvin Taboada Villca (JIRA)

Secured JBoss server configured via 'JBoss Server View' fail to Start/Debug --------------------------------------------------------------------------- Key: JBIDE-364 URL: http://jira.jboss.com/jira/browse/JBIDE-364 Project: JBoss IDE Issue Type: Bug Components: JBossAS Adapter Affects Versions: 2.0.0.Beta1 Environment: Windows Server 2003 eclipse-M20060823-1200 JBoss-4.0.4.GA jdk1.5.0_06 MBean: org.jboss.jmx.connector.invoker.InvokerAdaptorService (jmx-invoker-service.xml) <interceptor code="org.jboss.jmx.connector.invoker.AuthenticationInterceptor" securityDomain="java:/jaas/jmx-console"/> jmx-console also secured with the same security Domain. Reporter: Johans Marvin Taboada Villca Assigned To: Robert Stryker Secured JBoss server configured via 'JBoss Server View' fail to Start/Debug when: - MBean: org.jboss.jmx.connector.invoker.InvokerAdaptorService has the security domain configured via uncomment ($JBOSS_HOME/server/x/deploy/jmx-invoker-service.xml): <descriptors> <interceptors> <interceptor code="org.jboss.jmx.connector.invoker.AuthenticationInterceptor" securityDomain="java:/jaas/jmx-console"/> </interceptors> </descriptors> Im assuming that the 'jmx-console' is also secured with the same security Domain. Posible cause: Access to server status via twiddle script (¿JBossAS Adapter?) doesn't use user/password options to manage authentication on the server. -- 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, 10 months

2
3
0 / 0

[JBoss JIRA] Updated: (EJBTHREE-641) entitymanager is null then using @WebService and @Stateless annotations in one class

by Bill Burke (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-641?page=all ] Bill Burke updated EJBTHREE-641: -------------------------------- Fix Version/s: EJB 3.0 RC10 - FD (was: EJB 3.0 RC9 - FD) > entitymanager is null then using @WebService and @Stateless annotations in one class > ------------------------------------------------------------------------------------ > > Key: EJBTHREE-641 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-641 > Project: EJB 3.0 > Issue Type: Bug > Affects Versions: EJB 3.0 RC8 - FD > Reporter: Ramil Israfilov > Fix For: EJB 3.0 RC10 - FD > > > I have a class with both @Stateless and @WebService annotation and injected entitymanager: > @WebService(name = "WebServiceTest", > targetNamespace = "http://accesspoint.jc/server" ) > @SOAPBinding(style = SOAPBinding.Style.DOCUMENT) > @BindingType(value=javax.xml.ws.soap.SOAPBinding.SOAP12HTTP_MTOM_BINDING) > @Remote(ServerInterface.class) > public class Server implements ServerInterface { > @PersistenceContext(unitName="CertiOneAccessPoint") > EntityManager em; > @WebMethod > public SessionResponse createSession(SessionRequest sessionRequest) { > log.debug("sessionRequest"+sessionRequest); > SessionResponse resp = new SessionResponse(); > Session session = new Session(); > session=(Session) em.persist(session); > resp.setSessionId(session.getId()); > return resp; > } > } > I can successfully package and deploy EAR file. > If I access EJB3 bean from remote application using JNDI lookup then everything works ok. > But if I try to access webservice I got null pointer exception on line: session=(Session) em.persist(session); > 2006-06-29 17:24:02,815 DEBUG [be.certipost.jc.accesspoint.server.impl.Server] sessionRequestbe.certipost.jc.accesspoint.server.SessionRequest@fbf04a > 2006-06-29 17:24:02,815 ERROR [STDERR] java.lang.NullPointerException > 2006-06-29 17:24:02,815 ERROR [STDERR] at be.certipost.jc.accesspoint.server.impl.Server.createSession(Server.java:51) > 2006-06-29 17:24:02,815 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > 2006-06-29 17:24:02,815 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > 2006-06-29 17:24:02,815 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > 2006-06-29 17:24:02,815 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585) > 2006-06-29 17:24:02,815 ERROR [STDERR] at com.sun.xml.ws.api.server.InstanceResolver$1.invoke(InstanceResolver.java:127) > 2006-06-29 17:24:02,815 ERROR [STDERR] at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:247) > 2006-06-29 17:24:02,815 ERROR [STDERR] at com.sun.xml.ws.server.sei.SEIInvokerPipe.process(SEIInvokerPipe.java:97) > 2006-06-29 17:24:02,815 ERROR [STDERR] at com.sun.xml.ws.protocol.soap.ServerMUPipe.process(ServerMUPipe.java:62) > 2006-06-29 17:24:02,815 ERROR [STDERR] at com.sun.xml.ws.server.WSEndpointImpl$1.process(WSEndpointImpl.java:139) > 2006-06-29 17:24:02,815 ERROR [STDERR] at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:139) > 2006-06-29 17:24:02,815 ERROR [STDERR] at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:211) > 2006-06-29 17:24:02,815 ERROR [STDERR] at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:97) > 2006-06-29 17:24:02,815 ERROR [STDERR] at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doPost(WSServletDelegate.java:161) > 2006-06-29 17:24:02,815 ERROR [STDERR] at com.sun.xml.ws.transport.http.servlet.WSServlet.doPost(WSServlet.java:49) > 2006-06-29 17:24:02,815 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > 2006-06-29 17:24:02,815 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) > 2006-06-29 17:24:02,815 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) > 2006-06-29 17:24:02,815 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > 2006-06-29 17:24:02,815 ERROR [STDERR] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > 2006-06-29 17:24:02,815 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > 2006-06-29 17:24:02,815 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > 2006-06-29 17:24:02,815 ERROR [STDERR] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) > 2006-06-29 17:24:02,815 ERROR [STDERR] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) > 2006-06-29 17:24:02,815 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) > 2006-06-29 17:24:02,815 ERROR [STDERR] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) > 2006-06-29 17:24:02,815 ERROR [STDERR] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) > 2006-06-29 17:24:02,815 ERROR [STDERR] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) > 2006-06-29 17:24:02,815 ERROR [STDERR] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) > 2006-06-29 17:24:02,815 ERROR [STDERR] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) > 2006-06-29 17:24:02,815 ERROR [STDERR] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) > 2006-06-29 17:24:02,815 ERROR [STDERR] at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) > 2006-06-29 17:24:02,815 ERROR [STDERR] at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) > 2006-06-29 17:24:02,815 ERROR [STDERR] at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) > 2006-06-29 17:24:02,831 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595) -- 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, 10 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 September 2006