[JBoss-dev] [ jboss-Bugs-812991 ] NullPointerException when adding a Doclet
Bugs item #812991, was opened at 2003-09-26 12:44 Message generated for change (Comment added) made by letiemble You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=812991group_id=22866 Category: JBoss-IDE Group: None Status: Open Resolution: None Priority: 5 Submitted By: Laurent Etiemble (letiemble) Assigned to: Laurent Etiemble (letiemble) Summary: NullPointerException when adding a Doclet Initial Comment: Eclipse Version: 2.1.1 Build id: 200306271545 JVM Version: 1.4.2_01 Build id : 1.4.2_01-b06 With the latest JBoss IDE plugin (org.jboss.ide.eclipse_1.2.0.bin.dist.zip). I created the demo project, created the bean and used the xdoclet completion to create the necessary Javadoc comments. When I select properties for the project in the Java perspective and then go to XDoclet Configurations I can add an EJB configuration, but when I try to Add Doclet and add the ejbdoclet, the properties never appear in the right column and the stack trace is dumped into the .log files (see my previous post). -- Comment By: Laurent Etiemble (letiemble) Date: 2003-09-26 12:45 Message: Logged In: YES user_id=437455 The newly created Configuration need to be selected in order to be able to add a doclet. A null check is missing about the configuration which leads the the NPE. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=812991group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-812996 ] Wrong link in AdminServlet
Bugs item #812996, was opened at 2003-09-26 11:00 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=812996group_id=22866 Category: JBossSOAP Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Stephane Nicoll (stephane_nicoll) Assigned to: Nobody/Anonymous (nobody) Summary: Wrong link in AdminServlet Initial Comment: JBoss 3.2.2RC4 I installed the jboss-net.sar in the default/deploy directory and started. Everything went fine. Then http://localhost:8080/jboss-net shows me the Axis page. When I click on the AdminServlet it should point (according to the web page) to http://localhost:8080/jboss-net/servlet/AdminServlet However, in the web.xml of the Web application, it is refered as AxisAdminServlet Any further info, just ask, I will monitor the ticket Regards, Stephane Nicoll Kiala -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=812996group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-701731 ] Problem: MDB stops reacting
(removed.destination);
if (queue == null)
log.warn(The subscription was registered with a
destination that does not exist: + removed);
try
{
queue.nackMessages(removed);
}
catch (JMSException e)
{
log.warn(Unable to nack removed subscription: +
removed, e);
}
}
}
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-26 15:34
Message:
Logged In: YES
user_id=438410
Adrian.
We still encounter the problem every time Jboss is restarted.
The logs of such restart, with all the traces you've mentioned
before enabled are here:
ftp://ftp.vocognition.com/share/jboss/20030926.zip
Ed.
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-04 20:26
Message:
Logged In: YES
user_id=438410
No, we haven't yet, cause we managed to convince ourselves
that it has been solved with 3.0.8
Now, to define it more clearly today I witness the following:
There is queue. It has 28 MDB's listening with selectors.
If I start Jboss with my ear already being in the deploy dir the
queue reports (in JMX view) 27 receivers. Then I touch my
ear, it gets redeployed and receivers are back to 28. I cannot
confirm that the problem exists in exactly the same form as it
used to be (MDB going offline after some time) but at least it
is very related one. Should I open a different bug enable
logging in something different?
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-04 16:50
Message:
Logged In: YES
user_id=438410
No, we haven't yet, cause we managed to convince ourselves
that it has been solved with 3.0.8
Now, to define it more clearly today I witness the following:
There is queue. It has 28 MDB's listening with selectors.
If I start Jboss with my ear already being in the deploy dir the
queue reports (in JMX view) 27 receivers. Then I touch my
ear, it gets redeployed and receivers are back to 28. I cannot
confirm that the problem exists in exactly the same form as it
used to be (MDB going offline after some time) but at least it
is very related one. Should I open a different bug enable
logging in something different?
--
Comment By: Adrian Brock (ejort)
Date: 2003-09-01 17:56
Message:
Logged In: YES
user_id=9459
Did you go through the logging changes I mentioned in my
previous post?
Regards,
Adrian
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-01 17:45
Message:
Logged In: YES
user_id=438410
Adrian,
We have just experienced the same problem at the
customer's with 3.0.8. Right after the Jboss is started the
number of listeners on the queue is less by one that it should
be. If I redeploy the ear it goes back again. Still after some
activity it drops again.
Looks exactly like it used to be... Sorry. Is there anything we
can do to identify what the problem is?
Ed
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-01 17:45
Message:
Logged In: YES
user_id=438410
Adrian,
We have just experienced the same problem at the
customer's with 3.0.8. Right after the Jboss is started the
number of listeners on the queue is less by one that it should
be. If I redeploy the ear it goes back again. Still after some
activity it drops again.
Looks exactly like it used to be... Sorry. Is there anything we
can do to identify what the problem is?
Ed
--
Comment By: Adrian Brock (ejort)
Date: 2003-06-25 16:19
Message:
Logged In: YES
user_id=9459
Ok, reopen if you still have problems.
I do have one outstanding fix to backport from 3.2 to 3.0,
I'll try to find time to do in the next couple of days.
Regards,
Adrian
--
Comment By: Eduard Letifov (techtime)
Date: 2003-06-25 15:56
Message:
Logged In: YES
user_id=438410
Sorry, Adrian.
Yes, we took 3.0.8 and it seems to be working, at least here
in the office we were not able to break it. We have delivered
the version with 3.0.8 to the customer and now we just have
to wait when their IT department installs it.
Personally, I think you can close this bug.
Ed.
--
Comment By: Adrian Brock (ejort)
Date: 2003-06-25 15:47
Message:
Logged In: YES
user_id=9459
ping
--
Comment By: Adrian Brock (ejort)
Date: 2003-05-23 22:08
Message:
Logged In: YES
user_id=9459
Hi can you try this again with latest CVS either 3.0 or 3.2
I just fixed a problem in the ServerSession
[JBoss-dev] [ jboss-Bugs-701731 ] Problem: MDB stops reacting
(removed.destination);
if (queue == null)
log.warn(The subscription was registered with a
destination that does not exist: + removed);
try
{
queue.nackMessages(removed);
}
catch (JMSException e)
{
log.warn(Unable to nack removed subscription: +
removed, e);
}
}
}
--
Comment By: Adrian Brock (ejort)
Date: 2003-09-26 13:23
Message:
Logged In: YES
user_id=9459
I'm not sure what I'm looking at:
Your logs show everything stops at 9pm (was that a deadlock,
did you take a threaddump?)
You reboot at 1am, there are only three messages in the system,
which are persistent messages recovered in to-talkman during
recovery.
Everything else is listening on empty destinations.
Regards,
Adrian
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-26 11:34
Message:
Logged In: YES
user_id=438410
Adrian.
We still encounter the problem every time Jboss is restarted.
The logs of such restart, with all the traces you've mentioned
before enabled are here:
ftp://ftp.vocognition.com/share/jboss/20030926.zip
Ed.
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-04 16:26
Message:
Logged In: YES
user_id=438410
No, we haven't yet, cause we managed to convince ourselves
that it has been solved with 3.0.8
Now, to define it more clearly today I witness the following:
There is queue. It has 28 MDB's listening with selectors.
If I start Jboss with my ear already being in the deploy dir the
queue reports (in JMX view) 27 receivers. Then I touch my
ear, it gets redeployed and receivers are back to 28. I cannot
confirm that the problem exists in exactly the same form as it
used to be (MDB going offline after some time) but at least it
is very related one. Should I open a different bug enable
logging in something different?
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-04 12:50
Message:
Logged In: YES
user_id=438410
No, we haven't yet, cause we managed to convince ourselves
that it has been solved with 3.0.8
Now, to define it more clearly today I witness the following:
There is queue. It has 28 MDB's listening with selectors.
If I start Jboss with my ear already being in the deploy dir the
queue reports (in JMX view) 27 receivers. Then I touch my
ear, it gets redeployed and receivers are back to 28. I cannot
confirm that the problem exists in exactly the same form as it
used to be (MDB going offline after some time) but at least it
is very related one. Should I open a different bug enable
logging in something different?
--
Comment By: Adrian Brock (ejort)
Date: 2003-09-01 13:56
Message:
Logged In: YES
user_id=9459
Did you go through the logging changes I mentioned in my
previous post?
Regards,
Adrian
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-01 13:45
Message:
Logged In: YES
user_id=438410
Adrian,
We have just experienced the same problem at the
customer's with 3.0.8. Right after the Jboss is started the
number of listeners on the queue is less by one that it should
be. If I redeploy the ear it goes back again. Still after some
activity it drops again.
Looks exactly like it used to be... Sorry. Is there anything we
can do to identify what the problem is?
Ed
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-01 13:45
Message:
Logged In: YES
user_id=438410
Adrian,
We have just experienced the same problem at the
customer's with 3.0.8. Right after the Jboss is started the
number of listeners on the queue is less by one that it should
be. If I redeploy the ear it goes back again. Still after some
activity it drops again.
Looks exactly like it used to be... Sorry. Is there anything we
can do to identify what the problem is?
Ed
--
Comment By: Adrian Brock (ejort)
Date: 2003-06-25 12:19
Message:
Logged In: YES
user_id=9459
Ok, reopen if you still have problems.
I do have one outstanding fix to backport from 3.2 to 3.0,
I'll try to find time to do in the next couple of days.
Regards,
Adrian
--
Comment By: Eduard Letifov (techtime)
Date: 2003-06-25 11:56
Message:
Logged In: YES
user_id=438410
Sorry, Adrian.
Yes, we took 3.0.8 and it seems to be working, at least here
in the office we were not able to break it. We have delivered
the version with 3.0.8 to the customer and now we just have
to wait when their IT department installs
[JBoss-dev] [ jboss-Bugs-701731 ] Problem: MDB stops reacting
(removed.destination);
if (queue == null)
log.warn(The subscription was registered with a
destination that does not exist: + removed);
try
{
queue.nackMessages(removed);
}
catch (JMSException e)
{
log.warn(Unable to nack removed subscription: +
removed, e);
}
}
}
--
Comment By: Adrian Brock (ejort)
Date: 2003-09-26 14:21
Message:
Logged In: YES
user_id=9459
I don't suppose you did listReceivers() on the queue so we can
see which one is missing?
The only modification you are missing after 3.0.8 in the 3.0
branch is
this one (this fixes a copy on write bug that might show up
on an AS400):
http://cvs.sourceforge.net/viewcvs.py/jboss/jbossmq/src/main/org/jboss/mq/server/JMSDestinationManager.java?only_with_tag=Branch_3_0
Once 3.2.2 goes final I will be backporting all the latest
changes/fixes
into 3.0
Regards,
Adrian
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-26 13:33
Message:
Logged In: YES
user_id=438410
Adrian,
thanks for quick response. At 9pm customer stopped
working. I don't think there was any problem with that. Then
at 1 am the kill Jboss process (we've asked them several
times not to do this but so far they don't listen) Then they
start it again automatically. The problem is that by morning
the number of receivers on the from-talkman queue is 27,
while actually it is 28. If I redeploy the application it goes
back to 28. If I shutdown Jboss and start it again I will get 27
again.
--
Comment By: Adrian Brock (ejort)
Date: 2003-09-26 13:23
Message:
Logged In: YES
user_id=9459
I'm not sure what I'm looking at:
Your logs show everything stops at 9pm (was that a deadlock,
did you take a threaddump?)
You reboot at 1am, there are only three messages in the system,
which are persistent messages recovered in to-talkman during
recovery.
Everything else is listening on empty destinations.
Regards,
Adrian
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-26 11:34
Message:
Logged In: YES
user_id=438410
Adrian.
We still encounter the problem every time Jboss is restarted.
The logs of such restart, with all the traces you've mentioned
before enabled are here:
ftp://ftp.vocognition.com/share/jboss/20030926.zip
Ed.
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-04 16:26
Message:
Logged In: YES
user_id=438410
No, we haven't yet, cause we managed to convince ourselves
that it has been solved with 3.0.8
Now, to define it more clearly today I witness the following:
There is queue. It has 28 MDB's listening with selectors.
If I start Jboss with my ear already being in the deploy dir the
queue reports (in JMX view) 27 receivers. Then I touch my
ear, it gets redeployed and receivers are back to 28. I cannot
confirm that the problem exists in exactly the same form as it
used to be (MDB going offline after some time) but at least it
is very related one. Should I open a different bug enable
logging in something different?
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-04 12:50
Message:
Logged In: YES
user_id=438410
No, we haven't yet, cause we managed to convince ourselves
that it has been solved with 3.0.8
Now, to define it more clearly today I witness the following:
There is queue. It has 28 MDB's listening with selectors.
If I start Jboss with my ear already being in the deploy dir the
queue reports (in JMX view) 27 receivers. Then I touch my
ear, it gets redeployed and receivers are back to 28. I cannot
confirm that the problem exists in exactly the same form as it
used to be (MDB going offline after some time) but at least it
is very related one. Should I open a different bug enable
logging in something different?
--
Comment By: Adrian Brock (ejort)
Date: 2003-09-01 13:56
Message:
Logged In: YES
user_id=9459
Did you go through the logging changes I mentioned in my
previous post?
Regards,
Adrian
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-01 13:45
Message:
Logged In: YES
user_id=438410
Adrian,
We have just experienced the same problem at the
customer's with 3.0.8. Right after the Jboss is started the
number of listeners on the queue is less by one that it should
be. If I redeploy the ear it goes back again. Still after some
activity it drops again.
Looks exactly like it used to be... Sorry. Is there anything we
can do to identify what the problem is?
Ed
[JBoss-dev] [ jboss-Bugs-701731 ] Problem: MDB stops reacting
(removed.destination);
if (queue == null)
log.warn(The subscription was registered with a
destination that does not exist: + removed);
try
{
queue.nackMessages(removed);
}
catch (JMSException e)
{
log.warn(Unable to nack removed subscription: +
removed, e);
}
}
}
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-26 18:36
Message:
Logged In: YES
user_id=438410
In fact I did ! The missing on is called GetSignOnMDB. The ejb-
jar and jboss.xml we use are here:
ftp://ftp.vocognition.com/share/jboss/xml.zip
Ed.
--
Comment By: Adrian Brock (ejort)
Date: 2003-09-26 18:21
Message:
Logged In: YES
user_id=9459
I don't suppose you did listReceivers() on the queue so we can
see which one is missing?
The only modification you are missing after 3.0.8 in the 3.0
branch is
this one (this fixes a copy on write bug that might show up
on an AS400):
http://cvs.sourceforge.net/viewcvs.py/jboss/jbossmq/src/main/org/jboss/mq/server/JMSDestinationManager.java?only_with_tag=Branch_3_0
Once 3.2.2 goes final I will be backporting all the latest
changes/fixes
into 3.0
Regards,
Adrian
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-26 17:33
Message:
Logged In: YES
user_id=438410
Adrian,
thanks for quick response. At 9pm customer stopped
working. I don't think there was any problem with that. Then
at 1 am the kill Jboss process (we've asked them several
times not to do this but so far they don't listen) Then they
start it again automatically. The problem is that by morning
the number of receivers on the from-talkman queue is 27,
while actually it is 28. If I redeploy the application it goes
back to 28. If I shutdown Jboss and start it again I will get 27
again.
--
Comment By: Adrian Brock (ejort)
Date: 2003-09-26 17:23
Message:
Logged In: YES
user_id=9459
I'm not sure what I'm looking at:
Your logs show everything stops at 9pm (was that a deadlock,
did you take a threaddump?)
You reboot at 1am, there are only three messages in the system,
which are persistent messages recovered in to-talkman during
recovery.
Everything else is listening on empty destinations.
Regards,
Adrian
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-26 15:34
Message:
Logged In: YES
user_id=438410
Adrian.
We still encounter the problem every time Jboss is restarted.
The logs of such restart, with all the traces you've mentioned
before enabled are here:
ftp://ftp.vocognition.com/share/jboss/20030926.zip
Ed.
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-04 20:26
Message:
Logged In: YES
user_id=438410
No, we haven't yet, cause we managed to convince ourselves
that it has been solved with 3.0.8
Now, to define it more clearly today I witness the following:
There is queue. It has 28 MDB's listening with selectors.
If I start Jboss with my ear already being in the deploy dir the
queue reports (in JMX view) 27 receivers. Then I touch my
ear, it gets redeployed and receivers are back to 28. I cannot
confirm that the problem exists in exactly the same form as it
used to be (MDB going offline after some time) but at least it
is very related one. Should I open a different bug enable
logging in something different?
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-04 16:50
Message:
Logged In: YES
user_id=438410
No, we haven't yet, cause we managed to convince ourselves
that it has been solved with 3.0.8
Now, to define it more clearly today I witness the following:
There is queue. It has 28 MDB's listening with selectors.
If I start Jboss with my ear already being in the deploy dir the
queue reports (in JMX view) 27 receivers. Then I touch my
ear, it gets redeployed and receivers are back to 28. I cannot
confirm that the problem exists in exactly the same form as it
used to be (MDB going offline after some time) but at least it
is very related one. Should I open a different bug enable
logging in something different?
--
Comment By: Adrian Brock (ejort)
Date: 2003-09-01 17:56
Message:
Logged In: YES
user_id=9459
Did you go through the logging changes I mentioned in my
previous post?
Regards,
Adrian
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-01 17:45
Message:
Logged In: YES
user_id=438410
Adrian,
We have just experienced the same problem at the
customer's
[JBoss-dev] [ jboss-Bugs-802978 ] mysql database name in sql-query not encoded
Bugs item #802978, was opened at 2003-09-09 10:07 Message generated for change (Comment added) made by pilhuhn You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=802978group_id=22866 Category: JBossCMP Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Klebermass Martin (colemarcus) Assigned to: Nobody/Anonymous (nobody) Summary: mysql database name in sql-query not encoded Initial Comment: When using Database Names like abc-def using this database ( or table or field name) in the sql statement without ` arround it, causes a mysql query error. The simplest solution would be to put ` arroung every databasename,tablename and fieldname. example: using the database name w10222-test i got a show table w10222-test as 'blabla' send to the mysql server. Martin [EMAIL PROTECTED] -- Comment By: Heiko W.Rupp (pilhuhn) Date: 2003-09-26 17:04 Message: Logged In: YES user_id=217112 I am currently not sure if database names with dashes in them are correct sql even if mysql allows them. So I am not sure, if this should be supported or not. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=802978group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-716887 ] Incorrect length function syntax for Sybase
Bugs item #716887, was opened at 2003-04-07 20:05 Message generated for change (Comment added) made by pilhuhn You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=716887group_id=22866 Category: JBossCMP Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Vinh Nguyen (softwaremasters) Assigned to: Nobody/Anonymous (nobody) Summary: Incorrect length function syntax for Sybase Initial Comment: The correct Sybase syntax for the length function is char_length, not len. -- Comment By: Heiko W.Rupp (pilhuhn) Date: 2003-09-26 17:11 Message: Logged In: YES user_id=217112 What is the difference between datalength(?1) and char_length(?1) . Or are they equivalent? -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=716887group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-802978 ] mysql database name in sql-query not encoded
Bugs item #802978, was opened at 2003-09-09 10:07 Message generated for change (Comment added) made by colemarcus You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=802978group_id=22866 Category: JBossCMP Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Klebermass Martin (colemarcus) Assigned to: Nobody/Anonymous (nobody) Summary: mysql database name in sql-query not encoded Initial Comment: When using Database Names like abc-def using this database ( or table or field name) in the sql statement without ` arround it, causes a mysql query error. The simplest solution would be to put ` arroung every databasename,tablename and fieldname. example: using the database name w10222-test i got a show table w10222-test as 'blabla' send to the mysql server. Martin [EMAIL PROTECTED] -- Comment By: Klebermass Martin (colemarcus) Date: 2003-09-26 17:14 Message: Logged In: YES user_id=129118 Well i am sure that it is allowed in mysql. well first it works and second, a few days ago i submitted another bug concerning dashes in the name to mysql , and at the moment they are fixing it ( or at least one of the developer sayed that that problem will be fixed). -- Comment By: Heiko W.Rupp (pilhuhn) Date: 2003-09-26 17:04 Message: Logged In: YES user_id=217112 I am currently not sure if database names with dashes in them are correct sql even if mysql allows them. So I am not sure, if this should be supported or not. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=802978group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-802978 ] mysql database name in sql-query not encoded
Bugs item #802978, was opened at 2003-09-09 10:07 Message generated for change (Comment added) made by pilhuhn You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=802978group_id=22866 Category: JBossCMP Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Klebermass Martin (colemarcus) Assigned to: Heiko W.Rupp (pilhuhn) Summary: mysql database name in sql-query not encoded Initial Comment: When using Database Names like abc-def using this database ( or table or field name) in the sql statement without ` arround it, causes a mysql query error. The simplest solution would be to put ` arroung every databasename,tablename and fieldname. example: using the database name w10222-test i got a show table w10222-test as 'blabla' send to the mysql server. Martin [EMAIL PROTECTED] -- Comment By: Heiko W.Rupp (pilhuhn) Date: 2003-09-26 17:21 Message: Logged In: YES user_id=217112 I'll have a look at it. -- Comment By: Klebermass Martin (colemarcus) Date: 2003-09-26 17:14 Message: Logged In: YES user_id=129118 Well i am sure that it is allowed in mysql. well first it works and second, a few days ago i submitted another bug concerning dashes in the name to mysql , and at the moment they are fixing it ( or at least one of the developer sayed that that problem will be fixed). -- Comment By: Heiko W.Rupp (pilhuhn) Date: 2003-09-26 17:04 Message: Logged In: YES user_id=217112 I am currently not sure if database names with dashes in them are correct sql even if mysql allows them. So I am not sure, if this should be supported or not. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=802978group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-701731 ] Problem: MDB stops reacting
(removed.destination);
if (queue == null)
log.warn(The subscription was registered with a
destination that does not exist: + removed);
try
{
queue.nackMessages(removed);
}
catch (JMSException e)
{
log.warn(Unable to nack removed subscription: +
removed, e);
}
}
}
--
Comment By: Adrian Brock (ejort)
Date: 2003-09-26 16:30
Message:
Logged In: YES
user_id=9459
Found the problem.
Once I saw the log, it was obvious where to look.
The enabled flag in ClientConsumer wasn't synchronized
which meant block subscriptions could be missed during
connection.start();
Attached the fixed version of the source.
Regards,
Adrian
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-26 14:36
Message:
Logged In: YES
user_id=438410
In fact I did ! The missing on is called GetSignOnMDB. The ejb-
jar and jboss.xml we use are here:
ftp://ftp.vocognition.com/share/jboss/xml.zip
Ed.
--
Comment By: Adrian Brock (ejort)
Date: 2003-09-26 14:21
Message:
Logged In: YES
user_id=9459
I don't suppose you did listReceivers() on the queue so we can
see which one is missing?
The only modification you are missing after 3.0.8 in the 3.0
branch is
this one (this fixes a copy on write bug that might show up
on an AS400):
http://cvs.sourceforge.net/viewcvs.py/jboss/jbossmq/src/main/org/jboss/mq/server/JMSDestinationManager.java?only_with_tag=Branch_3_0
Once 3.2.2 goes final I will be backporting all the latest
changes/fixes
into 3.0
Regards,
Adrian
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-26 13:33
Message:
Logged In: YES
user_id=438410
Adrian,
thanks for quick response. At 9pm customer stopped
working. I don't think there was any problem with that. Then
at 1 am the kill Jboss process (we've asked them several
times not to do this but so far they don't listen) Then they
start it again automatically. The problem is that by morning
the number of receivers on the from-talkman queue is 27,
while actually it is 28. If I redeploy the application it goes
back to 28. If I shutdown Jboss and start it again I will get 27
again.
--
Comment By: Adrian Brock (ejort)
Date: 2003-09-26 13:23
Message:
Logged In: YES
user_id=9459
I'm not sure what I'm looking at:
Your logs show everything stops at 9pm (was that a deadlock,
did you take a threaddump?)
You reboot at 1am, there are only three messages in the system,
which are persistent messages recovered in to-talkman during
recovery.
Everything else is listening on empty destinations.
Regards,
Adrian
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-26 11:34
Message:
Logged In: YES
user_id=438410
Adrian.
We still encounter the problem every time Jboss is restarted.
The logs of such restart, with all the traces you've mentioned
before enabled are here:
ftp://ftp.vocognition.com/share/jboss/20030926.zip
Ed.
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-04 16:26
Message:
Logged In: YES
user_id=438410
No, we haven't yet, cause we managed to convince ourselves
that it has been solved with 3.0.8
Now, to define it more clearly today I witness the following:
There is queue. It has 28 MDB's listening with selectors.
If I start Jboss with my ear already being in the deploy dir the
queue reports (in JMX view) 27 receivers. Then I touch my
ear, it gets redeployed and receivers are back to 28. I cannot
confirm that the problem exists in exactly the same form as it
used to be (MDB going offline after some time) but at least it
is very related one. Should I open a different bug enable
logging in something different?
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-04 12:50
Message:
Logged In: YES
user_id=438410
No, we haven't yet, cause we managed to convince ourselves
that it has been solved with 3.0.8
Now, to define it more clearly today I witness the following:
There is queue. It has 28 MDB's listening with selectors.
If I start Jboss with my ear already being in the deploy dir the
queue reports (in JMX view) 27 receivers. Then I touch my
ear, it gets redeployed and receivers are back to 28. I cannot
confirm that the problem exists in exactly the same form as it
used to be (MDB going offline after some time) but at least it
is very related one. Should I open a different bug enable
logging in something different
[JBoss-dev] [ jboss-Bugs-701731 ] Problem: MDB stops reacting
(removed.destination);
if (queue == null)
log.warn(The subscription was registered with a
destination that does not exist: + removed);
try
{
queue.nackMessages(removed);
}
catch (JMSException e)
{
log.warn(Unable to nack removed subscription: +
removed, e);
}
}
}
--
Comment By: Adrian Brock (ejort)
Date: 2003-09-26 16:30
Message:
Logged In: YES
user_id=9459
Found the problem.
Once I saw the log, it was obvious where to look.
The enabled flag in ClientConsumer wasn't synchronized
which meant block subscriptions could be missed during
connection.start();
Attached the fixed version of the source.
Regards,
Adrian
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-26 14:36
Message:
Logged In: YES
user_id=438410
In fact I did ! The missing on is called GetSignOnMDB. The ejb-
jar and jboss.xml we use are here:
ftp://ftp.vocognition.com/share/jboss/xml.zip
Ed.
--
Comment By: Adrian Brock (ejort)
Date: 2003-09-26 14:21
Message:
Logged In: YES
user_id=9459
I don't suppose you did listReceivers() on the queue so we can
see which one is missing?
The only modification you are missing after 3.0.8 in the 3.0
branch is
this one (this fixes a copy on write bug that might show up
on an AS400):
http://cvs.sourceforge.net/viewcvs.py/jboss/jbossmq/src/main/org/jboss/mq/server/JMSDestinationManager.java?only_with_tag=Branch_3_0
Once 3.2.2 goes final I will be backporting all the latest
changes/fixes
into 3.0
Regards,
Adrian
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-26 13:33
Message:
Logged In: YES
user_id=438410
Adrian,
thanks for quick response. At 9pm customer stopped
working. I don't think there was any problem with that. Then
at 1 am the kill Jboss process (we've asked them several
times not to do this but so far they don't listen) Then they
start it again automatically. The problem is that by morning
the number of receivers on the from-talkman queue is 27,
while actually it is 28. If I redeploy the application it goes
back to 28. If I shutdown Jboss and start it again I will get 27
again.
--
Comment By: Adrian Brock (ejort)
Date: 2003-09-26 13:23
Message:
Logged In: YES
user_id=9459
I'm not sure what I'm looking at:
Your logs show everything stops at 9pm (was that a deadlock,
did you take a threaddump?)
You reboot at 1am, there are only three messages in the system,
which are persistent messages recovered in to-talkman during
recovery.
Everything else is listening on empty destinations.
Regards,
Adrian
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-26 11:34
Message:
Logged In: YES
user_id=438410
Adrian.
We still encounter the problem every time Jboss is restarted.
The logs of such restart, with all the traces you've mentioned
before enabled are here:
ftp://ftp.vocognition.com/share/jboss/20030926.zip
Ed.
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-04 16:26
Message:
Logged In: YES
user_id=438410
No, we haven't yet, cause we managed to convince ourselves
that it has been solved with 3.0.8
Now, to define it more clearly today I witness the following:
There is queue. It has 28 MDB's listening with selectors.
If I start Jboss with my ear already being in the deploy dir the
queue reports (in JMX view) 27 receivers. Then I touch my
ear, it gets redeployed and receivers are back to 28. I cannot
confirm that the problem exists in exactly the same form as it
used to be (MDB going offline after some time) but at least it
is very related one. Should I open a different bug enable
logging in something different?
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-04 12:50
Message:
Logged In: YES
user_id=438410
No, we haven't yet, cause we managed to convince ourselves
that it has been solved with 3.0.8
Now, to define it more clearly today I witness the following:
There is queue. It has 28 MDB's listening with selectors.
If I start Jboss with my ear already being in the deploy dir the
queue reports (in JMX view) 27 receivers. Then I touch my
ear, it gets redeployed and receivers are back to 28. I cannot
confirm that the problem exists in exactly the same form as it
used to be (MDB going offline after some time) but at least it
is very related one. Should I open a different bug enable
logging in something different
[JBoss-dev] [ jboss-Bugs-701731 ] Problem: MDB stops reacting
(removed.destination);
if (queue == null)
log.warn(The subscription was registered with a
destination that does not exist: + removed);
try
{
queue.nackMessages(removed);
}
catch (JMSException e)
{
log.warn(Unable to nack removed subscription: +
removed, e);
}
}
}
--
Comment By: Adrian Brock (ejort)
Date: 2003-09-26 16:30
Message:
Logged In: YES
user_id=9459
Found the problem.
Once I saw the log, it was obvious where to look.
The enabled flag in ClientConsumer wasn't synchronized
which meant block subscriptions could be missed during
connection.start();
Attached the fixed version of the source.
Regards,
Adrian
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-26 14:36
Message:
Logged In: YES
user_id=438410
In fact I did ! The missing on is called GetSignOnMDB. The ejb-
jar and jboss.xml we use are here:
ftp://ftp.vocognition.com/share/jboss/xml.zip
Ed.
--
Comment By: Adrian Brock (ejort)
Date: 2003-09-26 14:21
Message:
Logged In: YES
user_id=9459
I don't suppose you did listReceivers() on the queue so we can
see which one is missing?
The only modification you are missing after 3.0.8 in the 3.0
branch is
this one (this fixes a copy on write bug that might show up
on an AS400):
http://cvs.sourceforge.net/viewcvs.py/jboss/jbossmq/src/main/org/jboss/mq/server/JMSDestinationManager.java?only_with_tag=Branch_3_0
Once 3.2.2 goes final I will be backporting all the latest
changes/fixes
into 3.0
Regards,
Adrian
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-26 13:33
Message:
Logged In: YES
user_id=438410
Adrian,
thanks for quick response. At 9pm customer stopped
working. I don't think there was any problem with that. Then
at 1 am the kill Jboss process (we've asked them several
times not to do this but so far they don't listen) Then they
start it again automatically. The problem is that by morning
the number of receivers on the from-talkman queue is 27,
while actually it is 28. If I redeploy the application it goes
back to 28. If I shutdown Jboss and start it again I will get 27
again.
--
Comment By: Adrian Brock (ejort)
Date: 2003-09-26 13:23
Message:
Logged In: YES
user_id=9459
I'm not sure what I'm looking at:
Your logs show everything stops at 9pm (was that a deadlock,
did you take a threaddump?)
You reboot at 1am, there are only three messages in the system,
which are persistent messages recovered in to-talkman during
recovery.
Everything else is listening on empty destinations.
Regards,
Adrian
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-26 11:34
Message:
Logged In: YES
user_id=438410
Adrian.
We still encounter the problem every time Jboss is restarted.
The logs of such restart, with all the traces you've mentioned
before enabled are here:
ftp://ftp.vocognition.com/share/jboss/20030926.zip
Ed.
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-04 16:26
Message:
Logged In: YES
user_id=438410
No, we haven't yet, cause we managed to convince ourselves
that it has been solved with 3.0.8
Now, to define it more clearly today I witness the following:
There is queue. It has 28 MDB's listening with selectors.
If I start Jboss with my ear already being in the deploy dir the
queue reports (in JMX view) 27 receivers. Then I touch my
ear, it gets redeployed and receivers are back to 28. I cannot
confirm that the problem exists in exactly the same form as it
used to be (MDB going offline after some time) but at least it
is very related one. Should I open a different bug enable
logging in something different?
--
Comment By: Eduard Letifov (techtime)
Date: 2003-09-04 12:50
Message:
Logged In: YES
user_id=438410
No, we haven't yet, cause we managed to convince ourselves
that it has been solved with 3.0.8
Now, to define it more clearly today I witness the following:
There is queue. It has 28 MDB's listening with selectors.
If I start Jboss with my ear already being in the deploy dir the
queue reports (in JMX view) 27 receivers. Then I touch my
ear, it gets redeployed and receivers are back to 28. I cannot
confirm that the problem exists in exactly the same form as it
used to be (MDB going offline after some time) but at least it
is very related one. Should I open a different bug enable
logging in something different
[JBoss-dev] [ jboss-Bugs-435958 ] Out of Memory eception after many redepl
Bugs item #435958, was opened at 2001-06-25 04:53 Message generated for change (Settings changed) made by juhalindfors You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=435958group_id=22866 Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Andreas Schaefer (schaefera) Summary: Out of Memory eception after many redepl Initial Comment: This behavior has been observed on Windows 2000 SP2, running Sun JDK 1.3.1 and jBoss2.2.2 both Tomcat and Jetty bundles. After many EAR hot redeployments in a short period of time, (prehaps one every 5 to 20 minutes over a period of 6 hours) a redeployment will result in Out of Memory exceptions being thrown. This happens with both the Tomcat and Jetty bundles, but the error is much more clear with Jetty. In the case of Tomcat, it appears to redeploy correctly but creates a variety of errors when the app is run. -- Comment By: Tim McCune (javajedi) Date: 2003-09-26 01:22 Message: Logged In: YES user_id=62441 This still happens as of version 3.2. -- Comment By: Juha Lindfors (juhalindfors) Date: 2003-09-26 00:51 Message: Logged In: YES user_id=175239 Resubmit with a more recent JBoss version if you believe this is still a problem. -- Comment By: Tim McCune (javajedi) Date: 2003-03-18 00:07 Message: Logged In: YES user_id=62441 This is still happening. See http://jboss.org/forums/thread.jsp?forum=121thread=27888 Can you please reopen this bug? -- Comment By: Andreas Schaefer (schaefera) Date: 2001-10-30 04:07 Message: Logged In: YES user_id=70434 Need more information about what is deployed. Unfortunately memory is always limited and therefore hot deployment will one time reach a limit because all the loaded classes are not removed from the classloaders. But to see where a problem is I have to know what is deployed and maybe a error stack trace. -- Comment By: Andreas Schaefer (schaefera) Date: 2001-10-30 04:03 Message: Logged In: YES user_id=70434 Need more information about what is deployed. Unfortunately memory is always limited and therefore hot deployment will one time reach a limit because all the loaded classes are not removed from the classloaders. But to see where a problem is I have to know what is deployed and maybe a error stack trace. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=435958group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-435958 ] Out of Memory eception after many redepl
Bugs item #435958, was opened at 2001-06-25 04:53 Message generated for change (Comment added) made by juhalindfors You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=435958group_id=22866 Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Andreas Schaefer (schaefera) Summary: Out of Memory eception after many redepl Initial Comment: This behavior has been observed on Windows 2000 SP2, running Sun JDK 1.3.1 and jBoss2.2.2 both Tomcat and Jetty bundles. After many EAR hot redeployments in a short period of time, (prehaps one every 5 to 20 minutes over a period of 6 hours) a redeployment will result in Out of Memory exceptions being thrown. This happens with both the Tomcat and Jetty bundles, but the error is much more clear with Jetty. In the case of Tomcat, it appears to redeploy correctly but creates a variety of errors when the app is run. -- Comment By: Juha Lindfors (juhalindfors) Date: 2003-09-26 20:35 Message: Logged In: YES user_id=175239 Does changing the GC permanent collection size have an effect on how quickly you get OutofMemoryException? JDK 1.4.2, -XX:MaxPermSize=nnm -- Comment By: Tim McCune (javajedi) Date: 2003-09-26 01:22 Message: Logged In: YES user_id=62441 This still happens as of version 3.2. -- Comment By: Juha Lindfors (juhalindfors) Date: 2003-09-26 00:51 Message: Logged In: YES user_id=175239 Resubmit with a more recent JBoss version if you believe this is still a problem. -- Comment By: Tim McCune (javajedi) Date: 2003-03-18 00:07 Message: Logged In: YES user_id=62441 This is still happening. See http://jboss.org/forums/thread.jsp?forum=121thread=27888 Can you please reopen this bug? -- Comment By: Andreas Schaefer (schaefera) Date: 2001-10-30 04:07 Message: Logged In: YES user_id=70434 Need more information about what is deployed. Unfortunately memory is always limited and therefore hot deployment will one time reach a limit because all the loaded classes are not removed from the classloaders. But to see where a problem is I have to know what is deployed and maybe a error stack trace. -- Comment By: Andreas Schaefer (schaefera) Date: 2001-10-30 04:03 Message: Logged In: YES user_id=70434 Need more information about what is deployed. Unfortunately memory is always limited and therefore hot deployment will one time reach a limit because all the loaded classes are not removed from the classloaders. But to see where a problem is I have to know what is deployed and maybe a error stack trace. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=435958group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] A Bug, or a Feature in DavURLLister?
I also posted this to the forum. Before I open a bug, I thought I'd check
to see if there's a reason exploded jars can't be loaded with PROPFIND
during a netboot. Thanks!
I'm trying to use netboot, and I was under the impression that with v3.2+,
you didn't have to compact all the .war, .ear, and .jar files because of the
use of the PROPFIND WebDav feature.
From what I can tell, though, the PROPFIND is only used for directories
WITHOUT a . in their name.
From the DavURLLister class in method listMembers(URL,URLFilter,boolean):
if (scanNonDottedSubDirs getFilePartFromUrl (httpURL.toURL ()).indexOf
(.) == -1)
{
URL subUrl = new URL (url) ;
urls.addAll (listMembers (subUrl, filter, scanNonDottedSubDirs));
}
else
{
urls.add (new URL (url));
}
Is their a reason the exploded war, ear, and jar directories can't be
copied in this manner as well? Sorry if this is a stupid question.
--
Jim Brownfield
[EMAIL PROTECTED]
Radical System Solutions, Inc.
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
