Unexpected Broker Exception

Hi,
what does this transaction mean?
regards
Ricky
[24/Aug/2009:10:08:17 MEST] WARNING [B3229]: Transaction acknowledgement [79836403-172.23.150.105(c6:7d:dd:e5:f4:43)-50988-1251100039059, [consumer:818849448456328192, type=NONE]]TUID=818849514206184448 processing failed: Unexpected Broker Exception: [Transaction [consumer:818849448456328192, type=NONE] has state [COMMITED(6)], not in [STARTED(1)] state]:
com.sun.messaging.jmq.jmsserver.util.BrokerException: Unexpected Broker Exception: [Transaction [consumer:818849448456328192, type=NONE] has state [COMMITED(6)], not in [STARTED(1)] state]

Hi,
the exception looks like this:
[#|2009-08-24T10:08:17.049+0200|WARNING|IS5.1.3|com.stc.jmsjca.core.WorkContainer|_ThreadID=187; ThreadName=Worker: 101; Context=dpRouting_TRprjRoutingCo1922141060/Connectivity_queToRouting_srvRoute_ejb;|JMSJCA-E064: Unexpected exception encountered while executing a JMS CC-session: java.lang.RuntimeException: [ACKNOWLEDGE_REPLY(25)] [C4036]: A server error occurred. : Unexpected Broker Exception: [Transaction [consumer:818849448456328192, type=NONE] has state [COMMITED(6)], not in [STARTED(1)] state] user=infointernal, broker=svrai09.vt.ch:7679(45634)
java.lang.RuntimeException: [ACKNOWLEDGE_REPLY(25)] [C4036]: A server error occurred. : Unexpected Broker Exception: [Transaction [consumer:818849448456328192, type=NONE] has state [COMMITED(6)], not in [STARTED(1)] state] user=infointernal, broker=svrai09.vt.ch:7679(45634)
     at com.sun.messaging.jmq.jmsclient.ServerSessionRunner.run(ServerSessionRunner.java:113)
     at com.sun.messaging.jmq.jmsclient.SessionImpl.run(SessionImpl.java:2623)
     at com.stc.jmsjca.core.WorkContainer.run(WorkContainer.java:198)
     at com.sun.enterprise.connectors.work.OneWork.doWork(OneWork.java:54)
     at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:382)
|#]

Similar Messages

Unexpected Broker Exception: [can not close un-opened protocol] ???

Hi,
Has anyone seen this problem in the log file.... It occurred during a shutdown of the broker... Is it something I need to worried about?
Broker Startup Info:
================================================================================
Open Message Queue 4.3
Sun Microsystems, Inc.
Version: 4.3 (Build 7-g)
Compile: Fri Nov 7 19:11:27 PST 2008
Copyright (c) 2007 Sun Microsystems, Inc. All rights reserved. Use is
subject to license terms.
================================================================================
Java Runtime: 1.6.0_07 Sun Microsystems Inc. /usr/jdk/instances/jdk1.6.0/jre
[30/Jan/2009:11:45:08 MST] Syncing message store: false
[30/Jan/2009:11:45:08 MST]    IMQ_HOME=/opt/openmq/mq
[30/Jan/2009:11:45:08 MST] IMQ_VARHOME=/opt/openmq/var/mq
[30/Jan/2009:11:45:08 MST] SunOS 5.11 amd64 vdev3th (4 cpu) root
[30/Jan/2009:11:45:08 MST] Max file descriptors: 65536 (65536)
[30/Jan/2009:11:45:08 MST] Java Heap Size: max=933888k, current=253184k
[30/Jan/2009:11:45:08 MST] Arguments: -loglevel DEBUGHIGH -force -passfile /var/svc/profile/openmq.passfile
[30/Jan/2009:11:45:08 MST] Initializing ClusterDiscoveryService
[30/Jan/2009:11:45:08 MST] [B1004]: Starting the portmapper service using tcp [ 7676, 50, * ] with min threads 1 and max threads of 1
[30/Jan/2009:11:45:08 MST] [B1060]: Loading persistent data...
[30/Jan/2009:11:45:08 MST] Using built-in file-based persistent store: /opt/openmq/var/mq/instances/imqbroker/
[30/Jan/2009:11:45:08 MST] attempting to set Message Bytes Limit to 10240K for destination mq.sys.dmq [Queue]
[30/Jan/2009:11:45:08 MST] attempting to set Message Count Limit to 1000 for destination mq.sys.dmq [Queue]
[30/Jan/2009:11:45:08 MST] Loading Stored destination mq.sys.dmq [Queue] connectionUID=null
[30/Jan/2009:11:45:17 MST] [B1007]: Stopping Service jms with protocol tcp(host = *, port=0, mode=dedicated)
[30/Jan/2009:11:45:17 MST] Exception shutting down protocol, ignoring since we are exiting:
java.io.IOException: Unexpected Broker Exception: [can not close un-opened protocol]
        at com.sun.messaging.jmq.jmsserver.net.tcp.TcpProtocol.close(TcpProtocol.java:353)
        at com.sun.messaging.jmq.jmsserver.service.imq.IMQIPService.stopService(IMQIPService.java:292)
        at com.sun.messaging.jmq.jmsserver.service.ServiceInfo.stop(ServiceManager.java:664)
        at com.sun.messaging.jmq.jmsserver.service.ServiceManager.stopService(ServiceManager.java:307)
        at com.sun.messaging.jmq.jmsserver.service.ServiceManager.stopAllActiveServices(ServiceManager.java:430)
        at com.sun.messaging.jmq.jmsserver.BrokerStateHandler$ShutdownRunnable.shutdown(BrokerStateHandler.java:483)
        at com.sun.messaging.jmq.jmsserver.BrokerStateHandler$ShutdownRunnable.run(BrokerStateHandler.java:383)
        at java.lang.Thread.run(Thread.java:619)
[30/Jan/2009:11:45:17 MST] Session: Resuming Session [5282756623254863360][0]Consumer.java: resuming after detatch Consumer - Q:temporary_destination:__queue_10.80.165.6_65423_1:[consumer:5282756623254870016, type=CLIENT_ACKNOWLEDGE]
[30/Jan/2009:11:45:17 MST] JMX Connector Server jmxrmi stopped successfully
[30/Jan/2009:11:45:17 MST] Cleaning up transactions on connection IMQConnCLOSED,[email protected]:65423,admin:44113
[30/Jan/2009:11:45:17 MST] Destroying temp destination Q:temporary_destination:__queue_10.80.165.6_65423_1 on connection death
[30/Jan/2009:11:45:17 MST] [B1159]: Destination temporary_destination://queue/10.80.165.6/65423/1 [Queue] has been destroyed
[30/Jan/2009:11:45:17 MST] WARNING [B2181]: Removing 1 messages associated with destination temporary_destination://queue/10.80.165.6/65423/1 [Queue]
[30/Jan/2009:11:45:17 MST] Cleaning up transactions on connection IMQConnCLOSED,[email protected]:65423,admin:44113
[30/Jan/2009:11:45:17 MST] [B1066]:   Closing: [email protected]:65423->admin:44113 because "[B0061]: Client exited without closing connections". Count: service=0 broker=0
[30/Jan/2009:11:45:17 MST] closed connection IMQConnDESTROYING,[email protected]:65423,admin:44113:
java.io.IOException: [B4117]: Unexpected Broker Exception: [destroyed Connection]
        at com.sun.messaging.jmq.jmsserver.service.imq.IMQIPConnection.writeData(IMQIPConnection.java:1563)
        at com.sun.messaging.jmq.jmsserver.service.imq.IMQIPConnection.process(IMQIPConnection.java:631)
        at com.sun.messaging.jmq.jmsserver.service.imq.OperationRunnable.process(OperationRunnable.java:170)
        at com.sun.messaging.jmq.jmsserver.util.pool.BasicRunnable.run(BasicRunnable.java:493)
        at java.lang.Thread.run(Thread.java:619)
[30/Jan/2009:11:45:18 MST] [B1048]: Shutdown of broker complete.
[30/Jan/2009:11:45:18 MST] Broker exiting with status=0 because [B1199]: Shutdown Requested by adminIf more detail are needed, please ask and I will supply whatever is necessary...
Thanks.
-Howard
Edited by: Turret on Jan 30, 2009 1:10 PM

Hi Tom,
Thanks for the quick response!
I am glad to hear that the log level is the reason for the output and not an issue with the broker!
Thanks again....
-Howard

Unexpected Broker Exception: [destroyed Connection]

I am new to broker(s).
Can anyone help.
Mike
15/Mar/2007:12:14:47 PDT]
Connections: 0 JVM Heap: 33226752 bytes (30476096 free) Threads: 2 (14-1010)
In: 1 msgs (728 bytes) 14 pkts (2386 bytes)
Out: 0 msgs (0 bytes) 14 pkts (2795 bytes)
Rate In: 0 msgs/sec (0 bytes/sec) 0 pkts/sec (0 bytes/sec)
Rate Out: 0 msgs/sec (0 bytes/sec) 0 pkts/sec (0 bytes/sec)
[15/Mar/2007:12:15:28 PDT] Received JMQRBufferSize -100
[15/Mar/2007:12:15:28 PDT] [B1065]: Accepting: [email protected]:39174->jms:39104. Count=1
[15/Mar/2007:12:15:28 PDT] Created new session 1984136176305554944 on connection 1984136176305549056
[15/Mar/2007:12:15:28 PDT] Creating new Producer 1984136176305558016 on Q:myTestQueue for connection 1984136176305549056
[15/Mar/2007:12:15:28 PDT] Producer Producer[1984136176305558016,Q:myTestQueue,1984136176305549056] is true
[15/Mar/2007:12:15:28 PDT] Cleaning up transactions on connection IMQConn[CLOSED,[email protected]:39174,jms:39104]
[15/Mar/2007:12:15:28 PDT] closed connection IMQConn[DESTROYING,[email protected]:39174,jms:39104]:
java.io.IOException: [B4117]: Unexpected Broker Exception: [destroyed Connection]
at com.sun.messaging.jmq.jmsserver.service.imq.IMQConnection.writeData (IMQConnection.java:1930)
at com.sun.messaging.jmq.jmsserver.service.imq.IMQConnection.process(IMQConnection.java:803)
at com.sun.messaging.jmq.jmsserver.service.imq.OperationRunnable.process(OperationRunnable.java :141)
at com.sun.messaging.jmq.jmsserver.util.pool.BasicRunnable.run(BasicRunnable.java:459)
at java.lang.Thread.run(Thread.java:595)
[15/Mar/2007:12:15:28 PDT] [B1066]: Closing: [email protected]:39174->jms:39104 because "[B0059]: Client closed the connection". Count=0
[15/Mar/2007:12:15:47 PDT]
Connections: 0 JVM Heap: 33226752 bytes (30083968 free) Threads: 2 (14-1010)
In: 2 msgs (1632 bytes) 28 pkts (4949 bytes)
Out: 0 msgs (0 bytes) 28 pkts (5590 bytes)
Rate In: 0 msgs/sec (15 bytes/sec) 0 pkts/sec (42 bytes/sec)
Rate Out: 0 msgs/sec (0 bytes/sec) 0 pkts/sec (46 bytes/sec)

Hi Tom,
Thanks for the quick response!
I am glad to hear that the log level is the reason for the output and not an issue with the broker!
Thanks again....
-Howard

PasswordSync Unexpected Broker Exception: [destroyed Connection]

DEBUGHIGH set on brokerd
metrics set to 60 on brokerd
Help appreciated.
15/Mar/2007:12:14:47 PDT]
Connections: 0 JVM Heap: 33226752 bytes (30476096 free) Threads: 2 (14-1010)
In: 1 msgs (728 bytes) 14 pkts (2386 bytes)
Out: 0 msgs (0 bytes) 14 pkts (2795 bytes)
Rate In: 0 msgs/sec (0 bytes/sec) 0 pkts/sec (0 bytes/sec)
Rate Out: 0 msgs/sec (0 bytes/sec) 0 pkts/sec (0 bytes/sec)
[15/Mar/2007:12:15:28 PDT] Received JMQRBufferSize -100
[15/Mar/2007:12:15:28 PDT] [B1065]: Accepting: [email protected]:39174->jms:39104. Count=1
[15/Mar/2007:12:15:28 PDT] Created new session 1984136176305554944 on connection 1984136176305549056
[15/Mar/2007:12:15:28 PDT] Creating new Producer 1984136176305558016 on Q:myTestQueue for connection 1984136176305549056
[15/Mar/2007:12:15:28 PDT] Producer Producer[1984136176305558016,Q:myTestQueue,1984136176305549056] is true
[15/Mar/2007:12:15:28 PDT] Cleaning up transactions on connection IMQConn[CLOSED,[email protected]:39174,jms:39104]
[15/Mar/2007:12:15:28 PDT] closed connection IMQConn[DESTROYING,[email protected]:39174,jms:39104]:
java.io.IOException: [B4117]: Unexpected Broker Exception: [destroyed Connection]
at com.sun.messaging.jmq.jmsserver.service.imq.IMQConnection.writeData (IMQConnection.java:1930)
at com.sun.messaging.jmq.jmsserver.service.imq.IMQConnection.process(IMQConnection.java:803)
at com.sun.messaging.jmq.jmsserver.service.imq.OperationRunnable.process(OperationRunnable.java :141)
at com.sun.messaging.jmq.jmsserver.util.pool.BasicRunnable.run(BasicRunnable.java:459)
at java.lang.Thread.run(Thread.java:595)
[15/Mar/2007:12:15:28 PDT] [B1066]: Closing: [email protected]:39174->jms:39104 because "[B0059]: Client closed the connection". Count=0
[15/Mar/2007:12:15:47 PDT]
Connections: 0 JVM Heap: 33226752 bytes (30083968 free) Threads: 2 (14-1010)
In: 2 msgs (1632 bytes) 28 pkts (4949 bytes)
Out: 0 msgs (0 bytes) 28 pkts (5590 bytes)
Rate In: 0 msgs/sec (15 bytes/sec) 0 pkts/sec (42 bytes/sec)
Rate Out: 0 msgs/sec (0 bytes/sec) 0 pkts/sec (46 bytes/sec)

Hi Tom,
Thanks for the quick response!
I am glad to hear that the log level is the reason for the output and not an issue with the broker!
Thanks again....
-Howard

Unexpected Broker Internal Error : [transaction failed]:

Currently running glassfish v2.1 with jms broker mode set as LOCAL and remote client message listeners fail to get messages and the following is logged by imqbroker:
[23/Jun/2009:21:45:38 BST] WARNING [B3100]: Unexpected Broker Internal Error : [transaction failed]:
com.sun.messaging.jmq.jmsserver.util.BrokerException: Unexpected Broker Exception: [received message with Unknown Transaction ID -1: ignoring message]
at com.sun.messaging.jmq.jmsserver.data.TransactionList.addMessage(TransactionList.java:587)
at com.sun.messaging.jmq.jmsserver.data.TransactionList.addMessage(TransactionList.java:571)
at com.sun.messaging.jmq.jmsserver.data.handlers.DataHandler.routeMessage(DataHandler.java:448)
at com.sun.messaging.jmq.jmsserver.data.handlers.DataHandler.handle(DataHandler.java:244)
at com.sun.messaging.jmq.jmsserver.data.handlers.DataHandler.handle(DataHandler.java:97)
at com.sun.messaging.jmq.jmsserver.data.PacketRouter.handleMessage(PacketRouter.java:181)
at com.sun.messaging.jmq.jmsserver.service.imq.IMQIPConnection.readData(IMQIPConnection.java:1489)
at com.sun.messaging.jmq.jmsserver.service.imq.IMQIPConnection.process(IMQIPConnection.java:644)
at com.sun.messaging.jmq.jmsserver.service.imq.OperationRunnable.process(OperationRunnable.java:170)
at com.sun.messaging.jmq.jmsserver.util.pool.BasicRunnable.run(BasicRunnable.java:493)
at java.lang.Thread.run(Thread.java:595)
[23/Jun/2009:21:45:38 BST] WARNING [B2011]: Storing of JMS message from IMQConn[AUTHENTICATED,[email protected]:46541,jms:39771] failed:
com.sun.messaging.jmq.jmsserver.util.BrokerException: transaction failed: Unexpected Broker Exception: [received message with Unknown Transaction ID -1: ignoring message]
[23/Jun/2009:21:45:38 BST] WARNING [B2189]: Unknown transaction -1(-1), broker will not notify the client. Ignore ROLLBACK_TRANSACTION(48)
Packet: ROLLBACK_TRANSACTION(48):587-10.201.1.142(99:9a:41:23:bb:b7)-46541-1245789938570
Magic/Version: 469754818/301 Size: 112 Type: ROLLBACK_TRANSACTION(48)
Expiration: 0 Timestamp: 1245789938570
Source IP: 10.201.1.142(99:9a:41:23:bb:b7) Port: 46541 Sequence: 587
Property Offset: 76 Property Size: 36
Encryption: 0 Priority: 5
Flags: consumerID: 0
TransactionID: 0
MessageID: 587-10.201.1.142(99:9a:41:23:bb:b7)-46541-1245789938570
Properties: {JMQTransactionID=-1}
Message Body: 0 bytes
Internal Buffers (useDirect=false):
Fixed Header Buffer:java.nio.HeapByteBuffer[pos=0 lim=72 cap=72]
Any ideas? Clustering is turned off.

message broker log
# 1245801254899 Do not modify this line
[24/Jun/2009:00:54:14 BST]
================================================================================
Open Message Queue 4.3
Sun Microsystems, Inc.
Version: 4.3 (Build 7-g)
Compile: Fri Nov 7 18:14:54 PST 2008
Copyright (c) 2007 Sun Microsystems, Inc. All rights reserved. Use is
subject to license terms.
================================================================================
Java Runtime: 1.5.0_12 Sun Microsystems Inc. /usr/lib/jdk1.5.0_12/jre
[24/Jun/2009:00:54:14 BST] IMQ_HOME=/opt/our-server/glassfish/imq
[24/Jun/2009:00:54:14 BST] IMQ_VARHOME=/opt/our-server/glassfish/domains/domain1/imq
[24/Jun/2009:00:54:14 BST] Linux 2.6.16 i386 medusa.eng.dolby.net (4 cpu) root
[24/Jun/2009:00:54:14 BST] Java Heap Size: max=193920k, current=193920k
[24/Jun/2009:00:54:14 BST] Arguments: -javahome /usr/lib/jdk1.5.0_12/jre/.. -Dimq.cluster.nowaitForMasterBroker=true -varhome /opt/our-server/glassfish/domains/domain1/imq -startRmiRegistry -rmiRegistryPort 7776 -Dimq.imqcmd.user=admin -passfile /tmp/asmq23784.tmp -save -name imqbroker -port 7676 -bgnd -silent
[24/Jun/2009:00:58:35 BST] [B1065]: Accepting: [email protected]:51368->jms:35424. Count: service=12 broker=13
[24/Jun/2009:00:59:06 BST] WARNING [B3100]: Unexpected Broker Internal Error : [transaction failed]:
com.sun.messaging.jmq.jmsserver.util.BrokerException: Unexpected Broker Exception: [received message with Unknown Transaction ID -1: ignoring message]
     at com.sun.messaging.jmq.jmsserver.data.TransactionList.addMessage(TransactionList.java:587)
     at com.sun.messaging.jmq.jmsserver.data.TransactionList.addMessage(TransactionList.java:571)
     at com.sun.messaging.jmq.jmsserver.data.handlers.DataHandler.routeMessage(DataHandler.java:448)
     at com.sun.messaging.jmq.jmsserver.data.handlers.DataHandler.handle(DataHandler.java:244)
     at com.sun.messaging.jmq.jmsserver.data.handlers.DataHandler.handle(DataHandler.java:97)
     at com.sun.messaging.jmq.jmsserver.data.PacketRouter.handleMessage(PacketRouter.java:181)
     at com.sun.messaging.jmq.jmsserver.service.imq.IMQIPConnection.readData(IMQIPConnection.java:1489)
     at com.sun.messaging.jmq.jmsserver.service.imq.IMQIPConnection.process(IMQIPConnection.java:644)
     at com.sun.messaging.jmq.jmsserver.service.imq.OperationRunnable.process(OperationRunnable.java:170)
     at com.sun.messaging.jmq.jmsserver.util.pool.BasicRunnable.run(BasicRunnable.java:493)
     at java.lang.Thread.run(Thread.java:595)
[24/Jun/2009:00:59:06 BST] WARNING [B2011]: Storing of JMS message from IMQConn[AUTHENTICATED,[email protected]:54965,jms:35424] failed:
com.sun.messaging.jmq.jmsserver.util.BrokerException: transaction failed: Unexpected Broker Exception: [received message with Unknown Transaction ID -1: ignoring message]
[24/Jun/2009:00:59:06 BST] WARNING [B2189]: Unknown transaction -1(-1), broker will not notify the client. Ignore ROLLBACK_TRANSACTION(48)
     Packet: ROLLBACK_TRANSACTION(48):113-10.201.1.142(b3:b1:70:67:8e:45)-54965-1245801546716
Magic/Version: 469754818/301     Size: 112     Type: ROLLBACK_TRANSACTION(48)
Expiration: 0          Timestamp: 1245801546716
Source IP: 10.201.1.142(b3:b1:70:67:8e:45) Port: 54965     Sequence: 113
Property Offset: 76               Property Size: 36
Encryption: 0     Priority: 5
Flags:                consumerID: 0
TransactionID: 0
MessageID: 113-10.201.1.142(b3:b1:70:67:8e:45)-54965-1245801546716
Properties: {JMQTransactionID=-1}
Message Body: 0 bytes
Internal Buffers (useDirect=false):
Fixed Header Buffer:java.nio.HeapByteBuffer[pos=0 lim=72 cap=72]
[24/Jun/2009:01:09:52 BST] [B1066]: Closing: [email protected]:3031->jms:35424 because "java.net.SocketException: Connection reset". Count: service=0 broker=11
[24/Jun/2009:01:09:52 BST] [B1066]: Closing: [email protected]:3033->jms:35424 because "java.net.SocketException: Connection reset". Count: service=0 broker=10
[24/Jun/2009:01:09:54 BST] [B1066]: Closing: [email protected]:2930->jms:35424 because "java.net.SocketException: Connection reset". Count: service=0 broker=9
[24/Jun/2009:01:11:52 BST] [B1130]: Destroying auto-created destination workorderStatusTopic [Topic] inactive for 120 seconds
[24/Jun/2009:01:11:52 BST] [B1159]: Destination workorderStatusTopic [Topic] has been destroyed
[24/Jun/2009:01:11:52 BST] [B1130]: Destroying auto-created destination wfProfileStatusTopic [Topic] inactive for 120 seconds
[24/Jun/2009:01:11:52 BST] [B1159]: Destination wfProfileStatusTopic [Topic] has been destroyed
[24/Jun/2009:01:11:52 BST] [B1130]: Destroying auto-created destination sysMonitorTopic [Topic] inactive for 120 seconds
[24/Jun/2009:01:11:52 BST] [B1159]: Destination sysMonitorTopic [Topic] has been destroyed
[24/Jun/2009:01:11:52 BST] [B1130]: Destroying auto-created destination reportStatusTopic [Topic] inactive for 120 seconds
[24/Jun/2009:01:11:52 BST] [B1159]: Destination reportStatusTopic [Topic] has been destroyed
[24/Jun/2009:01:14:22 BST] [B1066]: Closing: [email protected]:37062->jms:35424 because "[B0059]: Client closed the connection". Count: service=0 broker=8
[24/Jun/2009:01:14:22 BST] [B1066]: Closing: [email protected]:55527->jms:35424 because "[B0059]: Client closed the connection". Count: service=0 broker=7
[24/Jun/2009:01:19:22 BST] [B1066]: Closing: [email protected]:36246->jms:35424 because "[B0059]: Client closed the connection". Count: service=0 broker=6
[24/Jun/2009:01:19:22 BST] [B1066]: Closing: [email protected]:54965->jms:35424 because "[B0059]: Client closed the connection". Count: service=0 broker=5
[24/Jun/2009:01:19:22 BST] [B1065]: Accepting: [email protected]:59844->jms:35424. Count: service=5 broker=6
glassfish server log snippets
[#|2009-06-24T00:59:13.547+0100|FINER|sun-appserver2.1|javax.resourceadapter.mqjmsra.outbound.connection|_ThreadID=14;_ThreadName=p: thread-pool-1; w: 8;ClassName=com.sun.messaging.jms.ra.SessionAdapter;MethodName=constructor();com.sun.messaging.jms.ra.ConnectionAdapter@171e8ba;BrokerAddress=localhost:7676(35424), ConnectionID=1429085906906648832, ReconnectEnabled: false, IsConnectedToHABroker: false;ConnectionID=1429085906906648832, SessionID=1429085906980997632;_RequestID=a8911f36-6814-472b-9d49-a7bac8f6b2d8;|ENTRY com.sun.messaging.jms.ra.ConnectionAdapter@171e8ba BrokerAddress=localhost:7676(35424), ConnectionID=1429085906906648832, ReconnectEnabled: false, IsConnectedToHABroker: false ConnectionID=1429085906906648832, SessionID=1429085906980997632|#]
[#|2009-06-24T00:59:13.598+0100|FINER|sun-appserver2.1|javax.resourceadapter.mqjmsra.outbound.connection|_ThreadID=14;_ThreadName=p: thread-pool-1; w: 8;ClassName=com.sun.messaging.jms.ra.SessionAdapter;MethodName=constructor();com.sun.messaging.jms.ra.ConnectionAdapter@171e8ba;BrokerAddress=localhost:7676(35424), ConnectionID=1429085906906648832, ReconnectEnabled: false, IsConnectedToHABroker: false;ConnectionID=1429085906906648832, SessionID=1429085906981010432;_RequestID=a8911f36-6814-472b-9d49-a7bac8f6b2d8;|ENTRY com.sun.messaging.jms.ra.ConnectionAdapter@171e8ba BrokerAddress=localhost:7676(35424), ConnectionID=1429085906906648832, ReconnectEnabled: false, IsConnectedToHABroker: false ConnectionID=1429085906906648832, SessionID=1429085906981010432|#]
.............

EJB QL "unexpected token: ( " Exception with IN operator and AND operator

Hey everyone,
Hopefully someone can help me. I am just starting to write more complex queries with EJB QL and am running into an issue. When I run my query I get an "Internal Exception: line 1:87: unexpected token: (" Exception below is my query with acording to the sun references I have managed to find looks right. Here is my query:
SELECT OBJECT(e) FROM Period e, IN (e.myScorecardItem.cyclesList) t WHERE current_date() BETWEEN e.startDate AND e.endDate AND t.id =?1
I have removed the portion with the IN navigation and it works fine, and I have removed the conditional statement and left the IN portion and that works fine but I can not get the to work together. Here is my bean relationships: Cycles have ScorecardItems have Periods. I am trying to find all the Periods that fall within a certain cycle. Any direction or help anyone can provide would be greatly appreciated.
Thanks,
Justen

It's not inherently bad - but it does depend on the optimizer getting good estimate of the data volume.
Did you test with 200 distinct values in your IN list, and can you see in the execution plan Oracle estimate of how many rows the subquery would generate.
Regards
Jonathan Lewis

CORE4007: Internal error: Unexpected Java exception thrown (java.lang.NullP

Hi,
Currently we have a custom devoloped Java application deployed in oracle iplanet webserver 7 with JDK 1.6. I am receiving the below errors. The application is not stable. It gives a 500 internal error sometimes when browsing. When i checked the error log. Below is the message.
CORE4007: Internal error: Unexpected Java exception thrown (java.lang.NullPointerException, no description), stack: java.lang.NullPointerException
Could you please throw some light on this.

You need to fix your custom developed app since it is causing the errors and instability. Tell the developers to properly verify the input data and improve their exception handling so you get better error messages that tells you what went wrong.

GP Mail: Unexpected internal exception during background execution

Hi,
I have designed a process in Guided Procedures which send mails when Approved or Rejected. I get an exception for users who have yahoo or gmail IDs.
Technical Exception:
Unexpected internal exception during background execution: The message contains non-trusted or invalid receivers
Is there any setting /configuration for sending mails to these.
Pl help
Thanks,
Vasu
Message was edited by:
Vasu Mullapudi

Hi,
are you using the Bounced Mails Framework to manage you mails? If so, one possible explanation is that BMF blocks untrusted messages.
To configure BMF options, go to the Administration workset and edit the list of trusted addresses in BMF.
More info:
<a href="http://help.sap.com/saphelp_nw70/helpdata/en/44/450862f1f014bce10000000a155369/frameset.htm">Administering the BMF</a>
<a href="http://help.sap.com/saphelp_nw70/helpdata/en/44/4491dafaab0597e10000000a155369/frameset.htm">Managing Trusted Addresses</a>
HTH
Regards, Petja

Unexpected internal Exception (RelatchRequiredException)

Hi,
I have recently upgraded to version 5.0.34 and was testing our application when I saw the following error:
com.sleepycat.je.EnvironmentFailureException: (JE 5.0.34) com.sleepycat.je.utilint.RelatchRequiredException UNEXPECTED_EXCEPTION: Unexpected internal Exception, may have side effects.
at com.sleepycat.je.EnvironmentFailureException.unexpectedException(EnvironmentFailureException.java:286)
at com.sleepycat.je.tree.BIN.fetchTarget(BIN.java:1268)
at com.sleepycat.je.Cursor.checkForInsertion(Cursor.java:3006)
at com.sleepycat.je.Cursor.retrieveNextAllowPhantoms(Cursor.java:2926)
at com.sleepycat.je.Cursor.retrieveNextNoDups(Cursor.java:2789)
at com.sleepycat.je.Cursor.retrieveNext(Cursor.java:2763)
at com.sleepycat.je.Cursor.getNext(Cursor.java:1116)
As a rough overview, the application has many threads (transactionally) inserting and removing into three separate tables. Commits are non synchronous (i.e. Transaction.commitNoSync() is being used). A separate thread regularly calls Environment.flushLog(true).
I've only seen this once so far, when the application was under very heavy load...
Any ideas?
Cheers,
Rob

OK... I've been doing some more testing and have some more information.
Firstly I have seen this a few more times though by no means is this particular error easily reproducable.
I have determined that it occurs on both jdk 1.7.0 and 1.6.0_26 (both linux, 64bit) as I wanted to rule out jdk 1.7 as a factor.
Since I had never seen this error when using v4.x of BDB I looked at the code change I hade made simultaneous with the upgrade, namely that previously in order to synchronously flush the asyncronoush transaction commits to disk I was calling Environment.sync() whereas with v5.0.34 I was calling Environment.flushFlog(true) (since this had demonstrated better performance and covered exactly the use case that I desired).
After switching this code back to sync() I could not reproduce the issue. Moreover neither did I see any of the other perplexing errors that I had been investigating (see below).
The part in my code where the error was occuring is the only place where cursors are actively used. All other transactional activity is either single record inserts, or single record deletes drived by a unique key. In the area of the code where I saw this exception being thrown, looks somewhat like this:
DatabaseEntry value = new DatabaseEntry();
value.setPartial(0, 0, true);
cursor = database.openCursor(tx, null);
status = cursor.getSearchKeyRange(key, value, LockMode.RMW);
while (status == OperationStatus.SUCCESS)
keyObject = binding.entryToObject(key);
if(keyObject.getId() != id)
break;
else
status = cursor.delete();
status = cursor.getNext(key, value, LockMode.RMW);
cursor.close();
tx.commitNoSync();
Where the idea is that the actual primary key for the table is a compound of (id,number), and we start the cursor from the key (id,0) and delete all entires until we find an entry with a different id.
Now as it happens, for the test I am running I know that there will only ever be at most one entry of the form (id, 0).
And if I change the code to remove the cursor, and instead just do a straight delete operation on the database, I again see no errors.
The other thing to note is that in addition to the Unexpected Internal Exception described above, I was seeing far more frequent LockTimeout exceptions... moreover backing off and retrying the transactions didn't seem to work - the locks seemed to be permanently locked. These timeouts also only occurred in the above part of my code, and not in any of the other transactions it was performing.
After changing to use Environment.sync() (rather than flushLog), or after removing the cursor (but keeping flishLog) these lock timeout exceptions also went away.
Finally I was seeing an even stranger (to me) error... Occaisionally my tests seemed to be completing fine, but when I came to shut down my process, closing the environment was reporting that some transactions were still uncommitted. Again - the only instances were from the transactions involving the cursor above. Now as above the only way that you can get through that code without committing is (AFAICT) by some method throwing an exception... and I was seeing no such exceptions reported.
Once again, either changing from flushLog(true) to sync(), or replacing the cursor with a straight delete stopped these issues from occurring.
So, in summary I was seeing a number of weird behaviours that only seemed to occur when I was using a cursor to delete records from my database, and when I was using flushLog() to flush the log records to disk.
Hope this is helpful... If there's anything more I can do to help you debug this issue, please let me know,
Cheers,
Rob

JDBC Unexpected Packet Exception

Hello all,
I receive a strange error when attempting to write to a blob column using the 9.2.1
version of the thin JDBC driver. The actual exception occurs when I call a flush on the blob
output stream.
Here is the relevant trace:
java.io.IOException: Io exception: Unexpected packet
at oracle.jdbc.dbaccess.DBError.SQLToIOException(DBError.java:716)
at oracle.jdbc.driver.OracleBlobOutputStream.flushBuffer(OracleBlobOutputStream.java:279)
at oracle.jdbc.driver.OracleBlobOutputStream.flush(OracleBlobOutputStream.java:215)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:131)
Any clues?
Thanks!
Christopher Fitch

Hi Gonzalo !
Please check that your XML document has the format described in
http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm
<StatementName2>
<dbTableName action=INSERT>
<table>realDbTableName</table>
<access>
<col1>val1</col1>
<col2>val2</col2>
</access>
<access>
<col1>val11</col1>
</access>
</dbTableName>
</StatementName2>
/people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
/people/siva.maranani/blog/2005/09/16/xi-how-to-on-jdbc-receiver-response
Regards,
Matias.
ps: please award point if helpful
Message was edited by:
Matias Denker
Message was edited by:
Matias Denker

Unexpected NO_DATA_FOUND exception corrupting data

First off:
Application Express 4.0.2.00.06 on Solaris
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
I'm having a very frustrating, intermittent, non-replicable problem with my ApEx application. I have seen about two dozen instances of this issue in the last 6 months. From the best of my debugging abilities, it appears that within one of my page processes is a very simple select with one bound variable (see below) that is throwing the "NO_DATA_FOUND" exception even though I know there is exactly one matching row. The data we are querying for was inserted in a transaction which was committed 18 hours prior (in the most recent case).
BEGIN
SELECT status INTO l_status FROM orders o, status s WHERE o.status_id=s.status_id AND o.order_id=:P11_ORDER_ID;
EXCEPTION WHEN NO_DATA_FOUND THEN
l_status := '';
END;
The expected result is l_status == 'OPEN' (1), but instead we're getting a null value. All of my trigger-based audit logs, debugging log, and the flashback data indicate that value of :P11_ORDER_ID is correct, the matching row existed, and o.status_id was set to integer value 1 during the time that the error occurred.
Are there any other reasons for this exception to be raised?
I've updated my debugging messages to confirm that the exception code is the source of the null value, but now I have to wait for another week or two to hopefully get the results of that test.
Thanks,
Jason Gullickson

Update -- we had another run in with this issue today, and the updated debugging message confirmed that the error message was indeed "ORA-01403: no data found" and code was 100.
Once again, the row existed, the query id was correct, and the target column was not null -- and yet we were given the NO_DATA_FOUND exception.
-Jason

PcdRuntimeException: unexpected lock exception when locking

The following error is faced while re-arranging the iViews in a page of a workset and saving it.
"Could not save page com.sap.portal.pcm.admin.ValidationException:save()of PcmAttributeSet failed! commit failed, set rollback only com.sapportals.portal.pcd.gl.PcdRuntimeException: unexpected lock exceptionwhen locking".
This error is faced only for this particular workset.
Please suggest us with the issue.
Error screenshot is attached.

Check in system admin lock objects if anything is locked
Close all browser sessions and try again
If that does not help try clearing pcd cache please note it willbdegrade performance do it after proper approvals

JMS Exception [SEND_REPLY(9)] [C4036]

com.sun.messaging.jms.JMSException: [SEND_REPLY(9)] [C4036]: A server error occurred. : transaction failed: Unexpected Broker Exception: [received message with Unknown Transaction ID -1: ignoring message] user=guest, broker=A0282.aesodev.ca:7676(1689)
     at com.sun.messaging.jmq.jmsclient.ProtocolHandler.throwServerErrorException(ProtocolHandler.java:3059)
     at com.sun.messaging.jmq.jmsclient.ProtocolHandler.writeJMSMessage(ProtocolHandler.java:1555)
     at com.sun.messaging.jmq.jmsclient.WriteChannel.sendWithFlowControl(WriteChannel.java:123)
     at com.sun.messaging.jmq.jmsclient.WriteChannel.writeJMSMessage(WriteChannel.java:76)
     at com.sun.messaging.jmq.jmsclient.Transaction.send(Transaction.java:128)
     at com.sun.messaging.jmq.jmsclient.SessionImpl.writeJMSMessage(SessionImpl.java:683)
     at com.sun.messaging.jmq.jmsclient.MessageProducerImpl.writeJMSMessage(MessageProducerImpl.java:155)
     at com.sun.messaging.jmq.jmsclient.MessageProducerImpl.writeJMSMessage(MessageProducerImpl.java:145)
     at com.sun.messaging.jmq.jmsclient.MessageProducerImpl.send(MessageProducerImpl.java:499)
     at com.sun.messaging.jmq.jmsclient.TopicPublisherImpl.publish(TopicPublisherImpl.java:73)
     at ca.aeso.itc.service.PostingService.notifyListeners(PostingService.java:437)
     at ca.aeso.itc.service.PostingService.postRealtimeCapacities(PostingService.java:220)
     at ca.aeso.itc.service.PostingService$$FastClassByCGLIB$$7a56d740.invoke(<generated>)
     at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
     at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:676)
     at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:122)
     at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:56)
     at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:144)
     at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:619)
     at ca.aeso.itc.service.PostingService$$EnhancerByCGLIB$$3626918a.postRealtimeCapacities(<generated>)
     at ca.aeso.itc.servlet.MaintainRealTimeOverrideAction.execute(MaintainRealTimeOverrideAction.java:218)
     at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:421)
     at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:226)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164)
     at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:415)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:767)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:264)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:178)
     at org.springframework.orm.hibernate.support.OpenSessionInViewFilter.doFilterInternal(OpenSessionInViewFilter.java:171)
     at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:210)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:178)
     at ca.aeso.itc.servlet.UserContextFilter.doFilter(UserContextFilter.java:54)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:210)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:178)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:263)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:225)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:132)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:933)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:184)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:653)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:534)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.doTask(ProcessorTask.java:403)
     at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:55)
|#]

Did you ever find out how to resolve this problem? I'm running into the same issue with a JMS transacted session. I know it's find in a stand a lone program but the same code fails when running in the App Server. Seems that it has something to do with the resource adapter but I can't put my finger on it?!

[SEND_REPLY(9)] [C4036]: A server error occurred. : transaction failed:

Anyone know why I'm getting this error? On the client side I'm getting the following exception:
[SEND_REPLY(9)] [C4036]: A server error occurred. : transaction failed: Unexpected Broker
Exception: [received message with Unknown Transaction ID -1: ignoring message] user=guest, broker=localhost:7676(3243)
at com.sun.messaging.jmq.jmsclient.ProtocolHandler.throwServerErrorException(ProtocolHandler.java:3059)
at com.sun.messaging.jmq.jmsclient.ProtocolHandler.writeJMSMessage(ProtocolHandler.java:1555)
at com.sun.messaging.jmq.jmsclient.WriteChannel.sendWithFlowControl(WriteChannel.java:123)
at com.sun.messaging.jmq.jmsclient.WriteChannel.writeJMSMessage(WriteChannel.java:76)
at com.sun.messaging.jmq.jmsclient.Transaction.send(Transaction.java:128)
at com.sun.messaging.jmq.jmsclient.SessionImpl.writeJMSMessage(SessionImpl.java:683)
at com.sun.messaging.jmq.jmsclient.MessageProducerImpl.writeJMSMessage(MessageProducerImpl.java:155)
at com.sun.messaging.jmq.jmsclient.MessageProducerImpl.writeJMSMessage(MessageProducerImpl.java:145)
at com.sun.messaging.jmq.jmsclient.MessageProducerImpl.send(MessageProducerImpl.java:499)
In the broker log, I'm getting this:
[03/Nov/2005:11:13:24 PST] WARNING [B3100]: Unexpected Broker Internal Error : [transaction failed] :
com.sun.messaging.jmq.jmsserver.util.BrokerException: Unexpected Broker Exception: [received message with Unknown Transaction ID -1: ignoring message]
     at com.sun.messaging.jmq.jmsserver.data.TransactionList.addMessage(TransactionList.java:216)
     at com.sun.messaging.jmq.jmsserver.data.handlers.DataHandler.handle(DataHandler.java:141)
     at com.sun.messaging.jmq.jmsserver.data.handlers.DataHandler.handle(DataHandler.java:59)
     at com.sun.messaging.jmq.jmsserver.data.PacketRouter.handleMessage(PacketRouter.java:146)
     at com.sun.messaging.jmq.jmsserver.service.imq.IMQConnection.readData(IMQConnection.java:1847)
     at com.sun.messaging.jmq.jmsserver.service.imq.IMQConnection.process(IMQConnection.java:816)
     at com.sun.messaging.jmq.jmsserver.service.imq.OperationRunnable.process(OperationRunnable.java:141)
     at com.sun.messaging.jmq.jmsserver.util.pool.BasicRunnable.run(BasicRunnable.java:459)
     at java.lang.Thread.run(Thread.java:595)
[03/Nov/2005:11:13:24 PST] ERROR [B3100]: Unexpected Broker Internal Error : [Unknown transaction: -1(-1) broker will not notify the client Ignoring ROLLBACK_TRANSACTION(48)
      Packet: ROLLBACK_TRANSACTION(48):117-192.168.0.2(e7:cb:48:e:43:5d)-4127-1131045204302
Magic/Version: 469754818/301     Size: 112      Type: ROLLBACK_TRANSACTION(48)
     Expiration: 0                 Timestamp: 1131045204302
      Source IP: 192.168.0.2(e7:cb:48:e:43:5d) Port: 4127     Sequence: 117
Property Offset: 76               Property Size: 36
     Encryption: 0     Priority: 5
          Flags:                   consumerID: 0
     TransactionID: 0
       MessageID: 117-192.168.0.2(e7:cb:48:e:43:5d)-4127-1131045204302
     Properties: {JMQTransactionID=-1}
Message Body: 0 bytes
Internal Buffers (useDirect=false):
Fixed Header Buffer:java.nio.HeapByteBuffer[pos=0 lim=72 cap=72]
]

Please provide more information,
. what is the version of MQ you are using ?
(see top of the broker log)
. are you using MQ cluster ?
. describe your application
amy

Help reqd..Not able to Starting and Testing a Message Broker

I am new to Sun Java System Message Queue. I have downloaded a trial version of Message Queue 3 2005Q4 (3.6 SP3) Platform Edition from Sun website. I have installed this on RedHat 4.0, Itanium 64 bit server, jrockit-jdk1.5.0_06 j2se. I am referring to Sun Java� System Message Queue 3 Developer�s Guide for Java Clients document, as per this I have setup Message Queue Directory Variables. After environment variables setup, trying to Starting and Testing a Message Broker. Once Run the broker startup command
"imqbrokerd -tty"
Getting following errors in terminal:
Exception in thread "Reference Handler" java.lang.StackOverflowError
at java.lang.Class.forName(Ljava.lang.String;ZLjava.lang.ClassLoader;)Ljava.lang.Class;(Unknown Source)
at java.lang.Class.forName(Ljava.lang.String;J)Ljava.lang.Class;(Unknown Source)
at java.lang.ref.Reference$ReferenceHandler.run()V(Unknown Source)
Exception in thread "Finalizer" java.lang.StackOverflowError
at java.lang.Thread.run()V(Unknown Source)
[23/Feb/2007:06:43:16 PST]
================================================================================Sun Java(tm) System Message Queue 3 2005Q4
Sun Microsystems, Inc.
Version: 3.6 SP3 (Build 02-A)
Compile: Wed Jun 22 15:30:03 PDT 2005
Copyright �� 2005 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
This product includes code licensed from RSA Data Security.
================================================================================Java Runtime: 1.5.0_06 BEA Systems, Inc. /PES-Software/jrockit-jdk1.5.0_06/jre
Exception in thread "JMQTimerThread" java.lang.StackOverflowError
at com.sun.messaging.jmq.util.timer.TimerThread.run(JMQTimer.java:410)
[23/Feb/2007:06:43:16 PST] License: Sun Java(tm) System Message Queue 3.6 Platform Edition
[23/Feb/2007:06:43:16 PST] IMQ_HOME=/opt/sun/mq
[23/Feb/2007:06:43:16 PST] IMQ_VARHOME=/var/opt/sun/mq
[23/Feb/2007:06:43:16 PST] Linux 2.6.9-42.EL ia64 rhel4 (8 cpu) root
[23/Feb/2007:06:43:16 PST] Java Heap Size: max=196608k, current=32768k
[23/Feb/2007:06:43:16 PST] Arguments: -tty
[23/Feb/2007:06:43:16 PST] [B1004]: Starting the portmapper service using tcp [ 7676, 50, * ] with min threads 1 and max threads of 1
java.lang.StackOverflowError
at java.lang.Thread.run()V(Unknown Source)
[23/Feb/2007:06:43:16 PST] WARNING [B3100]: Unexpected Broker Internal Error : [Uncaught Exception in thread Thread[JMQPortMapper,5,default]] :
java.lang.StackOverflowError
at java.lang.Thread.run()V(Unknown Source)
[23/Feb/2007:06:43:16 PST] [B1060]: Loading persistent data...
[23/Feb/2007:06:43:16 PST] Using built-in file-based persistent store: /var/opt/sun/mq/instances/imqbroker/
[23/Feb/2007:06:43:17 PST] [B1136]: Processing stored transactions
[23/Feb/2007:06:43:17 PST] [B1013]: Auto Creation of Queues is Enabled
[23/Feb/2007:06:43:17 PST] [B1151]: Loading destination mq.sys.dmq [Queue] with 0 messages
[23/Feb/2007:06:43:17 PST] [B1152]: Loading of destination mq.sys.dmq [Queue] complete
[23/Feb/2007:06:43:17 PST] [B1004]: Starting the admin service using tcp(host = *, port=0, mode=dedicated) with min threads 4 and max threads of 10
java.lang.StackOverflowError
at java.lang.Thread.run()V(Unknown Source)
[23/Feb/2007:06:43:17 PST] WARNING [B3100]: Unexpected Broker Internal Error : [Uncaught Exception in thread Thread[admin_ACCEPT,5,default]] :
java.lang.StackOverflowError
at java.lang.Thread.run()V(Unknown Source)
[23/Feb/2007:06:43:17 PST] [B1004]: Starting the jms service using tcp(host = *, port=0, mode=dedicated) with min threads 10 and max threads of 1000
java.lang.StackOverflowError
at java.lang.Thread.run()V(Unknown Source)
[23/Feb/2007:06:43:17 PST] WARNING [B3100]: Unexpected Broker Internal Error : [Uncaught Exception in thread Thread[jms_ACCEPT,5,default]] :
java.lang.StackOverflowError
at java.lang.Thread.run()V(Unknown Source)
[23/Feb/2007:06:43:17 PST] [B1039]: Broker "imqbroker@rhel4:7676" ready.
Exception in thread "Thread-1" java.lang.StackOverflowError
at com.sun.messaging.jmq.util.log.Logger.format(Logger.java:580)
at com.sun.messaging.jmq.util.log.Logger.logToAll(Logger.java:994)
at com.sun.messaging.jmq.jmsserver.brokerShutdownHook.run(Broker.java:1878)
Please suggest me how to resolve this issue..
Thanks,
Sajjan

How do you run the program?
I need to copy the compiled BasicPlugin.api under Acrobat\plug_ins folder. I can create a subfolder of plug_ins and copy the .api file there. Just one level deep: if I create a subfolder under a subfolder of plug_ins, the .api file will not be found by Acrobat.
Then I need to restart Acrobat and I find the plugin running. In particular, BasicPlugin add a new Acrobat SDK menu and a menu item under it.
If I close Acrobat and go back to Visual Studio, I can push the Debug button which will open Acrobat for me and stop the program execution at any breakpoints I have set in the code.

Unexpected Broker Exception

Similar Messages

Maybe you are looking for