June 2007 - jboss-user - Jboss List Archives

by stephen.friedrich

Huh? Either I am not understanding the anwser or Gavin, you did not understand the question. What if the maximum length changes to 5? Currently you have to update both the entity and the xhtml. Is there any possibility to avoid this? A JSF component or validator that queries the bean's metadata? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051380#4051380 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051380

19 years

1
0
0 / 0

[JBossWS] - Stop enforcing parameter names?

by bcowan

I've recently updated a web service from JBoss 4.0.2 to 4.0.5 with JBossWS 1.2.1, and it's causing problems. The new setup enforces the proper naming of method parameters, instead of just taking them positionally. Some older clients don't send the proper parameter names. For example, Axis generated clients just call them "in0", "in1", "in2", etc. Whereas the old server happily accepted this, the new one throws a NotFound exception because the WSDL lists them as "String_1", "String_2", and so on. Is there any way to stop enforcing parameter names? The WSDL specifies the proper order, and this is all we need. It is important so remain compatible with old clients without changing the WSDL. Thanks, Bruce View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051378#4051378 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051378

19 years

1
0
0 / 0

[JBoss Portal] - Re: Unique constraint (JBOSSPORTAL.SYS_C0034349) violated

by sasiportal

Hi sohil, I made changes. I replaced with 2.4.2 Final build files, But Still i am facing same problem, I am looking for your help. Your help will be appreciated. Thanks sasiumar View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051377#4051377 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051377

19 years

1
0
0 / 0

[JBoss Seam] - required jars & config

by urosmil

Hi, I am trying to start app with seam on tomcat 5.5. I have spend whole day and I can't. Questions: 1) What are required jars (all of them) for seam to work on tomcat 5.5 with JSF RI 1.1 and Facelets BUT WITHOUT EJB3 - JUST JPA + HIBERNATE? 2) Also how should web.xml and faces-config.xml look? 3) What other config files should be present (seam.properties, pages.xml, components.xml, ...) and where I should put them? Comments: 1) Examples structure is very confusing with resource folder. 2) There should be more examples without ejb3 required and with facelets. Thanks, Uros. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051375#4051375 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051375

19 years

1
0
0 / 0

[JBoss Messaging] - Exceptions and Inconsistent Display of listMessageCountersAs

by rtm333

Hi, JBoss Messaging 1.3.0.GA on JBoss AS 4.2.0.GA shows the following behaviour: When opening and closing JMS sessions in quick succession while concurrently publishing messages at a fast rate (using the test program from JIRA JBMESSAGING-962) exceptions as the ones below are thrown on the server side: | ... | 14:38:52,589 ERROR [ExceptionUtil] ConsumerEndpoint[2596] close [a5g2y2e-9slm11-f2kcioip-1-f2kcyvu5-10w] | java.lang.IllegalStateException: Cannot remove references while deliveries are in progress | at org.jboss.messaging.core.ChannelSupport.removeAllReferences(ChannelSupport.java:340) | at org.jboss.messaging.core.plugin.postoffice.DefaultPostOffice.unbindQueue(DefaultPostOffice.java:240) | at org.jboss.jms.server.endpoint.ServerConsumerEndpoint.localClose(ServerConsumerEndpoint.java:502) | at org.jboss.jms.server.endpoint.ServerConsumerEndpoint.close(ServerConsumerEndpoint.java:381) | at org.jboss.jms.server.endpoint.advised.ConsumerAdvised.org$jboss$jms$server$endpoint$advised$ConsumerAdvised$close$aop(ConsumerAdvised.java:59) | at org.jboss.jms.server.endpoint.advised.ConsumerAdvised$close_N4742752445160157748.invokeNext(ConsumerAdvised$close_N4742752445160157748.java) | at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105) | at org.jboss.jms.server.endpoint.advised.ConsumerAdvised$close_N4742752445160157748.invokeNext(ConsumerAdvised$close_N4742752445160157748.java) | at org.jboss.jms.server.endpoint.advised.ConsumerAdvised.close(ConsumerAdvised.java) | at org.jboss.jms.wireformat.CloseRequest.serverInvoke(CloseRequest.java:66) | at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:141) | 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) | 14:38:52,591 WARN [Dispatcher] Cannot find object with id 2596 to register | 14:38:52,592 ERROR [ExceptionUtil] SessionEndpoint[2595] close [a5g2y2e-9slm11-f2kcioip-1-f2kcyvu8-10x] | javax.jms.IllegalStateException: Cannot find binding for topic sub with queue name: a5g2y2e-9slm11-f2kcioip-1-f2kcyv93-10u | at org.jboss.jms.server.endpoint.ServerConsumerEndpoint.localClose(ServerConsumerEndpoint.java:490) | at org.jboss.jms.server.endpoint.ServerSessionEndpoint.localClose(ServerSessionEndpoint.java:795) | at org.jboss.jms.server.endpoint.ServerSessionEndpoint.close(ServerSessionEndpoint.java:275) | at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$close$aop(SessionAdvised.java:70) | at org.jboss.jms.server.endpoint.advised.SessionAdvised$close_N4742752445160157748.invokeNext(SessionAdvised$close_N4742752445160157748.java) | at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105) | at org.jboss.jms.server.endpoint.advised.SessionAdvised$close_N4742752445160157748.invokeNext(SessionAdvised$close_N4742752445160157748.java) | at org.jboss.jms.server.endpoint.advised.SessionAdvised.close(SessionAdvised.java) | at org.jboss.jms.wireformat.CloseRequest.serverInvoke(CloseRequest.java:66) | at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:141) | 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) | ... | In addition, the result of the method listMessageCountersAsHTML() of the ServerPeer in the JMX Console shows stranded subscriptions. Even long after closing all subscriptions, this list shows still some forty entries. One of these entries is for "a5g2y2e-9slm11-f2kcioip-1-f2kcyv93-10u", mentioned in the second exception above. The result of listAllSubscriptionsAsHTML() of the used topic is empty at the same time. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051374#4051374 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051374

19 years

1
0
0 / 0

[JBoss Messaging] - Re: [Error] Failed to expire delivery

by timfox

Please *always* state your versions when you make a post!! (I don't know how many times I have to say this to people) :) Anyway I suspect you are using a version prior to 1.3.0.GA since this looks like this bug http://jira.jboss.com/jira/browse/JBMESSAGING-951 which was fixed in 1.3.0.GA View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051369#4051369 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051369

19 years

1
0
0 / 0

[JBoss Seam] - Re: DOCTYPE definition on *pages.xml performance warning/imp

by lowecg2004

anonymous wrote : Sometimes we want to reuse the same components.xml file with minor changes during both deployment and testing. Seam lets you place wildcards of the form @wildcard@ in the components.xml file which can be replaced | either by your Ant build script (at deployment time) or by providing a file named components.properties in the classpath (at development time). You'll see this approach used in the Seam examples. Sorry, I'd misread the reference manual on that one. My mistake... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051368#4051368 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051368

19 years

1
0
0 / 0

[JBoss Messaging] - [Error] Failed to expire delivery

by Elvoret

Hi All, I'm trying to send messages from servlet inside JBoss to JMS Queue and I've encountered a strange error: "Failed to expire delivery". What can cause such error? Servlet code that sends messages: private void sendMessage(String messageText) throws JMSException, NamingException | { | String destinationName = "/queue/clickstream-client" + random.nextInt(10); | | InitialContext ic = null; | ConnectionFactory cf = null; | Connection connection = null; | try { | ic = new InitialContext(); | cf = (ConnectionFactory) ic.lookup("/ConnectionFactory"); | Queue queue = (Queue) ic.lookup(destinationName); | connection = cf.createConnection(); | Session session = connection.createSession(false, | Session.AUTO_ACKNOWLEDGE); | MessageProducer sender = session.createProducer(queue); | sender.setDeliveryMode(DeliveryMode.PERSISTENT); | Message msg = session.createTextMessage(messageText); | sender.setTimeToLive(1000 * 60 * 60 * 24 * 30); | sender.send(msg); | } finally { | if (ic != null) { | try { | ic.close(); | } catch (Exception e) { | throw new RuntimeException(e); | } | } | | closeConnection(connection); | } | } Server log: 2007-06-05 17:58:44,593 DEBUG [org.jboss.remoting.transport.socket.MicroSocketClientInvoker] SocketClientInvoker[45f4ae, bisocket://192.168.10.139:247586041] setting shouldCheckConnection to false | 2007-06-05 17:58:44,593 DEBUG [org.jboss.remoting.transport.socket.SocketClientInvoker] SocketClientInvoker[45f4ae, bisocket://192.168.10.139:247586041] setting timeout to 0 | 2007-06-05 17:58:44,593 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] registered 5c4oa3v-nb50ro-f2kftkar-1-f2kftlb7-7 -> SocketClientInvoker[45f4ae, bisocket://192.168.10.139:247586041] | 2007-06-05 17:58:44,593 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] got control socket: Socket[addr=/192.168.10.139,port=1864,localport=2243] | 2007-06-05 17:58:44,593 DEBUG [org.jboss.remoting.MicroRemoteClientInvoker] SocketClientInvoker[45f4ae, bisocket://192.168.10.139:247586041] connecting | 2007-06-05 17:58:44,593 DEBUG [org.jboss.remoting.MicroRemoteClientInvoker] SocketClientInvoker[45f4ae, bisocket://192.168.10.139:247586041] connected | 2007-06-05 17:58:44,593 DEBUG [org.jboss.remoting.callback.DefaultCallbackErrorHandler] DefaultCallbackErrorHandler[UNITIALIZED] setting server invoker to SocketServerInvoker[192.168.10.139:4457] | 2007-06-05 17:58:44,593 DEBUG [org.jboss.remoting.callback.DefaultCallbackErrorHandler] DefaultCallbackErrorHandler[SocketServerInvoker[192.168.10.139:4457]] setting callback handler to ServerInvokerCallbackHandler[5c4oa3v-nb50ro-f2kftkar-1-f2kftl60-4+5c4oa3v-nb50ro-f2kftkar-1-f2kftlb7-7] | 2007-06-05 17:58:44,593 DEBUG [org.jboss.remoting.callback.ServerInvokerCallbackHandler] Session id for callback handler is 5c4oa3v-nb50ro-f2kftkar-1-f2kftl60-4+5c4oa3v-nb50ro-f2kftkar-1-f2kftlb7-7 | 2007-06-05 17:58:44,593 DEBUG [org.jboss.jms.server.remoting.JMSServerInvocationHandler] adding callback handler ServerInvokerCallbackHandler[5c4oa3v-nb50ro-f2kftkar-1-f2kftl60-4+5c4oa3v-nb50ro-f2kftkar-1-f2kftlb7-7] | 2007-06-05 17:58:44,593 DEBUG [org.jboss.jms.server.remoting.JMSServerInvocationHandler] found calllback handler for remoting session ...-f2kftl60-4 | 2007-06-05 17:58:44,593 DEBUG [org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint] creating a new connection for user null | 2007-06-05 17:58:44,593 DEBUG [org.jboss.jms.server.connectionmanager.SimpleConnectionManager] registered connection ConnectionEndpoint[5] as ...-f2kftl60-4 | 2007-06-05 17:58:44,593 DEBUG [org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint] created and registered ConnectionEndpoint[5] | 2007-06-05 17:58:44,906 DEBUG [org.jboss.jms.server.endpoint.ServerConnectionEndpoint] ConnectionEndpoint[5] creating non transacted session, AUTO_ACKNOWLEDGE, non XA | 2007-06-05 17:58:44,906 DEBUG [org.jboss.jms.server.endpoint.ServerConnectionEndpoint] created and registered SessionEndpoint[6] | 2007-06-05 17:58:44,906 DEBUG [org.jboss.jms.server.endpoint.ServerConnectionEndpoint] created SessionDelegate[16987790, ID=6] | 2007-06-05 17:58:45,312 DEBUG [org.jboss.jms.server.security.SecurityMetadataStore] No SecurityMetadadata was available for clickstream-client0, using default security config | 2007-06-05 17:58:45,328 DEBUG [org.jboss.jms.server.endpoint.ServerConsumerEndpoint] ConsumerEndpoint[7] constructed | 2007-06-05 17:58:45,453 DEBUG [org.jboss.jms.server.endpoint.ServerSessionEndpoint] SessionEndpoint[6] created and registered ConsumerEndpoint[7] | 2007-06-05 17:58:45,515 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@91f0de, cl=org.jboss.mx.loading.HeirarchicalLoaderRepository3$CacheClassLoader@1a28183{ url=null ,addedOrder=0} | 2007-06-05 17:58:47,437 ERROR [org.jboss.jms.server.endpoint.ServerConsumerEndpoint] Failed to expire delivery: Delivery[Reference[11264]:RELIABLE](done) | java.lang.IllegalArgumentException: Cannot find mutex in map for JBossMessage[11264]:PERSISTENT | at org.jboss.messaging.core.plugin.LockMap.releaseLock(LockMap.java:89) | at org.jboss.messaging.core.plugin.JDBCPersistenceManager.releaseLocks(JDBCPersistenceManager.java:3378) | at org.jboss.messaging.core.plugin.JDBCPersistenceManager.handleBeforeCommit1PC(JDBCPersistenceManager.java:2312) | at org.jboss.messaging.core.plugin.JDBCPersistenceManager$TransactionCallback.beforeCommit(JDBCPersistenceManager.java:3777) | at org.jboss.messaging.core.tx.Transaction.commit(Transaction.java:208) | at org.jboss.jms.server.endpoint.ServerSessionEndpoint.moveInTransaction(ServerSessionEndpoint.java:1083) | at org.jboss.jms.server.endpoint.ServerSessionEndpoint.expireDelivery(ServerSessionEndpoint.java:743) | at org.jboss.jms.server.endpoint.ServerConsumerEndpoint.handle(ServerConsumerEndpoint.java:208) | at org.jboss.messaging.core.local.RoundRobinPointToPointRouter.handle(RoundRobinPointToPointRouter.java:120) | at org.jboss.messaging.core.ChannelSupport.deliverInternal(ChannelSupport.java:600) | at org.jboss.messaging.core.ChannelSupport$InMemoryCallback.afterCommit(ChannelSupport.java:1017) | at org.jboss.messaging.core.tx.Transaction.commit(Transaction.java:228) | at org.jboss.jms.server.endpoint.ServerSessionEndpoint.moveInTransaction(ServerSessionEndpoint.java:1083) | at org.jboss.jms.server.endpoint.ServerSessionEndpoint.expireDelivery(ServerSessionEndpoint.java:743) | at org.jboss.jms.server.endpoint.ServerConsumerEndpoint.handle(ServerConsumerEndpoint.java:208) | at org.jboss.messaging.core.local.RoundRobinPointToPointRouter.handle(RoundRobinPointToPointRouter.java:120) | at org.jboss.messaging.core.ChannelSupport.deliverInternal(ChannelSupport.java:600) | at org.jboss.messaging.core.ChannelSupport$InMemoryCallback.afterCommit(ChannelSupport.java:1017) | at org.jboss.messaging.core.tx.Transaction.commit(Transaction.java:228) | at org.jboss.jms.server.endpoint.ServerSessionEndpoint.moveInTransaction(ServerSessionEndpoint.java:1083) | at org.jboss.jms.server.endpoint.ServerSessionEndpoint.expireDelivery(ServerSessionEndpoint.java:743) | at org.jboss.jms.server.endpoint.ServerConsumerEndpoint.handle(ServerConsumerEndpoint.java:208) | at org.jboss.messaging.core.local.RoundRobinPointToPointRouter.handle(RoundRobinPointToPointRouter.java:120) | at org.jboss.messaging.core.ChannelSupport.deliverInternal(ChannelSupport.java:600) | at org.jboss.messaging.core.ChannelSupport$InMemoryCallback.afterCommit(ChannelSupport.java:1017) | | ... (repeated many times) ... | | at org.jboss.messaging.core.tx.Transaction.commit(Transaction.java:228) | at org.jboss.jms.server.endpoint.ServerSessionEndpoint.moveInTransaction(ServerSessionEndpoint.java:1083) | at org.jboss.jms.server.endpoint.ServerSessionEndpoint.expireDelivery(ServerSessionEndpoint.java:743) | at org.jboss.jms.server.endpoint.ServerConsumerEndpoint.handle(ServerConsumerEndpoint.java:208) | at org.jboss.messaging.core.local.RoundRobinPointToPointRouter.handle(RoundRobinPointToPointRouter.java:120) | at org.jboss.messaging.core.ChannelSupport.deliverInternal(ChannelSupport.java:600) | at org.jboss.messaging.core.ChannelSupport$InMemoryCallback.afterCommit(ChannelSupport.java:1017) | at org.jboss.messaging.core.tx.Transaction.commit(Transaction.java:228) | at org.jboss.jms.server.endpoint.ServerSessionEndpoint.moveInTransaction(ServerSessionEndpoint.java:1083) | at org.jboss.jms.server.endpoint.ServerSessionEndpoint.expireDelivery(ServerSessionEndpoint.java:743) | at org.jboss.jms.server.endpoint.ServerConsumerEndpoint.handle(ServerConsumerEndpoint.java:208) | at org.jboss.messaging.core.local.RoundRobinPointToPointRouter.handle(RoundRobinPointToPointRouter.java:120) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051367#4051367 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051367

19 years

1
0
0 / 0

[JBoss Seam] - Seam gen problem

by carlos.abreu

Hy, i tried to use the seam gen shell script in my Ubuntu O.S and i had the following exception: root@carlosabreu-laptop:/opt/jboss-seam-1.2.1.GA# sh seam generate-entities Buildfile: build.xml validate-workspace: validate-project: generate-entities: [hibernate] Executing Hibernate Tool with a JDBC Configuration (for reverse engineering) [hibernate] 1. task: hbm2java (Generates a set of .java files) BUILD FAILED java.lang.NoClassDefFoundError: net.sf.cglib.core.DebuggingClassWriter$1 Does anyone know what is happening?? Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051365#4051365 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051365

19 years

1
0
0 / 0

[Security & JAAS/JBoss] - run-as value doesn't get authenticated (vs WebLogic, where i

by Mr_Anonymous

We are in the process of moving an application from WebLogic to JBoss. Under WebLogic, any of our run-as values needed to be in LDAP as well. That is, WLS appeared to verify their existence as users in LDAP, though not to the extent of actually logging them in with a password. JBoss seems to let me put anything I want as a run-as value. It isn't clear to me that WLS' behavior is required by spec, but it was a nice thing to have as a sort of sanity check. Is there some way to have JBoss do the same sort of check? (There could quite easily be some configuration option I've overlooked, as I'm still getting up to speed on JBoss.) Thanks! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051360#4051360 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051360

19 years

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-user June 2007